Thus far randomly scattered in Issues #13, #57, #64, and #60, any new improvements and bugfixes of the disk dump process should be committed to this issue. There are at the moment known these major problems:
✓ dumping (and thus the whole app) crashes for extremely damaged floppies where sectors appear and disappear randomly in each disk revolution,
there's missing a "dummy container" to opt for when one wants only an analysis of the disk without actually producing a new image,
✓ only until the target image has been produced one sees the content of a bad sector (if any content); a hexa-editor instance should thus be part of the Sector read error dialog,
✓ for CAPS-based images, the current revolution isn't visible in the Sector read error dialog; furthermore, one can iterate over available revolutions only once, never being able to return to previous revolution.
Thus far randomly scattered in Issues #13, #57, #64, and #60, any new improvements and bugfixes of the disk dump process should be committed to this issue. There are at the moment known these major problems: