Deodiaus said:
I have a 6 yr old Dell inspiration 2200 but my HD [hitachi
hts424030m9at00] died.
1) I got an adapter and plugged it into another desktop. It is
detected by the bios, but not by WinXP. Are there any good
recommended web sites which might discuss ways to try to recover info
off that HD? I don't want to pay too much, as I doubt that info is
worth a lot, but it is worth something.
2) If I were to buy another HD, is there any way to go about getting
a version of WinXP for that laptop? If I call up Dell, I doubt that
they will give me a WinXP cd, for they stopped including the CDs with
their PC years ago?
Here is a condensed summary. You say you can see it in the BIOS, which
is a good sign. The name hts424030m9at00 suggests the disk initialized OK.
So it could just be a problem with the partition table, or with the
file system on the partition.
This tool displays the current partition table. Up to four primary
partitions
may be on the disk. More partitions can be there, by means of extended
partitions,
but I don't know how that works. Some prebuilt computers have three
partitions for example. Your reason for examining this table, is as a
sanity check. Do the numbers seem consistent with what you know about
your computer, and the size of partitions ? (This tool runs in Windows.)
ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/PTEDIT32.zip
If the partitions seemed wrong, there is this tool. It can scan the disk,
find the partitions, and build a new partition table. But you could
just as easily screw something up, as fix it.
http://www.cgsecurity.org/wiki/TestDisk
These tools, are examples of file scavengers. They should attempt to
find any files present, and allow you to copy the files to another spare
disk.
These tools happen to be free. There are tons of $39.95 tools for sale
on the Internet that will do something similar.
http://www.cgsecurity.org/wiki/PhotoRec
http://www.pricelesswarehome.org/WoundedMoon/win32/driverescue19d.html
The Windows built-in tool "chkdsk" can be used to repair damage
to a file system. But for that to work, a file system has to be
recognized on a partition. That is why I didn't mention chkdsk
in the above.
Some of the above suggestions, involve "in-place" repair. Such a
repair method is dangerous. If the disk was working at all,
you should do a sector by sector backup of the disk first, to
a spare disk. This would be your "insurance". I use the "dd"
program for that, and there is a Windows version of "dd" as well.
(In helping someone with this the other day, the poster almost
overwrote the disk on his repair computer. Don't be careless
with the syntax while using this!)
http://www.chrysocome.net/dd
Virtually all of the tools mentioned so far, are scary, and
much care must be used when preparing commands and so on.
So if you're not comfortable working at this level, go
to a local shop and get help.
*******
If you use PTEDIT32, and can actually get numbers from the
broken drive, then you might take the drive to a local
shop, and get them to perform the necessary voodoo.
If you can't get anything with PTEDIT32, then a data
recovery company ($$$) may be necessary. They can
open the HDA, replace the head assembly, and so on.
So at least using PTEDIT32, should be relatively safe
and quick as a check. But the rest of it requires a lot
more care. Ideally, you should have two spare disks,
larger than the broken disk, to aid in your data
recovery efforts.
The scavenger programs should also be safe, as long
as the output from the scavenger is pointed to a
spare disk. Do *not* try to write any recovered
files, to the broken disk. For some reason, there
are people who try stuff like that.
Paul