Re: Replace MB & Processor

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

If you follow the directions and uninstall extraneous
hardware, so Windows doesn't have to work around them, set
the BIOS to boot from the CD and then do your swap of the
mobo and CPU and boot from the CD, your only likely error is
to do a clean install as a dual boot. Be sure to follow the
instruction Bruce listed and read the instructions on screen
when the CD boots. Do it right and I'd say your odds at 95%
success. Be sure to have reliable power [ UPS ] if you can.
If you can afford it, why not buy a new hard drive and do a
clean install, gain more storage and avoid the hassle. The
your old drive becomes your slave and backup.



--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.
some support
http://www.usdoj.gov/olc/secondamendment2.htm
See http://www.fija.org/ more about your rights and duties.


"Irv" <Irv@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EB01CBA1-9B53-4756-BCC8-A17DDFFDC698@xxxxxxxxxxxxxxxx
| My question would be what are the chances of success?
| I am doing an upgrade to me system with an upgraded MB and
Dual COre
| processor. It is a retail version of winxp sp2
|
| "Bruce Chambers" wrote:
|
| > Irv wrote:
| > > I am getting ready to replace my MB and Processor. I
have read the article
| > > from MS ID#824125.
| > > What I am trying to do is repalce these items and not
touch the hard drive.
| > > I do not want to reinstall WinXP SP2 as I want to wait
until Vista is
| > > released and then do a complete reinstall. Has anyone
used this procedure
| > > with any luck? Any suggestions are welcome.
| > > Thanks
| >
| >
| > Normally, and assuming a retail license (many
factory-installed OEM
| > installations are BIOS-locked to a specific chipset and
therefore 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
| >
| > Changing a Motherboard or Moving a Hard Drive with WinXP
Installed
| > http://www.michaelstevenstech.com/moving_xp.html
| >
| > 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
| >
| > They that can give up essential liberty to obtain a
little temporary
| > safety deserve neither liberty nor safety. -Benjamin
Franklin
| >
| > Many people would rather die than think; in fact, most
do. -Bertrand Russell
| >


.

Relevant Pages

  • Re: Boot Problem
    ... see a red X next to something, but it either won't boot or works perfectly. ... On reboot, BIOS screens all run normally, then there is a 50/50 ... Install Service Pack 2 and instead of going into Hiberation, ... so I don't see how it can be a hardware problem. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: new case and motherboard
    ... evesham will provide a clean install. ... drivers, else you need to get a copy of XP and do a fresh install, you ... damage hardware around 3 out of 4 times out of all the links I read; ... windows boot sequence except as a malicious trojan process. ...
    (uk.comp.homebuilt)
  • Re: Advice on DOS / WinXP co-existence
    ... >First, MS-DOS can't read, write, boot from or even SEE and NTFS partition, ... WinXP can be installed into just about any volume (primary partition ... If you choose to install WinXP ... so DOS programs that try to directly manipulate ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Advice on DOS / WinXP co-existence
    ... >First, MS-DOS can't read, write, boot from or even SEE and NTFS partition, ... WinXP can be installed into just about any volume (primary partition ... If you choose to install WinXP ... so DOS programs that try to directly manipulate ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Advice on DOS / WinXP co-existence
    ... >First, MS-DOS can't read, write, boot from or even SEE and NTFS partition, ... WinXP can be installed into just about any volume (primary partition ... If you choose to install WinXP ... so DOS programs that try to directly manipulate ...
    (microsoft.public.windowsxp.perform_maintain)