Recent content by ack

ok, one last thing to try that I can think of. You said that openkey/infinikey worked fine for you with Tenchi wo Kurau II right? On the D board, try using that original d9k pal with your conversion.

Something you might try if its easy for you to reprogram the program roms. In your 23 program rom, do a hex search for this 39 30 F1 00 FE 9F 00 0C 77 00 F4 66 and replace it with this 71 4E 71 4E 71 4E 71 4E 71 4E 71 4E In theory there should be one occurrence of it near the beginning of...

My suggestion would be to burn the punisherj 21/22/23 roms and test with them. If that fixes the issue you know the problem is with your 22/23 roms, if you still get a black screen then its likely pointing at an issue with the kabuki/qsound roms or maybe the GAL on the D board..

The comments on all those entries in mame are just saying the roms from that punisherj romset are the same crc/data as another romset. ie: from punisher romset ROM_LOAD64_WORD( "ps-3m.5a", 0x000002, 0x80000, CRC(0122720b) SHA1(5f0d3097e097f64106048156fbb0d343fe78fffa) ) from punisherj...

Communication between the 68k and z80 cpus happens via the NEO-SDR-T chip. An actual value of 41 on that screen should have printed an additional error message, but sure why it didn't. 41 is what the z80 would send if it detects a crc issue with the diag m1 rom. I would check connectivity...

yeah if you can. Also just to confirm you are using the 0.19a02 m1 rom and not the original 0.19 m1? I forgot if 0.19a02 bios is backwards compatible with a 0.19 m1 rom.

Do you get any beep codes when you run the diag bios + test cart?

lithy already changed the name by having it be the VTX PICKnMIX edition.

Creating an increased version number of someone else software is bad form.

If the gbs-c is saying there is no signal I would start by looking at the sync signal coming from the mvs board.

So the address lines are shared between the 2x 2k ram chips and come from the LSPC chip. The error is indicating you have an issue with one of those address lines (likely A1 or A2). Its effecting both chips so you probably have a bridge to another pin/trace or a cut trace.

heh, I was after images of the screen when its showing the error message not the ram chips. The wrong tiles being displayed can provide info about what is wrong, but I can't make out what tiles they in your original screen shot of the error.

I dont see any images on that page.

That picture is pointing to a data issue with the 32K vram. If you can take a up close and in focus picture it maybe possible to narrow down were to look.

It would be difficult and not sure how well it could be done because of the number pins. I'm curious why you can't use mame for whatever you are trying to accomplish.