Motherboard replacement XP Headache

[Leythos]

I went back to my old motherboard, ran Ghost and all is well. My
question is. If I want to, in the future, upgrade my system, what steps
should I do? What backup program would allow a restore to another
install of windows XP without me having to reinstall all my programs? I
was so content with Ghost until I had to use it (granted it worked in
the long run with the reinstallation of my motherboard).

In general, when you change a motherboard and other hardware at the same
time, it's best to do a proper full install. There are ways to do just a
repair/reinstall, but I've always found it better to just do a full
install on the new motherboard.

 

[Marty]

My new DVD burner would not read or recognize CDs so I removed it from
my system for replacement. My system would not boot or even recognize
my hard drives. I removed one of my hard drives and put it into an
external USB case and was able to read it on my laptop. My conclusion
was that I had a motherboard failure. I replaced my Asrock K7S8X with
the Asrock K7VT6 (closest shipping model) and still had the boot
problem. Turned out that my drive was jumpered for Master w/ Slave
present and since I removed the DVD system would not recognize HD so I
jumpered HD to Master w/ no slave present. Now since I has the newer
motherboard installed I figured I would use it.

I ran Ghost to restore my last backup and system would not come up but
continue to reboot. After checking on Google I found out one cannot
expect XP to run after a major hardware change so I did a XP repair
from the XP CDs. The result - BSOD (Blue screen) on boot.

I went back to my old motherboard, ran Ghost and all is well. My
question is. If I want to, in the future, upgrade my system, what steps
should I do? What backup program would allow a restore to another
install of windows XP without me having to reinstall all my programs? I
was so content with Ghost until I had to use it (granted it worked in
the long run with the reinstallation of my motherboard).

 

[Marty]

But how would I recover all my programs and data files? Example, my
outlook express emails etc... Would Windows XP backup/restore survive a
motherboard change? Or is there some third party backup/restore tool
allow a cleaner migration between systems.

Marty

 

[Tom]

But how would I recover all my programs and data files? Example, my
outlook express emails etc... Would Windows XP backup/restore survive a
motherboard change? Or is there some third party backup/restore tool
allow a cleaner migration between systems.

Marty

In the situation you describe, a repair install would save all your things
anyway. But, anything can go wrong (like a power outage during a repair).
Back up anything important to you on CDR(W)s, or to an external drive.

As for Lamethos stating that a full install is better, that is hogwash, and
only reality, if the repair doesn't go correctly. You can always do a repair
install, and if it works, then you are good (except, you will have to get
updates from Windows again, depending on what Service Pack you have with the
install disk). If the repair doesn't work, then you'll have lost only around
15-20 minutes time, and then do a (the) full install.

 

[Kerry Brown]

I do this every day for a living. Invest in a portable hard drive. Copy all
your data to the portable drive, format and install Windows on your main
drive, install programs, copy the data from the portable drive. If you don't
have the knowledge or time to do it, take it to a profesional. Make sure
they understand that you need your data saved and get a firm quote in
advance. If they can't give you firm quote look elsewhere. They don't really
know what they're doing. They will need your Windows and program CD's and
associated keys. If a repair install didn't work this is the only method I
know that works for sure. Depending on the programs are involved I would
charge $75.00 to $200.00. It's usually $100.00 for most configurations.

Kerry Brown
KDB Systems

 

[Galen]

In

I went back to my old motherboard, ran Ghost and all is well. My
question is. If I want to, in the future, upgrade my system, what
steps should I do? What backup program would allow a restore to
another install of windows XP without me having to reinstall all my
programs? I was so content with Ghost until I had to use it (granted
it worked in the long run with the reinstallation of my motherboard).

Take a trip here, scroll down, and you'll find what you want to know:

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21195107.html

Mainly the system preperation bits are what you're interested in.

Galen
--

"My mind rebels at stagnation. Give me problems, give me work, give me
the most abstruse cryptogram or the most intricate analysis, and I am
in my own proper atmosphere. I can dispense then with artificial
stimulants. But I abhor the dull routine of existence. I crave for
mental exaltation." -- Sherlock Holmes

 

[jopo]

It's the old story; backup and backup and backup, 'cause you'll never know
when it's going to strike you.

 

[Trent©]

