Sign-in / Sign-up
Your question

New motherboard and chipset requires fresh isntall of OS?

Tags:
  • Motherboards
  • Chipsets
  • Product
Last response: in Motherboards
June 24, 2007 11:11:48 AM

Greets,

I have a GA-965P-DS3, and really hate the thing. I've had non-stop issues with the CMOS battery dieing on me every 2 to 4 weeks. Gigabyte don't send me a new one with an RMA since they just run the same tests as when i t left the factory.

At any rate, I was going to get the EVGA 122-CK-NF68-A1 and just reinstall all my current components onto that board. However, I really do not want to have to reinstall WindowXP and all my programs. I've read/heard from some places I will have to reinstall Window and heard I will not from other places. So I wanted to get the opinion from here.

Thanks in advance,
Ben



P.S. I still have the isntall disk's for Window so mybe I just need to boot from those and 'repair' but I don't know.



Edit: I'm not really partial to that 680i board, I just would like some 680i board and not Gigabyte. So if you have any recommendations, let me know.

More about : motherboard chipset requires fresh isntall

June 24, 2007 9:54:38 PM

Here's one way to do it. Before you take the hdd out, I'd uninstall all the drivers. I did this once just to see if it would boot into Windows on the new mobo, it did and then I did a clean install but I definitely wouldn't run it other than to back up data doing this.
http://www.theeldergeek.com/replace_motherboard.htm
June 25, 2007 10:09:03 AM

and turning the computer back on.

Windows must go - “AHHH where the F*%^ am I?”

I'd go for a new reinstall.

Get an Ubuntu live CD and use that. no HDD needed. if the windows install doesn't work and you need to get on the net.
Related resources
June 25, 2007 11:37:06 AM

Alright thanks.


I'll order the motherboard today and post if I have any issues.
July 5, 2007 11:38:57 PM

well, you can try "sysprep" on it, that works for me when i have updated hardware and don't want to do a full reinstall. BUT, if it doesn't work, you will then *have* to do a repair install. (if you're reluctant to take the chance, a repair install is the safer way to go; it accomplishes the same thing, it just takes longer.)

as the previous reply said, the *best* route is a full reinstall, but if you have a complicated setup with lots and lots of applications, that's a real PITA.

http://support.microsoft.com/kb/302577/en-us

is the link to the KB article describing sysprep. the utility is located in the SUPPORT folder of a Windows 2K/XP install disk. there's a folder in there called TOOLS, and inside there are some files. the one you want is called DEPLOY.CAB.

if you extract it, you will find a number of files, including sysprep.exe and setupcl.exe. create a new folder in the root level of your C: drive called "sysprep" and put sysprep.exe and setupcl.exe in there. then run the program in the DEPLOY folder called "setupmgr.exe". this will create the .inf file sysprep needs to get it's information from. it's pretty self-evident what info setupmgr wants: choose "Create new", "sysprep setup", pick which windows version, and choose "Yes, fully automate the installation." (though you can do a non-automated one and answer all the questions during the setup process, like you do with an install or repair.)

from here, answer the questions as needed. most of the stuff you won't need to add anything to, but the name, computer name, administrator password, and product key fields you will want to answer. (magicaljellybean.com has a keyfinder utility that makes it easy to get your installed windows key if you have no other record of it.)

when setupmgr finishes, it creates the sysprep.inf file. place a copy of this in the C:\sysprep folder. open a command prompt and change the directory to "C:\sysprep". type the following command when you are ready to shut your computer down before the upgrade: "sysprep.exe -reseal -mini -pnp".

this command forces sysprep to use the NT mini-setup (the question section of a windows install) and to re-initialize the Hardware Abstraction Layer (HAL) (i.e. the PnP info for your hardware.)

sysprep will "work..." for a bit, then shutdown.

when you reboot, you will eventually see a screen that says "please wait while setup is working" or something to that effect. eventually it will finish and continue to boot into your windows environment. at this point, you should be back to where you were before, with a fresh HAL and a new activation to go through! :evil:  if you're lucky, you will activate with no problems. you will need to run Windows Update again if that's your thing and probably have to restore a bunch of interface options, as these are reset during the sysprep run. also, install the motherboard drivers from the disc you received with it.

it's a *really* good idea to backup your current installation somewhere before you start this, as things can go awry and leave you with no choice but a repair install, or worse, a full re-install. i recommend moving all data files to another drive or partition (music, videos, documents, installers, etc.) and/or running the Files and Settings Transfer Wizard on your system and moving the USMT.UNC folder onto another drive as well. this will allow a quick restoration of most of your settings (and files if you choose that route.)

i use this procedure pretty frequently at my work to upgrade systems while leaving the windows installations intact. it saves a great deal of time on the 90% of systems that have no problems. i had one big hassle with a system the other day because it had been partitioned with "System Commander" and had a boot manager installed in the boot sector. this prevented windows from booting correctly and caused a great deal of time wastage.

good luck, if you choose to accept this mission.
July 6, 2007 1:12:39 AM

well... i have had this problem before and i would say just put the hdd back on and just call the automated shit from microsoft to give you a new "code" and you'll be all set
July 6, 2007 1:43:19 AM

suprisingly, i had absolutely no problems after JUST switching my mobo (not anything else). i went from an nforce chipset to an intel p35 and windows recognized it immediately after i installed mobo/chipset drivers off the cd.

worst comes to worst, just be prepared for a reinstall
July 6, 2007 2:50:21 AM

switch mobo, do a repair install, if that gives you floads of errors upon running windows, back up your gear and run a clean install
July 7, 2007 5:14:02 PM

If I am understanding you wright, you have a new board and and old drive with windows already installed, and yes to make a long store short, you can use your old drive. I have just completed an installation of a new board in my pc using my old hd. After going into bios on boot up and making sure all was good as far as time boot sequence and what not I then booted into my system. The mobo will recognize the drive and boot into your windows installation. You will have to re-active windows do to a change to your system, but all your information will be there waiting. You will have to install all drives using your disk sent with your new board, this in order to access the net. It's called "kiss" keep it simple stupid. This does not apple to you, but all those who try and make a mountain out of a mole hill. Have a good day.
July 7, 2007 6:07:41 PM

I've changed out motherboards a number of times and never had to reinstall the OS yet. Maybe I've just been lucky, but everything has worked fine for me. Sometimes I have to contact M$ and get the OS activeated, sometimes not.

Just be sure to back everything up before you make the change. Then if you do have to reinstall the OS, you won't loose anything.