I had this problem at work the other day. It was a win2K machine on a FAT32 system, so I just used a 98 boot disk, copied ntldr from a working computer, and then booted to disk and copied it to C drive. It said access was denied and the file could not be written, but it still worked after I did that. I would assume you could do something along those lines with an NTFS partition if you use the recovery console or a PE disk of some sort. That's all the experience I've had with it and it amazingly worked, so let me know if it is lucky again!
Computer is booting from a non-bootable source. Computer hard disk drive is not properly setup in BIOS. Corrupt NTLDR and/or NTDETECT.COM file. Misconfiguration with the boot.ini file. Attempting to upgrade from a Windows 95, 98, or ME computer that is using FAT32. New hard disk drive being added. Corrupt boot sector / master boot record. Seriously corrupted version of Windows 2000 or Windows XP. Loose or Faulty IDE/EIDE hard disk drive cable.
It has solutions for all those causes on the page.
Originally posted by CerebusWhat the hell does 'NTLDR is missing' mean?
I thought it might be that it wasn't reading the hard drive or something, but I popped it into another computer and it's fine. Everything is connected right and all but I'm getting this damn message.
I'd try Google or Yahoo, but the library I'm at has them blocked... don't ask, I don't know why.
My guess is that your PC is configured as the CD or ZIP drive as the first boot device and the CD or ZIp that is in the drive (and there IS one) does not have boot capability. NTLDR is indeed a boot issue with NT based OS systems (NT, W2K, XP).
I suspect it's a CD in the drive and the system wants to boot from the CD. Take the CD out and it should boot.
Now, is it ok for me yell THEATRE! in a crowded fire?
Well, that's interesting. Basically, to the letter, I have exactly the same problem. I tried turning off the Direct X stuff (as suggested), and while it may be a bit ropey, everything DOES then play. It's confusing.