6 Slot – Memory test on power up giving error
Address Write Read
00008000 5555 55FF
Checking with Mame, the memory chips in question were only small, so looking at the board revealed two DIL 5814’s. Chip select signals to these were toggling as expected, so I needed to identify which ram chip was which. Using the test probe I shorted pins 11+12 on one chip, powering on the board now gave read as 51FF so I was looking at the wrong chip. Replacing the other (with a 2018-35) sorted the problem.
Screen filled with coloured lines, unstable, no sync (see above) – check clock signals from horizontal and vertical scan generators (74161’s at 2R,2S,3R,3S) – no signal feeding into pin 2 of horizontal generators. Follow trace back to 7474 at 3N, signal going in, nothing coming out – replace chip and screen display back to normal….
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…
One of the guns on a Time Crisis 2 was no longer registering shots on the screen. Following checks on wiring, cleaning lens, etc. it appeared that the optical sensor (opto) was dead. This is a small PCB in the gun, 2421961100, pictured above. I couldn’t find any schematics or information about the parts used,…
No picture, Hole blown through LOPT. Had problems tracking down replacement – little tip given to me by Hantarex engineer – you can use the LOPT from an MTC9000 as long as you cut pin 2 off. (If you leave it connected, you will get a direct short to GND)
I had a spare bootleg replacement play pack from a Driving force on Galaxian hardware, so I proceeded to trace the circuit and try to identify the ICs used since they all have the IDs removed, other that the one attached as a later addition as IC7. Following the tracing, I used the pinouts to…
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….