Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Booting error 1

Status
Not open for further replies.

remote49

Technical User
Jun 22, 2005
2
US
I restarted my windows 2k professional but was unable to boot to the desktop because of a missing file -Winnt\system32\config\systemced.It stated that I could use the repair option but I dont have the emergency repir disk to that system and was wondering if there is a way out to repair instead of fresh installation
 
Remote49;

Put your W2K install disk in the CD drive and boot from it. Don't choose the repair option; choose Install. Yes, Install. When it gets to the point that it wants to start the installation, it will say that it detected a previous installation of W2K and then then prompt you "Do you want me to try and reepair it?"

Select YES, and it will replace all of the system files without screwing up your data or installed apps. I've done thkis many times without a problem.

ERD's are only relevant if nothing has changed on the machine after the disc was created. Not too likely here with a bunch of "creative" engineers running around.....

Mike, The IT Guy. [morning]

Life is too short to drink warm beer....
 
Remote49

goto RUN type as shown without quotes " sfc /scannow " to check/repair your system files.
This will all be done on boot up.

PS. Have your Win2K CD handy it may ask for it
 
I'd try running chkdsk /p from recovery console as first attempt -
(presume you have the 2k install CD - if not get the 4 boot floppies from & start recovery console from there).

If that doesn't fix it, Prydonian's suggestion (repair reinstall - - is good). Other option would be in recovery console - rename the \Winnt\system32\config\system file to something else (eg, system.bak), then rename the system.alt file in the same folder to system. Then reboot & see if any joy.
 
Prydonain
Mike, the IT Guy Thanks for your suggestion
I tried first the recovery console but that work on a system which had a blue screen with the message inaccesible boot device but for the corrupted system file, your idea was great.
 
Glad your issue worked out and thanks for responding! It's a great help for anyone else who may run across the same problem!

Mike, The IT Guy.

[morning]


Life is too short to drink warm beer....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top