Is it possible to replace MB & CPU without doing a clean WinXPPro install?

[LurkingInNC]

I posted this in the OS forum and got some good input. Thought I'd check here for possible different or additional perspective.

Original Post:
I'm upgrading my system from an MSI socket 7(?) MB with an AMD 1600+ CPU to an Epox 754 board with a Sempron 3400+ CPU. Money is tight & the new MB, CPU, and a HyperTX2 cooler only cost me $65 total and should last me for several years (not a big gamer).

Is it possible to replace the MB & CPU without doing a clean WinXP Pro install? I've got a number of games & other programs I'll lose & be unable to replace if I have to do a clean Windows install.

If it is possible, can someone guide me as to how to go about it?

My Answers to Questions in the OS Forum Post
I'm not 100% positive but I think I got the OS from MS itself in one of their promo deals (I built the computer). The CD folder says "Your Full Version Copy of Windows XP Professional" and "NOT FOR RESALE OR DISTRIBUTION" and it came with a Product Key sticker on the CD folder. The CD folder says "Don't Lose This Product Key! You must use it every time you install this software...." Nothing on the CD or Cd folder says OEM. Safe assumption that this is a re-installable version (if not retail)?

The current board is an MSI KT3 Ultra2 with a VIA KT333 + VT8235 chipset. The new board is an Epox 8HDAI PRO with a VIA K8T800 + VT8237R chipset.

Problem with doing a clean XP install is that I've picked up a bunch of games and programs through the site giveawayoftheday.com that I'd like to keep. The registration process is such that you can download and activate games/programs only on the specific day it is offered. You can reinstall, but not activate it at a later date (I'm assuming the activation key is stored in the registry, which is why you'd lose the program if you do a clean OS install?).

Suggestions I've Received
1. Use the mergeide.reg procedure

2. Use sysprep to tell Windows to do a complete hardware rediscovery. Also it would probably be a good idea to install the storage drivers for the new controller before you replace the board, just in case.

3. Uninstall any chipset related drivers from Windows before I change out any hardware.


Any additional thoughts from the MB experts before I give it a shot? Comparison of the relative difficulty & risk between #1 and #2?

Thanks for any additional feedback!

 

[5t3v0]

I've done this in the past on socket A and 939 using your 3rd suggestion. Alternatively, find the registry keys you need & export them to a file, and then add to the registry after a new install.

 

[MadMurph]

Do you have the orginal XP disc? A lot less labor-intensive method is to just boot from the CD, get to the install window where the program finds any existing copies of Windows on your hd, and select "Repair" from the menu choices at the bottom. That will reconfigure windows for your new hardware.

The down side is you loose all of your Windows updates and, depending on the install version, your service packs. And you still need to install all the new drivers for your board. Short of a clean install, this is the most fail safe method. If you leave any stray files on your system from one of your other methods, you stand the risk of getting page fault errors at boot up, and you'll be going through the process I just described, anyway, to try and find your oversight. Good luck. MM

 

[LurkingInNC]

MM - I do have the original XP disc and a SP2 disc, but even then this would be a bit problematic since where I live I can only get dial-up (or satellite which I can't afford). It would take probably a day(s) to download the rest of the MS updates. Could I make a CD with the updates before doing anything and use it somehow with MS auto update instead of downloading updates?

5t - I probably should try to find & export the registry keys to be safe, but that would be cumbersome as well since I've got so many games & programs from the GAOTD site. Don't play 'em all, but would like to keep them as kind of a games library for guests.