summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author Jonathan Gevaryahu <Lord-Nightmare@users.noreply.github.com>2011-11-10 20:54:25 +0000
committer Jonathan Gevaryahu <Lord-Nightmare@users.noreply.github.com>2011-11-10 20:54:25 +0000
commitc7044089302107c897228eef645ce624b61c03db (patch)
tree292860a3b97a9ebbb56ff6b66185fc1a4d6227ab
parente67817eb4f4993b4b0b06a896def18ca97ae1f96 (diff)
Very minor changes noting something about zeroteamb set. No whatsnew.
-rw-r--r--src/mame/drivers/raiden2.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/mame/drivers/raiden2.c b/src/mame/drivers/raiden2.c
index dc6cbc7f47c..ae965a86a9c 100644
--- a/src/mame/drivers/raiden2.c
+++ b/src/mame/drivers/raiden2.c
@@ -2623,7 +2623,8 @@ of the fg sei251 'key data' to the pcb on bootup (like raiden 2 does) rather tha
keys as programmed from factory (or via the suicide revival kit below); hence this romset is immune to the common
problem of the 3.6v lithium battery dying and the missing keys to cause the sprites to show up as gibberish */
// note: it is possible *but not proven* that this specific set in mame is a frankenstein-hybrid of the japan and us
-// sets, using the sound and char roms from us set and code from later japan set.
+// sets, using the sound and char roms from us set and code from later japan set. This would make sense if it was dumped
+// from a 'fixed, suicide free' modified us board where someone swapped in the later suicideless japan code roms.
ROM_START( zeroteamb ) // No licensee, later japan?
ROM_REGION( 0x200000, "mainprg", 0 ) /* v30 main cpu */
ROM_LOAD32_BYTE("1b.u024.5k", 0x000000, 0x40000, CRC(157743d0) SHA1(f9c84c9025319f76807ef0e79f1ee1599f915b45) )