ConnieThunder: CRC,MD5,SHA1 are the values used in ROM managers and offer a very simplistic way of scanning/renaming your games. With all values stored in the 'dat' file, it makes for a more 'accurate' and 'complete' file, while giving you the option of selecting which hash value/s to use when scanning - CRC is far quicker, both CRC and MD5 have been exploited (probability aside) though. 
  Not sure what polynomial length was used, but a guy did a performance analysis on Stackoverflow and determined that there wasn't much of a performance difference between MD5 and CRC.  
 It's true that MD5 have been broken and CRC was never meant to foil an attack to begin with, but let's face it, we don't do integrity check on our collection in case some weirdo decides to silently corrupt our GOG files in an undetectable manner. It's hard disk malfunctions we are really worried about.   
ConnieThunder: While I offer the MD5 file types to manually scan a game folder with, using for examples 'md5summer' or 'quickpar', it is a very tedious method if you are just starting to collect GOG or checking your collection.. 
  Well, you can always use the tool I programmed if you find the others tedious.  
 In the utility prompt, you run "verify -m -s *" and then go do something else   
ConnieThunder: clrmamepro and my dat file offer a 'click start' and 'wait' approach and it will check, rename, move outdated files and then inform you of missing games or updated files per game. 
  Almost sounds like my tool, except that mine only reports problems (and lets you decide how you want to address them).  
 I'm now entertaining the notion of it letting you repair bad game folders using a redundant copy if you have one.   
ConnieThunder: As with your tools though, it's only as complete and accurate depending on the collective input from everyone with games and keeping them up to date.  
 ...  
 Will there be updated versions anytime soon - I'm assuming your collection is still growing? 
  Keeping the database update with future updates is actually not that hard, because GOG now warns you when there is an update.  
 It's the updates they didn't warn me about in the past that are giving me issues.  
 My final post in this thread explains why updating the database with my entire collection is slow: 
http://www.gog.com/forum/general/library_size   And yes, my GOG collection is constantly growing.  
 However, JMich has a lot of games too.  
 I'm looking forward to do that merge with what he has once he produces a database which he is relatively confident won't have surplus files. To be fair, there were bugs with the exclusion list in the previous versions (as I don't need to use it myself) so he had to wait for me to fix them.   
ConnieThunder: I'd certainly appreciate your sql files with size,CRC,MD5 and SHA1 support - the more accurate sources I have of all the information I need to collate an up to date dat file, the better. I'm currently using 'SQLite Database Browser' to export and check naming and values against. 
  Yeah, I'll do the fork.