Query: Meaning of Retries in DVDDecrypter

[Kedirekin]

Just a couple of questions to satisfy my curiosity (to anyone who cares to answer).
[list=1]
What is the meaning of retries in DVDDecrypter?
On a successful retry, how likely is it that the copied/decrypted block is correct?
[/list=1]
Does a successful retry mean that a block matched a checksum? That it was error-corrected successfully? That two or more reads of the block matched? None of the above?

I know that the error correction on DVDs is very robust, but how likely is it that a successfully retried block has no errors? Are we talking 90%, 99%, 99.99%? I suspect the ballpark answer to this depends heavily on the answer to #1.

Thanks in advance.

[LIGHTNING UK!]

Its where the read command sent to the drive failed.
The program then submits the same command again (tries to read the same sector again) - that's 1 retry.

It does this 20 times (by default) before then displaying an I/O error dialog box.

I've no idea how correct the data is that gets returned. If the drive thinks it read it ok, that's good enough for me. Not much I can do about it anyway!

With the inclusion of the pack header checking / reporting in later versions, this is an additional check that the data read off ok.

[Dimmer]

@LIGHTNING UK!

On the same topic: what is the difference between software and hardware retries set in I/O and Device Preferences respectively?

Also, I wanted to use this opportunity to THANK YOU for the brilliant programme!

[LIGHTNING UK!]

Software retries are what I do within the software, hardware retries are those done by the drive itself.

Remember the old 'fast error skip' in CloneCD? Well that (I believe!) just put the hardware read error retries down to a low number. The drive didnt do much in the way of error correction and the software didnt either. That means safedisc bad sectors could be skipped over like lightning! (well, for some drives anyway)

You can tell a drive how many times to attempt error correction before giving up and returning an error to the software. That's hardware retries.

[Dimmer]

Thanks for the reply, now it makes more sense to me. I figured it has something in common with the 'fast error skip'.