1. Several large files
2. One md5 file with hashes, placed in the same directory
Problem:
1. If file has the extension .md5 or no extension at all, the command Files -> Verify Checksums passes OK.
2. If I change the extension to .txt, it says
This doesn't represent a big problem if the hash file is on a hard drive (because I can rename it to .md5), but it can be pain in the ear if it's located on a read-only drive (e.g. md5 hash file on Linux ISOs). In that case, I have to copy the hash file on a hard drive, rename it to .md5 (or remove the extension) and then search/replace relative paths with full paths to point to DVD drive, so the verify procedure can locate actual files.Wrong CRC: md5sum.txt
Errors: 1
OK: 0, not found: 0, read error: 0, wrong checksum: 1
Please make this command work according to file content and not according to file extension.
Here is an example md5 file:
https://dl.dropboxusercontent.com/u/22166389/md5sum.md5
(Unix-style endline format)