OEM XP Home won't work after new mb!

Simple solution-Remove the BIOS chip from the old motherboard and install it
in the new one. If you don't know how to do this yourself, take both boards
to a local computer shop and have them do it for you.

The old BIOS chip will have info Windows needs to boot properly.
Good Luck.

"Jonny" wrote:

> <nicholson.jr.DeleteThis@gmail.com> wrote in message
> news:1156284071.369118.253850@h48g2000cwc.googlegroups.com...
> > My Emachines mb went out so I bought an exact replacement. Now my
> > computer will not boot up. I've done multiple restores, still the same
> > error. My Dad has the same exact computer I've taken my hd and swapped
> > it out with his computer and it works fine. Conclusion, problem is the
> > OEM XP software doesn't like my new mb even though it is technically
> > the same mb. How can I get this to work. I've been told I have to buy
> > a new copy of Windows, but how can this be? I already own a copy of
> > Windows, it came with my computer. I have only replaced a failed part.
> > Does this happen when people upgrade too? Your not allowed to work on
> > your own computer anymore?? I'm very frustrated with this, it's just
> > wrong that every time a part fails on your computer it means Microsoft
> > gets another $100. I cannot believe this is true, but all indications
> > so far are starting to convince me. Please help!!
> >
>
> My guess is the bios checksum is different from your current motherboard.
> Not that unusual. See if you can get the older version from Emachine tech
> help.
> --
> Jonny
>
>
>

Rick the link you gave me says


Warning Do not use the procedure that is described in this article if
your computer has an OEM-installed operating system. The system hive on
OEM installations creates passwords and user accounts that did not
exist previously. If you use the procedure that is described in this
article, you may not be able to log back into the recovery console to
restore the original registry hives.


This is a OEM copy of Windows, do you still think it will work?

Dandy Don where is the BIOS chip? i have access to Electricians, so
tha might be an option.


DandyDon wrote:
> Simple solution-Remove the BIOS chip from the old motherboard and install it
> in the new one. If you don't know how to do this yourself, take both boards
> to a local computer shop and have them do it for you.
>
> The old BIOS chip will have info Windows needs to boot properly.
> Good Luck.
>
> "Jonny" wrote:
>
> > <nicholson.jr DeleteThis @gmail.com> wrote in message
> > news:1156284071.369118.253850@h48g2000cwc.googlegroups.com...
> > > My Emachines mb went out so I bought an exact replacement. Now my
> > > computer will not boot up. I've done multiple restores, still the same
> > > error. My Dad has the same exact computer I've taken my hd and swapped
> > > it out with his computer and it works fine. Conclusion, problem is the
> > > OEM XP software doesn't like my new mb even though it is technically
> > > the same mb. How can I get this to work. I've been told I have to buy
> > > a new copy of Windows, but how can this be? I already own a copy of
> > > Windows, it came with my computer. I have only replaced a failed part.
> > > Does this happen when people upgrade too? Your not allowed to work on
> > > your own computer anymore?? I'm very frustrated with this, it's just
> > > wrong that every time a part fails on your computer it means Microsoft
> > > gets another $100. I cannot believe this is true, but all indications
> > > so far are starting to convince me. Please help!!
> > >
> >
> > My guess is the bios checksum is different from your current motherboard.
> > Not that unusual. See if you can get the older version from Emachine tech
> > help.
> > --
> > Jonny
> >
> >
> >

The Bios chip is a black rectangular chip with the words 'Award, Phoenix, or
AMI on it. It is an EPROM. Take all ESD precautions.

"nicholson.jr@gmail.com" wrote:

> Rick the link you gave me says
>
>
> Warning Do not use the procedure that is described in this article if
> your computer has an OEM-installed operating system. The system hive on
> OEM installations creates passwords and user accounts that did not
> exist previously. If you use the procedure that is described in this
> article, you may not be able to log back into the recovery console to
> restore the original registry hives.
>
>
> This is a OEM copy of Windows, do you still think it will work?
>
> Dandy Don where is the BIOS chip? i have access to Electricians, so
> tha might be an option.
>
>
> DandyDon wrote:
> > Simple solution-Remove the BIOS chip from the old motherboard and install it
> > in the new one. If you don't know how to do this yourself, take both boards
> > to a local computer shop and have them do it for you.
> >
> > The old BIOS chip will have info Windows needs to boot properly.
> > Good Luck.
> >
> > "Jonny" wrote:
> >
> > > <nicholson.jr RemoveThis @gmail.com> wrote in message
> > > news:1156284071.369118.253850@h48g2000cwc.googlegroups.com...
> > > > My Emachines mb went out so I bought an exact replacement. Now my
> > > > computer will not boot up. I've done multiple restores, still the same
> > > > error. My Dad has the same exact computer I've taken my hd and swapped
> > > > it out with his computer and it works fine. Conclusion, problem is the
> > > > OEM XP software doesn't like my new mb even though it is technically
> > > > the same mb. How can I get this to work. I've been told I have to buy
> > > > a new copy of Windows, but how can this be? I already own a copy of
> > > > Windows, it came with my computer. I have only replaced a failed part.
> > > > Does this happen when people upgrade too? Your not allowed to work on
> > > > your own computer anymore?? I'm very frustrated with this, it's just
> > > > wrong that every time a part fails on your computer it means Microsoft
> > > > gets another $100. I cannot believe this is true, but all indications
> > > > so far are starting to convince me. Please help!!
> > > >
> > >
> > > My guess is the bios checksum is different from your current motherboard.
> > > Not that unusual. See if you can get the older version from Emachine tech
> > > help.
> > > --
> > > Jonny
> > >
> > >
> > >
>
>

