Monitoring remote mouse movements

kicks · Post by **kicks** » 2005-11-09 15:10

When others show me their desktop by adding my viewer as a new client, I can monitor their cursor movements only, if I manually change my viewer's default connection options from “Track remote cursor locally” to “Let remote server deal with mouse cursor”. This option may be performed after the incoming connection or even before it. However, I did not succeed in setting this option to my viewer right from its start. Using " ..\ultravnc\vncviewer.exe -normalcursor " has no effect. What did I miss? Many thanks for all hints,
Thomas

[mod=494,1131578733]moved from bug report to general help,
reason:is not a bug, is a limitation reverse connection [/mod]

redge · Post by **redge** » 2005-11-09 23:39

work around:

connect successfully to vnc server, set your options and then go menu File... Save As ... server1.vnc

and next time you can open vncviewer on listening mode with your prefered settings.

Start... Run
"%ProgramFiles%\UltraVNC\vncviewer.exe" -listen 5500 -config server1.vnc
(anyway, don't forget ")

kicks · Post by **kicks** » 2005-11-10 08:01

Many thanks, redge, works perfectly!

My apologies that in the parameter guide http://ultravnc.sourceforge.net/install/cmdline.html,
I had not really understood the mechanism of -config filename

Thomas

kicks · Post by **kicks** » 2005-11-10 18:44

Supplementary question: Exceptionally, the cursor movements of one particular machine get visible only after the remote mouse performed a rightclick or doubleclick. If this behavior depends on the remote mouse driver (intellipoint 5.2), what driver setting might overcome it?
Many thanks again, Thomas

redge · Post by **redge** » 2005-11-11 00:40

Exceptionally, the cursor movements of one particular machine get visible only after the remote mouse performed a rightclick or doubleclick.

already reported as bug
[topic=3546][/topic]

kicks · Post by **kicks** » 2005-11-11 08:12

Ok, I see. Remains my observation that the mouse cursor is not initially invisible in every connection (as stated in the bug report you mentioned), but only in particular cases. Its visibility systematically depends on the conditions on the server.

In my test environment (3 machines, all different hardware, all mult-OS 98SE, 2kSP4, XPproSP2, VNC 1.0.0.20 up to 1.1.0.1), only the one machine with intellipoint needs a rightclick to turn the cursor visible on the remote viewer. This is true for outgoing and incoming connections likewise. Of course, the reason may be even more specific than the family of the mouse driver. I suspect a particular driver setting unknown to me so far. So I am interested in further differential observations.

Additional observation: the cursor of one particular machine, though locally set to "Windows black extralarge" like on the other test machines, appears on all viewers as "regular small white" only.

TKD · Post by **TKD** » 2005-11-11 17:26

hi guys... i understand the mouse issue is resolved in the fully installed client/server version of ultravnc... but what about for SC? is there an easy way to tag on a parameter so that SC starts off with the mouse setting as specified above to avoid connection loss?

thanks for your help!

Monitoring remote mouse movements

Monitoring remote mouse movements

for SC...