Dave,
The rule when writing VNC clients is that they should not perform pixel
translation internally unless they have good reason to do so, such as
having pixel translation hardware. All servers must therefore support
as many pixel formats as they can. The most obvious to support are 32,
16 and 8 bit truecolour formats. The current Windows VNC viewer
violates this rule and tends to just ask the server for whatever pixel
format is offered.
Protocol version 3.5 was never officially released and something better
is in the pipeline anyway, so just ignore that. In any case, the server
is entirely at liberty to implement a lower protocol version than the
client - the client should not use 3.5-specific features with a 3.3
server. Equally, a 3.5 server should not use 3.5-specific features with
a 3.3. viewer.
Oh, and WinVNC is the name of the VNC Server for Windows. The viewer
is simply called VNCViewer!
Cheers,
--
---
James "Wez" Weatherall www.spineless.org.uk
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
