Keith Devens .com

I'm confused too, since TridiaVNC claims to utilize "tight encoding", potentially making it "tighter" than TightVNC, no?

Since I can't figure it out either, I'd just advise everybody to pick TightVNC because the name is so cool.

AFAICT, the "tight encoding" was pioneered by TightVNC and other branches of VNC are adopting it.

Ultr@VNC supports file xfers across the connection if both boxes are Win32.
If I remember correctly, OSXVNC is a server only. OS-X clients include Chicken of the VNC and VNCThing (my preferred as it supports bookmarks, although CotVNC has better Ctrl key support for OS-X to Win32 connections).

I've used Ultr@/Tight/Real/Tridia and decided to stick with Ultr@VNC. That was perhaps half a year ago, however, and I haven't tried the others since.

Ultr@VNC also has a video hook driver mode for Windows machines. Using that mode over a LAN has gotten me amazing results. I think they all have the tight encoding that TightVNC originally came up with now.

I don't think TridiaVNC has the Java applet support, which killed it as a choice for me. Being able to launch a web browser on a public terminal and logging into VNC has been very useful.