"Exchange MOBO without OS Reinstall"

LeonardoLeonardo Wake up and smell the glaciersEagle River, Alaska Icrontian
edited July 2003 in Hardware
One of the cardinal sins - exchanging a motherboard withoug a 'clean' operations system reinstallation? Hmm, maybe not. What do you think? :scratch:

http://arstechnica.infopop.net/OpenTopic/page?a=tpc&s=50009562&f=77909774&m=1400925745
«1

Comments

  • EnverexEnverex Worcester, UK Icrontian
    edited July 2003
    I have done it. Just remove EVERYTHING from device manager in safe mode before you switch mobos (needs to be the LAST thing you do).

    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
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    I had a go at doing it once on a 2K box, on a basic level it's just a case of uninstalling and allow the OS to re-install all the motherboard function drivers (like NS said). It's tricky to say the least, but can be done. I wouldn't want to try it on a 98 based system though, that would be asking for it.

    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.;)
  • mmonninmmonnin Centreville, VA
    edited July 2003
    I did it once. Worked OK after as well.
  • Omega65Omega65 Philadelphia, Pa
    edited July 2003
    Spinner said
    I wouldn't want to try it on a 98 based system though, that would be asking for it.
    ;D;D

    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.
  • WuGgaRoOWuGgaRoO Not in the shower Icrontian
    edited July 2003
    pfff...screw u crazy people...i tried that a couple of times...it never worked for me :(
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited July 2003
    I format as I have nothing to lose.
  • TekGamerTekGamer Earth
    edited July 2003
    formating is the best option but just run sysprep and install the new mobo...

    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
  • kanezfankanezfan sunny south florida Icrontian
    edited July 2003
    on 95 and 98 systems it's fine, it just asks for drivers and it's good to go, at least in my experience. with XP, it's even better, all you have to do is run the repair install, you don't have to format. it's like a new fresh install, except you don't lose everything and you don't have to re-install everything. my mobo recently died on me, I went from a kr7a to an ecs k7s5a, to a kx7-r, both times i switched the mobo i did a repair install and everything's perfect. the only thing that sucked was having to re-install all the windows updates.
  • TemplarTemplar You first.
    edited July 2003
    I did something similar to that. My dad had just bought a new PC from dell. 600mhz with a TNT2 (This was back in oh, 98 or so?) and we switched the HDDs between the two so he got mine and I had his. It took me a while but I eventually got the stuff running on his. It was tough without broadband :)

    I just went ahead and formatted and reinstalled Windows :) I knew what was coming.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2003
    I haven't tried it yet with XP. In 95 or 98 the way I did it was to:

    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
  • edited July 2003
    I have done this several times in the past, mostly with good success, with both Win9x and Win2k. I have 1 folding rig right now that has made the migration from a BH6 mobo with the original Win2k install through a Soyo BX board, which died on me after 6 months(bad caps), then an Abit VH6T and presently on an MSI K7T Turbo2 mobo without re-installing the OS or formatting the drive.
  • WahoogieWahoogie Marietta, GA, USA
    edited July 2003
    About a month ago I swapped my KD7-Raid for an 8RDA+ without any type of software changes (besides installing the nForce2 drivers) and no hitches at all... though I'm gonna format soon anyway.
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited July 2003
    Both my new systems are built now. I did not perform a clean OS installation on either computer. One computer was transformed form an AMD-Abit KR7A-R to an AMD Barton - Abit nForce board; the other was from an AMD - Abit KX7333-R to an Intel P4 - Abit IC7. Those are pretty radically different setups.

    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.
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    Leonardo said
    Both my new systems are built now. I did not perform a clean OS installation on either computer. One computer was transformed form an AMD-Abit KR7A-R to an AMD Barton - Abit nForce board; the other was from an AMD - Abit KX7333-R to an Intel P4 - Abit IC7. Those are pretty radically different setups.

    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. ;)
  • MJOMJO Denmark New
    edited July 2003
    I swapped my processor from a T-Bird to a Thoroughbred.
    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. :scratch:
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    MJO said
    I swapped my processor from a T-Bird to a Thoroughbred.
    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. :scratch:

    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?
  • TheLostSwedeTheLostSwede Trondheim, Norway Icrontian
    edited July 2003
    Spinner, hotswapping different cores is a nogo in windows unless you do a repair m8. I have seen cases where the cache didn´t upgrade.
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    Mackanz said
    Spinner, hotswapping different cores is a nogo in windows unless you do a repair m8. I have seen cases where the cache didn´t upgrade.

    Oh yeah, that's a good point, I forgot to even consider that. Bloody cache. Doh!:banghead:
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited July 2003
    I hadn't considered the cache equation either. But for exchanging within the same class of CPU, such as Thunderbird 1.2 to Thunderbird 1.4, it shouldn't matter at all, outside of the BIOS. At least that's my experience.
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    Leonardo said
    I hadn't considered the cache equation either. But for exchanging within the same class of CPU, such as Thunderbird 1.2 to Thunderbird 1.4, it shouldn't matter at all, outside of the BIOS. At least that's my experience.

    Yeah that's right. Stay with in the family and you're good to mess around, try and adopt and may ecounter problems.
  • TheLostSwedeTheLostSwede Trondheim, Norway Icrontian
    edited July 2003
    Leonardo said
    I hadn't considered the cache equation either. But for exchanging within the same class of CPU, such as Thunderbird 1.2 to Thunderbird 1.4, it shouldn't matter at all, outside of the BIOS. At least that's my experience.

    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.
  • EnverexEnverex Worcester, UK Icrontian
    edited July 2003
    Lets lose the term `hotswapping` here gents as its being used incorrectly, hot-swapping refers to changing something over while it is still running, i.e. USB devices and some new PCI slots, really wouldnt like to try it with processor.

    NS
  • edited July 2003
    Mackanz said


    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.

    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.
  • EnverexEnverex Worcester, UK Icrontian
    edited July 2003
    MJO said
    I swapped my processor from a T-Bird to a Thoroughbred.
    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. :scratch:

    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.
    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.

    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
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited July 2003
    really wouldnt like to try it with processor.

    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!:eek2::eek2:;D
  • TheLostSwedeTheLostSwede Trondheim, Norway Icrontian
    edited July 2003
    NightShade737 said
    Lets lose the term `hotswapping` here gents as its being used incorrectly, hot-swapping refers to changing something over while it is still running, i.e. USB devices and some new PCI slots, really wouldnt like to try it with processor.

    NS
    :rolleyes:
  • TheLostSwedeTheLostSwede Trondheim, Norway Icrontian
    edited July 2003
    muddocktor said
    Mackanz said


    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.

    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.

    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?
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2003
    This is a new one on me. I would have never thought that cache or no cache would cause a problem. I would have expected it to be detected and installed automatically, with no more fuss than changing a cdrom drive, even if you went from a K6-2 to a Pentium 4.

    Live and learn.:mullet:


    Prof
    (Each day holds new surprises for me - one advantage of being dumb, I guess...:tongue: )
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    NightShade737 said
    Lets lose the term `hotswapping` here gents as its being used incorrectly, hot-swapping refers to changing something over while it is still running, i.e. USB devices and some new PCI slots, really wouldnt like to try it with processor.

    NS

    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.:rarr: :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'.;)
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2003
    Hot-Swapping is particularly perilous if you're talking about swapping your girlfriend for the "hot" chick you just met.

    Even more dangerous that what Leonardo described - and it ain't gonna be your comp that gets burnt!

    ;D


    Prof
    (The Deviate)
Sign In or Register to comment.