dvdisaster Version 0.72 (pl3) | To the Internet version

Contents
News
Overview
Howtos
· | The big picture
· | Scanning media for errors
| - | Basic settings
| - | Performing the test
| - | Interpreting the results
| - | Advanced settings
· | Putting error correction data on a separate file
· | Putting error correction data on the medium
· | Recovering media images
· | Getting information about images and error correction data
· | Testing image compatibility
· | Dialogs and buttons
Download
Questions and Answers
Bug reporting
Scanning media for errors |
Advanced settings
Ignoring fatal errors. dvdisaster will normally abort the scan when the drive reports a fatal internal error like mechanical problems. The intention is to avoid damaging the drive. However some drives will erroneously report such problems when they get confused by damaged media. If you have such a drive you can use this option to force the scan to continue. Eject medium after sucessful read. dvdisaster tries to eject the medium after a successful scan if this option is activated. However ejecting the medium might be prohibited by the operating system so this is not guaranteed to work. For example if upon media insertion a window is opened for performing the contents it may not be possible to automatically eject the medium.
Screen shot: "Drive" tab.
Skipping sectors after a read error. Attempts for reading defective sectors cost a lot of time. Since it is likely to encounter another defective sector after hitting a read error, skipping a few sectors after a read error saves time and reduces wear on the drive. If you only want a quick overview of a damaged medium setting this value to 1024 might help. But keep in mind that all skipped sectors are treated as being defective so the number of reported errors becomes higher and less accurate. |
"Read attempts" tab.
Old documentation (V0.70)

Copyright 2004-2011 Carsten Gnörlich. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.