New OS With New Motherboard?

By mraftice ·
Am I correct that if you replace the motherboard on a machine that has a legally licensed copy of Windows XP that you have to buy another license because Microsoft considers it a "New Machine?"

This conversation is currently closed to new comments.

90 total posts (Page 9 of 9)   Prev   07 | 08 | 09
| Thread display: Collapse - | Expand +

All Answers

Collapse -

You will need to read

by nentech In reply to Your answer is not releva ...

This document on the microsoft website

Before we have any more discussion

I understand what you say

But Microsoft are bars**eds

When it comes to the OEM License racket

It appeared that you had not read the posts of other people in this discussion

Cheers from me

Collapse -

Let's all jump in without reading anybody else's comments first!

by RobPatten In reply to You will need to read

I agree completely, DigitalAI.

Unfortunately there seems to be an influx of responses recently from people who have not read the rest of the thread before they decide to jump in with their take on the situation.

People are very quick to base their comments on their previous experiences, which is fine, but the main difference here is that OEM licensing works differently and is much more restrictive, because it has been sold at usually around half the price of a retail copy, the main purpose being so that PC manufacurers can "bundle" the software with their computers making the price attractive compared to a consumer buying a bare computer and a full retail copy of the software.

As the discussion continues, we have not even heard anything back from the person posting the original question. We have no idea if he has a retail or OEM copy of XP. We have no idea if his motherboard is faulty or whether he wants to upgrade. We can only speculate and try to cover as many scenarios as possible in order to answer his question fully.

I think this bandwagon is now getting full.

Collapse -

I dont mind

by nentech In reply to Let's all jump in without ...

If some one jumps in

I may just point them to the posts they may find interesting or start a discussion

But natomega's first line in his post

?It appears that many people have jumped on this issue. However I have not read One relevant correct Answer.?

Was if nothing else rude

I would expect better from a IT Department Manager

So nice know someone thinks everybody else was wasting their time.

I have not always read all the posts in a discussion
But those were the Linux verses windows ones

They just go on and on and on
Deeper and deeper and I get tired of looking for something of real value

Collapse -

It is not always necessary

by RobPatten In reply to I dont mind

I quite agree, it is not always necessary to read an entire thread. However if he had even skimmed through a couple or looked over the subject lines before posting it would have made him look a bit less arrogant in assuming that nobody else had hit the nail on the head.

The fact is there is no definitive "right answer" here because we do not have enough information from the person who asked the original question.

However, there have been many excellent and accurate posts, some more relevant than others to the discussion.

Unfortunately there have also been, in the last few days, a number of people posting thinking they can "re-invent the wheel".

Before I jump in I at least make a bit of an effort to make sure somebody hasn't already made the same point as me.

Windows vs Linux... bores me to tears. AMD vs Intel... I don't care. Different people have different preferences and different needs. One solution does not fit all.

A couple of times on this thread I have sensed a post trying to spark a "you wouldn't have this problem with Linux" debate. Maybe you wouldn't, but it does not help answer the question that has been asked. I was glad to see that nobody rose to the bait anyway!

Collapse -

Intel that co is evil

by nentech In reply to I dont mind

How dare you mention that name

Hang on o dear
Never mind I was thinking of somthing else

Collapse -

You clearly have not read the other posts

by RobPatten In reply to New OS With New Motherboa ...

In fact, as DigitalAI has said, it doesn't even look like you read the original question properly, which has in fact been discussed by a number of people in this thread whose comments have been much more "relevant" and "correct" than yours.

What you state is correct from a practical viewpoint with regard to motherboard chipsets.

However the question related to licensing, rather than the practical side of a motherboard change.

Indeed you can re-activate and tell Microsoft you have upgraded your hardware. For retail copies of XP this is fine. The difference is with OEM copies (which has also been discussed at great length which you do not seem to have noticed) where you are only allowed to replace a motherboard if the original is defective.

Collapse -

7 items may be changed

by Borgesen In reply to New OS With New Motherboa ...

When MS launched the new Licensing program, I asked a MS certified retailer here in Denmark about the OEM license, where the license is tied to one single machine. I asked, "What is 'a machine', and when is there room for upgrades?"

I tried to put the case to the test, and finally received an answer (thou they would not give it to me in writing) that the machine was still considered an original until you changed / replaced / upgraded "electrified" component no. 7. I tried further to get a description of "what is a component" thinking of parts like "Motherboard/BIOS" / "CPU/Fan" / "Case Airflow Fan(s)" etc. but they finally gave up answering my questions, settling for "We will have to see, when the problem occurs".

Collapse -

My experience in replacing MOBOs

by ozi Eagle In reply to New OS With New Motherboa ...


I have had several mobos go belly up. I make sure that any replacement mobo (with cpu, RAM) has the same chip set as the original mobo, ie VIA, SIS etc. I have found that the drivers are close enough for the machine to boot into XP and then just load the new mobo drivers. I can't recall any need to re- activate.

Also there was a thread some time ago that explained how to avoid re-activation, to do with the wpa.dbl and wpa.bak files.


Edited for spelling

Collapse -

why no deactivation after new MOBO

by rtroy56 In reply to My experience in replacin ...

The problem of needing to reactivate XP after changing a BIOS (and obviously changing a MOBO changes the BIOS) is ONLY for OEM PREACTIVATED XP. In these PC's XP has a link to the OEM BIOS that is broken when the bios and/or mobo is replaced.

Back to Microsoft Forum
90 total posts (Page 9 of 9)   Prev   07 | 08 | 09

Related Discussions

Related Forums