XP Dell OEM = I'm clueless

eoniverse

Senior member
Sep 10, 2004
225
1
81
I'm building a system for my brother.

Trying to save a buck

And so....

When I look around for Windows XP Home or Pro...

I keep coming accross sites selling and people using new Dell OEM XP discs with COA.

I'm pretty sure these discs will install - no problem.

But does anyone know if they will 'validate' with Microsoft Update?
 

sparkyclarky

Platinum Member
May 3, 2002
2,389
0
0
A Dell XP OEM CD cannot be installed on another non-Dell machine without violating the licensing agreement.
 

eoniverse

Senior member
Sep 10, 2004
225
1
81
I understand.

But does anyone know if Windows Update will validate it on a built system?

Hypothetical question
 

pulsedrive

Senior member
Apr 19, 2005
688
0
0
You probably wouldn't even be able to install it. Because I wouldn't put it past dell for that CD to verify a dell mobo and serial number before it will even install. They even did that back in the win 9x days.
 

Deinonych

Senior member
Apr 26, 2003
633
0
76
Originally posted by: pulsedrive
You probably wouldn't even be able to install it. Because I wouldn't put it past dell for that CD to verify a dell mobo and serial number before it will even install. They even did that back in the win 9x days.


Yep. If you don't have a Dell system, don't bother with the Dell-specific XP builds. If you want to save a buck, get the standard OEM version from NewEgg. Note that the license is non-transferable (i.e. once you load it on a system, it becomes bound to that system and can't be installed on another).
 

eoniverse

Senior member
Sep 10, 2004
225
1
81
Does that mean that as I switch out parts in the system... and eventually/probably switch the motherboard... I'll have to buy another copy of XP?

Even if it's only in a single system?

So...

what if I build the PC for my niece -who is in college.

Am I allowed to purchase the an academic O/S and install it? Are there any functional limitations on an academic version vs retail or OEM retail?
 

ITJunkie

Platinum Member
Apr 17, 2003
2,512
0
76
www.techange.com
Originally posted by: eoniverse
Does that mean that as I switch out parts in the system... and eventually/probably switch the motherboard... I'll have to buy another copy of XP?

Even if it's only in a single system.

Yes...or call Microsoft and have them activate it over the phone. I think...:confused:
 

Deinonych

Senior member
Apr 26, 2003
633
0
76
Originally posted by: ITJunkie
Yes...or call Microsoft and have them activate it over the phone. I think...:confused:

Actually, if you change out the entire system, they will not let you activate it on a new system. The OEM version is tied to the original system to which it is installed. You may be able to plead with them to allow you to switch, but it's not their policy. The OEM version is meant to be used by manufacturers and system builders as part of a pre-built system. Most places like NewEgg require you to purchase it with hardware as a result.

 

tcsenter

Lifer
Sep 7, 2001
18,905
556
126
In February, Microsoft starting key matching branded OEM copies XP that are automatically activated during installation at the factory (Dell, HP, Gateway, IBM, et. al.). You will have to call Microsoft and answer some questions to activate these again. I don't know what questions they ask.
 

eoniverse

Senior member
Sep 10, 2004
225
1
81
I don't feel comfortable linking to one of them. They are all over the place...

including occasionally in the advertising on this site at the bottom.

Not referring to the 'sign for free software' nonsense.

Use google.

I
 

dew042

Platinum Member
Nov 2, 2000
2,934
0
76
In February, Microsoft starting key matching branded OEM copies XP that are automatically activated during installation at the factory (Dell, HP, Gateway, IBM, et. al.). You will have to call Microsoft and answer some questions to activate these again. I don't know what questions they ask.

If its a legal key all you have to do is call the phone number and the computer voice on the other end will activate it -- no high stress q&a sessions... Done it a hundred times.

You probably wouldn't even be able to install it. Because I wouldn't put it past dell for that CD to verify a dell mobo and serial number before it will even install. They even did that back in the win 9x days.


No -- an OEM cd is NOT tied to the system in any way. The only thing that seperates an HP OEM disc from a Dell one is additional software in the Value Added stuff. I have used Dell CDs for HPs/Compaqs/Sony and vice versa - No probelms.

Can you link to one of these DELL OEM cd's???

http://forums.anandtech.com/messageview...atid=40&threadid=1649854&enterthread=y

dew.

 

Codegen

Banned
Jul 25, 2005
516
0
0
I know my system is a Northern Micro. Changed the vid card, it wouldn't activate anymore. Changed the motherboard (Asus P4B to Chaintech 9VIF1) and it activated :S
 

freethrowtommy

Senior member
Jun 16, 2005
319
0
0
I was going to say... I have my XP disk that came with my Inspiron 8200 and have no problem installing it on my gf's laptop, Compaq. I don't see a problem here...
 

pcgeek11

Lifer
Jun 12, 2005
22,235
4,935
136
Originally posted by: freethrowtommy
I was going to say... I have my XP disk that came with my Inspiron 8200 and have no problem installing it on my gf's laptop, Compaq. I don't see a problem here...

Well other than being illegal it usually isn't a problem. Most of the installs will even pass through the validation check with a warning, (I don't remember the exact verbage) but something to the effect that the CD Key used is from one of the major mfgs, the hardware in your system is not in line with the usual hardware used in the major mfg systems and could cause problems in the future...

pcgeek11

 

eoniverse

Senior member
Sep 10, 2004
225
1
81
I don't know Microsoft validation all that well but that reads like...

as soon as Longhorn is established and most people start using it we will strictly enforce XP validation... and there won't be a big enough uproar for us to change our position.

Originally posted by: pcgeek11
[/i]
Well other than being illegal it usually isn't a problem. Most of the installs will even pass through the validation check with a warning, (I don't remember the exact verbage) but something to the effect that the CD Key used is from one of the major mfgs, the hardware in your system is not in line with the usual hardware used in the major mfg systems and could cause problems in the future...

.

 

Phoenix86

Lifer
May 21, 2003
14,644
10
81
Jesus, if you have to dance around this so much why don't you just download it? :roll:

First off, like it was already said, OEM copies that were sold with other PCs (aka a Dell, HP, <insert OEM> COA) are not kosher to install on other systems. It's not legal according to the licensing terms.

Second, MS *IS* taking steps to prevent this activity, see WGA. Even if you don't care about the legal and moral aspects of it, surely you can appreciate the fact that you will be upset if you can't activate/update because of it 6 months down the road.

The OS is one of the cheaper components of a system given what you probably paid for compared to your CPU or video card. Spend the cash just like you did on those parts.
 

Deinonych

Senior member
Apr 26, 2003
633
0
76
Originally posted by: dew042
No -- an OEM cd is NOT tied to the system in any way. The only thing that seperates an HP OEM disc from a Dell one is additional software in the Value Added stuff. I have used Dell CDs for HPs/Compaqs/Sony and vice versa - No probelms.

I guess it depends on the system, or perhaps they've discontinued the practice. I have an older Dell Precision workstation that came with a W2K CD, and it will only install on a Dell system. I tried installing it on one of my homebrew systems to no avail.
 

eoniverse

Senior member
Sep 10, 2004
225
1
81
I've taken care of my issue.

Just trying to reply to what people have posted here.

There's a big difference in my mind between spending 'a lot more money' on a piece of OEM hardware like a video card but using it in ANY one system as I see fit vs an OEM piece of software full of security holes that is tied to one system from now on because of the new validation process.