{ "numMessagesInTopic": 31, "nextInTime": 582, "senderId": "UQ3NABa8-DVga54bGXdL8D7RoHc1cIFjKW69FruS9W2AjpDmsWpt2squoSYvOf5O5bQcDmQupAOKxIu2MPWwGw_W8dXFIuFTWfyEOqqFNA", "systemMessage": false, "subject": "Re: MSI NX6800GT T2D256E", "from": ""fluppeteer" <yahoo@...>", "authorName": "fluppeteer", "msgSnippet": "Thanks for the feedback, guys! ... driver ... defined ... selectable ... the ... read ... Hmm. I d spotted that interface - but 1216x2400x48Hz is already ", "msgId": 581, "profile": "fluppeteer", "topicId": 553, "spamInfo": { "reason": "0", "isSpam": false }, "replyTo": "LIST", "userId": 192443393, "messageBody": "
>driver
\n> PowerStrip will, initially, only present the resolutions that the
\n
> claims, in the Windows Registry, to support.defined
\n> However, PowerStrip permits you to _add_ either PowerStrip pre-
\n
> resolutions (pre-defined for convenience only), or fully customselectable
\n> resolutions to the Registry so that the new resolutions are
\n
> by both PowerStrip and Windows. A re-boot _may_ be required oncethe
\n
> new resolutions are added in order to get the display driver to re-read
\n
> the supported resolutions.Hmm. I'd spotted that interface - but 1216x2400x48Hz is already
\n
\n
> The sequence in PowerStrip to get to the correct screen is:and
\n> (Right (or left) click on tray icon) Display profiles -> Configure
\n> Advanced timing options...
\n> Custom resolutions
\n> [Then define the resolution or pick one of the pre-defined ones,
\n
> click on "Add new resolution"]*Nod*. Thanks, I'll try and see where I get.
\n
\n
> Just to double-check: You are connecting the 2nd head to the 1stPrimary
\n
> interface on the T221, right?Ah. Good point. Dunce cap for me, then. (I'd used two heads before,
\n> The T221 uses the 1st Primary interface (as defined on the T221's
\n> connectors) as the master control for the display. If there is no
\n> signal on that interface, it will remain in standby mode.
\n
\n
> While I generally like to use Linux for everything where I want to_know_), I
\n> _know_ what is being done (source code makes it possible to
\n
> have found that PowerStrip is a _very_ convenient tool foradjusting
\n
> timing on the DVI interface. It is one of the very few hardwarerelated
\n
> things that I actually prefer to do under Windows.I belong to a bygone age, having edited monitor definition text files
\n
\n
> Ummm...than a
\n> At least on my T221 DG3, I am able to reduce blanking to:
\n> Horizontal (clocks): 0,8,0 (front porch, sync width, back porch)
\n> Vertical (clocks): 0,1,1 (front porch, sync width, back porch)
\n>
\n> However, is is not 100% stable at that, so I normally (for more
\n
> year now) run it at:closest
\n> Horizontal (clocks): 8,16,8 (front porch, sync width, back porch)
\n> Vertical (clocks): 1,3,3 (front porch, sync width, back porch)
\n> or something close to the above timings happens to have the
\n
> resultingwidth of
\n>
\n> [Ah, actually, I have mostly been using a Horizontal Sync Pulse
\n
> 8 clocks, not 16. I changed to 16 in October to avoid a minorcursor
\n
> corruption bug introduced in ATI's previous (August, Version8.043.1.1)
\n
> FireGL drivers (I have not yet tried their current (October,Version:
\n
> 8.062) drivers to see if that problem is fixed). The bugspecifically
\n
> was that the cursor would become corrupted if it was, and onlywhile it
\n
> was, in the last pixel on the right of any individual display whenthe
\n
> Horizontal Sync Pulse width was 8 clocks.]obtain
\n>
\n> The long and the short of it: A T221 DG3 is able to routinely
\n
> 33.722 Hz refresh in 2x 1920x2400 mode using reduced blankingtiming
\n
> custom set to:Cool, useful to know.
\n> Horizontal (clocks): 8,16,8 (front porch, sync width, back porch)
\n> Vertical (clocks): 1,3,5 (front porch, sync width, back porch)
\n> Pixel clock is: 158.574MHz
\n> PowerStrip: 1920x2400=1920,8,16,8,2400,1,3,5,158574,2306
\n
\n
> If you are interested, I uploaded in October the PowerStrip timingfiles
\n
> for the reduced blanking periods I use to the group's file area onCheers - interesting for looking at.
\n> Yahoo. They are in the "Timing" folder. These include:
\n> T221, 1920x1200, 41.001Hz refresh, 49.488kHz horizontal scan,
\n> 96.600MHz pixel clock.txt
\n
\n
> Hmmm... After re-reading your statements, I realized that you maymean
\n
> that the DG5's EDID data may describe a reduced sync timingcompared the
\n
> the DG3, and not be referring to the actual capabilities of theI have
\n> hardware, but merely what it reports to the system via the EDID.
\n
> not looked at the EDID information for the DG5, so I do not knowwhat it
\n
> reports for it's timing in any of it's EDIDs.Yes, I was just going off the EDIDs in the back of the manual,
\n
\n