fixing registry for migration without MergeIDE

[jade]

I have a crashed laptop with a working hard drive with win2000 that i want to migrate to VB. Since the computer it self isn't booting i can't fix the IDE/ATA controller problem with MergeIDE (as described here: http://virtualbox.org/wiki/Migrate_Windows).

Anyone know how to fix this manually?

[Ingo]

How do you access the hard drive?
Can you make an image?
Here are some ideas:
http://forums.virtualbox.org/viewtopic.php?t=1966

[tom909]

I am having the same problem. I cant go back to run mergeide. is there a editor for w2k registry files avaliable, where I could do manually what mergeide is doing (http://support.microsoft.com/kb/314082)?

thanks

[tom909]

?

[nxx]

I have a crashed laptop with a working hard drive with win2000 that i want to migrate to VB. Since the computer it self isn't booting i can't fix the IDE/ATA controller problem with MergeIDE (as described here: http://virtualbox.org/wiki/Migrate_Windows).

Anyone know how to fix this manually?

I have tried this with VDI, but you can do
the same with VMDK to physicall disk

Here is steps for solution with VDI:

1. create a new (temporary) VDI, install Windows into it

2. create another VDI (target)

3. copy target system to target VDI
as described here
http://forums.virtualbox.org/viewtopic.php?t=1966
i.e. xcopy D:\ F:\ /s /e /c /g /h /k /o /x /y >xcopy.log 2>&1

4. Boot temporary VDI with target VDI connected as secondary

5. download and unzip mergeide
copy mergeide.reg to
mergeide001.reg
and
mergeide002.reg

5. replace each "SYSTEM/CurrentControlSet"
in mergeide001.reg to "zzz/ControlSet001"
replace each "SYSTEM/CurrentControlSet"
in mergeide002.reg to "zzz/ControlSet002"

6. run regedt32
load hive SYSTEM from windows\system32\config
from target drive to key "zzz"
your paths will be
HKEY_LOCAL_MACHINE\zzz\ControlSet001
HKEY_LOCAL_MACHINE\zzz\ControlSet002

7. import mergeide001.reg
import mergeide002.reg
unload hive

8. copy manually
atapy.sys
intelide.sys
pciide.sys
pciidex.sys
to target windows\system32\drivers

9. if needed, boot live CD
and fix target drive with
repair console
(fixmbr, fixboot)

10. Boot target drive
It should work ok