|Viewing Issue Advanced Details||aristmk5.cpp|
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06374||Crash/Freeze||Critical (emulator)||Always||Sep 7, 2016, 11:13||Oct 5, 2016, 00:38|
|Tester||Kale||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||Resolution||Fixed||OS||Windows Vista/7/8 (64-bit)|
|Version||0.177||Fixed in Version||0.178||Build||Normal|
|Summary||06374: adonis: Changing System Configuration to anything but game_prg causes a crash|
Attempting to use a different ROM configuration than default game program causes MAME to crash.
Attempting to start a mk5 game with non-game_prg configuration saved in cfg file causes a startup crash as well.
|Steps To Reproduce||Go to System Configuration TAB, change the setting to any value other than game_prg and eventually soft reset the machine.|
This HW has some operator ROMs, that are used for resetting BIOS configuration by installing them in the sockets.
Tested adonis, assume all games do the same.
|Affected Sets / Systems||adonis|
Sep 7, 2016, 14:06
edited on: Oct 5, 2016, 01:26
Exception at EIP=0000000000402ca9 (aristmk5_state::machine_reset()+0x00c9): ACCESS VIOLATION
Sep 7, 2016, 14:10
Sep 27, 2016, 10:00
|Fixed by Reagan Roush.|
Oct 5, 2016, 00:38
Will this affect the ROM loading of the non-US sets? The 'BIOS' parent itself was a dirty hack added to implement swapping in the set chips for the American machines, which are not used at all in other regions - the actual BIOS code is inside the game ROMs themselves (with the exception of casino software, where u7/u11 actually is the BIOS, and u8/u12 and beyond is the game data; when changing one game to another u7 and u11 are kept in place on the PCB). ROM swapping is not done on non-US machines at all unless upgrading from one game to another.
The peset* in peplus.cpp are other examples of set chips, however in this case, there is only one set chip per ROM set rather than being bundled together in a 'peplus' set for example, and to set up the games you swap the game's nvram data across to the peset* data and run that in MAME instead, set it up, then swap the nvram data back to the game and the game should be good to go. Maybe the BIOS loading in aristmk5.cpp should be killed entirely in place of what is done in peplus.cpp, which will also end up splitting the ROMs inside aristmk5.zip.