Catch 22 - Activation vs Blue Screen

C

Chris White

I posted on my problem a few days ago, but I've started a new thread since
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 Mode.

There are no BIOS updates.

Is there something I can do with the Recovery Console to try and get rid of
the old drivers?

I am missing some needed CD's with applications that are used.

TIA
 
T

tru

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.
 
G

GHalleck

Chris said:
I posted on my problem a few days ago, but I've started a new thread since
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 Mode.

There are no BIOS updates.

Is there something I can do with the Recovery Console to try and get rid of
the old drivers?

I am missing some needed CD's with applications that are used.

TIA

Time for a full disclosure. What version or variant of Windows XP
was originally installed on the hard drive? Retail Microsoft? OEM
Microsoft Windows XP for new machines without an OS? Or E-Machines
branded Windows XP?
 
A

Alias

tru said:
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
 
A

Alias

Chris said:
I posted on my problem a few days ago, but I've started a new thread since
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 Mode.

There are no BIOS updates.

Is there something I can do with the Recovery Console to try and get rid of
the old drivers?

I am missing some needed CD's with applications that are used.

TIA

Go back into Safe Mode and remove all the drivers. Reboot into normal
mode and reinstall the drivers.

Alias
 
C

Chris White

Alias said:
Go back into Safe Mode and remove all the drivers. Reboot into normal mode
and reinstall the drivers.

Alias

I cannot get into Safe Mode, it says I have to boot regular and activate. I
cannot boot regular and activate because it blue screens. Thus my Catch 22.
I WANT to activate. The motherboard died and I had to replace the whole
guts of the computer.

I am not worried about licensing as I've done this a couple of times with
MS.

I'm trying to not do a complete reinstall as this is a relatively new
computer with a clean install of some applications that I do not a have a
recovery CD for.

Is there a way to remove offending drivers(I'm suspecting the video driver)
with Recovery Console or some other method?
 
D

Daave

Alias said:
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 is absolutely correct.

From the EULA:

"The SOFTWARE is licensed with the COMPUTER as a single
integrated product and may only be used with the COMPUTER."

Nowhere in the EULA does it state that 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."

Bottom line: Microsoft stating this addendum in a KB article after the
fact does not alter the EULA one iota.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top