English Amiga Board - View Single Post

PeterK · 04 April 2012, 17:25

Maybe this could be fixed with "PatchOverscan" in the startup-sequence.

Usually, the settings are like this: C:PatchOverscan ID=monitorid O=M 0 0 799 599

So, you could try out to shift it: C:PatchOverscan ID=monitorid O=M -2 0 797 599
either to the left or to the right: C:PatchOverscan ID=monitorid O=M 2 0 801 599

O=N for normal overscan and O=M for max overscan

Update: The SuperPlus monitor seems to have fixed values, sorry, Overscan Prefs can't be used. But there are tools like MonSpecsMUI to edit the monitor settings. ONLY for experts, like Ratte, who really know what they are doing. Real monitors don't like experiments with random values !!

04 April 2012, 17:25	#13
PeterK Registered User Join Date: Apr 2005 Location: digital hell, Germany, after 1984, but worse Posts: 3,378	Maybe this could be fixed with "PatchOverscan" in the startup-sequence. Usually, the settings are like this: C:PatchOverscan ID=monitorid O=M 0 0 799 599 So, you could try out to shift it: C:PatchOverscan ID=monitorid O=M -2 0 797 599 either to the left or to the right: C:PatchOverscan ID=monitorid O=M 2 0 801 599 O=N for normal overscan and O=M for max overscan Update: The SuperPlus monitor seems to have fixed values, sorry, Overscan Prefs can't be used. But there are tools like MonSpecsMUI to edit the monitor settings. ONLY for experts, like Ratte, who really know what they are doing. Real monitors don't like experiments with random values !! Last edited by PeterK; 04 April 2012 at 19:11.