Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
Boots up, and plays, but incorrect sprites – most noticeable little bug changes into ‘END’ at one point. Check 74ls138 at 8n, controlling graphics banking, and pins strobing. Replace chip and now uses correct sprites. Quiet missile sound and explosion sound. Both of these effects use the op-amp chip, LM324 at 7T. Replace this chip…
Totally dead, no screen display (blank white screen). For this I used the Fluke Z80-S2650 adapter to check out the ram and rom, and located two errors. The rom mapping was incorrect, with a large range of locations returning random values. Examining the board (since I have no schematics), all of the chip select lines meet up…
No display – When move board, display flickers – go around board pushing each chip in turn, when press on 2E picture appears. Pin 16 rusted, only just in place. replace chip – picture back to normal. No star display. Board had been hacked to play an alternate game, pin 15 on chip 2B had…
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…
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….
The board originally failed to get into the game, instead resetting just after drawing the ‘MISSILE COMMAND’ logo. Test mode faired a little better, managing to report RAM OK, MAP OK and ROM OK before resetting. Ram and Rom checked out OK using the Fluke. Measuring various CPU signals revealed that the interrupt seemed very…