What's new

About namco system 11 c431 keycus(dancing eyes)

RepairGuy95 said:
Whats left? 1 to go?
@pierpa86 system 12 next?
Click to expand...
So now, the last game are myangel3 but there is a little problem, its use 8MB graphics banks.
The only one in list so no way to test it without recompile mame without keycus.

ROM_REGION32_LE( 0x2000000, "bankedroms", 0 ) /* main data */
ROM_LOAD16_BYTE( "kqt1prg0l.ic2", 0x0000000, 0x800000, CRC(d67eee66) SHA1(1842e987ae406ac2cf4c173aaaa73b5f67f4fd3d) )
ROM_LOAD16_BYTE( "kqt1prg0u.ic5", 0x0000001, 0x800000, CRC(4d1c7bf3) SHA1(6bf9712264a82920f7898896643d05a6b425e74a) )
ROM_LOAD16_BYTE( "kqt1prg1l.ic3", 0x1000000, 0x800000, CRC(298d8eeb) SHA1(c421b1bdd5fd46c026a41e2cec47cafd1a69d33d) )
ROM_LOAD16_BYTE( "kqt1prg1u.ic6", 0x1000001, 0x800000, CRC(911783db) SHA1(1005fc9b38e212844e397150a6f98f43ad88d4b9) )

One more question, anyone really are going to play this game ?
 
got some tekken with this audio adapter.
i will copy that pcb.

WhatsApp Image 2026-04-14 at 14.03.19.jpeg
 
Are the PCB's the funny pinout to regular, or is this the adapter to change it to the funny pinout?

I know some namco mask roms are very strange - when dumping hammer champ i had to do some funky bank switching / file combine to get a good dump
 
pierpa86 said:
Tekken 2 Ver.B (World, TES2VER.D) - Done
Thats was hard

Remember that Tekken use different ic order.

ROM_REGION32_LE( 0x1000000, "user2", 0 ) /* main data */
ROM_LOAD16_BYTE( "tes1rom0l.ic6", 0x0000000, 0x200000, CRC(fc904ede) SHA1(cea378ba86f94beadb3d67685f1b8c141f478abe) )
ROM_LOAD16_BYTE( "tes1rom0u.ic5", 0x0000001, 0x200000, CRC(57b38f5d) SHA1(edb4beab47b1339a5b1bc8071086abfcba57722e) )
ROM_LOAD16_BYTE( "tes1rom1l.ic8", 0x0400000, 0x200000, CRC(aa48f04b) SHA1(f7383d2b3a84c4e649a27c0ad1e6af4702ec0a17) )
ROM_LOAD16_BYTE( "tes1rom1u.ic3", 0x0400001, 0x200000, CRC(b147c543) SHA1(c4b18c218999ec73d04c92e06fb3e6165ceebf2b) )
ROM_LOAD16_BYTE( "tes1rom2l.ic7", 0x0800000, 0x200000, CRC(b08da52c) SHA1(31fe2021d0fe37c16555650dd10d26ed80d9b493) )
ROM_LOAD16_BYTE( "tes1rom2u.ic4", 0x0800001, 0x200000, CRC(8a1561b8) SHA1(ebc02c9e7033d54aefb5034c97a3c8cd749b5600) )
ROM_LOAD16_BYTE( "tes1rom3l.ic9", 0x0c00000, 0x200000, CRC(d5ac0f18) SHA1(342d063f7974bd1f90b5ca4832dfa4fbc9605453) )
ROM_LOAD16_BYTE( "tes1rom3u.ic1", 0x0c00001, 0x200000, CRC(44ed509d) SHA1(27e26aaf5ce72ab686f3f05743b1d91b5334b4e0) )


ROM_REGION32_LE( 0x1000000, "user2", 0 ) /* main data */
ROM_LOAD16_BYTE( "so1rom0u.ic5", 0x0000000, 0x200000, CRC(e364d673) SHA1(70fd58fb912939c57e3a5fadd01c1467df08d4ac) )
ROM_LOAD16_BYTE( "so1rom0l.ic6", 0x0000001, 0x200000, CRC(9c5b0858) SHA1(f3ac726f1167551beea7edc46e43b826b7baaf62) )
ROM_LOAD16_BYTE( "so1rom1u.ic3", 0x0400000, 0x200000, CRC(8f9d8c5b) SHA1(ac1da70854eee344a645749f564366ceac571767) )
ROM_LOAD16_BYTE( "so1rom1l.ic8", 0x0400001, 0x200000, CRC(4406ef16) SHA1(c86f199fdb1db23e5944ca51e6518b9cd0dafb71) )
ROM_LOAD16_BYTE( "so1rom2u.ic4", 0x0800000, 0x200000, CRC(b4baa886) SHA1(0432692a4d71a3f1b47707efb6858927744940e4) )
ROM_LOAD16_BYTE( "so1rom2l.ic7", 0x0800001, 0x200000, CRC(37c1f66e) SHA1(13a8a73fce142ea5ebe3f0c1050e44a027ab42a6) )
ROM_LOAD16_BYTE( "so1rom3u.ic1", 0x0c00000, 0x200000, CRC(f11bd521) SHA1(baf936dec58cebfeef1c74f95e455b2fe74eb982) )
ROM_LOAD16_BYTE( "so1rom3l.ic9", 0x0c00001, 0x200000, CRC(84465bcc) SHA1(d8be888d41cfe194c3a1853d9146d3a74ef7bab1) )
Click to expand...
I'm not sure if the order you mentioned is the same as what I've experienced. I have several Tekken 2 sets. I desoldered some chips from the ROM boards to test them. Two of them had CRC values matching MAME's, but there was a swapped pair ， for example, 1U on the actual board corresponded to 1L in MAME, and 1L on the board corresponded to 1U in MAME. I didn't expect that when desoldering. I ended up soldering them back according to MAME's order, and the ROM board stopped working.


There's also a more unusual one: in MAME, all different versions of TES1 have IC1–IC9 as the same. But I have one board where all the silkscreens say TES1, yet the data on IC1–IC9 is completely different from MAME's. That board's KeyCUS（all marked C408） isn't interchangeable with the others either ，if I only swap the ROM board, I get an 'ERROR KEY' message.
 
crazyjojo said:
I'm not sure if the order you mentioned is the same as what I've experienced. I have several Tekken 2 sets. I desoldered some chips from the ROM boards to test them. Two of them had CRC values matching MAME's, but there was a swapped pair ， for example, 1U on the actual board corresponded to 1L in MAME, and 1L on the board corresponded to 1U in MAME. I didn't expect that when desoldering. I ended up soldering them back according to MAME's order, and the ROM board stopped working.


There's also a more unusual one: in MAME, all different versions of TES1 have IC1–IC9 as the same. But I have one board where all the silkscreens say TES1, yet the data on IC1–IC9 is completely different from MAME's. That board's KeyCUS（all marked C408） isn't interchangeable with the others either ，if I only swap the ROM board, I get an 'ERROR KEY' message.
Click to expand...
Yes, got the same problem check here:
pierpa86

Thread 'Tekken 2 Rev.B Error in the existing dump.'

Hello everyone, I'm reassembling the daughter of Tekken B daughter following the ROM Name files:

and this is the real board:

DSC_0057.jpg


Check here, this is the current dump:

1751662201018.png


So this is should be the correct name:

1751662474546.png
  • Like
 
You must log in or register to reply here.
Back
Top