- May 31, 2019
Thank you for that.No problem! I did test one shrunk WinCE game called "Armada" that worked well, at least for the 45 minutes or so that I played it. My plan is to shrink literally everything in the US TOSEC set and try each one, but I can probably start with just the WinCE titles to see how all the rest of them work.
Would you want the "blacklist" to be based on Product ID only, or also the MD5 of the IP.BIN? I ask because changing any flags in the IP.BIN (region, VGA, etc.) will obviously result in an MD5 difference. I observed that games managed using MadSheep's GDEMU SD Card Manager seemed to have different MD5s than the originals, but I haven't done a proper diff of two of them to figure out what's changed.
I'd say that it's better to gather more info than not enough, then we can choose what we will use without wasting many hours on your side.
You're right that mods could change the ip.bin or executable MD5, but they could also change the Product ID (bootsector swap). I'm note sure what the preferred approach would be.
If you could gather, either in a properly formatted CSV or a list of python dict saved with np.savez:
- ip.bin informations (title, product ID, etc) and MD5
- ip.bin MD5 with the VGA flag forced to 1 (should be a matter of changing a single character in memory)
- Main executable size and MD5
- Any other identifying information you can think of that'd survive after mods.
- Working or not after shrinking
My plan is to only do the bin2iso part of the shrinking if a game is in the blacklist. I'll allow an override option of course.