|
From: Constantin K. <co...@ce...> - 2001-12-04 13:13:55
|
Hello, >>>>> "LPL" == Lane P Lester <ll...@si...> writes: LPL> I'm connecting these two machines on a LAN, and since I switched LPL> the W2K server from the AT&T VNC to Tight, it seems to run LPL> considerably slower. According to the docs, it looks like I LPL> should run it in Hexabyte code instead of Tight, but I didn't see LPL> exactly how to specify that on the command line. Win32 viewer can be started this way: vncviewer.exe -encoding hextile remote_host_name And here is a similar command line to start the Unix viewer: vncviewer -encodings 'hextile copyrect' remote_host_name TightVNC installer in versions 1.2.1 and 1.2.2 creates two icons, one for slow connections (Tight encoding, max compression) and another for fast networks (Hextile encoding). LPL> Am I correct that the spec would be on the command line of the LPL> W2K server only and not also the Linux client? No, encoding should be specified on the client side. Server just uses encodings requested by clients. LPL> Are there other parameters that would make for a better LPL> connection in my situation? I think hextile or raw encoding in combination with copyrect would achieve best results on a high-speed LAN. -- With Best Wishes, Constantin |