Date of Activation

[Alias]

Read the link in my post to the OP.
Also read the posts in the various newsgroups about activation.
I am sure you already know at least part of the answer to your question.

What else can trigger it isn't exactly a difficult question. Can you
answer it without being patronizing and supercilious? Referring me to
"do research" after writing:

"That assumes that hardware caused activation.
Your answer is about as helpful as Carey's. There have been other things
that trigger activation so your solution assumes much."

is not very "helpful".

So, if you know, answer it. If you don't, be a man and say so.

Alias

 

[Alias]

Q. "Same computer" - What is the same computer?

A. The same make and model of motherboard. Microsoft defines the
motherboard as being the "heart and soul" of a computer.

Not in my EULA.

Q. "MS would perhaps suggest it's the motherboard. What if that dies and has to be replaced?"

A. If you have a "Retail Version" of Windows XP - no problem.
If you have an "OEM Version" of Windows XP - the license
is no longer valid with a totally different make/model of motherboard.

Lying again, I see. I am convinced you get a vicarious thrill out of
scaring people to buy something they don't need and you should be
ashamed of yourself. And don't copy and paste the url to the password
protected systems builder page because we are talking about an end user
here.

Alias

 

[Uncle Grumpy]

Wrong. Anyone who recently purchased or purchases a new
generic OEM version of Windows XP are now considered
"System Builders" and must abide by the System
Builder's licensing agreement.

As usual, you're fulla shit. Only this time you're dumb enough to keep
digging your hole, even while everyone else is dumping the dirt back in
on your head.

System builders - I once WAS a "ma and pa" system builder - buy OEM
versions of XP in BULK from authorized distributors at a slight
discount. There is nothing wrong with the end user re-installing those
versions of XP on a "new" machine unless they're still using it on the
"old" machine. The disk and its key will work as intended.

When a builder such as HP, Dell, etc. install their OWN OEM versions,
those versions are tied to the original setup - a totally different
situation.

You were an idiot when XP was initially released, and I see little
progress since then. How you were given the MVP title is beyond me.

 

[Carey Frisch [MVP]]

Here's concrete proof from the largest retailer in the world:

Microsoft Windows XP Home Edition OEM Version
http://www.walmart.com/catalog/product.do?product_id=1957319

"This OEM version is intended for system builders only and
cannot be transferred to another PC once it is installed.

The purchaser of this software is required to comply with the terms
of the System Builder license..."

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

"kurttrail"wrote:

| > Q. "Same computer" - What is the same computer?
| >
| > A. The same make and model of motherboard. Microsoft defines the
| > motherboard as being the "heart and soul" of a computer.
|
| Bullsh*t. Nowhere in the EULA is the "same computer" defined.
|
| >
| > Q. "MS would perhaps suggest it's the motherboard. What if that dies
| > and has to be replaced?"
| >
| > A. If you have a "Retail Version" of Windows XP - no problem.
| > If you have an "OEM Version" of Windows XP - the license
| > is no longer valid with a totally different make/model of
| > motherboard.
|
| Those are MS-certified System Builder's rules hidden behind a
| password-protected website. Not applicable to an End User that NEVER
| EVER had the chance to see those BS System Builder's rules, let alone
| ever had a chance to agree or disagree with them.
|
| >
| >
| >> <SNIP>
| >>> But since Windows XP can be reinstalled an unlimited # of times on
| >>> the same computer, activation is not normally a problem.
| >>
| >>
| >> "same computer" - What is the same computer?
| >> If the component parts are changed continually just what is the same
| >> computer?
| >>
| >> Is it?.... Any collection of bits forming a computer within the same
| >> PC case.
| >> This perhaps might be a legal interpretation as after all, MS
| >> require that the product key sticker is attached to the case.
| >>
| >> MS would perhaps suggest it's the motherboard.
| >> What if that dies and has to be replaced?
| >> MS may say - Oh that's ok if replaced with same type.
| >> What if it's a Skt. 370 / PIII combination and due to obsolescence
| >> can't be replaced with same type.
| >>
| >> Seems like a whole can of worms to me.
| >> Does anything in licensing documentation clarify this?
|
| --
| Peace!
| Kurt

 

