Performa
Member
When I went to VCFMW, I had a fairly short list of things I was looking to come back with. One of those was a multisync monitor- a flat panel monitor that can take a 15KHZ signal from an Amiga, Apple IIGS, and some other oddball computers without an issue. They sold out immediately at the VCF show, but on my way out the door I spotted a lone Samsung Multisync sitting on the free pile, and on a whim I grabbed it. Worst case scenario, I'd have to throw it out.
When I got it home, it took the signal from the Amiga, but only displayed the edge of the screen, as if it was badly over scanned. Unfortunately, there was no way to adjust this in settings. So I tried plugging it into a PC, and it worked fine, automatically adjusting to the PC's output. Then, I unplugged the VGA cable while the monitor was still running to the PC, and plugged it back into the Amiga. This was the result:
There are some weird black and blue boxes around the edges, but it does "work" in this configuration. At least until the monitor or the Amiga are reset- then the monitor "auto adjusts" itself and overscans the screen out of sight. Plugging it back into the PC for a moment fixes it again for the Amiga. I have no idea why it's doing this, nor why this odd fix works, but it was too weird not to share.
When I got it home, it took the signal from the Amiga, but only displayed the edge of the screen, as if it was badly over scanned. Unfortunately, there was no way to adjust this in settings. So I tried plugging it into a PC, and it worked fine, automatically adjusting to the PC's output. Then, I unplugged the VGA cable while the monitor was still running to the PC, and plugged it back into the Amiga. This was the result:
There are some weird black and blue boxes around the edges, but it does "work" in this configuration. At least until the monitor or the Amiga are reset- then the monitor "auto adjusts" itself and overscans the screen out of sight. Plugging it back into the PC for a moment fixes it again for the Amiga. I have no idea why it's doing this, nor why this odd fix works, but it was too weird not to share.
