NTLDR is missing.

[Roger Settle]

Hello,

I have a WIN2K machine that is coming up with the "NTLDR
is missing" error on boot.

I copied the NTLDR, NTDETECT.com, and boot.ini files to a
boot disk, booted to the boot disk, and from the command
line copied the files to the PC using the following
command:

copy ntldr c:\I386
copy ntdetect.com c:\I386

I rebooted the PC and still received the NTLDR is missing
error.

I desperately need the information of the hard drive so
reformatting the drive would be out of the question.

Any ideas? I thank you in advance for your help with
this problem.

--Roger Settle

 

[R. C. White]

Hi, Roger.

I don't know about the rest of your configuration (how many drives, which is
Drive 0, etc.), but you won't be able to boot unless ntldr, ntdetect.com and
boot.in files are in the Root of the "system partition", which is normally
Drive C:. In other words, no matter how many other copies of those files
you may have, or where they may be, you MUST have them in C:\.

So, assuming the typical hardware environment, just change your commands
ever so slightly:

copy ntldr c:\
copy ntdetect.com c:\
copy boot.ini c:\

Or, boot from the Win2K CD-ROM and run the Repair procedure, telling to only
"Inspect the startup environment" (or some similar wording; I haven't done
this in a couple of years).

RC

 

[John Doue]

Hello,

I have a WIN2K machine that is coming up with the "NTLDR
is missing" error on boot.

I copied the NTLDR, NTDETECT.com, and boot.ini files to a
boot disk, booted to the boot disk, and from the command
line copied the files to the PC using the following
command:

copy ntldr c:\I386
copy ntdetect.com c:\I386

I rebooted the PC and still received the NTLDR is missing
error.

I desperately need the information of the hard drive so
reformatting the drive would be out of the question.

Any ideas? I thank you in advance for your help with
this problem.

--Roger Settle

Boot for a dos diskette and check your c:\boot.ini file.

Usually, this problem occurs after a change of configuration and then,
the number between () indicating the boot partition no longer indicates
the correct number. Try changing this number in both instance after
"partition" by adding 1 or substracting 1 to the number in boot.ini.

If your boot.ini is corrupted, here is a sample of how it should look:

boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="WINDOWS 2000" /fastdetect

Hope this helps.

 

[R. C. White]

Hi, John.

But Roger's problem is finding NTLDR, which finds boot.ini.

The partition(#) in boot.ini points to the location of \WinNT or \Windows.
NTLDR finds boot.ini, not the other way 'round. And NTLDR is NEVER in
\WinNT; ALWAYS in the Root of the "system partition".

First the boot sector. Then C:\NTLDR. Then C:\boot.ini. Then
C:\ntdetect.com, which looks where boot.ini points to find ?:\WinNT.

When booting from a floppy, the C:\ would be A:\, of course.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

Hello,

I have a WIN2K machine that is coming up with the "NTLDR
is missing" error on boot.

I copied the NTLDR, NTDETECT.com, and boot.ini files to a
boot disk, booted to the boot disk, and from the command
line copied the files to the PC using the following
command:

copy ntldr c:\I386
copy ntdetect.com c:\I386

I rebooted the PC and still received the NTLDR is missing
error.

I desperately need the information of the hard drive so
reformatting the drive would be out of the question.

Any ideas? I thank you in advance for your help with
this problem.

--Roger Settle

Boot for a dos diskette and check your c:\boot.ini file.

Usually, this problem occurs after a change of configuration and then,
the number between () indicating the boot partition no longer indicates
the correct number. Try changing this number in both instance after
"partition" by adding 1 or substracting 1 to the number in boot.ini.

If your boot.ini is corrupted, here is a sample of how it should look:

boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="WINDOWS 2000" /fastdetect

Hope this helps.

 

[John Doue]

Hi, John.

But Roger's problem is finding NTLDR, which finds boot.ini.

The partition(#) in boot.ini points to the location of \WinNT or \Windows.
NTLDR finds boot.ini, not the other way 'round. And NTLDR is NEVER in
\WinNT; ALWAYS in the Root of the "system partition".

First the boot sector. Then C:\NTLDR. Then C:\boot.ini. Then
C:\ntdetect.com, which looks where boot.ini points to find ?:\WinNT.

When booting from a floppy, the C:\ would be A:\, of course.

RC

RC

Interesting. I did not know that but several times after I altered the
partition setup of one of my machines, the OS would refuse to boot and
would state: NTLDR not found (although it was still there). Ajusting the
partition # in both instances of Boot.ini solved the problem. Try to
alter this number on purpose on your machine, reboot and see what
message error you get. Am I correct or is my recollection fading ?

I would be curious to better understand why this is so, since it appears
to be inconsistent with what you tell me. Or am I missing something?

Regards

 

[R. C. White]

Hi, John.

Was it NTLDR not found? Or ntoskrnl.exe? That file is in the "boot folder"
(usually \WinNT or \Windows on some partition), and that folder is where
C:\boot.ini points.

But the computer never even looks for boot.ini until after NTLDR loads and
looks for it.

RC

 

[John Doue]

Hi, John.

Was it NTLDR not found? Or ntoskrnl.exe? That file is in the "boot folder"
(usually \WinNT or \Windows on some partition), and that folder is where
C:\boot.ini points.

But the computer never even looks for boot.ini until after NTLDR loads and
looks for it.

RC

RC,

It looks like my memory did not serve me well. I verified this after
altering my boot.ini file to double check this. In fact, the error
message I get is not always the same: sometimes says some file is
missing (did not jot down its name). Now you mention it, I do remember
instances when ntoskrnl.exe is, indeed, the file that is mentionned. I
certainly got mixed up in my memory between ntoskrnl.exe and NTLDR.

Thanks for correcting me and enlightening me at the same time in such a
nice manner. I appreciate it.

Regards