"Will Denny" <willdenny@mvps.org> wrote in message
news:%23019NCKDGHA.1676@TK2MSFTNGP09.phx.gbl...
> Hi
>
> Please try the following article:
>
> "Windows Product Activation (WPA) on Windows XP"
> http://aumha.org/win5/a/wpa.htm
>
> --
>
>
> Will Denny
> MS MVP Windows Shell/User
> Please reply to the News Groups

Thanks. I'd read a previous version of that very informative page some time
ago, and I appreciate the heads-up to the latest revision.

O.G.

Thanks!

O.G.

"Gerry Cornell" <gcjc@tenretnitb.com> wrote in message
news:Oxw4hEMDGHA.3920@tk2msftngp13.phx.gbl...
> DL
>
> You're on the ball. I meant the opposite, namely
> not problematic. Thanks for the correction.
>
> --
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
>
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> "DL" <dl@spoofmail.nothere> wrote in message
> news:ejRvHOKDGHA.2036@TK2MSFTNGP14.phx.gbl...
>>I dont think you mean this;
>>> Hard drives are
>>> problematic
>>> when it comes to compatibility.
>>
>>
>
>

"Anna" <myname@myisp.net> wrote in message
news:Ogh7O5KDGHA.628@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

Anna, thanks very much for all the info. I'll certainly try it first without
the Repair install.

O.G.

Old Geezer wrote:
> I am planning on putting a new motherboard in this Windows XP system as the
> present one has various problems. I built this system a year and a half ago
> with an OEM version of WinXP, purchased with a new hard drive. So as I
> understand the EULA, the hard drive is the part that this software is "tied"
> to. That's fine with me, since it's just the motherboard that I want to
> change anyway.
>


The OEM license, once installed, becomes tied to the entire
computer, as a unit. It doesn't matter with which component it was
originally purchased. This is explained in the OEM EULA.

According to its EULA, an OEM license may not be transferred from one
distinct PC to another PC. Nothing is said about prohibiting one from
repairing or upgrading the PC on which an OEM license is installed.

Now, some people believe that the motherboard is the key component
that defines the "original computer," but the OEM EULA does not make any
such distinction. Others have said that one could successfully argue
that it's the PC's case that is the deciding component, as that is where
one is instructed to affix the OEM CoA label w/Product Key. Again, the
EULA does not specifically define any single component as the computer.
Licensed Microsoft Systems Builders, who are allowed to distribute OEM
licenses with computers they sell, are contractually obligated to
"define" the computer as the motherboard, but this limitation/definition
can't be applied to the end user until the EULA is re-written.

Microsoft has, to date, been very careful _not_ publicly to define
when an incrementally upgraded computer ceases to be the original
computer. The closest I've ever seen a Microsoft employee come to this
definition (in a public forum) is to tell the person making the inquiry
to consult the PC's manufacturer. As the OEM license's support is
solely the responsibility of said manufacturer, they should determine
what sort of hardware changes to allow before the warranty and support
agreements are voided. To paraphrase: An incrementally upgraded
computer ceases to be the original computer, as pertains to the OEM
EULA, only when the *OEM* says it's a different computer. If you've
built the system yourself, and used a generic OEM CD, then _you_ are the
"OEM," and _you_ get to decide when you'll no longer support your product.


> I presume this will be enough of a change to mean re-activating Windows?
>

Oh, yes, and then some.


> There have been countless updates and upgrades to Windows itself and various
> other software (ISP, antivirus, security, etc.) on the system over that year
> and a half, and I hate to do all that all over again, so I am wondering if
> there's any reason I can't just change the motherboard and keep the existing
> hard drive as is, rather than doing a reinstall. The present board has a VIA
> chipset and the new one will also, so I should think just a motherboard
> drivers update would be all that's necessary, if even that.
>


Normally, and assuming a retail license (many OEM installations are
BIOS-locked to a specific chipset and therefore not transferable to a
new motherboard - check yours before starting), unless the new
motherboard is virtually identical (same chipset, same IDE controllers,
same BIOS version, etc.) to the one on which the WinXP installation was
originally performed, you'll need to perform a repair (a.k.a. in-place
upgrade) installation, at the very least:

How to Perform an In-Place Upgrade of Windows XP
http://support.microsoft.com/directo...;EN-US;Q315341

The "why" is quite simple, really, and has nothing to do with
licensing issues, per se; it's a purely technical matter, at this point.
You've pulled the proverbial hardware rug out from under the OS. (If
you don't like -- or get -- the rug analogy, think of it as picking up a
Cape Cod style home and then setting it down onto a Ranch style
foundation. It just isn't going to fit.) WinXP, like Win2K before it,
is not nearly as "promiscuous" as Win9x when it comes to accepting any
old hardware configuration you throw at it. On installation it
"tailors" itself to the specific hardware found. This is one of the
reasons that the entire WinNT/2K/XP OS family is so much more stable
than the Win9x group.

As always when undertaking such a significant change, back up any
important data before starting.

This will also probably require re-activation, unless you have a
Volume Licensed version of WinXP Pro installed. If it's been more than
120 days since you last activated that specific Product Key, you'll most
likely be able to activate via the Internet without problem. If it's
been less, you might have to make a 5 minute phone call.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH

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

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 Stevens wrote:

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

Since you've had that happen, I bow to your experience. It hasn't been
mine, but I have deep respect for you and your knowledge. Old Geezer,
do as Mr. Stevens says and do a Repair Install.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

In news:O%23wtj4ODGHA.1028@TK2MSFTNGP11.phx.gbl,
Malke <notreally@invalid.invalid> replied with a ;-)
> Michael Stevens wrote:
>
>>
>> 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
>
> Since you've had that happen, I bow to your experience. It hasn't been
> mine, but I have deep respect for you and your knowledge. Old Geezer,
> do as Mr. Stevens says and do a Repair Install.
>
> Malke

Malke,
Thanks for the compliment. From you I am honored.

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

> 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

"Michael Stevens" <mstevens@bogusmvps.org> wrote in message
news:ehQmFfODGHA.2320@TK2MSFTNGP11.phx.gbl...
> In news:Ogh7O5KDGHA.628@TK2MSFTNGP14.phx.gbl,
> Anna <myname@myisp.net> replied with a ;-)
[ . . . ]
>
> 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.

Actually I have already made a Ghost image of this drive just to be on the
safe side.


> 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

Thanks for that link on moving XP. That looks like just what I need to know,
and I will read it carefully before proceeding.

O.G.

In news:et1fKJPDGHA.628@TK2MSFTNGP14.phx.gbl,
Anna <myname@myisp.net> replied with a ;-)
>> 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
Anna,

That is what I have experienced and at one point a couple years ago there
were numerous posts that experienced the repair install option not being
available after a failed initial boot.
Once when this happened to me, I replaced the old motherboard and hardware,
rebooted the hard drive. XP booted right up and when I swapped the
motherboards and hardware the option to repair install was available.
I took this as pretty good indicator that booting without the repair install
was the cause of the option to repair not available.
That is why I suggest doing the repair install before first boot. I add that
I would not attempt the boot before repair unless I have a current backup
image.
--
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