Re: changing PCs

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 04/12/04 

Date: Mon, 12 Apr 2004 22:30:56 +1000

"BAR" <anonymous@discussions.microsoft.com> wrote in message
news:6498CF9C-E9B0-42F0-A564-5A4AB595F5CA@microsoft.com...
> My explanation is that the 'movement' to a new motherboard reflects a
significant change in environment: such as may be found when 'ghosting' one
hard drive [with an activated Windows XP System] to another; with the
ghosted drive then being installed in a new computer and being used without
any problems. Of course the anti-piracy features of Xp are designed to
detect and prevent this happening. Thus the failure to load Windows
results.
>
> In addition to any other solutions proposed to you: remember one other
licencing issue: if you have an OEM version of Windows XP [such as supplied
by a Manufacturer with the purchase of your original system], you are not
licenced to move that Xp system to an upgraded environment [motherboard,
CPU, disk drive]: check your EULA. If you bought a retail version of Xp:
you may.
>
> OK political correctness aside: here's how you may achieve your desired
migration. This proceedure was found on the internet and I have used it
successfully. Some additional comments included by me [warnings and extra
precautions].
>
> If you upgrade your motherboard on your Windows 2000 / XP system or tried
to move the hard drive to another computer, you may receive the following
error message 'STOP: 0x0000007B INACCESSIBLE_BOOT_DEVICE '. This is because
the Windows System does not contain the drivers for the hard drive
controller for the new motherboard.
>
> If you are using a SCSI drive subsystem, usually you can install the
target disk controller in the old system and install the drivers for the
controller. You can then move the controller and the hard drive to the new
system, boot, and remove the unused drivers.
>
> For IDE controllers, it is a little more complicated since the IDE
hardware is found on the motherboard itself. When Windows installs, it
detects the IDE controller and installs only the driver for the detected
hardware. When you upgrade the motherboard or move the hard drive to a new
computer, Windows will not find the correct drivers installed.
>
> If you are interested to find out which drive controller Windows detected
for your original system, look in the file \WINNT\setupapi.log.
>
> WARNING - DO NOT IGNORE THIS STEP:
> Before you begin this procedure, please have a good backup of the current
system or at leat ALL your data files and unique information [such as
username, password etc. for Internet Access, Online Bank etc.]
>
> FOLLOW THESE STEPS:
> 1. Boot the system using the hard drive in the old system. Copy the
following text into a file and call it copy.reg [use copy and paste commands
on the text below]:-
>
> 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-11CE-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
>
>
> You will need to copy the whole thing even if you think you know the
target driver.
>
> 2. Extract the following files from \winnt\system32\i386\driver
cache\i386\driver.cab and put them into the \winnt\system32\drivers
directory: atapi.sys, intelide.sys, pciide.sys, and pciidex.sys. If the
directory contains other cab files for service pack 1 (SP1.CAB) or service
pack 2 (SP2.CAB), get the files from there instead so that you are using the
latest files.
>
> 3. Right click the copy.reg file and select Merge to add it to your
registry. Confirm all prompts.
>
> 4. Move the hard drive into the new system and reboot. You should be able
to boot normally.
>
>
> Good luck
>

What an exhaustive reply! I think it covers just about any potential issue.

I suspect (but cannot prove it) that all of the above steps can be replaced
by this process:

1. While still on the old system, replace the specific Master IDE Controller
driver with the generic Microsoft driver.
2. Move the disk to the new system. I should boot OK, and Plug and Play will
sort out the remaining differences.

I have used this process successfully on several occasions, before I became
aware of the link I quoted in my first reply.

Relevant Pages

  • Re: Can logon my computer
    ... Once you've launched Windows, though, Windows can't ... find the appropriate driver for your boot device. ... The drivers for that controller got trounced and had to ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Windows XP OR MSI motherboard? Which is it?
    ... Windows XP Professional, MSI motherboard with an AMD Athlone64 shit- ... The Video Card drivers won't load. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: STOP 0x00000007B error after installing new RAID controller
    ... drivers for new mass storage device and once you provide new drivers ... Our HP Proliant ML350 had a HP Smart Array 532 controller. ... Windows Server is installed on the RAID1 volume. ...
    (microsoft.public.windows.server.setup)
  • Re: Replacing motherboard
    ... come up in normal mode to install the new drivers. ... First of all, when moving to a new motherboard, ALWAYS use a new hard drive. ... Uninstall all disk utilities such as disk optimizers/defragmenters. ... Boot to Windows, ...
    (microsoft.public.windowsxp.general)
  • Re: installing programs
    ... your copy of WinXP has been customized to fit the OLD motherboard. ... How to perform an in-place upgrade of Windows XP ... It should leave your working drivers and ... "install new hardware" for devices that need new drivers. ...
    (microsoft.public.windowsxp.general)