My new DVD burner would not read or recognize CDs so I removed it from
my system for replacement. My system would not boot or even recognize
my hard drives. I removed one of my hard drives and put it into an
external USB case and was able to read it on my laptop. My conclusion
was that I had a motherboard failure. I replaced my Asrock K7S8X with
the Asrock K7VT6 (closest shipping model) and still had the boot
problem. Turned out that my drive was jumpered for Master w/ Slave
present and since I removed the DVD system would not recognize HD so I
jumpered HD to Master w/ no slave present. Now since I has the newer
motherboard installed I figured I would use it.

I ran Ghost to restore my last backup and system would not come up but
continue to reboot. After checking on Google I found out one cannot
expect XP to run after a major hardware change so I did a XP repair
from the XP CDs. The result - BSOD (Blue screen) on boot.

I went back to my old motherboard, ran Ghost and all is well. My
question is. If I want to, in the future, upgrade my system, what steps
should I do?

Put in the new mainboard...turn on the computer...get into the CD and
do a repair install.

What backup program would allow a restore to another
install of windows XP without me having to reinstall all my programs? I
was so content with Ghost until I had to use it (granted it worked in
the long run with the reinstallation of my motherboard).

When you use Ghost, its best to use it as a cloning program...from
drive to drive.


Have a nice one...

Trent

Budweiser: Helping ugly people have sex since 1876!

 

[Guest]

To perform a clean installation, with the attendant requirement to reinstall
every application [and then all the updates] is an recognised and well
accepted pain in the neck.

The use of an imaged disk [such as Ghost's image] file to 'backup' an entire
System is good practice.

Now if the change of a significant system component [eg Hard Drive] causes
Windows headaches and it won't boot after an image file is restored to a new
HDD, then a QUICK recovery process is to perform a REPAIR install onto the
new HDD. Yes it takes 45 - 60 minutes, but that's all. Not the days to
completely rebuild the system and applications and then copy back all of
one's files.

I don't know why any can suggest otherwise.

 

[Leythos]

In the situation you describe, a repair install would save all your things
anyway. But, anything can go wrong (like a power outage during a repair).
Back up anything important to you on CDR(W)s, or to an external drive.

As for Lamethos stating that a full install is better, that is hogwash, and
only reality, if the repair doesn't go correctly. You can always do a repair
install, and if it works, then you are good (except, you will have to get
updates from Windows again, depending on what Service Pack you have with the
install disk). If the repair doesn't work, then you'll have lost only around
15-20 minutes time, and then do a (the) full install.

Nice, since your scope of installations is very limited you resort to
insults when you can't provide any useful information.

A change in motherboard, while it can be done with a repair/reinstall as I
clearly stated, is best done with a full reinstall due to the number of
changes in drivers and other functions.

As for saving the data, there are many ways to BACKUP a system, and most
people SHOULD be doing that already. There is also the option of
purchasing a second drive and installing the OS on it and then moving the
data from the first drive to the new one.

 

[Kerry Brown]

I don't know why any can suggest otherwise.

Because the OP stated he had already tried a repair install and it didn't
work. 95% of the time a repair install works fine. Occasionally it doesn't
and you have to choose the backup and reinstall route. Granted he had done
an extra step by using Ghost but that shouldn't have affected the outcome.
At least he has his original Ghost image and can get back to where he
started.

Kerry Brown
KDB Systems

 

[Tom]

Nice, since your scope of installations is very limited you resort to
insults when you can't provide any useful information.

Like calling people pirates and thieves!

A change in motherboard, while it can be done with a repair/reinstall as I
clearly stated, is best done with a full reinstall due to the number of
changes in drivers and other functions.

HUH? You make a comment about my "limited scope of installations", that
remark shows that it should pertain to you. A MOBO has nothing to do with
the OS and drivers, only posting, loading the hardware before Windows comes
into play. There are NO drivers that Windows uses for a MOBO, as it can't!

You need to read up what a repair install actually does to the OS when
performed.

 

[Leythos]

HUH? You make a comment about my "limited scope of installations", that
remark shows that it should pertain to you. A MOBO has nothing to do with
the OS and drivers, only posting, loading the hardware before Windows comes
into play. There are NO drivers that Windows uses for a MOBO, as it can't!

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.

You need to read up what a repair install actually does to the OS when
performed.

You should really read up on how Windows talks to components and chip-sets.

 

[Tom]

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.


You should really read up on how Windows talks to components and
chip-sets.

Bwahahahahahahaha! XP doesn't REMOVE those drivers during a repair install,
you idiot! That is why I made the comment about the MOBO. XP redectects
everything that is needed, like an install, only preserving personal
settings and other installed programs. IT WILL NOT REMOVE DRIVERS ALREADY
INSTALLED. One only has to update the system again from WINDOWS UPDATES. I
gave you the effin' link to read what a repair install entails, but (as
usual) you fail to avail yourself to such documentation.

 

