The NEW Build Your Own Arcade Controls

Software Support => GroovyMAME => Topic started by: krick on February 22, 2012, 10:50:35 pm

Title: Microsoft Knowledge Base 2006076
Post by: krick on February 22, 2012, 10:50:35 pm

I wonder if this is related to the resolution switching issues that exist in Windows 7...
http://support.microsoft.com/kb/2006076 (http://support.microsoft.com/kb/2006076)

Title: Re: Microsoft Knowledge Base 2006076
Post by: Calamity on February 24, 2012, 01:17:26 pm

Thanks for posting this.

I don't think this is related to the intelaced/progressive switching issues, but it's definitely interesting seeing how complicated they're doing things that otherwise should be rather simple. Just read this paragraph:

"Certain monitors report a TV-compatibility timing of 59.94Hz. Therefore, Windows 7 exposes two frequencies, 59Hz and 60Hz, for every resolution that is supported at that timing. The 59Hz setting makes sure that a TV-compatible timing is always available for an application such as Windows Media Center. The 60Hz setting maintains compatibility for applications that expect 60Hz.

In Windows 7, when a user selects 60Hz, the OS stores a value of 59.94Hz. However, 59Hz is shown in the Screen refresh rate in Control Panel, even though the user selected 60Hz. :laugh2:"

So, once they decided to reform the video part for their new OS, wouldn't it have been easier and cleaner to just add some decimal figures to the vertical refresh values reported by the OS instead of this sh*t? There shouldn't be any backwards compatibility problems as they could add those features to some new extended structure accessed by EnumDisplaySettings and keep the integer values usable for older apps. After so many years and it looks like the multimedia support for the PC platform is designed by our enemies.