Stumped

[mhowie]

I finally embarked upon my program of replacing my 40gb IBM HDD with a
new WD 120gb HDD but have run into a snag I can not work my way out of
and would appreciate some guidance...

Here is the chronology thus far:

1) Took WD drive out of box, configured as "slave", booted into Norton
Ghost 2002 boot disk and copied contents of my source drive over to the
destination drive (WD).

2) Removed IBM drive and replaced with the WD drive. Set as primary,
proper cabling ensured, and fired up. BIOS recognized drive, but prior
to booting, received an error message "Primary Master Hard Disk Fail".
Went into BIOS setup to ensure everything was copacetic (including
reported size) and proceeded to start again. Selected "continue" when
the error message was reported again, computer continued booting briefly,
and a failure message was then broadcast. I was (am) unable to boot into
XP with this drive currently.

3) Ran WD Lifeguard Tools to ensure the disk was not defective and the
report came back negative (as in no errors).

4) Reinstalled my IBM drive and booted computer with the WD drive now
configured as the slave drive just to see what would happen.

5) Computer started normally, XP booted, and the WD drive was detected as
a valid HDD. Perused the files via Explorer and it appeared everything
was, in fact, copied over. Space used/free congruent on both drives as
well.

6) Thinking (incorrectly) that perhaps XP needed to "see" the drive once
before it would boot using it as a primary drive, removed the IBM drive
again, set jumper on the WD drive (again) to primary, cabled correctly,
and tried it one more time.

7) Same result as before.

8) Help! Have I omitted some steps? Should I have formatted the drive
via XP prior to attempting the cloning (I thought Ghost would take care
of that)? What is preventing an essentially identical drive (save for
the size) from booting?

Thanks,

 

[mhowie]

Replying to my own question...

I discovered on the WD drives, jumper settings are critical. If there is not a slave drive present, the drive must be configured as "single". My IBM Deskstar allowed the "primary" jumper setting to be used regardless of the existence of a slave drive. Once I changed the jumper to "single", all has been well thus far with the new drive as it is running just like the old one did (in terms of the XP build and applications).