Re: Catch 22 - Activation vs Blue Screen
- From: Alias <iamalias@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 21 Jun 2008 12:45:52 +0200
tru wrote:
Did you read this part of the kb article?
http://support.microsoft.com/kb/824125/en-us
Users who run a Microsoft Original Equipment Manufacturer (OEM) operating
system may upgrade or replace most of the hardware components on the
computer and still maintain the license for the original Microsoft OEM
operating system software provided by the OEM, with the exception of an
upgrade or a replacement of the motherboard. An upgrade or a replacement of
the motherboard is considered to create a new personal computer. Therefore,
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 is created, and a new operating system license
is required. If the motherboard is replaced because of a defect, the user
does not need to acquire a new operating system license for the computer.
The motherboard replacement must be the same make and model, or the same
manufacturer's replacement or equivalent, as defined by that manufacturer's
warranty. 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
computer manufacturer. The EULA relates only to rights for that software as
installed on that particular computer. The System Builder is required to
support the software on that individual computer.
Understanding that end-users, over time, upgrade their computers with
different components, Microsoft views the CPU as the one remaining base
component that still defines that original computer. Because the motherboard
contains the CPU, when the motherboard is replaced for reasons other than
defect, a new computer is essentially created. Therefore, the original OEM
cannot be expected to support this new computer that they did not
manufacture.
The licensing rules do not apply to non-OEM Microsoft operating systems.
They don't apply to generic OEM licenses either. The ONLY EULA one has to abide by is the one that comes with the license, not something MS made up after the fact.
Alias
.
"Chris White" <no@xxxxxxx> wrote in message
news:eviFSl00IHA.2084@xxxxxxxxxxxxxxxxxxxxxxx
I posted on my problem a few days ago, but I've started a new thread sinceMode.
the circumstanses have changed a bit. If I find a solution I will post it
to both threads.
I put a new motherboard/CPU/memory/OnboardGPU in an Emachines computer.
When I booted it Blue Screened. I went to Safe Mode and installed the new
drivers(I did not remove the old drivers first and I think this was my
problem).
I've done a Repair, but still Blue Screening. And when I try to boot to
Safe Mode, it tells me I have to Activate and I cannot do that in Safe
There are no BIOS updates.of
Is there something I can do with the Recovery Console to try and get ridthe old drivers?
I am missing some needed CD's with applications that are used.
TIA
- Follow-Ups:
- Re: Catch 22 - Activation vs Blue Screen
- From: Daave
- Re: Catch 22 - Activation vs Blue Screen
- References:
- Catch 22 - Activation vs Blue Screen
- From: Chris White
- Re: Catch 22 - Activation vs Blue Screen
- From: tru
- Catch 22 - Activation vs Blue Screen
- Prev by Date: Re: KB899589 failed to instal
- Next by Date: Re: Catch 22 - Activation vs Blue Screen
- Previous by thread: Re: Catch 22 - Activation vs Blue Screen
- Next by thread: Re: Catch 22 - Activation vs Blue Screen
- Index(es):
Relevant Pages
|
|
