chevyavalanche said:
The crux of the issue is to get the NTbackup software to backup to the
correct drive. I am not there physically but what just happened was a
restore of the system state to the wrong drive thereby screwing it up
now. My C drive was the drive not working correctly and now my G
drive has the C system state on it. How does one force the NTbackup
to the right drive? He was booting into G drive and wanted to restore
system state to C drive.
He could have selected to restore to an Alternate Location, I'm not at a
Windows 2000 station right now so I can't check but I do believe that it
is in the NTBackup restore options. It wouldn't make much difference
because when you restore to an alternate location it doesn't restore the
complete System State, on a workstation for all intents and purposes it
would only restore the registry files, it more or less would be the same
as copying the individual files from the Regback folder to the config
folder.
As I see it now, it looks like things are going from bad to worse, I
hope that you aren't paying by the hour for this repair job! If the
machine cannot be brought back up by remote registry editing or by
replacing the registry hives with the backup copies it may be time to
cut your losses. Before you take further steps you should make sure
that all your important files are retrieved and properly stored on an
independent media source. If your backup plans included disaster or
bare metal recovery methods it may be time to put the plan in action.
If you had no disaster/bare metal recovery plans then the next thing to
try might be to do an in-place upgrade (repair) of the operating system.
How to perform an in-place upgrade of Windows 2000
http://support.microsoft.com/kb/292175
What an in-place Windows 2000 upgrade changes and what it does not change
http://support.microsoft.com/kb/306952/
John