[Marty]

Galen, thanks! Even though I was able to get my desktop up and running
by restoring my old motherboard, it is good to know that there is a
fighting chance of doing a restore. I am tempted to do a ghost backup
on another system then a ghost restore of my current system using the
information from the Sysprep articles and see if I can get the other
system up and running. Then I will do a ghost restore to conclude the
excersize.

I have a flakey Sony Vaio Laptop that I will be putting to pasture once
I get my HP AMD 64 laptop delivered. If I can restore my Desktop AMD
system to my Vaio PII 333 laptop - if the restore works (to the extent
that there is a vast difference in hardware - TV Tuner etc), then I
know that all is not lost.

Marty

 

[NobodyMan]

As for Lamethos stating that a full install is better, that is hogwash, and
only reality, if the repair doesn't go correctly. You can always do a repair
install, and if it works, then you are good (except, you will have to get
updates from Windows again, depending on what Service Pack you have with the
install disk). If the repair doesn't work, then you'll have lost only around
15-20 minutes time, and then do a (the) full install.

FYI, you don't ALWAYS have to get all the post sp service packs again.
I installed SP2 the day it came out - and there were several
hotfixes/updates released since then. Two weeks ago I put in a new
mainboard/processor/memory/hard drive upgrade, and did a repair
install using my XP SP2 slipstream CD I made right after SP2 was
released.

Guess how many updates I had to reinstall afterwards: NONE. Every
post SP2 update was still there and functioning.

 

[Anna]

Tom responds to the above...

HUH? You make a comment about my "limited scope of installations", that
remark shows that it should pertain to you. A MOBO has nothing to do with
the OS and drivers, only posting, loading the hardware before Windows
comes > into play. There are NO drivers that Windows uses for a MOBO, as
it can't!

You need to read up what a repair install actually does to the OS when
performed.

And now Leythos...

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.
You should really read up on how Windows talks to components and
chip-sets.

Tom responds...
(Snip)XP doesn't REMOVE those drivers during a repair install,
you idiot! That is why I made the comment about the MOBO. XP redectects
everything that is needed, like an install, only preserving personal
settings and other installed programs. IT WILL NOT REMOVE DRIVERS ALREADY
INSTALLED. One only has to update the system again from WINDOWS UPDATES. I
gave you the effin' link to read what a repair install entails, but (as
usual) you fail to avail yourself to such documentation.


Marty:
I hope you're not too terribly confused by all this but you would do well to
hearken unto Tom. He's right on the mark with the advice he's given you (and
I trust, others). There's absolutely no reason why you shouldn't attempt a
Repair install of XP following a motherboard change (or for that matter, any
major component change that results in a failure to boot following the
change). As a matter of fact in a significant number of cases (based upon my
experience) there is a possibility that notwithstanding the fact that a user
has installed a different make/model motherboard from your current one, your
computer *will* boot, thus avoiding the necessity of a Repair install.
There's no telling beforehand. In a fair minority of cases, our experience
has been that the computer booted after a motherboard change and no Repair
install was necessary.

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.

A Google search of "xp repair install" or some such will point you to a
wealth of information as to performing a Repair install.
Anna

 

[Kerry Brown]

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.

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

 

[Leythos]

Bwahahahahahahaha! XP doesn't REMOVE those drivers during a repair install,
you idiot! That is why I made the comment about the MOBO. XP redectects

Nowhere did I suggest that XP removed the drivers.

everything that is needed, like an install, only preserving personal
settings and other installed programs. IT WILL NOT REMOVE DRIVERS ALREADY
INSTALLED. One only has to update the system again from WINDOWS UPDATES. I
gave you the effin' link to read what a repair install entails, but (as
usual) you fail to avail yourself to such documentation.

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.

 

[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.

Did you miss the part where the OP already stated that the repair didn't
work?