Unexpected Result when changing mobo

[Fern]

Thanks for looking.

This result seems odd and am wondering if others have experienced this. Will I have problems down the road?

What happened? Well, I put a new mobo in my fathers PC (change from an NF2 -> Via chipset). Articles like Anands "How to change a mobo w/o a reinstall" lead me to expect a "blue screen" upon attempting to boot.

Instruction say I must do a "repair install" to switch the drivers etc.

However, this thing booted up OK. Did get some "new hardware" found messages etc. I had to stop at this point as my father's cd drive is not working.

But I did check in the hardware manager and looks like XP stuck in some "stock drivers" (the nForce drivers were not to be found etc).

I'm not familiar with XP (I use 2Kpro). Everything I have read about changing mobo lead to me believe that thing should absolutley not boot, given the different chipsets (I usually reformat/reinstall when changing out my own mobos).

What say you guys??

TIA
Fern

 

[Smilin]

Booting is not an unexpected result, just a lucky one.

Update all your drivers of course. Service pack and patch too.


If things are just not working right, pop in your XP CD and choose upgrade. This is the GUI way of performing a repair.

 

[Fern]

Well, it's showing up as having SP2. Since I never had to try the repair install thingy mentioned in the articles, seems to me that everthing should still be there.

I'm just shocked it would boot with such a mobo change (nForce chipset to Via chipset). I've just NEVER read where anybody said it would/could boot under such circumstances.

Thanks,
Fern

 

[Nothinman]

I'm just shocked it would boot with such a mobo change (nForce chipset to Via chipset).

The chipset is largelly irrelevant in that regard, usually the problem is the storage controller since you won't have drivers for the new controller already installed or some other crappy driver that likes to BSOD when it's hardware isn't present.

 

[NogginBoink]

Originally posted by: Nothinman

I'm just shocked it would boot with such a mobo change (nForce chipset to Via chipset).

The chipset is largelly irrelevant in that regard, usually the problem is the storage controller since you won't have drivers for the new controller already installed or some other crappy driver that likes to BSOD when it's hardware isn't present.

Since the IDE/SATA controllers are typically part of the chipset, the chipset is relevant. 🙂

 

[Nothinman]

Since the IDE/SATA controllers are typically part of the chipset, the chipset is relevant.

I suppose so, but they're still seperate entities. I guess I'm just spoiled by not having to worry about the chipset, all of my drivers come with the kernel and any chipset quirks are handled there transparently.