Can't get x64 to work on Dual with Win2K (NTOSKRNL)

I was previously running dual boot with Win2K and WinXP SP1 on two
separate primary partitions (C and F respectively). After getting XP
x64 I decided to nuke my XPSP1 since I wasn't really using it and
install x64 on the old XPSP1 partition. So I booted from the x64 CD,
formatted the old XPSP1 partition, and installed x64.

While copying files, I got an error, something about "NTOSKRNL.EXE is
missing or corrupt. Please reinstall this file". The installation
continued after that and everything seemed fine until the initial boot,
and then I got the same error.

So I did what the message says and look for that file, finding it in
the AMD64 folder on the CD. I then use the expand command to extract
that file into the windows\system32 folder on the x64 partition (I've
booted into the Win2k partition to do this ofcourse). Except this
didn't fix the problem, I still get the same error message.

Anyone have any idea what the problem could be?

BigEd
Tue Dec 27 02:04:01 CST 2005



"linm@mcmaster.ca" wrote:

> I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>
>

BigEd
Tue Dec 27 02:07:22 CST 2005


I believe your problem is you can not dual boot with windows 2k and x64. I
have dual boot setup with xp pro and x64 and works great. I am by far not
expert, but
believe you have to repartition the windows 2k to ntfs and install xp pro on
that partition and then install x64 on the other partition. Ed
"linm@mcmaster.ca" wrote:

> I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>
>

Tony
Tue Dec 27 03:09:03 CST 2005

From the initial post, I assume that your Win2k sits on the C:\ partition -
this is your system drive, and this is where you should copy the file in
question - not the x64 partition, unless that is the system partition!!!

Tony. . .


<linm@mcmaster.ca> wrote in message
news:1135662725.656468.112010@g47g2000cwa.googlegroups.com...
>I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>

Rick
Tue Dec 27 05:34:21 CST 2005

Where did you get your Win x64 CD from?


linm@mcmaster.ca wrote:
> I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>

Colin
Tue Dec 27 15:29:32 CST 2005

Where did you get your information that W2k and x64 cannot be dual booted on
the same computer?

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"BigEd" <BigEd@discussions.microsoft.com> wrote in message
news:1D6C23ED-426F-426A-B423-8B0D7549520F@microsoft.com...
>
> I believe your problem is you can not dual boot with windows 2k and x64.
> I
> have dual boot setup with xp pro and x64 and works great. I am by far not
> expert, but
> believe you have to repartition the windows 2k to ntfs and install xp pro
> on
> that partition and then install x64 on the other partition. Ed
> "linm@mcmaster.ca" wrote:
>
>> I was previously running dual boot with Win2K and WinXP SP1 on two
>> separate primary partitions (C and F respectively). After getting XP
>> x64 I decided to nuke my XPSP1 since I wasn't really using it and
>> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
>> formatted the old XPSP1 partition, and installed x64.
>>
>> While copying files, I got an error, something about "NTOSKRNL.EXE is
>> missing or corrupt. Please reinstall this file". The installation
>> continued after that and everything seemed fine until the initial boot,
>> and then I got the same error.
>>
>> So I did what the message says and look for that file, finding it in
>> the AMD64 folder on the CD. I then use the expand command to extract
>> that file into the windows\system32 folder on the x64 partition (I've
>> booted into the Win2k partition to do this ofcourse). Except this
>> didn't fix the problem, I still get the same error message.
>>
>> Anyone have any idea what the problem could be?
>>
>>

me
Tue Dec 27 16:13:56 CST 2005

On 26 Dec 2005 21:52:05 -0800, linm@mcmaster.ca wrote:

