Question about upgrade to larger drive and some anomolies

  • Thread starter Thread starter Rockin Ronnie
  • Start date Start date
R

Rockin Ronnie

I used Drivewizard to image my Maxtor 40 gig hard drive when I upgraded to a
120 gig Seagate 7200.7 drive (1 partition) so that I could use the larger
(and faster) drive as the boot drive. Everything went fine, the jumpers were
changed when instructed and the computer booted as it should. Took about two
hours.

A couple of strange things happened however once I was in the OS. My Office
XP acted funny. Couldn't launch Word because it could not fine the
executable, Outlook is also giving me trouble because it cannot locate the
*.pst file. Games ran fine but COD had to be reinstalled because it could
not find a "folder". Otherwise everything else works great.

(Methinks that a fresh install of WinXP Pro is probably around the corner).

Any thoughts about what could have happened?

Box has an Asus P4T-E, 512 RDRAM, now 2 hard drives; a 40 and a 120, Radeon
9600Pro, 300W+ PSU.

Ron
 
I used Drivewizard

That was your big mistake, using that with XP.
to image my Maxtor 40 gig hard drive when I upgraded to
a 120 gig Seagate 7200.7 drive (1 partition) so that I could
use the larger (and faster) drive as the boot drive. Everything
went fine, the jumpers were changed when instructed and the
computer booted as it should. Took about two hours.

Did it tell you to have the old drive unplugged for the first boot
after the copy had been done ? If it didnt, thats the problem.
That needs to be done with XP otherwise it gets seriously
confused when it can see the original and the copy of XP
and the config involves parts of XP on both drives.
A couple of strange things happened however once I was in the
OS. My Office XP acted funny. Couldn't launch Word because it
could not fine the executable, Outlook is also giving me trouble
because it cannot locate the *.pst file. Games ran fine but COD
had to be reinstalled because it could not find a "folder".
Otherwise everything else works great.

You may well find that XP wont even boot successfully
if you physically unplug the original drive and try to boot.
(Methinks that a fresh install of WinXP Pro is probably around the corner).

It may be possible to do the copy again and this time
make sure that XP cant see both copys on the first boot.

I'd personally use ghost or drive image tho, not DriveWizard which even
some for maxtor support monkeys realise is a steaming turd at times.
Any thoughts about what could have happened?

Basically copying an XP isnt a trivial exercise and
XP will get seriously confused if it can see both
copys on the first boot after the copy has been made.
 
Rod Speed said:
That was your big mistake, using that with XP.


Did it tell you to have the old drive unplugged for the first boot
after the copy had been done ? If it didnt, thats the problem.
That needs to be done with XP otherwise it gets seriously
confused when it can see the original and the copy of XP
and the config involves parts of XP on both drives.


You may well find that XP wont even boot successfully
if you physically unplug the original drive and try to boot.
corner).

It may be possible to do the copy again and this time
make sure that XP cant see both copys on the first boot.

I'd personally use ghost or drive image tho, not DriveWizard which even
some for maxtor support monkeys realise is a steaming turd at times.


Basically copying an XP isnt a trivial exercise and
XP will get seriously confused if it can see both
copys on the first boot after the copy has been made.

I realize that now and I can assume that the only way to "fix" it now is to
reinstall Windows. And no, Drivewizard did not mention this in the
instructions. Thanks.

Ron
 
Rockin Ronnie said:
Rod Speed said:
It may be possible to do the copy again and this time
make sure that XP cant see both copys on the first boot.

I'd personally use ghost or drive image tho, not DriveWizard which even
some for maxtor support monkeys realise is a steaming turd at times.


Basically copying an XP isnt a trivial exercise and
XP will get seriously confused if it can see both
copys on the first boot after the copy has been made.
[...]
I realize that now and I can assume that the only way to "fix" it now is to
reinstall Windows. And no, Drivewizard did not mention this in the
instructions. Thanks.


Re-read the posting. You don't have to re-install XP. You just
have to re-clone the HD. But don't boot up the new HD with any
other HD (such as the old one) connected. The cloning might be
attainable with DriveWizard, or as Rod suggested, do it with
Drive Image or Ghost. If you want to experiment with a free beta
utility by a well-reputed programmer, download xxClone from
www.xxClone.com .

*TimDaniels*
 
Timothy Daniels said:
Rockin Ronnie said:
Rod Speed said:
It may be possible to do the copy again and this time
make sure that XP cant see both copys on the first boot.

I'd personally use ghost or drive image tho, not DriveWizard which even
some for maxtor support monkeys realise is a steaming turd at times.

Any thoughts about what could have happened?

Basically copying an XP isnt a trivial exercise and
XP will get seriously confused if it can see both
copys on the first boot after the copy has been made.
[...]
I realize that now and I can assume that the only way to "fix" it now is to
reinstall Windows. And no, Drivewizard did not mention this in the
instructions. Thanks.


Re-read the posting. You don't have to re-install XP. You just
have to re-clone the HD. But don't boot up the new HD with any
other HD (such as the old one) connected. The cloning might be
attainable with DriveWizard, or as Rod suggested, do it with
Drive Image or Ghost. If you want to experiment with a free beta
utility by a well-reputed programmer, download xxClone from
www.xxClone.com .

*TimDaniels*

BTW, thanks for the advice, Rod

Ron
 
Back
Top