PDA

View Full Version : NView Dual Monitor Problem

cwalker
09-08-2004, 01:53 PM
I'm new here so please be patient....

I have an Nvidia Quadro FX 500 on a Windows XP Pro OS Set for Dual Monitor usage, most of the time that is. Occasionally on a cold boot or a re-boot the card will ignore my primary monitor. Shifting the image to the secondary monitor. This is made slightly more complicated by the fact that my secondary is a 15" on it side running 768x1024. This matches the Height size and res of my primary 19: at 1280x1024. The problem comes in when I try and reset the Nveiw display mode... It seems that when this happens it will no longer recognize the Nview Dual View mode. I end up going through a complicated and some what random sequence of re-installing the driver, restarting and pleading with the computer gods.

As if it could not get more complicated. I am running two computers on my primary monitor. I use a Belkin switcher to move from one machine to the other. This means that both monitors are running in analog via a converter on my Secondary to dumb the signal down from the DVI. The primary runs out of the analog to the switcher...

Now that I think about it. Does the computer default to looking to the DVI signal first? If I switch the two outputs... would this help?

If anyone has a clue what I've rambled out here, I would be more than grateful for a suggestion or two.

Thanks!
lots
09-08-2004, 03:26 PM
Take out the switch and see if it works ok...

If so.. then one thing i can recommend is make sure your switched to the computer that has the dual monitor setup while its booting up.. i know a few switches will not operate correctly if you boot the machine they're attached to with it switched to a different computer.. just a thought.. but you should really take the switch out of the equation.. they can cause problems on some systems (depending on quality of switch..)
jackburton
09-08-2004, 05:02 PM
I've got the almost the same set-up you do, with the Belkin switch and everything except I'm running Win2000. I had the same problem until I shut off the NView desktop managment features and used the built-in Windows multiple monitor feature. I'm not much help in that area however, because I'm not quite sure what voodoo I did to get it to work. Anyway both monitors show up in the properties dialog and the description says "multiple monitors on Nvidia FX500" instead of "multiple monitors on Nvidia DualView". Come to think of it, it was a tech at Boxx who told me how to do that. I also remember forcing it to recognize the primary by starting up with the secondary off, then quickly turning the secondary on after the bios screen, or during the windows start-up screen. Even though it's not XP related that might put you on the right track, sounds like you're going through the same kinds of crap I went through.
lots
09-08-2004, 06:24 PM
unfortunately when you run without the nview options enabled and let windows handle the dual screen, you lose the ability to display open GL graphics on the secondary monitor..

I really think your problem stems from the switch.. you should try it without and see what happens..
jackburton
09-08-2004, 09:05 PM
Are you sure about not being able to run openGL on a second monitor? I thought that was when using two seperate video cards. I've never seen any slowdown moving from one to the other in 3d apps, with the FX500 anyway. If so that sucks.
lots
09-08-2004, 11:32 PM
I just tried it out on my system, wasn't home earlier, (running a Geforce 4 Ti4600) and indeed, it does display the open gl windows on the other screen, with some errors and it does seem kind of slower, to me.. but it works. However on my ATI card, I dont get any OpenGL support on the secondary monitor unless I'm in clone mode, so maybe this is more specific to ATI than Nvidia :) In Lightwave the open gl windows display correctly and run much faster in the NView "Horizontal Spanning" compared to the "Extend my desktop to this monitor" option in windows.
CGTalk Moderation
01-19-2006, 05:00 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.