C-Command Software Forum

Reporting of attempts to verify non-read-only images

I read in the DropDMG manual that “only disk images in read-only formats can be verified” and I understand that, but is this the reason why attempts to verify images NOT created in read-only formats report as “verification failed”? I ask because I would have thought that the app might have reported “cannot verify because image is not read-only” or similar instead of the “failed” report.

Yes, perhaps we can improve the error message to say that, but right now it’s normal for it to say “Verification failed…<file>.dmg has no checksum.”