Wont boot!

NTDETECT failed can be a missing file:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q242/1/12.ASP&NoWebContent=1

Ran emergency repair disk. Thanks guys

No Prob

If you have some working knowledge of computers, then there is one solution I would like to bring to your attention. Only attempt this if you feel comfortable with working on the inside of your computers case. First thing you should do is unplug the affected machine and unplug all wires from the back. Remove the case and touch the chassis to ground out any static electricity. Now remove your hard disk drive by unplugging the IDE cable and power cable from it. Detach the hard drive from the machine (handle with care) and install it into another computer as the slave drive. You may need to adjust the jumper settings on the end of the hard drive that the wires plug into. Most hard drives have some type of reference on what jumpers should be crossed to make that particular drive the slave. Either using an IDE Controller Card or an existing IDE cable that has an additional adapter, install the hard drive into a different computer. Boot up the machine and navigate to Windows Explorer. The hard drive should be listed and all of it's contents. Go to the root directory, if the drive was installed as D: then that is your root, D:\. Your boot.ini file is located in the root directory of the drive. Sometimes the boot.ini file is hidden, if so, adjust your configuration to allow hidden and system files to be shown. Open your boot.ini file (should open into notepad) and inspect it. It should be fairly simple.. if you have a basic configuration on the affected machine, then your boot.ini should look something like this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

Depending on your configuration, the only thing that should be different is the name of the operating system, and possibly the stated locations.. rdisk(1)partition(1).... your's will probably be different. If there is only one partition on the drive, and it's the only drive on the affected PC, then that particular line should read:
multi(0)disk(0)rdisk(0)partition(1)\YOUR_OPERATING_SYSTEM="Your OS" /fastdetect

Hope you dont have to resort to this lengthy method, but it is definetly one way to see whats wrong. Just move the drive to another computer as the slave drive. :-)