> > This is one reason I'll always tell people to use the latest MAME, not old versions > > of MAME. The excuse of 'my roms work with old versions' is a bad one, they don't > work > > with newer ones, typically because they were wrong and have been replaced. > > Recommending people keep using old sets, and keep them looking current when they're > > not is just bad for preservation in general because people new coming to emulation, > > especially from commercial backgrounds etc. end up seeing the (stupid) raving > 'THESE > > OLD VERSION ARE THE BEST!!!!' fanboys, without really understanding that it's a > > complete fallacy mostly propagated because people are too lazy to do want to do > > things properly, or don't want to invest in proper hardware. > > > > The problem with console emulation is *far* worse however because most of the > > dedicated emulators have no way of rejecting known bad dumps so people blissfully > > keep using them and spreading them. This to some people makes the console emulators > > better, because they never need to update their ROMs, but in reality, it just keeps > a > > long-term problem going and causes things like what you're observing here to > happen. > > The only use case I have found for this sort of thing is something like replays with > inp files. Other than that there is pretty much 0 reason to keep the older broken > things. I recently cleaned out about 15 gig of MAME executables and source that for > some reason I had accumulated.
and a lot of the time when inp files don't work anymore is because tiny improvements have been made in the emulation that means they no longer work.
See Donkey Kong.
|