Just installed Windows 8 and downloaded the Catalyst version which ATI website recommended. However it says that it can't start! My main monitor is connected to my PC via a HDMI cable and the display is not full screen (there is a blank padding area around display). Usually I change overscan/underscan settings in CCC to reset it but since I have no access to it, I wanted to know if there is any way I can change it without CCC (through registry maybe?) Thanks.
Change Overscan/Underscan settings without Catalyst Control Center
amd-catalystdisplay-driverdisplay-settings
Best Answer
I've had extensive discussion about the overscan/underscan dilemma with AMD developers who work on the Catalyst drivers.
The basic idea is that AMD would rather underscan some people whose HDMI displays don't overscan, and create too small of a picture (blank spaces around the picture), rather than not underscan and cause people whose displays always overscan (with no setting to change it and incorrect EDID information) to have the desktop display too large. The argument is that if the desktop is too large, then the user can't see where the Catalyst icon is or the start menu, and they therefore can't navigate the UI in order to make the appropriate change. So they are sticking to their guns on underscanning by default on HDMI to ensure that nobody gets stuck with a desktop that's too big for their screen (with UI elements hanging "off the screen").
I don't agree with the policy, but that's the way it is. It also seems to be a fairly unique decision among graphics driver developers, as I can't reproduce the weirdness on a number of other non-AMD devices: Android tablets, Nvidia cards, and Intel on-chip graphics.
There is a way to directly tweak the underscan/overscan on Linux by modifying values in the "PCSDB" (Persistent Configuration Store Database). I don't know what the equivalent is on Windows, or if you can even read/write the settings without using Catalyst.
I can't personally test this solution, but it appears that it worked for people on fairly recent drivers, so give it a shot: go to Tom's Hardware or I'll just re-post it here:
Here is a quote from an AMD source (who will remain anonymous) from several years ago about their HDMI underscan/overscan policy. Note that this applies to both Windows and Linux.