Wrong, he's commenting on your original that there is no point
in imaging the bad drive and your original is just plain wrong.
try reading it again- i made no such "original"
there is nothing wrong with imaging the drive; there are few simpler,
quicker and cheaper steps to take before that. that's all.
Wrong. And decent imager can image at the sector level.
uh... 132MB limit mean anything to you? or "dynamic disk"? there's a
few things that can and do prevent imaging a drive- it's not cut and
dried. it's a complex process with a lot of variables, and suggesting
it to someone on USENET with limited amounts of verifiable information
is not terribly responsible.
it's like telling someone with one squeaky brake that they need to
replace all their rotors and pads and change out the brake fluid out
"to be on the safe side"
neither you, nor me, nor "john doe" knows anything more about this
person's problems than what's been posted here- that's why i'm
suggesting the quickest, safest, and easiest way out.
and lo! it worked- everything is fine now, no need to spend the better
part of day yanking PCs apart and fiddling with live CDs, spare hard
drives, and gobs of time.
Which can screw the drive data structures even worse than they
are already. If you have an image, you can try various fixes.
that's a load of mule muffins. partition information recovery is
harmless to your drive. TestDisk, which i recomended, and may i remind
you, *solved the problem*, is pathetically easy to use and very
reliable.
now, if someone had suggested fdisk, or chkdsk /r, that would be wrong.
restoring an MBR is safe as houses.
ALL it needs is another drive.
OK- assume it's an 80GB consumer drive- she needs another of the same
maker or a bigger drive- that's $85.
add in True Image, which is an excellent product, and that's $30- now
she's $115 in the hole and needs a PC that can handle all the drives
and do 2 - 6 hours worth of crunch time, AND there's about a 1:4 chance
of getting a corrupt image AND doing sector by sector imaging on
anything above the 132GB limit is guaranteed to have a higher fail rate
AND might screw up a giant drive permanently.
so.... the quick, free, and safe option still seems like the right one
to me. go figure.
it's working out so far- i'll chalk this up in my "Win" column, and you
and John Doe can chalk it up in your "Sour Grapes" column.
Stupid assumption. Makes more sense to do it the safe way instead.
MY way was the safe way. YOUR way was the long, expensive, complicated
way.
That last is just plain wrong when you use something like Spinrite.
Spinrite is *not* the "10-minute diagnosis/recovery". duh.
carl