Kenlyn Services Limited

Motheboard changing

CHANGING MOTHERBOARDS; KEEPING WINDOWS AND APPLICATIONS INTACT

Microsoft support articles are effectively (almost completely) silent on the subject of adapting an installed operating system to a different motherboard.  Because there is no official guidance from Microsoft, Windows users have developed a variety of methods on their own.  With no standard procedure, users variously modify basic methods with alternate procedures.  Following are the various methods reported to be used successfully by Windows users.  All known alternate procedures for each basic method are included.

For the benefit of Windows users, Microsoft should publish recommended step-by-step procedures for each operating system. Methods need to be unambiguous and standardized. There are currently too many variants. It’s confusing.

If Microsoft has no recommended procedure because it finds that Windows adapts poorly to a motherboard swap (and they can’t therefore recommend a procedure other than a fresh Windows reinstall), then the Windows operating systems needs to be improved. Changing a motherboard and moving a hard drive to new hardware are not unusual occurrences. These common events should not require that Windows and all applications be reinstalled.

Due to lack of information from Microsoft, the majority of information contained herein comes from unofficial sources. Accordingly, use it at your own risk. Raw user reports forming the original basis for this guide can be found at:

http://www.amdmb.com/vb/showthread.php?s=c9d0bef8f0a923b24e2de3376ebe4f03&threadid=83657

This document is an ongoing public project continually improved by user feedback. Corrective comments and other helpful input from Windows geniuses is requested.

This guide was last updated on: January 6, 2002.

NOTABLE USER COMMENTS:

When changing motherboards, wiping your hard drive and starting over is totally unnecessary. Do this only if you enjoy re-installing Windows and all of your other software. Doing a re-format and then a full re-install is a pain, but the real problem is re-installing all those applications; finding all the disks and downloads for them, then finding all the updates (the updates rarely have file names which seem obvious months or years later), then restoring all those hundreds of custom settings and tweaks accumulated and thoughtfully applied over months or years. Aaaggghhh!!!

It's amazing how many people will advocate and go through the process

of f/disking and reformatting their hard drive when all that is needed to get their machine in top running condition again is to clean the left-over garbage out of their registry. There is a great little program in Windows (all flavors) called RegEdit. You can go in there and physically delete all the references to a rogue program in just a few minutes. (Also mentioned: “RegRepair 2000” (easydesksoftware.com); One user states “This program is totally automatic. It cleans up the registry like a fresh install.”) [Note: There are no doubt other registry utility programs that do this as well.]

If the motherboard swap involves the same model motherboard, no special procedures are required. Just shutdown, replace the board, boot into BIOS, adjust BIOS settings, and reboot into Windows; (you may need to rebind the NIC). If the hardware change involves different motherboards, then the following procedures can be used to make the change without disturbing the existing installed operating system and applications.

PRE-ACTION PROCEDURES:

Before undertaking any action, do this:

1) Verify that new hardware is compatible with the operating system, and (where applicable) approved for the CPU (e.g. motherboard, power supply, heatsink and fan, RAM, etc.).

2) Have the Windows setup CD, the latest motherboard BIOS, and all needed driver files on hand.

3) Copy all the Windows cab files (contents of the Windows setup folder) from the install directory on the Windows CD, into a directory on your hard drive so that you don’t need your CD-ROM drive active on the first boot. (Windows still has the habit of deciding it needs some of the motherboard drivers before it has sorted out the IDE drivers for the CD. You may not have CD drive access until you reboot a few times (if the IDE controllers have to be reinstalled)).

a) For Windows 2000, (recommended) copy the \i386 directory structure from the Win2000 distribution CD to a directory under C:\Winnt (e.g. C:\Winnt\Cabs, or C:\Winnt\Cabs2000).

Note: To reconfigure where your Win2K system looks for the files, go to the following Registry key:

[HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows \CurrentVersion \Setup]

You want to change the following values: (For the second one, point to the folder just before the \i386 folder. So if you copy it to C:\i386, point it to C:\).

"Installation Sources"

"SourcePath"="C:"

b) For Windows 95/98/98SE/Me, (recommended) copy all Windows cab files from the distribution CD to a directory under C:\Windows (e.g. C:\Windows\options\Cabs, or C:\Windows\98se).

Note: To reconfigure where your Win95/98/98SE/Me system looks for the files, if the files are copied to the C:\windows\options\cabs folder, make the change in the Registry to set the SourcePath by going to the following location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup. In the right pane look for "SourcePath" and set the path to: C:\windows\options\cabs

4) Copy all motherboard and other device driver and BIOS updates into a directory on the hard drive, and also onto floppy disks. Include all needed drivers that Windows does not have. Be sure to include drivers for the chipset and the latest BIOS revision for the new motherboard.

a) For Windows 2000, create directories for installed hardware under C:\Winnt and preload with the drivers you'll need, (e.g. C:\Winnt\Audio, C:\Winnt\Display, etc.).

b) For Windows 95/98/98SE/Me, create directories for installed hardware under C:\Windows and preload with the drivers you'll need, (e.g. C:\Windows\Audio, C:\Windows\Display, etc.).

Note: Make sure drivers and Windows cab files are copied to the hard drive (and floppies) because when you delete the ENUM key (procedure described below) you are erasing Windows’ hardware database for your computer and you will not be able to access your CD-ROM drive until it is redetected later (after Windows has installed all the basic IDE drivers and system devices).

5) Before changing any hardware, boot up the existing (old) system. In Device Manager, make a list of items in "System Devices".

6) If running W2K on an NTFS drive, it’s recommended to do a second minimal W2K install to a second-partition or second drive just in case something goes wrong with the main install; the minimal install gives you access to the original install in a way you are not able to get from the Recovery Console.

7) Do a Full Backup of all hard drives.

8) Backup the System State (Registry).

9) To floppy disk, make a copy of any individual folders, files, or registry keys that are to be deleted as part of the procedure. This makes is easy to restore any single item.

10) Open Device Manager; make a list of all items in System Devices.

11) Create an Emergency Repair Disk.

12) Create system boot floppy disks. The boot disk(s) must enable access to the CD-ROM drive. (Test it.)

13) Using DriveImage, Ghost, etc., create an image of the hard drive.

WINDOWS XP PROCEDURES:

(See the Win2000 section below for more detail on any solution; methods that work for Win2000 are reported to also work for XP). Users report the following procedures work successfully under Windows XP:

Solution 1; Simply swap motherboards and reboot; XP detects changes:

Do nothing. Just change the motherboard, hardware, and reboot. WinXP redetects all changes automatically, and installs the correct drivers. Especially effective if old and new motherboards use the same chipset.

Solution 2; In-Place Upgrade to force hardware re-detection:

(See the Win2000 section below for more procedural detail).

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Change motherboards or move hard drive to new system.

3) Boot the system from the WinXP CD. Have your CDKEY ready.

4) Select the “Install” option. (Don't select repair! The first repair option only verifies XP files against the XP CD versions and makes no system setting changes).

5) Setup will find the XP install that is already there and ask if you wish to repair it. Say yes.

6) Setup will run the upgrade code that will re-enumerate the hardware and set itself to boot from the new controller.

7) Install newer drivers as needed.

Note: Microsoft Knowledge Base Article:

You May Lose Data or Program Settings After Reinstalling, Repairing, or Upgrading Windows XP (Q312369)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q312369

