Re: upgrading to new motherboard
From: Opinicus (gezgin_at_spamcop.net)
Date: 07/13/04
- Next message: Jim Macklin: "Re: upgrading to new motherboard"
- Previous message: Ray Woodcock: "SATA Drive Not Recognized"
- In reply to: tooly: "upgrading to new motherboard"
- Next in thread: Jim Macklin: "Re: upgrading to new motherboard"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Jul 2004 17:27:07 +0300
"tooly" <rdh11@bellsouth.net> wrote
> I'm upgrading to a new motherboard (and cpu) and want to
know what to expect
> when I 'transfer' the hard disk over containing winXP.
Will it not identify
> the mobo as 'wrong'...and any new or added peripherals,
like an added 80gig
> second harddisk as problematic?
> This is an 'upgrade' version of XP, not standalone. What
I'd really like to
> do is transfer the OS over to the new 80 gig hard drive,
keeping the old 40
> gig as the backup...but knowing XP and all it's hardware
validation mess,
> probably not worth the problems I'd encounter (?).
> So, any techies out there who might step me through what
to do on this?
I'm not a techie but the following is is my experience.
I removed the old mob, installed the new one. Turned on the
system and WinXP (Home) naturally complained. I was directed
to do a repair installation, for which the qualifying media
in my case was an OEM version of WinXP. The repair
installation went off without a hitch and the next time I
rebooted the system, WinXP was fine. Well, almost without a
hitch. Due to a mistake on my part I had confusing multiple
user structures with old and newly created users, all of
whom were me. (As I said, this was entirely my fault.) I
lived with this for a while but eventually it got so
annoying that a few days later I did a clean format and
reinstallation and everything went off just fine. It took me
2-3 days to reinstall all my software--which, I should add,
worked fine so far as I could tell after the repair
installation.
A couple of months later, I upgraded my HD to a much bigger
Seagate. The new drive was to be the boot drive and the old
one the slave drive. Seagate provided a wizard that
partitioned and formatted the drive and relocated all my
data and programs etc to the new drive. I was very sceptical
about this but it went off surprisingly well. Once the dust
cleared, everything was working fine--until I decided to
clean out the slave drive so I could use it for backup.
Suddenly many of the programs that the wizard had relocated
to the new drive wouldn't work. The problem it seemed was
that these programs were still retrieving their modules from
the old drive. The locations had somehow been "hard-coded"
into the programs. After dicking around with this for a
while I did the only thing I could: Once again I did a clean
format and reinstallation etc.
YMMV.
-- Bob Kanyak's Doghouse http://www.kanyak.com > This has to be a common question...right? Why not in MS knowledge base I > wonder?
- Next message: Jim Macklin: "Re: upgrading to new motherboard"
- Previous message: Ray Woodcock: "SATA Drive Not Recognized"
- In reply to: tooly: "upgrading to new motherboard"
- Next in thread: Jim Macklin: "Re: upgrading to new motherboard"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
