All content on this web site is licensed under the Creative Commons Attribution 2.5 License.Any works containing material derived from this web site must cite The VirtualGL Project as the source of the material and list the current URL for the TurboVNC web site. DFMirage mirror display driver allows TightVNC to gain the best performance under old versions of Windows. With DFMirage, TightVNC Server can detect screen updates and grab pixel data in a very efficient way.
![]()
Download TightVNCDownload TightVNCFree, Lightweight, Fast and ReliableRemote Control / Remote Desktop SoftwareThis site uses cookies.See more details here:Highlights:TightVNC:DownloadLicensing / SDK:Information:Feedback:More Products:Licensing TermsThere are two licensing options available for TightVNC software:. GNU General Public License version 2 (often abbreviated as GNU GPL). This is thedefault licensing option.
It's completely free but it does not allow integrationwith closed-source products. Read the complete text of the license (opens in a newwindow).
Commercial source code license.
This appendix provides basic reference information about TurboVNC. Topics include:
For instructions in using the TurboVNC server, see Manually Using TurboVNC. The TurboVNC commands are not normally in your PATH. Either add their location /opt/TurboVNC/bin to your PATH or enter full pathnames to the following commands.
Common TurboVNC ScenariosTurboVNC Server Scenarios
TABLE B-1 describes different scenarios for the TurboVNC server, the vncserver command, and respective comments.
Upon startup, the TurboVNC server session uses the userâs VNC startup file. If the file does not exist, the TurboVNC session creates one. This startup file is named $HOME/.vnc/xstartup.turbovnc on release 1.1.1 and $HOME/.vnc/xstartup on previous releases. The xstartup file that TurboVNC creates uses operating system specific techniques to launch the userâs most recently used window manager.
TurboVNC Viewer Scenarios
vncviewer'>On a Windows host, start a TurboVNC viewer by selecting TurboVNC Viewer in the TurboVNC Start Menu group. A small GUI (shown in TurboVNC Connection Dialog on a Windows Client) appears to allow selection of image encoding protocol and related parameters. These are further described inTurboVNC Image Encoding Protocols and Dynamic Quality/Performance Tradeoff
TABLE B-2 describes different scenarios for starting a TurboVNC viewer from a command line. Options that would be used on UNIX and on Windows are provided.
TurboVNC Image Encoding Protocols and Dynamic Quality/Performance Tradeoff
TurboVNC allows user control to balance the (often conflicting) goals of high image quality and high performance. First we describe the options that control TurboVNCâs compression of images in TABLE B-3. Then we describe predefined option combinations in Useful Combinations of TurboVNC Quality and Performance Options.
TABLE B-4 lists the most useful combinations of the compression options above. These are called the âImage Encoding Protocolâ in release 1.1.1. In previous releases, these were known as Connection Profiles (with a slightly different set of options). âTightâ refers to the image encoding used by TightVNC, on which TurboVNC is based.
This selection can be made statically for your viewer session or changed dynamically âon-the-flyâ as you use your viewer session. Selecting the Image Encoding depends on your viewer.
For dynamic control of the protocol, after connecting to your server, click the Options button at the top of the browser window to obtain the same dialog.
FIGURE B-1 WebVNC Options Dialog
For dynamic control of the protocol, after connecting to the server, click on the Connection Options button in the toolbar to obtain the same dialog.
FIGURE B-2 TurboVNC Viewer Options Dialog on a Windows Client
![]()
For dynamic control of the protocol, you can press the F8 key after connecting to display a menu (see FIGURE B-3) from which you can dynamically control the image encoding protocol and parameters.
FIGURE B-3 TurboVNCâs Configuration Dialog (Defaults for Perceptually Lossless JPEG Are Shown)
Lossless Refresh
TurboVNC can optionally compress images losslessly, but this mode does not perform well except on extremely fast networks. Another option for quality-critical applications is the Lossless Refresh feature. Lossless Refresh causes the server to send a mathematically lossless copy of the current screen to the viewer. So, for instance, you can rotate, pan, or zoom an object in your application using a very lossy quality setting. Then, when you are ready to interpret or analyze the object closely, you can request a lossless refresh of the screen.
![]()
Take one of the following actions, depending on your viewer:
Troubleshooting Common TurboVNC Session Startup ErrorsX Font Server Issues
On some systems, when you start the TurboVNC server session, this message appears:
Usually after this message is displayed, the TurboVNC session starts, but without all the fonts that would be available if the font server were running.
This message is normally caused by the X font server not running. This issue is unlikely to occur with TurboVNC 0.5 (in Sun Shared Visualization 1.1.1) or later releases, because it attempts to find the fonts it needs without depending on the font server. If you encounter font server issues, you can, as superuser, configure the X font server to start automatically.
As superuser, enter the command appropriate to the operating system.
On many Linux systems, you also can start the X font server immediately. Enter:
X Authentication Issues
TurboVNC relies on xauth, the X authentication control program. Your script that starts up vncserver might not find xauth unless it is included in your PATH. When xauth is not found, the TurboVNC session might fail to start or might start an X server that cannot be connected to by your X clients (such as windows or a window manager).
To avoid this problem, make sure that xauth is included in your PATH. Also, when you invoke the TurboVNC server, avoid unintentionally invoking a vncserver command that shares the X directory. This might happen if the X directories are listed prior to /opt/TurboVNC/bin in your PATH.
For more information on this issue, see CR 6710919 at http://sunsolve.sun.com.
xstartup Issues
Upon startup, the TurboVNC server session uses the userâs VNC startup file. If the file does not exist, the TurboVNC session creates one. This startup file is named $HOME/.vnc/xstartup.turbovnc on release 1.1.1. On previous releases, it was named $HOME/.vnc/xstartup and could contain contents from a different VNC server, which was incompatible with TurboVNC.
The startup file that TurboVNC creates uses operating system specific techniques to launch the userâs most recently used window manager. If necessary, you can edit the startup file created by TurboVNC.
Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |