D
D.Currie
In (e-mail address removed), Benny Fu wrote:
But none of this answers Dave's question about whether Microsoft considers
changing his motherboard making it a new computer and invalidating his OEM
license.
--
Ken Blake
Please reply to the newsgroup
Well, I was wrong. There is some discussion of this, and it seems that if
the OEM has the mobo under warranty and replaces it -- with any motherboard,
not necessarily the same one -- then it is the same computer. If it's out of
warranty and the end-user replaces it, it is a new computer.
So, if the end-user is the OEM, it is the OEM who decides how long the
warranty is, and what if covers, so it would appear that the OEM-end-user
gets to make the call on whether it's a new system or not.
It's an interesting solution. It protects the big OEMs, as under this
definition, they wouldn't be required to supply a copy of Windows that's
installable on anything other than their own hardware. At the same time,
small OEMs that do custom systems and might not stock replacement
motherboards would not be stuck having to replace the OS if a motherboard
went bad. And home builders can do whatever they want, since they are their
own OEM.
I'd be willing to be this wasn't the original plan, though, because
activation could have easily been tied to the motherboard, and not triggered
by replacement of other parts. And it's not what I heard from Microsoft reps
when XP was being launched.
But none of this answers Dave's question about whether Microsoft considers
changing his motherboard making it a new computer and invalidating his OEM
license.
--
Ken Blake
Please reply to the newsgroup
Well, I was wrong. There is some discussion of this, and it seems that if
the OEM has the mobo under warranty and replaces it -- with any motherboard,
not necessarily the same one -- then it is the same computer. If it's out of
warranty and the end-user replaces it, it is a new computer.
So, if the end-user is the OEM, it is the OEM who decides how long the
warranty is, and what if covers, so it would appear that the OEM-end-user
gets to make the call on whether it's a new system or not.
It's an interesting solution. It protects the big OEMs, as under this
definition, they wouldn't be required to supply a copy of Windows that's
installable on anything other than their own hardware. At the same time,
small OEMs that do custom systems and might not stock replacement
motherboards would not be stuck having to replace the OS if a motherboard
went bad. And home builders can do whatever they want, since they are their
own OEM.
I'd be willing to be this wasn't the original plan, though, because
activation could have easily been tied to the motherboard, and not triggered
by replacement of other parts. And it's not what I heard from Microsoft reps
when XP was being launched.