Hi Mathias, I appreciate all the work you did with that extension within MC in the last months fixing the remaining bugs and adding unicode support, all working as expected.
Recently I got some corruption in my HDDs and used the file checksums to analyze which files got corrupted... in the process I found I missed some things to make it that system totally reliable.
Corrupted Checksum files (*.md5, *.sfv, ...) are not loaded by the extension nor can be identified. I found this to be a problem because apart from having my files (to be checked) corrupted, some of the sfv files themselves were also corrupted. If I try to check them nothing happens since the info stored is not readable BUT the program also does not warn you about it.
Is not important when you just check one file but it does if you are checking 10000 sfv files without user attention, just loading the entire batch from folders and subfolders. You have no way to know if a small numbers of all your sfv files is not being loaded at all.
1.
Add total number of checksum files analyzed/loaded at the bottom of the file checksum window.Result: WWWW checksum files analyzed, xxxx files OK, yyyy files failed, zzzz files missing
This lets the user to compare the number of checksum successfully loaded against the total checksum files. At least gives some clue about some of them failing to be read or missing files. If you have X folders and you expect to have the same number X of checksum files, it becomes really helpful.
2.
Warn about checksum files not being as expected. For ex... 0 byte checksum files, checksum files without any CRC stored, etc. Corruption is easily identifiable no need to make complex analysis. If you load a sfv file but it can not be checked as sfv then I expect the program to warn me about it, not just omitting it.
Show them the same failed checksum files or missing files are also shown in the result window, and maintain them after clearing successful from list.
3.
Delete individual entries, something simple, just "supr". There is a clear all and clear successful from list options, but can not remove an specific checksum file from the list, independently of its status. Really useful when you are working with the final failed results to recover the wrong files or have to recreate the checksum file (since it is not reloaded from disk but memory once it's on the list).