Steve:Yes, the old mirage driver definitely contributed to EchoVNC 2.35's instability. The larger problem, however, was that EchoVNC 2.35 ran it's own flavor of VNC server, and I was unable to keep up with the pace of Windows OS, UAC, and runtime library updates.
In the 3.0 version, EchoVNC goes back to our 1.x approach in which it *invokes* a standalone VNC server only when needed. That allows me to focus on what we do well: provide a firewall-friendly connection to remote desktop services, rather than trying to maintain said remote desktop services....
hope that helps, Scott On Mar 25, 2011, at 10:04 PM, Steve Sobol wrote:
<<inline: compose-unknown-contact.jpg>>
Scott Best Friday, March 25, 2011 9:58 PM Heyaz. After years of delay bordering on abandonment ... the 3.0 update to the EchoVNC server for Windows is now available for beta testing: ftp://ftp.echogent.com/EchoVNC/windows/beta/Yay, Scott :) One thought:EchoVNC 2.35 seems to crash more than it should. I've always wondered if this is caused by an old, possibly buggy version of the Mirage Driver. More recent versions are available, and they are WHQL- certified. 3.0 uses the latest Mirage Driver, right?Thanks -- Lobos Studios - Website Design, Programming, IT Support Phone: 877.919.4WEB (877.919.4932) (Toll-free) Phone: 760.684.8859 (Victor Valley) www.LobosStudios.com -- www.facebook.com/LobosStudios www.twitter.com/LobosStudios
------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
