Just an idea I had when I manually edited a checksum file with the hashes of 4 rather large files and was running the checksum verification to make sure I didn't mess up the folder paths, and realized that any checksum verifier, without needing to hash the contents of a file, would know instantly if a given file actually exists or not (whether it's the correct file is obviously a different story).
So it got me thinking that maybe it'd make sense for HashCheck to first "ping" all of the files in an existing checksum file to see if they even exist before performing any hashes, thereby fully populating the list of any "Unreadable" files rather quickly.
Just an idea I had when I manually edited a checksum file with the hashes of 4 rather large files and was running the checksum verification to make sure I didn't mess up the folder paths, and realized that any checksum verifier, without needing to hash the contents of a file, would know instantly if a given file actually exists or not (whether it's the correct file is obviously a different story).
So it got me thinking that maybe it'd make sense for HashCheck to first "ping" all of the files in an existing checksum file to see if they even exist before performing any hashes, thereby fully populating the list of any "Unreadable" files rather quickly.