summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author Robbbert <Robbbert@users.noreply.github.com>2018-09-08 12:28:38 +1000
committer Robbbert <Robbbert@users.noreply.github.com>2018-09-08 12:28:38 +1000
commitc00fbed1c07cbd3715b6c88ad5758fa413289d99 (patch)
treed7e8bead43261bfad582319b288ca6badcc3f731
parent4297917206b968723e6567dfd342056fe8cbb8fa (diff)
(nw) bounty2 : notes from investigation by iq_132 and myself.
-rw-r--r--src/mame/drivers/zodiack.cpp7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/mame/drivers/zodiack.cpp b/src/mame/drivers/zodiack.cpp
index 10e379f8640..705d99273af 100644
--- a/src/mame/drivers/zodiack.cpp
+++ b/src/mame/drivers/zodiack.cpp
@@ -86,6 +86,13 @@ Notes:
ALL ROMs 2732
ALL PROMs MMI 6331
+Bounty2:
+- First 0x100 bytes of the first rom contains a screen that appears if the protection fails.
+- The PCB uses a large CPU epoxy module marked "CPU PACKII". A battery can be spotted through the epoxy.
+- If you copy the first 0x100 bytes from "bounty" then the game works.
+- Therefore, it can be surmised that the epoxy blob contains a static ram or similar with
+ the first 256 bytes of the real game's rom, for as long as the battery lasts.
+
***************************************************************************/
#include "emu.h"