Re: Adding extra HD and worried about XP licence accepting it



Hi,

No, that will be fine. A new hard drive is only a minor change in the
hardware hash used by activation. You may want to consider using the FAST
wizard to backup the existing system for later import into the new
installation. Information:
http://aumha.org/win5/a/fast.htm

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"Debbie" <Debbie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37930B9D-16F3-44A9-99D4-9B728DDA706B@xxxxxxxxxxxxxxxx
>I bought a new 200 gig HD and would like to intall in my PC. I am running
>XP
> Home on Intel Celeron 2.6, 512 Ram, 80 gig HD. This system I bought about
> two years ago with XP pre-installed (from MDG in Canada)
>
> I have been reading up on OEM licences, which I have, and now am worried
> that maybe if I add this HD to my sytem MS will reject my licence. How
> can I
> tell for sure? I wanted to put the OS on the new drive and use the 80 as
> backup.
>
> I copied some info I was reading on below which I got from
> http://aumha.org/win5/a/wpa.htm
>
>
> OEM versions
> Restrictions of specific license types may limit the foregoing. OEM
> versions
> of Windows XP are licensed together with the hardware with which they are
> purchased, as an entity, and such a copy may not be moved to a different
> computer. Also, other specific license types (e.g., Academic licenses) are
> handled in different ways. These arenâ??t a WPA issue per se, but rather
> an
> issue of the license for that purchase, and therefore outside the scope of
> this discussion of WPA.
>
> There are two versions of OEM Windows XP systems. One can be purchased
> separately, with qualifying subsidiary hardware, and installed with that
> hardware to an existing machine, to which it becomes bound. The software
> may
> be reinstalled and reactivated indefinitely as with a retail system as
> long
> as it is still on the original machine. It may not be transferred to a
> different computer. It is activated as described above, but if it were
> installed to hardware seen as not substantially the same, the activation
> would be refused as falling outside the license.
>
>
> ---the above is what I believe I have, can I add extra hardware and still
> use my Win XP or will I have to purchase XP once again? (motherboard,
> bios,
> etc has not been changed) Thanks for any help.
>


.



Relevant Pages

  • Re: Differences between Windows Xp professional and Windos Xp Media Ce
    ... There was a disclaimer on it but no signs of hardware. ... I cannot speak for eBuyer but I recently purchased a part that was OEM only ... Microsoft offers our Windows opertaing system for general retail sale or ... license usage rights etc. ...
    (microsoft.public.windowsxp.general)
  • Re: OEM license
    ... The original Microsoft OEM operating system software cannot be ... Hardware Purchasers. ... The End User License Agreement for OEM software, ...
    (microsoft.public.windowsxp.general)
  • Re: Disaster Recovery & OEM Software
    ... point purchasing server software OEM because of this reason. ... I am now wondering what the point of OEM software is as far as servers ... You can transfer the license to another person if you ... > transfer the hardware with it, but you can't transfer the license to ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding extra HD and worried about XP licence accepting it
    ... have an OEM version, and it wasn't bothered by the change one bit. ... > Restrictions of specific license types may limit the foregoing. ... > of Windows XP are licensed together with the hardware with which they are ... > use my Win XP or will I have to purchase XP once again? ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: OEM licencing and virtualization
    ... A SB can supply COEM client OS on solid server hardware. ... Open (and the original poster was saying 2 OEM s/w!). ... license was supplied? ... Except the scenario is also installing SBS and then installing the OEM ...
    (microsoft.public.windows.server.sbs)