Wez:
Hello, and Happy New Year! Thanks for writing. I probably misused
the term "VNC-compatible" -- I meant it to indicate that the EchoVNC
server accepts both direct and echoWare-relayed connections from the
RealVNC Viewer, and the RealVNC server accepts both direct and relayed
connections from the EchoVNC Viewer. If there's something else I should
add (remove?) to our flavor to maintain VNC compatibility, please point
me to the details and I'll pursue it.
Regarding the Mirror-Driver problem, you are right, and we're
working on a Mirage-Driver update for the next release.
cheers,
Scott
On Wed, 3 Jan 2007, James Weatherall wrote:
Hi Scott,
Please note that UltraVNC is not, to the best of my knowledge,
VNC-compatible, nor is the mirror driver it uses open-sourced at this time.
The "Mirage" driver used by the TightVNC project has been open-sourced, and
the TightVNC project maintains VNC compatibility too, so perhaps that's what
you're thinking of?
Cheers,
Wez @ RealVNC Ltd.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott C. Best
Sent: 03 January 2007 00:07
To: [email protected]
Subject: speaking of firewalls...EchoVNC 2.0 is now available
[snip]
As EchoVNC is based (with thanks!) on [EMAIL PROTECTED], it also
provides
[snip]
o Utilizes the open-source "Mirror Driver" for improved
[snip]
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
