Motherboard replacement XP Headache

[Leythos]

But the likely scenario is that the computer will *not* boot following a
motherboard change and a Repair install of XP will be necessary. As Tom (and
perhaps one or two others responding to your query) has pointed out, there
is simply no absolute need to (in effect) reformat your HD and make a fresh
install of XP merely because of a change in motherboards. In our experience,
the Repair install works fine in this case.

Why is it that you people can't read what the OP posted - he's already
tried a repair/reinstall and it didn't work - that means that he doesn't
have the proper drivers for the new motherboard and that there isn't
available drivers on his XP CD to handle the changes in the hardware.

While there are several ways to get around a wipe/reinstall, it's almost
as quick to just clean install and that also cleans up the left over crap
too.

I would never suggest that someone wipe their drive for a basic driver
issue, but after they've tried a repair/reinstall and state that it
doesn't work, it would be a next step, without holding their hands, to
just wipe/reinstall.

 

[Leythos]

NO matter what the MOBO, Windows will install default drivers for the
chipset, it is then up to the PC person to install updated drivers for it,
and YOU CAN ONLY DO THAT WHILE IN WINDOWS! get it? So, regardless of whether
one does an inplace install (repair, or fresh install, the proper drivers
are used, to then be updated accordingly)

Look, I've installed enough upgrades to know that changing a motherboard
is often a crapshoot when it comes to repair/reinstall. Sure, it works
many times, but there are times when it just doesn't work. As an example,
consider SATA controllers, or Promise controllers - if you can't access
the drive and XP doesn't have native drivers then you are SOL.

 

[Tom]

Nowhere did I suggest that XP removed the drivers.

Oh dear! density meter almost hits a 10 on the hardness scale on this one,
but I am going to give you benefit of an education here.

And the reinstall may not always work due to issues of drivers that are
not available for the NEW motherboard, which means that there are times
when a full reinstall is needed. You appear to think that the NEW
motherboard was exactly the same as the old one, and if it was it would
have just been a simple swap without the need for repair/reinstall, but it
does not appear to be exactly the same board.

Wow, your logic is terrible!! But here goes---

You say he may need new drivers, and hint, that installing a new MOBO may
require that for the chipset, OK. Do you think XP will not run, if the
updated drivers are not there? If so, then one absolutely cannot run
Windows, right? OK!

NO matter what the MOBO, Windows will install default drivers for the
chipset, it is then up to the PC person to install updated drivers for it,
and YOU CAN ONLY DO THAT WHILE IN WINDOWS! get it? So, regardless of whether
one does an inplace install (repair, or fresh install, the proper drivers
are used, to then be updated accordingly)

In the OPs case, he doesn't need new drivers since he was able to retain the
original MOBO, but that doesn't mean one cannot do a repair install (or any
install) with the updated drivers, or one couldn't get into any kind of
install of Windows. If you cannot see the total fallacy of your argument,
then that is again how you think things work, regardless of how they do in
the real world.

 

[Leythos]

So what! This does not address your contention that drivers are needed for
Windows to work with the new chipsets that come on another MOBO. I addressed
your logic as totally fallacy, and as usual, you avoid it!

Since the motherboard has chipsets for SATA and/or Promise devices, and
since those are not supported in the shipped XP CD, where do you think XP
Repair/Reinstall is going to get them?

It clearly addresses that there are some hardware built into motherboards
that is not directly supported by XP and that can even keep the system
from booting without additional drivers.

My guess is that you're use to working with older computers and not
anything in the last years production and absolutely not servers.

 

[Tom]

Look, I've installed enough upgrades to know that changing a motherboard
is often a crapshoot when it comes to repair/reinstall. Sure, it works
many times, but there are times when it just doesn't work. As an example,
consider SATA controllers, or Promise controllers - if you can't access
the drive and XP doesn't have native drivers then you are SOL.

So what! This does not address your contention that drivers are needed for
Windows to work with the new chipsets that come on another MOBO. I addressed
your logic as totally fallacy, and as usual, you avoid it!

You said:

I got news for you, but the motherboard does indeed matter to Windows and
how it's accessed - ever hear of Chipset drivers, how about SCSI drivers,
how about IDE/SATA chipset drivers, how about Video (integrated) drivers,
how about USB drivers.... It has a lot to do with Windows OS.

So, repair or not, doesn't one have to already be using Windows to install
drivers? This is what is contentious to your logic to doing an clean or a
repiar install. In either event, one will have to load drivers, but by your
estimation, you cannot use Windows without the newer drivers.

 

[Leythos]

