Widescreen Gaming Forum

[quote][quote]Speaking of the new update, what is the frequency in Hz that the new resolutions are at? I think it would be helpful to know so we don't accidentally buy a monitor that doesn't support it.

57 Hz for 1440x900 and 5040x1050.

Well, now that I know it's 57 Hz... how would I go about setting that?

(4870 X2, Catalyst Control Center, Vista 64-bit)

Did you ever figure that out? I have the same card as you and I'm interested in buying 3WS monitors next year, but only if the 4870 X2 supports 3x1680x1050

I bought a new Triple head last year. Do I need a new unit to display the updated resloution or can i flash the old unit? It is digital. Sad to have to buy a new unit for the update.

You can flash the old unit, as long as it's the digital version.

[quote]Speaking of the new update, what is the frequency in Hz that the new resolutions are at? I think it would be helpful to know so we don't accidentally buy a monitor that doesn't support it.

57 Hz for 1440x900 and 5040x1050.That's not quite right ... it is 60Hz for 3 x 1440x900 ...
Supported resolutions and their refresh rates ... http://www.matrox.com/graphics/en/products/gxm/th2go/resolution/digital/resolutions.html

That is great news! Got 3 x 24" Samsungs (in boxes in my office), a couple of SLI'ed 8800's and a new PC waiting to go. It is a digital unit. Glad Matrox is supporting the product and making it better. All I need now is the time to do all this. Thanks for replying. BTW: Hey Paddy, nice to see you!

You can flash the old unit, as long as it's the digital version.

EDIT:

After viewing the forum a little bit more, I now realize that my questions below have been answered. Sorry!

......................................................................................................
Hello folks...

I have the DTH2GO and 3x22" Acer Monitors. Two of the monitors are exactly the same (Acer AL2216W) and the third one is an Acer 2223W.

Here are the problems I am having on my dual-boot (XP Pro 32bit/ Vista Ulimate 64bit)...

When in XP Pro, I am only able to go to 1440x900. When I try to go to 1680x1050 only the Acer 2223W will display. The other 2 display a blank screen... although the LED light on each stays green.

I can however "force" 1680x1050 by using the nVidia Control Panel, by changing the resolution to 60Hz from 57Hz. This does not result in the desired effect, as the desktop is larger than the display area, and the Matrox PowerDesk SE no longer controls the displays.

This leads me to believe that the two AL2216Ws don't like 57Hz.

When in Vista, the "new" widescreen modes don't even show up when viewing display modes for TripleHead. They do show up when switching to DualHead view mode however.

Any thoughts/help/etc. would be much appreciated!

That is great news! Got 3 x 24" Samsungs (in boxes in my office), a couple of SLI'ed 8800's and a new PC waiting to go. It is a digital unit. Glad Matrox is supporting the product and making it better. All I need now is the time to do all this. Thanks for replying. BTW: Hey Paddy, nice to see you!

[quote]You can flash the old unit, as long as it's the digital version.

So this works with SLI????

I have the same problem.

Just upgraded my 17" monitors to 22" when I saw that 1680x1050 was supported. Upgraded the Th2go and installed the latest drivers.

Can't find the 1680x1050 resolution.

When enabling the loggin in the GXM I get the following:


To me the lines about LowLevelUnit::InstallMonitorInf are interesting.
I guess this is due to the fact that the driver is 32 bit while i'm running Vista Business 64.

I have opened a case against Matrox but they haven't yet responded to the question whether or not the driver should work in Vista 64.

Is there anyone who has been able to run 1680x1050 under a 64-bit OS?

I have a 8800 GTX and 3 Samsung 2243bw.

I appreciate all help on this matter!

EDIT:

After viewing the forum a little bit more, I now realize that my questions below have been answered. Sorry!

......................................................................................................
Hello folks...

I have the DTH2GO and 3x22" Acer Monitors. Two of the monitors are exactly the same (Acer AL2216W) and the third one is an Acer 2223W.

