Raiden Fighters 2 - Doesn't boot (and it's undumped...)

[Nebula]

Hi guys!

I have a Raiden Fighters 2 game cartridge along with a new version of Seibu SPI motherboard (SXX2D v2.1) that works perfectly a while ago.

I have this board for years and it was stored long time ago. Recently I plug it into my cab and sadly saw that the boards won't boot and some static black and white squares appears on the screen.

Knowing the problems that this systems tends to have (checksum error, region error etc..) and this one seems different, first idea that came to my mind was to dump eproms in the cartridge to ensure that all of them are OK. And bingo... one Eprom reads "FF" in all of its registers, more specifically, rom 1 of program data, so it is

I though: "OK, I only need to replace it with a new one with data from the proper mame romset", so next thing was to identify the romset of this cartridge with the help of romident and using every single romset from mame. Here is when I shit on my pants and rant in everything....

This romset is still not available in mame...

romset is made up of
-4 program eproms
-1 for sound
-3 for text layer
-(and other smd roms for graphics that I didn't dump)

First program rom labeled "SEIBU 1" is the fail one. But there is something strange with the rest of the roms:

-Sound rom ("SEIBU 8") is the same for all sets.
-3 text layer roms (labeled "SEIBU 5", "SEIBU 6" and "SEIBU 7") are exactly the same as: rdft2 (europe), rdft2u (usa set 1), rdft2u (usa set 2), rdft2j (japan set 1), rdft2jc (japan set 4), rdft2a (asia set 1)
-3 other program roms (labeled "SEIBU 2", "SEIBU 3" and "SEIBU 4") are the same as: rdft2jb (japan set 3)

There is no other romset with the same combination of program/text roms.

Then I also realized that every romset has an unique program 1 rom. None of them are the same between sets.

I tried to burn some program 1 rom from other romset but obiously it boots with checksum error:

At this point, I am really sad because this romset is undumped and I have this game long time ago without knowing that, and it cannot be repaired until it will be eventually added to mame or someone dumps it. I am pretty sure that this game is from asia region according to the previous owner, so probably it would be "rdft2ab" (as rdft2aa already exists in mame)

One workaround to repair the game could be reburn 3 other program eproms with data from "rdft2a" to avoid errors from region check and checksum check, but I would like to maintain it as original and add it this unique set to mame.

So I make a call to everyone who has this magnific game to check if someone has this undumped version and can help me (and everyone else adding it to mame) providing the contents of that eprom.

Thanks in advance !

 

[nem]

Good timing, I just dumped mine:

Seibu SPI region changer -SPI REVIVE-

Cart looks the same, so could be the same revision?

Send me a PM and I'll send you the Seibu 1 file to try out.

 

[Nebula]

I could be the same revision, but there is a lot of them even inside the same region.

Mine is one from Asia region for sure but, as I posted in OP, roms 2, 3 and 4 are the same as those in "rdft2" but 5, 6 and 7 aren't. Last ones are the same as those in "rdft2jb". This combination is not registered in any romset from mame, so I suspect I have an undumped asian version. Rom 1 is (unfortunately) different in every single set.


Did you try to identify which romset is your cartridge from?


Anyway I will pm you to try your file out. Thanks a lot!!!


EDIT: seeing source code from seibu spi from mame, a new "rdft2jc" is added some days ago. Could it be your romset? I also check CRC from files in that new version and they doesn't fit with mines:


My set:

Program roms (same as rdft2jb)

ROM_LOAD32_BYTE("prg1.rom", 0x000001, 0x80000, CRC(a0f09dc5) SHA1(e8ad20be1f04752b0884571384d4490813ed82d9) )
ROM_LOAD32_BYTE("prg2.rom", 0x000002, 0x80000, CRC(368580e0) SHA1(184036a0cbddbf79b62e388b93cb93b885faee88) )
ROM_LOAD32_BYTE("prg3.rom", 0x000003, 0x80000, CRC(7ad45c01) SHA1(d782057658dd000c1cf0a4726a6ed821e6f2be67) )

Text roms (same as rdft2 and rdft2j)

ROM_REGION( 0x30000, "gfx1", ROMREGION_ERASEFF ) /* text layer roms */
ROM_LOAD24_BYTE("fix0.u0524", 0x000001, 0x10000, CRC(6fdf4cf6) SHA1(7e9d4a49e829dfdc373c0f5acfbe8c7a91ac115b) )
ROM_LOAD24_BYTE("fix1.u0518", 0x000000, 0x10000, CRC(69b7899b) SHA1(d3cacd4ef4d2c95d803403101beb9d4be75fae61) )
ROM_LOAD24_BYTE("fixp.u0514", 0x000002, 0x10000, CRC(99a5fece) SHA1(44ae95d650ed6e00202d3438f5f91a5e52e319cb) )

New rdft2jc set:

ROM_LOAD32_BYTE("seibu_2.u0212", 0x000001, 0x80000, CRC(65ee556e) SHA1(13311850aabba9fc373adfd5cd590c114505933f) )
ROM_LOAD32_BYTE("seibu_3.u0221", 0x000002, 0x80000, CRC(d2458358) SHA1(18a9cfee77a6a09584bc3fb0073c822d12de5bf1) )
ROM_LOAD32_BYTE("seibu_4.u0220", 0x000003, 0x80000, CRC(5c4412f9) SHA1(c72603bee3ce14f40d4bf5e3ae3f041b923edd57) )

[...]

ROM_REGION( 0x30000, "gfx1", ROMREGION_ERASEFF ) /* text layer roms */
ROM_LOAD24_BYTE("fix0.u0524", 0x000001, 0x10000, CRC(6fdf4cf6) SHA1(7e9d4a49e829dfdc373c0f5acfbe8c7a91ac115b) )
ROM_LOAD24_BYTE("fix1.u0518", 0x000000, 0x10000, CRC(69b7899b) SHA1(d3cacd4ef4d2c95d803403101beb9d4be75fae61) )
ROM_LOAD24_BYTE("fixp.u0514", 0x000002, 0x10000, CRC(99a5fece) SHA1(44ae95d650ed6e00202d3438f5f91a5e52e319cb) )

Text layer roms are the same, but program roms aren't

 

[nem]

EDIT: seeing source code from seibu spi from mame, a new "rdft2jc" is added some days ago. Could it be your romset?

Yes, that's mine.

Unfortunate. Hopefully other owners will dump their carts.