>If you run a TightVNC server that uses extra >compression over the protocol, how can a >non-TightVNC viewer understand it?
The viewer fails to send the indication that it understands Tight encoding (which is correct - it doesn't), and so the server simply doesn't send it. >I thought you had to use TightVNC on both sides >of the com-link. To take advantage of Tight encoding, yes. For simple interoperability, no. -- -------------------------------------------------------------- from: Jonathan "Chromatix" Morton mail: [EMAIL PROTECTED] (not for attachments) website: http://www.chromatix.uklinux.net/vnc/ geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) tagline: The key to knowledge is not to rely on people to teach you it. --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
