SF2 World Warrior - Tested good but non-booting rom set

NoAffinity

Well-known member
Joined
Oct 25, 2005
Messages
1,370
Reaction score
92
SF2 World Warrior - Tested good but non-booting rom set

I've got a SF2 WW B board that I thought was bad, but then swapped in the game roms (roms 28-31, 35-38) from a known good game, and it works fine. I take the roms off the B board that was not booting, and a known good SF2 WW set will not boot with them installed.

The roms are all labeled SF2U: 28D, 29B, 30D, 31D, 35D, 36B, 37D and 38D. Note all are "D" except 29B and 36B.

I tested the roms and they all test good and pass verification, against the MAME sets.

The roms all appear to be factory original, with original capcom labeling. Removing two of the labels to reprogram the roms noted below confirmed that they are original.

Recently experimenting with some CPS-2 games, they produce the same result that I'm experiencing here, when roms are mis-matched - no boot, black screen - so I suspected this as the cause with this SF2 set as well.

I referenced this page to try to determine if maybe some roms had been mis-matched:
http://www.solvalou.com/subpage/arcade_roms/S/sf2

That page notes that 29 and 36 (the only "non-D" roms in the set) should be sf2_29a and sf2_36a. So, I reprogrammed these two with the only "a" roms I could find, which were files sf2u_29a and sf2u_36a.

Still no joy.

Next suggestions? I'm assuming I will need to program all 8 roms and just start over fresh. But is there potentially something else causing this issue? Were all other chips on these boards identical between all versions (PAL's, SF2-xM's, etc)?

I have to start fresh by reprogramming all 8 roms, I'd like to update the set to the final US release - 910522 rev. I. Where can I get a complete rom set, with all 8 rom files?
 
The ROM set you have is good, no need to reprogram anything.It belongs to 'sf2ud' MAME set, you can see the 29b and 36b, it's not a mismatch.

* B-Board 90629B-3 */
ROM_START( sf2ud )
ROM_REGION( CODE_SIZE, "maincpu", 0 ) /* 68000 code */
ROM_LOAD16_BYTE( "sf2u_30d.11e", 0x00000, 0x20000, CRC(4bb2657c) SHA1(b2d077296b77be7db371f953b7fc446a67d8a9d6) ) // == sf2e_30d.11e
ROM_LOAD16_BYTE( "sf2u_37d.11f", 0x00001, 0x20000, CRC(b33b42f2) SHA1(2e0babc8734c79dc2b51a6be64433bb2411c3da5) )
ROM_LOAD16_BYTE( "sf2u_31d.12e", 0x40000, 0x20000, CRC(d57b67d7) SHA1(43d0b47c9fada8d9b445caa4b96ac8493061aa8b) ) // == sf2e_31d.12e
ROM_LOAD16_BYTE( "sf2u_38d.12f", 0x40001, 0x20000, CRC(9c8916ef) SHA1(a4629356a816454bcc1d7b41e70e147d4769a682) ) // == sf2e_38d.12f
ROM_LOAD16_BYTE( "sf2u_28d.9e", 0x80000, 0x20000, CRC(175819d1) SHA1(c98b6b7af4e57735dbfb3d1e61ba1bfb9f145d33) ) // == sf2e_28d.9e
ROM_LOAD16_BYTE( "sf2u_35d.9f", 0x80001, 0x20000, CRC(82060da4) SHA1(7487cfc28cce3d76772ece657aef83b56034011e) ) // == sf2e_35d.9f
ROM_LOAD16_BYTE( "sf2_29b.10e", 0xc0000, 0x20000, CRC(bb4af315) SHA1(75f0827f4f7e9f292add46467f8d4fe19b2514c9) )
ROM_LOAD16_BYTE( "sf2_36b.10f", 0xc0001, 0x20000, CRC(c02a13eb) SHA1(b807cc495bff3f95d03b061fc629c95f965cb6d8) )

Try to clean the pins of the EPROMs, probably they are dirty (but some chips could be also altered so they can be read on your programmer but they don't work when installed on PCB, it can happen sometimes).Obvioulsy compare your dumps again MAME database by using the ROMCMP utility, this will tell you if the contents of your EPROM belongs really to this 'sf2ud' set (judging from labels it should be so).
If you want to prepare a new ROM set, you know well where to get ROM files!There are plenty of sites that offer MAME ROM sets....
 
Last edited:
So, I started taking another stab at this, this weekend. I ordered some 27C1001, and burned a complete set, with the intent of swapping roms one by one to find the one that is causing the non-boot.

The new complete set would not bet on either the B board that original had these US Rev D roms, nor on a known good board. Same issue on both. I won't bother fully explaining the symptoms... there was some signs of life but not much.

So, I put the original roms back in, and had noted in my research that the US Rev D roms are associated with the C board containing CPS-B-05. So, I first replaced a missing CCX ceramic capacitor on that board from a parts A board, and then married up B and C board.

I then tried the pair on a soundless A board that I haven't yet gotten around to troubleshooting the sound issues, but is otherwise working.

And it came up with 90% success. Some graphics issues, as you will see below.

I then tried the pair on another A board, one I am working through tracking down sound cutting out after 5-10 minutes. And, I got the same result - 90% success with the graphics issues you see below.

I then tried a CPS-B-17 C board, and got a no boot. According to the below link, only a couple of C boards are interchangeable. I suspected that to be true, and that the '17' C board and '5' C board are not interchangeable. My testing seems to support this.

http://www.arcadecollecting.com/info/cps-b_numbers.html

So, with 2 A boards which are presumed 'known good with audio issues' producing the same result (aka it is not a A board custom causing the problem), where to look next?




Anomalies at the fence

Anomaly at the street, at the sidewalk corner. Also, the black blocks which are more obvious.



Anomalies in the roof and the floor.
 
Last edited:
CPS-B-05 and CPS-B-17 are not interchangeable.Are you using the same B-BOARD?If yes, I'd check the MAKS ROM as well as sockets.Can you use a good known CPS-B-05 in order to rule it out?
 
^Yes, 2 known good A boards produce the exact same results. If I take them to a known good 910214 B/C set, there are no issues.

Same B board in both cases of issues. I did swap in the 910214 roms on this B board, in conjunction with a B-17, and there weren't issues. Unfortunately, this questionable set is the only rev D roms and B-05 that I have.

Thanks for the suggestions, I will start pulling and checking mask roms...maybe even run the board through the dishwasher. It is pretty dirty, possibly there some funk buildup somewhere causing a short.

Will report back once I do those things.
 
Back
Top Bottom