Sounds like a bug in TightVNC, or in the Solaris build of it.  You might
have more luck reporting this to the developer.

Alternatively, you might prefer to upgrade to VNC 4, of course.

Cheers,

Wez @ RealVNC Ltd.
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to