1360x768 with GMA950

1360x768 with GMA950

Hi,

I was not able to choose 1360x768 for my LG 32LE2R. Then I found these reg keys:

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlVideo{F2C46A2B-C33A-47E8-95E3-361988275F9B}001]
"TotalDTDCount"=dword:00000005
"DTD_1"=hex:66,21,50,b0,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01
"DTD_2"=hex:66,21,50,a0,51,00,1b,30,74,70,36,00,00,00,00,00,00,1e,37,01
"DTD_3"=hex:18,21,50,b0,51,00,1b,30,40,90,13,00,00,00,00,00,00,1c,37,01
"DTD_4"=hex:66,21,48,b8,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01
"DTD_5"=hex:66,21,48,a8,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlVideo{F2C46A2B-C33A-47E8-95E3-361988275F9B}000]
"TotalDTDCount"=dword:00000005
"DTD_1"=hex:66,21,50,b0,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01
"DTD_2"=hex:66,21,50,a0,51,00,1b,30,74,70,36,00,00,00,00,00,00,1e,37,01
"DTD_3"=hex:18,21,50,b0,51,00,1b,30,40,90,13,00,00,00,00,00,00,1c,37,01
"DTD_4"=hex:66,21,48,b8,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01
"DTD_5"=hex:66,21,48,a8,51,00,1b,30,40,70,36,00,00,00,00,00,00,1e,37,01

This worked with driver version 15.6 but produced a very unsharp screen. (I know that it worked a long time ago without extra reg keys and a sharp screen)

Now I tried to update to 15.6.1 but the reg keys doesn't work anymore with this version :(

So, how can I get reg keys which produce a sharp screen and (optionally) work with 15.6.1?

(sorry for my bad english)

4 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

IhrEnglisch ist besser als mein Deutsch.

Make sure you have populated all the DTDs with those values. Search your registry for all instances of TotalDTDCount and make sure they've all got your preferred resolutions. Perhaps new keys were added in 15.6.1 and they haven't been populated yet.

As for why it's not "sharp" anymore, I can't really answer that, although I will note that you have five different DTDs there for essentially the same rez (1360x768), although two of them are for 1352x768-- I suspect to get around a Stupid BIOS Limitation. I'd pare it down to one, put that in DTD_1, and change TotalDTDCount to 1.

You may have had a "sharp" screen at one point becausethe driverselected one of these DTDs, and now "unsharp" because the algorithm has changed slightly and it's chosen another. DTD_3, for instance, has a different refresh rate than all the others. It may be the "good" one and it's no longer chosen... or it may in fact be the "bad" one and it is chosen. It's hard to say. That's why I say reduce to one: then you can be sure.

That's right. The DTDs are nearly the same (I've chosen 1360x768@60).

Could it be that timing/clock or something in these reg keys are not perfect for my TV? I had the idea to connect my TV to my PC with a NVidia card and to try Powerstrip to get the best values. Is it possible to convert Powerstrip's values to Intel's DTD?

It's no problem that the new driver version don't work. I did only try it because I thought it'll get the right resolution without any reg hacks or something like this.

OK, I'll try now to use only one DTD but which one is 1360x768@60? :)

Technically, all of the first three are 1360x768. There are some slight differences in the first two between syncs, and the third has a different pixel clock than the others.

Nvidia + Powerstrip can generate a Modeline we can convert.

Leave a Comment

Please sign in to add a comment. Not a member? Join today