From: Michael Fontenot <mfontenot@am...> - 2010-04-07 20:47:11
I've been using TightVNC 1.3dev5 for years now to connect with a few
friend's and their parent's computers to solve problems as they arose. I
did this by writing a batch file that did the following:
[path_to_winvnc]\winvnc -kill -run
[path_to_winvnc]\winvnc -connect [my_static_ip_address::port_number]
I created a shortcut to the batch file on their desktop; and voila, they
could reverse connect to me anytime I was running VNC Viewer. Well a
couple of people have gone to Windows Vista and 7, so now I have the
issues mentioned on the site.
My question is this: Will there be anyway to launch tvnserver.exe and
automatically connect to a listening viewer in the final release? If
not, is there some other way to accomplish a similar operation with the
new 2.0 version?
Thanks in advance for any help,
From: Constantin Kaplinsky <const@ti...> - 2010-04-08 05:08:51
>>>>> Michael Fontenot wrote:
> My question is this: Will there be anyway to launch tvnserver.exe and
> automatically connect to a listening viewer in the final release? If
> not, is there some other way to accomplish a similar operation with the
> new 2.0 version?
Here is a quote from the upcoming TightVNC 2.0 Beta 2 announcement:
=== cut ===
Several useful command-line options have been re-implemented:
-connect, -disconnectall, -reload and -shutdown (they must be preceded
with either -controlservice or -controlapp in the command line).
Similar options (with slightly different names) were supported by
TightVNC 1.x, but there were no counterparts available in TightVNC 2.0
Beta 1. You requested them, and here they are.
=== cut ===
With Best Wishes,