Again, HITF does one install the drivers without being in Windows, this is
the point your dense effin skull cannot absorb!

You're really showing your ignorance - you are not in "Windows" when you
press F6 to install drivers during the initial setup, before Windows
launches.

 

[Tom]

Since the motherboard has chipsets for SATA and/or Promise devices, and
since those are not supported in the shipped XP CD, where do you think XP
Repair/Reinstall is going to get them?

It clearly addresses that there are some hardware built into motherboards
that is not directly supported by XP and that can even keep the system
from booting without additional drivers.

Again, HITF does one install the drivers without being in Windows, this is
the point your dense effin skull cannot absorb!

My guess is that you're use to working with older computers and not
anything in the last years production and absolutely not servers.

Your guess is totally wrong, and servers have nothing to do with drivers in
the case here. get a life, and get off your high horse, that one who doesn't
run a server, doesn't know operating systems. But my guess is that you are
liar when it comes to how workstations and servers you say you actually use
for home use, considering your inability to address your contradiction, or
your avoidance to find fault in your thinking.

 

[Leythos]

And it is indeed a topic worth discussing
because of the misinformation and outright distortion one frequently comes
across in this and other newsgroups concerning this subject.

Anna - have you ever experienced a repair that didn't get the computer
back up and running? I have.

 

[Anna]

Does anyone read the OP? He said he had tried a repair install. It
didn't work. Before the repair it would reboot itself. After the repair he
got the BSOD. If the repair install doesn't work it may be worthwhile
trying it once more but then a full clean install is the next option. I
don't think anyone recommended a full install as the first step after
installing a motherboard.

Kerry Brown
KDB Systems

Kerry:
You're absolutely correct about the OP's statement concerning the failed
Repair attempt. But the thread had subsequently evolved into a rather
contentious argument over the question as to whether a fresh install of the
XP OS was necessary following a motherboard change or whether a Repair
install was the desired route at that point. And that's what we were
discussing (arguing about?). And it is indeed a topic worth discussing
because of the misinformation and outright distortion one frequently comes
across in this and other newsgroups concerning this subject.
Anna

 

[Tom]

You're really showing your ignorance - you are not in "Windows" when you
press F6 to install drivers during the initial setup, before Windows
launches.

LOL, OK, then remove the disk, and put in the proper drivers from another
disk (or source) since the XP disk doesn't have them, and there is no floppy
drive (me thinks youre using older hardware and OSes, sicne this requires
Floppy drives). Using F6 is for specific OEM drivers for SCSI, IDE and RAID
controller setups, not for chipset drivers that HAVE TO BE INSTALLED WHILE
IN WINDOWS.. this (chipset) is your contention, not mine.

YOU CANNOT INSTALL CHIPSET DRIVERS WHILE NOT IN WINDOWS!!!!!!!

ftp://aiedownload.intel.com/df-support/5916/ENG/readme_XP_2K.txt

 

[Leythos]

LOL, OK, then remove the disk, and put in the proper drivers from another
disk (or source) since the XP disk doesn't have them, and there is no floppy
drive (me thinks youre using older hardware and OSes, sicne this requires
Floppy drives). Using F6 is for specific OEM drivers for SCSI, IDE and RAID
controller setups, not for chipset drivers that HAVE TO BE INSTALLED WHILE
IN WINDOWS.. this (chipset) is your contention, not mine.

YOU CANNOT INSTALL CHIPSET DRIVERS WHILE NOT IN WINDOWS!!!!!!!

Just what do you call those drivers installed to support the onboard
chipset devices before you even complete the installation of Windows?

I don't recall being asked for any additional drivers for my SCSI cards,
my SATA controllers, etc... once I loaded them during the install of
windows before Windows booted.

 

[Anna]

Anna - have you ever experienced a repair that didn't get the computer
back up and running? I have.

Leythos:
This is fast becoming (nay, it already has become!) "the theatre of the
absurd". Of course I've experienced a Repair installation that failed. No
doubt thousands upon thousands of XP users have also experienced a failed
Repair install. That's not the question and I suspect you know that. The
point is that you try it, I say try it!, before going through the trauma of
a fresh install of the OS on a reformatted hard drive. In most cases the
Repair install will work, i.e., you'll be able to boot to a working drive.
What in heaven's name is the harm of trying this? If it doesn't work, we go
to Plan B, no?
Anna

 

[Kerry Brown]

This is fast becoming (nay, it already has become!) "the theatre of the
absurd". Of course I've experienced a Repair installation that failed. No
doubt thousands upon thousands of XP users have also experienced a failed
Repair install.