Solution 3; File and Settings Transfer Wizard:

If you need to keep your existing OS settings etc., you can use the File and Settings Transfer Wizard and save them to a CD-R or a local hard drive on a network. Then after you have installed XP, transfer them back.

Solution 4; Microsoft Resources:

Moving Disks: http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkb_cnc_ykyz.asp

WINDOWS 2000 PROCEDURES:

Users report the following procedures work successfully under Windows 2000:

Solution 1; Microsoft Knowledge Base Recommendation:

Microsoft Knowledge Base article - Q249694 “How to Move a Windows Installation to Different Hardware And Troubleshooting Windows 2000 Hardware Abstraction Layer Issues.”

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q249694

Windows Backup (Ntbackup.exe) has the ability to merge differences in hardware configuration information between computers and maintain critical registry entries unique to the new computer to which you are restoring information. This capability makes it possible to perform a full backup of your source computer and restore it on top of a fresh Windows installation on your destination computer to migrate to new hardware.

(This procedure is a bit complex, and appears to be intended for moving an existing OS installation from one PC to another using two networked PCs (each having different hardware). It doesn’t appear to be for a single-PC hardware upgrade operation.)

Solution 2; Simply swap motherboards and reboot; W2K detects changes:

Do nothing. Just change the motherboard, hardware, and reboot. Win2K redetects all changes automatically, and installs the correct drivers. Reboot in Safe Mode to delete old hardware from device manager. Effective only if old and new motherboards use the same chipset, I/O controllers, and there’s little variation in hardware.

Solution 3; In-place Upgrade to force fresh hardware redetection:

What an In-Place Upgrade Changes:

· It does NOT change the installed components and programs.

· It does NOT change any passwords.

· It does NOT change third-party registry entries.

· It rolls back any hotfixes, service packs, and Microsoft Internet Explorer upgrades to their base versions.

· It refreshes the registry and restores default registry values.

· It reapplies default permissions.

· It reregisters Component Object Model (COM) components and Windows File Protection (WFP) files.

· It reenumerates Plug and Play devices, including the hardware abstraction layer (HAL).

· It reenumerates and changes drive letters, based on the current drives and partitions that are seen during the in-place upgrade and on the rules that are documented in the following article in the Microsoft Knowledge Base:

Q234048 How Windows 2000 Assigns, Reserves, and Stores Drive Letters

Windows 2000 is not plug and play when it comes to motherboards. When swapping motherboards with different HALs or chipsets in a W2K system you must reinstall W2K to force windows to redetect the chipset. The reinstall is done as an upgrade. The advantage of this procedure is that you get the setup engine doing a close inspection of the new setup, and loading drivers as needed. No Emergency Repair Disk is required.

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Change motherboards or move hard drive to new system. (See Alternate 3A below for alternate procedure starting here).

3) Power up, and enter BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

Note: If your BIOS isn't current, flash upgrade your bios, reboot, recheck your bios settings, and shut down. It’s preferable to flash from the hard drive; floppy disks and floppy drives are more likely to fail or encounter physical errors during a flash sequence. If you must use a floppy, be absolutely certain both the disk and drive are good before you start.

4) Boot the new system from the Win2000 CD (from the Windows 2000 installation CD-ROM, run Winnt32.exe from the \I386 directory); (great if you have a slipstreamed Windows 2000 installation CD w/ SP2; see HERE for details), or 4 boot floppies. (If the hard drive is accessible, you can run Winnt32.exe on the hard drive, or Setup.exe on the CD from Explorer). Have your CDKEY ready.

5) If Win2K doesn’t have I/O disk controller drivers for your motherboard, to avoid Inaccessible_Boot_Device error screen (See Inaccessible Boot Device solution section at the end of this document), insert the floppy disk containing driver (TXTSETUP.OEM), and add it using the F6 key when prompted. (The F6 prompt is shortly after the screen changes from black to blue (during white text on blue screen)). Next, press ‘S’ to specify an additional driver. Windows then prompts for the disk containing the driver file TXTSETUP.OEM. After necessary drivers are loaded, press Enter to continue with Setup.

Note: You do not need to install the ATA-100 driver during the WIN2K install process on a non-RAID IDE motherboard; WIN2K will simply treat it as an ATA-66 drive. Once Setup is complete, install SP2, and WIN2K will see the drive as ATA-100. If the disk is on a SCSI or RAID controller, you must use the 3rd party mass-storage device <F6> option, or WIN2K won’t see the disk.

6) If third-party drivers are not needed at this time or will be installed later, skip F6, then, at the first screen asking you if you want to perform a repair or new install, select Install Windows 2000 -> Upgrade to Windows 2000. (Don't select repair or recovery on the first screen! The first repair option only verifies Win2K files against the Win2K CD versions and makes no system setting changes).

7) Setup will find the existing Win2K installation (usually C:\winnt) and ask if you wish to install over it or repair it. At this second prompt, select Repair.

Note: If the Setup program does not detect a previous installation but just continues to the partitioning screen, there is a problem. An in-place upgrade may not be possible

8) Setup will run the upgrade code that will re-enumerate the hardware and set itself to boot from the new controller. The upgrade will retain all settings but will update drivers for the current motherboard and hardware. (You can reinstall windows over windows with no problems. It basically just skims over your existing installation and fixes bad files and fills in the blanks if something is missing. Everything will be the same after your reinstall.)

9) All programs, settings, and configurations will still exist after this upgrade, however, if you don't have a slipstreamed Windows 2000 installation CD w/ SP2, (see HERE for details), all drivers are reset to Windows basic, and Microsoft updates will need to be reapplied. Run Microsoft Windows Upgrade (on Windows Start menu) to reapply updates as needed. Reports state that IE will be back to IE5.0 and will need to be updated. Any Service Packs will need to be reinstalled. All security updates that have been installed need to be reinstalled. It is best to install the security updates based on the time order.