[Carey Frisch [MVP]]

I guess in your little twisted world, ignorance is bliss....

Here's concrete proof from the largest retailer in the world:

Microsoft Windows XP Home Edition OEM Version
http://www.walmart.com/catalog/product.do?product_id=1957319

"This OEM version is intended for system builders only and
cannot be transferred to another PC once it is installed.

The purchaser of this software is required to comply with the terms
of the System Builder license..."

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Carey Frisch [MVP] wrote:
| > Wrong. Anyone who recently purchased or purchases a new
| > generic OEM version of Windows XP are now considered
| > "System Builders" and must abide by the System
| > Builder's licensing agreement.
|
| As usual, you're fulla shit. Only this time you're dumb enough to keep
| digging your hole, even while everyone else is dumping the dirt back in
| on your head.
|
| System builders - I once WAS a "ma and pa" system builder - buy OEM
| versions of XP in BULK from authorized distributors at a slight
| discount. There is nothing wrong with the end user re-installing those
| versions of XP on a "new" machine unless they're still using it on the
| "old" machine. The disk and its key will work as intended.
|
| When a builder such as HP, Dell, etc. install their OWN OEM versions,
| those versions are tied to the original setup - a totally different
| situation.
|
| You were an idiot when XP was initially released, and I see little
| progress since then. How you were given the MVP title is beyond me.
|

 

[Carey Frisch [MVP]]

Any person who does not possess the mental capacity
of comprehending and adhering to OEM licensing agreements
should only purchase and use a "Retail Version" of Windows XP.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Carey Frisch [MVP] wrote:
| > Q. "Same computer" - What is the same computer?
| >
| > A. The same make and model of motherboard. Microsoft defines the
| > motherboard as being the "heart and soul" of a computer.
|
| Not in my EULA.
|
| >
| > Q. "MS would perhaps suggest it's the motherboard. What if that dies and has to be replaced?"
| >
| > A. If you have a "Retail Version" of Windows XP - no problem.
| > If you have an "OEM Version" of Windows XP - the license
| > is no longer valid with a totally different make/model of motherboard.
| >
|
| Lying again, I see. I am convinced you get a vicarious thrill out of
| scaring people to buy something they don't need and you should be
| ashamed of yourself. And don't copy and paste the url to the password
| protected systems builder page because we are talking about an end user
| here.
|
| Alias

 

[Alias]

I guess in your little twisted world, ignorance is bliss....

Here's concrete proof from the largest retailer in the world:

Microsoft Windows XP Home Edition OEM Version
http://www.walmart.com/catalog/product.do?product_id=1957319

"This OEM version is intended for system builders only and
cannot be transferred to another PC once it is installed.

If it's intended for system builders, why do they sell it to end users?

The purchaser of this software is required to comply with the terms
of the System Builder license..."

Um, no one purchases software but licences, remember? I can show you
many web sites in Spain that retail OEM licences and none of them say
*anything* about system builders or the system builder licence. I would
venture to say that when one buys from Walmart, one does not have to be
a systems builder but someone with cash and cash only. One will not be
given a systems builder contract to sign. All an end user will have is
their EULA that says nothing about a motherboard or a systems builder.

Alias

 

[Alias]

Any person who does not possess the mental capacity
of comprehending and adhering to OEM licensing agreements
should only purchase and use a "Retail Version" of Windows XP.

Now we finally find out why Carey only buys retail versions.

Alias

 

[Guest]

A "clean install" of the operating system...

 

[Alias]

A "clean install" of the operating system...

Very good, Carey, I hadn't thought of that [NOT]. I meant, however, what
can trigger it without doing that, besides a hardware change, of course.

It all comes back to the fact that WPA and WGA will be the bane of MS,
serve no useful purpose and only inconvenience paying customers, not the
crackers and pirates.

