A Windows 2000 system was on my old PC on the first partition of my
second harddisk. It was assigned drive letter D. After I restored a
partition image of it on a new PC, the boot process of the restored
system searches for files on E (for example winlogon.exe), then
declares E for locked and then halts unfinished. So I guess, restored
w2k assignes driver letter E to itself.

Is there a way to get the restored system to identify itself as D? If
a registry hack helped, I might do it from a parallel OS by regedt32.

Thanks for advice, Sven

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/kb/223188/

John

Sven Berg wrote:

> A Windows 2000 system was on my old PC on the first partition of my
> second harddisk. It was assigned drive letter D. After I restored a
> partition image of it on a new PC, the boot process of the restored
> system searches for files on E (for example winlogon.exe), then
> declares E for locked and then halts unfinished. So I guess, restored
> w2k assignes driver letter E to itself.
>
> Is there a way to get the restored system to identify itself as D? If
> a registry hack helped, I might do it from a parallel OS by regedt32.
>
> Thanks for advice, Sven
>

"Sven Berg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> A Windows 2000 system was on my old PC on the first partition of my
> second harddisk. It was assigned drive letter D. After I restored a
> partition image of it on a new PC, the boot process of the restored
> system searches for files on E (for example winlogon.exe), then
> declares E for locked and then halts unfinished. So I guess, restored
> w2k assignes driver letter E to itself.
>
> Is there a way to get the restored system to identify itself as D? If
> a registry hack helped, I might do it from a parallel OS by regedt32.
>
> Thanks for advice, Sven
>


That won't work for several reasons:

1) your boot files will always be on the primary partition (C even if
win2k is installed on another drive.

2) restoring an image for use on another machine is unlikely to work due to
the different hardware.

You'll save a lot of time by juts performing a fresh install on your new
machine