Custom Resolution Utility (CRU)
|
02-21-2015, 07:46 PM
Post: #1247
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(02-21-2015 05:49 PM)MS-DOS Wrote: 1. Is there a way to import standard extension block as a template for a custom one? Mine is empty.Use a program like GetEDID to export the full EDID to a file: http://devgurus.amd.com/servlet/JiveServ...ID-1.2.zip Then import the file into CRU. You will probably have to set "Default extension block" before exporting to remove the extension block override. I really wanted to integrate something like that into CRU, but that would require driver-specific methods, and I haven't found a way to determine which monitor belongs to which entry in the registry, especially if multiple monitors have the same exact EDID. (02-21-2015 05:49 PM)MS-DOS Wrote: 2. What is the difference between No extension block and a disabled custom one?Disabling a custom extension block leaves it in the registry, while "No extension block" removes the extension block override. There should be no functional difference. |
|||
« Next Oldest | Next Newest »
|