No dipshit, the .inf file ATI is using set the timing way to high. You
never use the optimal or adapter defaults? Vid drivers are supposed to
read the monitor .inf file but it looks like ATI drivers don't. Do
some research dork.
Here's your research, dork. Perhaps you should do some of your own,
rather than puke out what you've heard from others.
From ATI:
"...There have been many posts in the forums discussing this issue, it
seems it is a common theory, picked up from one place and keep being
circulated. One such theory suggests the following: “Instead of reading
the refresh rates from the PRIMARY display INF files, it is reading the
SECONDARY display INF refresh rates.”
In XP and 2K, we don’t have access to monitor INF information in our
driver component that manages display capability. We have never used
this monitor information for any purpose. We rely on EDID data or user
override information to determine monitor capability. Even though the OS
may use the monitor information to expose high refresh rate based on
monitor INF content, the driver always restricts the actual refresh rate
going to the monitor based on EDID or the user override. In essence, the
user may be able to select from OS controlled monitor page (in advanced
property pages) a high refresh rate but internally driver will restrict
the refresh rate going to the monitor based on EDID information or user
override information. If user set the override information incorrectly
then incompatible signals would be sent to the monitor. In 9x, we can
access monitor INF information but due to issues with how OS maps the
INF to a monitor, we had disabled reading the monitor INF via registry.
Unless someone deliberately changes the registry setting for this in 9x,
they would not run into any monitor INF related issues..."
