Mame question

[lisowskikevin]

Hey guys I’ve noticed last night while playing a game in mame about 20 minutes into the game it kicked me back out to the beginning of the game like I hit the reset button or something on it. It gave some in game rom error message that I can’t recall.

Anyone run into this? I’ve dealt with external rom failures before but never an in game error message and odd behaviour. Maybe a corrupt rom?

[PL1]

Hey guys I’ve noticed last night while playing a game in mame about 20 minutes into the game it kicked me back out to the beginning of the game like I hit the reset button or something on it. It gave some in game rom error message that I can’t recall.

Anyone run into this? I’ve dealt with external rom failures before but never an in game error message and odd behaviour. Maybe a corrupt rom?

Some more details might help.   

1. Which version of MAME?

2. ROMname?

3. CRC for your ROM?

4. Is it set to free play?

5. Can you duplicate the error?

6. Any similar bugs for that ROM/driver reported at MAME Testers?


Scott

[Mr. Peabody]

There may be a MAME log event.

[Howard_Casto]

Typically when mame throws an error like that you are running a game with an incomplete driver.  Did you check the game info when the rom started?

[Haze]

Sounds like maybe you simply crashed the game?

Some games have actual game bugs, just like anything else.  There are plenty of examples of 'real game bugs' (note the sheer number of revisions some arcade games have)

Sometimes running things like highscore hacks, or cheats can also break things. (some Taito games have anti-tamper code that is thrown off by this kind of hack)

Also sometimes bootleg sets do this, as the original games had protection that wasn't properly patched out by the bootleggers.

If it's an original set and reproduces consistently (every time in the same place) without you having to do anything that could be considered 'abnormal' to trigger it, then it could be an emulation bug.

Sometimes it can be a genuinely corrupt ROM, eg. with Marvel vs. Capcom in older versions, the parent ROMset was actually a bad dump, this was only found out later, at which point it was replaced.  However if you're running the latest MAME version, and it doesn't report any checksum mismatches while loading you're using the best known dumps at least.

If you're using some ancient version (eg. the 2003 / 2010 builds that some insist on) then the emulation was terrible, all over the shop, and this kind of error was much more frequent due to incomplete protection simulations, bad dumps that hadn't been identified, CPU emulation errors, misguided speedup hacks, limitations of MAME's memory system, and sometimes simply cases of incomplete research etc.  Bonze Adventure for example would quite frequently crash with onscreen messages prior to last year when the protection chip was dumped and emulated.

There are one or two cases where current versions have similar issues (Aaron broke later stages Atari's Rampart last time he did a big Slapstic update, and has never come back to fix it) but those are incredibly rare.

[lisowskikevin]

Thanks guys more than enough info for me to go with. I’m running an older version of mame and I haven’t replicated the error thus far.

I’m not too concerned I just thought I’d throw it out there to see if anyone else has seen it before. As always thanks to everyone who took the time to contribute to this thread.

 

While I have you guys here one more quick question....I’ve been running Windows 7 prof 64 bit intel core 2 duo 2.93 ghz as my engine for hyper spin and my emulators. Any point in upgrading my memory from 8gb to something larger? I do run daphne and model 3 on my machine as well.