 No.11933
Tafoid Administrator
Aug 2, 2015, 19:57
|
This broke immediately after 0.163 was released when some other memory change issues cropped up: https://github.com/mamedev/mame/commit/88949a5b47798b3c82851c31b6f801e4fb8ca06f |
|---|---|
 No.11936
Haze Senior Tester
Aug 4, 2015, 17:16
|
yeah, there are some nasty hacks in that driver. first of all it patches the rom, which really shouldn't be necessary. following that it intercepts various writes and uses them to patch the vector table in ROM... makes me wonder if rocnropek isn't a bootleg however, the fact it doesn't need any of this stuff is suspicious. |
|
No.11937
AWJ Developer
Aug 5, 2015, 00:19
edited on: Aug 5, 2015, 00:21
|
The vector patching isn't actually a hack, though it could be implemented in a more modern/savestate-friendly way. I've looked at the schematics and there really is a tiny RAM overlaying the ROM. The patching in the DRIVER_INIT is definitely a hack, though. |
|
No.11941
Haze Senior Tester
Aug 5, 2015, 13:40
|
ok, just struck me as a bit weird writing at 0x8182 to overlay at 0xfff2, but I guess that's just how they configured it, or the read window can be moved? |
 No.11943
Mamesick Senior Tester
Aug 5, 2015, 19:45
|
Hack or not hack the problem is that the opcode in the DRIVER_INIT is xored with the wrong mask. After a quick look at \machine\konami1.c, here' s what seems to be the correct hack to make the game playable again:memregion("maincpu")->base()[0x703d] = 0x98^0x22; /* fix one instruction */
instead of previous:memregion("maincpu")->base()[0x703d] = 0x98^0x88; /* fix one instruction */
I have no idea why this ROM patch is so needed. Maybe a bad dump? Or there's something unemulated in the driver when start button is pressed and cause a reset? |
|
No.11944
Haze Senior Tester
Aug 5, 2015, 22:10
|
well both rocnrope and ropeman suffer from the same issue and have different roms at that position so it seems unlikely to be a bad dump.. maybe the exact type of m6809 inside the Konami1 encrypted CPU is wrong, unfortunately the real time decryption plays hell with the debugger. |