changed setup, raid1 system won't load windows

[JClark]

I have a hardware raid1 configuration (Adaptec), win2kPro, sp4.
Running fine until I changed setup so that a password woud be required
on bootup. Now Windows won't load. Could changing something in setup
have changed the adaptec raid configuration to cause this? I of course
went back and took out the passwords in setup, but Windows still won't
load. Msg = missing system.config...or something like that.
I'd really appreciate any advice about how to restore my system.

Jack

 

[Pegasus \(MVP\)]

Please state exactly how far the boot process goes, and
quote the error message(s) verbatim.

 

[JClark]

Please state exactly how far the boot process goes, and
quote the error message(s) verbatim.

Pegasus: I'll have to do it tomorrow. Computer is at my office.
Thanks.

Jack

 

[Dave Patrick]

Asked and answered in .hardware

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

| I have a hardware raid1 configuration (Adaptec), win2kPro, sp4.
| Running fine until I changed setup so that a password woud be required
| on bootup. Now Windows won't load. Could changing something in setup
| have changed the adaptec raid configuration to cause this? I of course
| went back and took out the passwords in setup, but Windows still won't
| load. Msg = missing system.config...or something like that.
| I'd really appreciate any advice about how to restore my system.
|
| Jack

 

[JClark]

Asked and answered in .hardware

Thanks, Dave. I apologize if it is bad manners to post the question in
two groups. I wasn't sure which would be more appropriate.
Jack

 

[JClark]

Pegasus: I'll have to do it tomorrow. Computer is at my office.
Thanks.

Jack

Pegasus:
I handwrote out the verbatim message (lengthy) then in my fatigued
state idiotically left it at the office. Will post it later for your
thoughts. Meanwhile, I've restored (I think) at least a working system
with Dave Patrick's advice in .hardware. Something's not quite right,
though, and I may end up formatting and reinstalling everything.

Jack

 

[JClark]

Pegasus:
Pegasus:

What happened was that it would boot but then lock up. Mouse wouldn't
work. CTRL-ALT-DEL ineffective. Same thing in safe mode. After
numerous tries, somewhere along the line, I got this message:

Windows 2000 could not start because the following file is missing or
corrupt:
\winnt\system32\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 CD-ROM. Select 'r' at the
first screen to start repair.

I don't know what happened to the line containing
\SYSTEMced....followed by acouple of spaces then "startup options...."
etc. Looks like that error message got corrupted itself.
But anyway the \winnt\system32\config\system was restored from the
\repair folder as advised by Dave Patrick in .hardware...and after
installing a lot of hardware drivers, at least the system is
functional again.
Any idea what may have caused this file to be corrupted? I think now
it did not have anything to do with putting a password in setup or
with the Raid controller. I did run a complete virus scan with Panda
just before it happened. Wonder if that messed something up?
Many thanks for your help and with past advice as well.

Jack

 

[Pegasus \(MVP\)]

Pegasus:
Pegasus:

What happened was that it would boot but then lock up. Mouse wouldn't
work. CTRL-ALT-DEL ineffective. Same thing in safe mode. After
numerous tries, somewhere along the line, I got this message:

Windows 2000 could not start because the following file is missing or
corrupt:
\winnt\system32\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 CD-ROM. Select 'r' at the
first screen to start repair.

I don't know what happened to the line containing
\SYSTEMced....followed by acouple of spaces then "startup options...."
etc. Looks like that error message got corrupted itself.
But anyway the \winnt\system32\config\system was restored from the
\repair folder as advised by Dave Patrick in .hardware...and after
installing a lot of hardware drivers, at least the system is
functional again.
Any idea what may have caused this file to be corrupted? I think now
it did not have anything to do with putting a password in setup or
with the Raid controller. I did run a complete virus scan with Panda
just before it happened. Wonder if that messed something up?
Many thanks for your help and with past advice as well.

Jack

I'm glad you're up and running again. Just two observations:

- When a system freezes the way yours did, it's often caused by
some interrupt conflict. The usual fix is to remove all non-essential
adapters. Alternatively, you could boot into Safe Mode.

- The "corrupted" message you quote is actually covered in a
knowledge base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269075

 

[JClark]

I'm glad you're up and running again. Just two observations:

- When a system freezes the way yours did, it's often caused by
some interrupt conflict. The usual fix is to remove all non-essential
adapters. Alternatively, you could boot into Safe Mode.

- The "corrupted" message you quote is actually covered in a
knowledge base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269075

Thanks Pegasus. I did read the article referenced. It refers to a
Promise Technology adapter which I don't have, but I do have the
Adaptec Raid controller. Maybe the same thing. Anyway, as you point
out, I am up and running, so best leave well enough alone. I may get
the energy to format and clean reinstall and update everything...maybe
just to make me feel better.
Jack