Feature request for SFV Ninja: add an option to persist checksum results to a specified output file at fixed intervals (e.g., XX mins), so that not all progress is lost upon a system crash.

In my use case, I'm running checksums against large amounts of data that take multiple hours to complete, so a system crash part way through is quite annoying. For me personally, persisting only the completed checksums is perfectly fine: i.e., have the user be responsible for reconciliation/adding back incomplete files.

I'm liking the pause button in 1.3.3 but miss the ability to scroll while performing the checksum (the middle portion is grayed out/non-interactive). Any chance you could add that back?

Both these items should be addressed in the latest version I just uploaded.  Please test and let me know.  Links at bottom.

-skwire (December 26, 2014, 10:59 PM)

Thanks, they both work great. It's much faster now!

The timestamp data is not currently pulled for each file so I'm not certain how much cumulative time this would add.  So, how important is this feature to you?

-skwire (December 26, 2014, 10:59 PM)

It's nice-to-have but not critical: the drives I'm CRC'ing are largely append/read-only, so it's not too hard to sift through the bad CRCs and figure out if it was because the file changed. I guess if most of your files are always changing, stale CRCs will be pretty useless.

I haven't ever developed in Windows, so my guess was that if it were anything like Unix, where stat-ing a file will give you a struct with both file size and timestamps, it wouldn't add any disk overheads (since you're already scanning for file sizes). If that's not the case, it'd probably take twice as long in the worst case (an additional scan, no caching).