Here are the problems I am having on my dual-boot (XP Pro 32bit/ Vista Ulimate 64bit)...

When in XP Pro, I am only able to go to 1440x900. When I try to go to 1680x1050 only the Acer 2223W will display. The other 2 display a blank screen... although the LED light on each stays green.

I can however "force" 1680x1050 by using the nVidia Control Panel, by changing the resolution to 60Hz from 57Hz. This does not result in the desired effect, as the desktop is larger than the display area, and the Matrox PowerDesk SE no longer controls the displays.

This leads me to believe that the two AL2216Ws don't like 57Hz.

When in Vista, the "new" widescreen modes don't even show up when viewing display modes for TripleHead. They do show up when switching to DualHead view mode however.

Any thoughts/help/etc. would be much appreciated!

[/code]

I solved it :)

I rolled back the Nvidia driver to version 175.19 and now the resolution is there.

I found another forumthread about the Nvidia drivers and Matrox seem to be aware of the problem so hopefully there will be a solution soon.

I have the same problem.

Just upgraded my 17" monitors to 22" when I saw that 1680x1050 was supported. Upgraded the Th2go and installed the latest drivers.

Can't find the 1680x1050 resolution.

When enabling the loggin in the GXM I get the following:

Code:

[2008-11-27 - 23:13:19]  [Matrox.GXM.dll] Gxm2::Initialize : Log Enabled for GXM2.
   [2008-11-27 - 23:13:22]  [Matrox.GXM.dll] DisplayFinder::FindWithWhitePatternGDI : Gxm Found on display 2.
   [2008-11-27 - 23:13:22]  [Matrox.GXM.dll] LowLevelUnit::InstallMonitorInf : The calling application is a 32-bit application attempting to execute in a 64-bit environment, which is not allowed..
   [2008-11-27 - 23:13:22]  [Matrox.GXM.dll] LowLevelUnit::InstallMonitorInf : The calling application is a 32-bit application attempting to execute in a 64-bit environment, which is not allowed..
   [2008-11-27 - 23:15:50]  [Matrox.GXM.dll] DisplayFinder::HaveDisplayBeenAttachedOrDetached : Display(s) have been attached or detached. Re-detection required..
   [2008-11-27 - 23:15:51]  [Matrox.GXM.dll] DisplayFinder::FindWithWhitePatternGDI : Gxm Found on display 2.

To me the lines about LowLevelUnit::InstallMonitorInf are interesting.
I guess this is due to the fact that the driver is 32 bit while i'm running Vista Business 64.

I have opened a case against Matrox but they haven't yet responded to the question whether or not the driver should work in Vista 64.

Is there anyone who has been able to run 1680x1050 under a 64-bit OS?

I have a 8800 GTX and 3 Samsung 2243bw.

I appreciate all help on this matter!


[quote]EDIT:

After viewing the forum a little bit more, I now realize that my questions below have been answered. Sorry!

......................................................................................................
Hello folks...

I have the DTH2GO and 3x22" Acer Monitors. Two of the monitors are exactly the same (Acer AL2216W) and the third one is an Acer 2223W.

Here are the problems I am having on my dual-boot (XP Pro 32bit/ Vista Ulimate 64bit)...

When in XP Pro, I am only able to go to 1440x900. When I try to go to 1680x1050 only the Acer 2223W will display. The other 2 display a blank screen... although the LED light on each stays green.

I can however "force" 1680x1050 by using the nVidia Control Panel, by changing the resolution to 60Hz from 57Hz. This does not result in the desired effect, as the desktop is larger than the display area, and the Matrox PowerDesk SE no longer controls the displays.

This leads me to believe that the two AL2216Ws don't like 57Hz.

When in Vista, the "new" widescreen modes don't even show up when viewing display modes for TripleHead. They do show up when switching to DualHead view mode however.

Any thoughts/help/etc. would be much appreciated!

[/code]

So this works with SLI????

SLI has nothing to do with TripleHead2Go supporting new widescreen resolutions ;)