Move an IDE Drive w/Windows 2000 or XP to A New System :: MostlyCreativeWorkshop

Main Menu

· Home
· Contact Info

Sections
· Discussion Forum
· Donations
· Downloads
· News
· News Topics
· Recommend Us
· Reviews
· Search
· Web Links

User's Login

Technical Support: Move an IDE Drive w/Windows 2000 or XP to A New System

Posted by: Jas Batra on Monday, August 12, 2002 - 04:07 PM PST

So, you've decided to move your drive with Windows 2000 (or XP) to a new system, or upgraded your motherboard, and you now get the dreaded blue screen of death before the operating system gets to the desktop. All you get is a STOP 0x0000007B error (INACCESSIBLE_BOOT_DEVICE). What now???? Well, here's what you need to do...

Well, the first thing you need to do is to get the system working again, so, put the system back in the original working configuration. If you changed the motherboard, change it back to the original. If you moved the drive to a new system, place it in the old one.

Now, for people that understand what they are doing, and how to do it, here are the "quick" steps:
1 - Extract 'Atapi.sys,' 'Intelide.sys,' 'Pciide.sys,' and 'Pciidex.sys' from '%SystemRoot%\Driver Cache\i386\Driver.cab' (or SPx.CAB if it exists, where x is the latest service pack)
2 - Copy those four files to the following location: '%SystemRoot%\System32\Drivers' (do not replace files already there)
3 - Merge the registry file found below (copy the text to notepad and save as a .reg file), or better, download it here
4 - THAT'S IT! Move it to the new system (or change the motherboard), and your system should start up.

STEP BY STEP INSTRUCTIONS FOR THOSE THAT NEED IT:
1 - Click START, go to RUN, type in "CMD" (without quotes), hit ENTER
2 - At the command prompt, type in:
"CD %SystemRoot%\Driver Cache\i386" (without quotes) hit ENTER
"dir/w" (without quotes) hit ENTER
If you are running Windows 2000, check for SPx.CAB (where x is the highest number), in the following steps, use the SPx.CAB instead of DRIVER.CAB
(If you are asked to OVEBWRITE any file, choose NO)
"expand driver.cab -f:atapi.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand driver.cab -f:intelide.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand driver.cab -f:pciide.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand driver.cab -f:pciidex.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"exit" (without quotes) hit ENTER
3 - You should now be back at the Desktop, you need to download the registry file from HERE, save it to someplace you will remember, preferably your desktop. After it is downloaded, DOUBLE-CLICK on it, you will be asked if you wish to MERGE the contents with you registry, CHOOSE YES.
4 - THAT'S IT! Your system is prepared to be moved to another system/have the motherboard changed.

HERE IS THE REGISTRY FILE (COPY IT INTO NOTEPAD, AND SAVE IT AS A .REG FILE, OR BETTER, DOWNLOAD IT HERE)

********* START COPY AFTER THIS LINE *************
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-1!CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00

;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
************ END COPY ABOVE THIS LINE ***************

Most read story in Computer News:
Move an IDE Drive w/Windows 2000 or XP to A New System

Move an IDE Drive w/Windows 2000 or XP to A New System | Login/Create an account | 12 Comments

Comments are owned by the poster. We aren't responsible for their content.

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by DataKraft (-) on Jun 10, 2003 - 05:57 PM
(User info | Send a Message) http://

Or... After moving the drive to its new location, simply run a repair install if your not comfortable with reg editting etc.

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by Admin on Jun 20, 2003 - 12:33 AM
(User info | Send a Message) http://www.MostlyCreativeWorkshop.com

We just wanted to post an update to this article -
For those running Windows XP w/Service Pack 1, the proper locations for the 'atapi.sys,' 'intelide.sys,' and 'pciidex.sys' file are in the SP1.cab. The 'pciide.sys' file remains in the driver.cab file. The updated commands, for those that need them:
"expand sp1.cab -f:atapi.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand sp1.cab -f:intelide.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand driver.cab -f:pciide.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER
"expand sp1.cab -f:pciidex.sys %SystemRoot%\System32\Drivers" (without quotes) hit ENTER