10) Install optimized chipset drivers, ATA100 drivers, and other branded drivers as needed (those not previously installed using F6 in #4 above).

Solution 3A Alternate procedure for In-place Upgrade:

Alternate Solution 3A: Proceed per Solution 3 steps, except that no hardware is changed until the first reboot power-down during the upgrade install.

Before changing any hardware in the old system, insert the Win2000 CD and bootup. Start the Windows 2000 Setup, and proceed with the Install-Upgrade as described (“Upgrade current version to Windows 2000”). Once the system has copied files and first asks you to reboot, say OK. At the POST on this first reboot, turn off the power. Remove old hardware. Install the new motherboard and other new hardware. Boot to enter BIOS; adjust settings. Shutdown. With the Win2K CD still in place, power back on; Win2K will continue the installation with a complete hardware rescan, detecting new hardware and installing drivers. Proceed with steps 9 and 10 as described above.

Solution 3B Alternate procedure for In-place Upgrade:

Alternate Solution 3B: Proceed per Solution 3 steps, except that no hardware is changed until the first reboot power-down during the upgrade install, AND the Upgrade is commenced from within Win2000 running on the hard drive, not by booting up to the Win2000 Installation CD.

Before changing any hardware in the old system, while running Win2000 on the hard drive, insert the Win2000 Setup CD and start Win2000 setup from within Win2000 (From Explorer or Start-Run, run Setup.exe on the CD); (important to start from within Windows 2000, otherwise you don't get the option to upgrade). Proceed with Upgrade as described; choose to 'UPGRADE CURRENT VERSION TO WINDOWS 2000'. Once the system has copied files and asks you to reboot, say OK. At the POST on this first reboot, turn off the power. Remove old hardware. Install the new motherboard and new hardware. Boot to enter BIOS; adjust BIOS settings. Shutdown. Power back on; Win2K will continue the upgrade installation with a complete hardware rescan, detecting new hardware and installing drivers. Proceed with steps 9 and 10 as described above.

Note: Microsoft Knowledge Base Article:

No Upgrade Option When Setup Is Started from Disks or CD-ROM (Q181049)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q181049

SYMPTOMS

When you boot your computer from the Windows 2000 floppy disks or CD-ROM to start the Windows 2000 Setup program, you are not given an option to upgrade your operating system. When you start the Setup program in this manner, you can perform only a new installation of Windows 2000.

CAUSE

This behavior occurs because the Windows 2000 Setup program does not support upgrading when you boot your computer from the Windows 2000 floppy disks or CD-ROM.

NOTE : It is possible to boot from Windows 2000 floppy disks or CD-ROM and do a repair installation if Windows 2000 is already installed on the machine. For more information, please see the following article:

Q292175 How to Perform an In-Place Upgrade of Windows 2000

RESOLUTION

To work around this behavior, start the Windows 2000 Setup program from within the operating system you want to upgrade. To do so, run the Winnt32.exe program from the Windows 2000 CD-ROM.

Solution 3C Alternate procedure for In-place Upgrade:

Alternate Solution 3C: Proceed per Solution 3 steps, except that all devices in device manager are deleted prior to last shutdown before hardware change.

Boot into safe mode; remove old hardware. (“You MUST boot into safe mode and remove the old hardware - or risk odd occurrences on your machine”).

Solution 4; Delete all devices in Device Manager; Reboot to redetect:

Since the only thing at issue here is the operating system drivers (mainly the PCI bus, disk controllers, USB, etc...), the easiest thing to do is to just uninstall all of your devices from device manager prior to the last time you shut down your box before the new installation. Delete devices. Shut down. Change hardware. Boot into BIOS to make adjustments. Reboot. When Windows restarts, it will not have any devices installed, so it will detect the new ones and install the drivers.

Solution 5; Delete ENUM key in the registry; Reboot to redetect:

(Caution: Removing the ENUM key is NOT recommended for a NT-based OS such as 2000 or XP. In contrast to consistent good results in Win98, in Win2K, reports state that deleting the enum key is not a good idea, especially if Windows 2000 has been installed in ACPI mode. There’s a chance of killing the installation if you delete the enum key in Win2K. Also, the machine will not boot to detect new drivers unless the mass storage controller driver is installed. If the controller driver is deleted, you will likely get the INACCESSIBLE_ BOOT_DEVICE blue screen on next boot. Be sure to create a backup of the registry (or individual keys to be deleted) so the registry can be restored if deleting Enum does not work).

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Backup the following registry key:

Key: HKEY_LOCAL_MACHINE/Enum

3) Uninstall or otherwise disable (you can use msconfig) all device specific TSR's and other non-essential programs that load at startup. This includes AntiVirus Software and firewalls. Remember to reenable later.

4) Boot into safe mode.

5) Start RegEdit. In the registry, go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002 and delete the ENUM key. (This deletes the current hardware information, causing the hardware registry data to be rebuilt.)

6) Shut down and make motherboard and hardware changes.

7) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

Note: If your BIOS isn't current, flash your bios, reboot, recheck your bios settings, and shut down. It’s preferable to flash from the hard drive; floppy disks and floppy drives are more likely to fail or encounter physical errors during a flash sequence. If you must use a floppy, be absolutely certain both the disk and drive are good before you start.

8) Reboot. Press <F8> on Windows startup; select the "Last known configuration” option. This will cause Win2000 to use ControlSet002 without any of the hardware detected. Hardware is detected in 1 step and 1 reboot.

9) Shut down and boot into Safe Mode. Check Device Manager for errors and duplicate entries. Correct as needed.

10) Shut down. Reboot normally.

Solution 6: Boot on basic Microsoft drivers, then change drivers:

(The objective is to get a bootable system by installing basic Microsoft default drivers which are compatible with most hardware. After the system is running, new hardware can be detected, and specific optimized drivers can then be loaded).

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Boot the PC system using the existing (previous) motherboard. **If you've installed the UltraATA Driver (if so, Device Manager->IDE Controllers->Primary Channel will be lacking its usual "Advanced Settings" tab) then uninstall said driver from Control Panel and reboot before continuing **

3) From the Device Manager, open up the "IDE ATA/ATAPI Controllers" section. (On a typical system there will be three entries under this - the controller itself, and then the primary/secondary IDE channels.)

4) Double-click on the entry for the controller, and change the driver to the generic default Microsoft "Standard Dual-Channel PCI IDE Controller". Set DMA to "PIO Only". (Double click on the IDE controller icon in the Device Manager. Click on the "Driver" tab. Click on "Update Driver". Click next. Click "display list of the known drivers for this device so that I choose a specific driver" button. Click next. There it is.) This is to IDE controllers what the Standard VGA driver is to video cards - i.e., it'll work on just about anything, but is rather slow and basic. This avoids the INACCESSIBLE_BOOT_DEVICE BSOD (See IBD solution section at the end of this document) you might otherwise get due to differences in old and new controllers.

5) If you use a USB keyboard or mouse, follow the procedure for the IDE controllers for both USB roots if you have two. The driver name is "Standard Universal PCI to USB Host Controller"

6) Under "System Devices", find the Northbridge; that's the CPU to AGP or CPU to PCI controller. The driver you need is "PCI standard PCI-to-PCI bridge". Anything else under system devices that's branded should be either set to standard or uninstalled.

7) Video card and display drivers may be set to default driver.

8) Disable all network and sound adapters.

9) Shut down the system, and replace the motherboard as required.

8) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed for new hardware. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

9) Reboot into Windows. As the new IDE controller is compatible with the "Standard Dual-Channel PCI IDE Controller" driver, then the system should, all being well, boot into Windows 2000.

10) At this point you should install the optimized IDE/ATAPI drivers (i.e. VIA 4in1 drivers), and other drivers as needed.

Solution 7; Create a new Hardware Profile; Reboot to redetect:

(This is a non-destructive alternative to deleting the enum registry key or deleting devices in device manager).

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Open Control Panel / System / Hardware / Hardware Profiles. If no additional hardware profiles were created since OS installation, there will be one profile named “Profile 1”. This is the current hardware profile.

Note: If you cannot boot the old system and must boot on the new system, you MUST boot into Safe Mode on your first boot with the new board to accomplish the following steps 3 and 4.

3) Identify the current profile and rename it to something representing the existing hardware configuration; i.e. “OldMobo Orig”, or “OldMobo 1”. The “Orig” or “1” designation distinguishes this file from the copy to be created next, and the profile that Windows creates later.

4) Copy the existing current profile to create a duplicate profile; i.e. “OldMobo Copy” or “OldMobo 2”. At this point you should have two identical profiles, 'Orig' and 'Copy' or ‘1’ and ‘2’. (The duplicate is created to trigger a system prompt on reboot which is needed to get the required hardware redetection. The only time Win2000 prompts you for the name of a hardware profile is when two profiles are so similar that it cannot differentiate between them).