>I was previously running dual boot with Win2K and WinXP SP1 on two
>separate primary partitions (C and F respectively). After getting XP
>x64 I decided to nuke my XPSP1 since I wasn't really using it and
>install x64 on the old XPSP1 partition. So I booted from the x64 CD,
>formatted the old XPSP1 partition, and installed x64.
>
>While copying files, I got an error, something about "NTOSKRNL.EXE is
>missing or corrupt. Please reinstall this file". The installation
>continued after that and everything seemed fine until the initial boot,
>and then I got the same error.
>
>So I did what the message says and look for that file, finding it in
>the AMD64 folder on the CD. I then use the expand command to extract
>that file into the windows\system32 folder on the x64 partition (I've
>booted into the Win2k partition to do this ofcourse). Except this
>didn't fix the problem, I still get the same error message.
>
>Anyone have any idea what the problem could be?

The x64 versions of ntldr and ntdetect.com need to be on your boot
drive.

John
Tue Dec 27 17:04:39 CST 2005

They need to be on the system drive. This may or may not be the boot drive



"me" <me@home.now> wrote in message
news:e2f3r154pk3d17b5qc73gr28q16smc3009@4ax.com...
> On 26 Dec 2005 21:52:05 -0800, linm@mcmaster.ca wrote:
>
>>I was previously running dual boot with Win2K and WinXP SP1 on two
>>separate primary partitions (C and F respectively). After getting XP
>>x64 I decided to nuke my XPSP1 since I wasn't really using it and
>>install x64 on the old XPSP1 partition. So I booted from the x64 CD,
>>formatted the old XPSP1 partition, and installed x64.
>>
>>While copying files, I got an error, something about "NTOSKRNL.EXE is
>>missing or corrupt. Please reinstall this file". The installation
>>continued after that and everything seemed fine until the initial boot,
>>and then I got the same error.
>>
>>So I did what the message says and look for that file, finding it in
>>the AMD64 folder on the CD. I then use the expand command to extract
>>that file into the windows\system32 folder on the x64 partition (I've
>>booted into the Win2k partition to do this ofcourse). Except this
>>didn't fix the problem, I still get the same error message.
>>
>>Anyone have any idea what the problem could be?
>
> The x64 versions of ntldr and ntdetect.com need to be on your boot
> drive.

linm
Tue Dec 27 22:34:42 CST 2005

Tony Sperling wrote:
> From the initial post, I assume that your Win2k sits on the C:\ partition -
> this is your system drive, and this is where you should copy the file in
> question - not the x64 partition, unless that is the system partition!!!
>
> Tony. . .

yeah.. my Win2K is my c:\ partition. From your answers and the answer
that the others gave it seems like this is the concensus that I should
copy that NTOSKRNL.exe file from the x64 CD into the c:\ drive. I'll
try it. Hopefully it'll work (and won't screw up my Win2K). Thanks.

linm
Tue Dec 27 22:40:55 CST 2005

me wrote:
> The x64 versions of ntldr and ntdetect.com need to be on your boot
> drive.

my Win2K folder where these files are located are
c:\winnt\servicepackfiles\i386. The error message says to put
ntoskrnl.exe in the c:\windows\system32 folder. But I don't have this
folder in my Win2K partition.

Tony
Wed Dec 28 04:13:56 CST 2005

Hmm, it will hardly work without it - on my system it is called
[C:\WINNT\SYSTEM32\] or, check how your filemanager (Windows Explorer?) is
set to display things:

