Custom Resolution Tool for Intel Graphics: Easier Overscan Correction - Page 2

Have you tried manually typing in the following Modelines into the left panel to generate DTDs, and then try them on the CarPC...

"832x624" 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync
"800x480" 40.00 800 864 928 1088 480 481 484 509 +hsync +vsync

They're from

http://www.mp3car.com/vbulletin/linu...ml#post1137622

He's using the 845G, which uses the embedded drivers, and that guy preferred the 832x624 on the K90 because it sounds like the touchscreen didn't like 800x480, but he also provided one for that, too.

Yes, my point is since the user I mentioned published those Modelines, those Modelines are valid for the monitor and the graphics drivers (non-embedded) can use the same values. DTDCalc can accept those Modeline parameters in the left panel and construct the proper DTD, which DTDCalc can stuff into the registry.

The registry had five DTD_* parameters available, and TotalDTDCount indicates how many of them are active (i.e. available as a mode) at any given moment (starting at 1 and going in order). DTDCalc Registry Hack screen changes TotalDTDCount with the More and Less buttons, and the Get Calculation grabs the current DTD you're working on and stuffs it into the appropriate DTD_* entry.

That part of DTDCalc is purely a GUI for the registry editing process; we used to have to do it manually (and still can). The power of DTDCalc is really in the mode modification to cope with overscan, IMO, though it's still useful if all you want to do is convert a Modeline to a DTD for your own nefarious purposes.

Again, there's nothing about the 720x480p resolution which the Intel driver can't handle unless the BIOS is refusing it, and you'll only be able to get around that with 718x480 or 722x480. There is a less likely possibility, and that is that there is a monitor driver present (.INF file somewhere providing specifics of what frequencies are supported by that monitor), and the frequencies of 720x480 are below that level... but that's not an Intel thing, that's a Windows thing. And I would expect the embedded drivers to be affected by that condition, too.

The embedded drivers may let you do more because they are meant for developers, not consumers, and have less checks and balances in place to protect us from ourselves (from back in the day when sending a monitor badly constructed timings could physically damage it)... but really aside from BIOS considerations, using a custom DTD should be able to accomplish anything the embedded drivers can do resolution-wise.

It's only reading the DTDs from the first block, for whatever reason. You can stuff each of these into the Reverse Calculation tab of DTDCalc to find what they are (which is what I did):

02 3a 80 d0 72 38 2d 40 10 2c 45 80 df a4 21 00 00 1e: 1080p @ 50Hz
8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 df a4 21 00 00 18: 720x480p @ 59.94Hz

01 1d 00 72 51 d0 1e 20 6e 28 55 00 df a4 21 00 00 1e: 1280x720p @ 60Hz
8c 0a d0 90 20 40 31 20 0c 40 55 00 df a4 21 00 00 18: 720x576p @ 50Hz
01 1d 00 bc 52 d0 1e 20 b8 28 55 40 df a4 21 00 00 1e: 1280x720p @ 50Hz
01 1d 80 18 71 1c 16 20 58 2c 25 00 df a4 21 00 00 9e: 1920x1080i @ 60Hz
01 1d 80 d0 72 1c 16 20 10 2c 25 80 df a4 21 00 00 9e: 1920x1080i @ 50Hz

I don't see 1080p @ 60Hz on here, which is what I suspect you might want; your TV's not reporting it as a capability, though it will probably work anyway. In that case, go to the Standard Timings pulldown in DTDCalc and use the industry standard (not specific to your monitor) timings listed there.

Edit: Sorry, forgot the Short Video Descriptors at the beginning of the second block:

1920x1080i50
720x480p60
1280x720p60
720x576p50
1280x720p50
1920x1080i60
640x480p60
720x480i60
720x576i50
1920x1080p50 (native)
1920x1080p60

1080p60 is listed, but there's no DTD available for it. My recommendation to use the "standard timings" does not change.

There's an anti-Austrian bias to the software, alas. I'm afraid you'll have to find a different solution.

Woozy's the software guy on this one, so I'll have to let him answer, but here's my guess...

The registry has several copies of the DTD information, and if the right one is changed, it will get copied to the Current Settings on the next reboot. If the wrong one is changed, the Current Settings will get overwritten on the reboot.

There have been some questions on which are the right ones to overwrite. My G965 XP registry looked different from Wo0zy's G35 and G33 Vista, for example. We did our best to hit all the configurations (at least all the ones we had access to) but I suspect your configuration is using a different registry entry as it's "copy to Current Settings" source.

Can you search your registry for all instances of "DTD_1" and list them either here or in a PM to Wo0zy? This will help us fix the DTDCalc SW for you and others like you.

Sorry to hear that, bingobill, though I understand your consternation. Please let Intel Customer Service know why you selected another vendor. Unless they hear it from their customers/OEMs, there will be no improvement.

SugoE,

I wanted to apologize to you: I was away from my machine when I said "720x480 should work". It should, but when I put the settings into DTDCalc, while DTDCalc wrote them properly to the registry the lowest resolution which showed up as selectable was 800x600. Weird.

Even weirder is the fact that if you download ResChange and execute

reschange -width=720 -height=480 -depth=32 -refresh=60

it works just fine and gets added to the selectable resolutions.

So your experiences were right and I spoke way too soon. It is possible, but much more cryptic than I thought.

You Brits are way too US-centric.