Communicatie (Lees Instellingen)


[Nog niet alle pagina's zijn vertaald.  Dit is een werk van lange adem.  Indien een bepaalde pagina u zeer interreseert maar nog moet vertaald worden, gelieve dan de exacte link naar deze pagina naar ons op te sturen met het verzoek prioriteit te geven aan de vertaling ervan.  Dank u.]

Read Settings

IsoBuster - Communicatie  (Lees Instellingen)

Retries

During reading, IsoBuster will typically (and where possible) read more than one block at a time.
If that fails for some reason IsoBuster will read every block individually.
For both mechanisms a default retry count is set.  You can change this per device using the sliders.
This change only affects IsoBuster behavior, no other application (e.g. the OS itself) is affected !
This setting is not saved and next time when you start up IsoBuster the default setting will be used again.

In case reading takes very long, because there are many errors and the CD/DVD readers needs a long time per block, you could consider to read with a lower retry count.  If you notice that with more retries you don't find the data either it is rather safe to go to a lower retry count and it will save you a lot of time.  

Worst case, trying to read corrupted data, the drive needs 30 seconds per block.  This times the retry count and this times the amount of blocks which ranges from 330,000 (CD) to 2,200,000 (DVD).  I don't need to make you a picture of what that can mean to your precious time.  Luckily and mostly only a smaller part of the blocks is unreadable, hardly never will all data be too corrupt to read.

Delays

Especially with older drives, in combination with certain (hard to read) discs, it is sometimes possible that when you select "retry" on a faulty read the data can be read anyway.  This is a bit strange as IsoBuster does a number of retries internally anyway and the only explanation seems to be that the drive needs some time to "breath".
E.g. the drive needs to cool down or spin down or there is a design flaw in hardware or embedded software that causes this behavior.
So if you are in this situation, e.g. you're extracting data from a CD and each time you find yourself hitting retry after which the process continues normally, then this option is for you.
By setting a number of seconds in this option, IsoBuster will wait that long each time before the read is retried.  So the drive is allowed to spin down and correct whatever situation that causes this problem.
This option can cause a serious speed penalty, so use it only when you are sure it will help you !

  • Preferred communication layer
  • Remapping settings
  • Custom remapping settings