TightVNC actually is based on the code from the TridiaVNC 1.4 distribution of VNC (http://www.tridiavnc.com), and then integrates "tight encoding", libjpeg compression, and other goodies.
The tight encoding option is optimal for VNC over low-speed connections such as dial up. However, determining the ideal arrangement of options for your needs really requires individual testing - it's going to depend on things like the speed of the machine you're connecting to, the graphical complexity of the desktop on the machine you're connecting to, etc. Glenn -----Original Message----- From: Ben Hunsberger [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 2:05 PM To: [EMAIL PROTECTED] Subject: TightVNC vs Regular Hi, I'm new to the VNC scene. I just downloaded "regular" VNC 3.3.3r9. However, I've now noticed this discussion regarding TightVNC What has been the experiences of people who have used both products? What is the relative stability issues? Should I even consider VNC 3.3.3.r9 when TightVNC is reportable faster? In short I'd like to pick the appropriate product first. Performance over 56/64k is important Stability on windows only platforms: Win2000, WinNT 4.0, win9x. Free is of course a major benefit :). Are these two separate products now, with 2 separate development paths or does TightVNC take regular and integrate their "tight" protocal? Long list of questions, Thanks in advance Ben Hunsberger Banks Corporation Elkhart In. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