5) Don’t make any hardware or driver changes until you reboot; you are running the ‘Orig’ or ‘1’ profile at this time and you don’t want new changes written to that profile.

6) Shut down the PC, remove power, and do the motherboard swap.

7) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed for new hardware. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

8) Boot into Windows. If the “Inaccessible_Boot_Device” BSOD error is encountered here, then one of the procedures described in the Inaccessible Boot Device section of this document must be applied to make the disk bootable before proceeding. (Typically, change the hard disk controller to generic default Microsoft "Standard Dual-Channel PCI IDE Controller").

9) If the boot into Windows is successful, you should be asked which profile you wish to use. Do not select either of the “Orig” /”1” or “Copy” /”2” profiles, instead, select 'None of the Above'.

10) With “None of the Above” selected, having no profile to load, Windows will redetect all the hardware. If Windows needs the Win CD or newer drivers, simply point the install at the directory where you copied Windows or drivers. If using a VIA chipset, install VIA 4in1 drivers at this time. (You may have to re-boot the machine once or twice, making sure that you choose "NONE OF THE ABOVE" each time until Windows tells you that it has created a new hardware profile, and states the new configuration name).

Note: One report states that through this process of selecting “None of the Above”, Windows is actually updating the original (“orig” or “1”) profile, not creating a third or new profile. If this is correct, to boot with the new settings, then, select the original profile. Also, do not delete the “orig” or “1” profile thinking it is for the old motherboard.

11) Note the name given to the newly created profile. Use this profile when booting on the new hardware configuration.

12) Boot into Safe Mode. Check Device Manager for errors and duplicate entries. Correct as needed.

13) Install any optimized drivers missed during redetection.

The great thing about this procedure is that if everything goes wrong, you can put the old board back, select the 'orig' /’1’ profile, and be back with a booting system.

Optional:

Once you have the new system properly installed, if you know for sure you won’t ever boot on the old system again:

1) Delete the 'old' profiles (orig, and copy, or 1 and 2). Deleting unneeded profiles cleans up the registry.

2) Boot into Safe Mode and remove left-overs from the old board in device Manager.

Solution 8; Microsoft’s System Preparation Tool (SysPrep):

Use the SysPrep tool to deploy machines with a standard image.

Research SysPrep; Search Microsoft Knowledge Base per OS: http://support.microsoft.com/default.aspx?scid=fh;rid;kbinfo

Download Sysprep from: http://www.microsoft.com/windows2000/downloads/tools/sysprep/default.asp

Tool Summary: SysPrep removes all devices and shuts-down the PC. This rolls the hardware database back to a factory state, and as long as the new motherboard and old motherboard use the same HAL (ACPI or Standard PC, single CPU) the system will correctly redetect all hardware devices in the PC. On next boot it will take you through re-detection of devices and re-naming the PC. Existing software applications do not have to be reinstalled.

Sysprep is used to pre-populate the intended upgrade system with the necessary mass storage controller prior to installing the new motherboard. The correct directory structure for the Sysprep files and a modified sysprep.ini file is important.

A couple of caveats, back up your profile data (just in case) and if you were using a Standard PC HAL you may need to execute sysprep with the "-pnp" parameter for it to correctly identify the hardware. On an ACPI system with no legacy hardware (ie. no ISA cards) this is not necessary.

Also Note: Using SYSPREP and imaging software (DriveImage or Ghost) to move a Windows 2000 installation to new hardware (even to motherboards having a different hard disk controller):

See: http://www.rtpnet.org/tech/tips/ghost.txt

Also Note: Sysprep will remove much user and network information from the machine (unfortunately, doesn't seem to do this completely when you need it to), and also the product ID, so that you have to re-enter all of this stuff. It will not help with problems caused by changes in the hardware.

See: http://www.microsoft.com/technet/win2000/win2ksrv/sysprep.asp

WINDOWS NT PROCEDURES:

(No procedures specific to NT found. See Win2000 section.)

Note: Windows NT requires a mini-port driver to communicate with the boot controller. If the device driver is corrupt or incompatible with your controller, you can replace it by copying a new drive to the %systemroot%\system32\drivers folder or through the Emergency Repair process. On computers running on a SCSI controller or ATAPI enabled systems, SCSIPORT.SYS and DISK.SYS (Windows NT 4.0 only) device drivers are also required to successfully boot.

If you attempt a "WINNT /B" installation, you may receive a STOP 0x7B before mass storage detection takes place. To work around this, when the computer reboots after the initial file copy, press F6 as soon as "Setup is inspecting your computers hardware configuration" is displayed. This will allow you to add a mass storage device at the very beginning of text mode setup.

ARTICLE-ID: Q125933 TITLE : STOP 0x0000007B: Inaccessible Boot Device After Removing CD-ROM

ARTICLE-ID: Q164471 TITLE : Replacing System Files Using a Modified Emergency Repair Disk

WINDOWS 98/98SE/Me PROCEDURES:

Most of the same procedures listed in the Win2000 section can be used for Windows 98/98SE/Me. Users report the following procedures work successfully under Windows 98/98SE/Me:

Solution 1; Simply swap motherboards and reboot; Win detects changes:

Do nothing. Just change the motherboard, hardware, and reboot. Windows redetects all changes automatically, and installs the correct drivers. Reboot in Safe Mode to delete old hardware from device manager. Effective only if old and new motherboards use the same chipset, I/O controllers, and there’s little variation in hardware.

User Reports:

“It has been my experience that the deletion of files is unneeded with the improved Plug and Play function of Win98 thru WinMe. You may simply install the Harddrive into the new case and start-up. The system will require several restarts as it sequentially installs first system resources, the PCI, then PCI peripherals and ISA, and finally ISA peripherals. The system will show a mix of drivers on the first couple of cycles but should finish with all appropriate drivers. Although the Windows install disks will have most common chipset drivers, you may need to supply uncommon chipset drivers."

And:

"I switched motherboards from a Celeron system to an AMD Athlon system and the windows did everything itself. I switched the hard drive from one system to the other and windows did the drivers changes automatically. Just 2 to 3 reboots or so to find every change in the mainboard and that was it. Maybe if you have problems, install the CD with the mainboard drivers from the windows system, and that's it!!! Very easy!!!"

And:

“Relying on automatic device detection on the first boot up is a crap shoot. Sometimes it works (quite well, in fact.) Other times it can leave a system dead in the water.”

Solution 2; Delete ENUM key in the registry; Reboot to redetect:

Reports state mixed results when deleting the Enum key (mostly “worked flawlessly”, but a few “unable to boot” (unknown if related to procedure or if user just did it wrong)). Deleting the ENUM key is a procedure middle-ground between a straight motherboard swap and an upgrade reinstall using the Windows Setup CD.

Be sure to create a backup of the registry (or individual keys to be deleted) so the registry can be restored if deleting Enum does not work; (start>run enter scanregw). If you find you’ve made a mistake deleting ENUM you can get it back just like it was by restoring a previous booting copy of the registry. Use the command "scanreg /restore" and use the last previous registry that booted the machine. Enum will be back. If anything goes wrong with modifying the registry, Windows also maintains backups in C:\Windows\SYSBCKUP in the files rbxxx.cab. If disaster strikes, you can always boot into DOS with a floppy and then restore your registry manually by extracting the files from one of these CAB files (using the Extract command located in C:\Windows\Command).

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Backup any folders, files, and keys to be deleted, and specifically, the following:

Folder: C:\Windows\inf\other

Files: Autoexec.bat; Config.sys; Win.ini

Key: HKEY_LOCAL_MACHINE/ENUM

3) Optional; (One tech reports) For the extra cautious: Delete all entries in the directory C:\Windows\inf\other

