j68k

We could then support usage like: ```verifydump --system SomeConsole C:\Games\SomeConsole``` or even infer the system from the folder for just: ```verifydump C:\Games\SomeConsole```

That should be an easy one. I'll try and add that next time I do an update. Thanks for the suggestion!

Should check if there's a good tool for batching this already to avoid reinventing the wheel.

That's an interesting one. Thanks very much for the report!

Ahh, awesome work figuring that out @Z-95! I see that the underlying filename matching module [`fnmatch`](https://docs.python.org/3/library/fnmatch.html#module-fnmatch) supports escaping parts of the pattern and from a quick test it looks like...

I think a nice way of implementing this would be to keep a cache file (perhaps in the folder with the .chd files or perhaps just in ~/.cache or something)....

The reference to the game in the Datfile would need to store enough information so that we could tell if the game has changed in a new version of the...

There could be an option to skip verifying the SHA-1 of previously verified .chd files, since that would just be checking for bitrot/accidental modification. Maaaybe that option should be on...

I thought about writing a standard sha1sum file next to the verified files, with a comment that includes an additional hash of all the game details from the Datfile. So...

Yeah, really good points. I think it's best then if verifydump just does the caching of results behind the scenes to keep things simple for the users. If it can...