Yes. That is useful to know. At this point it would also be useful to get
some information about the drive's partition table. For that, PartinfW
can be downloaded from
http://www.bootitng.com free utilities section.
It's in the partinfo.zip download. From command prompt or run command
simply run
PartinfW >partinfo.txt
then copy and paste the contents of partinfo.txt back.
I've asked someone else (Walter Claton) to have a look and see what might
be usefully done.
Tom
MSMVP
Windows shell/User
"Pherekydes" <(E-Mail Removed)> wrote in message
news:4A7B2073-393A-473B-ADF5-(E-Mail Removed)...
: There's been a new development which might provide a clue about why the
: system won't make the new drive accessible:
:
: I found an old 40-gig Western Digital HD and connected it as a slave on
the
: primary channel. The computer recognized it immediately and assigned
it to
: E:. I could read from it and write to it without problems!
:
: Now, what can we conclude from this development? That there's something
: particular to the drive I'm trying to install that the system deosn't
like
: and that makes it inaccessible?
:
: ======================
: "Pherekydes" wrote:
:
: > I'm trying to move a 160-gig Western Digital hard drive with
important data
: > already on it (not a boot drive) from one computer to a Compaq
Presario
: > SR1820NX Athlon 64 3400 w/ 1 gig RAM, a 160-gig HD, and DVD-RW
optical drive,
: > running XP Home, SP2. The destination computer sees the drive in the
BIOS --
: > and in Disk Management as "DRV2_VOL1 NTFS Healthy (Active)" but
without a
: > drive letter. The drive also does not appear in My Computer. This
drive was
: > working fine as a slave in its previous computer (an eMachines 2.66
ghz
: > Celeron D 330 w/ 1 gig RAM, a 80-gig HD, and 2 optical drives,
running XP
: > Home, SP2).
: >
: > When I right click on the drive in Disk Management, all of the menu
options
: > (Open, Explore, Format, Change Drive Letter, etc.) are ghosted and
: > unavailable, except for Delete Partition and Help.
: >
: > The drive is attached to the slave connector of an 80-line IDE ribbon
cable,
: > with the existing boot drive connected as the master. I have the
jumper of
: > the new drive set to slave, with the boot drive set as "master with
slave."
: > I've also tried setting both drives to "cable select," with the same
negative
: > result.
: >
: > I also:
: >
: > --checked and re-checked all cable connections;
: > --reinstalled the drive in its previous computer to make sure it's
working
: > properly. The previous computer recognized it, accessed it, and
welcomed it
: > as if it had never left;
: > --tried "uninstalling" the drive in Device Manager. On rebooting, a
"Found
: > New Hardware" alert displayed for five seconds, but the New Hardware
wizard
: > never opened. I then tried "Add New Hardware" in Control Panel -- it
couldn't
: > find the drive on its own, but included it in the list of already
installed
: > hardware. No luck there. In subsequent repetitions of this whole
procedure, I
: > no longer even get the "Found New Hardware" alert.
: > --ran Diskpart to see if I could assign a drive letter, but it
couldn't do
: > it (hey, I'm desperate).
: > --would try sacrificing a chicken, if it would help.
: >
: > I don't want to re-format the drive and lose all of the data; and
there is
: > way too much data on it to make backing it up first practical.
: >
: > What stupidly obvious thing(s) have I overlooked?