4) Disable (you can use msconfig) all device specific TSR's and other non-essential programs that load at startup. This includes AntiVirus Software and firewalls. Remember to reenable later.

5) Boot into Safe Mode.

6) Optional; (One tech reports) For the extra cautious: Rename autoexec.bat and config.sys

7) Optional; (One tech reports) For the extra cautious: Clear any entries in the load and run lines of win.ini

8) Optional; (One tech reports) For the extra cautious: Remove all devices from device manager. When done you'll be left with two entries - the child devices from the hard drive controller (assuming an IDE based system).

9) Start RegEdit (Start-Run-Regedit), and delete the following registry folder (and all subfolders under it): HKEY LOCAL MACHINE/Enum (Expand the HKEY_LOCAL_MACHINE branch in the left pane. Right click on the Enum key under HKEY_LOCAL_MACHINE and pick delete). [This may cause the system to stop responding, so do it the last thing before shutdown for hardware change.]

Note: Deleting the ENUM key removes all hardware that windows has detected since it was installed, and when you reboot, it's as if windows has never had any hardware installed. Deleting ENUM is like deleting all Win9x driver information from Device Manager, but in one action; (only “Computer” remains in Device Manager). With the current hardware information deleted, Windows is forced to rebuild the hardware registry data; (the ENUM key is recreated). This does not rebuild the VMM32 file, however.

Note: (Always backup keys and files before deleting).

For WinMe, one report stated that the following key is also deleted: HKEY DYN DATA\Config Manager\Enum

For WinMe, one report stated that the following file is also deleted: HWINFO.DAT

10) Shut down and make motherboard and hardware changes.

11) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed. Note ACPI. Save your settings, exit, and shutdown.

12) Reboot into Windows. Hardware is not automatically redetected on reboot. When Windows starts, you'll be in 640x480 16 color, and presented with an error message about the display adapter. Cancel and close that and go to "Add New Hardware" and let Windows go to work and redetect everything. Windows detects all the new hardware and installs drivers. Reboot when prompted (this will happen several times) until you no longer get the prompts. If it prompts you to insert the Windows CD, point it to the cab files. If it asks for a manufacturer's driver disk, point it to the appropriate folder. Don't worry if a driver install fails, you can always go back later and reinstall that particular device from scratch. If you have a VIA based board, now is the time to install the "4 in 1" drivers.

Alternate: Many users recommend rebooting every time Windows prompts, but others (experienced) prefer to wait until all devices have been detected, and then before rebooting, open device manager, and delete the NON-SPLATTED entries (that's right, the non-splatted entries) for all duplicates. Common duplicates will be Display Adapters, Keyboards, and DMA controllers. Also delete all Sound Card entries.

13) Boot into Safe Mode. Check Device Manager for errors and duplicate entries. Correct as needed. (You MUST boot into safe mode and remove the old hardware - or risk odd occurrences on your machine.)

Note: You will probably have some yellow flags. You will probably have 2 items that are flagged with unflagged duplicates - the keyboard and the DMA controller. Remove the entry that is NOT flagged. If you have 2 display adapters, one will be flagged - usually the "standard VGA" will not be flagged and the actual adapter will be flagged. Remove the unflagged standard VGA. By now you should have CD support, so any other devices that are flagged can be reinstalled using the appropriate CD if necessary.

14) Install optimized drivers as needed. Uninstall any unused drivers.

15) Shut down. Reboot normally.

Solution 2A; Alternate Delete ENUM key; Reboot using Setup CD:

Alternate Solution 2A: Proceed per Solution 2 steps, except that the system is rebooted using the Windows Setup disk.

Replace step 14 with:

14) Boot the system with the Windows Startup Disk and run the Windows 95/98 Setup (or boot with the system with the Safe Mode Command Prompt Only option and run Setup from the folder you copied the setup file to). Windows redetects hardware. This will replace the hardware tree and avoid duplications and conflicts, but not destroy your software settings. The advantage is that you get the setup engine doing a close inspection of the (new) setup, and loading drivers as needed.

14A) Reboot and run Windows Update. Reapply any needed Windows updates.

14B) Install optimized hardware drivers.

Solution 2B; Alternate Delete ENUM key; Reboot using Setup CD:

Alternate Solution 2B: Proceed per Solution 2 steps, except that the system is booted using the Windows Setup disk, AND additional files are renamed, and additional keys are deleted.

Between steps 10 and 11: (One tech reports); From the file manager, rename the following folders:

\Windows\Inf to \InfOLD

\Windows\System\IOSudSys to \IOSudSysOLD

\Windows\System\VMM32 to \VMM32OLD

As part of step 11: (One tech reports); Delete the following registry keys prior to deleting the ENUM key:

HKLM\System\CurrentControlSet\Services\VxD (Usually empty)

HKLM\System\CurrentControlSet\Services\Class (Usually empty)

Replace step 14 with:

14A) Reboot and run Windows Update. Reapply any needed Windows updates.

14B) Install optimized hardware drivers.

Solution 2C; Alternate Delete ENUM key; If likely to move back and forth between old and new hardware:

Alternate Solution 2C: Proceed per Solution 2 steps, except that the following steps are taken prior to deletion of the ENUM key.

Before you delete the ENUM key, while the hard drive is still running on the old motherboard, do this just in case you want to reinstall the hard drive back on to the old motherboard (if you are moving the drive permanently, this is not needed, just delete the enum key and have at it):

1) This procedure assumes that your hard drive is still in your OLD computer and operable ..

2) Click on My Computer; Select VIEW > FOLDER OPTION >VIEW; Enable "SHOW ALL FILES". Close this Windows when done.

3) Open folder WINDOWS\SYSBCKUP.

4) On the Explorer bar click VIEW; Select VIEW DETAILS; click on TYPE - this will arrange all files found there by the Type of the file.

5) Look for RB***.CAB; when found, use SHIFT and select the first = RB000.CAB - and the last = RB005.CAB; Right click on it and DELETE - still holding the shift Button. This will DELETE the files out of the System.

6) Leave the My Computer Window open and go to START > RUN and type
SCANREGW; Press enter if asked to BACKUP the REGISTRY; Select Y or yes or OK.

7) Go back to the My Computer window which still is open; there somewhere of your CHOICE, create a NEW FOLDER and Name it OLDMOBO.

8) Go to the SYSBACKUP folder and find RB000.CAB; right click this file and select COPY; Go over to your newly created OLDMOBO and paste the file in there. RENAME the file to OLDMOBO.CAB

At this point, you are finished and ready to delete ENUM and move the hard drive to the NEW board as a PRIMARY MASTER. If you want to move the drive as a PRIMARY SLAVE or SECONDARY MASTER or SLAVE then all this doesn't need to be done, including deletion of ENUM!

Shut down the computer, then switch the drive to the other computer or switch the motherboard.

