Madaracs
Well-known member
WG6100 on Star Wars Monitor/Board Adjustments? X-Size maxed.
Here's the situation: The low voltage section on my deflection board burned out twice. Long story short I had to wait for a faulty LV2000 board to come back from Jeff Hendrix which he graciously fixed. He rocks.
In the meantime, it was suggested that one of the chassis transistors may be causing a fault on my deflection board. I replaced all of the "bottle-cap style" 2N3716 & 2N3792 transistors on the WG6100 chassis and I ordered a different deflection board (same model P314 minus the Atari input protection board that my original had) which had a new LV2000 installed on it.
After the repair and putting in the new deflection board, everything worked swimmingly when I started it up except that the screen size had shrunk a bit. Here is an example image:
I put the game into test and adjusted the Y-Size and X-Size pots on the AVG board.
I had to max out the X-Size pot to have it fill the screen. So I decided to back it off a bit just because I don't know if:
a. That might be over-driving the X-Size on the AVG board or something?
b. I had to adjust it to make the text look right.
The LV2000 voltage settings are -26.04 and +26.08.
Ultimately I settled on something a screen size slightly smaller than had previously been adjusted to. I can still clearly see the alignment dots on the screen as seen in this example:
My issue is:
Now when the death star explodes and/or when the scrolling text goes by in attract mode it's getting kind of bunched up on the right and left side of the screen. Not terrible but noticeable. Also, I'm not sure I'm supposed to see the blue dots.
My questions are:
1. Is the X-Size pot being maxed a bad thing?
2. Are there other adjustments on the WG6100 I can make (Purity rings?) to fully utilize my monitor's landscape in both X and Y directions? Would upping the voltage slightly on the LV2000 help?
3. Am I supposed to see the blue dots?
I realize this might not be the exact spot for this... Could be a monitor issue could be a board issue... I suspect monitor so I'm puttin' it out here first.
Here's the situation: The low voltage section on my deflection board burned out twice. Long story short I had to wait for a faulty LV2000 board to come back from Jeff Hendrix which he graciously fixed. He rocks.
In the meantime, it was suggested that one of the chassis transistors may be causing a fault on my deflection board. I replaced all of the "bottle-cap style" 2N3716 & 2N3792 transistors on the WG6100 chassis and I ordered a different deflection board (same model P314 minus the Atari input protection board that my original had) which had a new LV2000 installed on it.
After the repair and putting in the new deflection board, everything worked swimmingly when I started it up except that the screen size had shrunk a bit. Here is an example image:
I put the game into test and adjusted the Y-Size and X-Size pots on the AVG board.
I had to max out the X-Size pot to have it fill the screen. So I decided to back it off a bit just because I don't know if:
a. That might be over-driving the X-Size on the AVG board or something?
b. I had to adjust it to make the text look right.
The LV2000 voltage settings are -26.04 and +26.08.
Ultimately I settled on something a screen size slightly smaller than had previously been adjusted to. I can still clearly see the alignment dots on the screen as seen in this example:
My issue is:
Now when the death star explodes and/or when the scrolling text goes by in attract mode it's getting kind of bunched up on the right and left side of the screen. Not terrible but noticeable. Also, I'm not sure I'm supposed to see the blue dots.
My questions are:
1. Is the X-Size pot being maxed a bad thing?
2. Are there other adjustments on the WG6100 I can make (Purity rings?) to fully utilize my monitor's landscape in both X and Y directions? Would upping the voltage slightly on the LV2000 help?
3. Am I supposed to see the blue dots?
I realize this might not be the exact spot for this... Could be a monitor issue could be a board issue... I suspect monitor so I'm puttin' it out here first.
Last edited:

