Glitched graphics. Screen changes as board is flexed. Moved around board pressing chips until pressing the custom surface mount chip at B6 changed the effect. Noticed that the corner most pins had come up from the board. After an unsuccessful effort to resolder them, I used some enameled 38 swg wire to solder from the affected pins across to a convenient point on the tracks. Having completed this the graphics are back to normal. The wire is very delicate, and located where someone was likely to grab the board to disconnect the jamma connector, so the work was then covered in some hot melt glue to protect it.
Similar Posts
Do Run Run
Crashing game. Game woud start attract mode, but shortly after would crash and boot loop. Entering test mode (hold player 1 start button whilst switching on) and it would pass first time around, but fail at random addresses on subsequent runs. The /WAIT signal on the main Z80 is handled by the IC at E2…
Carnival
Carnival on a Gremlin / Sega Vic Dual PCB. Just had blue bars on screen, although probing the Z80 showed it was trying to run code. Using a logic probe I discovered that the /WRITE signal of the ram chips was always high. This signal comes from a 74LS10 at U77. Checked this chip and…
Make Trax
ByadminBoot up with garbage, quickly clears screen and then nothing. Used Fluke with Z80 pod – read rom OK, and write ram OK, but timeout reading any Ram location. Check fluke status and ‘wait’ always set. Check pin 24 of Z80– stuck low, trace back through 7H,7C,6C1 to 6B1 pin 2 – always low, although…
Frogger (Sega)
Missing Chip. This was a converted moon cresta board. The IC at 1.2S (shoehorned in sideways between rows 1 and 2 by the sprite ram) was missing. This was not featured on any schematics I had, so I traced the connections to see what it could be. It basically takes the output from the sprite…
Gallag
Ran through self test OK, came up with chequer board screen and then reset most of the time. Occasionally would start game, but with credit noise continually playing and credits rapidly counting upwards. This is caused by CPU 4 (E5) not running properly. checked the eprom and ram (C5,D5 and E5) and ram was faulty….