I got the error when I did disaster recovery by restoring
an image to a server. Both machines are IBM servers but
different model. Suspected it is caused by the SCSI
driver which causing the OS fails to boot.
I copied the new *.sys file to c:\winnt\system32\drivers
and the new *.dll to c:\winnt\system32 using recovery
console but still fails.

Is there any way I can add the new 'SCSI service' or edit
registry in the recovery console?

"Bay" <(E-Mail Removed)> wrote in message
news:26d301c4a9ca$6bca3b40$(E-Mail Removed)...
> I got the error when I did disaster recovery by restoring
> an image to a server. Both machines are IBM servers but
> different model. Suspected it is caused by the SCSI
> driver which causing the OS fails to boot.
> I copied the new *.sys file to c:\winnt\system32\drivers
> and the new *.dll to c:\winnt\system32 using recovery
> console but still fails.
>
> Is there any way I can add the new 'SCSI service' or edit
> registry in the recovery console?

Porting an Win2000 installation to different hardware is not
really recommended. Sometimes you can do it successfully
but I would never seriously consider it for a server, due to
the high demand on reliability one places on a server. Here
is some light reading on the topic:

How to Move a Windows Installation to Different Hardware
http://support.microsoft.com/directo...;EN-US;Q249694

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/support...es/Q292175.ASP

http://support.microsoft.com/default...b;en-us;824125