UltraVNC

I'm guessing the answer is "no."

You have a laptop running win7, laptop display is secondary (position on the left side) and a external monitor (primary display on the right side). you use 10962 server and viewer version? correct? Correct. Except I'm using an iPad viewer. you said mouse click event on the monitor display ( primary ...

Yes, 10962. I produce it with a server running 10962 on Win7. Laptop display is on the left, external monitor (main display) is on the right. Previous builds displayed the main display but the mouse was stuck on the left edge of the laptop display. 10962 moves the mouse properly, but it displays the ...

3. after successfull connection, it show primary display, click on full desktop button on viewer toolbar, it will show you the second display. You're right, B. The iPad viewer doesn't have that button. That feature would be nice but it shouldn't be necessary. There is a *BUG* in the current server ...

Rudi, I tried running 10962 on my Win7 system. It seems to be a bit better -- the mouse does move around now, instead of being stuck on the left side of the laptop screen -- but it's still on the wrong display. I connected to port 5900 and it displays my main (big) monitor, but the mouse tracks on ...

I'm trying to access my WIn7 system from an iPad, so I don't have the new display-switching option available. (But I have the same problem if I connect with the uvnc client.) What can I do? I tried the instructions in this post (selecting secondary display) and that didn't seem to change anything ...

Hi Rudi, OK, I killed the winvnc processes, copied winvnc.exe to a temp folder, and ran it. Once I realized it moved from port 5901 to 5901, everything worked fine. So I copied the ini file to the Program Files folder, and ran winvnc.exe again, and it worked! This is XP!! Why did it have a problem ...

Installed 1.0.8.2 on a Win7 laptop (client) and an XP system (server). I've established what port it's listening on (5901). I've had a number of different failure modes: * One time it gave an error something like "service running as application" or something like that -- only saw it once ...