W2kSBS Repair Doesnt Work....? Files in System32/config/system ...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

.... are apparently missing or damaged, but there is no actual file name
telling me which ones are missing or damaged. The exact message is
"Windows 2000 could not start because the following file is missing or
corrupt.
\WINNT\SYSTEM\CONFIG\SYSTEMced startup options for windows 2000, press F8.

You can attempt to repair this file by starting Windows 2000 Setup using the
original setup floppy disk or CDROM.
Select "r" at the first screen to start repair."

I have run the recovery console but cant use FIXBOOT or FIXMBR as I cannot
allow the partition tables or Exchange information to be damaged in any way.
I havent been able to replace files in the system folder as the message
doesnt tell me which ones are missing or corrupt.

When I try to run the Repair function Windows setup tells me it cant find a
Windows installation. I have installed the PERC 3 drivers.

I am at a loss how to recover this drive without losing information on the
drive. If anyone could help I would be very grateful.
Thanks in advance.
 
Velish said:
... are apparently missing or damaged, but there is no actual file name
telling me which ones are missing or damaged. The exact message is
"Windows 2000 could not start because the following file is missing or
corrupt.
\WINNT\SYSTEM\CONFIG\SYSTEMced startup options for windows 2000, press F8.

You can attempt to repair this file by starting Windows 2000 Setup using the
original setup floppy disk or CDROM.
Select "r" at the first screen to start repair."

I have run the recovery console but cant use FIXBOOT or FIXMBR as I cannot
allow the partition tables or Exchange information to be damaged in any way.
I havent been able to replace files in the system folder as the message
doesnt tell me which ones are missing or corrupt.

When I try to run the Repair function Windows setup tells me it cant find a
Windows installation. I have installed the PERC 3 drivers.

I am at a loss how to recover this drive without losing information on the
drive. If anyone could help I would be very grateful.
Thanks in advance.

This might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269075

On a related subject: The iron rule of computing says that all important
files must be backed up to an independent medium once a week.
Many people chose to ignore this rule until they suffer a king hit.
 
Hi Pegasus,

Thanks for this answer. It seems to be exactly related to the issue I am
having. I am now not in the office but will try it as soon as I get back.

In relation to the backup... I believe very much in the greatness of
backups, unfortunately my backup doesnt believe in itself :( It has been
failing over the last week or so sadly... which is always the way isnt it :)

Thanks again for the info... will post results soon. :)
Velish
 
In this particular case you need not worry about your files. They
are safe, even if the operating system should turn out to be hosed.
 
Hi Pegasus,

Ran the recovery console and tried to ren the files that were suggested but
the result was a rename failed message. When i tried to dir on the directory
\system32\config it wouldnt let me.

Any ideas?
Thanks
 
Unfortunately you did not say what message you received when
you tried to navigate to the "config" folder, hence what I write
below is based on guesswork.

Here are a few alternative methods to resolve your problem:

- Press F8 early during the boot phase, then select "Last Known
Good Configuration".

- Temporarily connect the disk as a slave disk in some other
Win2000/XP machine, then rename the file suggested in the
MS KB article.

- Boot the machine with a Bart PE boot CD (www.bootdisk.com),
then rename the file. To make a Bart CD, you need a CD burner,
a WinXP Professional CD (but no licence key!) and a measure
of time and patience.
 
Thanks Pegasus,

It seems to be totally sorted now. Although the rename and copy of the files
in the config folder didnt work and when i did a "dir" it came up with a
enumeration error. After running chkdsk /r I rebooted and everything is hunky
dorey. :)

Thanks
 
The website you directed me to walked me through the process for fixing my
computer. Thanks for all of your help! I am now up and running again!
 
Back
Top