Computing.Net > Forums > Windows NT > ntdetect fail when computer starts

ntdetect fail when computer starts

Reply to Message Icon

Original Message
Name: ernie
Date: April 24, 2002 at 08:58:25 Pacific
Subject: ntdetect fail when computer starts
Comment:

when i start my computer running windows NT, the boot process fail and i get the error message: NTDETECT FAIL.
I read from the microsoft website that the behaviour can occur if the Ntdetect.com file is missing or damaged and i needed an EMERGENCY REPAIR DISK to restore the boot files. But i dont have one. Is there any other way i can resolve this problem?
Is it possible to replace the boot files manually?


Report Offensive Message For Removal

Response Number 1
Name: trvlr
Date: April 24, 2002 at 12:54:06 Pacific
Subject: ntdetect fail when computer starts
Reply: (edit)

Options that come to mind.

1)
Do a parallel install as:

c:\temp-winnt-t

Do it via the 3 floppies (or a CD boot if allowed).

It will do several things:
It will rewrite the NT boot files completely; it will set itself as default OS to boot; it will add itself to the boot.ini/menu. It will also present you with a fresh Admin login (for this 'temp' version). Leave the passsword blank - this isn't going to be around very long... - and boot through to it. Reset default OS to boot to original version - and reboot - hopefully OK?

Once in OK, locate and remove C:\temp\winnt-t from drive; also edit out the 2 line reference to it in the boot.ini.

Job done?

The two routes below also usually work when attempting to restore damaged boot/start-up files.

A) Start a new install - and choose either an Upgrade of present installation; or even a Repair. (A Repair can be done without the ERD - at least at the level you are needing.)
Perhaps go for the Upgrade? At first reboot, stop the process, remove all discs and reboot - hopefully OK to original version.

B) Start as before and choose Repair; allow it to Repair the installation - without an ERD...

You may need to re-apply any SP you have running going via the Repair route; not totally sure about that via a Repair (in toto). Going the Upgrade route, and interrupting it shouldn't require the SP afterwards. Going a full Upgrade (no interrupting it) will probably require the SP afterwards.

More than likely the 'interupted Upgrade' should do the job. Likewise even an 'interrupted C:\temp\winnt-t' approach; (i.e. interrupting the C:\temp install at first reboot - as in the Upgrade route) may also (will probably) resolve the problem.

If the interrupted approaches, and even a true Repair and/or Upgrade don't resolve it, then go the full parallel install (C:\temp\winnt-t). This should do it.

All of the above have been tried and tested (used) by folks various, here and other forums/fora. I picked up most of them elsewhere (http://www.zdnet.com/community and http://www.virtualdr.com) a while back.

They also usually work with W2K...


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: ntdetect fail when computer starts

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software