Widescreen Gaming Forum

OK, let me lay the background here.

Start about two weeks ago. I saw that the Matrox W7 drivers were out, and because the L4D2 demo spat out a pop-up at me letting me know that my then-current config of Vista 64 & Nvidia driver 182.50 weren't going to cut it, I decided to do a fresh install of the full version of W7 Home Premium 64.

I upgrade my DTH2Go's firmware, download the W7 drivers and get the latest Nvidia WHQL driver 191.07 straight off Nvidia's site.

No joy.

Pissed, I hunt down possible fixes in these forums for the next few days, trying all sorts of custom rez settings.

No joy.

I call Matrox Support. 3x's over the next few days.

First call finds them poking around my system and trying all the same fixes that I had been trying for days. It ends with the advice to keep trying driver and PowerDesk combo's till I find one that works.

Yeah, riiiiight. (/snark)

I, despite my frustration, do exactly that. Over the course of the next day, day and a half, I try every possible combination with all Nvidia WHQL drivers from 182.50 onward to present, and every PowerDesk from the "beta" that worked with 182.50 up until the new one for W7. I even made a little matrix on a sheet of paper to ensure I didn't miss anything. Tried the standard vanilla install routine, and when that inevitably failed, I would try to set up a custom rez via the Nv CP...

No joy every single time.

I call Matrox Support for the second time. Then a third.

Still no joy.

Then the tech support told me a very, very interesting little tidbit:

Matrox currently is not allowed access to Nvidia's API. They are working on that situation, but until then, there is no possible way for them to build a proper PowerDesk that will work for damn near everyone in the manner that a driver for this type of hardware should. In particular, Matrox is having issues with the GTX 285 and another card in that line, either the 275 or 295. I can't recall because all I was interested in was the 285 since I run three of them.

So, the crux is that until Matrox gets the legal OK to slice open the Nvidia API, any work around is going to be totally situationally dependent. This comes straight from Matrox.

I wanted to say thanks to all those that have posted how they have managed to get their 5040 up and running. Even though it didn't work for me, if might have worked/will work for someone else.

Looks like those of us with Nvidia cards might want to start hitting up the Nvidia forums to let them know how aggravated we are with the whole situation.

Just a thought...

Thanks for that info, man that is crap. Here I am with the latest BETA NV driver (for MW2 support) and I am fine to 5040. As of tonight I will be 3x1920x1200 (eventually I will be able to say what 3x1920 adds up to but not now ;)) so it is all irrelevant to me now, just see how many GTXs hit TradeMe/Ebay/CraigsList/etc from this forum!

Good luck in the future though

_________________
Dipping bags at Mach1.9

They'll just say it is Matrox's fault :roll:

Damn it. When I built my new system, I used two GTX 275's. I really hope they resolve this soon. Otherwise ATI will be getting some cash from me soon.

I have been spending the vast majority of my free time trying to get my build working. I am running a pair of 275's in SLI on a 9950 PhenomX4 platform trying like hell to get 1050 x 5040 running. (Edit: running win7 x 64) The ONLY way I can get it is with the VISTA x64 driver (182.5's), but then nothing runs - only blank screens. In fact I can ONLY get resolutions that are 4-3. NO 16-10 resolutions work.

Is there a combination of OS and driver version that WILL work? Or is this another examle of Nvidia pulling some crap with thier customer base? I experienced similar issues getting opengl on Nvidia's 3d Vision setup - one that they have ensured will only work with Quattro cards and not mainstream gaming cards. Sooo.... I gave up and forked out big bucks for two more monitors to run 3x1650x1050. I guess this was a mistake too? What a farking joke.