Upgrading Mobo and CPU

  • Thread starter Thread starter Graeme
  • Start date Start date
Yes, but the result will likely be unhappy. Best to perform a repair
install of Win XP as soon as you turn on the newly rebuilt machine.

NOTE: If you have OEM version of XP rather than a retail version, the
answer is "NO". OEM XP is branded to the original motherboard and can not
be re-registered on a different motherboard.

steve
 
joust in jest said:
NOTE: If you have OEM version of XP rather than a retail version, the
answer is "NO". OEM XP is branded to the original motherboard and can not
be re-registered on a different motherboard.
Click to expand...

Not so. If it's a full OEM version and not a limited one
such as Compaq or IBM provide, you can reinstall it after a
motherboard replacement. I know because I recently did it
myself. There was no problem with activation.

Note to original poster: My experience was that a clean
install was better than a repair install. I tried a repair
install first and it sort of "worked" but the result was
very unsatisfactory so I reformatted the HD and installed
from scratch.

Be sure to back up all your data first and remember that
after a repair/clean installation of WinXP you're going to
have to redo all the upgrades, patches, etc.
 
Thanks guys, sounds like a reformat of the HD is the
safest route. One other question. My XP was an upgrade
version from 98, do you know if I'd have to start out by
installing 98 first then upgrading? (There's a clue to
how old my original system is!)
 
Sure! But it likely will not boot. Do a repair install of Windows XP if it
does not.

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard :-)
 
No, but you do need the Win98 CD for proof. The install will tell you when
to put it into the tray.

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard :-)
 
If you upgrade your motherboard you have every chance of seeing the following error message 'STOP: 0x0000007B INACCESSIBLE_BOOT_DEVICE '. This is because the hard drive does not contain the drivers for the hard drive controller for the new motherboard. [amongst many other things

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 systems, it is a little more complicated since the IDE hardware is usually integrated on the motherboard itself. When Windows installs, it detects the IDE controller and only installs 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.

NOW AS LONG AS IT IS NOT IN VIOLATION OF YOUR LICENCE AGREEMENT, this article will show you how you can install the correct drivers so that you can move the hard drive to a new MOBO. After looking through this, you may think it's all to hard: so you can always move your hard drive and then do a repair install. By by the way Office XP may give you similar headaches, but will only need to be reactivated

If you are interested to find out which drive controller Windows detected, look in the file \WINNT\setupapi.log.

Before you begin this procedure, please have a tested backup of the current system

1. Boot the system using the hard drive in the old system. Copy the following text into a file and call it copy.reg

Windows Registry Editor Version 5.0

[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
Im my experience, you 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.
 
Back
Top