Ah, I see I misunderstood your offer. I thought you wanted to post the list of md5 hashes. That's why I suggested Pastebin. Nevertheless, many thanks.

I do not have Python environment setup on my computer (never actually use or learn Python), but hopefully someday I will.

I highly recommend it.

As far as scripting languages go, I find that Python combines elegance and power.

And if you need speed, well, there is always C/C++ for that.

I've been musing over it during my commute and I agree with you that my little script is of limited use.

I think I'll extend it to organize GOG downloads in a neat directory structure and check hashes against a refence hashlist stored in a sqlite file.

Got the games released this week and created files for CRC32, MD5 and SHA1 digests which can be found here.

Thanks for that info.

I'll add it to the sqlite file if my ulility.

No problem. If you want any more information (different digests, file sizes and such), just let me know.

It's pretty good so far. Between what you have and what I have, at least 90% of GOG's collection should be covered.

I used a script to generate the DB entries for the game titles.

So far, I entered the info for game files manually. I'm starting to think about creating a script for that, but it's finicky (GOG's naming convention for game files is not 100% consistent).

I think I'll get it working with the games that start with an 'A' and then I'll expend my utility to include more games gradually.

Only games no longer in the catalogue are not covered so it's more like 99.98% :P

And that's only because I can't buy them *cough*and they haven't "accidently" been added to my account..*cough*

Well, I did the Bs as well and you don't have Blood :P.

Thankfully, I have it.

I own all the games in the catalogue. The directory is called "one_whole_unit_blood".

https://sourceforge.net/projects/gogdwnmanager/

Sorry for the delay. Pesky RL responsabilities got in the way of completing this sooner.

Currently, only games starting with an 'A' or 'B' are stored in the DB.

I'll address this as time allows.

3 Reasons:

1) So that you don't have to run the installers when you buy many games at once (say, during promos)

2) So that you can automatically test your collection against future corruption.

3) So that if GOG does future updates on game files, the MD5 of future download won't match and anyone running the utility will come bitching here about it and let us know that there was an update (at which point the utility can be updated with it).

My utility also cut-pastes GOG downloads in a neat directory structure, but that's just additional gravy on top.

I know I always hated doing it manually.

Doing the 'C' presently and you missed some extra material for "Crusader: No Remorse" I think.

My downloader just hasn't rescanned that title yet :P

Please do, my 'c' are incomplete and it's nagging me. A little OCD there I guess :P.