It's isn't cool to boot up your computer and be told that, in no
uncertain terms, that if you don't activate you won't be able to use
your computer and, when you go to activate, you're told you're already
activated or you've activated too many times when, all along, you needed
to get an email out that's worth a grand to you and the last thing you
want to do it have to spend the rest of the day messing with WPA or WGA.

"Where do you want to go?" has changed into, "No, sorry, you can't go
there".

Alias

 

[kurttrail]

Here's concrete proof from the largest retailer in the world:

Microsoft Windows XP Home Edition OEM Version
http://www.walmart.com/catalog/product.do?product_id=1957319

"This OEM version is intended for system builders only and
cannot be transferred to another PC once it is installed.

The purchaser of this software is required to comply with the terms
of the System Builder license..."

ROFL! Too bad the System Builders license doesn't mention that your
motherboard is the computer BS either, Carey.



--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity/index.php?showtopic=3
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[R. McCarty]

Uninstalling certain applications will trigger a re-Activation. I've seen
this occur many times. Cannot explain how a Hardware Hash can
change based on installed applications - but it can and does happen.

A "clean install" of the operating system...

Very good, Carey, I hadn't thought of that [NOT]. I meant, however, what
can trigger it without doing that, besides a hardware change, of course.

It all comes back to the fact that WPA and WGA will be the bane of MS,
serve no useful purpose and only inconvenience paying customers, not the
crackers and pirates.

It's isn't cool to boot up your computer and be told that, in no uncertain
terms, that if you don't activate you won't be able to use your computer
and, when you go to activate, you're told you're already activated or
you've activated too many times when, all along, you needed to get an
email out that's worth a grand to you and the last thing you want to do it
have to spend the rest of the day messing with WPA or WGA.

"Where do you want to go?" has changed into, "No, sorry, you can't go
there".

Alias

 

[kurttrail]

Any person who does not possess the mental capacity
of comprehending and adhering to OEM licensing agreements
should only purchase and use a "Retail Version" of Windows XP.

Talking about yourself, Carey? ROFL!



--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity/index.php?showtopic=3
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Carey Frisch [MVP]]

That question is answered everyday in the OEM
System Builder's newsgroup.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| > Here's concrete proof from the largest retailer in the world:
| >
| > Microsoft Windows XP Home Edition OEM Version
| > http://www.walmart.com/catalog/product.do?product_id=1957319
| >
| > "This OEM version is intended for system builders only and
| > cannot be transferred to another PC once it is installed.
| >
| > The purchaser of this software is required to comply with the terms
| > of the System Builder license..."
|
| ROFL! Too bad the System Builders license doesn't mention that your
| motherboard is the computer BS either, Carey.
|
| >
| >
| >>> Q. "Same computer" - What is the same computer?
| >>>
| >>> A. The same make and model of motherboard. Microsoft defines the
| >>> motherboard as being the "heart and soul" of a computer.
| >>
| >> Bullsh*t. Nowhere in the EULA is the "same computer" defined.
| >>
| >>>
| >>> Q. "MS would perhaps suggest it's the motherboard. What if that dies
| >>> and has to be replaced?"
| >>>
| >>> A. If you have a "Retail Version" of Windows XP - no problem.
| >>> If you have an "OEM Version" of Windows XP - the license
| >>> is no longer valid with a totally different make/model of
| >>> motherboard.
| >>
| >> Those are MS-certified System Builder's rules hidden behind a
| >> password-protected website. Not applicable to an End User that NEVER
| >> EVER had the chance to see those BS System Builder's rules, let alone
| >> ever had a chance to agree or disagree with them.
| >>
| >>>
| >>>
| >>>> <SNIP>
| >>>>> But since Windows XP can be reinstalled an unlimited # of times on
| >>>>> the same computer, activation is not normally a problem.
| >>>>
| >>>>
| >>>> "same computer" - What is the same computer?
| >>>> If the component parts are changed continually just what is the
| >>>> same computer?
| >>>>
| >>>> Is it?.... Any collection of bits forming a computer within the
| >>>> same PC case.
| >>>> This perhaps might be a legal interpretation as after all, MS
| >>>> require that the product key sticker is attached to the case.
| >>>>
| >>>> MS would perhaps suggest it's the motherboard.
| >>>> What if that dies and has to be replaced?
| >>>> MS may say - Oh that's ok if replaced with same type.
| >>>> What if it's a Skt. 370 / PIII combination and due to obsolescence
| >>>> can't be replaced with same type.
| >>>>
| >>>> Seems like a whole can of worms to me.
| >>>> Does anything in licensing documentation clarify this?
| >>
| >> --
| >> Peace!
| >> Kurt
|
|
|
| --
| Peace!
| Kurt

 

