summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author davidhay <davidhay@localhost>2009-01-25 12:52:06 +0000
committer davidhay <davidhay@localhost>2009-01-25 12:52:06 +0000
commite75096c53867d6779f0666305f757479eb7eeabb (patch)
tree52d4247de952ab4fe1937f971dbf0c84a4ff0306
parent2fd6773b191fa1dc8e9092ebf07e61ac31ac5e7e (diff)
updated the comment about simulating the magic10 protection slightly. we could simulate it, but it wouldn't really be a good idea.
-rw-r--r--src/mame/drivers/magic10.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/mame/drivers/magic10.c b/src/mame/drivers/magic10.c
index 155926553f7..8159ac89d6f 100644
--- a/src/mame/drivers/magic10.c
+++ b/src/mame/drivers/magic10.c
@@ -66,8 +66,8 @@
and some reads that drive the note displayed?)
- Dump/decap/trojan the MCU in the later games (magic102, suprpool, hotslot, mcolors).
The MCU shares memory addresses at $500000-$50001f (in magic102)
- and it can't be simulated since the game logic is all in there,including
- rngs for the cards and combinations for the points.
+ It can't be simulated with a high level of confidence because all the game logic is
+ in there, including rngs for the cards and combinations for the points.
- Priorities,likely to be hardwired with the color writes (0=tile has the
highest priority).