|
Re: [Solved]Dungeons&Dragons Tower of Doom and Shadow over Mystara Noob Questions
07/20/17 05:42 AM
|
|
|
> Has the similar bug been fixed as well? > I reported MT #3265 way back in 2009 where loading a modified or obsolete ROM set > (with no missing files) via the command line works fine, but in the internal UI it > results in MAME refusing to launch the game even if the exact same ROMs were actually > running in the background. > > "Missing" files and "incorrect" files are two completely different things and should > be treated as such. Loading a matching file but with wrong checksums should not be a > fatal error. > > Back when I found the bug, it was when a certain driver (aristmk4.cpp) had the exact > same filenames for every single ROM set, so simply renaming a zip file was sufficient > to test other games using the same hardware without having to compile MAME every time > on an ancient single core PC, which used to take over three hours on my old Celeron > to do a clean compile of 0.140 or whatever it was back then. > > Coincidentally, MT #3264 (reported by another user) was exactly the same thing but it > was dismissed and closed simply because someone was unable to reproduce the bug, > which would have only needed a matching filename with wrong checksums to reproduce.
Nope, internal UI behaviour is not changed. It's still "don't run if set isn't best available". I can understand why dankan made in behave this way - it potentially cuts down false bug reports if you refuse to run with a bad ROM image. Launching with a "bad" ROM image is treated as an "advanced" operation and requires dropping to the command line.
|
|