Is this weird? dual installation survived a motherboard change.

[MxMaciel]

Hello all, I'm new to these forums and I bring some wacky case that
just happened to me a month ago. I had a system with the following
specs: Core2Duo E6550, 4GB DDR2 OCZ, 2x250GB WD HDD, 2x160GB Seagate
Hdd, GeForce 9600GT running with a Gigabyte Motherboard with the
Nvidia Nforce 650SLI chipset. The system reported very high
temperatures since the beginning with coolermaster's mystique chassis
so I put some extra fans in strategic positions and also changed the
CPU fan with no great improvement. Then I decided to switch to a
cooler chipset and traded my motherboard with some friend and got
another Gigabyte with Intel's P35 chipset. I switched the MoBos and
installed everything just fine but I was too lazy to uninstall the
chipset driver. So I just powered on the PC expecting a big fat
BSOD... I was surprised the moment I noticed how windows vista started
recognizing all my hardware again, all the drivers, one by one. So I
just restarted again the machine and the machine worked just fine. So
I tried the same on the XP partition and surprise! same there. This is
the first time ever this happened to me so... what do you think?

 

[Adam Albright]

Hello all, I'm new to these forums and I bring some wacky case that
just happened to me a month ago. I had a system with the following
specs: Core2Duo E6550, 4GB DDR2 OCZ, 2x250GB WD HDD, 2x160GB Seagate
Hdd, GeForce 9600GT running with a Gigabyte Motherboard with the
Nvidia Nforce 650SLI chipset. The system reported very high
temperatures since the beginning with coolermaster's mystique chassis
so I put some extra fans in strategic positions and also changed the
CPU fan with no great improvement. Then I decided to switch to a
cooler chipset and traded my motherboard with some friend and got
another Gigabyte with Intel's P35 chipset. I switched the MoBos and
installed everything just fine but I was too lazy to uninstall the
chipset driver. So I just powered on the PC expecting a big fat
BSOD... I was surprised the moment I noticed how windows vista started
recognizing all my hardware again, all the drivers, one by one. So I
just restarted again the machine and the machine worked just fine. So
I tried the same on the XP partition and surprise! same there. This is
the first time ever this happened to me so... what do you think?

I've seen it before. While it might work you're better off finding and
installing the appropriate drivers that came with the new MB on the
install CD/DVD. Chances are what happened is Vista installed some
generic drivers.

 

[spankydemonkey]

I've seen it before. While it might work you're better off finding and
installing the appropriate drivers that came with the new MB on the
install CD/DVD. Chances are what happened is Vista installed some
generic drivers.- Hide quoted text -

- Show quoted text -

You haven't seen it before. You can hardly see the floor from the
gutter.

 

[MxMaciel]

MxMaciel;729307 Wrote:

Hello all, I'm new to these forums and I bring some wacky case that
just happened to me a month ago. I had a system with the following
specs: Core2Duo E6550, 4GB DDR2 OCZ, 2x250GB WD HDD, 2x160GB Seagate
Hdd, GeForce 9600GT running with a Gigabyte Motherboard with the
Nvidia Nforce 650SLI chipset. The system reported very high
temperatures since the beginning with coolermaster's mystique chassis
so I put some extra fans in strategic positions and also changed the
CPU fan with no great improvement. Then I decided to switch to a
cooler chipset and traded my motherboard with some friend and got
another Gigabyte with Intel's P35 chipset. I switched the MoBos and
installed everything just fine but I was too lazy to uninstall the
chipset driver. So I just powered on the PC expecting a big fat
BSOD... I was surprised the moment I noticed how windows vista started
recognizing all my hardware again, all the drivers, one by one. So I
just restarted again the machine and the machine worked just fine. So
I tried the same on the XP partition and surprise! same there. This is
the first time ever this happened to me so... what do you think?

The quickest way to kill an XP installation is to change motherboards.
Chances are, your XP installation didn't have the chipset drivers
installed for the old motherboard, which is why it survived the change.

But as for your Vista installation, it's no surprise. I changed my
motherboard and CPU about 3 months ago because of hardware failure, and
my Vista x64 transitioned without any problems. Which worked out ok,
because it afforded me the chance to recover some data which I couldn't
do previously on a dead motherboard.

The only "problem" I encountered was the Vista install had to be
re-activated. This was a no-issue, because I re-installed from scratch
anyway after getting back my data that I wanted (email, contacts, and a
few other goodies).

Vista installations survive drastic hardware changes must better than
XP.

--
Dzomlija

Peter Alexander Dzomlija
-Do you hear, huh? The Alpha and The Omega? Death and Rebirth? And as
you die, so shall I be Reborn...-

_*Prometheus*_
MOBO: ASUS MB-M3A32-MVP Deluxe/WiFi-AP
CPU: AMD Phenom 9600 Quad
RAM: 2 x A-Data 2GB DDR2-800
GPU: ASUS ATI Radeon HD 2400PRO, 256MB
BOX: Thermaltake Tai-Chi Water Cooled
OS: Windows Vista Ultimate x64
'' (http://valid.x86-secret.com/show_oc...valid.x86-secret.com/cache/banner/333562.png]'
(http://valid.x86-secret.com/cache/banner/333562.png)- Ocultar texto de la cita -

- Mostrar texto de la cita -

You got a point there Dzomlija, because both motherboards share the
same driver for sound and network, and the Intel chipset driver is
quite simple to install compared to nvidia's and the intel one doesn't
have special features. That's why I was shocked about the xp
installation, because it had the Nvidia board driver installed and
worked just fine.

Thanks for the comments.

PD.


Spanky and Dave: BITE ME.