Associate
- Joined
- 15 Sep 2005
- Posts
- 837
When I upgraded mboard + CPU (and as side-effect network interface) my OEM winXP install considered that too much had changed and it needed reactivating which just took a short phone call where I type a list of nubers windows gave me and an automated system dictated another set back to me which I typed in and voila it was happy again. This behaviour didn't surprise me as from reading up on the MS web site it was what I'd expected - I'd done some research to check that XP would allow me to change mboard/CPU etc first.
One key point that I found was that there are *two* distinct forms of XP OEM
1) The version supplied on the big PC company machines (i.e. Dell, HP, etc) are tied to a key in the BIOS ... on these you can change anything so long as the BIOS is still recognised as being the same ... i.e. on these if you change mboard then you are probably stuck ... I wasn't in this category so have no idea if you can get a reactivation if you do change mboard (I think the webpages do comment that if you have a fault on the mboard then you need to replace with the same mboard)
2) The 2nd OEM version is the one that small system builders would use and which is what places like OC sell ... this one generates a key from the major components of the PC (mboard, CPU, mem, ethernet MAC, HDD id etc) and if more than certain number change within 6 months then the reactivation I used is needed.
I think the fact that there are these two OEM versions of XP with significantly different abilities to upgrade hardware leads reams of dogmatic statements about what you can do with an OEM license that may only apply to a subset of OEM installs.
Situation with Vista may well be similar
One key point that I found was that there are *two* distinct forms of XP OEM
1) The version supplied on the big PC company machines (i.e. Dell, HP, etc) are tied to a key in the BIOS ... on these you can change anything so long as the BIOS is still recognised as being the same ... i.e. on these if you change mboard then you are probably stuck ... I wasn't in this category so have no idea if you can get a reactivation if you do change mboard (I think the webpages do comment that if you have a fault on the mboard then you need to replace with the same mboard)
2) The 2nd OEM version is the one that small system builders would use and which is what places like OC sell ... this one generates a key from the major components of the PC (mboard, CPU, mem, ethernet MAC, HDD id etc) and if more than certain number change within 6 months then the reactivation I used is needed.
I think the fact that there are these two OEM versions of XP with significantly different abilities to upgrade hardware leads reams of dogmatic statements about what you can do with an OEM license that may only apply to a subset of OEM installs.
Situation with Vista may well be similar