misleading error messages

[Mike Scheutzow]

Hello Thomas,

Thank you for creating such a high-quality app.

I want to share a recent experience where the error message misdirected 
me for about 30 minutes. I use the command line. I wanted to backup 
several file trees to a blank blu-ray disk, but I didn't realize the 
file size exceeded the capacity of the blu-ray disk. The error messages 
output by xorriso didn't guide me in the right direction:

> xorriso : SORRY : Missing on disk and in ISO: disk_path 
'/d2/android-studio'
> Not ok. Comparison or update failed due to error. (runtime 0.0 s)
> xorriso : WARNING : No session MD5 is recorded with the loaded session
> MD5 MISMATCH WITH DATA OF LOADED SESSION !
> xorriso : FAILURE : Event triggered by MD5 comparison mismatch
> xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
> xorriso : FAILURE : -eject: Image changes pending. -commit or 
-rollback first

At the very end, it did print the following (but I didn't notice it 
until after much debugging effort):

> xorriso : FAILURE : Image size 13004673s exceeds free space on media 
12219392s

My suggestion is that if a disk does not have sufficient free space, 
it'd be much clearer if the app aborted immediately with that final 
FAILURE message, and avoided showing all the intermediate "fake" 
failures. Linux users have been trained to debug using the first few 
errors, not the 8th one.

thanks again for an excellent app,
Mike Scheutzow