philo wrote:
> "Stilllearning" <adminxxx@æcomcast.net> wrote in message
> news:jIedna7J-rwEJMDanZ2dnUVZWhednZ2d@comcast.com...
>> Would someone please point me to a step-by-step procedure for replacing
> the
>> 40 gb boot hard drive in an XP home computer. I have the new 80gb EIDE
> HD,
>> Acronis 10, and an a 150 gb external HD.The computer also has a second
>> internal HD with 100gb free. The bad HD is making those "I'm about to
> croak
>> noises".
>> Something simple for my simple mind.......
>>
>
>
> Even though your drive is failing...if it's still usable ...you should be
> OK.
>
>
> Disconnect the external drive and your 100 gig drive
>
> Install the new drive in place of the 100 gig... (be sure to jumper it
> correctly)
>
> then run Acronis and clone your old drive to your new one...
>
> Shut down but do not reboot.
>
> Now remove your old drive and put the new one in it's place
> (be sure to change jumpers if necessary)
>
> Re-install your 100 gig drive and external and you should be all set
>
>
The critical step there is:
When you've finished copying the old drive to the new one,
only boot the new hard drive when it is by itself.
You don't want the old and new drives connected at the same
time, when the new drive is booting for the first time. Just
the new drive should be connected.
I've had problems, when both the new drive and old drive are
connected, and I boot the new one. After the new drive has
been rebooted once, then everything will be fine, and you
can use any combination of hard disks you want, after that.
You can then shut down and reconfigure disks as needed.
If you screw it up, you can always copy the old drive to the
new drive, and try again. So in that sense, no harm done.
Just be careful that you have the correct source and
destination drives. Again, for simplicity, it makes sense to
only have the old and new drives connected, when you are
using Acronis, as then the possibility of mistakes is
reduced. Once the old is copied to the new, then disconnect
the old one, before booting from the new one for the first
time.
My experience with this, is limited to my experiments with Win2K.
I've cloned a couple times lately, and had to do it over again,
to get past this problem. Booting the new disk all by itself is
what worked for me.
Paul
