As some of you know, I'm developing a launchbox-like game manager. This manager of mine, will try to automatically detect the games, through a list of .exe and .com that it detects in the folder that the user designates as "games folder", but for him to know who is who, he needs a base of data. It can be MS-DOS and Windows games, no restrictions, all will be accepted.

I need md5 and crc32 hashes. I'm using a free app called HashMyFiles, it can be obtained here: https://www.nirsoft.net/utils/hashmyfiles.zip

Don't worry about junk files (like dxsetup.exe, dos4gw.exe, _isetup.exe) you can send me the raw file, because I already have a cleaning algorithm. I will merge everything with my CSV.

CSV FORMAT:

EXE/COM_NAME.EXE;CRC32 CHECKSUM;MD5 CHECKSUM;GAME NAME AND DEFAULT PATCH;MODIFIED EXE DATE;FILE SIZE (KB);FILE VERSION;PRODUCT VERSION;

Example

settings.exe;29B930E156F9AB0C9007BB7393058082;72F8E809;Grand Theft Auto Include London 1969 (1997)(DMA Design)\gtawin\settings.exe;24/12/1996 23:32;188.416;1, 0, 0, 1;1, 0, 0, 1

How will I use this information:

settings.exe == The name of the .exe or .com. Will be the main research article
29B930E156F9AB0C9007BB7393058082 == is the md5 checksum. MD5 is a little more intensive (on an older computer) than CRC32. It will ONLY be used in cases where the result of CRC32 is repeated (two files with the same CRC32), it will be used to compare.
72F8E809 == CRC32, was chosen because it is fast on older machines (although unreliable), it will mainly validate the exe or com name.
Grand Theft Auto Include London 1969 (1997)(DMA Design) == Name of the folder that contains the game. Some of us store the game in folders with more descriptive names than their executables. If your game is contained in a folder with a short name, or any name, don't worry, this is just to make the database work easier (names not found will be searched in a more complex database)
\gtawin\settings.exe == subfolder where the exe is located. This string is part of the top string, but my software separates them and uses them separately.
24/12/1996 23:32 == exe/com modification date, another one of the mechanisms I use to identify versions, patches, language, etc...
188.416 == size
1, 0, 0, 1 == file version (if there is) not mandatory, will rarely be used for comparison. It will be shown on the frontend.
1, 0, 0, 1 == product version (if there is) the same as above.