Replacing motherboard...

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I have an e machine with a dead motherboard.

I have an MSI PM8M-V that I'm planning on replacing it with.

Is there a painless way I can just pop the new MB in, replace some drivers &

Both old & new boards have everything onboard.

Since I have extra HDs laying around, my next choice was to install
everything new on another HD & copy Docs & Settings from old HD.

I am open to any other suggestions!

Re: Replacing motherboard...

Quoted text here. Click to load it
Your last suggestion of a clean install is the best idea. far fewer hassles
than trying to use the old windows setup. Make sure you have all the
mobo drivers before you start.

Re: Replacing motherboard...

If you change the motherboard in a computer that has a version of Windows
loaded on the harddrive, then after changing the motherboard you MUST
reformat the harddrive and do a fresh install of the OS.  Otherwise you will
experience ongoing nasty data errors and system malfunctions.


Quoted text here. Click to load it

Re: Replacing motherboard...

On Thu, 2 Mar 2006 16:16:12 -0800, "DaveW"

Quoted text here. Click to load it

We've been through all this before, no that is not
necessarily true.

If he buys another motherboard with the same chipset, odds
are windows will boot up and it'll simply have to
replug-n-play a few bits.  He may need to uninstall some
drivers from add/remove programs, maybe even boot safe mode
(but I doubt it).  Worst case with that situation is to do a
repair install.  It's far more likely to be necessary with a
different motherboard chipset.

Format the hard drive and do a fresh install is the "you
don't know how", not the "it's necessary" answer.

Re: Replacing motherboard...

kony wrote:
Quoted text here. Click to load it

I agree. It also depends on the version of Windows. XP is the fussiest, 98SE
you could change the mobo, graphics card, NIC, sound card all at once and
often it'd boot up and install new drivers just fine.

Re: Replacing motherboard...

Mike wrote:

Quoted text here. Click to load it

There's no _completely_ painless way to do this;
you'll wind up making some sort of a sacrifice to
the gods of computer geekery, either blood from a
dinged knuckle or sliced finger, or a dropped hard
drive, or running over an important CD with your
chair, or.... <grin>

Ah, nevermind. I'm just in the process of building
systems for donation out of all the old socket 7
parts I've got lying around.

-- Marten Kemp
(Fix name and ISP to reply)
... There is only one Gosh, and Jeepers is His son.
* TagZilla 0.059 *

Re: Replacing motherboard...

Also some emachine cases are built to only take the motherboards they
install.  (Proprietary).  I'm not sure if this is true in all cases
but at least in the two I attempted to install micro atx motherboards

Re: Replacing motherboard...

Hi Mike

If you replace the motherboard, you must do a clean install of Windows.
The reason being that the OS installation detects your hardware. So I
do recommend that you take out a clean HD and install Windows and your
old apps there.

Best Regards,
Gary Hendricks

Find hundreds of FREE tips on building computers.
Subscribe to my newsletter, The Computer Builder:

Re: Replacing motherboard...

On 4 Mar 2006 03:57:33 -0800, "Gary Hendricks"

Quoted text here. Click to load it

In fact, there is zero gain to doing a clean installation of
windows over a migration of an existing installation once it
works.  By that I mean a repair installation might be
necessary or any other issues handled on a case-by-case
basis.  The most pointless thing to do is never bother
trying, since any way you look at it, if the current
installation can't be moved due to lack of ability by the
installer, at most the installer was out a few minutes of
their time (not many minutes either, even a repair
installation can be mostly unattended).

Quoted text here. Click to load it

Which might be important if plug-n-play didn't exist.

Re: Replacing motherboard...

Windows 2000 is the worst, XP is a little better.

With win2k the system would only tolerate a certain amount of hardware
change before bluscreening at startup this was designed into the system in
an attempt to stop pirating  by cloning partitions (ghosting). Ghosting
works fine up to a limit.

XP usually just needs a system repair from the install CD (or other
location) to fix it up, but depending on your setup it may be almost as fast
to do a complete re-install. The problem is that you may have some obscure
program installed and associated in the system.

My experience is that (on my own personal machines) the install process does
not end at the installation of windows, it continues on into the
installation of the software packages, and then in to the customization of
the interface. It may go on for some weeks until everything is exactly the
way you like it again.

If you can avoid this then by all means do so.

Quoted text here. Click to load it
Quoted text here. Click to load it

Site Timeline