To DCLIVE, Much thanks

[thuffner3]

Dclive,
Thank you so much for all your help. So far I've been able to pretty much painlessly get back into my system having only to install device drivers and whatnot. Software is fine so far.
The only thing I did was move the SYSTEM hive from the repair folder to the SYSTEM32\CONFIG
folder and all was fine. Since I do have an extra HD installed on ther system, as soon as all the buzzers and bells are working fine. I will certainly use it as a backup device.


Thanks again

Peace
Neil

 

[Smilin]

kudos and one good bump.

 

[dclive]

Originally posted by: thuffner3
Dclive,
Thank you so much for all your help. So far I've been able to pretty much painlessly get back into my system having only to install device drivers and whatnot. Software is fine so far.
The only thing I did was move the SYSTEM hive from the repair folder to the SYSTEM32\CONFIG
folder and all was fine. Since I do have an extra HD installed on ther system, as soon as all the buzzers and bells are working fine. I will certainly use it as a backup device.


Thanks again

Peace
Neil

Great! Running NTBACKUP (and doing a system state backup) from time to time on the XP system will then create a newer, more up to date version of the registry (current at the time of the NTBACKUP) in c:\windows\repair, so that's an idea too.

Problem synopsis: Installed new device driver, and somehow the registry itself became corrupted - so badly that we couldn't even log in via recovery console.

Resolution: Ideally we'd have put the hard drive into another machine and copied the system restore point System hive data from a few days prior to the incident into c:\windows\system32\config, but we had a parallel install on there, so the restore point data was overwritten. So, you copied the original registry's SYSTEM file from c:\windows\repair to c:\windows\system32\config, and that allowed the system to boot and be workable.