I saw this once as well, and while I couldn't determine
the exact cause, I did find a fix for it: when I deleted the ORL
registry key (the one used by legacy VNC3 flavors like TightVNC),
the new version worked just fine.
I believe that some registry key set by another non-Tight
VNC flavor is causing confusion -- the server doesn't grok the
key -- and in its confusion, the TightVNC server fails to load
the echoWare DLL. But I haven't been able to reliably reproduce
it....yet.
Hope that helps!
-Scott
On Wed, 28 Sep 2005, Stewart Taylor wrote:
Hi Scott
I tried out the TightVNC with the EchoVNC overlay.
Not entirely being sure of what it would do I unloaded all VNC flavours
before starting.
The TightVNC server comes up nicely complete with an Echo Server tab.
However the screen is all grayed out and notes that EchoWare (Version
unknown). Status: Missing.
What am I missing?
Stewart
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
