AMD/ATI Pixel Clock Patcher

[MS-DOS]

(08-10-2013 07:13 PM)ToastyX Wrote:  If the refresh rate gets added but the monitor won't display it, then it's a monitor limitation, not a driver limitation. Changing the EDID won't make a difference. The monitor doesn't care about the EDID.

I would agree, but based on what cypherix93 said:

(07-30-2013 07:49 PM)cypherix93 Wrote:  I found a weird workaround though - In the EDID, if I set the byte that defines the display input to A5 (DisplayPort), I can get past that 165MHz limit in CRU (adlutil still won't work). I am running at 1080p@85Hz (which is around 203MHz) with custom settings and no problems whatsoever. BUT, AMD HD3D won't work under this configuration. Yes, it works without the EDID override.

...his monitor did care about that small thing in EDID, that allowed to past the limit. So, my previous question remains. It's not that hard to try anyway, I just don't know how to edit EDID directly.