“Retry” has worked when the root cause of the error was operator error.
My first thought, too.
For me it often works when only part of the disk is boned. Then I can get to some, most, or even all of the data I want.
retry could also have benefit when using a problematic 5 1/4. in older or lesser quality ones they sometimes would bind up. removing and giving a finger rotate would free them up.
retry was also useful as mentioned when not moving the lever (5 1/4) or fully inserting (3 1/2) ones. when you had files that might span dozens of disks you could get out of sync with your motions easily.
Of course it did–when I put the disk back in the drive or closed the drive door.
And, yes, it did work a few other times, when I didn’t do anything. You have to know how disks fail: when a sector is bad, it just means that the data couldn’t be read in a short enough time period. The data may still be retrievable if you go slow enough–that’s how Scandisk repaired bad sectors, and I’m sure chkdisk still does it that way. If you catch something right on the brink, it might not work one time but work another time.
Typically, Fail would tell the program that the data couldn’t be read, and Abort would kill the program outright. Retry would read the requested data again and, if it worked, would just give the program the data, without telling it that there had been an error.
Please tell me you didn’t think this advice through considering you’re pairing up sex and that particular computer error’s wording :eek:
I can’t recall retry ever working. Fail, though, that seems to have worked once or twice, skipping a missing shared dll, maybe?