Switching from New Motherboard back to Old Motherboard:

Recognize that when switching between different motherboards, that the hardware on the boards is different. Accordingly, the registry of Windows running on different boards isn’t the same. After you have successfully switched motherboards using the above procedure, whenever you want to move the hard drive from the NEW board back to the OLD board, you must RENAME the RB000.CAB created on the NEW BOARD to NEWMOBO.CAB, and copy it to the folder OLDMOBO.

Assume you switched the drive or the board and RIGHT NOW you are using the NEW BOARD but for what ever reason you would like to get the DIRVE BACK to work on the OLD board - so that you don't have to go through all the procedure again, all you need to do is:

1) Install the hard drive into the OLD computer.

2) Boot to MS-DOS prompt. (Do not boot into Windows yet).

3) RENAME the RB000.CAB created on the NEW BOARD to NEWMOBO.CAB, and copy it to the folder OLDMOBO.

4) Restore the registry by copying the file OLDMOBO.CAB into C:\WINDOWS\SYSBCKUP\OLDMOBO.CAB

5) Boot into BIOS. Make any BIOS adjustments needed. Save settings.

6) Boot into Windows.

This will allow you to switch motherboards or hard drives within a few minutes without going through all the installation procedures repeatedly.

Solution 3; Delete all devices in Device Manager; Reboot to redetect:

Since the only thing at issue in a motherboard change is the operating system drivers (mainly the PCI bus, disk controllers, USB, etc...), the easiest thing to do is to just uninstall all of your devices from device manager prior to the last time you shut down your box before the new installation. Deleting the devices in Device Manager usually works, but there are exceptions. If you are changing chipsets or going from non-ACPI to ACPI (or back), one tech reports “just delete HKLM\Enum and be done with it”. Others report “This has been a tried and true method over the years and never failed to work”.

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Before changing any hardware, boot into Safe Mode. (Right after you boot and hear the beep, hold down the 'F8' on your keyboard. You should get a menu with options. Select 'Safe Mode').

3) Ignore the message about 'Windows is running in Safe Mode.' Right-click on 'My Computer,' click 'Properties,' then click 'Device Manager' tab.

4) Starting with 'PnP BIOS' in System Devices, delete ALL entries (one tech says keep “My Computer”), including CD, video, hard drive controllers, hard drives, etc. Save HDD controllers and HDD for later; save your mouse for last (it's difficult navigating Device Manager via the keyboard). If you use a USB mouse or keyboard, do not remove the USB root hub first. Remove all IDE-devices, then move your way down the list and last remove the USB controller and associated items. UNTIL ALL DEVICES ARE DELETED, DO NOT REBOOT IF PROMPTED.

Note: Multiple users report that the IDE/ATA ATAPI Controller devices are the only required deletion (these MUST be deleted). All other devices need not be deleted, especially old hardware items that are continuing in use in the new machine. One tech reports this is “Much easier than deleting the ENUM key, and works every time”. One tech reports that only the PCI Bus needs deletion.

5) Shut down and make motherboard and hardware changes.

6) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed. Note ACPI. Save your settings, exit, and shutdown.

7) Reboot into Windows. When Windows restarts, it will not have any devices installed, so it will redetect all hardware and install the drivers. If it doesn't do this automatically, goose it with 'Add New Hardware' wizard in Control Panel. (When Windows starts, you'll be in 640x480 16 color, and presented with an error message about the display adapter. Cancel and close that and go to "add new hardware" and let Windows go to work and redetect everything). Windows detects all the new hardware and installs drivers. Reboot when prompted (this will happen several times) until you no longer get the prompts. If it prompts you to insert the Windows CD, point it to the cab files. If it asks for a manufacturer's driver disk, point it to the appropriate folder. Don't worry if a driver install fails, you can always go back later and reinstall that particular device from scratch. If you have a VIA based board, now is the time to install the "4 in 1" drivers.

Alternate: Many recommend rebooting every time Windows prompts, but others (experienced) prefer to decline all reboot prompts, and instead, waiting until all devices have been detected and all Wizard activity subsides. Then, before rebooting, open device manager, and delete the NON-SPLATTED entries (that's right, the non-splatted entries) for all duplicates. Common duplicates will be Display Adapters, Keyboards, and DMA controllers. Also delete all Sound Card entries.

8) Boot into Safe Mode. Check Device Manager for errors and duplicate entries. Correct as needed.

Note: You will probably have some yellow flags. You will probably have 2 items that are flagged with unflagged duplicates - the keyboard and the DMA controller. Remove the entry that is NOT flagged. If you have 2 display adapters, one will be flagged - usually the "standard VGA" will not be flagged and the actual adapter will be flagged. Remove the unflagged standard VGA. By now you should have CD-ROM support, so any other devices that are flagged can be reinstalled using the appropriate CD if necessary.

9) Install optimized drivers as needed. Uninstall any unused drivers.

Note: One user suggests a reinstallation of DirectX.

10) Shut down. Reboot normally.

Note: If you have problems with drivers (i.e. video or ide bus masters), try starting in Safe Mode and delete the settings in the device manager. This is supposed to be the same as killing the enum key entries but a lot of times WIN98 will ID the wrong drivers and reload them from its configuration record.

For instance the key HKEY_LOCAL_MACHINE\Enum\MF may have multiple configurations listed. Compare against HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\hdc. CAREFUL examination of which one is the one you want and deleting the ones you don't in the ENUM key will solve the problem of "musical driver" loads. There should be only three entries under

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\hdc for standard PCs. 000 is the controller, 001 is the primary and 002 the secondary. When WIN sees a misconfiguration elsewhere it goes back and redetects. Its an improvement over 95 but still dumb.

Take great care and use a registry backup program to be safe. The ENUM key is usually a safe place to edit.

Solution 4-4A-4B; In-place Upgrade to force fresh hardware redetection

(Described in Win2000 section 3)

Solution 4C Alternate procedure for In-place Upgrade:

Alternate Solution 4C: Proceed per Solution 4 steps, except that the registry key HKEY_LOCAL_MACHINE/Enum is deleted prior to last shutdown before hardware change.

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Boot into Safe Mode.

3) Start RegEdit or other registry editor.

4) Delete the following registry key: HKEY_LOCAL_MACHINE/Enum (This deletes the current hardware information, causing the hardware registry data to be rebuilt. However, this does not rebuild the VMM32 file. (You MUST boot into safe mode and remove the old hardware - or risk odd occurrences on your machine.)

5) Shut down and make motherboard and hardware changes.

6) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

7) Reboot with a boot disk and run setup from the Windows CD. (Yes, you are still re-running setup, but you install over the existing installation and therefore do not lose any of the registry information other than the hardware information. It is good to run setup rather than just reboot and let windows detect everything because during setup is the only time the VMM32 is built, and you need to rebuild it with the new hardware in place.)

Solution 5; Boot with CD ROM Support; Tools/Sysrec/PCRestore:

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Change motherboard and hardware.

3) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed for new hardware. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

4) Insert Windows CD and power up.

5) Select "Boot with CD-ROM Support"; Type x:(where x is your CD drive letter).

6) Select cd tools; cd sysrec ;pcrestore

Solution 5A; Boot with CD ROM Support; Run Setup with Switches:

