Hi, thanks for this program
Pretty sure I've found a bug with it when running multiple instances on Win7 64bit. To recreate:-
1. Create a checksum file (I used Md5) for a directory containing a few hundred files of around 20mb each (I'm checking .CR2 image files). Save it in the directory.
2. Open TWO instances of SFVNinja by double-clicking the .Md5 file.
3. Start verifying all files in both instances.
Both instances should report a random selection of "bad" checksums.
If you only run 1 instance of SFVNinja or leave one open but not verifying while you verify with the other, then all files are verified as ok. As soon as two instances are verifying at the same time, spurious "bad" results occur.
The same problem occurs if two or more instances are verifying different directories against different checksum files.
I'm guessing it's some kind of threading issue.
I haven't checked if it also happens if one instance is creating new checksums while a second is verifying a different directory, but I expect it does as that's what I was doing when I first started seeing "bad" checksums. The scenario above was created specifically to test for this bug.
This had me very worried that my files were randomly corrupting themselves in-situ for a while!!
Luckily, the workaround (to only run one instance at a time) seems to work, although of course it's less convenient.
I'm using Version 1.1.3 Build 1
Thanks again anyway!