Re: Re: Move an IDE Drive w/Windows 2000 or XP to A New System by nomadh on Aug 15, 2005 - 05:21 PM
- Re: Re: Re: Move an IDE Drive w/Windows 2000 or XP to A New System by nomadh on Aug 16, 2005 - 01:40 PM

Moving Win2000 when the old motherboard is unavailable (Score: 1)
by jamiefaye (jamieNO@SPAMMERSfentonia.com) on Jan 01, 2004 - 01:09 PM
(User info | Send a Message) http://www.fentonia.com/bio/

I came up with a way to apply this change without having to go back to the old system.
Since many people must change-out their motherboards because the old one died, here is how to do it
with just the new motherboard:

Get a second NT machine and put the C: drive of the system you are moving into the D: drive.

Put the driver files in the C:\WinNT\System32\Drivers directory as per the instructions. If you are running the same service pack level on both machines, you can just copy the files directly over.

Run REGEDT32

Click on HKEY_LOCAL_MACHINE

Select Load Hive from the Registry menu.

Browse to D:\WinNT\System32\config\system and open. (That is the registry for the system you are moving)

You will be asked to name the root key for this hive. Make something up like MOVER. You don't want it to overlap any existing key name!

You can then browse around and look at the HKEY_LOCAL_MACHINE\MOVER\SYSTEM\SELECT\Current value. It will indicate which of the two saved control sets is active. Make note of that value.

Make a copy of the registry change file that Jas posted. Open it with an editor and do a global search and replace:

Find:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

Replace all with (assuming Current value is 0x1):

HKEY_LOCAL_MACHINE\MOVER\ControlSet001\

Note: If the Current value is 0x2, then use the following instead:

HKEY_LOCAL_MACHINE\MOVER\ControlSet002\

Double click on the edited registry change file to apply the changes.

Check and make sure that the MOVER registry was changed. I had a minor problem where the CriticalDeviceDatabase key was listed twice. I went and deleted the second instance which only had one key in it.

Select the MOVER key and unload that hive (again from the Registry menu). This disconnects the D: drive registry from the C: drive system's world.

Remove the D: drive, switch the jumpers back, and put it into the C: drive of the target motherboard. Reboot.

You should be good to go.

NOTE: I have only done this once. A smart sysadmin would make sure she had backups of both hard drives before trying this hack out!

Re: Moving Win2000 when the old motherboard is unavailable by Hexchild on Oct 12, 2007 - 05:36 AM

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by Rosencavelier (-) on Feb 08, 2004 - 04:35 AM
(User info | Send a Message)

Just thought I'd let you know that this also worked for transferring Windows 2003 Server from a machine with SCSI HDD to a machine with IDE HDD (don't ask.. strange circumstances).

Thanks a lot for the great info!

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by lafutura (-) on Sep 26, 2005 - 08:29 PM
(User info | Send a Message)

i had to register just so that i could leave a comment - i know this is several years since this was originally posted, but i came across it in google and it solved my problem - tried to put a hd with windows 2000 in a new computer and got this error message. followed your instructions on here and it worked like a dream. thank you a million times over.

Re: Re: Move an IDE Drive w/Windows 2000 or XP to A New System by andytx on Dec 02, 2005 - 11:23 PM
Re: Re: Move an IDE Drive w/Windows 2000 or XP to A New System by andytx on Dec 03, 2005 - 10:24 AM

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by andytx (-) on Dec 03, 2005 - 10:27 AM
(User info | Send a Message)

Hi,

The intruction to copy 4 files to system32\drivers and apply registry does not works on my win2000 Server.

Can anyone show me how to make it woks on Windows 2000 Advanced Server without Repair

BTW the I have not done Repair when move to new conputer, it still blue screen

Thank you

Re: Move an IDE Drive w/Windows 2000 or XP to A New System (Score: 1)
by fwttg (-) on Jan 27, 2008 - 05:12 PM
(User info | Send a Message) http://

Like lafutura, I also had to post a big thank you! This procedure worked moving a W2K hard drive from an older AMD motherboard to a new (2007/2008) Intel motherboard. Searching revealed many uncertain or brutal suggestions. This procedure worked elegantly.

Thank you!