1) Boot from a floppy, and copy operating system files to a folder on the hardrive. This prevents getting locked out in case of problems with controllers.

2) Now, boot from the floppy, with CDROM support.

3) Change to the directory where you put your OS files. (have any driver disks handy, for later when the OS asks)

4) Use the Setup command but with the following changes.

setup /ie /iv /im /is /IF /Pf

This will pseudo reinstall windows...very quickly and usually without BSOD or lockups, and it will freshen the registry with the newly detected devices. It will also skip scandisk, diskspace detection, billboards, memory checks (as you know you have enough memory), etc.... It will also not copy files that already exist, or are newer than the OS wants to install (uses "cachefindfirst"), and speeds up the installation. You can leave the /IF off if you want...it also turns off the verify after write during the install.

Solution 6; Create a new Hardware Profile; Reboot to redetect:

(This is a non-destructive alternative to deleting the enum registry key or deleting devices in device manager).

A hardware profile consists of specified changes to the original hardware profile configured in the SOFTWARE and SYSTEM keys of HKEY_LOCAL_MACHINE. These changes are stored in the Hardware Profiles subkey in HKEY_LOCAL_MACHINE. The Hardware Profiles subkey in the IDConfigDB subkey stores information about the profile, but not the profile itself. You can use System in Control Panel to create a hardware profile. Also, the system creates new hardware profiles automatically when it encounters configurations that require new profiles. You can create a profile before you make extensive changes to your system. That way, if the system doesn’t work correctly after the changes, you can restore the hardware setup to the way it was, and then start Windows using the profile for the original configuration.

1) Review and complete Pre-Action Procedures described in the Pre-Action Procedures section above.

2) Before changing any hardware, boot up the existing (old) system. Open Control Panel / System / Hardware Profiles. If profiles are unchanged since OS installation, there will be one profile named “Original Configuration”. This is the current hardware profile.

3) Identify the current profile and rename it to something representing the existing hardware configuration; e.g. “OldMobo-1” (original). The “1” designation identifies this file as the original and distinguishes it from the copy to be created next.

4) Copy the existing current profile to create a duplicate profile; e.g. “OldMobo-2” (copy). At this point you should have two identical profiles, “1” and “2”; (close and reopen the profiles window to be sure they are saved).

Note: The duplicate is created to trigger a system prompt on reboot which is needed to get the required hardware redetection. The only time Windows prompts you for the name of a hardware profile is when two profiles are so similar that it cannot differentiate between them.

5) Optional; For the extra-cautious only: Go into C:\windows\inf and delete drvdata.bin and drvidx.bin. (backup before deletion)

6) Optional; For the extra-cautious only: While in C:\windows\inf, delete any *.inf files you KNOW you no longer need. (backup before deletion)

7) Optional; For the extra-cautious only: In C:\windows\inf\other, delete any *.inf files you KNOW you no longer need. (backup before deletion)

8) Don’t make any hardware or driver changes until you reboot; you are running the ‘OldMobo-1’ profile at this time and you don’t want new changes written to that profile.

9) Shut down the PC, remove power, and do the motherboard swap.

10) Power up, and go into BIOS setup. Note the BIOS revision to be sure you have the most current version. Make any BIOS adjustments needed for new hardware. Note ACPI in BIOS. Keep it enabled if Windows is installed with ACPI or disable it if Windows is installed without it. Save your settings, exit, and shutdown.

11) Continue boot into Windows. As Windows starts, you should be asked which profile you wish to use. Do not select either of the ”OldMobo-1” or “OldMobo-2” profiles, instead, select 'None of the Above'.

12) With “None of the Above” selected, Windows boots up as if it’s the first time, and redetects all the hardware (new and old still in use). You should only need driver disks for any new hardware as existing hardware drivers will be on your hard drive. If Windows needs the Win CD or newer drivers, simply point the install at the directory where you copied Windows or drivers.

Note: It may be a misunderstanding, but two reports state that through this process of selecting “None of the Above”, Windows is actually updating or “redoing” the original (“OldMobo-1”) profile, not creating a third or new profile. If this is correct, to boot with the new settings, then, select the “OldMobo-1” profile. Also, do not delete the “OldMobo-1” profile thinking it is for the old motherboard. This advice is proved invalid if a third or new profile appears.

13) Note the name given to the newly created profile; “Original Configuration” (DON’T DELETE THIS). You can rename it to more clearly represent the new hardware (e.g. “NewMobo-1”). Use this profile when booting on the new hardware configuration.

14) Optional: As a backup for possible future use, some users recommended creating a copy of the new profile “NewMobo-1”; e.g. “NewMobo-2” (copy). Set the computer to always boot from “NewMobo-1” so the profile menu is not displayed at startup.

The great thing about this procedure is that it’s fast, and if everything goes wrong, you can put the old board back, select the 'OldMobo-1' (original) or ‘OldMobo-2’ (copy) profile, and be back with a booting system. Once you have the new system properly installed, if you won’t ever boot on the old system again, you can delete the 'old' profiles (OldMobo-1 and OldMobo-2). Deleting unneeded profiles cleans up the registry.

To manually create a new hardware profile:

1) From the Start menu, point to Settings, and then click Control Panel.

2) Double-click System.

3) On the Hardware tab, click Hardware Profiles.

4) Under Available hardware profiles, click a profile, and then click Copy.

5) In the Copy Profile dialog box, enter a name for the new profile.

To manually configure a hardware profile:

1) From the Start menu, point to Settings, and then click Control Panel.

2) Double-click System.

3) On the Hardware tab, click Device Manager.

4) Double-click the device you want to add or remove from the hardware profile, and then under Device usage select the setting you want.

INACCESSIBLE BOOT DEVICE:

After you change motherboards, or move the Windows system (boot) disk to another computer with a different motherboard, you may receive the following blue screen stop message when you try to boot-up:

***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE

This event is standard with Win2000, and uncommon with Win98 and Me. The cause is that the registry entries and drivers for the mass storage controller hardware on the new motherboard are not installed in Windows. Accordingly, Windows setup can't find the drive controller and/or the driver for it. Other causes might be: 1) The boot device setting in CMOS setup may be incorrect, or 2) poor drive or drive controller cable connections.

Win2K can cope with most hardware changes (by running the Found New Hardware wizard) but only if it can boot as far as the GUI desktop in the first place. And one of the few device changes that might prevent that is a change to the hard disk controller.

For IDE controllers, there are several different chipsets available. Each chipset uses a different Plug-n-Play (PNP) ID to identify it. The PNP-ID information of mass storage controllers for the new motherboard must be in the registry prior to startup for Windows to initialize the correct drivers. To fix, you must install the UDMA 66/100 or SCSI controller drivers in Win2000 before the hard drive will be recognized as the primary boot device; (To install drivers: <F6> during Setup).

In addition to the OS-specific motherboard-change procedures described later in this document, users report that the following solutions also correct this IBD problem.

IBD Solution 1: Microsoft Knowledge Base Recommendation:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q271965

IBD Solution 2: Load generic Microsoft drivers (all compatible):

On occasion, the user may wish to exchange the mainboard of a computer system running Windows 2000. Unless the replacement is identical to the original, a STOP (Blue Screen) error INACESSIBLE_BOOT_DEVICE will be observed when attempting to boot the existing disk image on the new board. This is caused by the presence of a mass storage controller on the new board that is incompatible with that on the previous motherboard. In most cases, this scenario will require a re-installation of Windows 2000; however, there are instances where this is not necessary, if the following conditions are met:

