It's quite a common problem to modify a sector and then forget it mark as "dirty". It isn't as big pitfall in case of virtual images as it is in case of real disk - sectors not explicitly marked as dirty are NOT saved!
To save real hardware and real disks, a virtual DSK image should thus implement an automated detection of modified but clean (non-dirty) sectors. This detection should be triggered during an attempt to save the content of the disk. If all modified sectors are marked as dirty (the ideal case), the saving should proceed. Otherwise, nothing should be saved and the developer should be informed on maybe having forgotten to mark a particular sector as dirty.
It's not necessary to have this functionality in Release mode - this is mainly for a RIDE developer to facilitate debugging of his/her implementation.
It's quite a common problem to modify a sector and then forget it mark as "dirty". It isn't as big pitfall in case of virtual images as it is in case of real disk - sectors not explicitly marked as dirty are NOT saved!
To save real hardware and real disks, a virtual DSK image should thus implement an automated detection of modified but clean (non-dirty) sectors. This detection should be triggered during an attempt to save the content of the disk. If all modified sectors are marked as dirty (the ideal case), the saving should proceed. Otherwise, nothing should be saved and the developer should be informed on maybe having forgotten to mark a particular sector as dirty.
It's not necessary to have this functionality in Release mode - this is mainly for a RIDE developer to facilitate debugging of his/her implementation.