> In news:Ogh7O5KDGHA.628@TK2MSFTNGP14.phx.gbl,
> Anna <myname@myisp.net> replied with a ;-)
>> "Old Geezer" <nowhere@all.net> wrote in message
>> news:ej3aw6JDGHA.3140@TK2MSFTNGP14.phx.gbl...
>> O.G.
>> I see you've received a number of responses to your query but I'm not
>> sure they've been totally responsive to the issue you raise, so let
>> me give you my experience...
>>
>> It's a crapshoot at best as to whether you'll even be required to
>> re:activate the system following installation of your new motherboard,
>> although there's a strong likelihood that activation *will* be
>> necessary. However, we have encountered a number of instances,
>> similar to your situation, where the activation process was not
>> required.
>> In other instances where activation *was* necessary, in some cases it
>> was automatically accomplished without further ado, and in other
>> instances the telephone process involving speaking to a MS rep was
>> necessary. After explaining to the rep the need for a motherboard
>> change to replace a defective one, in every instance I'm acquainted
>> with, the system was activated. I'm unaware of any instance where
>> activation was refused under these circumstances.
>>
>> Now as to the motherboard change itself...
>>
>> It is likely, but not necessarily absolute, that you will need to run
>> a Repair install following the motherboard change as Rock has
>> indicated. And, of course, I'm sure you're knowledgeable enough to
>> know that you will have to install the necessary drivers from the
>> motherboard's installation CD after you install the new motherboard.
>> But there is a real possibility that the system will boot *without*
>> the need for a Repair install. Even if the new motherboard is a
>> completely different make/model from the one it's replacing.
>>
>> You needn't fear to try to boot with the new motherboard immediately
>> following its installation (including its drivers). As I've previously
>> indicated, it's worth a try. I note Rock's comment, "Don't try to
>> boot the system first just to see if it works. Run the repair
>> install first." And I've come across other similar admonitions in
>> this situation. I'm at a loss as to why that cautionary note is
>> expressed so frequently. I have performed dozens of motherboard
>> changes in an XP environment and I've never come across a *single*
>> instance where a failed first attempt with a new motherboard caused
>> any subsequent problems with the operating system. I've talked with
>> other technicians about this and they confirm my experience. At worst
>> you'll have to perform a Repair install. Anna
>

"Michael Stevens" <mstevens@bogusmvps.org> wrote in message
news:ehQmFfODGHA.2320@TK2MSFTNGP11.phx.gbl...
> I would only try booting without the repair install if I had a backup
> image, because from feedback and personal experience, if it doesn't boot
> successfully, it may not have the repair option when you run setup.
> Move XP to new hardware.
> http://www.michaelstevenstech.com/moving_xp.html
> --
> Michael Stevens MS-MVP XP
> xpnews@bogusmichaelstevenstech.com
> http://www.michaelstevenstech.com
> For a better newsgroup experience. Setup a newsreader.
> http://www.michaelstevenstech.com/ou...snewreader.htm


Michael:
Cloning the contents of one's HD to another HD is *always* a prudent action
to undertake any time a significant software/hardware change is being made
to the computer. I most certainly agree with that. Personally, and in the
shops in which I've worked, this was *standard* procedure. Unfortunately,
for one reason or another, most PC users (in my experience) are unable or
unwilling to undertake this safety measure. More's the pity.

Do I understand you to say that in your personal experience you've
encountered situations in which following a change of motherboards a failed
initial boot resulted in the Repair option on the user's XP installation CD
not being available to that user because of that failed initial boot? The
inference being that had the user *not* attempted that initial boot, the
Repair option *would* be available to him or her? If that's what you're
saying, my experience certainly differs from yours. I have *never*
encountered a single instance of that cause/effect. And as I mentioned in my
previous post I consulted a number of computer technicians re this issue
(together I would guess we've made hundreds of motherboard changes in an XP
environment) and neither I nor any of them could remember encountering any
problem in undertaking a Repair installation following an initial boot after
a change of motherboards that was attributable to a failed initial boot. It
seems strange that your experience has been so different from ours.
Anna