> > What? It's 1 byte, why wouldn't I think that?
> You wouldn't think that an emulator, which openly states that its intention is the
> accurate preservation of digital (and, to an extent, analog) data, would care about a
> byte being changed?
> Were you under the impression that the team keeps track of individual files' CRC32
> and SHA1 hashes just for fun?
> ROM_LOAD( "5e.cpu", 0x0000, 0x1000, CRC(18442c37)
> SHA1(fac445d15731532364315852492b48470039c0ca) )
> When you mistype a password, does it baffle you as to why it doesn't work, because
> hey, "it's just one byte"? Really?
Funny thing is MAME won't actually care, at least if you run it from the command line, it will tell you that the ROM is incorrect then attempt to run it anyway. It's not going to pass an audit or show as available in an unofficial UI build that way because it's not the expected file but there's no actual barrier in MAME to prevent it from running.
Of course it would make more sense to do it with the cheat engine, as a cheat than hacking the files, I thought somebody already had actually.