Custom Resolution Utility (CRU)
|
10-30-2016, 10:18 AM
Post: #2368
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
>The first number seems to be port-based
The solution is obvious (and used if you read links): this port numbers lay between 0 and 10, maximal value which i see is 9 for eDP connection. So we can simply set all of it. >What if there are two of the same monitor? Which belongs to which? This is first problem for full automation. Not for manual installation if we will give user method to set this port. >How will this conflict when the new drivers support EDID overrides? When intel will support microsoft way - we will use microsoft way. But Intel drivers method work under XP - which never be covered by microsoft. >I also don't have a system with an Intel GPU, so how can I test this? Hmm. This is second problem. But this problem don't stop me in 2005 year to remotely debug _driver_ ![]() >What systems does this trick work on? From very old versions (G31 minimum). >At least this way, I know how it's supposed to work, and it works with both AMD and NVIDIA. See the comment above. >The changes haven't made their way into official releases yet, but it's coming. Ok, but this will work only for newest drivers. Old systems will never get newest drivers. |
|||
« Next Oldest | Next Newest »
|