[Alias]

Uninstalling certain applications will trigger a re-Activation. I've seen
this occur many times. Cannot explain how a Hardware Hash can
change based on installed applications - but it can and does happen.
Cute.

Alias

A "clean install" of the operating system...

Very good, Carey, I hadn't thought of that [NOT]. I meant, however, what
can trigger it without doing that, besides a hardware change, of course.

It all comes back to the fact that WPA and WGA will be the bane of MS,
serve no useful purpose and only inconvenience paying customers, not the
crackers and pirates.

It's isn't cool to boot up your computer and be told that, in no uncertain
terms, that if you don't activate you won't be able to use your computer
and, when you go to activate, you're told you're already activated or
you've activated too many times when, all along, you needed to get an
email out that's worth a grand to you and the last thing you want to do it
have to spend the rest of the day messing with WPA or WGA.

"Where do you want to go?" has changed into, "No, sorry, you can't go
there".

Alias

 

[Alias]

That question is answered everyday in the OEM
System Builder's newsgroup.

I imagine that newsgroup is for, drum roll, system builders? I am not in
the computer business but I do build my own computers. I can change my
motherboard any old time my little heart desires to change it and be
within my OEM licensing rights. What I *can't* do is install it on two
computers and stay within the OEM licensing rights.

Alias

 

[kurttrail]

That question is answered everyday in the OEM
System Builder's newsgroup.

The System Builder License doesn't mention your motherboard is the
computer nonsense.

http://oem.microsoft.com/downloads/public/sblicense/English_SB_License.pdf

Read it and weep!

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity/index.php?showtopic=3
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Carey Frisch [MVP]]

Quoted from Microsoft's System Builder FAQ:

Q. Can a PC with OEM Windows XP have its motherboard upgraded
and keep the same license? What if it was replaced because it was defective?


A. Generally, you may upgrade or replace all of the hardware components on your customer's computer and the end user may maintain
the license for the original Microsoft® OEM operating system software, with the exception of an upgrade or replacement of the
motherboard. An upgrade of the motherboard is considered to result in a "new personal computer" to which Microsoft® OEM operating
system software cannot be transferred from another computer. If the motherboard is upgraded or replaced for reasons other than a
defect, then a new computer has been created and the license of new operating system software is required. If the motherboard is
replaced because it is defective, you do NOT need to acquire a new operating system license for the PC.

The reason for this licensing rule primarily relates to the end-user license agreement (EULA) and the support of the software
covered by that EULA. The EULA is a set of usage rights granted to the end-user by the PC manufacturer and relates only to rights
for that software as installed on for that particular PC. The System Builder is required to support that license the software on
that individual PC. Understanding that end users, over time, upgrade their PC with different components, Microsoft needed to have
one base component "left standing" that would still define that original PC. Since the motherboard contains the CPU and is the
"heart and soul" of the PC, when the motherboard is replaced (for reasons other than defect) a new PC is essentially created. The
original System Builder, therefore, can not be expected to support this new PC that they in effect, did not manufacture."

Ref: https://oem.microsoft.com/script/contentpage.aspx?PageID=553075


--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Carey Frisch [MVP] wrote:
|
| > That question is answered everyday in the OEM
| > System Builder's newsgroup.
|
| The System Builder License doesn't mention your motherboard is the
| computer nonsense.
|
| http://oem.microsoft.com/downloads/public/sblicense/English_SB_License.pdf
|
| Read it and weep!
|
| --
| Peace!
| Kurt

 

