R
Rod Speed
Rod Speed wrote
try reading it again-
No need, it was wrong then and still is now.
i made no such "original"
Says he after carefully deleting where he said just that from the quoting.
Its now back again right at the top.
there is nothing wrong with imaging the drive;
The exact opposite of what you said originally.
there are few simpler, quicker and cheaper
steps to take before that. that's all.
Nothing like you originally said.
uh... 132MB limit mean anything to you?
Irrelevant to whether sector imaging still works fine.
or "dynamic disk"?
You didnt say it was useless with dynamic disks and
you would have been just plain wrong even if you did.
there's a few things that can and do prevent imaging a drive-
Bugger all in fact in practice.
it's not cut and dried. it's a complex process with a lot of variables,
Bullshit it is with sector level imaging.
and suggesting it to someone on USENET with limited
amounts of verifiable information is not terribly responsible.
More mindlessly silly stuff. Wont do any harm over not doing one at all.
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"
Nope, nothing like.
neither you, nor me, nor "john doe" knows anything more
about this person's problems than what's been posted here-
Which is another damned good reason for imaging the drive for
safety before doing anything to attempt to make it usable again.
that's why i'm suggesting the quickest, safest, and easiest way out.
You did the exact opposite in fact.
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.
And as far as you ever knew, the result could have been completely different.
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.
Irrelevant to your stupid pig ignorant
claim TO JOE, that imaging is useless.
now, if someone had suggested fdisk, or chkdsk /r, that
would be wrong. restoring an MBR is safe as houses.
Irrelevant to your stupid pig ignorant
claim TO JOE, that imaging is useless.
OK- assume it's an 80GB consumer drive- she needs
another of the same maker or a bigger drive- that's $85.
Not if you have one available to use.
add in True Image, which is an excellent product, and that's $30-
Not if you choose to not pay for it. There are free imagers too.
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
Pig ignorant silly stuff.
AND doing sector by sector imaging on anything above the 132GB limit
Pig ignorant silly stuff when its done with a linux based imager.
is guaranteed to have a higher fail rate AND
might screw up a giant drive permanently.
More utterly mindless pig ignorant silly stuff.
so.... the quick, free, and safe option still
seems like the right one to me. go figure.
Yep, you're a fool that lives dangerously.
Nothing to 'figure' about that.
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.
Never ever could bullshit its way out of a wet paper bag.
MY way was the safe way.
Bare faced pig ignorant lie.
YOUR way was the long, expensive, complicated way.
Bare faced pig ignorant lie.
Spinrite is *not* the "10-minute diagnosis/recovery". duh.
Pity it was what JOE was suggesting might be worth
trying if more basic recovery approaches didnt work.