You will need your windows xp cd to fix that.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q315341&ID=KB;EN-US;Q315341
--
-----------------------------------------
Michael Ortega
"Wendy E" <Wendy E...@discussions.microsoft.com> wrote in message
news:2D8D5CD4-D8B2-482F...@microsoft.com...
Normally, and assuming a retail license (many OEM installations
and licenses are not transferable to a new motherboard - check yours
before starting), unless the new motherboard is virtually identical
(same chipset, same IDE controllers, same BIOS version, etc.) to the
one on which the WinXP installation was originally performed, 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
The "why" is quite simple, really, and has nothing to do with
licensing issues, per se; it's a purely technical matter, at this
point. You've pulled the proverbial hardware rug out from under the
OS. (If you don't like -- or get -- the rug analogy, think of it as
picking up a Cape Cod style home and then setting it down onto a Ranch
style foundation. It just isn't going to fit.) WinXP, like Win2K
before it, is not nearly as "promiscuous" as Win9x when it comes to
accepting any old hardware configuration you throw at it. On
installation it "tailors" itself to the specific hardware found. This
is one of the reasons that the entire WinNT/2K/XP OS family is so much
more stable than the Win9x group.
As always when undertaking such a significant change, back up any
important data before starting.
This will also probably require re-activation, unless you have a
Volume Licensed version of WinXP Pro installed. If it's been more
than 120 days since you last activated that specific Product Key,
you'll most likely be able to activate via the internet without
problem. If it's been less, you might have to make a 5 minute phone
call.
--
Bruce Chambers
Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html
You can have peace. Or you can have freedom. Don't ever count on
having
both at once. - RAH
--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/
"Wendy E" <Wendy E...@discussions.microsoft.com> wrote in message
news:2D8D5CD4-D8B2-482F...@microsoft.com...
JJ has the correct story. The Repair install will reset XP to the new
hardware environment and also back to the state of your install disk - XP
basic, XP SP1 - so SP2 will need to be reinstalled.
Repair Install to SET XP to New Motherboard
1. Do Not BOOT into Windows XP on first boot after Motherboard or Hard Drive
change! If booting from CD is not an option, return to BIOS and make sure
booting from CD is the first boot option.
2. If your computer does not support booting from the CD, check your OEM or
Motherboard makers web site for updated BIOS.
3. Perform a Repair Install by following the step by step below.
Wen you see the "Welcome To Setup" screen, you will see the options below
This portion of the Setup program prepares Microsoft Windows XP to run on
your computer:
To setup Windows XP now, press ENTER.
To repair a Windows XP installation using Recovery Console, press R.
To quit Setup without installing Windows XP, press F3.
Press Enter to start the Windows Setup.
Accept the License Agreement and Windows will search for existing Windows
installations.
Select the XP installation you want to repair from the list and press R to
start the repair.
Setup will copy the necessary files to the hard drive and reboot. Do not
press any key to boot from CD when the message appears. Setup will continue
as if it were doing a clean install, but your applications and settings will
remain intact.
Blaster worm warning: Do not immediately activate over the internet when
asked, enable the XP firewall before connecting to the internet. You can
activate after the firewall is enabled. Control Panel - Network Connections.
Right click the connection you use, Properties, and there is a check box on
the advanced page.
Reapply updates or service packs applied since initial Windows XP
installation.
Activation
What happens when you change a motherboard or move a hard drive depends on
the accumulated changes made within a 120 day period since initial
activation.
It also depends on the version of Windows XP intended for the move.
Retail versions of XP
Rtail versions of XP can be moved from and reinstalled as many times as you
want as long as it is in compliance with the EULA. The EULA states: You may
install, use, access, display and run one copy of the Software on a single
computer, such as a workstation, terminal or other device ("Workstation
Computer")
OEM versions of XP
1. OEM versions of XP preinstalled on systems according to the OEM EULA
cannot be transferred to another computer[or new Motherboard]. This is
defined in the EULA.
2. OEM versions sold with a piece of hardware are thought to be tied to the
original computer it is installed on.
For clarification: Contact
Microsoft Corporate and Legal Affairs
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399
USA
BAR:
In your excellent step-by-step instructions to the OP for carrying out a
Repair install, you caution against an initial boot following a
motherboard/hard drive change. I've seen the same cautionary note from other
posters as well. Indeed, the Michael Steven's site, probably the most often
recommended site for information on performing a Repair install also
contains this advice. I've even come across statements to the effect that an
initial boot before undertaking a Repair install could be "fatal", (whatever
that means).
Would you be good enough to explain why you believe this initial boot can
cause problems? I raise this issue since I've had occasion to undertake
perhaps 50 Repair installs on various machines after a motherboard/hard
drive/processor/RAM, etc. change and I ALWAYS attempt an initial boot
immediately following the change. Admittedly, in the vast majority of cases
the system will not boot, however, in a few cases the system will boot,
notwithstanding the fact that major components were changed and presumably
the system should not have booted. But it did. And by so doing, the rather
lengthy Repair install proved unnecessary. Should the initial boot fail, I
proceed, of course, with a Repair install. I have never come across a single
instance where performing a failed initial boot caused any subsequent
problems of the OS that could be traced to a failed first boot in this
situation.
I would appreciate your further comments on this issue.
Art
How so? Please provide specific technical details.