Catalyst 5.7 Still Doesn't Work Correctly on Non Standard Monitors

  • Thread starter Thread starter Will
  • Start date Start date
W

Will

There is a bug - still not resolved in Catalyst 5.7 - where if you are using
a non-standard monitor the Catalyst drivers will allow you to set the full
resolution of the monitor but will not allow you to change the display
properties. Without the ability to change the display properties, the
desktop is stuck at 1600x1200, and higher resolutions must be mapped as a
virtual desktop to the lower resolution.

Normally you overcome this misfeature by setting the display properties
manually in Catalyst, and then the physical desktop expands to full size.
If you have a non-standard monitor however, Catalyst will fail to recognize
it, and under display properties you see the monitor disconnected, and you
are therefore not able to set its properties.

ATI should add a checkbox on the display properties - or on the
troubleshooting button from that page - that forces recognition of the
display. That would let the user override the default buggy behavior.
 
Will said:
There is a bug - still not resolved in Catalyst 5.7 - where if you are
using
a non-standard monitor the Catalyst drivers will allow you to set the full
resolution of the monitor but will not allow you to change the display
properties.
Click to expand...

You call this a bug; some idiot at Microsoft WHQL-testing calls it a safety
feature. It prevents the ignorant user from using a non-supported res or an
excessive refresh rate, which can damage the monitor.
Normally you overcome this misfeature by setting the display properties
manually in Catalyst, and then the physical desktop expands to full size.
If you have a non-standard monitor however, Catalyst will fail to
recognize
it, and under display properties you see the monitor disconnected, and you
are therefore not able to set its properties.
Click to expand...

Normally you overcome this misfeature by installing the custom INF file that
comes with your monitor. INF files can be found either on the manufacturer's
web site or a repository like http://www.monitor-drivers.com/ . Otherwise,
google for it.
ATI should add a checkbox on the display properties - or on the
troubleshooting button from that page - that forces recognition of the
display. That would let the user override the default buggy behavior.
Click to expand...

Have you tried the utility Powerstrip?
 
First of One said:
Normally you overcome this misfeature by installing the custom INF file that
comes with your monitor. INF files can be found either on the manufacturer's
web site or a repository like http://www.monitor-drivers.com/ . Otherwise,
google for it.
Click to expand...

I did try a few INF variants with no luck. I will try the site you
reference as well, but at this point I am afraid to touch the system because
I got it to work through invoking a set of bugs that had desirable side
effects, and I doubt I could duplicate the sequence if you paid me. :)

Have you tried the utility Powerstrip?
Click to expand...

Can you send the URL?

Thanks for the references.
 
Back
Top