Thanks so very much for this great s/w. I especially love the file renaming flexibility. I have one request…
I would really like the ability to be able to verify that files are copied correctly. If it is already inherent in RPD I couldn’t find any reference to it in the documentation.
I really want to know that files have been copied 100% correctly before I delete the originals off the SD card. Would it be possible to add an option for RPD to generate md5/sha256 or somesuch for each file as part of the copy process, and to verify the file with the copy?
I’m thinking of something like creating a file.original.md5 in the destination folder with the checksum of the source file. After the copy, md5sum --check (for example) would be used to verify integrity. Perhaps using the tee command would allow the source file to only be accessed once for both the copy and the checksum generation so may not slow things down too much.
I appreciate it may slow things down and so may have to be a select-able option. Personally I’d be happy to accept a slowdown (or a second verification step) for the peace of mind it would give.
FYI, at the moment I use kdiff3 (or sometimes meld) to do a binary comparison after the copy (and on the backup), before deleting the original SD card.