Please consider upgrading to the latest version of your browser by clicking one of the following links.
Intel Custom Resolution Not Showing Manual Says ItsThe manual says its native resolution is 1440x900, or 1680x1050, or 1360x768, but those resolutions are not showing up as selectable in Display Properties.What do you do to unlock the full resolution potential of your monitor.In fact, I still recommend PowerStrip for overscanunderscan, and for people who just dont want to get down and dirty with their system in order to get better support of their monitor.
![]() These should work on both WinXP and Vista; possibly Win2K and others, too, but to my knowledge no one has tried those. One of many things VESA has established over the years is an interoperability helper known as the Extended Display Identification Data. Over VGA, DVI, HDMI, and probably UDIDisplayPort too, a video driving device (video card, consumer electronics device) can query the monitor to see what its capable of. Execute it with your monitor connected and you will get a load of information back which includes the EDID block. Its all in an obscure VESA spec somewhere, though a good deal of data can be found at the standard Wikipedia site for EDID. What we care about is in one of up to four Descriptor Blocks starting at byte 54: in any or e Descriptor Blocks we can find a string of 18 bytes called the DTD, or Detailed Timing Descriptor. In some cases, there may be more than one DTD listed because the monitor manufacturer has chosen to provide detailed timings for other modes-- possibly because they have an in-line scaler which works best with specific input timings. Consider all of these for your use, but the most important one for our purposes is the one which matches the native resolution of your display. In most cases (as in the example given), that will be the only one provided. If there are more than one, the best way to decide which to use, if you know what your monitors native resolution is supposed to be, is to do a brief decode of the DTD parameters. Intel Custom Resolution Not Showing .Exe Or WhateverWhen you run setup.exe or whatever executable installs the new software, one thing which occurs is that one or more.INF files are parsed and used to determine which registry entries need to be created and modified. Intel Custom Resolution Not Showing Drivers By DefaultIts when you get away from the standards and into the more interesting panel displays and plasmas that you cant seem to get what you want out of the drivers by default. Many of Intels OEMs (Dell, HP, Gateway, etc.) bundle their machines with monitors with nonstandard resolutions; since the drivers are so picky, how do these OEMs guarantee that their customers machines run the right resolutions to provide the best display to the bundled monitors if Intels drivers dont support them by default. If these fields are filled, new resolutions miraculously become available. Open the appropriate.INF file in a text editor and search for. We dont like that. Change it to 1 (or, if youre planning on extra resolutions besides the one, change it to 5). The last two bytes I have no clue about; I just leave them as the default (which, in this case, is 37,01). ![]() Now run setup.exe in the driver directory to install the Intel drivers. In this case, your custom DTD should be included in the list of permitted resolutions (you may have to uncheck Hide modes this monitor cannot display).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |