"Disable local input" doesn't work

[Matze]

Hi,

I'm using the UltraVNC viewer on a Windows XP SP3 Machine and the server on a Vista computer (used the 1.0.5.6 installer). The option "disable local input" has no effect on the Vista machine.

Do I have to attend to something or is it a bug?

[supercoe]

Bump,

Bug still exists in 1.0.8.2 on Vista32

[redge]

bug confirmed

[noumman]

does that mean, we cant control vista computer running the server file from a xp computer running viewer?

[supercoe]

noumman,

No, it only means that the "disable local inputs" button on the viewers toolbar doesn't do anything when the server is running on Vista/7.

[pgmoney]

noumman,

No, it only means that the "disable local inputs" button on the viewers toolbar doesn't do anything when the server is running on Vista/7.

This bug hasn't been ignored, it's just I havn't been able to duplicate it until I finally used the winvnc.exe directly from the UVNC distro but it's kind of odd since the winvnc.exe in OneClick works fine on Vista & Win7 32/64 and it was compiled unchanged (except for graphics) from the svn sources so the source code doesn't appear to be broken.

All I did was replace the UVNC winvnc.exe in the UltraVNC folder with the one from the OneClick package. Can someone confirm?

The link to the winvnc.exe is:

http://www.advantig.com/files/ocwinvnc.zip

[redge]

This bug hasn't been ignored, it's just I havn't been able to duplicate it until I finally used the winvnc.exe directly from the UVNC distro but it's kind of odd since the winvnc.exe in OneClick works fine on Vista & Win7 32/64 and it was compiled unchanged (except for graphics) from the svn sources so the source code doesn't appear to be broken.

i think the difference, there some pointer/reference/flag aren't removed from code to executable, so end user see some bug that developers can't see because you have some flag for tracking bug on the preview exe

that happen 2 times i asked the debug version.
Rudi unable to reproduce some bugs

so i asked the version with debug code and well, the bug won't exist.
then he find the bug and can remove one flag and compile new exe success.
That make me thinking the same issue.
maybe we must ask the debug version and final exe before any release.