What are the conditions that make the method work?
(My system is:
Intel NM10 Express chipset with Intel Graphics Media Accelerator 3150 Driver for Windows XP, Version 14.37.50.4.5260, date 04/24/2010,
an external monitor HP LP2065, native res. 1600x1200.
The netbook (Acer AOD257) manufacturer claims the maximum resolution for the external VGA is 1400x1350, but 1600x1200 is possible with the generic graphic driver that comes with Windows XP.)
I tried both
- the manual method explained by Aaron Brezenski at http://software.intel.com/en-us/articles/custom-resolutions-on-intel-graphics
- and the DTDCalculator
and none had any effect on my system.
So I ask why?
question 1
Shall the method work with any recent Intel driver that injects TotalDTDCount, DTD_x into registry? Or the injection of TotalDTDCount, DTD_x is not a sufficient condition and the method is also limited to certain chipsets? Or there are no clear rules that determine systems where the method works?
question 2
With my computer the higher resolution (oficially unsupported by the netbook manufacturer) works with the generic driver from Windows XP (the one that is used just after the fresh Windows instal) and also with Linux. In this situation is there a possibility the problem may still lie in the BIOS limitations?
question 3
Did it happen already? Did any laptop supplier start to forbid graphic modes in BIOS more effectively ? (I guess they would allow certain graphic modes only, in place of disallowing certain modes.)
What are the conditions that make the method work?
(My system is:
Intel NM10 Express chipset with Intel Graphics Media Accelerator 3150 Driver for Windows XP, Version 14.37.50.4.5260, date 04/24/2010,
an external monitor HP LP2065, native res. 1600x1200.
The netbook (Acer AOD257) manufacturer claims the maximum resolution for the external VGA is 1400x1350, but 1600x1200 is possible with the generic graphic driver that comes with Windows XP.)
I tried both
- the manual method explained by Aaron Brezenski at http://software.intel.com/en-us/articles/custom-resolutions-on-intel-graphics
- and the DTDCalculator
and none had any effect on my system.
So I ask why?
question 1
My chipset (Intel NM10 Express) is not listed there but his article is rather old...Aaron Brezenski wrote in his article :
This trick should work with G35, G33, G31, G965, GM965, 945G/GM, and 915G/GM
chipsets which use the 14.25.50 drivers or later.
Shall the method work with any recent Intel driver that injects TotalDTDCount, DTD_x into registry? Or the injection of TotalDTDCount, DTD_x is not a sufficient condition and the method is also limited to certain chipsets? Or there are no clear rules that determine systems where the method works?
question 2
With my computer the higher resolution (oficially unsupported by the netbook manufacturer) works with the generic driver from Windows XP (the one that is used just after the fresh Windows instal) and also with Linux. In this situation is there a possibility the problem may still lie in the BIOS limitations?
question 3
Aaron Brezenski wrote:
... You won't get 1280x1024 for this example, but you will get 1272x1024. It's
annoying to throw away 8 pixels due to something stupid like this, but it will tide
you over until your motherboard or laptop supplier gets around to fixing their VideoBIOS.
Did it happen already? Did any laptop supplier start to forbid graphic modes in BIOS more effectively ? (I guess they would allow certain graphic modes only, in place of disallowing certain modes.)