raid drivers maybe? Did you turn raid off in the cmos and try it?

I still think your friends a moron though.

 

-----signature-----

I'll keep playing with it.

 

-----signature-----

I've done fairly smooth in-place swaps of mobos with similar hardware (same northbridge/southbridge/storage driver, etc.) in Windows XP.

Otherwise repair install is the preferred method, if you want things 100% perfect full reinstall is the only way.

GLHF!



PS: Also look into Sysprep tool, applicable in some cases, I actually used that personally and not repair install for clients back in the day. It will require reactivation as I recall.

 

-----signature-----

Fresh install of windows is what I recommend. I'm not a tech but this is what I do everytime I switch mainboards

 

-----signature-----

My understanding is that, unless the replacement mobo is fundamentally the same (chipset basically) as the old one, Windows will 'burp' and you will have to buy a new license for the Windows you have (if OEM).

 

-----signature-----

If you replace the MB but keep the same Windows system - Windows will completely freak the fark out.



The friend sounds experienced to me - you're the one coming off sounding like the moron.


Windows will not play nice on a new motherboard, because the GUID/UUIDs of everything changes. When it boots it will fall down and go BOOM - either by rebooting continuously, or just Blue Screening the moment it leaves the bootloader. (Edit: And it has nothing what-so-ever to do with the CPU or licensing. It's the fact that all the hardware Windows is expecting to find is now just gone, including the hard drive as far as it is concerned)


Can this be worked around? Certainly - it's just not fun and does involve significant prep time. This includes replacing all the motherboard and especially storage drivers and switching to generic drivers for those same components. This may or may not be possible on your old motherboard. Don't just remove the old motherboard drivers - switch instead to the generic built-in driver for each component and make sure you can still boot. If you can boot using the generic drivers you should be able to get it to boot when you swap in the new MB.


It is, of course, a helluvalot easier to just reinstall. You don't have to, but if you've never done a p2p Windows migration before then this is probably not the time to figure out how.

 

-----signature-----

Turn it off. Wait thirty seconds. Restart.

Sexpanther

 

-----signature-----

This. A Mobo swap - unless it's an identical model - will almost always result in a blue screen on boot. Win 7 may have changed that, but I doubt it. It's economically favorable to Microsoft to prevent hardware swapping as much as their users will tolerate.

 

-----signature-----

You can have Windows freshly installed in under an hour. Stop wasting your time.

A new motherboard (of a different brand or model) means a new install. Don't let anyone tell you otherwise.

 

-----signature-----

Never ascribe to malice what can be accurately blamed on incompetence... especially when it comes to Microsoft engineering.



You can safely ignore ignorant bullsh!at like this.


You can do a motherboard swap without having to reinstall. It isn't even extremely difficult - it's just time consuming. You also have to be very meticulous in how you go about doing it.


In general it's easier and often times faster to just reinstall. If you don't mind learning some new tricks however it can be beneficial, even "fun", to do it the hard way and swap the MB and make Windows work on the new hardware.

 

-----signature-----