New motherboard and XP

Associate
Joined
15 Sep 2005
Posts
845
Just upgraded PC from XP3800/Asrock Dual Sata-II to 720X3/Biostar TA790GX.

Since people often raise questions on whether you can change mbs and not have to reinstall XP (and in particular OEM versions) here are my experiences. Firstly I was assuming it would work as I've done it before but I did more reading up which seems to have helped.

1) before starting I took precaution of backing up important stuff on PC to a NAS and also copied the XP partition on my HDD using a partitioning tool so that in event of problems I could restore the initial state.

2) before taking out old mboard I used SYSPREP from XP to "reseal" the installation. This, I think, strips the install back to the bare minimal drivers etc.

3) First step was to boot up mb with no HDD/CD connected to check out the BIOS - TA790GX came with an old BIOS that posted with the 720X3 but didn't recognize it ... using the BIOS based flash update I was able to update to current version via a USB stick.

4) Having got this sorted out plugged the HDD/CD in and booted up ... XP started and due to resealing went into a mini-install mode and basically worked. Only minor panic was when it said my windows id code wasn't valid ... but on checking I'd mistyped one digit. During mini-install and/or initial boot after its restart it asked for some drivers and I pointed it to the CD that came with the mb.

5) XP now worked but said it needed to be authenticate ... once I'd got the LAN drivers installed and network connection running clicked on the relevant icon and it went off and re-authenticated itself.

So it all went extremely smoothly and no issues.
 
Oo, sysprep, sounds useful. So all your applications etc copied across without need to re-install ?

All applications are there ... its the same HDD so nothing is being copied. What Sysprep seems to do is to roll back the driver support to the basic set that the XP install starts with so that when it next reboots it repeats the install steps where it recognised the hardware and loads the relevant drivers ... for most of this the drivers are already on the HDD and for the ones from the new MB they are on its CD.

After this completes everything appears to be as it was .... only issues are with apps that recognised the hardware for authentication purposes (for me this seemed to be XP, Office and steam - XP and Office needed a quick internet exchange to re-authenticate and steam just needed my password).

Note: I gather that this isn't really what SYSPREP is designed for .... its intended for people like IT departments to make a standard XP install that can be rolled out across PCs with each PC able to customize to its hardware.

Previous time I changed mb's I took the approach of deleting all the MB drivers via control panel/system/hardware devices then let next XP reboot find the new ones ... sort of the same process but didn't go as cleanly and, I think, ended up with XP deciding it definitely needed re-autheticating before I'd got the network working so that time I had to do it via phone and exchange 40-digit codes with an automated response system.
 
After my recent upgrade this is just what I'm looking for and definitely worth a try. Any idea if it prompts for raid controller driver disks ?

No idea - I'm not using RAID. I suspect that this could be a problem as the boot on the new MB needs to know that its RAIDed ... but at that stage you don't have the correct RAID drivers. So may not be so simple in this case
 
I wanted to transfer my complete OS install from on board RAID0 on my old DFi nF4 chipset 939 board to on board RAID0 on my new Asus M3A79-T Deluxe AM2+ board, so I gave sysprep a try.

:D It Works :D

Great news ... I assumed that "unRAIDing", sysprep-ing, changing to new MB and doing mini-install then "reRAIDing" would probably work
 
Back
Top Bottom