Widescreen Gaming Forum

my system:

XP 64
GTX 295
3x Acer V223W, 22" monitors, 1680x1050 native
TH2G Digital running latest firmware off Matrox site
nVidia Driver: 182.08
---------------

Followed this guide as soon as I unpacked and plugged everything in:
http://www.matrox.com/graphics/en/support/gxm/windows/th2go/digital/howto1/

My only variation was that the guide points to a slightly older version of PowerdeskSE, i noticed in Matrox downloads a 2.0.4 version instead of 2.0.3 as the guide points out.

So I updated firmware, restarted
Installed PowerdeskSE, restarted

As soon as the machine came back up a wizard launched, it prompted me to setup my resolution, so i selected TripleHead, Widescreen [email protected] i hit OK, it attempted to apply the resolution at which point the software said SUCCESSFUL, but my monitors are showing a [email protected] they look very strange.

I called Matrox, they said that current version of PD does NOT support the 295....but i see plenty of you guys running my same setup!

what am i missing? do i need to run older version of nVidia drivers? older version of PD-SE?

help!

Mmm you are the first person I have seen to run XP 64! I wonder if that is the problem? But for me just use the latest NV drivers and the latest PD-SE software and it works fine.

However I am using XP32 and GTX280's

_________________
Dipping bags at Mach1.9

Mmm you are the first person I have seen to run XP 64! I wonder if that is the problem? But for me just use the latest NV drivers and the latest PD-SE software and it works fine.

However I am using XP32 and GTX280's

its an nehalem based system so im running 6gb(3x2gb) ddr3 kit...without x64 i wouldnt be able to run as much memory...x64 causes alot of little quirks in apps :/

i read a thread on how to 'test' if your monitor supports 1680x1050@57, but judging from the posts

i was FINALLY able to successfuly run 1440x900@60 in the meantime, works find in desktop, so no more dealing with stretched images, and all games i have installed detect the 4320x900 res so :)

just have to deal with the slight blurriness of not running the display at native res for now.

will keep playing around with it tonight; might resort to reinstalling 32bit just for 'proof' of it working OK.

if anyone else has some suggestions im all ears!

Try Vista x64?

I have the EXACT same thing, monitors gtx295 and XP 64, mine works fine, make sure your using the latest Matrox software.

After reading this thread, I'm a little concerned. I just purchased the GTX295 and I am waiting for my TH2G. But I am running Windows XP. I am considering going to Vista 32bit.

Do you think I will have the same problem?

Nope... not really even sure what the problem is. The PD software doesnt need to (or can) support specific chipsets, just drivers. It supports nVidia drivers by way of Ini hacks (as documented in the custom res hacking thread) which in turn support whatever new gfx cards.

The only reason new drivers occasionally dont work with the Matrox software is due to nVidia changing their driver syntax or changing the the method of implementing custom settings.

People have the impression here that the Matrox SW does some very complicated voodoo, it really doesnt.

_________________
[GTX1080 - 4.48GHz 4690k - planning projector mayhem]

It's possible tu play on the 5040x1050 on Vista64/32 without problem or bug now ?

In short:
Officially Matrox says:
1. XP and NVidia card OK for 5040
2. Vista and/or Ati card max is 4320.

However
1. If you have a 200 series card there is a BETA Matrox PD-SE available which gives 5040 in Vista and Win7
2. Some people have been able to get 5040 by setting a custom res in NVidia Ctrl Panel.
For both of these see the sticky here for links to those fixes.

_________________
Dipping bags at Mach1.9

Nope... not really even sure what the problem is. The PD software doesnt need to (or can) support specific chipsets, just drivers. It supports nVidia drivers by way of Ini hacks (as documented in the custom res hacking thread) which in turn support whatever new gfx cards.

The only reason new drivers occasionally dont work with the Matrox software is due to nVidia changing their driver syntax or changing the the method of implementing custom settings.

People have the impression here that the Matrox SW does some very complicated voodoo, it really doesnt.

thats right, its simpy creating the custom res' for you and injecting it into the display panel/nv control panel.