[kurttrail]

Quoted from Microsoft's System Builder FAQ:

Q. Can a PC with OEM Windows XP have its motherboard upgraded
and keep the same license? What if it was replaced because it was
defective?


A. Generally, you may upgrade or replace all of the hardware
components on your customer's computer and the end user may maintain
the license for the original Microsoft® OEM operating system
software, with the exception of an upgrade or replacement of the
motherboard. An upgrade of the motherboard is considered to result in
a "new personal computer" to which Microsoft® OEM operating system
software cannot be transferred from another computer. If the
motherboard is upgraded or replaced for reasons other than a defect,
then a new computer has been created and the license of new operating
system software is required. If the motherboard is replaced because
it is defective, you do NOT need to acquire a new operating system
license for the PC.

The reason for this licensing rule primarily relates to the end-user
license agreement (EULA) and the support of the software covered by
that EULA. The EULA is a set of usage rights granted to the end-user
by the PC manufacturer and relates only to rights for that software
as installed on for that particular PC. The System Builder is
required to support that license the software on that individual PC.
Understanding that end users, over time, upgrade their PC with
different components, Microsoft needed to have one base component
"left standing" that would still define that original PC. Since the
motherboard contains the CPU and is the "heart and soul" of the PC,
when the motherboard is replaced (for reasons other than defect) a
new PC is essentially created. The original System Builder,
therefore, can not be expected to support this new PC that they in
effect, did not manufacture."

Ref: https://oem.microsoft.com/script/contentpage.aspx?PageID=553075

ROFL! That takes me to a sign on for MS Partners!

I never agreed to be a MS Partner, so what is behind your
password-protected site for Microsoft Partners is irrelevant!

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity/index.php?showtopic=3
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Carey Frisch [MVP]]

If you do not wish to bother with learning about the
restrictions of an OEM license, then you should not
be posting any "seat-of the-pants" thoughts that are
truly false and misleading.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Carey Frisch [MVP] wrote:
|
| > Quoted from Microsoft's System Builder FAQ:
| >
| > Q. Can a PC with OEM Windows XP have its motherboard upgraded
| > and keep the same license? What if it was replaced because it was
| > defective?
| >
| >
| > A. Generally, you may upgrade or replace all of the hardware
| > components on your customer's computer and the end user may maintain
| > the license for the original Microsoft® OEM operating system
| > software, with the exception of an upgrade or replacement of the
| > motherboard. An upgrade of the motherboard is considered to result in
| > a "new personal computer" to which Microsoft® OEM operating system
| > software cannot be transferred from another computer. If the
| > motherboard is upgraded or replaced for reasons other than a defect,
| > then a new computer has been created and the license of new operating
| > system software is required. If the motherboard is replaced because
| > it is defective, you do NOT need to acquire a new operating system
| > license for the PC.
| >
| > The reason for this licensing rule primarily relates to the end-user
| > license agreement (EULA) and the support of the software covered by
| > that EULA. The EULA is a set of usage rights granted to the end-user
| > by the PC manufacturer and relates only to rights for that software
| > as installed on for that particular PC. The System Builder is
| > required to support that license the software on that individual PC.
| > Understanding that end users, over time, upgrade their PC with
| > different components, Microsoft needed to have one base component
| > "left standing" that would still define that original PC. Since the
| > motherboard contains the CPU and is the "heart and soul" of the PC,
| > when the motherboard is replaced (for reasons other than defect) a
| > new PC is essentially created. The original System Builder,
| > therefore, can not be expected to support this new PC that they in
| > effect, did not manufacture."
| >
| > Ref: https://oem.microsoft.com/script/contentpage.aspx?PageID=553075
| >
|
| ROFL! That takes me to a sign on for MS Partners!
|
| I never agreed to be a MS Partner, so what is behind your
| password-protected site for Microsoft Partners is irrelevant!
|
| --
| Peace!
| Kurt