Discussion Locked

Couldn't find NTLDR

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have DELL Optiplex 400MHz with NTWS install.
One time someone was doing ghost imaging on that machine.
Now when I turn on the machine I got:
BOOT: Couldn't find NTLDR
Please insert another disk.

What disk am I suppose to insert?

13 replies

by jhofferle

NTLDR is the program that brings up the menu asking you what operating system you want to boot. You're getting this error because it can't find the NTLDR file, and wants you to insert a bootable disk. You can try running NT setup, and selecting the "repair a damaged NT installation."

by pointblank

Make sure you aren't booting with a disk in the A drive, as this will give you this message.

by joeh

Hi,

Most likely when the machine was ghosted the ARC Path is differnet from the original machines ARC Path. If the system is formated FAT them your can try to boot with a DOS disk and get to the boot.ini on the new system. Then you can modify theARC Path to the correct path. Hope this helps.

Regards,
Joe

by sukesh75

As said above NTLDR is the file which is one among the list of files that NT uses at startup, the others being NTDETECT.COM, BOOT.INI and BOOTSEC.DOS. IF one of these files are missing the NT will fail to load. Try booting with the CD or if you havebootable disks try booting with that and then run the CD and repair with emergency repair disk as there is an option. This i beleive should restore your NTLDR.

by paul_beauvais

99% of the time this is becouse of your boot.ini file. the ghost image is not identical so the boot.ini file does not know where NT is. to fix this go to a machine that was imaged with the same ghost image then copy the boot.ini and put it in the root of c: of the new machine. this should fix it. if not let me know and I will send you an artical on arc paths so you can write an arc path and New boot.ini file.

by jturner

This can also be the result of an incorrectly configured boot device. If you use SCSI devices and the original setup uses device #1 in the boot.ini, then you activate another SCSI device and it becomes device #1 causing the original device to move to #2.

This discussion is closed to new replies.