Is it just not recognizing the games (meaning that they are not in the database) or does it do nothing? The new version automatically opens the game ID editor. You can manually select a hash target and its hash and all of the other fields. It lets you open version/QA files and readmes by simply clicking a button. It can also try to get the interpreter version via another button. It has a search menu that lets you search for the release on a number of different sites (the wikis, MobyGames, Wikipedia, etc.) for any missing information. The preview feature allows you to run the game to see what can be found via the About item in the game and the debugger. While invoking the debugger will crash so many of the earlier SCI games (probably missing debug scripts) it will display the interpreter version. The labels of physical media usually has some release information like game version and interpreter version. Later floppy releases used the release date for the interpreter version. Once all of the determined information has been added there is a button that will write a file that can be uploaded where I can simply copy and past it into the database.
I'll have to set some standards for the information, like which file to select for the hash target, usually the map file for SCI games and the LOGDIR for AGI. Booter images are harder to determine as the image file may have any name and you cannot just look for an extension for images as some might have multiple disks. Formatting will need to standardized as well. Probably need to set some naming standards, too.
Going through my collection with the tool has let me fix some issues that were not apparent. It is letting me do some considerable updating the database. Moving it from an external CSV list to an internal C# class makes it far easier to update and to it. Additionally, if the tool gets more widely used there would be a problem maintaining a consistent database with the external CSV list.
