

(Or use a comparison tool like WinMerge or Beyond Compare which are great for that kind of thing and integrate well into Opus.) If you want to test if two folders are the same, generating a list of checksums for all the files and then comparing the list will take the same amount of time and tell you which files are missing or different, which seems better. We could concatenate every file in (and below?) a folder, but the result would depend on the order and be unlikely to be comparable to anything other than Opus itself. What do you mean by checksums for folders? Folders themselves have no data to checksum.


SHA-1: B30BDCF78EA0BF6D9996BA40318F2201CEB1065Bģ.3) Format of this text file: UTF-8 without BOM or ANSI or Unicode or others "%MD5%" or "%SHA1%" or "%MD5%, and on the next line %SHA1%".įor example, DOpus will create for the file "DOpusInstall_12.18.exe" next text-file "DOpusInstall_12.18.exe_file.txt", which will contain the following text:ĭate of change: 2019.11.20 Wednesday, 06:44:32 Namely what will be saved in this file:ģ.1) the name of the file itself %name%.%extension%_file.%namesumm%įor example: "7zip.exe" -> "7-Zip.exe_file.txt" or "7zip_file.md5" or "7zip.exe_file.md5"ģ.2) the contents of the file as a sample for all such cases:ĭate and time of change (dd. Please right-click to save the checksums to the file. Why are there no CRC32- or CRC64- or SHA256- or SHA512-sums and other checksums for files and folders? In the next version, please add MD5 and SHA1 amounts for folders in the file/folder overview columns.