LOL it is becoming absurd. A simple question turns into a bunch of experts
aguing over who has done the most motherboard upgrades while agreeing on the
fact that a repair install doesn't always work. Maybe we should all be out
installing motherboards

Cheers,
Kerry Brown
KDB Systems

 

[Leythos]

This is fast becoming (nay, it already has become!) "the theatre of the
absurd". Of course I've experienced a Repair installation that failed. No
doubt thousands upon thousands of XP users have also experienced a failed
Repair install. That's not the question and I suspect you know that. The
point is that you try it, I say try it!, before going through the trauma of
a fresh install of the OS on a reformatted hard drive. In most cases the
Repair install will work, i.e., you'll be able to boot to a working drive.
What in heaven's name is the harm of trying this? If it doesn't work, we go
to Plan B, no?

Anna, I never advocated doing a wipe/reinstall as the first step, in fact,
I read the users post where he stated that he had already tried it and
failed. I also said that in many cases where a motherboard is changed the
only way to get it working is to wipe/reinstall. Notice that I still don't
and didn't advocate doing a wipe/reinstall as a first step, not even a
second, I just stated that it sometimes happens that you have to do it
that way.

 

[Tom]

Just what do you call those drivers installed to support the onboard
chipset devices before you even complete the installation of Windows?

I don't recall being asked for any additional drivers for my SCSI cards,
my SATA controllers, etc... once I loaded them during the install of
windows before Windows booted.

Oh Dear! I think you just read what you want to read, but this is the last
I'll hit on it. Windows installs default drivers for the chipset, and it is
up to the user to update after installing Windows, You made a claim where
one may not be able to use windows without those chipsets installed. I tried
telling your deafness that you have to be in Windows to update, or install
drivers that are newer, as you suggested may need to be done with a new
MOBO, or Window may not work. I am not going to go over the fact that is
what you said, and now you change it up to cover the gormless person that
you are.

 

[Leythos]

I am not going to go over the fact that is what you said, and now you
change it up to cover the gormless person that you are.

That's because what I said wasn't wrong, I' have not changed anything I
said, you just assumed more than what I said. You know, if you were not
such as ass you might be easier to follow.

 

[Marty]

Before I did the repair I did a fresh install of XP on my new
motherboard to make sure that XP did recognize my configuration and it
did. I at a loss as to why repair did not work. If I had more time to
play I would do as follows -

1) Ghost my current configuration
2) "Uninstall" all my devices via device manager
3) Shutdown and Ghost configuration (I have 2 spare drives that I use
for Ghost (backup) purposes which I alternate)
3) Swap motherboards
4) Do a repair instalation

If that works then my backup stratergy would be as follows -

1) Ghost current configuration
2) "Uninstall" all my devices via device manager
3) Shutdown and Ghost configuration
4) Reload via Ghost configuration from step #1

This way I have two backups - one for a restore of current
configuration - and another in case of a motherboard failure or system
upgrade

 

[Trent©]

Anna, I never advocated doing a wipe/reinstall as the first step, in fact,
I read the users post where he stated that he had already tried it and
failed. I also said that in many cases where a motherboard is changed the
only way to get it working is to wipe/reinstall. Notice that I still don't
and didn't advocate doing a wipe/reinstall as a first step, not even a
second, I just stated that it sometimes happens that you have to do it
that way.

And that's absolutely false. I've never had a repair install NOT
work. Sure, sometimes you hafta make changes in the BIOS first...or
even boot from the boot disk....but they ALWAYS work.

For someone who has upgraded since 3.1, doing a fresh install would
pretty much be a death sentence!


Have a nice one...

Trent

Budweiser: Helping ugly people have sex since 1876!

 

[Leythos]

And that's absolutely false. I've never had a repair install NOT
work. Sure, sometimes you hafta make changes in the BIOS first...or
even boot from the boot disk....but they ALWAYS work.

In my experience that has not been true in every case.

For someone who has upgraded since 3.1, doing a fresh install would
pretty much be a death sentence!

If you're still running a machine that you upgraded from 3.1 you should
consider a fresh install if just to get rid of all the left over crap.

How would a fresh install be a death sentence?

 

[Trent©]

In my experience that has not been true in every case.


If you're still running a machine that you upgraded from 3.1 you should
consider a fresh install if just to get rid of all the left over crap.

How would a fresh install be a death sentence?

You'd lose all the old programs that you installed from day 1. That's
the main PURPOSE of an upgrade...to keep all the present programs
intact and running.


Have a nice one...

Trent

Budweiser: Helping ugly people have sex since 1876!