Greg:

        Heya. Yes, the "run at startup" does actually mean "run
at login"...sorry if it was misleading. The 1.5 release of EchoVNC
should include a mode to install a VNC service that's echoWare
enabled.
        In the meantime...the best workarounds for running
EchoVNC as a service are:

1. Use srvany.exe from Microsoft:
   http://support.microsoft.com/kb/q137890/
   Setup is a bit tricky, but I've heard some EchoServer users got
   it working this way. If anyone would like to post details of
   how they got it to work for EchoVNC, I'll get them onto the
   FAQ-O-Matic

2. Use "TightVNC with EchoWare", part of the EchoWare Remote
   Support System download, or just grab it from our ftp site.
   It's a VNC server that has echoWare embedded already, as
   opposed to EchoVNC which enables echoWare connections to
   existing VNC servers. Simply install TightVNC normally,
   register it as a service, then overwrite the original
   binaries with ours.

        The downside of the 2nd approach is that it currently
uses an earlier version of the DLL (1.55), but we'll be releasing
an update for that this month.

        I hope that helps!

cheers,
Scott


On Thu, 9 Feb 2006, Greg wrote:

My platform is Windows XP on both server and client. My VNC server is
behind a firewall. Both this server and my VNC viewer are configured
to use EchoVNC to connect. In order to connect, though, the server
needs to have an active session, i.e., there must be someone logged
into it. This poses a security risk because I must leave the server
(my office computer) with an unattended active session in order to use
EchoVNC.

I tried setting the "Automatically activate EchoVNC at startup"
setting, but this is a bit of a misnomer since this doesn't cause
EchoVNC to activate at startup of the machine but rather at startup of
the user session for which it is configured. It puts a command string
setting under the HKCU registry key "Run" so that EchoVNC starts when
the user logs in. I tried putting that command string under the HKLM
"RunServices" registry key, which is the appropriate place to put
commands that are to run before user login, but that doesn't work.
Apparently, EchoVNC needs an interactive session in order to start.

Is there any way to have EchoVNC to start and run without an active
user session and, if not, are there any plans to do this?

Thanks much,
Greg


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users

Reply via email to