Do you get sick of ROMs always shipping with a dumb readme? Are you tired of not knowing what console that pesky .BIN file is for? Do you wish you could stick your game credit someplace besides a splash screen? The UROM format is for you! So read this! And after you're done reading that, here's an example Python script that can add, read, and delete UROM footers from ROM files: Yes! Right here! (Please note that script is a proof of concept, and as such it has next to no error handling, and is not built to be reliable.) Thanks a bunch!
As I mentioned in #SSRG last night, the 'file' utility does a pretty good job at filetype identification. I recently submitted a bunch of new definitions for various consoles that have identifiable headers, which will be included in the next release. There's a few other noticeable issues with this footer: The "ROM" name listed doesn't indicate the revision or checksum (CRC32, MD5, etc) of the original ROM. The date format is not specified. The example date listed, "04042016", is ambiguous; it could be MMDDYYYY (US format) or DDMMYYYY (UK format). The standard ISO 8601 date format is YYYY-MM-DD. The system and revision fields are redundant. Assuming Sega platforms, this can easily be determined by reading the standard ROM header. The same is true for many other platforms. Why is "length of footer" a fixed 4-character field that's interpreted as decimal?