1) The Mass Storage Controller on both the old and new boards are standard onboard ATA/IDE PCI devices, as commonly found on many desktop system boards.

2) Neither controller uses RAID functionality.

3) It is still possible to boot Windows 2000 on the previous motherboard.

If these conditions are met, then the user may wish to try the following procedure:

1) Boot the PC system using the existing (previous) motherboard. **If you've installed the UltraATA Driver (if so, Device Manager->IDE Controllers->Primary Channel will be lacking its usual "Advanced Settings" tab) then uninstall said driver from Control Panel and reboot before continuing **

2) From the Device Manager, open up the "IDE ATA/ATAPI Controllers" section. On a typical system there will be three entries under this - the controller itself, and then the primary/secondary IDE channels.

3) Double-click on the entry for the controller, and change the driver to the generic default Microsoft "Standard Dual-Channel PCI IDE Controller". This is to IDE controllers what the Standard VGA driver is to video cards - i.e., it'll work on just about anything, but is rather slow and basic.

Note: If you're going to change graphics adapters as part of the motherboard change, be sure to change your graphics adapter driver to Standard VGA before you shut down the old motherboard for the last time. Otherwise, the computer will try to use the wrong (old) driver for the new video card when you start up.

4) Now shut down the system, and replace the motherboard as required.

5) If the new IDE controller is compatible with the "Standard Dual-Channel PCI IDE Controller" driver, then the system should boot into Windows 2000. (The "generic" driver is compatible with most IDE controllers out there - albeit at lower performance.)

6) At this point you should install the correct optimized IDE/ATAPI drivers for the controller. (i.e. VIA 4in1 drivers).

IBD Solution 3: Load mass storage drivers for new motherboard during setup:

Q216406 Specifying Third-Party Disk Controller Driver During Setup http://support.microsoft.com/support/kb/articles/q216/4/06.asp

Specifying a third-party controller driver during Setup should be necessary only if Windows 2000 does not contain a driver for your SCSI adapter, CD-ROM drive, or special disk controller, or if Setup does not detect your hardware correctly. To select a third-party controller during Setup:

1) Obtain the correct driver file from the motherboard or controller card maker. Copy file to a floppy disk.

2) Change motherboards.

3) Place Windows2000 Setup CD in the CDROM-Drive, reboot, and boot from the CDROM.

4) Early during the first phase of Setup, at the "Setup is inspecting your computer's hardware configuration" screen, press the F6 key ASAP; (F6 quickly to prevent drive controller detection). Then press “S” to specify an additional device.

Alternate: During the first phase of Setup, press F8 to troubleshoot, and choose boot up in Safe Mode. Press F6, then press “S” to specify an additional device.

Note: You do not need to install the ATA-100 driver during the WIN2K install process on a non-RAID IDE motherboard; WIN2K will simply treat it as an ATA-66 drive. Once Setup is complete, install SP2, and WIN2K will see the drive as ATA-100. If the drive is on a SCSI or RAID controller, you must use the 3rd party mass-storage device <F6> option, or WIN2K doesn't see the drive.

5) Win2000 setup will now ask for a TXTSETUP.OEM disk. Place the TXTSETUP.OEM disk in the floppy drive, and press Enter to continue.

6) Windows installs the correct driver.

7) To continue with Setup, press Enter.

IBD Solution 4: Delete Drivers using Recovery Console:

1) Open the Recovery Console and type LISTSVC. A list of drivers loaded on startup will be displayed.

2) Locate the IDE drivers and type DISABLE name.ext (where name.ext is the driver name and extension).

3) Once the IDE drivers are disabled, exit and reboot. On reboot, Win2k will load the standard default IDE driver and should startup.

IBD Solution 5: Boot using UDMA33, then load correct UDMA66/100 IDE drivers for new motherboard:

1) Obtain the correct driver file from the motherboard or controller card maker. Copy file to a floppy disk.

2) Attach hard drive to IDE 1 or 2 with a 40 pin cable. ID this HD in bios.

3) Boot up the system using UDMA33.

4) Go to device manager and highlight MASS STORAGE CONTROLLER. Go to properties, change driver; put the UDMA66-100 driver disk in the floppy drive. Update the driver on one of these MASS STORAGE CONTROLLER lines. When asked to reboot, do NOT reboot right now.

5) Highlight the other line of MASS STORAGE CONTROLLER, perform the same operation as the first line. When asked to reboot, YES.

6) When the system starts POST, turn off the power.

7) Attach HD to the UDMA66-100 port using 80 pin cable. Be sure the ends are attached per instructions in manual. Remove the 40 pin cable from the system (unless there is a CD-Rom, burner, extra HD etc. intended to connect using a 40 pin cable).

8) Power up the system. Go into bios and remove the HD previously detected. Just say "none" if you do not have anything attached to this port.

9) Save and exit.

IBD Solution 6: (To Salvage Data) Install unbootable drive as slave:

This does not solve the IBD error, but does allow data recovery from an unbootable drive:

If the old PC is trashed and cannot run, then provided that the disk has not been encrypted, you can install it in the new system as a slave.  Install another hard disk as Master, then install Windows afresh on the new disk.  Once installed, you should be able to access the old disk and copy data to the new drive.

GENERAL USER TIPS; NOT SPECIFIC TO ANY WINDOWS VERSION:

Usually, when a hard drive is moved to a new system, all devices should be set to 'standard' devices : ie- Standard IDE, VGA, etc. With standard devices compatible with anything, the operating system can be moved to new hardware, and Windows will boot on the new system without encountering a BSOD. Once the system is bootable, Windows can operate to detect and install the appropriate optimized drivers.

Safe Mode: If your computer will not start, you may be able to start it in safe mode. In safe mode, Windows uses default settings (VGA monitor, Microsoft mouse driver, no network connections, and the minimum device drivers required to start Windows).

When moving an operating system from an old hard drive to a new hard drive, there are several options:

Install the old HD as the boot disk (master, primary channel) in the new system. Make all system changes. After all is working well, install the new hard drive on the secondary channel, then Image the old HD to the new HD. Remove the old HD and move the new HD to master position on the primary channel.

On the old HD, prepare the OS for hardware change (e.g. delete HKEY_LOCAL_MACHINE enum, etc.). Move the old HDD to IDE2, and install the new HDD on IDE1. Boot with a floppy and run DriveImage or Ghost. Copy the old partition(s) to the new drive. Remove the Image floppy, and reboot. Upon reboot, Windows detects the hardware components.

Or, as a safety, Image the old HD to the new HD, remove the old HD, and make all changes to the new HD. If anything goes wrong, you'll still have everything on the old HD.

After system build, to test, boot from a floppy. This will give you a chance to make sure everything is at least basically working before getting involved with the existing OS and hard drive.

If you don’t remove your old hardware drivers when changing motherboards or any other hardware, Windows still has the drivers for the old hardware loading up. If you want to see this, start Windows in Safe Mode and open Device Manager; look under each item to see references to old hardware no longer installed.

You'll need to reinstall Windows if you want SSE to be utilized (according to AMD). SSE is new to the AMD CPUs; only XP CPUs have it.

------------------------------------------------------------------

Shopping cart by ShopFactory