"Exchange MOBO without OS Reinstall"
One of the cardinal sins - exchanging a motherboard withoug a 'clean' operations system reinstallation? Hmm, maybe not. What do you think?
http://arstechnica.infopop.net/OpenTopic/page?a=tpc&s=50009562&f=77909774&m=1400925745
http://arstechnica.infopop.net/OpenTopic/page?a=tpc&s=50009562&f=77909774&m=1400925745
0
Comments
Wost that could happen is Windows complain it cant find the Windows boot drive, in which case you need to do a repair install with will detect your HD controlers and all should be fine.
Though when I switched mobos without formatting, I noticed a small speed increase after formating (at a later date) but only in games.
Hell, I have put my current hard drive in a totaly differnt machine, booted and used Windows (XP) fine before, it just used default drivers.
NS
I still wouldn't suggest anyone do it just to save themselves a re-install, but it's always good for practicing your OS taming skills.
Should be only tried by the brave and skilled.
I might add, my attempt at doing it with 2K, ended up in failure, and the motherboards in question were very similar.:banghead:
A testament to my personal limited computer ability, or a re-iteration of a fact of near impossibility. I think it's somewhere in the middle.;)
I had an 98SE install migrate from a Epox 8KHA+ > 8K3A+ > 8K5A2+ > 8K9A2+
Mobo swaps go easier when you stay with a particular mobo line (same mobo and chipset company) In this case Epox and Via KT266A/333/400 series.
I did not read the link but if thats what it says then I agree with it. If not and it says something like remove all the crap in dev man then I disagree...
Sysprep is your friend.
Tek
I just went ahead and formatted and reinstalled Windows I knew what was coming.
1) boot in safe mode
2) clean out device manager
3) edit the registry to get rid of the IDE controller primary and secondary "Child" devices (they disappear from device manager when you get rid of the main controller, but remain in the registry)
4) clean out the non-standard .inf files from the Windows Inf folder (i.e. all of them except the ones Windows sticks in there during installation).
I always format my drive for any computer I care about, and have only used this method as a temporary measure, or situations like the accountants computer at one place I worked at. She would doof up her computer on a weekly basis (self-inflicted PEBKAC problems), then insist that it just couldn't be her fault and demand new hardware.
Prof
Here's how I did it:
1) remove/uninstall nearly all drivers and devices via Windows' "Add or Remove Programs" and Device Manager
2) used RegCleaner to remove remnants of device drivers (where possible)
3) shut down system
4) disassemble
5) rebuild (using hard drives fresh from the previous configurations)
6) reset CMOS
7) start-boot to CD
8) install WinXP in "Repair" mode
9) as soon as Windows is up, install all device drivers from the motherboard CD
After steps one through nine were executed, there were still leftover, unneeded devices, such as Highpoint RAID and Highpoint RCM. Windows was unable to remove everything, as some removals requiring rebooting on the original machine.
Both before and after rebuild, in Device Manager, under view setting, select "Show Hidden Devices"
Before I did all this though, I backed up everything to spare hard drives using Norton Ghost. I also used the Files and Settings Transfer Wizard to back up Windows and programs settings. Email folders were also exported or archived depending on clients used.
Crazy b**... I mean, well done man. Nice job.
Let us just say Windows XP was not too happy afterwards.
I tried a repair and some other things.
I ended up reinstalling the whole thing.
CPU hot swapping, isn't something which should cause you problems. Curious. I presume you mobo fully supported the thoroughbred? what exactly happened in the OS?
Oh yeah, that's a good point, I forgot to even consider that. Bloody cache. Doh!:banghead:
Yeah that's right. Stay with in the family and you're good to mess around, try and adopt and may ecounter problems.
That´s correct my friend. Even going from Tbred A to B isn´t going to cause any problems. Pally to Tbred MIGHT work, but i wouldn´t bet on it.
NS
Had no problems at all from a Pally to Tbred A. Also had no problems at all from a Tbred B to Barton on my A7N8X board either. I also upgraded a friend's computer from a Spitfire Duron to a Pally 1800 and had no problems with his WinMe install accepting the upgrade either.
I've never run into a problem on a straight processor upgrade, but I'm sure it can happen.
You really shouldnt have had any problems with that at all.
You can use the same Windows install in a completely differerent machine, but there are particular times when you get problems.
You dont get problems if it is pretty much the same hardware as it uses the same drivers or compatilble.
You dont get problems if it is completely different hardware as Windows loads the different drivers.
You do get problems when Windows thinks it can use some of the current drivers for the different hardware, as it all goes wrong.
You do get problems if windows doesntl load the current drivers for the hard drives as it wont be able to read anything and will give either the "Innaccessable Boot Device" error (seen when trying to use RAID without loading the drivers first) or you will get hive or boot file errors and a point blank blue screen boot halt.
Changing processors of any type withing the Athlon family shouldnt cause any problems, ever. If it does, you broke something else and it was unrelated.
Levels of cache change wouldnt affect anything as that is all delt with the processor and at highest level the BIOS, not the OS.
NS
Now there's an idea for you - swapping a CPU with the power on. Have couple drinks first, have a camera ready, and please, turn off the smoke detector down the hall!
The issue isn´t whether it´s accepting it or not, it WILL accept it but in many cases, you loose the cache gain. From Duron to pally is a bit of cache difference, the same on Tbredb to Barton.
Do you still use any of those setups and still on the same os install? Im curious, can you take a wcpuid and have a look?
Live and learn.
Prof
(Each day holds new surprises for me - one advantage of being dumb, I guess... )
I realise what the term means dude, I was using it in the context of having the OS still installed (hot) etc etc. So essentially in relative terms, having an OS installed and changing the CPU without re-installing it, is relative to changing something over while the power is still on. That is just what I meant.
So from here on in, I officially proclaim that the term hot-swapping when used with reference to changing a CPU, means to change the processor on a machine, without performing a re-install of the operating system. :ukflag:
Because I mean, you're right, trying to change the CPU whilst the power is still on, is just called 'Being-Stupid', not 'Hot-Swapping'.;)
Even more dangerous that what Leonardo described - and it ain't gonna be your comp that gets burnt!
Prof
(The Deviate)