[Tools | Folder Options | View tab - Select "Show hidden files and
folders" ;
De-select "Hide
extensions for known file types"
De-select "Hide
protected operating system files".

If you can boot to that system, the folder has to be there!

Tony. . .


<linm@mcmaster.ca> wrote in message
news:1135744855.015890.160900@g44g2000cwa.googlegroups.com...
> me wrote:
>> The x64 versions of ntldr and ntdetect.com need to be on your boot
>> drive.
>
> my Win2K folder where these files are located are
> c:\winnt\servicepackfiles\i386. The error message says to put
> ntoskrnl.exe in the c:\windows\system32 folder. But I don't have this
> folder in my Win2K partition.
>

Tony
Wed Dec 28 04:37:31 CST 2005

Oops, forgot to mention - the only other location for that file, that I
'think' will be O.K, would be [C:\ ] but don't use it unless you are
positive that the 'system32' folder really isn't there AND that the system
IS bootable as it is.

Tony. . .


"Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
news:O8Wx5d5CGHA.336@TK2MSFTNGP14.phx.gbl...
> Hmm, it will hardly work without it - on my system it is called
> [C:\WINNT\SYSTEM32\] or, check how your filemanager (Windows Explorer?) is
> set to display things:
>
> [Tools | Folder Options | View tab - Select "Show hidden files and
> folders" ;
> De-select "Hide
> extensions for known file types"
> De-select "Hide
> protected operating system files".
>
> If you can boot to that system, the folder has to be there!
>
> Tony. . .
>
>
> <linm@mcmaster.ca> wrote in message
> news:1135744855.015890.160900@g44g2000cwa.googlegroups.com...
>> me wrote:
>>> The x64 versions of ntldr and ntdetect.com need to be on your boot
>>> drive.
>>
>> my Win2K folder where these files are located are
>> c:\winnt\servicepackfiles\i386. The error message says to put
>> ntoskrnl.exe in the c:\windows\system32 folder. But I don't have this
>> folder in my Win2K partition.
>>
>
>

Randy
Wed Dec 28 04:31:18 CST 2005

On my Win2K system, it's in my C:\WINNT\system32 folder.

<linm@mcmaster.ca> wrote in message
news:1135744855.015890.160900@g44g2000cwa.googlegroups.com...
> me wrote:
> > The x64 versions of ntldr and ntdetect.com need to be on your boot
> > drive.
>
> my Win2K folder where these files are located are
> c:\winnt\servicepackfiles\i386. The error message says to put
> ntoskrnl.exe in the c:\windows\system32 folder. But I don't have this
> folder in my Win2K partition.
>

John
Wed Dec 28 06:16:55 CST 2005

Don't overwrite the one you have until you make a copy of it, or you are
going to regret it. The only place that file should be placed is on the x64
partition and in your Windows\system32 folder.


<linm@mcmaster.ca> wrote in message
news:1135744482.799320.41760@z14g2000cwz.googlegroups.com...
> Tony Sperling wrote:
>> From the initial post, I assume that your Win2k sits on the C:\
>> partition -
>> this is your system drive, and this is where you should copy the file in
>> question - not the x64 partition, unless that is the system partition!!!
>>
>> Tony. . .
>
> yeah.. my Win2K is my c:\ partition. From your answers and the answer
> that the others gave it seems like this is the concensus that I should
> copy that NTOSKRNL.exe file from the x64 CD into the c:\ drive. I'll
> try it. Hopefully it'll work (and won't screw up my Win2K). Thanks.
>

linm
Wed Dec 28 11:23:04 CST 2005

Tony Sperling wrote:
> Hmm, it will hardly work without it - on my system it is called
> [C:\WINNT\SYSTEM32\] or, check how your filemanager (Windows Explorer?) is
> set to display things:
>
> [Tools | Folder Options | View tab - Select "Show hidden files and
> folders" ;
> De-select "Hide
> extensions for known file types"
> De-select "Hide
> protected operating system files".
>
> If you can boot to that system, the folder has to be there!
>
> Tony. . .

oops.. sorry. my mistake. The NTOSKRNL.EXE file is indeed currently in
my c:\winnt\system32 folder. But the previous poster said I should also
copy the x64 version of ntldr and ntdetect and those two files are NOT
located in c:\winnt\system32 folder but rather the
c:\windows\servicepack\i386 folder. Do I have to replace those as well?

John
Wed Dec 28 11:53:34 CST 2005

Clean your CD and re-install x64 before you mess up your Win2k system.


<linm@mcmaster.ca> wrote in message
news:1135662725.656468.112010@g47g2000cwa.googlegroups.com...
>I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>

Tony
Wed Dec 28 13:54:43 CST 2005

Those two other - [C:\ntldr & C:\ntdetect.com, here with me] check that
location! The [servicepack] folder, I do not know about, must be some sort
of update, I would leave that alone. As John said, make backups of the
originals before copying, the idea is to make the system drive aware of
another bootable partition so that the system can present you with a
boot-menu that you can choose from.

But wait a minute, I just see you referring to [C:\winnt AND C:\windows] are
you having two installations on one partition? Let's clear this up before
taking any action, O.K.?

Tony. . .


<linm@mcmaster.ca> wrote in message
news:1135790583.979542.117080@z14g2000cwz.googlegroups.com...
> Tony Sperling wrote:
>> Hmm, it will hardly work without it - on my system it is called
>> [C:\WINNT\SYSTEM32\] or, check how your filemanager (Windows Explorer?)
>> is
>> set to display things:
>>
>> [Tools | Folder Options | View tab - Select "Show hidden files and
>> folders" ;
>> De-select
>> "Hide
>> extensions for known file types"
>> De-select
>> "Hide
>> protected operating system files".
>>
>> If you can boot to that system, the folder has to be there!
>>
>> Tony. . .
>
> oops.. sorry. my mistake. The NTOSKRNL.EXE file is indeed currently in
> my c:\winnt\system32 folder. But the previous poster said I should also
> copy the x64 version of ntldr and ntdetect and those two files are NOT
> located in c:\winnt\system32 folder but rather the
> c:\windows\servicepack\i386 folder. Do I have to replace those as well?
>

linm
Thu Dec 29 14:08:19 CST 2005

Tony Sperling wrote:
> Those two other - [C:\ntldr & C:\ntdetect.com, here with me] check that
> location! The [servicepack] folder, I do not know about, must be some sort
> of update, I would leave that alone. As John said, make backups of the
> originals before copying, the idea is to make the system drive aware of
> another bootable partition so that the system can present you with a
> boot-menu that you can choose from.
>
> But wait a minute, I just see you referring to [C:\winnt AND C:\windows] are
> you having two installations on one partition? Let's clear this up before
> taking any action, O.K.?
>
> Tony. . .

I do indeed have a c:\winnt and a c:\windows, but the latter only has
an Application Data subfolder and nothing else. The winnt folder has
all the system files. I only have one OS on the c: partition.

As for the ntldr and ntdetect files. The only place on my c: drive
where these two files are located as c:\winnt\servicepackfiles\i386

Regarding the boot menu, it does appear when I boot, as my boot.ini
appears to be ok. It gives me two options, WinXP x64 and Win2K. After I
choose the x64 one, that's when I get the error message regarding
ntoskrnl

me
Thu Dec 29 14:57:38 CST 2005

On 29 Dec 2005 12:08:19 -0800, linm@mcmaster.ca wrote:

>Tony Sperling wrote:
>> Those two other - [C:\ntldr & C:\ntdetect.com, here with me] check that
>> location! The [servicepack] folder, I do not know about, must be some sort
>> of update, I would leave that alone. As John said, make backups of the
>> originals before copying, the idea is to make the system drive aware of
>> another bootable partition so that the system can present you with a
>> boot-menu that you can choose from.
>>
>> But wait a minute, I just see you referring to [C:\winnt AND C:\windows] are
>> you having two installations on one partition? Let's clear this up before
>> taking any action, O.K.?
>>
>> Tony. . .
>
>I do indeed have a c:\winnt and a c:\windows, but the latter only has
>an Application Data subfolder and nothing else. The winnt folder has
>all the system files. I only have one OS on the c: partition.
>
>As for the ntldr and ntdetect files. The only place on my c: drive
>where these two files are located as c:\winnt\servicepackfiles\i386
>
>Regarding the boot menu, it does appear when I boot, as my boot.ini
>appears to be ok. It gives me two options, WinXP x64 and Win2K. After I
>choose the x64 one, that's when I get the error message regarding
>ntoskrnl

This is for NT and XP, but the same holds true for 2000 and XP 64 bit.
http://support.microsoft.com/default.aspx?scid=kb;en-us;315233

linm
Thu Dec 29 15:02:01 CST 2005

John Barnes wrote:
> Clean your CD and re-install x64 before you mess up your Win2k system.

yeah I tried that already. Same errror.

John
Thu Dec 29 15:21:32 CST 2005

There is something wrong with your media if you keep getting the same
missing file every time you try to install. OTOH if the copy works but you
get the missing NTOSKRNL message when the system reboots, there is another
problem.
This would indicate that the startup is finding the mbr, the ntldr which
finds the boot.ini so those should be fine. You need to be more
informative of your system, how you have the system set up. Is your drive
IDE or SATA, it sounds like 1 drive with 2 partitions. What kinds of
partitions do you have. What is your active partition.
You are failing from the point where NTDETECT.com is looking for the boot
partition and failing to be directed to the proper startup files (ie
ntoskrnl and hal)
This can be caused by a number of things which will require more information
and additional testing.


<linm@mcmaster.ca> wrote in message
news:1135886998.629377.13420@f14g2000cwb.googlegroups.com...
> John Barnes wrote:
>> Clean your CD and re-install x64 before you mess up your Win2k system.
>
> yeah I tried that already. Same errror.
>

linm
Fri Dec 30 12:46:02 CST 2005

me wrote:
> On 29 Dec 2005 12:08:19 -0800, linm@mcmaster.ca wrote:
>
> >Tony Sperling wrote:
> >> Those two other - [C:\ntldr & C:\ntdetect.com, here with me] check that
> >> location! The [servicepack] folder, I do not know about, must be some sort
> >> of update, I would leave that alone. As John said, make backups of the
> >> originals before copying, the idea is to make the system drive aware of
> >> another bootable partition so that the system can present you with a
> >> boot-menu that you can choose from.
> >>
> >> But wait a minute, I just see you referring to [C:\winnt AND C:\windows] are
> >> you having two installations on one partition? Let's clear this up before
> >> taking any action, O.K.?
> >>
> >> Tony. . .
> >
> >I do indeed have a c:\winnt and a c:\windows, but the latter only has
> >an Application Data subfolder and nothing else. The winnt folder has
> >all the system files. I only have one OS on the c: partition.
> >
> >As for the ntldr and ntdetect files. The only place on my c: drive
> >where these two files are located as c:\winnt\servicepackfiles\i386
> >
> >Regarding the boot menu, it does appear when I boot, as my boot.ini
> >appears to be ok. It gives me two options, WinXP x64 and Win2K. After I
> >choose the x64 one, that's when I get the error message regarding
> >ntoskrnl
>
> This is for NT and XP, but the same holds true for 2000 and XP 64 bit.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;315233

no I don't think this is applicable as first of all it's the ntoskrnl
not ntldr file that's missing. Second, this scenario only applies if I
installed NT/2K AFTER I installed x64, which isn't the case. My 2K has
always been there.

linm
Fri Dec 30 12:58:13 CST 2005

John Barnes wrote:
> There is something wrong with your media if you keep getting the same
> missing file every time you try to install. OTOH if the copy works but you
> get the missing NTOSKRNL message when the system reboots, there is another
> problem.
> This would indicate that the startup is finding the mbr, the ntldr which
> finds the boot.ini so those should be fine. You need to be more
> informative of your system, how you have the system set up. Is your drive
> IDE or SATA, it sounds like 1 drive with 2 partitions. What kinds of
> partitions do you have. What is your active partition.
> You are failing from the point where NTDETECT.com is looking for the boot
> partition and failing to be directed to the proper startup files (ie
> ntoskrnl and hal)
> This can be caused by a number of things which will require more information
> and additional testing.

I'm running an Athlon 64 on a NForce4SLi board. I'm running 2X 40gig
IDE on RAID stripe0 using the NVidia RAID controller. I have two
primary partitions, c: and g:. c: is FAT32 and is currently the active
primary used for my main OS Win2K and the g: is NTFS partition where
I'm trying to install x64. In addition, I have one big extended
partition with two partitions in it, d: (FAT32) and f: (NTFS)

hope that helps

John
Fri Dec 30 13:25:21 CST 2005

Are you now getting past the copy error, since that indicates a problem with
the read or write media. You should have no problems in the copy stage. I
am assuming you are loading both of the appropriate x64 nvidia raid drivers
via F6 at the start of the text phase. You can get the latest x64 drivers
from the Nvidia site. You are not finding ntoskrnl when you finish the TEXT
phase and are rebooting into the GUI phase.
Please correct anything I am not understanding.


<linm@mcmaster.ca> wrote in message
news:1135969093.501059.215760@o13g2000cwo.googlegroups.com...
> John Barnes wrote:
>> There is something wrong with your media if you keep getting the same
>> missing file every time you try to install. OTOH if the copy works but
>> you
>> get the missing NTOSKRNL message when the system reboots, there is
>> another
>> problem.
>> This would indicate that the startup is finding the mbr, the ntldr which
>> finds the boot.ini so those should be fine. You need to be more
>> informative of your system, how you have the system set up. Is your
>> drive
>> IDE or SATA, it sounds like 1 drive with 2 partitions. What kinds of
>> partitions do you have. What is your active partition.
>> You are failing from the point where NTDETECT.com is looking for the boot
>> partition and failing to be directed to the proper startup files (ie
>> ntoskrnl and hal)
>> This can be caused by a number of things which will require more
>> information
>> and additional testing.
>
> I'm running an Athlon 64 on a NForce4SLi board. I'm running 2X 40gig
> IDE on RAID stripe0 using the NVidia RAID controller. I have two
> primary partitions, c: and g:. c: is FAT32 and is currently the active
> primary used for my main OS Win2K and the g: is NTFS partition where
> I'm trying to install x64. In addition, I have one big extended
> partition with two partitions in it, d: (FAT32) and f: (NTFS)
>
> hope that helps
>

me
Fri Dec 30 14:21:33 CST 2005

On 30 Dec 2005 10:46:02 -0800, linm@mcmaster.ca wrote:

>me wrote:
>> On 29 Dec 2005 12:08:19 -0800, linm@mcmaster.ca wrote:
>>
>> >Tony Sperling wrote:
>> >> Those two other - [C:\ntldr & C:\ntdetect.com, here with me] check that
>> >> location! The [servicepack] folder, I do not know about, must be some sort
>> >> of update, I would leave that alone. As John said, make backups of the
>> >> originals before copying, the idea is to make the system drive aware of
>> >> another bootable partition so that the system can present you with a
>> >> boot-menu that you can choose from.
>> >>
>> >> But wait a minute, I just see you referring to [C:\winnt AND C:\windows] are
>> >> you having two installations on one partition? Let's clear this up before
>> >> taking any action, O.K.?
>> >>
>> >> Tony. . .
>> >
>> >I do indeed have a c:\winnt and a c:\windows, but the latter only has
>> >an Application Data subfolder and nothing else. The winnt folder has
>> >all the system files. I only have one OS on the c: partition.
>> >
>> >As for the ntldr and ntdetect files. The only place on my c: drive
>> >where these two files are located as c:\winnt\servicepackfiles\i386
>> >
>> >Regarding the boot menu, it does appear when I boot, as my boot.ini
>> >appears to be ok. It gives me two options, WinXP x64 and Win2K. After I
>> >choose the x64 one, that's when I get the error message regarding
>> >ntoskrnl
>>
>> This is for NT and XP, but the same holds true for 2000 and XP 64 bit.
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;315233
>
>no I don't think this is applicable as first of all it's the ntoskrnl
>not ntldr file that's missing. Second, this scenario only applies if I
>installed NT/2K AFTER I installed x64, which isn't the case. My 2K has
>always been there.

Without thinking about it I installed 2000 to my dual boot (XP home
and XP 64 bit) system. XP home had the symptoms described in the KB,
but XP 64 bit complained about ntoskrnl.exe being missing or corrupt
until I copied the 64 bit ntldr and ntdetect.com files to C:\

linm
Sat Dec 31 00:38:33 CST 2005

John Barnes wrote:
> Are you now getting past the copy error, since that indicates a problem with
> the read or write media. You should have no problems in the copy stage. I

I don't recall when I get the error the first time, I think it's after
copying all the files, after the first reset, and before getting into
the GUI screen for the first time. The installation continues
installing all drivers after the error. It screws up after the second
reset, ie: after it passes "finish installation".

> am assuming you are loading both of the appropriate x64 nvidia raid drivers
> via F6 at the start of the text phase. You can get the latest x64 drivers
> from the Nvidia site. You are not finding ntoskrnl when you finish the TEXT
> phase and are rebooting into the GUI phase.
> Please correct anything I am not understanding.

yeah.. I dl the x64 RAID drivers from the MB site, so that's not a
problem

linm
Sat Dec 31 00:41:03 CST 2005

me wrote:
> On 30 Dec 2005 10:46:02 -0800, linm@mcmaster.ca wrote:

> Without thinking about it I installed 2000 to my dual boot (XP home
> and XP 64 bit) system. XP home had the symptoms described in the KB,
> but XP 64 bit complained about ntoskrnl.exe being missing or corrupt
> until I copied the 64 bit ntldr and ntdetect.com files to C:\

like I said before, I would do that, except those two files aren't in
the c:\winnt\system32 folder, they're in the
c:\winnt\servicepackfiles\i386 folder, so I'm not sure. I think I'll
try it anyways. First backing up the files ofcourse.

John
Sat Dec 31 09:00:02 CST 2005

As I said before those 2 files + boot.ini need to be in the root of your
system drive. In your case, C:\ Since you get to the boot screen, maybe
you aren't searching hidden and system files.


<linm@mcmaster.ca> wrote in message
news:1136011263.003992.27450@f14g2000cwb.googlegroups.com...
> me wrote:
>> On 30 Dec 2005 10:46:02 -0800, linm@mcmaster.ca wrote:
>
>> Without thinking about it I installed 2000 to my dual boot (XP home
>> and XP 64 bit) system. XP home had the symptoms described in the KB,
>> but XP 64 bit complained about ntoskrnl.exe being missing or corrupt
>> until I copied the 64 bit ntldr and ntdetect.com files to C:\
>
> like I said before, I would do that, except those two files aren't in
> the c:\winnt\system32 folder, they're in the
> c:\winnt\servicepackfiles\i386 folder, so I'm not sure. I think I'll
> try it anyways. First backing up the files ofcourse.
>

Chutzpah
Tue Jan 10 20:41:02 CST 2006



"linm@mcmaster.ca" wrote:

> I was previously running dual boot with Win2K and WinXP SP1 on two
> separate primary partitions (C and F respectively). After getting XP
> x64 I decided to nuke my XPSP1 since I wasn't really using it and
> install x64 on the old XPSP1 partition. So I booted from the x64 CD,
> formatted the old XPSP1 partition, and installed x64.
>
> While copying files, I got an error, something about "NTOSKRNL.EXE is
> missing or corrupt. Please reinstall this file". The installation
> continued after that and everything seemed fine until the initial boot,
> and then I got the same error.
>
> So I did what the message says and look for that file, finding it in
> the AMD64 folder on the CD. I then use the expand command to extract
> that file into the windows\system32 folder on the x64 partition (I've
> booted into the Win2k partition to do this ofcourse). Except this
> didn't fix the problem, I still get the same error message.
>
> Anyone have any idea what the problem could be?
>
> I believe that 'ntoskrnl.exe' needs to be in a particular area of the partition. I have installed win2k and xp64 as a dual boot and win2k/xpPro64/xpPro as a triple boot. My experience was that the last installed system boots, the earlier ones get the ntoskrnl error message. My solution was to reinstall each OS that won't boot, using the "Repair existing installation on drive F (or whatever)" The system files will be re-written, placing ntoskrnl in an appropriate sector of the drive.