new motherboard - XP wont start

  • Thread starter Thread starter John
  • Start date Start date
J

John

I get the "sorry for the inconvenience" screen and then
the system loops back to P.O.S.T.
I just went from an ABIT MAX2 to an ASUS A7N8X-E Deluxe
and have tried to boot from the CD (not happenin') to
attempt a repair.
Must I reinstall XP? Ugh!
Isn't there something else to try?
 
That is XP's wonderful way of preventing users from installing the OS on
more than one system - sucks, eh? Basically, XP now thinks it is on a
different system and is trying to protect itself. I thought I had read that
you could call Microsoft, but you may be better off reinstalling....
depending on how patient you are...

sorry...
 
You undertake a repair install, if prompted with an MS msg re allready
installed etc you need to phone MS to reactivate
David
 
Bill;
This has nothing to do with "...preventing users from installing the
OS on more than one system".
It is simply a hardware issue easily resolved by performing a Repair
Installation to properly detect the new hardware.
 
Greetings --

Normally, and assuming either a retail license or a generic
(non-branded) OEM license, unless the new motherboard is virtually
identical to the old one (same chipset, same IDE controllers, same
BIOS version, etc.), you'll need to perform a repair (a.k.a. in-place
upgrade) installation, at the very least:

How to Perform an In-Place Upgrade of Windows XP
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q315341

As always when undertaking such a significant change, back up any
important data before starting.


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Greetings --

That's completely wrong, you know. By changing the motherboard,
the OP "pulled the rug out from under" the WinXP installation, which
was specifically customized to the original motherboard. You really
should think about learning a little about computers and operating
systems.

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
That is XP's wonderful way of preventing users from installing the OS on
more than one system - sucks, eh? Basically, XP now thinks it is on a
different system and is trying to protect itself. I thought I had read that
you could call Microsoft, but you may be better off reinstalling....
depending on how patient you are...

sorry...
Click to expand...

Grrrr...enough with the MS conspiracy theories. This has nothing to
do with MS thinking you're trying to cheat them out of some cash. It
has to do with the fact that a new mainboard will have different
resources from the old one; the OS needs to relearn how to work with
the new board.

Think about it. If you put a new engine in your car, that is
radically different from the old engine, then hooked it up to your
car's existing ignition and control computers, would it work? Of
course not. The analogy hold true with the Old OS/New mainboard.
 
I just went from an ABIT MAX2 to an ASUS A7N8X-E Deluxe
Click to expand...


If you have the right Mobo info of course windows is having a
problem. Your going from a 875 intel chip and cpu to an Nforce2 and
AMD cpu. Windows has the agp, northbridge drivers, etc set up for an
intel chip on a AMD board. It has no idea what you want it to do
because when windows starts it's looking for those intel chips and not
finding them. I would think the best thing to do is a complete format
and reinstall. I know when I went from a kt333 chip to the Nforce2 I
ended up doing a complete reinstall to cure the left overs I was
having problems with. Any way good luck.
 
-----Original Message-----
Read this article and you will find that my original statement stands.
Microsoft built-in this behavior to help combat piracy issues....
url=/technet/prodtechn
ol/winxppro/evaluate/xpactiv.asp
Click to expand...

It's always fun when a moron provides a link to information
thinking that the information proves a point, when in fact
the link proves only that the poster didn't read it
himself, or did read it and is incapable of understanding
what's been read.
 
Feel free to provide documentation indicating it is a simple hardware issue
and has absolutely nothing to do with Windows Reactivation and an attempt to
prevent cloning....

On another note, when you typically "pull the rug" out from an OS ( an
appropriate example would be imaging an OS and then restoring on different
hardware ), the OS can recover if it doesn't have built-in "checks" to
prevent such actions ( refer to my previous posts regarding piracy
protection ). You can successfully image and restore linux ( which I have
done with RH & Mandrake ), Novell ( virtually any version ), and Windows w/o
too heartburn.... unless the OS specifically prevents this action, like XP
does...
 
Greetings --

I see, besides a limited reading comprehension, that you also know
almost nothing about operating systems based upon the WinNT kernel.
Your choice of more "promiscuous" operating systems for your example
only proves the point. (By the way, when did Novell _ever_ offer a
workstation or desktop operating system?)

The original issue has absolutely nothing to do with WPA (How
could it? Think for a moment. The OS won't even boot, so the
activation mechanism cannot even be "triggered.") It's purely a
hardware issue. If you knew anything about the OS, you'd understand
what I encounter every day in real life.


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Greetings --

Waiting? Why wait. Just do a quick search of this news or a
similar Win2K news group. And do you always resort to name-calling
when you're shown to be demonstrably wrong? It must make life tough
for you.


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
In the words of John Rambo, "You drew first blood, not me"

I have searched through the newsgroup postings, the web, and microsoft, and
for every argument that I read one way, I read another opposing argument.
The "anti-cloning" argument is the only one I have found documented by
Microsoft, thus my previous statement regarding "still waiting..." for valid
documentation supporting the hardware issues.

I have also searched the posts you have responded to, Bruce, and you
certainly are knowledgeable on topics related to XP... it is just too bad
your bedside manner leaves to a bit to be desired.

"You really should think about learning a little about computers and
operating systems."
"..besides a limited reading comprehension, that you also know almost
nothing about operating systems based upon the WinNT kernel"
 
I have an Idea. Someone send him a Win98 or WinME disk, let him
install his old Intel 875 chip mobo along with the intel CPU and
install the older windows version. Then without changing anything in
windows remove the old mobo again and reinstall the new Nforce2
chipped mobo along with his new AMD cpu that he has installed now and
restart. I would bet windows won't start, be it WinMe or Win98. That
kinda blows the old conspiracy therory away over WinXP.

Why can't people understand that an intel 875 mobo has totally
different drivers than an AMD Nforce2 board? Imagine this, take out
your Radeon9800 Pro vid card then stick in a Geforce5800 vid card and
then try to make that Geforce use those Radeon drivers. Ain't gonna
happen. You will never get that Geforce to run on those drivers. And
no it's not winXP's fault either.

Not trying to cause trouble but it's just that simple. The drivers
must match the hardware and an AMD NForce2 mobo is as opposent a
Intlel 875 mobo as one can get.

Read his original quesiton, it's a intel mobo originally and
changed to an AMD style mobo. Spin it how ever you want but I don't
think even linux will let you get away with that.


Renegade
 
-----Original Message-----
Feel free to provide documentation indicating it is a simple hardware issue
and has absolutely nothing to do with Windows Reactivation and an attempt to
prevent cloning....

On another note, when you typically "pull the rug" out from an OS ( an
appropriate example would be imaging an OS and then restoring on different
hardware ), the OS can recover if it doesn't have built- in "checks" to
prevent such actions ( refer to my previous posts regarding piracy
protection ). You can successfully image and restore linux ( which I have
done with RH & Mandrake ), Novell ( virtually any version ), and Windows w/o
too heartburn.... unless the OS specifically prevents this action, like XP
does...
Click to expand...

Better to keep your mouth shut and be thought an idiot
than to open it and remove all doubt. What earthly
reason could there be for MS to build the OS so that it
would crash in this type of situation? Why not just go
ahead and allow the boot, but stop at a mandatory-
activation screen? Also, congratulations on your
discovery that XP is different from Linux and other
operating systems. This shows that you may indeed have
some small amount of functioning brain tissue, although
including Novell in the comparison makes one wonder.
 
Back
Top