Widescreen Gaming Forum

You can't do 5040 at 60Hz only 57, it is a limit of the DVI cable (apparently!). If you are at 5040 just stick with it.

_________________
Dipping bags at Mach1.9

You can't do 5040 at 60Hz only 57, it is a limit of the DVI cable (apparently!). If you are at 5040 just stick with it.

Problem is the following: monitors report much less than standing in settings, e.g. if there's in driver settings 57Hz in fact it is something like 55Hz which is much too low for normal monitors. If you put 60Hz it will do something like 57,8 Hz, which is o.k..
BUT: idiotic screen test will you not do so, I my case it is like that: despite everything works fine, it reports test not o.k. and returns back in lower mode. That was the reason why I asked somebody to supply a hack because the task would only to be to cheat the foolish " test not o.k.", then it would work fine!
:evil:

OK, have you tried ctrl-alt-deleting out of the test failed? Someone had this in Win7 and that worked.
But yeah the BETA should get around the out of range error, so I don't know why your rig won't work.

However the (TNT)BW got his working using the BETA so there is no point for him to muck around with anything!

_________________
Dipping bags at Mach1.9

OK, have you tried ctrl-alt-deleting out of the test failed? Someone had this in Win7 and that worked.
But yeah the BETA should get around the out of range error, so I don't know why your rig won't work.

However the (TNT)BW got his working using the BETA so there is no point for him to muck around with anything!

Please be a bit more precise: "ctrl-alt-deleting" and then? stopping any task? But then config is not written...
(TNT)BW can be used for 60Hz setting?? How?

OK, I dunno to be honest, someone (somewhere.....) in one of the many 5040 threads posted that he could kill the NVdia test resolution failed pop up and get the 5040 to work. That seemed reasonable to me because when that error message popped up for me the screen was actually at 5040 and it was only when I hit OK (rather than killing the pop up) that the res dropped back to the lower res. I thought maybe you could give it a go.

As for the second bit (TNT)BW is a forum user name; you posted:

[quote]I'm running Vista 32 ,Nvidia GTX260 and 182.08 driver, and the beta GXM did the trick for my system to get 5040x1050@57hz, thanks alot. 8)

But 57Hz is sh..., how about 60Hz?? Did you try it?
So I was saying why should he want to try 60Hz when he has 5040 @ 57Hz working fine? AFAIK trying to get 60HZ at 5040 working is a dead end. Sorry for the confusion.

_________________
Dipping bags at Mach1.9

OK, I dunno to be honest, someone (somewhere.....) in one of the many 5040 threads posted that he could ...AFAIK trying to get 60HZ at 5040 working is a dead end. Sorry for the confusion.

Sorry, but after half a year (!) trying in vaine with hundrets of different hints I would like to wait for someone who is sure.
Thanks anyway.

Driver sweeper + 182.50 + beta GXM = success ! :D
Setup was a no-brainer, the setup wizard took care of everything. Finally, my Vista64 can show off in both 2560x1600 and 5040x1050. No more booting in XP to enjoy TripleHead. I'm happy !

awesome! :triplewide

_________________
Dipping bags at Mach1.9

Driver sweeper + 182.50 + beta GXM = success ! :D
Setup was a no-brainer, the setup wizard took care of everything. Finally, my Vista64 can show off in both 2560x1600 and 5040x1050. No more booting in XP to enjoy TripleHead. I'm happy !

Please be a bit more detailed: at which frequency does it run at your system?
Where can I get driver sweeper?
Thank you!! :lol:

No details = no need for details ;) It was as straightforward as any software install should be.

- Driver Sweeper can be found on guru3d.com. I'm not even sure it's required, but I figured starting off a clean base couldn't hurt. I hadn't bothered in my previous failed attempt with some older 180 driver btw.
- 5040x1050 runs at 57 Hz, and is present in GXM's list. I didn't have to create a custom res or care about the refresh rate at all, the Wizard that used to fail in the past finally did the job 8)