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.
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 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)
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….
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…
Altered Beast – Colours missing, no reds, other colours looked like diminished palette (like windows in 16 colours) – used test mode to perform ram test, and one ram chip identified as faulty (I10). Replaced this and red was back, but still reduced pallette. Looking at colour circuit, and it uses resistor arrays driven by I11…
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…