When you try to load Windows using any option besides LAST CONFIG, any
error messages reported could help. Have you tried to recover via
KB307545?

But then again, does the eMachine's restore CD (I assume 2 or more CDs
actually) boot into a special eMachine restore process? I.e. MS CDs
boot into a setup program allowing more than just installling XP.

It sounds as if the eMachines restore CD fails to properly setup the
registry, or perhaps there is some part of their OEM version of Windows
that actually looks for something in the BIOS for it to even boot. If
the former you just may be able to get it to work, but not without a
ton of work. If the latter, you can ask eMachines for one of their
BIOSes.

If it is a registry problem then one couild install you HDD as a
secondary drive in another PC and load it's registry for modification
("Load Hive"). One needs to know what to fix though.

A retail version of XP will most probably work fine for you. I assume
that the eMachine's restore wiped out your HDD already so don't even
bother with a "Repair Install" and just install as new.

Some OEM restore CDs are nothing like MS retail CDs and will not
install on non-OEM hardware. (Some OEM CDs, like Dell's, are very close
to MS retail and will install, but will ask for a product key which --
for lack of a better term -- needs to be in their OEM "range" or it
will not activate. Some Dell CDs will actually work on more than one
Dell hardware platform, which is kind of interesting.)

It is a Microsoft/OEM collusion caused "problem". Normal capitalism
drives them to squeeze every last dime that they can from their
customers (you in this case), and corporate greed drives them to
produce software that cannot be run on anyone else's hardware.


nicholson.jr.TakeThisOut@gmail.com wrote:
> Ok I thought when I explained that everything worked fine in my dad's
> sytem people would get that it is in fact a problem between the mb and
> the Emachines BIOS. To answer the questions, on bootup I get a
>
> SAFEMODE
> SAFE MODE WITH NETWORKING
> SAFE MODE WITH COMMAND PROMPT
>
> LAST CONFIGURATION THAT WORKED
>
> START WINDOWS NORMALLY
>
> The only thing that doesn't get me back to where I started is last
> config that worked which gives me the error
>
> \WINDOWS\Sytem32\config\WINDOWS
>
> Emachines writes
>
> Thank you for your e-mail. To further assist you on the issue with
> your
> replacement motherboard that displays an Intel screen instead of
> eMachines screen, please be informed that your System Restore CD should
> work with your replacement motherboard. Please be informed that Intel
> screen appears instead of eMachines because Intel had manufactured
> first
> batch of motherboards only for eMachines that is why eMachines logo
> appears on your screen before. What you have got as a replacement is
> the same motherboard for your system, however, it is named after Intel
> and not eMachines.
>
> then they go on to tell me later after 3 restores
>
> Thank you for your e-mail. I believed the hard drive is not failing.
> The reason for this error is that the restore CD is customized and
> proprietary with the eMachines original motherboard. I suggest to
> purchase a retail version of the Operating System.
>
> So telling me I was stupid for buying a Emachines or any other computer
> at a big box store isn't helpful. I would say 90% of the people who
> buy computers get them at big box stores and expect everything that
> comes with the computer is theirs to use fairly.
>
> THIS IS A MICROSOFT PROBLEM. It has to do with people trying to pirate
> their OS and now 90% of their customers are caught in the middle, and
> of course the little guy gets screwed and the pirates keep not paying.
> This is the same as buying a new car changing out bad brakes at Midas
> instead of the Dealer and now my car won't start. This is exactly what
> is happening.
>
> Now back to my original problem, if I "obtain" a retail version of
> Windows XP home and get my sytem running can I in fact use my serial
> #'s to register and update my computer legally or do I have to actually
> shell out some more money to Microsoft and buy a full retail version
> and then use the new serial #'s??

Hello,
I'm in the same boat you are in...or should I say boot...
Did you find a solution?
I run linux on all my boxes but this is someone else.
If you found a solution, I would appreciate you sharing that with me.
TIA
Steve