Ok.
Been working on the cab....
I've got good news and bad news.
The good news is that the NOVRAM tested ok in the setup/test menu.All the other tests ran fine, apart from the raster test which seems to be overloading the monitor a bit (still have to re-cap the deflection board).
Also I managed increasing the size of the picture quite a bit ! And I managed to get rid of the poor linearity as well. It looks really impressive, especialy the deathstar blow up
I checked the High Voltage and it was lower than what it should be. So I carefully increased it to the required 19,5 kV. When I took a look at the screen I could see retrace lines in the center, so I quickly turned the HV back to the original level. It looks fine that way, and it's safe
I also tried to up it to the max for a second or 3, and it never reached the 25 kV that is needed to kick in the HV overvoltage protection. So I can safely play without being X-rayed.....
I fired the PCB up with the jumper wire that I created to repair the broken trace on the vector PCB. When I opened it, I got a lot of (quite interesting) retrace lines......so obviously I had managed to create that broken trace myself
. Anyway, easy fix, and it worked great for quite some time.....
The bad news is, that while trying to set a record to see if the NOVRAM really still works,something went wrong on the vector PCB....
All of a sudden, the Star Wars logo was screwed. I switched to set-up and ran the hardware tests (I had run them without errors before). I got an error on VG (Vector Graphics) RAMS at 4P and ROM at 1L with some hex code.....
I tried reseating the indicated chips, cleaned the pins, no improvement. The game actualy still plays, but the fireballs look wrong, there's only partly text on the death star and the worst thing, the game crashes when going into the deatstar level for the 2nd time. Must be the vector generator being confused by the bad data from the RAM/ROM.....
SOoooooooo, I'm heading to the electronics parts store, get some new, wire wound chip sockets and check the traces.....
I think it's strange that it's indicating both a bad ROM AND a bad RAM all at the same time. Gotta check the schematics if there's some driver IC or anything that could also be faulty...