Archived from groups: microsoft.public.windowsxp.help_and_support (
More info?)
"Ottar Tverberg" wrote:
> Sorry for asking such general question, but I'm fearly new to XP issues...
>
> I am about to change to a more modern motherboard to go with my Athlon XP
> CPU..
> The new mobo supports serial ata disks so I will change boot disk too..
>
> I now have XP Pro on the machine, but will preferably make a new clean
> install on the new HD.
> Is this possible without getting problems with the activation of XP, as
> there is less than 120days since I installed XP on the machine..?
>
> Should I install the new MOBO with existing HD first, reactivate, and then
> make a clean install on the new HD?
> Can I use XP backup to move all programs to the new hd and change to boot
> from the new hd afterwards?
>
> regards
> Ottar Tverberg
>
> --
> Sendt med M2 - Operas revolusjonerende e-postprogram:
>
http://www.opera.com/m2/
Ottar,
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 that particular
PC. The System Builder is required to support 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.
This info is related ONLY for MIcrosoft Oem License and doesn't affect the
Retail Version FPP
Hope this info can help you
>