x11vnc: more features to ssl_vncviewer for enhanced tightvnc viewer project

7 files changed, 1631 insertions, 1171 deletions

diff --git a/classes/ssl/ssl_vncviewer b/classes/ssl/ssl_vncviewer
index 820a666..96ad36d 100755
--- a/classes/ssl/ssl_vncviewer
+++ b/classes/ssl/ssl_vncviewer
@@ -1,21 +1,26 @@
 #!/bin/sh
 #
-# ssl_vncviewer:  wrapper for vncviewer to use an stunnel SSL tunnel.
+# ssl_vncviewer:  wrapper for vncviewer to use an stunnel SSL tunnel
+#                 or an SSH tunnel.
 #
 # Copyright (c) 2006 by Karl J. Runge <runge@karlrunge.com>
 #
-# You must have stunnel(8) installed on the system and in your
-# PATH (n.b. stunnel is usually in an sbin subdir).
+# You must have stunnel(8) installed on the system and in your PATH
+# (however, see the -ssh option below, in which case you will need ssh(1)
+# installed)  Note: stunnel is usually installed in an "sbin" subdirectory.
 #
 # You should have "x11vnc -ssl ..." or "x11vnc -stunnel ..." 
-# running as the VNC server. 
+# already running as the VNC server on the remote machine.
+# (or use stunnel on the server side for any other VNC server)
 #
-# usage: ssl_vncviewer [cert-args] host:display <vncviewer-args>
+#
+# Usage: ssl_vncviewer [cert-args] host:display <vncviewer-args>
 #
 # e.g.:  ssl_vncviewer snoopy:0
 #        ssl_vncviewer snoopy:0 -encodings "copyrect tight zrle hextile"
 #
 # [cert-args] can be:
+#
 #	-verify /path/to/cacert.pem		
 #	-mycert /path/to/mycert.pem		
 #	-proxy  host:port
@@ -30,7 +35,39 @@
 #         to reach the VNC server (e.g. your firewall requires a proxy).
 #         For the "double proxy" case use -proxy host1:port1,host2:port2
 #
-# A couple other args (not related to certs):
+#    See http://www.karlrunge.com/x11vnc/#faq-ssl-ca for details on SSL
+#    certificates with VNC.
+#
+# A few other args (not related to SSL and certs):
+#
+# -ssh    Use ssh instead of stunnel SSL.  ssh(1) must be installed and you
+#         must be able to log into the remote machine via ssh.
+#
+#         In this case "host:display" may be of the form "user@host:display"
+#         where "user@host" is used for the ssh login (see ssh(1) manpage).
+#
+#         If -proxy is supplied it can be of the forms: "gwhost" "gwhost:port"
+#         "user@gwhost" or "user@gwhost:port".  "gwhost" is an incoming ssh 
+#         gateway machine (the VNC server is not running there), an ssh -L
+#         redir is used to "host" in "host:display" from "gwhost". Any "user@"
+#         part must be in the -proxy string (not in "host:display").
+#
+#         Under -proxy use "gwhost:port" if connecting to any ssh port
+#         other than the default (22).  (even for the non-gateway case,
+#         -proxy must be used to specify a non-standard ssh port)
+#
+#         Examples:
+#
+#         ssl_vncviewer -ssh bob@bobs-home.net:0
+#         ssl_vncviewer -ssh -sshcmd 'x11vnc -localhost' bob@bobs-home.net:0
+#
+#         ssl_vncviewer -ssh -proxy fred@mygate.com:2022 mymachine:0
+#         ssl_vncviewer -ssh -proxy bob@bobs-home.net:2222 localhost:0
+#
+#
+# -sshcmd cmd   Run "cmd" via ssh instead of the default "sleep 15"
+#               e.g. -sshcmd 'x11vnc -display :0 -localhost -rfbport 5900'
+#
 #
 # -alpha  turn on cursor alphablending hack if you are using the
 #         enhanced tightvnc vncviewer.
@@ -40,14 +77,15 @@
 #         fvwm that do not otherwise work in fullscreen mode)
 #
 #
-# set VNCVIEWERCMD to whatever vncviewer command you want to use:
+# set VNCVIEWERCMD to whatever vncviewer command you want to use.
 #
 VNCIPCMD=${VNCVIEWERCMD:-vncip}
 VNCVIEWERCMD=${VNCVIEWERCMD:-vncviewer}
 #
-# Same for STUNNEL, e.g. /path/to/stunnel or stunnel4, etc.
+# Same for STUNNEL, e.g. set it to /path/to/stunnel or stunnel4, etc.
 #
 
+
 PATH=$PATH:/usr/sbin:/usr/local/sbin:/dist/sbin; export PATH
 
 if [ "X$STUNNEL" = "X" ]; then
@@ -60,10 +98,13 @@ if [ "X$STUNNEL" = "X" ]; then
 fi
 
 help() {
-	head -39 $0 | tail +2
+	tail +2 "$0" | sed -e '/^$/ q'
 }
 
 gotalpha=""
+use_ssh=""
+ssl_sleep=15
+ssh_cmd="sleep $ssl_sleep"
 
 # grab our cmdline options:
 while [ "X$1" != "X" ]
@@ -75,12 +116,18 @@ do
                 ;;
 	"-proxy")	shift; proxy="$1"
                 ;;
+	"-ssh")		use_ssh=1
+                ;;
+	"-sshcmd")	shift; ssh_cmd="$1"
+                ;;
 	"-alpha")	gotalpha=1
                 ;;
 	"-grab")	VNCVIEWER_GRAB_SERVER=1; export VNCVIEWER_GRAB_SERVER
                 ;;
 	"-h"*)	help; exit 0
                 ;;
+	"--h"*)	help; exit 0
+                ;;
 	*)	break
                 ;;
     esac
@@ -95,6 +142,13 @@ fi
 orig="$1"
 shift
 
+if [ "X$use_ssh" = "X1" ]; then
+	if [ "X$mycert" != "X" -o "X$verify" != "X" ]; then
+		echo "-mycert and -verify cannot be used in -ssh mode" 
+		exit 1
+	fi
+fi
+
 # play around with host:display port:
 if echo "$orig" | grep ':' > /dev/null; then
 	:
@@ -117,7 +171,7 @@ fi
 use=""
 inuse=""
 if uname | grep Linux > /dev/null; then
-	inuse=`netstat -ant | grep LISTEN | awk '{print $4}' | sed 's/^.*://'`
+	inuse=`netstat -ant | egrep 'LISTEN|WAIT|ESTABLISH|CLOSE' | awk '{print $4}' | sed 's/^.*://'`
 elif uname | grep SunOS > /dev/null; then
 	inuse=`netstat -an -f inet -P tcp | grep LISTEN | awk '{print $1}' | sed 's/^.*\.//'`
 fi
@@ -140,6 +194,53 @@ if [ "X$use" = "X" ]; then
 	use=`expr $use + 5930`
 fi
 
+if [ $use -ge 5900 ]; then
+	N=`expr $use - 5900`
+else
+	N=$use
+fi
+
+if echo "$0" | grep vncip > /dev/null; then
+	VNCVIEWERCMD="$VNCIPCMD"
+fi
+
+if [ "X$use_ssh" = "X1" ]; then
+	ssh_port="22"
+	ssh_host="$host"
+	vnc_host="localhost"
+	ssh=${SSH:-"ssh -x"}
+	if [ "X$proxy" != "X" ]; then
+		ssh_port=`echo "$proxy" | awk -F: '{print $2}'`
+		if [ "X$ssh_port" = "X" ]; then
+			ssh_port="22"
+		fi
+		ssh_host=`echo "$proxy" | awk -F: '{print $1}'`
+		vnc_host="$host"
+	fi
+	echo ""
+	echo "Running ssh:"
+	echo "$ssh -f -p $ssh_port -L ${use}:${vnc_host}:${port} $ssh_host \"$ssh_cmd\""
+	$ssh -f -p $ssh_port -L ${use}:${vnc_host}:${port} $ssh_host "$ssh_cmd"
+	if [ "$?" != "0" ]; then
+		echo ""
+		echo "ssh to $ssh_host failed."
+		exit 1
+	fi
+	echo ""
+	if [ "X$ssh_cmd" = "Xsleep $ssl_sleep" ] ; then
+		sleep 1
+	else
+		# let any command get started a bit.
+		sleep 5
+	fi
+	echo ""
+	echo "Running viewer:"
+	echo $VNCVIEWERCMD "$@" localhost:$N
+	$VNCVIEWERCMD "$@" localhost:$N
+
+	exit $?
+fi
+
 # create the stunnel config file:
 if [ "X$verify" != "X" ]; then
 	if [ -d $verify ]; then
@@ -154,6 +255,27 @@ if [ "X$mycert" != "X" ]; then
 	cert="cert = $mycert"
 fi
 
+mytmp() {
+	tf=$1
+	rm -rf "$tf" || exit 1
+	if [ -d "$tf" ]; then
+		echo "tmp file $tf still exists as a directory."
+		exit 1
+	elif [ -L "$tf" ]; then
+		echo "tmp file $tf still exists as a symlink."
+		exit 1
+	elif [ -f "$tf" ]; then
+		echo "tmp file $tf still exists."
+		exit 1
+	fi
+	touch "$tf" || exit 1
+	chmod 600 "$tf" || exit 1
+}
+
+if echo "$RANDOM" | grep '[^0-9]' > /dev/null; then
+	RANDOM=`date +%S`
+fi
+
 pcode() {
 	tf=$1
 	SSL_VNC_PROXY=$proxy; export SSL_VNC_PROXY
@@ -274,19 +396,15 @@ sub xfer {
 	close($out);
 }
 '
-	rm -f $tf
-	if [ -f $tf ]; then
-		echo "$tf still exists!"
-		exit 1
-	fi
 	echo "$cod" > $tf
 	chmod 700 $tf
 }
 
 ptmp=""
 if [ "X$proxy" != "X" ]; then
-	ptmp="/tmp/ssl_vncviewer.$$.pl"
-	pcode $ptmp
+	ptmp="/tmp/ssl_vncviewer${RANDOM}.$$.pl"
+	mytmp "$ptmp"
+	pcode "$ptmp"
 	connect="exec = $ptmp"
 else
 	connect="connect = $host:$port"
@@ -294,8 +412,10 @@ fi
 
 
 ##debug = 7
-tmp=/tmp/ssl_vncviewer.$$
-cat > $tmp <<END
+tmp=/tmp/ssl_vncviewer${RANDOM}.$$
+mytmp "$tmp"
+
+cat > "$tmp" <<END
 foreground = yes
 pid =
 client = yes
@@ -311,12 +431,13 @@ END
 echo ""
 echo "Using this stunnel configuration:"
 echo ""
-cat $tmp | uniq
+cat "$tmp" | uniq
 echo ""
 sleep 1
 
-echo "running: $STUNNEL $tmp"
-$STUNNEL $tmp < /dev/tty > /dev/tty &
+echo ""
+echo "Running: $STUNNEL $tmp"
+$STUNNEL "$tmp" < /dev/tty > /dev/tty &
 pid=$!
 echo ""
 
@@ -326,18 +447,12 @@ if [ "X$mycert" != "X" ]; then
 	sleep 4
 fi
 sleep 2
-rm -f $tmp
+rm -f "$tmp"
 
-if [ $use -ge 5900 ]; then
-	n=`expr $use - 5900`
-fi
-
-if echo "$0" | grep vncip > /dev/null; then
-	# hack for runge's special wrapper script vncip.
-	$VNCIPCMD "$@" localhost:$n
-else
-	$VNCVIEWERCMD "$@" localhost:$n
-fi
+echo ""
+echo "Running viewer:"
+echo $VNCVIEWERCMD "$@" localhost:$N
+$VNCVIEWERCMD "$@" localhost:$N
 
 kill $pid
 sleep 1
diff --git a/x11vnc/README b/x11vnc/README
index 6ad6e2e..85cf13b 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
 
-x11vnc README file                         Date: Fri Jul 28 15:40:45 EDT 2006
+x11vnc README file                         Date: Sun Jul 30 23:30:27 EDT 2006
 
 The following information is taken from these URLs:
 
@@ -28,7 +28,8 @@ x11vnc: a VNC server for real X displays
    It has built-in [7]SSL encryption and authentication, UNIX [8]account
    and password support, server-side [9]scaling, [10]single port HTTPS
    and VNC, and TightVNC and UltraVNC [11]file-transfer. It has also been
-   extended to work with [12]webcams and TV tuner capture devices.
+   extended to work with [12]webcams and TV tuner capture devices and
+   with [13]embedded Linux systems such as Qtopia Core.
 
    I wrote x11vnc back in 2002 because x0rfbserver was basically
    impossible to build on Solaris and had poor performance. The primary
@@ -37,11 +38,15 @@ x11vnc: a VNC server for real X displays
    added a some enhancements to improve the interactive response, add
    many esoteric features, etc.
 
-   This page and the [13]FAQ contain a lot of information [14][*] and
+   This page and the [14]FAQ contain a lot of information [15][*] and
    solutions to many problems and interesting applications, but
-   nevertheless please feel free to [15]contact me if you have problems
+   nevertheless please feel free to [16]contact me if you have problems
    or questions.
 
+   An x11vnc side-project provides an [17]Enhanced TightVNC Viewer
+   package with automatic SSL (and SSH) tunnelling support, NewFBSize
+   support on Unix, and cursor alphablending.
+
     Background:
 
    VNC (Virtual Network Computing) is a very useful network graphics
@@ -51,10 +56,10 @@ x11vnc: a VNC server for real X displays
    framebuffer (RFB) protocol
 
    Some VNC links:
-     * [16]http://www.realvnc.com
-     * [17]http://www.tightvnc.com
-     * [18]http://www.ultravnc.com/
-     * [19]http://www.redstonesoftware.com/
+     * [18]http://www.realvnc.com
+     * [19]http://www.tightvnc.com
+     * [20]http://www.ultravnc.com/
+     * [21]http://www.redstonesoftware.com/
 
    For Unix, the traditional VNC implementation includes a virtual X11
    server Xvnc (usually launched via the vncserver command) that is not
@@ -92,9 +97,9 @@ x11vnc: a VNC server for real X displays
    display you wish to view is "far-away.east:0" and the workstation you
    are presently working at is "sitting-here.west".
 
-   Step 0. Download x11vnc ([20]see below) and have it available to run
+   Step 0. Download x11vnc ([22]see below) and have it available to run
    on far-away.east. Similarly, have a VNC viewer (e.g. vncviewer) ready
-   to run on sitting-here.west. We recommend [21]TightVNC Viewers.
+   to run on sitting-here.west. We recommend [23]TightVNC Viewers.
 
    Step 1. By some means log in to far-away.east and get a command shell
    running there. You can use ssh, rlogin, telnet, or any other method to
@@ -113,11 +118,11 @@ x11vnc: a VNC server for real X displays
    display (i.e. no viewer clients yet).
 
    Common Gotcha: To get X11 permissions right, you may also need to set
-   the XAUTHORITY environment variable (or use the [22]-auth option) to
+   the XAUTHORITY environment variable (or use the [24]-auth option) to
    point to the correct MIT-MAGIC-COOKIE file (e.g.
    /home/joe/.Xauthority). If x11vnc does not have the authority to
    connect to the display it exits immediately. More on how to fix this
-   [23]below.
+   [25]below.
 
    If you suspect an X11 permissions problem do this simple test: while
    sitting at the physical X display open a terminal window
@@ -125,7 +130,7 @@ x11vnc: a VNC server for real X displays
    successfully in that terminal without any need for command line
    options. If that works OK then you know X11 permissions are the only
    thing preventing it from working when you try to start x11vnc via a
-   remote shell. Then fix this with the tips [24]below.
+   remote shell. Then fix this with the tips [26]below.
 
    When x11vnc starts up there will then be much chatter printed out,
    until it finally says something like:
@@ -144,8 +149,8 @@ x11vnc: a VNC server for real X displays
    viewers for Unix, Windows, MacOS, Java-enabled web browsers, and even
    for PDA's like the Palm Pilot! You can use any of them to connect to
    x11vnc (see the above VNC links under "Background:" on how to obtain a
-   viewer for your platform or see [25]this FAQ. For Solaris, vncviewer
-   is available in the [26]Companion CD package SFWvnc).
+   viewer for your platform or see [27]this FAQ. For Solaris, vncviewer
+   is available in the [28]Companion CD package SFWvnc).
 
    In this example we'll use the Unix vncviewer program on sitting-here
    by typing the following command in a second terminal window:
@@ -155,13 +160,13 @@ x11vnc: a VNC server for real X displays
    That should pop up a viewer window on sitting-here.west showing and
    allowing interaction with the far-away.east:0  X11 desktop. Pretty
    nifty! When finished, exit the viewer: the remote x11vnc process will
-   shutdown automatically (or you can use the [27]-forever option to have
+   shutdown automatically (or you can use the [29]-forever option to have
    it wait for additional viewer connections).
 
    Shortcut: Of course if you left x11vnc running on far-away.east:0 in a
-   terminal window with the [28]-forever option or as a [29]service,
+   terminal window with the [30]-forever option or as a [31]service,
    you'd only have to do Step 3 as you moved around. Be sure to use a VNC
-   [30]Password or [31]other measures if you do that.
+   [32]Password or [33]other measures if you do that.
 
 
    Desktop Sharing: The above more or less assumed nobody was sitting at
@@ -177,7 +182,7 @@ x11vnc: a VNC server for real X displays
    For these cases it should be obvious how it is done. The above steps
    will work, but more easily the user sitting at far-away.east:0 simply
    starts up x11vnc from a terminal window, after which the guests would
-   start their VNC viewers. For this usage mode the "[32]-connect
+   start their VNC viewers. For this usage mode the "[34]-connect
    host1,host2" option may be of use automatically connect to vncviewers
    in "-listen" mode on the list of hosts.
      _________________________________________________________________
@@ -206,13 +211,13 @@ splay :0'
    Note that "x11vnc -localhost ..." limits incoming vncviewer
    connections to only those from the same machine. This is very natural
    for ssh tunnelling (the redirection appears to come from the same
-   machine). Use of a [33]VNC password is also strongly recommended.
+   machine). Use of a [35]VNC password is also strongly recommended.
 
    Some VNC viewers will do the ssh tunnelling for you automatically, the
    TightVNC vncviewer does this when the "-via far-away.east" option is
    supplied to it (this requires x11vnc to be already running on
-   far-away.east or having it started by [34]inetd(8)). See the 3rd
-   script example [35]below for more info.
+   far-away.east or having it started by [36]inetd(8)). See the 3rd
+   script example [37]below for more info.
 
    If the machine you SSH into is not the same machine with the X display
    you wish to view (e.g. your company provides incoming SSH access to a
@@ -221,7 +226,7 @@ splay :0'
    (ssh, rsh, etc.) to the workstation machine 'otherhost' and then start
    up x11vnc on it (if it isn't already running). For an automatic way to
    use a gateway and have all the network traffic encrypted (including
-   inside the firewall) see [36]chaining ssh's
+   inside the firewall) see [38]chaining ssh's
 
      _________________________________________________________________
 
@@ -230,9 +235,13 @@ splay :0'
    above port and display numbers may change a bit (e.g. -> 5901 and :1).
    However, if you "know" port 5900 will be free on the local and remote
    machines, you can easily automate the above two steps by using the
-   x11vnc option [37]-bg (forks into background after connection to the
+   x11vnc option [39]-bg (forks into background after connection to the
    display is set up) or using the -f option of ssh. Some example scripts
    are shown below.
+
+   You may also want to look at the [40]Enhanced TightVNC Viewer
+   packages, because they contain scripts and guis to automatically set
+   up SSH tunnels (e.g. "ssl_tightvncviewer -ssh user@far-away.east:0")
      _________________________________________________________________
 
    #1. A simple example script, assuming no problems with port 5900 being
@@ -240,6 +249,7 @@ splay :0'
 #!/bin/sh
 # usage: x11vnc_ssh <host>:<xdisplay>
 #  e.g.: x11vnc_ssh snoopy.peanuts.com:0
+#  (user@host:N also works)
 
 host=`echo $1 | awk -F: '{print $1}'`
 disp=`echo $1 | awk -F: '{print $2}'`
@@ -261,10 +271,11 @@ done
 
    #2. Another method is to start the VNC viewer in listen mode
    "vncviewer -listen" and have x11vnc initiate a reverse connection
-   using the [38]-connect option:
+   using the [41]-connect option:
 #!/bin/sh
 # usage: x11vnc_ssh <host>:<xdisplay>
 #  e.g.: x11vnc_ssh snoopy.peanuts.com:0
+#  (user@host:N also works)
 
 host=`echo $1 | awk -F: '{print $1}'`
 disp=`echo $1 | awk -F: '{print $2}'`
@@ -303,7 +314,7 @@ export VNC_VIA_CMD
 vncviewer -via $host localhost:0      # must be TightVNC vncviewer.
 
    Of course if you already have the x11vnc running waiting for
-   connections (or have it started out of [39]inetd(8)), you can simply
+   connections (or have it started out of [42]inetd(8)), you can simply
    use the TightVNC "vncviewer -via gateway host:port" in its default
    mode to provide secure ssh tunnelling.
      _________________________________________________________________
@@ -311,20 +322,20 @@ vncviewer -via $host localhost:0      # must be TightVNC vncviewer.
 
 
    VNC password file: Also note in the #1. example script that the
-   [40]option "-rfbauth .vnc/passwd" provides additional protection by
+   [43]option "-rfbauth .vnc/passwd" provides additional protection by
    requiring a VNC password for every VNC viewer that connects. The
-   vncpasswd or storepasswd programs, or the x11vnc [41]-storepasswd
+   vncpasswd or storepasswd programs, or the x11vnc [44]-storepasswd
    option can be used to create the password file. x11vnc also has the
-   slightly less secure [42]-passwdfile and "-passwd XXXXX" [43]options
+   slightly less secure [45]-passwdfile and "-passwd XXXXX" [46]options
    to specify passwords.
 
    Very Important: It is up to YOU to tell x11vnc to use password
    protection (-rfbauth or -passwdfile), it will NOT do it for you
-   automatically or force you to (see [44]-usepw if you want to be forced
+   automatically or force you to (see [47]-usepw if you want to be forced
    to). The same goes for encrypting the channel between the viewer and
-   x11vnc: it is up to you to use ssh, stunnel, [45]-ssl mode, a VPN,
+   x11vnc: it is up to you to use ssh, stunnel, [48]-ssl mode, a VPN,
    etc. For additional safety, also look into the -allow and -localhost
-   [46]options and building x11vnc with [47]tcp_wrappers support to limit
+   [49]options and building x11vnc with [50]tcp_wrappers support to limit
    host access.
 
      _________________________________________________________________
@@ -332,39 +343,43 @@ vncviewer -via $host localhost:0      # must be TightVNC vncviewer.
     Tunnelling x11vnc via SSL:
 
    One can also encrypt the VNC traffic using an SSL tunnel such as
-   [48]stunnel or using the built-in (Mar/2006) [49]-ssl openssl mode. A
+   [51]stunnel or using the built-in (Mar/2006) [52]-ssl openssl mode. A
    SSL-enabled Java applet VNC Viewer is also provided (and https can be
    used to download it).
 
    Although not as ubiquitous as ssh, SSL tunnelling still provides a
-   useful alternative. See [50]this FAQ on -ssl and -stunnel modes for
+   useful alternative. See [53]this FAQ on -ssl and -stunnel modes for
    details and examples.
+
+   The [54]Enhanced TightVNC Viewer packages contains some convenient
+   utilities to automatically set up and SSL tunnel form the viewer-side
+   (i.e. to connect to "x11vnc -ssl ..."). And other enhancements too.
      _________________________________________________________________
 
     Downloading x11vnc:
 
-   x11vnc is a contributed program to the [51]LibVNCServer project at
+   x11vnc is a contributed program to the [55]LibVNCServer project at
    SourceForge.net. I use libvncserver for all of the VNC aspects; I
    couldn't have done without it. The full source code may be found and
    downloaded (either file-release tarball or CVS tree) from the above
-   link. As of Jul 2006, the [52]x11vnc-0.8.2.tar.gz source package is
-   released (recommended download). The [53]x11vnc 0.8.2 release notes.
+   link. As of Jul 2006, the [56]x11vnc-0.8.2.tar.gz source package is
+   released (recommended download). The [57]x11vnc 0.8.2 release notes.
 
    The x11vnc package is the subset of the libvncserver package needed to
    build the x11vnc program. Also, you can get a copy of my latest,
-   bleeding edge [54]x11vnc-0.8.3.tar.gz tarball to build the most up to
+   bleeding edge [58]x11vnc-0.8.3.tar.gz tarball to build the most up to
    date one.
 
-   Precompiled Binaries/Packages:  See the [55]FAQ below for information
+   Precompiled Binaries/Packages:  See the [59]FAQ below for information
    about where you might obtain a precompiled x11vnc binary from 3rd
    parties and some ones I create.
 
    To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
    try these links:
-     * [56]http://www.tightvnc.com/download.html
-     * [57]http://www.realvnc.com/download-free.html
-     * [58]http://sourceforge.net/projects/cotvnc/
-     * [59]http://www.ultravnc.com/
+     * [60]http://www.tightvnc.com/download.html
+     * [61]http://www.realvnc.com/download-free.html
+     * [62]http://sourceforge.net/projects/cotvnc/
+     * [63]http://www.ultravnc.com/
 
 
    More tools: Here is a rsh/ssh wrapper script rx11vnc that attempts to
@@ -375,8 +390,8 @@ vncviewer -via $host localhost:0      # must be TightVNC vncviewer.
    rx11vnc.pl that attempts to tunnel the vnc traffic through an ssh port
    redirection (and does not assume port 5900 is free). Have a look at
    them to see what they do and customize as needed:
-     * [60]rx11vnc wrapper script
-     * [61]rx11vnc.pl wrapper script to tunnel traffic thru ssh
+     * [64]rx11vnc wrapper script
+     * [65]rx11vnc.pl wrapper script to tunnel traffic thru ssh
 
      _________________________________________________________________
 
@@ -407,8 +422,8 @@ vncviewer -via $host localhost:0      # must be TightVNC vncviewer.
    Note: Currently gcc is recommended to build libvncserver. In some
    cases it will build with non-gcc compilers, but the resulting binary
    sometimes fails to run properly. For Solaris pre-built gcc binaries
-   are at [62]http://www.sunfreeware.com/. Some Solaris pre-built x11vnc
-   binaries are [63]here.
+   are at [66]http://www.sunfreeware.com/. Some Solaris pre-built x11vnc
+   binaries are [67]here.
 
    However, one user reports it does work fine when built with Sun Studio
    10, so YMMV. In fact, here is a little build script to do this on
@@ -428,12 +443,12 @@ export MAKE AM_CFLAGS
 $MAKE
 
    In general you can use the "make -e" trick if you don't like
-   libvncserver's choice of AM_CFLAGS. See the [64]build scripts below
+   libvncserver's choice of AM_CFLAGS. See the [68]build scripts below
    for more ideas. Scripts similar to the above have been shown to work
    with vendor C compilers on HP-UX (ccom: HP92453-01) and Tru64 (Compaq
    C V6.5-011).
 
-   You can find information on [65]Misc. Build problems here.
+   You can find information on [69]Misc. Build problems here.
 
      _________________________________________________________________
 
@@ -471,9 +486,9 @@ r/sfw; make'
 
    If your system does not have these libraries at all you can get the
    source for the libraries to build them: libjpeg is available at
-   [66]ftp://ftp.uu.net/graphics/jpeg/ and zlib at
-   [67]http://www.gzip.org/zlib/. See also
-   [68]http://www.sunfreeware.com/ for Solaris binary packages of these
+   [70]ftp://ftp.uu.net/graphics/jpeg/ and zlib at
+   [71]http://www.gzip.org/zlib/. See also
+   [72]http://www.sunfreeware.com/ for Solaris binary packages of these
    libraries as well as for gcc. Normally they will install into
    /usr/local but you can install them anywhere with the
    --prefix=/path/to/anywhere, etc.
@@ -544,7 +559,7 @@ ls -l ./x11vnc/x11vnc
    script.
 
    If you need to build on Solaris 2.5.1 or earlier or other older Unix
-   OS's, see [69]this workaround FAQ.
+   OS's, see [73]this workaround FAQ.
 
 
    Building on FreeBSD, OpenBSD, ...:   The jpeg libraries seem to be in
@@ -592,19 +607,20 @@ make
    Summer/Fall 2006.
 
    The version 0.8.3 beta tarball is kept here:
-   [70]x11vnc-0.8.3.tar.gz
+   [74]x11vnc-0.8.3.tar.gz
 
    There are also some Linux, Solaris, and other OS test binaries
-   [71]here. Please kick the tires and report bugs, performance
-   regressions, undesired behavior, etc. to [72]me.
+   [75]here. Please kick the tires and report bugs, performance
+   regressions, undesired behavior, etc. to [76]me.
 
-   To aid testing of the [73]built-in SSL support for x11vnc, a number of
+   To aid testing of the [77]built-in SSL support for x11vnc, a number of
    packages for Unix and Windows have been created that provide SSL
-   Support for the TightVNC Viewer (this is done by [74]wrapper scripts
-   that start STUNNEL, [75]more details here) It should be pretty
+   Support for the TightVNC Viewer (this is done by [78]wrapper scripts
+   that start STUNNEL, [79]more details here) It should be pretty
    convenient for SSL connections. A number of other features where added
    to TightVNC Viewer (e.g. rfbNewFBSize resizing support). It is
-   described and can be downloaded from [76]here.
+   described and can be downloaded from the [80]Enhanced TightVNC Viewer
+   page.
 
 
    Here are some features that appeared in the 0.8.2 release:
@@ -612,61 +628,65 @@ make
        supported by the uinput linux device driver. This enables full
        interaction with non-X applications on the Linux console (e.g.
        Qt-embedded/Qtopia-Core apps). This will be autodetected in:
-       [77]-rawfb console mode, and can be forced on via: [78]-pipeinput
+       [81]-rawfb console mode, and can be forced on via: [82]-pipeinput
        UINPUT
-     * The [79]-display WAIT:... option extends the normal [80]-display
+     * The [83]-display WAIT:... option extends the normal [84]-display
        option by having x11vnc wait until a VNC viewer connects before
        attaching to an X display. A command can also be supplied that
        will determine the DISPLAY and XAUTHORITY data. A default one is
        built-in for WAIT:cmd=FINDDISPLAY. Coupling this with "-unixpw
        -users unixpw=" (available in beta version) provides a way to
        allow a user to login with their UNIX password and have their
-       display connected to [81]automatically.
-     * The [82]-grabkdb and [83]-grabptr options allow some degree of
+       display connected to [85]automatically.
+     * The [86]-grabkdb and [87]-grabptr options allow some degree of
        grabbing the pointer and keyboard so local users cannot perform
        input (e.g. remote helpdesk application).
      * More new options:
-          + [84]-allowedcmds to fine-tune which external commands may be
+          + [88]-allowedcmds to fine-tune which external commands may be
             run by x11vnc, rather than shutting them all off with
-            [85]-nocmds,
-          + [86]-env VAR=VALUE convenience option to avoid the need of
+            [89]-nocmds,
+          + [90]-env VAR=VALUE convenience option to avoid the need of
             setting environment variables before starting x11vnc,
-          + [87]-allinput option to enable libvncserver
+          + [91]-allinput option to enable libvncserver
             handleEventsEagerly parameter,
-          + [88]-rawfb rand fun/testing option using /dev/urandom as a
+          + [92]-rawfb rand fun/testing option using /dev/urandom as a
             fb,
-          + [89]-license print license, copying, warranty information.
+          + [93]-license print license, copying, warranty information.
 
 
    Here are some features that will appear in the 0.8.3 release:
-     * The [90]-ssl option provides SSL encryption and authentication
-       natively via the [91]www.openssl.org library. One can use from a
+     * The [94]-ssl option provides SSL encryption and authentication
+       natively via the [95]www.openssl.org library. One can use from a
        simple self-signed certificate server certificate up to full CA
        and client certificate authentication schemes.
-     * The [92]-stunnel option starts up a SSL tunnel server stunnel
+     * The [96]-stunnel option starts up a SSL tunnel server stunnel
        (that must be installed separately on the system:
-       [93]www.stunnel.org) to allow only encrypted SSL connections from
+       [97]www.stunnel.org) to allow only encrypted SSL connections from
        the network.
-     * The [94]-sslverify option allows for authenticating VNC clients
+     * The [98]-sslverify option allows for authenticating VNC clients
        via their certificates in either -ssl or -stunnel modes.
      * An SSL enabled Java applet VNC Viewer applet is provided in
        classes/ssl/VncViewer.jar. It may also be loaded into the web
        browser via https (http over SSL) in addition to http. (via the
-       VNC port or also by the separate [95]-https port option). A
-       wrapper shell script [96]ssl_vncviewer is also provided that sets
+       VNC port or also by the separate [99]-https port option). A
+       wrapper shell script [100]ssl_vncviewer is also provided that sets
        up a stunnel client-side tunnel on Unix systems.
-     * The [97]-unixpw option supports Unix username and password
-       authentication (a variant is the [98]-unixpw_nis option that works
-       in NIS environments). The [99]-ssl or [100]-localhost +
-       [101]-stunnel options are enforced in this mode to prevent
+     * The [101]-unixpw option supports Unix username and password
+       authentication (a variant is the [102]-unixpw_nis option that
+       works in NIS environments). The [103]-ssl or [104]-localhost +
+       [105]-stunnel options are enforced in this mode to prevent
        password sniffing. As a convenience, the -ssl or -stunnel
        requirements are lifted if a SSH tunnel can be deduced (but
        -localhost still applies). Coupling -unixpw with "-display
        WAIT:cmd=FINDDISPLAY" provides a way to allow a user to login with
        their UNIX password and have their display connected to
-       [102]automatically.
+       [106]automatically.
+     * The [107]-rotate option enables you to rotate or reflect the
+       screen before exporting via VNC. This is intended for use on
+       handhelds and other devices where the rotation orientation is not
+       "natural".
 
-   Here are some [103]previous release notes
+   Here are some [108]previous release notes
      _________________________________________________________________
 
     Some Notes:
@@ -693,11 +713,11 @@ make
    protocol.) I suggest using xsetroot, dtstyle or similar utility to set
    a solid background while using x11vnc. You can turn the pretty
    background image back on when you are using the display directly.
-   Update: As of Feb/2005 x11vnc has the [104]-solid [color] option that
+   Update: As of Feb/2005 x11vnc has the [109]-solid [color] option that
    works on recent GNOME, KDE, and CDE and also on classic X (background
    image is on the root window).
 
-   I also find the [105]TightVNC encoding gives the best response for my
+   I also find the [110]TightVNC encoding gives the best response for my
    usage (Unix <-> Unix over cable modem). One needs a tightvnc-aware
    vncviewer to take advantage of this encoding.
 
@@ -709,16 +729,16 @@ make
    is X11's default listening port). Had port 5900 been taken by some
    other application, x11vnc would have next tried 5901. That would mean
    the viewer command above should be changed to vncviewer
-   far-away.east:1. You can force the port with the "[106]-rfbport NNNN"
+   far-away.east:1. You can force the port with the "[111]-rfbport NNNN"
    option where NNNN is the desired port number. If that port is already
    taken, x11vnc will exit immediately.   (also see the "SunRay Gotcha"
    note below)
 
    Options:   x11vnc has (far too) many features that may be activated
-   via its [107]command line options. Useful options are, e.g., -scale to
+   via its [112]command line options. Useful options are, e.g., -scale to
    do server-side scaling, and -rfbauth passwd-file to use VNC password
    protection (the vncpasswd or storepasswd programs, or the x11vnc
-   [108]-storepasswd option can be used to create the password file).
+   [113]-storepasswd option can be used to create the password file).
 
    Algorithm:   How does x11vnc do it? Rather brute-forcedly: it
    continuously polls the X11 framebuffer for changes using
@@ -745,7 +765,7 @@ make
    first testing out the programs. You get an interesting
    recursive/feedback effect where vncviewer images keep popping up each
    one contained in the previous one and slightly shifted a bit by the
-   window manager decorations. There will be an [109]even more
+   window manager decorations. There will be an [114]even more
    interesting effect if -scale is used. Also, if the XKEYBOARD is
    supported and the XBell "beeps" once, you get an infinite loop of
    beeps going off. Although all of this is mildly exciting it is not
@@ -755,8 +775,8 @@ make
 
     Sun Ray Notes:
 
-   You can run x11vnc on your (connected or disconnected) [110]SunRay
-   session. Here are some [111]notes on SunRay usage with x11vnc.
+   You can run x11vnc on your (connected or disconnected) [115]SunRay
+   session. Here are some [116]notes on SunRay usage with x11vnc.
 
      _________________________________________________________________
 
@@ -768,7 +788,7 @@ make
        than you normally do to minimize the effects (e.g. do fullpage
        paging rather than line-by-line scrolling, and move windows in a
        single, quick motion). Recent work has provided the
-       [112]-scrollcopyrect and [113]-wireframe speedups using the
+       [117]-scrollcopyrect and [118]-wireframe speedups using the
        CopyRect VNC encoding and other things, but they only speed up
        certain activities, not all.
      * A rate limiting factor for x11vnc performance is that video
@@ -815,14 +835,14 @@ make
        it may be of use for special purpose applications.
        Also, a faster and more accurate way is to use the "dummy"
        XFree86/Xorg device driver (or our Xdummy wrapper script). See
-       [114]this FAQ for details.
+       [119]this FAQ for details.
      * Somewhat surprisingly, the X11 mouse (cursor) shape is write-only
        and cannot be queried from the X server. So traditionally in
        x11vnc the cursor shape stays fixed at an arrow. (see the "-cursor
-       X" and "-cursor some" [115]options, however, for a partial hack
+       X" and "-cursor some" [120]options, however, for a partial hack
        for the root window, etc.). However, on Solaris using the SUN_OVL
        overlay extension, x11vnc can show the correct mouse cursor when
-       the [116]-overlay option is also supplied. A similar thing is done
+       the [121]-overlay option is also supplied. A similar thing is done
        on IRIX as well when -overlay is supplied.
        More generally, as of Dec/2004 x11vnc supports the new XFIXES
        extension (in Xorg and Solaris 10) to query the X server for the
@@ -830,18 +850,18 @@ make
        with transparency (alpha channel) need to approximated to solid
        RGB values (some cursors look worse than others).
      * Audio from applications is of course not redirected (separate
-       redirectors do exist, e.g. esd [117]the FAQ on this below.) The
+       redirectors do exist, e.g. esd [122]the FAQ on this below.) The
        XBell() "beeps" will work if the X server supports the XKEYBOARD
        extension. (Note that on Solaris XKEYBOARD is disabled by default.
        Passing +kb to Xsun enables it).
-     * The scroll detection algorithm for the [118]-scrollcopyrect option
+     * The scroll detection algorithm for the [123]-scrollcopyrect option
        can give choppy or bunched up transient output and occasionally
        painting errors.
      * Using -threads can expose some bugs in libvncserver.
 
-   Please feel free to [119]contact me if you have any questions,
+   Please feel free to [124]contact me if you have any questions,
    problems, or comments about x11vnc, etc.
-   Also, some people ask if they can make a donation, see [120]this link
+   Also, some people ask if they can make a donation, see [125]this link
    for that.
      _________________________________________________________________
 
@@ -850,331 +870,331 @@ make
 
    [Building and Starting]
 
-   [121]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed
+   [126]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed
    (null)" or "Xlib: connection to ":0.0" refused by server Xlib: No
    protocol specified" and then exits. What do I need to do? 
 
-   [122]Q-2: I can't get x11vnc and/or libvncserver to compile. 
+   [127]Q-2: I can't get x11vnc and/or libvncserver to compile. 
 
-   [123]Q-3: I just built x11vnc successfully, but when I use it my
+   [128]Q-3: I just built x11vnc successfully, but when I use it my
    keystrokes and mouse button clicks are ignored  (I am able to move the
    mouse though). 
 
-   [124]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old
+   [129]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old
    Unix/Linux) and it doesn't compile! 
 
-   [125]Q-5: Where can I get a precompiled x11vnc binary for my Operating
+   [130]Q-5: Where can I get a precompiled x11vnc binary for my Operating
    System? 
 
-   [126]Q-6: Where can I get a VNC Viewer binary (or source code) for the
+   [131]Q-6: Where can I get a VNC Viewer binary (or source code) for the
    Operating System I will be viewing from? 
 
-   [127]Q-7: How can I see all of x11vnc's command line options and
+   [132]Q-7: How can I see all of x11vnc's command line options and
    documentation on how to use them? 
 
-   [128]Q-8: I don't like typing arcane command line options every time I
+   [133]Q-8: I don't like typing arcane command line options every time I
    start x11vnc. What can I do? Is there a config file? Or a GUI? 
 
-   [129]Q-9: How can I get the GUI to run in the System Tray, or at least
+   [134]Q-9: How can I get the GUI to run in the System Tray, or at least
    be a smaller, simpler icon? 
 
-   [130]Q-10: Can I make x11vnc more quiet and also go into the
+   [135]Q-10: Can I make x11vnc more quiet and also go into the
    background after starting up? 
 
-   [131]Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies
+   [136]Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies
    with the error message like: "Broken pipe". I'm using the -forever
    mode and I want x11vnc to keep running. 
 
-   [132]Q-12: Are there any build-time customizations possible, e.g.
+   [137]Q-12: Are there any build-time customizations possible, e.g.
    change defaults, create a smaller binary, etc? 
 
    [Win2VNC Related]
 
-   [133]Q-13: I have two separate machine displays in front of me, one
+   [138]Q-13: I have two separate machine displays in front of me, one
    Windows the other X11: can I use x11vnc in combination with Win2VNC in
    dual-screen mode to pass the keystrokes and mouse motions to the X11
    display? 
 
-   [134]Q-14: I am running Win2VNC on my Windows machine and "x11vnc
+   [139]Q-14: I am running Win2VNC on my Windows machine and "x11vnc
    -nofb" on Unix to pass keyboard and mouse to the Unix monitor.
    Whenever I start Win2VNC it quickly disconnects and x11vnc says:
    rfbProcessClientNormalMessage: read: Connection reset by peer 
 
    [Color Issues]
 
-   [135]Q-15: The X display I run x11vnc on is only 8 bits per pixel
+   [140]Q-15: The X display I run x11vnc on is only 8 bits per pixel
    (bpp) PseudoColor (i.e. only 256 distinct colors). The x11vnc colors
    may start out OK, but after a while they are incorrect in certain
    windows. 
 
-   [136]Q-16: Color problems: Why are the colors for some windows
+   [141]Q-16: Color problems: Why are the colors for some windows
    incorrect in x11vnc? BTW, my X display has nice overlay/multi-depth
    visuals of different color depths: e.g. there are both depth 8 and 24
    visuals available at the same time. 
 
-   [137]Q-17: How do I figure out the window id to supply to the -id
+   [142]Q-17: How do I figure out the window id to supply to the -id
    windowid option? 
 
-   [138]Q-18: Why don't menus or other transient windows come up when I
+   [143]Q-18: Why don't menus or other transient windows come up when I
    am using the -id windowid option to view a single application window? 
 
-   [139]Q-19: My X display is depth 24 at 24bpp (instead of the normal
+   [144]Q-19: My X display is depth 24 at 24bpp (instead of the normal
    depth 24 at 32bpp). I'm having lots of color and visual problems with
    x11vnc and/or vncviewer. What's up? 
 
    [Xterminals]
 
-   [140]Q-20: Can I use x11vnc to view and interact with an Xterminal
+   [145]Q-20: Can I use x11vnc to view and interact with an Xterminal
    (e.g. NCD) that is not running UNIX and so x11vnc cannot be run on it
    directly? 
 
-   [141]Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file)
+   [146]Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file)
    correct for a Unix/Linux machine acting as an Xterminal? 
 
    [Sun Rays]
 
-   [142]Q-22: I'm having trouble using x11vnc with my Sun Ray session. 
+   [147]Q-22: I'm having trouble using x11vnc with my Sun Ray session. 
 
    [Remote Control]
 
-   [143]Q-23: How do I stop x11vnc once it is running in the background? 
+   [148]Q-23: How do I stop x11vnc once it is running in the background? 
 
-   [144]Q-24: Can I change settings in x11vnc without having to restart
+   [149]Q-24: Can I change settings in x11vnc without having to restart
    it? Can I remote control it? 
 
    [Security and Permissions]
 
-   [145]Q-25: How do I create a VNC password for use with x11vnc? 
+   [150]Q-25: How do I create a VNC password for use with x11vnc? 
 
-   [146]Q-26: Can I make it so -storepasswd doesn't show my password on
+   [151]Q-26: Can I make it so -storepasswd doesn't show my password on
    the screen? 
 
-   [147]Q-27: Can I have two passwords for VNC viewers, one for full
+   [152]Q-27: Can I have two passwords for VNC viewers, one for full
    access and the other for view-only access to the display? 
 
-   [148]Q-28: Can I have as many full-access and view-only passwords as I
+   [153]Q-28: Can I have as many full-access and view-only passwords as I
    like? 
 
-   [149]Q-29: Does x11vnc support Unix usernames and passwords? Can I
+   [154]Q-29: Does x11vnc support Unix usernames and passwords? Can I
    further limit the set of Unix usernames who can connect to the VNC
    desktop? 
 
-   [150]Q-30: Why does x11vnc exit as soon as the VNC viewer disconnects?
+   [155]Q-30: Why does x11vnc exit as soon as the VNC viewer disconnects?
    And why doesn't it allow more than one VNC viewer to connect at the
    same time? 
 
-   [151]Q-31: Can I limit which machines incoming VNC clients can connect
+   [156]Q-31: Can I limit which machines incoming VNC clients can connect
    from? 
 
-   [152]Q-32: How do I build x11vnc/libvncserver with libwrap
+   [157]Q-32: How do I build x11vnc/libvncserver with libwrap
    (tcp_wrappers) support? 
 
-   [153]Q-33: Can I have x11vnc only listen on one network interface
+   [158]Q-33: Can I have x11vnc only listen on one network interface
    (e.g. internal LAN) rather than having it listen on all network
    interfaces and relying on -allow to filter unwanted connections out? 
 
-   [154]Q-34: Now that -localhost implies listening only on the loopback
+   [159]Q-34: Now that -localhost implies listening only on the loopback
    interface, how I can occasionally allow in a non-localhost via the -R
    allowonce remote control command? 
 
-   [155]Q-35: Can I fine tune what types of user input are allowed? E.g.
+   [160]Q-35: Can I fine tune what types of user input are allowed? E.g.
    have some users just be able to move the mouse, but not click or type
    anything? 
 
-   [156]Q-36: Can I prompt the user at the local X display whether the
+   [161]Q-36: Can I prompt the user at the local X display whether the
    incoming VNC client should be accepted or not? Can I decide to make
    some clients view-only? How about running an arbitrary program to make
    the decisions? 
 
-   [157]Q-37: I start x11vnc as root because it is launched via inetd(8)
+   [162]Q-37: I start x11vnc as root because it is launched via inetd(8)
    or a display manager like gdm(1). Can I have x11vnc later switch to a
    different user? 
 
-   [158]Q-38: I use a screen-lock when I leave my workstation (e.g.
+   [163]Q-38: I use a screen-lock when I leave my workstation (e.g.
    xscreensaver or xlock). When I remotely access my workstation desktop
    via x11vnc I can unlock the desktop fine, but I am worried people will
    see my activities on the physical monitor. What can I do to prevent
    this, or at least make it more difficult? 
 
-   [159]Q-39: Can I have x11vnc automatically lock the screen when I
+   [164]Q-39: Can I have x11vnc automatically lock the screen when I
    disconnect the VNC viewer? 
 
    [Encrypted Connections]
 
-   [160]Q-40: How can I tunnel my connection to x11vnc via an encrypted
+   [165]Q-40: How can I tunnel my connection to x11vnc via an encrypted
    SSH channel between two Unix machines? 
 
-   [161]Q-41: How can I tunnel my connection to x11vnc via an encrypted
+   [166]Q-41: How can I tunnel my connection to x11vnc via an encrypted
    SSH channel from Windows using an SSH client like Putty? 
 
-   [162]Q-42: How can I tunnel my connection to x11vnc via an encrypted
+   [167]Q-42: How can I tunnel my connection to x11vnc via an encrypted
    SSL channel using an external tool like stunnel? 
 
-   [163]Q-43: Does x11vnc have built-in SSL tunneling? 
+   [168]Q-43: Does x11vnc have built-in SSL tunneling? 
 
-   [164]Q-44: How do I use VNC Viewers with built-in SSL tunneling? 
+   [169]Q-44: How do I use VNC Viewers with built-in SSL tunneling? 
 
-   [165]Q-45: How do I use VNC Viewers with built-in SSL tunneling when
+   [170]Q-45: How do I use VNC Viewers with built-in SSL tunneling when
    going through a Web Proxy? 
 
-   [166]Q-46: Can Apache web server act as a gateway for users to connect
+   [171]Q-46: Can Apache web server act as a gateway for users to connect
    via SSL from the Internet with a Web browser to x11vnc running on
    their workstations behind a firewall? 
 
-   [167]Q-47: Can I create and use my own SSL Certificate Authority (CA)
+   [172]Q-47: Can I create and use my own SSL Certificate Authority (CA)
    with x11vnc? 
 
    [Display Managers and Services]
 
-   [168]Q-48: How can I run x11vnc as a "service" that is always
+   [173]Q-48: How can I run x11vnc as a "service" that is always
    available? 
 
-   [169]Q-49: How can I use x11vnc to connect to an X login screen like
+   [174]Q-49: How can I use x11vnc to connect to an X login screen like
    xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into
    an X session yet). 
 
-   [170]Q-50: Can I run x11vnc out of inetd(8)? How about xinetd(8)? 
+   [175]Q-50: Can I run x11vnc out of inetd(8)? How about xinetd(8)? 
 
-   [171]Q-51: Can I have x11vnc allow a user to log in with her UNIX
+   [176]Q-51: Can I have x11vnc allow a user to log in with her UNIX
    password and then have it find her X display on that machine and
    connect to it? 
 
-   [172]Q-52: Can I have x11vnc restart itself after it terminates? 
+   [177]Q-52: Can I have x11vnc restart itself after it terminates? 
 
-   [173]Q-53: How do I make x11vnc work with the Java VNC viewer applet
+   [178]Q-53: How do I make x11vnc work with the Java VNC viewer applet
    in a web browser? 
 
-   [174]Q-54: Are reverse connections (i.e. the VNC server connecting to
+   [179]Q-54: Are reverse connections (i.e. the VNC server connecting to
    the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
    
-   [175]Q-55: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
+   [180]Q-55: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
    real display, but for a virtual one I keep around). 
 
-   [176]Q-56: How can I use x11vnc on "headless" machines? Why might I
+   [181]Q-56: How can I use x11vnc on "headless" machines? Why might I
    want to? 
 
    [Resource Usage and Performance]
 
-   [177]Q-57: I have lots of memory, but why does x11vnc fail with
+   [182]Q-57: I have lots of memory, but why does x11vnc fail with
    shmget: No space left on device    or    Minor opcode of failed
    request: 1 (X_ShmAttach)? 
 
-   [178]Q-58: How can I make x11vnc use less system resources? 
+   [183]Q-58: How can I make x11vnc use less system resources? 
 
-   [179]Q-59: How can I make x11vnc use MORE system resources? 
+   [184]Q-59: How can I make x11vnc use MORE system resources? 
 
-   [180]Q-60: I use x11vnc over a slow link with high latency (e.g.
+   [185]Q-60: I use x11vnc over a slow link with high latency (e.g.
    dialup modem), is there anything I can do to speed things up? 
 
-   [181]Q-61: Does x11vnc support the X DAMAGE Xserver extension to find
+   [186]Q-61: Does x11vnc support the X DAMAGE Xserver extension to find
    modified regions of the screen quickly and efficiently? 
 
-   [182]Q-62: When I drag windows around with the mouse or scroll up and
+   [187]Q-62: When I drag windows around with the mouse or scroll up and
    down things really bog down (unless I do the drag in a single, quick
    motion). Is there anything to do to improve things? 
 
-   [183]Q-63: Why not do something like wireframe animations to avoid the
+   [188]Q-63: Why not do something like wireframe animations to avoid the
    windows "lurching" when being moved or resized? 
 
-   [184]Q-64: Can x11vnc try to apply heuristics to detect when a window
+   [189]Q-64: Can x11vnc try to apply heuristics to detect when a window
    is scrolling its contents and use the CopyRect encoding for a speedup?
    
    [Mouse Cursor Shapes]
 
-   [185]Q-65: Why isn't the mouse cursor shape (the little icon shape
+   [190]Q-65: Why isn't the mouse cursor shape (the little icon shape
    where the mouse pointer is) correct as I move from window to window? 
 
-   [186]Q-66: When using XFIXES cursorshape mode, some of the cursors
+   [191]Q-66: When using XFIXES cursorshape mode, some of the cursors
    look really bad with extra black borders around the cursor and other
    cruft. How can I improve their appearance? 
 
-   [187]Q-67: In XFIXES mode, are there any hacks to handle cursor
+   [192]Q-67: In XFIXES mode, are there any hacks to handle cursor
    transparency ("alpha channel") exactly? 
 
    [Mouse Pointer]
 
-   [188]Q-68: Why does the mouse arrow just stay in one corner in my
+   [193]Q-68: Why does the mouse arrow just stay in one corner in my
    vncviewer, whereas my cursor (that does move) is just a dot? 
 
-   [189]Q-69: Can I take advantage of the TightVNC extension to the VNC
+   [194]Q-69: Can I take advantage of the TightVNC extension to the VNC
    protocol where Cursor Positions Updates are sent back to all connected
    clients (i.e. passive viewers can see the mouse cursor being moved
    around by another viewer)? 
 
-   [190]Q-70: Is it possible to swap the mouse buttons (e.g. left-handed
+   [195]Q-70: Is it possible to swap the mouse buttons (e.g. left-handed
    operation), or arbitrarily remap them? How about mapping button clicks
    to keystrokes, e.g. to partially emulate Mouse wheel scrolling? 
 
    [Keyboard Issues]
 
-   [191]Q-71: How can I get my AltGr and Shift modifiers to work between
+   [196]Q-71: How can I get my AltGr and Shift modifiers to work between
    keyboards for different languages? 
 
-   [192]Q-72: When I try to type a "<" (i.e. less than) instead I get ">"
+   [197]Q-72: When I try to type a "<" (i.e. less than) instead I get ">"
    (i.e. greater than)! Strangely, typing ">" works OK!! 
 
-   [193]Q-73: When I try to type a "<" (i.e. less than) instead I get
+   [198]Q-73: When I try to type a "<" (i.e. less than) instead I get
    "<," (i.e. an extra comma). 
 
-   [194]Q-74: I'm using an "international" keyboard (e.g. German "de", or
+   [199]Q-74: I'm using an "international" keyboard (e.g. German "de", or
    Danish "dk") and the -modtweak mode works well if the VNC viewer is
    run on a Unix/Linux machine with a similar keyboard.   But if I run
    the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or
    Windows with any keyboard, I can't type some keys like:   "@", "$",
    "<", ">", etc. How can I fix this? 
 
-   [195]Q-75: When typing I sometimes get double, triple, or more of my
+   [200]Q-75: When typing I sometimes get double, triple, or more of my
    keystrokes repeated. I'm sure I only typed them once, what can I do? 
 
-   [196]Q-76: The x11vnc -norepeat mode is in effect, but I still get
+   [201]Q-76: The x11vnc -norepeat mode is in effect, but I still get
    repeated keystrokes!! 
 
-   [197]Q-77: The machine where I run x11vnc has an AltGr key, but the
+   [202]Q-77: The machine where I run x11vnc has an AltGr key, but the
    local machine where I run the VNC viewer does not. Is there a way I
    can map a local unused key to send an AltGr? How about a Compose key
    as well? 
 
-   [198]Q-78: I have a Sun machine I run x11vnc on. Its Sun keyboard has
+   [203]Q-78: I have a Sun machine I run x11vnc on. Its Sun keyboard has
    just one Alt key labelled "Alt" and two Meta keys labelled with little
    diamonds. The machine where I run the VNC viewer only has Alt keys.
    How can I send a Meta keypress? (e.g. emacs needs this) 
 
-   [199]Q-79: Can I map a keystroke to a mouse button click on the remote
+   [204]Q-79: Can I map a keystroke to a mouse button click on the remote
    machine? 
 
-   [200]Q-80: How can I get Caps_Lock to work between my VNC viewer and
+   [205]Q-80: How can I get Caps_Lock to work between my VNC viewer and
    x11vnc? 
 
    [Screen Related Issues and Features]
 
-   [201]Q-81: The remote display is larger (in number of pixels) than the
+   [206]Q-81: The remote display is larger (in number of pixels) than the
    local display I am running the vncviewer on. I don't like the
    vncviewer scrollbars, what I can do? 
 
-   [202]Q-82: Does x11vnc support server-side framebuffer scaling? (E.g.
+   [207]Q-82: Does x11vnc support server-side framebuffer scaling? (E.g.
    to make the desktop smaller). 
 
-   [203]Q-83: Does x11vnc work with Xinerama? (i.e. multiple monitors
+   [208]Q-83: Does x11vnc work with Xinerama? (i.e. multiple monitors
    joined together to form one big, single screen). 
 
-   [204]Q-84: Can I use x11vnc on a multi-headed display that is not
+   [209]Q-84: Can I use x11vnc on a multi-headed display that is not
    Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? 
 
-   [205]Q-85: Can x11vnc show only a portion of the display? (E.g. for a
+   [210]Q-85: Can x11vnc show only a portion of the display? (E.g. for a
    special purpose rfb application). 
 
-   [206]Q-86: Does x11vnc support the XRANDR (X Resize, Rotate and
+   [211]Q-86: Does x11vnc support the XRANDR (X Resize, Rotate and
    Reflection) extension? Whenever I rotate or resize the screen x11vnc
    just seems to crash. 
 
-   [207]Q-87: Independent of any XRANDR, can I have x11vnc rotate and/or
+   [212]Q-87: Independent of any XRANDR, can I have x11vnc rotate and/or
    reflect the screen that the VNC viewers see? (e.g. for a handheld
    whose screen is rotated 90 degrees). 
 
-   [208]Q-88: Why is the view in my VNC viewer completely black? Or why
+   [213]Q-88: Why is the view in my VNC viewer completely black? Or why
    is everything flashing around randomly? 
 
-   [209]Q-89: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+   [214]Q-89: I use Linux Virtual Consoles (VC's) to implement 'Fast User
    Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7,
    Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those
    keystrokes to switch between their sessions).   How come the view in a
@@ -1182,45 +1202,45 @@ make
    otherwise all messed up unless the X session x11vnc is attached to is
    in the active VC? 
 
-   [210]Q-90: I am using x11vnc where my local machine has "popup/hidden
+   [215]Q-90: I am using x11vnc where my local machine has "popup/hidden
    taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc
    runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the
    mouse to the edge of the screen where the popups happen, the taskbars
    interfere and fight with each other in strange ways. What can I do? 
 
-   [211]Q-91: Can I use x11vnc to view my VMWare session remotely? 
+   [216]Q-91: Can I use x11vnc to view my VMWare session remotely? 
 
-   [212]Q-92: Can non-X devices (e.g. a raw framebuffer) be viewed (and
+   [217]Q-92: Can non-X devices (e.g. a raw framebuffer) be viewed (and
    even controlled) via VNC with x11vnc? 
 
-   [213]Q-93: Can I export via VNC a Webcam or TV tuner framebuffer using
+   [218]Q-93: Can I export via VNC a Webcam or TV tuner framebuffer using
    x11vnc? 
 
-   [214]Q-94: Can I connect via VNC to a Qt-embedded/Qtopia application
+   [219]Q-94: Can I connect via VNC to a Qt-embedded/Qtopia application
    running on my handheld or PC using the Linux console framebuffer (i.e.
    not X11)? 
 
-   [215]Q-95: Now that non-X11 devices can be exported via VNC using
+   [220]Q-95: Now that non-X11 devices can be exported via VNC using
    x11vnc, can I build it with no dependencies on X11 header files and
    libraries? 
 
-   [216]Q-96: Can I use x11vnc to record a Shock Wave Flash (or other
+   [221]Q-96: Can I use x11vnc to record a Shock Wave Flash (or other
    format) video of my desktop, e.g. to record a tutorial or demo? 
 
    [Misc: Clipboard, File Transfer, Sound, Beeps, Thanks, etc.]
 
-   [217]Q-97: Does the Clipboard/Selection get transferred between the
+   [222]Q-97: Does the Clipboard/Selection get transferred between the
    vncviewer and the X display? 
 
-   [218]Q-98: Can I transfer files back and forth with x11vnc? 
+   [223]Q-98: Can I transfer files back and forth with x11vnc? 
 
-   [219]Q-99: How can I hear the sound (audio) from the remote
+   [224]Q-99: How can I hear the sound (audio) from the remote
    applications on the desktop I am viewing via x11vnc? 
 
-   [220]Q-100: Why don't I hear the "Beeps" in my X session (e.g. when
+   [225]Q-100: Why don't I hear the "Beeps" in my X session (e.g. when
    typing tput bel in an xterm)? 
 
-   [221]Q-101: Thanks for your program and for your help! Can I make a
+   [226]Q-101: Thanks for your program and for your help! Can I make a
    donation? 
      _________________________________________________________________
 
@@ -1233,7 +1253,7 @@ make
 
    For the former error, you need to specify the X display to connect to
    (it also needs to be on the same machine the x11vnc process is to run
-   on). Set your DISPLAY environment variable or use the [222]-display
+   on). Set your DISPLAY environment variable or use the [227]-display
    option to specify it. Nearly always the correct value will be ":0" (in
    fact, x11vnc will now assume :0 if given no other information).
 
@@ -1250,9 +1270,9 @@ make
    working when you try to start x11vnc via, say, a remote shell.
 
    How to Solve:  See the xauth(1), Xsecurity(7), and xhost(1) man pages
-   or [223]this Howto for much info on X11 permissions. For example, you
+   or [228]this Howto for much info on X11 permissions. For example, you
    may need to set your XAUTHORITY environment variable or use the
-   [224]-auth option to point to the correct MIT-MAGIC-COOKIE file (e.g.
+   [229]-auth option to point to the correct MIT-MAGIC-COOKIE file (e.g.
    /home/joe/.Xauthority or /var/gdm/:0.Xauth or /var/lib/kdm/A:0-crWk72K
    or /tmp/.gdmzndVlR, etc.), or simply be sure you run x11vnc as the
    correct user (i.e. the user who is logged into the X session you wish
@@ -1274,7 +1294,7 @@ make
   x11vnc -display :0 -auth /var/gdm/:0.Xauth
 
    (this is for the display manager gdm and requires root permission to
-   read the gdm cookie file, see [225]this faq for other display manager
+   read the gdm cookie file, see [230]this faq for other display manager
    cookie file names). While running x11vnc as root, remember it comes
    with no warranty ;-).
 
@@ -1284,7 +1304,7 @@ make
    (from the same machine). The person could then type "xhost -localhost"
    after x11vnc has connected to go back to the default permissions.
    Also, for some situations the "-users lurk=" option may be of use
-   (please read the documentation on the [226]-users option).
+   (please read the documentation on the [231]-users option).
 
    To test out your X11 permissions from a remote shell, set DISPLAY and
    possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on
@@ -1396,7 +1416,7 @@ h
    earlier and perhaps non-Solaris):
 
    First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
-   above [227]Solaris build script to run the configure command. That
+   above [232]Solaris build script to run the configure command. That
    should succeed without failure. Then you have to hand edit the
    autogenerated rfb/rfbconfig.h file in the source tree, and just before
    the last #endif at the bottom of that file insert these workaround
@@ -1422,7 +1442,7 @@ typedef unsigned int in_addr_t;
    on other older OS (Solaris, Linux, ...) releases.
 
    Here are some notes for similar steps that need to be done to build on
-   [228]SunOS 4.x
+   [233]SunOS 4.x
 
    Please let us know if you had to use the above workaround (and whether
    it worked or not). If there is enough demand we will try to push clean
@@ -1432,28 +1452,28 @@ typedef unsigned int in_addr_t;
    Q-5: Where can I get a precompiled x11vnc binary for my Operating
    System?
 
-   Hopefully the [229]build steps above and [230]FAQ provide enough info
+   Hopefully the [234]build steps above and [235]FAQ provide enough info
    for a painless compile for most environments. Please report problems
    with the x11vnc configure, make, etc. on your system (if your system
    is known to compile other GNU packages successfully).
 
    There are precompiled x11vnc binaries built by other groups that are
    available at the following locations:
-    Debian:         (.deb)  [231]http://packages.debian.org/x11vnc
-
-   Slackware: (.tgz) [232]http://www.linuxpackages.net/ Redhat/Fedora:
-   (.rpm) [233]http://dag.wieers.com/packages/x11vnc/
-   [234]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm)
-   [235]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
-   [236]http://www.sunfreeware.com/ FreeBSD: (.tbz)
-   [237]http://www.freebsd.org/ [238]http://www.freshports.org/net/x11vnc
-   OpenBSD: (.tgz) [239]http://www.openbsd.org/ NetBSD: (src)
-   [240]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb)
-   [241]http://mike.saunby.net/770/x11vnc/ Sharp Zaurus
-   [242]http://www.pdaxrom.org/ and [243]http://www.focv.com/
+    Debian:         (.deb)  [236]http://packages.debian.org/x11vnc
+
+   Slackware: (.tgz) [237]http://www.linuxpackages.net/ Redhat/Fedora:
+   (.rpm) [238]http://dag.wieers.com/packages/x11vnc/
+   [239]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm)
+   [240]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
+   [241]http://www.sunfreeware.com/ FreeBSD: (.tbz)
+   [242]http://www.freebsd.org/ [243]http://www.freshports.org/net/x11vnc
+   OpenBSD: (.tgz) [244]http://www.openbsd.org/ NetBSD: (src)
+   [245]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb)
+   [246]http://mike.saunby.net/770/x11vnc/ Sharp Zaurus
+   [247]http://www.pdaxrom.org/ and [248]http://www.focv.com/
 
    If the above binaries don't work and building x11vnc on your OS fails
-   (and all else fails!) you can try one of [244]my collection of
+   (and all else fails!) you can try one of [249]my collection of
    binaries for various OS's and x11vnc releases.
 
    As a general note, the x11vnc program is simple enough you don't
@@ -1474,10 +1494,10 @@ typedef unsigned int in_addr_t;
 
    To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
    try here:
-     * [245]http://www.tightvnc.com/download.html
-     * [246]http://www.realvnc.com/download-free.html
-     * [247]http://sourceforge.net/projects/cotvnc/
-     * [248]http://www.ultravnc.com/
+     * [250]http://www.tightvnc.com/download.html
+     * [251]http://www.realvnc.com/download-free.html
+     * [252]http://sourceforge.net/projects/cotvnc/
+     * [253]http://www.ultravnc.com/
 
 
    Q-7: How can I see all of x11vnc's command line options and
@@ -1485,7 +1505,7 @@ typedef unsigned int in_addr_t;
 
    Run:  x11vnc -opts   to list just the option names or run:  x11vnc
    -help   for long descriptions about each option. The output is listed
-   [249]here as well. Yes, x11vnc does have a lot of options, doesn't
+   [254]here as well. Yes, x11vnc does have a lot of options, doesn't
    it...
 
 
@@ -1517,10 +1537,10 @@ display :0
    program is needed for operation. The gui is not particularly
    user-friendly, it just provides a point and click mode to set all the
    many x11vnc parameters and obtain help on them. It is also very useful
-   for testing. See the [250]-gui option for more info. Examples: "x11vnc
+   for testing. See the [255]-gui option for more info. Examples: "x11vnc
    ... -gui" and "x11vnc ... -gui other:0" in the latter case the gui is
    displayed on other:0, not the X display x11vnc is polling. There is
-   also a "[251]-gui tray" system tray mode.
+   also a "[256]-gui tray" system tray mode.
 
 
    Q-9: How can I get the GUI to run in the System Tray, or at least be a
@@ -1547,11 +1567,11 @@ display :0
    Q-10: Can I make x11vnc more quiet and also go into the background
    after starting up?
 
-   Use the [252]-q and [253]-bg options, respectively.  (also: -quiet is
+   Use the [257]-q and [258]-bg options, respectively.  (also: -quiet is
    an alias for -q)
 
    Note that under -bg the stderr messages will be lost unless you use
-   the "[254]-o logfile" option.
+   the "[259]-o logfile" option.
 
 
    Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
@@ -1572,7 +1592,7 @@ display :0
 
    There are some options. They are enabled by adding something like
    -Dxxxx=1 to the CPPFLAGS environment variable before running configure
-   (see the [255]build notes for general background).
+   (see the [260]build notes for general background).
 /*
  * Mar/2006
  * Build-time customization via CPPFLAGS.
@@ -1643,21 +1663,21 @@ display :0
    dual-screen mode to pass the keystrokes and mouse motions to the X11
    display?
 
-   Yes, for best response start up x11vnc with the "[256]-nofb" option
+   Yes, for best response start up x11vnc with the "[261]-nofb" option
    (disables framebuffer polling, and does other optimizations) on the
    secondary display (X11) machine. Then start up Win2VNC on the primary
    display (Windows) referring it to the secondary display.
 
-   This will also work X11 to X11 using [257]x2vnc, however you would
+   This will also work X11 to X11 using [262]x2vnc, however you would
    probably just want to avoid VNC and use x2x for that.
 
    For reference, here are some links to Win2VNC-like programs for
    multiple monitor setups:
-     * [258]Original Win2VNC
-     * [259]Enhanced Win2VNC and [260]sourceforge link
-     * [261]x2vnc
-     * [262]x2x also [263]here
-     * [264]zvnc (MorphOS)
+     * [263]Original Win2VNC
+     * [264]Enhanced Win2VNC and [265]sourceforge link
+     * [266]x2vnc
+     * [267]x2x also [268]here
+     * [269]zvnc (MorphOS)
 
    All of them will work with x11vnc (except x2x where it is not needed).
 
@@ -1677,7 +1697,7 @@ display :0
    on your display to be depth 24 TrueColor? Sun machines often have 8+24
    overlay/multi-depth visuals, and you can make the default visual depth
    24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004 x11vnc
-   has the [265]-visual option to allow you to force the framebuffer
+   has the [270]-visual option to allow you to force the framebuffer
    visual to whatever you want (this usually messes up the colors unless
    you are very clever). In this case, the option provides a convenient
    workaround for the Win2VNC bug:
@@ -1692,7 +1712,7 @@ display :0
    PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may
    start out OK, but after a while they are incorrect in certain windows.
 
-   Use the [266]-flashcmap option to have x11vnc watch for changes in the
+   Use the [271]-flashcmap option to have x11vnc watch for changes in the
    colormap, and propagate those changes back to connected clients. This
    can be slow (since the whole screen must be updated over the network
    whenever the colormap changes). This flashing colormap behavior often
@@ -1701,13 +1721,13 @@ display :0
    example of this. Consider reconfiguring the system to 16 bpp or depth
    24 TrueColor if at all possible.
 
-   Also note the option [267]-8to24 (Jan/2006) can often remove the need
+   Also note the option [272]-8to24 (Jan/2006) can often remove the need
    for flashing the colormap. Everything is dynamically transformed to
    depth 24 at 32 bpp using the colormaps. There may be painting errors
    however (see the following FAQ for tips on reducing and correcting
    them).
 
-   In some rare cases the [268]-notruecolor option has corrected colors
+   In some rare cases the [273]-notruecolor option has corrected colors
    on 8bpp displays. The red, green, and blue masks were non-zero in 8bpp
    PseudoColor on an obscure setup, and this option corrected the
    problems.
@@ -1718,13 +1738,13 @@ display :0
    different color depths: e.g. there are both depth 8 and 24 visuals
    available at the same time.
 
-   You may want to review the [269]previous question regarding 8 bpp
+   You may want to review the [274]previous question regarding 8 bpp
    PseudoColor.
 
-   On some hardware (Sun/SPARC and SGI), the [270]-overlay option
+   On some hardware (Sun/SPARC and SGI), the [275]-overlay option
    discussed a couple paragraphs down may solve this for you (you may
    want to skip to it directly). On other hardware the less robust
-   [271]-8to24 option may help (also discussed below).
+   [276]-8to24 option may help (also discussed below).
 
    Run xdpyinfo(1) to see what the default visual is and what the depths
    of the other visuals are. Does the default visual have a depth of 8
@@ -1760,7 +1780,7 @@ TrueColor defdepth 24
 
    The -overlay mode: Another option is if the system with overlay
    visuals is a Sun system running Solaris or SGI running IRIX you can
-   use the [272]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+   use the [277]-overlay x11vnc option (Aug/2004) to have x11vnc use the
    Solaris XReadScreen(3X11) function to poll the "true view" of the
    whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on
    IRIX. This is useful for Legacy applications (older versions of
@@ -1785,7 +1805,7 @@ TrueColor defdepth 24
    Xsun, e.g. in your /etc/dt/config/Xservers file).
 
 
-   The -8to24 mode: The [273]-8to24 x11vnc option (Jan/2006) is a kludge
+   The -8to24 mode: The [278]-8to24 x11vnc option (Jan/2006) is a kludge
    to try to dynamically rewrite the pixel values so that the 8bpp part
    of the screen is mapped onto depth 24 TrueColor. This is less robust
    than the -overlay mode because it is done by x11vnc outside of the X
@@ -1799,11 +1819,11 @@ TrueColor defdepth 24
    32bpp view is exported via VNC.
 
    Even on pure 8bpp displays it can be used as an alternative to
-   [274]-flashcmap to avoid color flashing completely.
+   [279]-flashcmap to avoid color flashing completely.
 
    This scheme is approximate and can often lead to painting errors. You
    can manually correct most painting errors by pressing 3 Alt_L's in a
-   row, or by using something like: [275]-fixscreen V=3.0 to
+   row, or by using something like: [280]-fixscreen V=3.0 to
    automatically refresh the screen every 3 seconds. Also -fixscreen
    8=3.0 has been added to just refresh the non-default visual parts of
    the screen.
@@ -1816,23 +1836,23 @@ TrueColor defdepth 24
    nogetimage can give a nice speedup if the default depth 24 X server
    supports hiding the 8bpp bits in bits 25-32 of the framebuffer data.
    On very slow machines -8to24 poll=0.2,cachewin=5.0 gives an useful
-   speedup. See the [276]-8to24 help description for information on
+   speedup. See the [281]-8to24 help description for information on
    tunable parameters, etc.
 
 
    Colors still not working correctly? Run xwininfo on the application
    with the incorrect colors to verify that the depth of its visual is
    different from the default visual depth (gotten from xdpyinfo). One
-   possible workaround in this case is to use the [277]-id option to
+   possible workaround in this case is to use the [282]-id option to
    point x11vnc at the application window itself. If the application is
    complicated (lots of toplevel windows and popup menus) this may not be
    acceptable, and may even crash x11vnc (but not the application).
 
    It is theoretically possible to solve this problem in general (see
    xwd(1) for example), but it does not seem trivial or sufficiently fast
-   for x11vnc to be able to do so in real time. The [278]-8to24 method
+   for x11vnc to be able to do so in real time. The [283]-8to24 method
    does this approximately and is somewhat usable. Fortunately the
-   [279]-overlay option works for Solaris machines with overlay visuals
+   [284]-overlay option works for Solaris machines with overlay visuals
    where most of this problem occurs.
 
 
@@ -1843,9 +1863,9 @@ TrueColor defdepth 24
    the desired application window. After clicking, it will print out much
    information, including the window id (e.g. 0x6000010). Also, the
    visual and depth of the window printed out is often useful in
-   debugging x11vnc [280]color problems.
+   debugging x11vnc [285]color problems.
 
-   Also, as of Dec/2004 you can use "[281]-id pick" to have x11vnc run
+   Also, as of Dec/2004 you can use "[286]-id pick" to have x11vnc run
    xwininfo(1) for you and after you click the window it extracts the
    windowid. Besides "pick" there is also "id:root" to allow you to go
    back to root window when doing remote-control.
@@ -1863,7 +1883,7 @@ TrueColor defdepth 24
    you should be able to see these transient windows.
 
    If things are not working and you still want to do the single window
-   polling, try the [282]-sid windowid option ("shifted" windowid).
+   polling, try the [287]-sid windowid option ("shifted" windowid).
 
 
    Q-19: My X display is depth 24 at 24bpp (instead of the normal depth
@@ -1898,7 +1918,7 @@ TrueColor defdepth 24
    handle 24bpp from the server, so you may want to use those. They
    evidently request 32 bpp and libvncserver obliges.
 
-   Update: as of Apr/2006 you can use the [283]-24to32 option to have
+   Update: as of Apr/2006 you can use the [288]-24to32 option to have
    x11vnc dynamically transform the 24bpp pixel data to 32bpp. This extra
    transformation could slow things down further however.
 
@@ -1917,15 +1937,15 @@ TrueColor defdepth 24
    since you will be polling the X display over the network as opposed to
    over the local hardware. To do this, run x11vnc on a UNIX machine as
    close as possible network-wise (e.g. same switch) to the Xterminal
-   machine. Use the [284]-display option to point the display to that of
+   machine. Use the [289]-display option to point the display to that of
    the Xterminal (you'll of course need basic X11 permission to do that)
-   and finally supply the [285]-noshm option (this enables the polling
+   and finally supply the [290]-noshm option (this enables the polling
    over the network).
 
    The response will likely be sluggish (maybe only one "frame" per
    second). This mode is not recommended except for "quick checks" of
    hard to get to X servers. Use something like "-wait 150" to cut down
-   on the polling rate. You may also need [286]-flipbyteorder if the
+   on the polling rate. You may also need [291]-flipbyteorder if the
    colors get messed up due to endian byte order differences.
 
    Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct
@@ -1949,7 +1969,7 @@ TrueColor defdepth 24
    copied to the Xterminal. If $HOME/.Xauthority is exported via NFS
    (this is insecure of course, but has been going on for decades), then
    x11vnc can simply pick it up via NFS (you may need to use the
-   [287]-auth option to point to the correct file). Other options include
+   [292]-auth option to point to the correct file). Other options include
    copying the auth file using scp, or something like:
   central-server>  xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
 
@@ -1961,7 +1981,7 @@ TrueColor defdepth 24
    details.
 
    If the display name in the cookie file needs to be changed between the
-   two hosts, see [288]this note on the "xauth add ..." command.
+   two hosts, see [293]this note on the "xauth add ..." command.
 
    A less secure option is to run something like "xhost +127.0.0.1" while
    sitting at the Xterminal box to allow cookie-free local access for
@@ -1975,7 +1995,7 @@ TrueColor defdepth 24
    occasional app more efficiently locally on the Xterminal box (e.g.
    realplayer).
 
-   Not recommended, but as a last resort, you could have x11vnc [289]poll
+   Not recommended, but as a last resort, you could have x11vnc [294]poll
    the Xterminal Display over the network. For this you would run a
    "x11vnc -noshm ..." process on the central-server (and hope the
    network admin doesn't get angry...)
@@ -2004,13 +2024,13 @@ TrueColor defdepth 24
 
    Q-22: I'm having trouble using x11vnc with my Sun Ray session.
 
-   The [290]Sun Ray technology is a bit like "VNC done in hardware" (the
+   The [295]Sun Ray technology is a bit like "VNC done in hardware" (the
    Sun Ray terminal device, DTU, playing the role of the vncviewer).
    Completely independent of that, the SunRay user's session is still an
    X server that speaks the X11 protocol and so x11vnc simply talks to
    the X server part to export the SunRay desktop to any place in the
    world (i.e. not only to a Sun Ray terminal device), creating a sort of
-   "Soft Ray". Please see [291]this discussion of Sun Ray issues for
+   "Soft Ray". Please see [296]this discussion of Sun Ray issues for
    solutions to problems.
 
    [Remote Control]
@@ -2018,18 +2038,18 @@ TrueColor defdepth 24
    Q-23: How do I stop x11vnc once it is running in the background?
 
    As of Dec/2004 there is a remote control feature. It can change a huge
-   amount of things on the fly: see the [292]-remote and [293]-query
+   amount of things on the fly: see the [297]-remote and [298]-query
    options. To shut down the running x11vnc server just type "x11vnc -R
    stop". To disconnect all clients do "x11vnc -R disconnect:all", etc.
 
-   If the [294]-forever option has not been supplied, x11vnc will
+   If the [299]-forever option has not been supplied, x11vnc will
    automatically exit after the first client disconnects. In general if
    you cannot use the remote control, then you will have to kill the
    x11vnc process This can be done via: "kill NNNNN" (where NNNNN is the
    x11vnc process id number found from ps(1)), or "pkill x11vnc", or
    "killall x11vnc" (Linux only).
 
-   If you have not put x11vnc in the background via the [295]-bg option
+   If you have not put x11vnc in the background via the [300]-bg option
    or shell & operator, then simply press Ctrl-C in the shell where
    x11vnc is running to stop it.
 
@@ -2039,15 +2059,15 @@ TrueColor defdepth 24
    down state in the Xserver. Tapping the stuck key (either via a new
    x11vnc or at the physical console) will release it from the stuck
    state. If the keyboard seems to be acting strangely it is often fixed
-   by tapping Ctrl, Shift, and Alt. Alternatively, the [296]-clear_mods
-   option and [297]-clear_keys option can be used to release pressed keys
+   by tapping Ctrl, Shift, and Alt. Alternatively, the [301]-clear_mods
+   option and [302]-clear_keys option can be used to release pressed keys
    at startup and exit.
 
 
    Q-24: Can I change settings in x11vnc without having to restart it?
    Can I remote control it?
 
-   Look at the [298]-remote (same as -R) and [299]-query (same as -Q)
+   Look at the [303]-remote (same as -R) and [304]-query (same as -Q)
    options added in Dec/2004. They allow nearly everything to be changed
    dynamically and settings to be queried. Examples: "x11vnc -R shared",
    "x11vnc -R forever", "x11vnc -R scale:3/4", "x11vnc -Q modtweak",
@@ -2058,7 +2078,7 @@ TrueColor defdepth 24
    correctly for communication to be possible.
 
    There is also a simple Tcl/Tk gui based on this remote control
-   mechanism. See the [300]-gui option for more info. You will need to
+   mechanism. See the [305]-gui option for more info. You will need to
    have Tcl/Tk (i.e. /usr/bin/wish) installed for it to work. It can also
    run in the system tray: "-gui tray" or as a standalone icon window:
    "-gui icon".
@@ -2073,12 +2093,12 @@ TrueColor defdepth 24
    vncpasswd(1) program from those packages.
 
    As of Jun/2004 x11vnc supports the -storepasswd "pass" "file"
-   [301]option, which is the same functionality of storepasswd. Be sure
+   [306]option, which is the same functionality of storepasswd. Be sure
    to quote the "pass" if it contains shell meta characters, spaces, etc.
    Example:
   x11vnc -storepasswd 'sword*fish' $HOME/myvncpasswd
 
-   You then use the password via the x11vnc option: "[302]-rfbauth
+   You then use the password via the x11vnc option: "[307]-rfbauth
    $HOME/myvncpasswd"
 
    As of Jan/2006 if you do not supply any arguments:
@@ -2090,11 +2110,11 @@ TrueColor defdepth 24
    ~/.mypass", the password you are prompted for will be stored in that
    file.
 
-   x11vnc also has the [303]-passwdfile and -passwd/-viewpasswd plain
+   x11vnc also has the [308]-passwdfile and -passwd/-viewpasswd plain
    text (i.e. not obscured like the -rfbauth VNC passwords) password
    options.
 
-   You can use the [304]-usepw option to automatically use any password
+   You can use the [309]-usepw option to automatically use any password
    file you have in ~/.vnc/passwd or ~/.vnc/passwdfile (the latter is
    used with the -passwdfile option).
 
@@ -2126,14 +2146,14 @@ TrueColor defdepth 24
    Q-27: Can I have two passwords for VNC viewers, one for full access
    and the other for view-only access to the display?
 
-   Yes, as of May/2004 there is the [305]-viewpasswd option to supply the
-   view-only password. Note the full-access password option [306]-passwd
+   Yes, as of May/2004 there is the [310]-viewpasswd option to supply the
+   view-only password. Note the full-access password option [311]-passwd
    must be supplied at the same time. E.g.: -passwd sword -viewpasswd
    fish.
 
    To avoid specifying the passwords on the command line (where they
    could be observed via the ps(1) command by any user) you can use the
-   [307]-passwdfile option to specify a file containing plain text
+   [312]-passwdfile option to specify a file containing plain text
    passwords. Presumably this file is readable only by you, and ideally
    it is located on the machine x11vnc is run on (to avoid being snooped
    on over the network). The first line of this file is the full-access
@@ -2141,7 +2161,7 @@ TrueColor defdepth 24
    it is taken as the view-only password. (use "__EMPTY__" to supply an
    empty one).
 
-   View-only passwords currently do not work for the [308]-rfbauth
+   View-only passwords currently do not work for the [313]-rfbauth
    password option (standard VNC password storing mechanism). FWIW, note
    that although the output (usually placed in $HOME/.vnc/passwd) by the
    vncpasswd or storepasswd programs (or from x11vnc -storepasswd) looks
@@ -2154,7 +2174,7 @@ TrueColor defdepth 24
    Q-28: Can I have as many full-access and view-only passwords as I
    like?
 
-   Yes, as of Jan/2006 in the libvncserver CVS the [309]-passwdfile
+   Yes, as of Jan/2006 in the libvncserver CVS the [314]-passwdfile
    option has been extended to handle as many passwords as you like. You
    put the view-only passwords after a line __BEGIN_VIEWONLY__.
 
@@ -2164,7 +2184,7 @@ TrueColor defdepth 24
 
    Q-29: Does x11vnc support Unix usernames and passwords? Can I further
    limit the set of Unix usernames who can connect to the VNC desktop?
-   Update: as of Feb/2006 x11vnc has the [310]-unixpw option that does
+   Update: as of Feb/2006 x11vnc has the [315]-unixpw option that does
    this outside of the VNC protocol and libvncserver. The standard su(1)
    program is used to validate the user's password. A familiar "login:"
    and "Password:" dialog is presented to the user on a black screen
@@ -2174,7 +2194,7 @@ TrueColor defdepth 24
    A list of allowed Unix usernames may also be supplied along with
    per-user settings.
 
-   There is also the [311]-unixpw_nis option for non-shadow-password
+   There is also the [316]-unixpw_nis option for non-shadow-password
    (typically NIS environments, hence the name) systems where the
    traditional getpwnam() and crypt() functions are used instead of
    su(1). The encrypted user passwords must be accessible to the user
@@ -2183,11 +2203,11 @@ TrueColor defdepth 24
    shadow(5).
 
    Two settings are enforced in the -unixpw and -unixpw_nis modes to
-   provide extra security: the 1) [312]-localhost and 2) [313]-stunnel or
-   [314]-ssl options. Without these one might send the Unix username and
+   provide extra security: the 1) [317]-localhost and 2) [318]-stunnel or
+   [319]-ssl options. Without these one might send the Unix username and
    password data in clear text over the network which is a very bad idea.
    They can be relaxed if you want to provide encryption other than
-   stunnel or [315]-ssl (the constraint is automatically relaxed if
+   stunnel or [320]-ssl (the constraint is automatically relaxed if
    SSH_CONNECTION is set and indicates you have ssh-ed in, however the
    -localhost requirement is still enforced).
 
@@ -2206,13 +2226,13 @@ TrueColor defdepth 24
    approximate at best.
 
    One approximate method involves starting x11vnc with the
-   [316]-localhost option. This basically requires the viewer user to log
+   [321]-localhost option. This basically requires the viewer user to log
    into the workstation where x11vnc is running via their Unix username
    and password, and then somehow set up a port redirection of his
    vncviewer connection to make it appear to emanate from the local
    machine. As discussed above, ssh is useful for this: "ssh -L
    5900:localhost:5900 user@hostname ..." See the ssh wrapper scripts
-   mentioned [317]elsewhere on this page. [318]stunnel does this as well.
+   mentioned [322]elsewhere on this page. [323]stunnel does this as well.
 
    Of course a malicious user could allow other users to get in through
    his channel, but that is a problem with every method. Another thing to
@@ -2223,7 +2243,7 @@ TrueColor defdepth 24
    traditional way would be to further require a VNC password to supplied
    (-rfbauth, -passwd, etc) and only tell the people allowed in what the
    VNC password is. A scheme that avoids a second password involves using
-   the [319]-accept option that runs a program to examine the connection
+   the [324]-accept option that runs a program to examine the connection
    information to determine which user is connecting from the local
    machine. That may be difficult to do, but, for example, the program
    could use the ident service on the local machine (normally ident
@@ -2262,15 +2282,15 @@ exit 1  # reject it
 
    These defaults are simple safety measures to avoid someone unknowingly
    leaving his X11 desktop exposed (to the internet, say) for long
-   periods of time. Use the [320]-forever option (aka -many) to have
+   periods of time. Use the [325]-forever option (aka -many) to have
    x11vnc wait for more connections after the first client disconnects.
-   Use the [321]-shared option to have x11vnc allow multiple clients to
+   Use the [326]-shared option to have x11vnc allow multiple clients to
    connect simultaneously.
 
-   Recommended additional safety measures include using ssh ([322]see
-   above), stunnel, [323]-ssl, or a VPN to authenticate and encrypt the
+   Recommended additional safety measures include using ssh ([327]see
+   above), stunnel, [328]-ssl, or a VPN to authenticate and encrypt the
    viewer connections or to at least use the -rfbauth passwd-file
-   [324]option to use VNC password protection (or [325]-passwdfile) It is
+   [329]option to use VNC password protection (or [330]-passwdfile) It is
    up to YOU to apply these security measures, they will not be done for
    you automatically.
 
@@ -2278,7 +2298,7 @@ exit 1  # reject it
    Q-31: Can I limit which machines incoming VNC clients can connect
    from?
 
-   Yes, look at the [326]-allow and [327]-localhost options to limit
+   Yes, look at the [331]-allow and [332]-localhost options to limit
    connections by hostname or IP address. E.g.
   x11vnc -allow 192.168.0.1,192.168.0.2
 
@@ -2290,7 +2310,7 @@ exit 1  # reject it
    Note that -localhost achieves the same thing as "-allow 127.0.0.1"
 
    For more control, build libvncserver with libwrap support
-   [328](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+   [333](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
    for complete details.
 
 
@@ -2310,7 +2330,7 @@ exit 1  # reject it
    is "vnc", e.g.:
   vnc: 192.168.100.3 .example.com
 
-   Note that if you run x11vnc out of [329]inetd you do not need to build
+   Note that if you run x11vnc out of [334]inetd you do not need to build
    x11vnc with libwrap support because the /usr/sbin/tcpd reference in
    /etc/inetd.conf handles the tcp_wrappers stuff.
 
@@ -2319,15 +2339,15 @@ exit 1  # reject it
    internal LAN) rather than having it listen on all network interfaces
    and relying on -allow to filter unwanted connections out?
 
-   As of Mar/2005 there is the "[330]-listen ipaddr" option that enables
+   As of Mar/2005 there is the "[335]-listen ipaddr" option that enables
    this. For ipaddr either supply the desired network interface's IP
    address (or use a hostname that resolves to it) or use the string
    "localhost". For additional filtering simultaneously use the
-   "[331]-allow host1,..." option to allow only specific hosts in.
+   "[336]-allow host1,..." option to allow only specific hosts in.
 
    This option is useful if you want to insure that no one can even begin
    a dialog with x11vnc from untrusted network interfaces (e.g. ppp0).
-   The option [332]-localhost now implies "-listen localhost" since that
+   The option [337]-localhost now implies "-listen localhost" since that
    is what most people expect it to do.
 
 
@@ -2335,7 +2355,7 @@ exit 1  # reject it
    interface, how I can occasionally allow in a non-localhost via the -R
    allowonce remote control command?
 
-   To do this specify "[333]-allow localhost". Unlike [334]-localhost
+   To do this specify "[338]-allow localhost". Unlike [339]-localhost
    this will leave x11vnc listening on all interfaces (but of course only
    allowing in local connections, e.g. ssh redirs). Then you can later
    run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot
@@ -2346,7 +2366,7 @@ exit 1  # reject it
    some users just be able to move the mouse, but not click or type
    anything?
 
-   As of Feb/2005, the [335]-input option allows you to do this. "K",
+   As of Feb/2005, the [340]-input option allows you to do this. "K",
    "M", "B", and "C" stand for Keystroke, Mouse-motion, Button-clicks,
    and Clipboard, respectively. The setting: "-input M" makes attached
    viewers only able to move the mouse. "-input KMBC,M" lets normal
@@ -2361,7 +2381,7 @@ exit 1  # reject it
    some clients view-only? How about running an arbitrary program to make
    the decisions?
 
-   Yes, look at the "[336]-accept command" option, it allows you to
+   Yes, look at the "[341]-accept command" option, it allows you to
    specify an external command that is run for each new client. (use
    quotes around the command if it contains spaces, etc.). If the
    external command returns 0 the client is accepted, otherwise the
@@ -2380,7 +2400,7 @@ exit 1  # reject it
    own simple popup window. To accept the client press "y" or click mouse
    on the "Yes" button. To reject the client press "n" or click mouse on
    the "No" button. To accept the client View-only, press "v" or click
-   mouse on the "View" button. If the [337]-viewonly option has been
+   mouse on the "View" button. If the [342]-viewonly option has been
    supplied, the "View" action will not be present: the whole display is
    view only in that case.
 
@@ -2396,7 +2416,7 @@ exit 1  # reject it
    program to prompt the user whether the client should be accepted or
    not. This requires that you have xmessage installed and available via
    PATH. In case it is not already on your system, the xmessage program
-   is available at [338]ftp://ftp.x.org/
+   is available at [343]ftp://ftp.x.org/
 
    To include view-only decisions for the external commands, prefix the
    command something like this: "yes:0,no:*,view:3 mycommand ..." This
@@ -2435,7 +2455,7 @@ elif [ $rc = 4 ]; then
 fi
 exit 1
 
-   Stefan Radman has written a nice dtksh script [339]dtVncPopup for use
+   Stefan Radman has written a nice dtksh script [344]dtVncPopup for use
    in CDE environments to do the same sort of thing. Information on how
    to use it is found at the top of the file. He encourages you to
    provide feedback to him to help improve the script.
@@ -2444,13 +2464,13 @@ exit 1
    popup is being run, so attached clients will not receive screen
    updates, etc during this period.
 
-   To run a command when a client disconnects, use the "[340]-gone
+   To run a command when a client disconnects, use the "[345]-gone
    command" option. This is for the user's convenience only: the return
    code of the command is not interpreted by x11vnc. The same environment
    variables are set as in "-accept command" (except that RFB_MODE will
    be "gone").
 
-   As of Jan/2006 the "[341]-afteraccept command" option will run the
+   As of Jan/2006 the "[346]-afteraccept command" option will run the
    command only after the VNC client has been accepted and authenticated.
    Like -gone the return code is not interprted. RFB_MODE will be
    "afteraccept").
@@ -2460,7 +2480,7 @@ exit 1
    display manager like gdm(1). Can I have x11vnc later switch to a
    different user?
 
-   As of Feb/2005 x11vnc has the [342]-users option that allows things
+   As of Feb/2005 x11vnc has the [347]-users option that allows things
    like this. Please read the documentation on it (also in the x11vnc
    -help output) carefully for features and caveats. It's use can often
    decrease security unless care is taken.
@@ -2485,7 +2505,7 @@ exit 1
 
    In any event, as of Jun/2004 there is an experimental utility to make
    it more difficult for nosey people to see your x11vnc activities. The
-   source for it is [343]blockdpy.c The idea behind it is simple (but
+   source for it is [348]blockdpy.c The idea behind it is simple (but
    obviously not bulletproof): when a VNC client attaches to x11vnc put
    the display monitor in the DPMS "off" state, if the DPMS state ever
    changes immediately start up the screen-lock program. The x11vnc user
@@ -2501,8 +2521,8 @@ exit 1
    bulletproof. A really robust solution would likely require X server
    and perhaps even video hardware support.
 
-   The blockdpy utility is launched by the [344]-accept option and told
-   to exit via the [345]-gone option (the vnc client user should
+   The blockdpy utility is launched by the [349]-accept option and told
+   to exit via the [350]-gone option (the vnc client user should
    obviously re-lock the screen before disconnecting!). Instructions can
    be found in the source code for the utility at the above link.
 
@@ -2510,7 +2530,7 @@ exit 1
    Q-39: Can I have x11vnc automatically lock the screen when I
    disconnect the VNC viewer?
 
-   Yes, a user mentions he uses the [346]-gone option under CDE to run a
+   Yes, a user mentions he uses the [351]-gone option under CDE to run a
    screen lock program:
   x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
 
@@ -2519,7 +2539,7 @@ exit 1
   x11vnc -display :0 -forever -gone 'kdesktop_lock'
   x11vnc -display :0 -forever -gone 'xlock &'
 
-   Here is a scheme using the [347]-afteraccept option (in version 0.7.3)
+   Here is a scheme using the [352]-afteraccept option (in version 0.7.3)
    to unlock the screen after the first valid VNC login and to lock the
    screen after the last valid VNC login disconnects:
   x11vnc -display :0 -forever -shared -afteraccept ./myxlocker -gone ./myxlocke
@@ -2550,18 +2570,21 @@ fi
    Q-40: How can I tunnel my connection to x11vnc via an encrypted SSH
    channel between two Unix machines?
 
-   See the description earlier on this page on [348]how to tunnel VNC via
+   See the description earlier on this page on [353]how to tunnel VNC via
    SSH from Unix to Unix. A number of ways are described along with some
    issues you may encounter.
 
    Other secure encrypted methods exists, e.g. stunnel, IPSEC, various
    VPNs, etc.
 
+   See also the [354]Enhanced TightVNC Viewer page where much of this is
+   now automated.
+
 
    Q-41: How can I tunnel my connection to x11vnc via an encrypted SSH
    channel from Windows using an SSH client like Putty?
 
-   [349]Above we described how to tunnel VNC via SSH from Unix to Unix,
+   [355]Above we described how to tunnel VNC via SSH from Unix to Unix,
    you may want to review it. To do this from Windows using Putty it
    would go something like this:
      * In the Putty dialog window under 'Session' enter the hostname or
@@ -2580,12 +2603,13 @@ fi
    You can keep all of the settings in a Putty 'Saved Session'. Also,
    once everything is working, you can consider putting x11vnc -display
    :0 (plus other cmdline options) in the 'Remote command' Putty setting
-   under 'Connections/SSH'. It is likely possible to script the whole
-   process in a BAT file including launching the VNC viewer by using the
-   plink Putty utility. Send us the script if you get that working.
+   under 'Connections/SSH'.
+
+   See also the [356]Enhanced TightVNC Viewer page where much of this is
+   now automated via the Putty plink utility.
 
-   For extra protection feel free to run x11vnc with the [350]-localhost
-   and [351]-rfbauth/[352]-passwdfile options.
+   For extra protection feel free to run x11vnc with the [357]-localhost
+   and [358]-rfbauth/[359]-passwdfile options.
 
    If the machine you SSH into via Putty is not the same machine with the
    X display you wish to view (e.g. your company provides incoming SSH
@@ -2593,11 +2617,11 @@ fi
    dialog setting to: 'Destination: otherhost:5900', Once logged in,
    you'll need to do a second login (ssh or rsh) to the workstation
    machine 'otherhost' and then start up x11vnc on it. This can also be
-   automated by [353]chaining ssh's.
+   automated by [360]chaining ssh's.
 
-   As discussed [354]above another option is to first start the VNC
+   As discussed [361]above another option is to first start the VNC
    viewer in "listen" mode, and then launch x11vnc with the
-   "[355]-connect localhost" option to establish the reverse connection.
+   "[362]-connect localhost" option to establish the reverse connection.
    In this case a Remote port redirection (not Local) is needed for port
    5500 instead of 5900 (i.e. 'Source port:  5500' and
    'Destination:  localhost:5500' for a Remote connection).
@@ -2607,7 +2631,7 @@ fi
    channel using an external tool like stunnel?
 
    It is possible to use a "lighter weight" encryption setup than SSH or
-   IPSEC. SSL tunnels such as [356]stunnel provide an encrypted channel
+   IPSEC. SSL tunnels such as [363]stunnel provide an encrypted channel
    without the need for Unix users, passwords, and key passphrases
    required for ssh (and at the other extreme SSL can also provide a
    complete signed certificate chain of trust). OTOH, since SSH is
@@ -2615,12 +2639,12 @@ fi
    ssh is frequently the path of least resistance (it also nicely manages
    public keys for you).
 
-   Update: As of Feb/2006 x11vnc has the options [357]-ssl,
-   [358]-stunnel, and [359]-sslverify to provide integrated SSL schemes.
-   They are discussed [360]in the Next FAQ (you may want to skip to it
+   Update: As of Feb/2006 x11vnc has the options [364]-ssl,
+   [365]-stunnel, and [366]-sslverify to provide integrated SSL schemes.
+   They are discussed [367]in the Next FAQ (you may want to skip to it
    now).
 
-   Here are some basic examples using [361]stunnel but the general idea
+   Here are some basic examples using [368]stunnel but the general idea
    for any SSL tunnel utility is the same:
      * Start up x11vnc and constrain it to listen on localhost.
      * Then start up the SSL tunnel running on the same machine to
@@ -2644,7 +2668,7 @@ fi
 
    The above two commands are run on host "far-away.east". The
    stunnel.pem is the self-signed PEM file certificate created when
-   stunnel is built. One can also create certificates [362]signed by
+   stunnel is built. One can also create certificates [369]signed by
    Certificate Authorities or self-signed if desired using the x11vnc
    utilities described there.
 
@@ -2658,7 +2682,7 @@ fi
    Then point the viewer to the local tunnel on port 5902:
   vncviewer -encodings "copyrect tight zrle hextile" localhost:2
 
-   That's it.  (note that the [363]ssl_vncviewer script can automate
+   That's it.  (note that the [370]ssl_vncviewer script can automate
    this.)
 
    Be sure to use a VNC password because unlike ssh by default the
@@ -2666,13 +2690,13 @@ fi
    some extra configuration one could also set up certificates to provide
    authentication of either or both sides as well (and hence avoid
    man-in-the-middle attacks). See the stunnel and openssl documentation
-   and also [364]the key management section for details.
+   and also [371]the key management section for details.
 
    stunnel has also been ported to Windows, and there are likely others
    to choose from for that OS. Much info for using it on Windows can be
-   found at the stunnel site and in this [365]article The article also
+   found at the stunnel site and in this [372]article The article also
    shows the detailed steps to set up all the authentication
-   certificates. (for both server and clients, see also the [366]x11vnc
+   certificates. (for both server and clients, see also the [373]x11vnc
    utilities that do this). The default Windows client setup (no certs)
    is simpler and only 4 files are needed in a folder: stunnel.exe,
    stunnel.conf, libssl32.dll, libeay32.dll. We used an stunnel.conf
@@ -2693,7 +2717,7 @@ connect = far-away.east:5901
    As an aside, if you don't like the little "gap" of unencrypted TCP
    traffic (and a localhost listening socket) on the local machine
    between stunnel and x11vnc it can actually be closed by having stunnel
-   start up x11vnc in [367]-inetd mode:
+   start up x11vnc in [374]-inetd mode:
   stunnel -p /path/to/stunnel.pem -P none -d 5900 -l ./x11vnc_sh
 
    Where the script x11vnc_sh starts up x11vnc:
@@ -2736,28 +2760,28 @@ connect = 5900
    they probably wouldn't work since the SSL negotiation is likely
    embedded in the VNC protocol unlike our case where it is external.
 
-   Note: as of Mar/2006 libvncserver/x11vnc provides a [368]SSL-enabled
-   Java applet that can be served up via the [369]-httpdir or [370]-http
-   options when [371]-ssl is enabled. It will also be served via HTTPS
+   Note: as of Mar/2006 libvncserver/x11vnc provides a [375]SSL-enabled
+   Java applet that can be served up via the [376]-httpdir or [377]-http
+   options when [378]-ssl is enabled. It will also be served via HTTPS
    via either the VNC port (e.g. https://host:5900/) or a 2nd port via
-   the [372]-https option.
+   the [379]-https option.
 
    In general current SSL VNC solutions are not particularly "seemless".
    But it can be done, and with a wrapper script on the viewer side and
-   the [373]-stunnel or [374]-ssl option on the server side it works well
-   and is convenient. Here is a simple script [375]ssl_vncviewer that
+   the [380]-stunnel or [381]-ssl option on the server side it works well
+   and is convenient. Here is a simple script [382]ssl_vncviewer that
    automates running stunnel on the VNC viewer side on Unix a little more
    carefully than the commands printed above. (One could probably do a
    similar thing with a .BAT file on Windows in the stunnel folder.)
 
-   Update: we now provide an [376]Enhanced TightVNC Viewer package that
-   starts up STUNNEL automatically along with some other features. All
-   binaries are provided in the package.
+   Update Jul/2006: we now provide an [383]Enhanced TightVNC Viewer
+   package that starts up STUNNEL automatically along with some other
+   features. All binaries are provided in the package.
 
 
    Q-43: Does x11vnc have built-in SSL tunneling?
 
-   You can read about non-built-in methods [377]in the Previous FAQ
+   You can read about non-built-in methods [384]in the Previous FAQ
 
    SSL tunnels provide an encrypted channel without the need for Unix
    users, passwords, and key passphrases required for ssh (and at the
@@ -2768,14 +2792,14 @@ connect = 5900
 
    Built-in SSL x11vnc options:
 
-   As of Feb/2006 the x11vnc [378]-ssl and [379]-stunnel options automate
-   the SSL tunnel creation on the x11vnc server side. An [380]SSL-enabled
+   As of Feb/2006 the x11vnc [385]-ssl and [386]-stunnel options automate
+   the SSL tunnel creation on the x11vnc server side. An [387]SSL-enabled
    Java Viewer applet is also provided that can be served via HTTP or
    HTTPS to automate SSL on the client side.
 
-   The [381]-ssl mode uses the [382]www.openssl.org library if available
-   at build time. The [383]-stunnel mode requires the
-   [384]www.stunnel.org command stunnel(8) to be installed on the system.
+   The [388]-ssl mode uses the [389]www.openssl.org library if available
+   at build time. The [390]-stunnel mode requires the
+   [391]www.stunnel.org command stunnel(8) to be installed on the system.
 
    Both modes require an SSL certificate and key (i.e. .pem file). These
    are usually created via the openssl(1) (in fact in for options "-ssl"
@@ -2827,12 +2851,12 @@ connect = 5900
    is to encrypt the key with a passphrase (note however this requires
    supplying the passphrase each time x11vnc is started up).
 
-   See the discussion on [385]x11vnc Key Management for some utilities
+   See the discussion on [392]x11vnc Key Management for some utilities
    provided for creating and managing certificates and keys and even for
    creating your own Certificate Authority (CA) for signing VNC server
    and client certificates. This may be done by importing the certificate
    into Web Browser or Java plugin keystores, or pointing stunnel to it.
-   The wrapper script [386]ssl_vncviewer provides an example on unix
+   The wrapper script [393]ssl_vncviewer provides an example on unix
    (-verify option).
 
    Here are some notes on the simpler default (non-CA) operation. To have
@@ -2848,7 +2872,7 @@ connect = 5900
    to machines where the VNC Viewer will be run to enable authenticating
    the x11vnc SSL VNC server to the clients. When authentication takes
    place this way (or via the more sophisticated CA signing described
-   [387]here), then Man-In-The-Middle-Attacks are prevented. Otherwise,
+   [394]here), then Man-In-The-Middle-Attacks are prevented. Otherwise,
    the SSL encryption only provides protection against passive network
    traffic "sniffing". Nowadays, most people seem mostly concerned about
    only the latter (and the default x11vnc SSL modes protect against it.)
@@ -2873,7 +2897,7 @@ connect = 5900
    including using https to download it into the browser and connect to
    x11vnc.
 
-   See the [388]next FAQ for SSL enabled VNC Viewers.
+   See the [395]next FAQ for SSL enabled VNC Viewers.
 
 
    Q-44: How do I use VNC Viewers with built-in SSL tunneling?
@@ -2884,9 +2908,9 @@ connect = 5900
    The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package
    supports only SSL based connections by default (set the applet
    parameter disableSSL=yes in index.vnc to override). As mentioned above
-   the [389]-httpdir can be used to specify the path to .../classes/ssl.
+   the [396]-httpdir can be used to specify the path to .../classes/ssl.
    A typical location might be /usr/local/share/x11vnc/classes/ssl. Or
-   [390]-http can be used to try to have it find the directory
+   [397]-http can be used to try to have it find the directory
    automatically.
 
    The Java viewer uses SSL to communicate securely with x11vnc. Note
@@ -2911,7 +2935,7 @@ connect = 5900
    example) can occasionally be slow or unreliable (it has to read some
    input and try to guess if the connection is VNC or HTTP). If it is
    unreliable and you still want to serve the Java applet via https, use
-   the [391]-https option to get an additional port dedicated to https
+   the [398]-https option to get an additional port dedicated to https
    (its URL will also be printed in the output).
 
    Another possibility is to add the GET applet parameter:
@@ -2924,7 +2948,7 @@ connect = 5900
 
    You may also use "?GET=somestring" to have /somestring prepended to
    /request.https.vnc.connection". Perhaps you are using a web server
-   [392]proxy scheme to enter a firewall or otherwise have rules applied
+   [399]proxy scheme to enter a firewall or otherwise have rules applied
    to the URL. If you need to have any slashes "/" in "somestring" use
    "_2F_" (a deficiency in libvncserver prevents using the more natural
    "%2F".)
@@ -2948,7 +2972,7 @@ connect = 5900
    connection is VNC instead of the HTTPS it actually is (but since you
    have paused too long at the dialog the GET request comes too late).
    Often hitting Reload and going through the dialogs more quickly will
-   let you connect. Use the [393]-https option if you want a dedicated
+   let you connect. Use the [400]-https option if you want a dedicated
    port for HTTPS connections instead of sharing the VNC port.
 
 
@@ -2957,10 +2981,10 @@ connect = 5900
    If you want to use a native VNC Viewer with the SSL enabled x11vnc you
    will need to run an external SSL tunnel on the Viewer side. There do
    not seem to be any native SSL VNC Viewers outside of the x11vnc
-   package. The basic ideas of doing this were discussed [394]for
+   package. The basic ideas of doing this were discussed [401]for
    external tunnel utilities here.
 
-   The [395]ssl_vncviewer script provided with x11vnc can set up the
+   The [402]ssl_vncviewer script provided with x11vnc can set up the
    stunnel tunnel automatically on unix as long as the stunnel command is
    installed on the Viewer machine and available in PATH (and vncviewer
    too of course). Note that on Debian based system you will need to
@@ -2992,13 +3016,17 @@ connect = 5900
 
    The fifth one shows that Web proxies can be used if that is the only
    way to get out of the firewall. If the "double proxy" situation arises
-   separate the two by commas. See [396]this page for more information on
+   separate the two by commas. See [403]this page for more information on
    how Web proxies come into play.
 
-   If one uses a Certificate Authority (CA) scheme described [397]here,
+   If one uses a Certificate Authority (CA) scheme described [404]here,
    the wrapper script would use the CA cert instead of the server cert:
   3')  ssl_vncviewer -verify ./cacert.crt far-away.east:0
 
+   Update Jul/2006: we now provide an [405]Enhanced TightVNC Viewer
+   package that starts up STUNNEL automatically along with some other
+   features. All binaries are provided in the package.
+
 
    Q-45: How do I use VNC Viewers with built-in SSL tunneling when going
    through a Web Proxy?
@@ -3031,7 +3059,7 @@ connect = 5900
    (instead of the unsigned one in https://yourmachine.com:5900/ that
    gives the default index.vnc)
 
-   Note that the [398]ssl_vncviewer stunnel wrapper script can use Web
+   Note that the [406]ssl_vncviewer stunnel wrapper script can use Web
    proxies as well.
 
    Proxies that limit CONNECT to ports 443 and 563:
@@ -3060,7 +3088,7 @@ connect = 5900
   https://yourmachine.com/proxy.vnc?PORT=443
 
    this is cleaner because it avoids editing the file, but requires more
-   parameters in the URL. To use the GET [399]trick discussed above, do:
+   parameters in the URL. To use the GET [407]trick discussed above, do:
   https://yourmachine.com/proxy.vnc?PORT=443&GET=1
 
 
@@ -3068,7 +3096,7 @@ connect = 5900
    SSL from the Internet with a Web browser to x11vnc running on their
    workstations behind a firewall?
    Yes. You will need to configure apache to forward these connections.
-   It is discussed [400]here. This provides a clean alternative to the
+   It is discussed [408]here. This provides a clean alternative to the
    traditional method where the user uses SSH to log in through the
    gateway to create the encrypted port redirection to x11vnc running on
    her desktop.
@@ -3076,7 +3104,7 @@ connect = 5900
 
    Q-47: Can I create and use my own SSL Certificate Authority (CA) with
    x11vnc?
-   Yes, see [401]this page for how to do this and the utility commands
+   Yes, see [409]this page for how to do this and the utility commands
    x11vnc provides to create and manage many types of certificates and
    private keys.
 
@@ -3095,13 +3123,13 @@ connect = 5900
    need to have sufficient permissions to connect to the X display.
 
    Here are some ideas:
-     * Use the description under "Continuously" in the [402]FAQ on x11vnc
+     * Use the description under "Continuously" in the [410]FAQ on x11vnc
        and Display Managers
-     * Use the description in the [403]FAQ on x11vnc and inetd(8)
-     * Use the description in the [404]FAQ on Unix user logins and
+     * Use the description in the [411]FAQ on x11vnc and inetd(8)
+     * Use the description in the [412]FAQ on Unix user logins and
        inetd(8)
      * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
-     * Although less reliable, see the [405]x11vnc_loop rc.local hack
+     * Although less reliable, see the [413]x11vnc_loop rc.local hack
        below.
 
    The display manager scheme will not be specific to which user has the
@@ -3132,7 +3160,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
    while running x11vnc as root, e.g. for the gnome display manager, gdm:
   x11vnc -auth /var/gdm/:0.Xauth -display :0
 
-   (the [406]-auth option sets the XAUTHORITY variable for you).
+   (the [414]-auth option sets the XAUTHORITY variable for you).
 
    There will be a similar thing for xdm using however a different auth
    directory path (perhaps something like
@@ -3157,7 +3185,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
    auth file should be in /var/dt), you'll also need to add something
    like Dtlogin*grabServer:False to the Xconfig file
    (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see
-   [407]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+   [415]the example at the end of this FAQ). Then restart dtlogin, e.g.:
    /etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot.
 
    Continuously.   Have x11vnc reattach each time the X server is
@@ -3220,7 +3248,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
 
    Then restart: /usr/sbin/gdm-restart (or reboot). The
    KillInitClients=false setting is important: without it x11vnc will be
-   killed immediately after the user logs in. Here are [408]full details
+   killed immediately after the user logs in. Here are [416]full details
    on how to configure gdm
      _________________________________________________________________
 
@@ -3262,14 +3290,14 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
 
    If you do not want to deal with any display manager startup scripts,
    here is a kludgey script that can be run manually or out of a boot
-   file like rc.local: [409]x11vnc_loop It will need some local
+   file like rc.local: [417]x11vnc_loop It will need some local
    customization before running. Because the XAUTHORITY auth file must be
    guessed by this script, use of the display manager script method
-   described above is greatly preferred. There is also the [410]-loop
+   described above is greatly preferred. There is also the [418]-loop
    option that does something similar.
 
    If the machine is a traditional Xterminal you may want to read
-   [411]this FAQ.
+   [419]this FAQ.
 
 
    Q-50: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
@@ -3279,7 +3307,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
 
   5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
 
-   where the shell script /usr/local/bin/x11vnc_sh uses the [412]-inetd
+   where the shell script /usr/local/bin/x11vnc_sh uses the [420]-inetd
    option and looks something like (you'll need to customize to your
    settings).
 #!/bin/sh
@@ -3292,7 +3320,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
    and that confuses it greatly, causing it to abort). If you do not use
    a wrapper script as above but rather call x11vnc directly in
    /etc/inetd.conf and do not redirect stderr to a file, then you must
-   specify the -q (aka [413]-quiet) option: "/usr/local/bin/x11vnc -q
+   specify the -q (aka [421]-quiet) option: "/usr/local/bin/x11vnc -q
    -inetd ...". When you supply both -q and -inet and no "-o logfile"
    then stderr will automatically be closed (to prevent, e.g. library
    stderr messages leaking out to the viewer). The recommended practice
@@ -3300,12 +3328,12 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
    script with "2>logfile" redirection because the errors and warnings
    printed out are very useful in troubleshooting problems.
 
-   Note also the need to set XAUTHORITY via [414]-auth to point to the
+   Note also the need to set XAUTHORITY via [422]-auth to point to the
    MIT-COOKIE auth file to get permission to connect to the X display
    (setting and exporting the XAUTHORITY variable accomplishes the same
    thing). See the x11vnc_loop file in the previous question for more
    ideas on what that auth file may be, etc. The scheme described in the
-   [415]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY
+   [423]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY
    issue nicely.
 
    Note:  On Solaris you cannot have the bare number 5900 in
@@ -3370,13 +3398,13 @@ service x11vncservice
    Q-51: Can I have x11vnc allow a user to log in with her UNIX password
    and then have it find her X display on that machine and connect to it?
 
-   The easiest way to do this is via [416]inetd(8) using the [417]-unixpw
-   and [418]-display WAIT options. The reason inetd(8) makes this easier
+   The easiest way to do this is via [424]inetd(8) using the [425]-unixpw
+   and [426]-display WAIT options. The reason inetd(8) makes this easier
    is that it starts a new x11vnc process for each new user connection.
    Otherwise a wrapper would have to listen for connections and spawn new
-   x11vnc's (see [419]this example).
+   x11vnc's (see [427]this example).
 
-   The [420]-display WAIT option makes x11vnc wait until a VNC viewer is
+   The [428]-display WAIT option makes x11vnc wait until a VNC viewer is
    connected before attaching to the X display. Additionally it can be
    used to run an external command that returns the DISPLAY and
    XAUTHORITY data. So one could supply "-display
@@ -3419,7 +3447,7 @@ exit 0
    as the first line and any remaining lines are either XAUTHORITY=file
    or raw xauth data (the above example does the latter).
 
-   The [421]-unixpw option allows [422]UNIX password logins. Here are a
+   The [429]-unixpw option allows [430]UNIX password logins. Here are a
    couple /etc/inetd.conf examples for this:
 5900  stream  tcp  nowait  nobody  /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd
 -unixpw \
@@ -3439,9 +3467,9 @@ xpw=
    directory will need to be set up to allow "nobody" to use them.
 
    In the second one x11vnc is run as root and switches to the user that
-   logs in due to the "[423]-users unixpw=" option.
+   logs in due to the "[431]-users unixpw=" option.
 
-   Note that [424]SSL is required for this mode because otherwise the
+   Note that [432]SSL is required for this mode because otherwise the
    unix password would be passed in clear text over the network. In
    general -unixpw is not required for this sort of scheme, but it is
    convenient because it determines exactly who the user is whose display
@@ -3452,7 +3480,7 @@ xpw=
    Q-52: Can I have x11vnc restart itself after it terminates?
 
    One could do this in a shell script, but now there is an option
-   [425]-loop that makes it easier. Of course when x11vnc restarts it
+   [433]-loop that makes it easier. Of course when x11vnc restarts it
    needs to have permissions to connect to the (potentially new) X
    display. This mode could be useful if the X server restarts often. Use
    e.g. "-loop5000" to sleep 5000 ms between restarts. Also "-loop2000,5"
@@ -3463,7 +3491,7 @@ xpw=
    web browser?
 
    To have x11vnc serve up a Java VNC viewer applet to any web browsers
-   that connect to it, run x11vnc with this [426]option:
+   that connect to it, run x11vnc with this [434]option:
   -httpdir /path/to/the/java/classes/dir
 
    (this directory will contain the files index.vnc and, for example,
@@ -3482,7 +3510,7 @@ xpw=
    then you can connect to that URL with any Java enabled browser. Feel
    free to customize the default index.vnc file in the classes directory.
 
-   As of May/2005 the [427]-http option will try to guess where the Java
+   As of May/2005 the [435]-http option will try to guess where the Java
    classes jar file is by looking in expected locations and ones relative
    to the x11vnc binary.
 
@@ -3498,7 +3526,7 @@ xpw=
    As of Mar/2004 x11vnc supports reverse connections. On Unix one starts
    the VNC viewer in listen mode: vncviewer -listen (see your
    documentation for Windows, etc), and then starts up x11vnc with the
-   [428]-connect option. To connect immediately at x11vnc startup time
+   [436]-connect option. To connect immediately at x11vnc startup time
    use the "-connect host:port" option (use commas for a list of hosts to
    connect to). The ":port" is optional (default is 5500).
 
@@ -3506,7 +3534,7 @@ xpw=
    file is checked periodically (about once a second) for new hosts to
    connect to.
 
-   The [429]-remote control option (aka -R) can also be used to do this
+   The [437]-remote control option (aka -R) can also be used to do this
    during an active x11vnc session, e.g.:
 x11vnc -display :0 -R connect:hostname.domain
 
@@ -3518,7 +3546,7 @@ x11vnc -display :0 -R connect:hostname.domain
    starting x11vnc.
 
    To use the vncconnect(1) program (from the core VNC package at
-   www.realvnc.com) specify the [430]-vncconnect option to x11vnc (Note:
+   www.realvnc.com) specify the [438]-vncconnect option to x11vnc (Note:
    as of Dec/2004 -vncconnect is now the default). vncconnect(1) must be
    pointed to the same X11 DISPLAY as x11vnc (since it uses X properties
    to communicate with x11vnc). If you do not have or do not want to get
@@ -3563,7 +3591,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
 
    There are some annoyances WRT Xvfb though. The default keyboard
    mapping seems to be very poor. One should run x11vnc with
-   [431]-add_keysyms option to have keysyms added automatically. Also, to
+   [439]-add_keysyms option to have keysyms added automatically. Also, to
    add the Shift_R and Control_R modifiers something like this is needed:
 #!/bin/sh
 xmodmap -e "keycode any = Shift_R"
@@ -3585,11 +3613,11 @@ xmodmap -e "add Control = Control_L Control_R"
 
    The main drawback to this method (besides requiring extra
    configuration and possibly root permission) is that it also does the
-   Linux Virtual Console/Terminal (VC/VT) [432]switching even though it
+   Linux Virtual Console/Terminal (VC/VT) [440]switching even though it
    does not need to (since it doesn't use a real framebuffer). There are
    some "dual headed" (actually multi-headed/multi-user) patches to the X
    server that turn off the VT usage in the X server. Update: As of
-   Jul/2005 we have an LD_PRELOAD script [433]Xdummy that allows you to
+   Jul/2005 we have an LD_PRELOAD script [441]Xdummy that allows you to
    use a stock (i.e. unpatched) Xorg or XFree86 server with the "dummy"
    driver and not have any VT switching problems! Currently Xdummy needs
    to be run as root, but with some luck that may be relaxed in the
@@ -3621,7 +3649,7 @@ startx -- /path/to/Xdummy :1
    An X server can be started on the headless machine (sometimes this
    requires configuring the X server to not fail if it cannot detect a
    keyboard or mouse, see the next paragraph). Then you can export that X
-   display via x11vnc (e.g. see [434]this FAQ) and access it from
+   display via x11vnc (e.g. see [442]this FAQ) and access it from
    anywhere on the network via a VNC viewer.
 
    Some tips on getting X servers to start on machines without keyboard
@@ -3664,7 +3692,7 @@ startx -- /path/to/Xdummy :1
   19/03/2004 10:10:58 error creating tile-row shm for len=4
   19/03/2004 10:10:58 reverting to single_copytile mode
 
-   Here is a shell script [435]shm_clear to list and prompt for removal
+   Here is a shell script [443]shm_clear to list and prompt for removal
    of your unattached shm segments (attached ones are skipped). I use it
    while debugging x11vnc (I use "shm_clear -y" to assume "yes" for each
    prompt). If x11vnc is regularly not cleaning up its shm segments,
@@ -3698,40 +3726,40 @@ ied)
    in /etc/system. See the next paragraph for more workarounds.
 
    To minimize the number of shm segments used by x11vnc try using the
-   [436]-onetile option (corresponds to only 3 shm segments used, and
+   [444]-onetile option (corresponds to only 3 shm segments used, and
    adding -fs 1.0 knocks it down to 2). If you are having much trouble
    with shm segments, consider disabling shm completely via the
-   [437]-noshm option. Performance will be somewhat degraded but when
+   [445]-noshm option. Performance will be somewhat degraded but when
    done over local machine sockets it should be acceptable (see an
-   [438]earlier question discussing -noshm).
+   [446]earlier question discussing -noshm).
 
 
    Q-58: How can I make x11vnc use less system resources?
 
-   The [439]-nap (now on by default) and "[440]-wait n" (where n is the
+   The [447]-nap (now on by default) and "[448]-wait n" (where n is the
    sleep between polls in milliseconds, the default is 30 or so) option
-   are good places to start. Something like "[441]-sb 15" will cause
+   are good places to start. Something like "[449]-sb 15" will cause
    x11vnc to go into a deep-sleep mode after 15 seconds of no activity
    (instead of the default 60).
 
    Reducing the X server bits per pixel depth (e.g. to 16bpp or even
    8bpp) will further decrease memory I/O and network I/O. The ShadowFB
-   will make x11vnc's screen polling less severe. Using the [442]-onetile
+   will make x11vnc's screen polling less severe. Using the [450]-onetile
    option will use less memory and use fewer shared memory slots (add
-   [443]-fs 1.0 for one less slot).
+   [451]-fs 1.0 for one less slot).
 
 
    Q-59: How can I make x11vnc use MORE system resources?
 
-   You can try [444]-threads and dial down the wait time (e.g. -wait 1)
-   and possibly dial down [445]-defer as well. Note that if you try to
+   You can try [452]-threads and dial down the wait time (e.g. -wait 1)
+   and possibly dial down [453]-defer as well. Note that if you try to
    increase the "frame rate" too much you can bog down the server end
    with the extra work it needs to do compressing the framebuffer data,
    etc.
 
    That said, it is possible to "stream" video via x11vnc if the video
    window is small enough. E.g. a 256x192 xawtv TV capture window (using
-   the x11vnc [446]-id option) can be streamed over a LAN or wireless at
+   the x11vnc [454]-id option) can be streamed over a LAN or wireless at
    a reasonable frame rate.
 
 
@@ -3747,7 +3775,7 @@ ied)
      * Use a smaller desktop size (e.g. 1024x768 instead of 1280x1024)
      * Make sure the desktop background is a solid color (the background
        is resent every time it is re-exposed). Consider using the
-       [447]-solid [color] option to try to do this automatically.
+       [455]-solid [color] option to try to do this automatically.
      * Configure your window manager or desktop "theme" to not use fancy
        images, shading, and gradients for the window decorations, etc.
        Disable window animations, etc. Maybe your desktop has a "low
@@ -3756,9 +3784,9 @@ ied)
        -> Use Smooth Scrolling (deselect it).
      * Avoid small scrolls of large windows using the Arrow keys or
        scrollbar. Try to use PageUp/PageDown instead. (not so much of a
-       problem in x11vnc 0.7.2 if [448]-scrollcopyrect is active and
+       problem in x11vnc 0.7.2 if [456]-scrollcopyrect is active and
        detecting scrolls for the application).
-     * If the [449]-wireframe option is not available (earlier than
+     * If the [457]-wireframe option is not available (earlier than
        x11vnc 0.7.2 or you have disabled it via -nowireframe) then
        Disable Opaque Moves and Resizes in the window manager/desktop.
      * However if -wireframe is active (on by default in x11vnc 0.7.2)
@@ -3778,7 +3806,7 @@ ied)
        noticed.
 
      VNC viewer parameters:
-     * Use a [450]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+     * Use a [458]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
        with ZRLE encoding is not too bad either; some claim it is
        faster).
      * Make sure the tight (or zrle) encoding is being used (look at
@@ -3800,37 +3828,37 @@ ied)
        file.
 
      x11vnc parameters:
-     * Make sure the [451]-wireframe option is active (it should be on by
+     * Make sure the [459]-wireframe option is active (it should be on by
        default) and you have Opaque Moves/Resizes Enabled in the window
        manager.
-     * Make sure the [452]-scrollcopyrect option is active (it should be
+     * Make sure the [460]-scrollcopyrect option is active (it should be
        on by default). This detects scrolls in many (but not all)
        applications an applies the CopyRect encoding for a big speedup.
      * Enforce a solid background when VNC viewers are connected via
-       [453]-solid
-     * Specify [454]-speeds modem to force the wireframe and
+       [461]-solid
+     * Specify [462]-speeds modem to force the wireframe and
        scrollcopyrect heuristic parameters (and any future ones) to those
        of a dialup modem connection (or supply the rd,bw,lat numerical
        values that characterize your link).
      * If wireframe and scrollcopyrect aren't working, try using the more
-       drastic [455]-nodragging (no screen updates when dragging mouse,
+       drastic [463]-nodragging (no screen updates when dragging mouse,
        but sometimes you miss visual feedback)
-     * Set [456]-fs 1.0 (disables fullscreen updates)
-     * Try increasing [457]-wait or [458]-defer (reduces the maximum
+     * Set [464]-fs 1.0 (disables fullscreen updates)
+     * Try increasing [465]-wait or [466]-defer (reduces the maximum
        "frame rate", but won't help much for large screen changes)
-     * Try the [459]-progressive pixelheight mode with the block
+     * Try the [467]-progressive pixelheight mode with the block
        pixelheight 100 or so (delays sending vertical blocks since they
        may change while viewer is receiving earlier ones)
-     * If you just want to watch one (simple) window use [460]-id (cuts
+     * If you just want to watch one (simple) window use [468]-id (cuts
        down extraneous polling and updates, but can be buggy or
        insufficient)
-     * Set [461]-nosel (disables all clipboard selection exchange)
-     * Use [462]-nocursor and [463]-nocursorpos (repainting the remote
+     * Set [469]-nosel (disables all clipboard selection exchange)
+     * Use [470]-nocursor and [471]-nocursorpos (repainting the remote
        cursor position and shape takes resources and round trips)
      * On very slow links (e.g. <= 28.8) you may need to increase the
-       [464]-readtimeout n setting if it sometimes takes more than 20sec
+       [472]-readtimeout n setting if it sometimes takes more than 20sec
        to paint the full screen, etc.
-     * Do not use [465]-fixscreen to automatically refresh the whole
+     * Do not use [473]-fixscreen to automatically refresh the whole
        screen, tap three Alt_L's then the screen has painting errors
        (rare problem).
 
@@ -3853,7 +3881,7 @@ ied)
 
    Note that the DAMAGE extension does not speed up the actual reading of
    pixels from the video card framebuffer memory, by, say, mirroring them
-   in main memory. So reading the fb is still painfully [466]slow (e.g.
+   in main memory. So reading the fb is still painfully [474]slow (e.g.
    5MB/sec), and so even using X DAMAGE when large changes occur on the
    screen the bulk of the time is still spent retrieving them. Not ideal,
    but use of the ShadowFB XFree86/Xorg option speeds up the reading
@@ -3871,27 +3899,27 @@ ied)
    DAMAGE rectangles to contain real damage. The larger rectangles are
    only used as hints to focus the traditional scanline polling (i.e. if
    a scanline doesn't intersect a recent DAMAGE rectangle, the scan is
-   skipped). You can use the "[467]-xd_area A" option to adjust the size
+   skipped). You can use the "[475]-xd_area A" option to adjust the size
    of the trusted DAMAGE rectangles. The default is 20000 pixels (e.g. a
    140x140 square, etc). Use "-xd_area 0" to disable the cutoff and trust
    all DAMAGE rectangles.
 
-   The option "[468]-xd_mem f" may also be of use in tuning the
-   algorithm. To disable using DAMAGE entirely use "[469]-noxdamage".
+   The option "[476]-xd_mem f" may also be of use in tuning the
+   algorithm. To disable using DAMAGE entirely use "[477]-noxdamage".
 
 
    Q-62: When I drag windows around with the mouse or scroll up and down
    things really bog down (unless I do the drag in a single, quick
    motion). Is there anything to do to improve things?
 
-   This problem is primarily due to [470]slow hardware read rates from
+   This problem is primarily due to [478]slow hardware read rates from
    video cards: as you scroll or move a large window around the screen
    changes are much too rapid for x11vnc to keep up them (it can usually
    only read the video card at about 5-10 MB/sec, so it can take a good
    fraction of a second to read the changes induce from moving a large
    window, if this to be done a number of times in succession the window
    or scroll appears to "lurch" forward). See the description in the
-   [471]-pointer_mode option for more info. The next bottleneck is
+   [479]-pointer_mode option for more info. The next bottleneck is
    compressing all of these changes and sending them out to connected
    viewers, however the VNC protocol is pretty much self-adapting with
    respect to that (updates are only packaged and sent when viewers ask
@@ -3901,26 +3929,26 @@ ied)
    default should now be much better than before and dragging small
    windows around should no longer be a huge pain. If for some reason
    these changes make matters worse, you can go back to the old way via
-   the "[472]-pointer_mode 1" option.
+   the "[480]-pointer_mode 1" option.
 
-   Also added was the [473]-nodragging option that disables all screen
+   Also added was the [481]-nodragging option that disables all screen
    updates while dragging with the mouse (i.e. mouse motion with a button
    held down). This gives the snappiest response, but might be undesired
    in some circumstances when you want to see the visual feedback while
    dragging (e.g. menu traversal or text selection).
 
-   As of Dec/2004 the [474]-pointer_mode n option was introduced. n=1 is
+   As of Dec/2004 the [482]-pointer_mode n option was introduced. n=1 is
    the original mode, n=2 an improvement, etc.. See the -pointer_mode n
    help for more info.
 
-   Also, in some circumstances the [475]-threads option can improve
+   Also, in some circumstances the [483]-threads option can improve
    response considerably. Be forewarned that if more than one vncviewer
    is connected at the same time then libvncserver may not be thread safe
    (try to get the viewers to use different VNC encodings, e.g. tight and
    ZRLE).
 
-   As of Apr/2005 two new options (see the [476]wireframe FAQ and
-   [477]scrollcopyrect FAQ below) provide schemes to sweep this problem
+   As of Apr/2005 two new options (see the [484]wireframe FAQ and
+   [485]scrollcopyrect FAQ below) provide schemes to sweep this problem
    under the rug for window moves or resizes and for some (but not all)
    window scrolls. These are the preferred way of avoiding the "lurching"
    problem, contact me if they are not working. (Note on SuSE the RECORD
@@ -3939,8 +3967,8 @@ ied)
    the window move/resize stops, it returns to normal processing: you
    should only see the window appear in the new position. This spares you
    from interacting with a "lurching" window between all of the
-   intermediate steps. BTW the lurching is due to [478]slow video card
-   read rates (see [479]here too). A displacement, even a small one, of a
+   intermediate steps. BTW the lurching is due to [486]slow video card
+   read rates (see [487]here too). A displacement, even a small one, of a
    large window requires a non-negligible amount of time, a good fraction
    of a second, to read in from the hardware framebuffer.
 
@@ -3948,7 +3976,7 @@ ied)
    for -wireframe to do any good.
 
    The mode is currently on by default because most people are afflicted
-   with the problem. It can be disabled with the [480]-nowireframe option
+   with the problem. It can be disabled with the [488]-nowireframe option
    (aka -nowf). Why might one want to turn off the wireframing? Since
    x11vnc is merely guessing when windows are being moved/resized, it may
    guess poorly for your window-manager or desktop, or even for the way
@@ -3993,13 +4021,13 @@ ied)
      * Maximum time to show a wireframe animation.
      * Minimum time between sending wireframe outlines.
 
-   See the [481]"-wireframe tweaks" option for more details. On a slow
+   See the [489]"-wireframe tweaks" option for more details. On a slow
    link, e.g. dialup modem, the parameters may be automatically adjusted
    for better response.
 
 
    CopyRect encoding:  In addition to the above there is the
-   [482]"-wirecopyrect mode" option. It is also on by default. This
+   [490]"-wirecopyrect mode" option. It is also on by default. This
    instructs x11vnc to not only show the wireframe animation, but to also
    instruct all connected VNC viewers to locally translate the window
    image data from the original position to the new position on the
@@ -4047,7 +4075,7 @@ ied)
    requiring the image data to be transmitted over the network. For fast
    links the speedup is primarily due to x11vnc not having to read the
    scrolled framebuffer data from the X server (recall that reading from
-   the hardware framebuffer is [483]slow).
+   the hardware framebuffer is [491]slow).
 
    To do this x11vnc uses the RECORD X extension to snoop the X11
    protocol between the X client with the focus window and the X server.
@@ -4069,10 +4097,10 @@ ied)
    the X server display: if one falls too far behind it could become a
    mess...
 
-   The initial implementation of [484]-scrollcopyrect option is useful in
+   The initial implementation of [492]-scrollcopyrect option is useful in
    that it detects many scrolls and thus gives a much nicer working
-   environment (especially when combined with the [485]-wireframe
-   [486]-wirecopyrect [487]options, which are also on by default; and if
+   environment (especially when combined with the [493]-wireframe
+   [494]-wirecopyrect [495]options, which are also on by default; and if
    you are willing to enable the ShadowFB things are very fast). The fact
    that there aren't long delays or lurches during scrolling is the
    primary improvement.
@@ -4105,10 +4133,10 @@ ied)
        One can tap the Alt_L key (Left "Alt" key) 3 times in a row to
        signal x11vnc to refresh the screen to all viewers. Your
        VNC-viewer may have its own screen refresh hot-key or button. See
-       also: [488]-fixscreen
+       also: [496]-fixscreen
      * Some applications, notably OpenOffice, do XCopyArea scrolls in
        weird ways that assume ancestor window clipping is taking place.
-       See the [489]-scr_skip option for ways to tweak this on a
+       See the [497]-scr_skip option for ways to tweak this on a
        per-application basis.
      * Selecting text while dragging the mouse may be slower, especially
        if the Button-down event happens near the window's edge. This is
@@ -4125,7 +4153,7 @@ ied)
        because it fails to detect scrolls in it. Sometimes clicking
        inside the application window or selecting some text in it to
        force the focus helps.
-     * When using the [490]-scale option there will be a quick CopyRect
+     * When using the [498]-scale option there will be a quick CopyRect
        scroll, but it needs to be followed by a slower "cleanup" update.
        This is because for a fixed finite screen resolution (e.g. 75 dpi)
        scaling and copyrect-ing are not exactly independent. Scaling
@@ -4138,7 +4166,7 @@ ied)
 
    If you find the -scrollcopyrect behavior too approximate or
    distracting you can go back to the standard polling-only update method
-   with the [491]-noscrollcopyrect (or -noscr for short). If you find
+   with the [499]-noscrollcopyrect (or -noscr for short). If you find
    some extremely bad and repeatable behavior for -scrollcopyrect please
    report a bug.
 
@@ -4177,23 +4205,23 @@ ied)
    this is because the cursor shape is often downloaded to the graphics
    hardware (video card), but I could be mistaken.
 
-   A simple kludge is provided by the "[492]-cursor X" option that
+   A simple kludge is provided by the "[500]-cursor X" option that
    changes the cursor when the mouse is on the root background (or any
    window has the same cursor as the root background). Note that desktops
    like GNOME or KDE often cover up the root background, so this won't
-   work for those cases. Also see the "[493]-cursor some" option for
+   work for those cases. Also see the "[501]-cursor some" option for
    additional kludges.
 
    Note that as of Aug/2004 on Solaris using the SUN_OVL overlay
    extension and IRIX, x11vnc can show the correct mouse cursor when the
-   [494]-overlay option is supplied. See [495]this FAQ for more info.
+   [502]-overlay option is supplied. See [503]this FAQ for more info.
 
    Also as of Dec/2004 XFIXES X extension support has been added to allow
    exact extraction of the mouse cursor shape. XFIXES fixes the problem
    of the cursor-shape being write-only: x11vnc can now query the X
    server for the current shape and send it back to the connected
    viewers. XFIXES is available on recent Linux Xorg based distros and
-   [496]Solaris 10.
+   [504]Solaris 10.
 
    The only XFIXES issue is the handling of alpha channel transparency in
    cursors. If a cursor has any translucency then in general it must be
@@ -4201,7 +4229,7 @@ ied)
    situations where the cursor transparency can also handled exactly:
    when the VNC Viewer requires the cursor shape be drawn into the VNC
    framebuffer or if you apply a patch to your VNC Viewer to extract
-   hidden alpha channel data under 32bpp. [497]Details can be found here.
+   hidden alpha channel data under 32bpp. [505]Details can be found here.
 
 
    Q-66: When using XFIXES cursorshape mode, some of the cursors look
@@ -4234,17 +4262,17 @@ ied)
    for most cursor themes and you don't have to worry about it.
 
    In case it still looks bad for your cursor theme, there are (of
-   course!) some tunable parameters. The "[498]-alphacut n" option lets
+   course!) some tunable parameters. The "[506]-alphacut n" option lets
    you set the threshold "n" (between 0 and 255): cursor pixels with
    alpha values below n will be considered completely transparent while
    values equal to or above n will be completely opaque. The default is
-   240. The "[499]-alphafrac f" option tries to correct individual
+   240. The "[507]-alphafrac f" option tries to correct individual
    cursors that did not fare well with the default -alphacut value: if a
    cursor has less than fraction f (between 0.0 and 1.0) of its pixels
    selected by the default -alphacut, the threshold is lowered until f of
    its pixels are selected. The default fraction is 0.33.
 
-   Finally, there is an option [500]-alpharemove that is useful for
+   Finally, there is an option [508]-alpharemove that is useful for
    themes where many cursors are light colored (e.g. "whiteglass").
    XFIXES returns the cursor data with the RGB values pre-multiplied by
    the alpha value. If the white cursors look too grey, specify
@@ -4270,10 +4298,10 @@ ied)
    alpha channel data to libvncserver. However, this data will only be
    used for VNC clients that do not support the CursorShapeUpdates VNC
    extension (or have disabled it). It can be disabled for all clients
-   with the [501]-nocursorshape x11vnc option. In this case the cursor is
+   with the [509]-nocursorshape x11vnc option. In this case the cursor is
    drawn, correctly blended with the background, into the VNC framebuffer
    before being sent out to the client. So the alpha blending is done on
-   the x11vnc side. Use the [502]-noalphablend option to disable this
+   the x11vnc side. Use the [510]-noalphablend option to disable this
    behavior (always approximate transparent cursors with opaque RGB
    values).
 
@@ -4297,14 +4325,17 @@ ied)
    example on how to change the Windows TightVNC viewer to achieve the
    same thing (send me the patch if you get that working).
 
+   This patch is applied to the [511]Enhanced TightVNC Viewer package we
+   provide.
+
    [Mouse Pointer]
 
    Q-68: Why does the mouse arrow just stay in one corner in my
    vncviewer, whereas my cursor (that does move) is just a dot?
 
-   This default takes advantage of a [503]tightvnc extension
+   This default takes advantage of a [512]tightvnc extension
    (CursorShapeUpdates) that allows specifying a cursor image shape for
-   the local VNC viewer. You may disable it with the [504]-nocursor
+   the local VNC viewer. You may disable it with the [513]-nocursor
    option to x11vnc if your viewer does not have this extension.
 
    Note: as of Aug/2004 this should be fixed: the default for
@@ -4318,17 +4349,17 @@ ied)
    clients (i.e. passive viewers can see the mouse cursor being moved
    around by another viewer)?
 
-   Use the [505]-cursorpos option when starting x11vnc. A VNC viewer must
+   Use the [514]-cursorpos option when starting x11vnc. A VNC viewer must
    support the Cursor Positions Updates for the user to see the mouse
    motions (the TightVNC viewers support this). As of Aug/2004 -cursorpos
-   is the default. See also [506]-nocursorpos and [507]-nocursorshape.
+   is the default. See also [515]-nocursorpos and [516]-nocursorshape.
 
 
    Q-70: Is it possible to swap the mouse buttons (e.g. left-handed
    operation), or arbitrarily remap them? How about mapping button clicks
    to keystrokes, e.g. to partially emulate Mouse wheel scrolling?
 
-   You can remap the mouse buttons via something like: [508]-buttonmap
+   You can remap the mouse buttons via something like: [517]-buttonmap
    13-31 (or perhaps 12-21). Also, note that xmodmap(1) lets you directly
    adjust the X server's button mappings, but in some circumstances it
    might be more desirable to have x11vnc do it.
@@ -4336,7 +4367,7 @@ ied)
    One user had an X server with only one mouse button(!) and was able to
    map all of the VNC client mouse buttons to it via: -buttonmap 123-111.
 
-   Note that the [509]-debug_pointer option prints out much info for
+   Note that the [518]-debug_pointer option prints out much info for
    every mouse/pointer event and is handy in solving problems.
 
    To map mouse button clicks to keystrokes you can use the alternate
@@ -4358,7 +4389,7 @@ ied)
 
    Exactly what keystroke "scrolling" events they should be bound to
    depends on one's taste. If this method is too approximate, one could
-   consider not using [510]-buttonmap but rather configuring the X server
+   consider not using [519]-buttonmap but rather configuring the X server
    to think it has a mouse with 5 buttons even though the physical mouse
    does not. (e.g. 'Option "ZAxisMapping" "4 5"').
 
@@ -4388,7 +4419,7 @@ ied)
    Q-71: How can I get my AltGr and Shift modifiers to work between
    keyboards for different languages?
 
-   The option [511]-modtweak should help here. It is a mode that monitors
+   The option [520]-modtweak should help here. It is a mode that monitors
    the state of the Shift and AltGr Modifiers and tries to deduce the
    correct keycode to send, possibly by sending fake modifier key presses
    and releases in addition to the actual keystroke.
@@ -4397,16 +4428,16 @@ ied)
    to get the old behavior). This was done because it was noticed on
    newer XFree86 setups even on bland "us" keyboards like "pc104 us"
    XFree86 included a "ghost" key with both "<" and ">" it. This key does
-   not exist on the keyboard (see [512]this FAQ for more info). Without
+   not exist on the keyboard (see [521]this FAQ for more info). Without
    -modtweak there was then an ambiguity in the reverse map keysym =>
    keycode, making it so the "<" symbol could not be typed.
 
-   Also see the [513]FAQ about the -xkb option for a more powerful method
+   Also see the [522]FAQ about the -xkb option for a more powerful method
    of modifier tweaking for use on X servers with the XKEYBOARD
    extension.
 
    When trying to resolve keyboard mapping problems, note that the
-   [514]-debug_keyboard option prints out much info for every keystroke
+   [523]-debug_keyboard option prints out much info for every keystroke
    and so can be useful debugging things.
 
 
@@ -4418,9 +4449,9 @@ ied)
    (e.g. pc105 in the XF86Config file when it should be something else,
    say pc104).
 
-   Short Cut: Try the [515]-xkb or [516]-sloppy_keys options and see if
+   Short Cut: Try the [524]-xkb or [525]-sloppy_keys options and see if
    that helps the situation. The discussion below is a bit outdated (e.g.
-   [517]-modtweak is now the default) but it is useful reference for
+   [526]-modtweak is now the default) but it is useful reference for
    various tricks and so is kept.
 
 
@@ -4463,17 +4494,17 @@ ied)
    -remap less-comma
 
    These are convenient in that they do not modify the actual X server
-   settings. The former ([518]-modtweak) is a mode that monitors the
+   settings. The former ([527]-modtweak) is a mode that monitors the
    state of the Shift and AltGr modifiers and tries to deduce the correct
    keycode sequence to send. Since Jul/2004 -modtweak is now the default.
-   The latter ([519]-remap less-comma) is an immediate remapping of the
+   The latter ([528]-remap less-comma) is an immediate remapping of the
    keysym less to the keysym comma when it comes in from a client (so
    when Shift is down the comma press will yield "<").
 
-   See also the [520]FAQ about the -xkb option as a possible workaround
+   See also the [529]FAQ about the -xkb option as a possible workaround
    using the XKEYBOARD extension.
 
-   Note that the [521]-debug_keyboard option prints out much info for
+   Note that the [530]-debug_keyboard option prints out much info for
    every keystroke to aid debugging keyboard problems.
 
 
@@ -4481,13 +4512,13 @@ ied)
    (i.e. an extra comma).
 
    This is likely because you press "Shift" then "<" but then released
-   the Shift key before releasing the "<". Because of a [522]keymapping
+   the Shift key before releasing the "<". Because of a [531]keymapping
    ambiguity the last event "< up" is interpreted as "," because that key
    unshifted is the comma.
 
-   This should not happen in [523]-xkb mode, because it works hard to
+   This should not happen in [532]-xkb mode, because it works hard to
    resolve the ambiguities. If you do not want to use -xkb, try the
-   option [524]-sloppy_keys to attempt a similar type of algorithm.
+   option [533]-sloppy_keys to attempt a similar type of algorithm.
 
 
    Q-74: I'm using an "international" keyboard (e.g. German "de", or
@@ -4511,7 +4542,7 @@ ied)
    In both cases no AltGr is sent to the VNC server, but we know AltGr is
    needed on the physical international keyboard to type a "@".
 
-   This all worked fine with x11vnc running with the [525]-modtweak
+   This all worked fine with x11vnc running with the [534]-modtweak
    option (it figures out how to adjust the Modifier keys (Shift or
    AltGr) to get the "@"). However it fails under recent versions of
    XFree86 (and the X.org fork). These run the XKEYBOARD extension by
@@ -4528,7 +4559,7 @@ ied)
      * there is a new option -xkb to use the XKEYBOARD extension API to
        do the Modifier key tweaking.
 
-   The [526]-xkb option seems to fix all of the missing keys: "@", "<",
+   The [535]-xkb option seems to fix all of the missing keys: "@", "<",
    ">", etc.: it is recommended that you try it if you have this sort of
    problem. Let us know if there are any remaining problems (see the next
    paragraph for some known problems). If you specify the -debug_keyboard
@@ -4536,7 +4567,7 @@ ied)
    debugging output (send it along with any problems you report).
 
    Update: as of Jun/2005 x11vnc will try to automatically enable
-   [527]-xkb if it appears that would be beneficial (e.g. if it sees any
+   [536]-xkb if it appears that would be beneficial (e.g. if it sees any
    of "@", "<", ">", "[" and similar keys are mapped in a way that needs
    the -xkb to access them). To disable this automatic check use -noxkb.
 
@@ -4551,7 +4582,7 @@ ied)
        was attached to keycode 93 (no physical key generates this
        keycode) while ISO_Level3_Shift was attached to keycode 113. The
        keycode skipping option was used to disable the ghost key:
-       [528]-skip_keycodes 93
+       [537]-skip_keycodes 93
      * In implementing -xkb we noticed that some characters were still
        not getting through, e.g. "~" and "^". This is not really an
        XKEYBOARD problem. What was happening was the VNC viewer was
@@ -4569,16 +4600,16 @@ ied)
        What to do? In general the VNC protocol has not really solved this
        problem: what should be done if the VNC viewer sends a keysym not
        recognized by the VNC server side? Workarounds can possibly be
-       created using the [529]-remap x11vnc option:
+       created using the [538]-remap x11vnc option:
   -remap asciitilde-dead_tilde,asciicircum-dead_circumflex
        etc. Use -remap filename if the list is long. Please send us your
        workarounds for this problem on your keyboard. Perhaps we can have
        x11vnc adjust automatically at some point. Also see the
-       [530]-add_keysyms option in the next paragraph.
-       Update: for convenience "[531]-remap DEAD" does many of these
+       [539]-add_keysyms option in the next paragraph.
+       Update: for convenience "[540]-remap DEAD" does many of these
        mappings at once.
-     * To complement the above workaround using the [532]-remap, an
-       option [533]-add_keysyms was added. This option instructs x11vnc
+     * To complement the above workaround using the [541]-remap, an
+       option [542]-add_keysyms was added. This option instructs x11vnc
        to bind any unknown Keysyms coming in from VNC viewers to unused
        Keycodes in the X server. This modifies the global state of the X
        server. When x11vnc exits it removes the extra keymappings it
@@ -4597,7 +4628,7 @@ ied)
 
    Short answer: disable key autorepeating by running the command "xset r
    off" on the Xserver where x11vnc is run (restore via "xset r on") or
-   use the new (Jul/2004) [534]-norepeat x11vnc option. You will still
+   use the new (Jul/2004) [543]-norepeat x11vnc option. You will still
    have autorepeating because that is taken care of on your VNC viewer
    side.
 
@@ -4621,7 +4652,7 @@ ied)
    off", does the problem go away?
 
    The workaround is to manually apply "xset r off" and "xset r on" as
-   needed, or to use the [535]-norepeat (which has since Dec/2004 been
+   needed, or to use the [544]-norepeat (which has since Dec/2004 been
    made the default). Note that with X server autorepeat turned off the
    VNC viewer side of the connection will (nearly always) do its own
    autorepeating so there is no big loss here, unless someone is also
@@ -4632,7 +4663,7 @@ ied)
    keystrokes!!
 
    Are you using x11vnc to log in to an X session via display manager?
-   (as described in [536]this FAQ) If so, x11vnc is starting before your
+   (as described in [545]this FAQ) If so, x11vnc is starting before your
    session and it disables autorepeat when you connect, but then after
    you log in your session startup (GNOME, KDE, ...) could be resetting
    the autorepeat to be on. Or it could be something inside your desktop
@@ -4656,7 +4687,7 @@ ied)
    machine where I run the VNC viewer does not. Is there a way I can map
    a local unused key to send an AltGr? How about a Compose key as well?
 
-   Something like "[537]-remap Super_R-Mode_switch" x11vnc option may
+   Something like "[546]-remap Super_R-Mode_switch" x11vnc option may
    work. Note that Super_R is the "Right Windoze(tm) Flaggie" key; you
    may want to choose another. The -debug_keyboard option comes in handy
    in finding keysym names (so does xev(1)).
@@ -4679,7 +4710,7 @@ ied)
 
    Since xmodmap(1) modifies the X server mappings you may not want to do
    this (because it affects local work on that machine). Something like
-   the [538]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+   the [547]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
    needs, and does not modify the X server environment. Note that you
    cannot send Alt_L in this case, maybe -remap Super_L-Meta_L would be a
    better choice if the Super_L key is typically unused in Unix.
@@ -4690,7 +4721,7 @@ ied)
 
    This can be done directly in some X servers using AccessX and
    Pointer_EnableKeys, but is a bit awkward. It may be more convenient to
-   have x11vnc do the remapping. This can be done via the [539]-remap
+   have x11vnc do the remapping. This can be done via the [548]-remap
    option using the fake "keysyms" Button1, Button2, etc. as the "to"
    keys (i.e. the ones after the "-")
 
@@ -4699,7 +4730,7 @@ ied)
    button "paste" because (using XFree86/Xorg Emulate3Buttons) you have
    to click both buttons on the touch pad at the same time. This
    remapping:
-  [540]-remap Super_R-Button2
+  [549]-remap Super_R-Button2
 
    maps the Super_R "flag" key press to the Button2 click, thereby making
    X pasting a bit easier.
@@ -4718,10 +4749,10 @@ ied)
    Caps_Lock in the viewer your local machine goes into the Caps_Lock on
    state and sends keysym "A" say when you press "a". x11vnc will then
    fake things up so that Shift is held down to generate "A". The
-   [541]-skip_lockkeys option should help to accomplish this. For finer
-   grain control use something like: "[542]-remap Caps_Lock-None".
+   [550]-skip_lockkeys option should help to accomplish this. For finer
+   grain control use something like: "[551]-remap Caps_Lock-None".
 
-   Also try the [543]-nomodtweak and [544]-capslock options.
+   Also try the [552]-nomodtweak and [553]-capslock options.
 
    [Screen Related Issues and Features]
 
@@ -4744,7 +4775,7 @@ ied)
    There may also be scaling viewers out there (e.g. TightVNC or UltraVNC
    on Windows) that automatically shrink or expand the remote framebuffer
    to fit the local display. Especially for hand-held devices. See also
-   [545]this FAQ on x11vnc scaling.
+   [554]this FAQ on x11vnc scaling.
 
 
    Q-82: Does x11vnc support server-side framebuffer scaling? (E.g. to
@@ -4752,7 +4783,7 @@ ied)
 
    As of Jun/2004 x11vnc provides basic server-side scaling. It is a
    global scaling of the desktop, not a per-client setting. To enable it
-   use the "[546]-scale fraction" option. "fraction" can either be a
+   use the "[555]-scale fraction" option. "fraction" can either be a
    floating point number (e.g. -scale 0.5) or the alternative m/n
    fraction notation (e.g. -scale 3/4). Note that if fraction is greater
    than one the display is magnified.
@@ -4773,7 +4804,7 @@ ied)
 
    One can also use the ":nb" with an integer scale factor (say "-scale
    2:nb") to use x11vnc as a screen magnifier for vision impaired
-   [547]applications. Since with integer scale factors the framebuffers
+   [556]applications. Since with integer scale factors the framebuffers
    become huge and scaling operations time consuming, be sure to use
    ":nb" for the fastest response.
 
@@ -4799,7 +4830,7 @@ ied)
    If one desires per-client scaling for something like 1:1 from a
    workstation and 1:2 from a smaller device (e.g. handheld), currently
    the only option is to run two (or more) x11vnc processes with
-   different scalings listening on separate ports ([548]-rfbport option,
+   different scalings listening on separate ports ([557]-rfbport option,
    etc.).
 
    Update: As of May/2006 x11vnc also supports the UltraVNC server-side
@@ -4809,8 +4840,8 @@ ied)
    "-rfbversion 3.6" for this to be recognized by UltraVNC viewers.
 
    BTW, whenever you run two or more x11vnc's on the same X display and
-   use the [549]GUI, then to avoid all of the x11vnc's simultaneously
-   answering the gui you will need to use something like [550]"-connect
+   use the [558]GUI, then to avoid all of the x11vnc's simultaneously
+   answering the gui you will need to use something like [559]"-connect
    file1 -gui ..." with different connect files for each x11vnc you want
    to control via the gui (or remote-control). The "-connect file1" usage
    gives separate communication channels between a x11vnc proces and the
@@ -4819,7 +4850,7 @@ ied)
 
    Update: As of Mar/2005 x11vnc now scales the mouse cursor with the
    same scale factor as the screen. If you don't want that, use the
-   [551]"-scale_cursor frac" option to set the cursor scaling to a
+   [560]"-scale_cursor frac" option to set the cursor scaling to a
    different factor (e.g. use "-scale_cursor 1" to keep the cursor at its
    natural unscaled size).
 
@@ -4841,17 +4872,17 @@ ied)
    screen is not rectangular (e.g. 1280x1024 and 1024x768 monitors joined
    together), then there will be "non-existent" areas on the screen. The
    X server will return "garbage" image data for these areas and so they
-   may be distracting to the viewer. The [552]-blackout x11vnc option
+   may be distracting to the viewer. The [561]-blackout x11vnc option
    allows you to blacken-out rectangles by manually specifying their
    WxH+X+Y geometries. If your system has the libXinerama library, the
-   [553]-xinerama x11vnc option can be used to have it automatically
+   [562]-xinerama x11vnc option can be used to have it automatically
    determine the rectangles to be blackened out. (Note on 8bpp
    PseudoColor displays the fill color may not be black). Update:
-   [554]-xinerama is now on by default.
+   [563]-xinerama is now on by default.
 
    Some users have reported that the mouse does not behave properly for
    their Xinerama display: i.e. the mouse cannot be moved to all regions
-   of the large display. If this happens try using the [555]-xwarppointer
+   of the large display. If this happens try using the [564]-xwarppointer
    option. This instructs x11vnc to fake mouse pointer motions using the
    XWarpPointer function instead of the XTestFakeMotionEvent XTEST
    function. (This may be due to a bug in the X server for XTEST when
@@ -4876,23 +4907,23 @@ ied)
    Note: if you are running on Solaris 8 or earlier you can easily hit up
    against the maximum of 6 shm segments per process (for Xsun in this
    case) from running multiple x11vnc processes. You should modify
-   /etc/system as mentioned in another [556]FAQ to increase the limit. It
-   is probably also a good idea to run with the [557]-onetile option in
+   /etc/system as mentioned in another [565]FAQ to increase the limit. It
+   is probably also a good idea to run with the [566]-onetile option in
    this case (to limit each x11vnc to 3 shm segments), or even
-   [558]-noshm to use no shm segments.
+   [567]-noshm to use no shm segments.
 
 
    Q-85: Can x11vnc show only a portion of the display? (E.g. for a
    special purpose rfb application).
 
-   As of Mar/2005 x11vnc has the "[559]-clip WxH+X+Y" option to select a
+   As of Mar/2005 x11vnc has the "[568]-clip WxH+X+Y" option to select a
    rectangle of width W, height H and offset (X, Y). Thus the VNC screen
    will be the clipped sub-region of the display and be only WxH in size.
-   One user used -clip to split up a large [560]Xinerama screen into two
+   One user used -clip to split up a large [569]Xinerama screen into two
    more managable smaller screens.
 
    This also works to view a sub-region of a single application window if
-   the [561]-id or [562]-sid options are used. The offset is measured
+   the [570]-id or [571]-sid options are used. The offset is measured
    from the upper left corner of the selected window.
 
 
@@ -4901,7 +4932,7 @@ ied)
    crash.
 
    As of Dec/2004 x11vnc supports XRANDR. You enable it with the
-   [563]-xrandr option to make x11vnc monitor XRANDR events and also trap
+   [572]-xrandr option to make x11vnc monitor XRANDR events and also trap
    X server errors if the screen change occurred in the middle of an X
    call like XGetImage. Once it traps the screen change it will create a
    new framebuffer using the new screen.
@@ -4911,7 +4942,7 @@ ied)
    then the viewer will automatically resize. Otherwise, the new
    framebuffer is fit as best as possible into the original viewer size
    (portions of the screen may be clipped, unused, etc). For these
-   viewers you can try the [564]-padgeom option to make the region big
+   viewers you can try the [573]-padgeom option to make the region big
    enough to hold all resizes and rotations.
 
    If you specify "-xrandr newfbsize" then vnc viewers that do not
@@ -4924,7 +4955,7 @@ ied)
    reflect the screen that the VNC viewers see? (e.g. for a handheld
    whose screen is rotated 90 degrees).
 
-   As of Jul/2006 there is the [565]-rotate option allow this. E.g's:
+   As of Jul/2006 there is the [574]-rotate option allow this. E.g's:
    "-rotate +90", "-rotate -90", "-rotate x", etc.
 
 
@@ -4987,9 +5018,9 @@ ied)
      * Fullscreen mode
 
    The way VMWare does Fullscreen mode on Linux is to display the Guest
-   desktop in a separate Virtual Console (e.g. VC 8) (see [566]this FAQ
+   desktop in a separate Virtual Console (e.g. VC 8) (see [575]this FAQ
    on VC's for background). Unfortunately, this Fullscreen VC is not an X
-   server. So x11vnc cannot access it (however, [567]see this discussion
+   server. So x11vnc cannot access it (however, [576]see this discussion
    of -rawfb for a possible workaround). x11vnc works fine with "Normal X
    application window" and "Quick-Switch mode" because these use X.
 
@@ -5010,13 +5041,13 @@ ied)
    improve response. One can also cut the display depth (e.g. to 16bpp)
    in this 2nd X session to improve video performance. This 2nd X session
    emulates Fullscreen mode to some degree and can be viewed via x11vnc
-   as long as the VMWare X session [568]is in the active VC.
+   as long as the VMWare X session [577]is in the active VC.
 
    Also note that with a little bit of playing with "xwininfo -all
    -children" output one can extract the (non-toplevel) windowid of the
    of the Guest desktop only when VMWare is running as a normal X
    application. Then one can export just the guest desktop (i.e. without
-   the VMWare menu buttons) by use of the [569]-id windowid option. The
+   the VMWare menu buttons) by use of the [578]-id windowid option. The
    caveats are the X session VMWare is in must be in the active VC and
    the window must be fully visible, so this mode is not terribly
    convenient, but could be useful in some circumstances (e.g. running
@@ -5029,10 +5060,10 @@ ied)
    controlled) via VNC with x11vnc?
 
    As of Apr/2005 there is support for this. Two options were added:
-   "[570]-rawfb string" (to indicate the raw framembuffer device, file,
-   etc. and its parameters) and "[571]-pipeinput command" (to provide an
+   "[579]-rawfb string" (to indicate the raw framembuffer device, file,
+   etc. and its parameters) and "[580]-pipeinput command" (to provide an
    external program that will inject or otherwise process mouse and
-   keystroke input). Some useful [572]-pipeinput schemes, VID, CONSOLE,
+   keystroke input). Some useful [581]-pipeinput schemes, VID, CONSOLE,
    and UINPUT, have since been built into x11vnc for convenience.
 
    This non-X mode for x11vnc is somewhat experimental because it is so
@@ -5070,9 +5101,9 @@ ied)
    access method). Only use file if map isn't working. BTW, "mmap" is an
    alias for "map" and if you do not supply a type and the file exists,
    map is assumed (see the -help output and below for some exceptions to
-   this). The "snap:" setting applies the [573]-snapfb option with
+   this). The "snap:" setting applies the [582]-snapfb option with
    "file:" type reading (this is useful for exporting webcams or TV tuner
-   video; see [574]the next FAQ for more info).
+   video; see [583]the next FAQ for more info).
 
    Also, if the string is of the form "setup:cmd" then cmd is run and the
    first line of its output retrieved and used as the rawfb string. This
@@ -5113,7 +5144,7 @@ ied)
    screen to either shm or a mapped file. The format of these is XWD and
    so the initial header should be skipped. BTW, since XWD is not
    strictly RGB the view will only be approximate, but usable. Of course
-   for the case of Xvfb x11vnc can poll it much better via the [575]X
+   for the case of Xvfb x11vnc can poll it much better via the [584]X
    API, but you get the idea.
 
    By default in -rawfb mode x11vnc will actually close any X display it
@@ -5142,13 +5173,13 @@ ied)
    tty1-tty6), or X graphical display (usually starting at tty7). In
    addition to text console may be other graphical ones may be viewed and
    interacted with, e.g. DirectFB or SVGAlib apps, VMWare non-X
-   fullscreen, or [576]Qt-embedded apps (PDAs/Handhelds). By default the
+   fullscreen, or [585]Qt-embedded apps (PDAs/Handhelds). By default the
    pipeinput mechanisms UINPUT and CONSOLE (keystrokes only) are
    automatically attempted in this mode under "-rawfb console".
 
    The Video4Linux Capture device, /dev/video0, etc is either a Webcam or
    a TV capture device and needs to have its driver enabled in the
-   kernel. See [577]this FAQ for details. If specified via "-rawfb Video"
+   kernel. See [586]this FAQ for details. If specified via "-rawfb Video"
    then the pipeinput method "VID" is applied (it lets you change video
    parameters dynamically via keystrokes).
 
@@ -5156,10 +5187,10 @@ ied)
    also useful in testing.
 
 
-   All of the above [578]-rawfb options are just for viewing the raw
+   All of the above [587]-rawfb options are just for viewing the raw
    framebuffer (although some of the aliases do imply keystroke and mouse
    pipeinput methods). That may be enough for certain applications of
-   this feature (e.g. suppose a [579]video camera mapped its framebuffer
+   this feature (e.g. suppose a [588]video camera mapped its framebuffer
    into memory and you just wanted to look at it via VNC).
    To handle the pointer and keyboard input from the viewer users the
    "-pipeinput cmd" option was added to indicate a helper program to
@@ -5197,7 +5228,7 @@ ied)
    keystrokes into the Linux console (e.g. the virtual consoles:
    /dev/tty1, /dev/tty2, etc) in x11vnc/misc/vcinject.pl. It is based on
    the vncterm/LinuxVNC.c program also in the libvncserver CVS. So to
-   view and interact with VC #2 (assuming it is the [580]active VC) one
+   view and interact with VC #2 (assuming it is the [589]active VC) one
    can run something like:
   x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
 
@@ -5252,7 +5283,7 @@ ied)
    better to use the more accurate and faster LinuxVNC program. The
    advantage x11vnc -rawfb might have is that it can allow interaction
    with a non-text application, e.g. one based on SVGAlib or
-   [581]Qt-embedded Also, for example the [582]VMWare Fullscreen mode is
+   [590]Qt-embedded Also, for example the [591]VMWare Fullscreen mode is
    actually viewable under -rawfb and can be interacted with if uinput is
    enabled.
 
@@ -5272,9 +5303,9 @@ ied)
    Q-93: Can I export via VNC a Webcam or TV tuner framebuffer using
    x11vnc?
 
-   Yes, this is possible to some degree with the [583]-rawfb option.
+   Yes, this is possible to some degree with the [592]-rawfb option.
    There is no X11 involved: snapshots from the video capture device are
-   used for the screen image data. See the [584]previous FAQ on -rawfb
+   used for the screen image data. See the [593]previous FAQ on -rawfb
    for background. For best results, use x11vnc version 0.8.1 or later.
 
    Roughly, one would do something like this:
@@ -5286,7 +5317,7 @@ ied)
    snapshot to a file that you point -rawfb to; ask me if it is not clear
    what to do).
 
-   The "snap:" enforces [585]-snapfb mode which appears to be necessary.
+   The "snap:" enforces [594]-snapfb mode which appears to be necessary.
    The read pointer for video capture devices cannot be repositioned
    (which would be needed for scanline polling), but you can read a full
    frame of data from the device.
@@ -5308,7 +5339,7 @@ ied)
 
    Many video4linux drivers tend to set the framebuffer to be 24bpp (as
    opposed to 32bpp). Since this can cause problems with VNC viewers,
-   etc, the [586]-24to32 option will be automatically imposed when in
+   etc, the [595]-24to32 option will be automatically imposed when in
    24bpp.
 
    Note that by its very nature, video capture involves rapid change in
@@ -5316,7 +5347,7 @@ ied)
    wavering in brightness is always happening. This can lead to much
    network bandwidth consumption for the VNC traffic and also local CPU
    and I/O resource usage. You may want to experiment with "dialing down"
-   the framerate via the [587]-wait, [588]-slow_fb, or [589]-defer
+   the framerate via the [596]-wait, [597]-slow_fb, or [598]-defer
    options. Decreasing the window size and bpp also helps.
 
 
@@ -5405,7 +5436,7 @@ ied)
          format to HI240, RGB565, RGB24, RGB32, RGB555, and
          GREY respectively. See -rawfb video for details.
 
-   See also the [590]-freqtab option to supply your own xawtv channel to
+   See also the [599]-freqtab option to supply your own xawtv channel to
    frequency mappings for your country (only ntsc-cable-us is built into
    x11vnc).
 
@@ -5414,7 +5445,7 @@ ied)
    running on my handheld or PC using the Linux console framebuffer (i.e.
    not X11)?
 
-   Yes, the basic method for this is the [591]-rawfb scheme where the
+   Yes, the basic method for this is the [600]-rawfb scheme where the
    Linux console framebuffer (usually /dev/fb0) is polled and the uinput
    driver is used to inject keystrokes and mouse input. Often you will
    just have to type:
@@ -5427,7 +5458,7 @@ ied)
   x11vnc -rawfb /dev/fb0@640x480x16
 
    Also, to force usage of the uinput injection method use "-pipeinput
-   UINPUT". See the [592]-pipeinput description for tunable parameters,
+   UINPUT". See the [601]-pipeinput description for tunable parameters,
    etc.
 
    One problem with the x11vnc uinput scheme is that it cannot guess the
@@ -5443,7 +5474,7 @@ ied)
    Even with the correct acceleration setting there is stil some drift
    (probably because of the mouse threshold where the acceleration kicks
    in) and so x11vnc needs to reposition the cursor from 0,0 about 5
-   times a second. See the [593]-pipeinput UINPUT option for tuning
+   times a second. See the [602]-pipeinput UINPUT option for tuning
    parameters that can be set (there are some experimental thresh=N
    tuning parameters as well)
 
@@ -5473,7 +5504,7 @@ ied)
    Q-95: Now that non-X11 devices can be exported via VNC using x11vnc,
    can I build it with no dependencies on X11 header files and libraries?
 
-   Yes, as of Jul/2006 x11vnc enables building for [594]-rawfb only
+   Yes, as of Jul/2006 x11vnc enables building for [603]-rawfb only
    support. Just do something like when building:
   ./configure --without-x    (plus any other flags)
   make
@@ -5489,7 +5520,7 @@ ied)
 
    Yes, it is possible with a number of tools that record VNC and
    transform it to swf format or others. One such popular tool is
-   [595]pyvnc2swf. There are a number of [596]tutorials on how to do
+   [604]pyvnc2swf. There are a number of [605]tutorials on how to do
    this. Another option is to use the vnc2mpg that comes in the
    LibVNCServer package.
    An important thing to remember when doing this is that tuning
@@ -5505,11 +5536,11 @@ ied)
    As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol.
    Furthermore, x11vnc is able to hold the PRIMARY and CLIPBOARD
    selection (Xvnc does not seem to do this). If you don't want the
-   Clipboard/Selection exchanged use the [597]-nosel option. If you don't
+   Clipboard/Selection exchanged use the [606]-nosel option. If you don't
    want the PRIMARY selection to be polled for changes use the
-   [598]-noprimary option. (with a similar thing for CLIPBOARD). You can
-   also fine-tune it a bit with the [599]-seldir dir option and also
-   [600]-input.
+   [607]-noprimary option. (with a similar thing for CLIPBOARD). You can
+   also fine-tune it a bit with the [608]-seldir dir option and also
+   [609]-input.
 
    You may need to watch out for desktop utilities such as KDE's
    "Klipper" that do odd things with the selection, clipboard, and
@@ -5524,7 +5555,7 @@ ied)
    (and Windows viewers only support filetransfer it appears).
 
    TightVNC file transfer is on by default, if you want to disable it use
-   the [601]-nofilexfer option. UltraVNC file transfer is currently off
+   the [610]-nofilexfer option. UltraVNC file transfer is currently off
    by default, to enable it use something like "-rfbversion 3.6
    -permitfiletransfer"
    options (UltraVNC incorrectly uses the RFB protocol version to
@@ -5636,9 +5667,9 @@ or:
    in Solaris, see Xserver(1) for how to turn it on via +kb), and so you
    won't hear them if the extension is not present.
 
-   If you don't want to hear the beeps use the [602]-nobell option. If
+   If you don't want to hear the beeps use the [611]-nobell option. If
    you want to hear the audio from the remote applications, consider
-   trying a [603]redirector such as esd.
+   trying a [612]redirector such as esd.
 
 
 
@@ -5667,597 +5698,606 @@ References
   10. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
   11. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
   12. http://www.karlrunge.com/x11vnc/index.html#faq-video
-  13. http://www.karlrunge.com/x11vnc/index.html#faq
-  14. http://www.karlrunge.com/x11vnc/disclaimer.html
-  15. http://www.karlrunge.com/x11vnc/index.html#contact
-  16. http://www.realvnc.com/
-  17. http://www.tightvnc.com/
-  18. http://www.ultravnc.com/
-  19. http://www.redstonesoftware.com/vnc.html
-  20. http://www.karlrunge.com/x11vnc/index.html#downloading
-  21. http://www.tightvnc.com/download.html
-  22. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
-  23. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
-  24. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
-  25. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
-  26. http://www.sun.com/software/solaris/freeware/
-  27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
-  28. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
-  29. http://www.karlrunge.com/x11vnc/index.html#faq-service
-  30. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
-  31. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file
-  32. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+  13. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
+  14. http://www.karlrunge.com/x11vnc/index.html#faq
+  15. http://www.karlrunge.com/x11vnc/disclaimer.html
+  16. http://www.karlrunge.com/x11vnc/index.html#contact
+  17. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+  18. http://www.realvnc.com/
+  19. http://www.tightvnc.com/
+  20. http://www.ultravnc.com/
+  21. http://www.redstonesoftware.com/vnc.html
+  22. http://www.karlrunge.com/x11vnc/index.html#downloading
+  23. http://www.tightvnc.com/download.html
+  24. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+  25. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
+  26. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
+  27. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
+  28. http://www.sun.com/software/solaris/freeware/
+  29. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+  30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+  31. http://www.karlrunge.com/x11vnc/index.html#faq-service
+  32. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
   33. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file
-  34. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
-  35. http://www.karlrunge.com/x11vnc/index.html#tightvnc_via
-  36. http://www.karlrunge.com/x11vnc/chainingssh.html
-  37. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
-  38. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
-  39. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
-  40. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
-  41. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
-  42. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
-  43. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
-  44. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
-  45. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
-  46. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
-  47. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
-  48. http://www.stunnel.org/
-  49. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
-  50. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
-  51. http://sourceforge.net/projects/libvncserver/
-  52. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=431725
-  53. http://sourceforge.net/project/shownotes.php?release_id=431725&group_id=32584
-  54. http://www.karlrunge.com/x11vnc/x11vnc-0.8.3.tar.gz
-  55. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
-  56. http://www.tightvnc.com/download.html
-  57. http://www.realvnc.com/download-free.html
-  58. http://sourceforge.net/projects/cotvnc/
-  59. http://www.ultravnc.com/
-  60. http://www.karlrunge.com/x11vnc/rx11vnc
-  61. http://www.karlrunge.com/x11vnc/rx11vnc.pl
-  62. http://www.sunfreeware.com/
-  63. http://www.karlrunge.com/x11vnc/bins
-  64. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
-  65. http://www.karlrunge.com/x11vnc/miscbuild.html
-  66. ftp://ftp.uu.net/graphics/jpeg/
-  67. http://www.gzip.org/zlib/
-  68. http://www.sunfreeware.com/
-  69. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
-  70. http://www.karlrunge.com/x11vnc/x11vnc-0.8.3.tar.gz
-  71. http://www.karlrunge.com/x11vnc/bins
-  72. mailto:x11vnc-beta@karlrunge.com
-  73. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
-  74. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
-  75. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
-  76. http://www.karlrunge.com/x11vnc/enhanced_tight_vncviewer.html
-  77. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
-  78. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
-  79. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
-  80. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
-  81. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
-  82. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkdb
-  83. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
-  84. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allowedcmds
-  85. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocmds
-  86. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-env
-  87. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allinput
-  88. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
-  89. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-license
-  90. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
-  91. http://www.openssl.org/
-  92. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
-  93. http://www.stunnel.org/
-  94. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
-  95. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
-  96. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
-  97. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
-  98. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
-  99. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 100. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 101. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 102. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 103. http://www.karlrunge.com/x11vnc/prevrels.html
- 104. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 105. http://www.tightvnc.com/
- 106. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 107. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 108. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 109. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
- 110. http://wwws.sun.com/sunray/index.html
- 111. http://www.karlrunge.com/x11vnc/sunray.html
- 112. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 113. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 114. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 115. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 116. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 117. http://www.karlrunge.com/x11vnc/index.html#faq-sound
- 118. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 119. mailto:xvml@karlrunge.com
- 120. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 121. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
- 122. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 123. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest
- 124. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
- 125. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
- 126. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
- 127. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
- 128. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
- 129. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
- 130. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
- 131. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
- 132. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations
- 133. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
- 134. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
- 135. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 136. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 137. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
- 138. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
- 139. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
- 140. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 141. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 142. http://www.karlrunge.com/x11vnc/index.html#faq-sunrays
- 143. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
- 144. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
- 145. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 146. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho
- 147. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 148. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd
- 149. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 150. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
- 151. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
- 152. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 153. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
- 154. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
- 155. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
- 156. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 157. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
- 158. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
- 159. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
- 160. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
- 161. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
- 162. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
- 163. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
- 164. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 165. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy
- 166. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
- 167. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-ca
- 168. http://www.karlrunge.com/x11vnc/index.html#faq-service
- 169. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 170. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 171. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 172. http://www.karlrunge.com/x11vnc/index.html#faq-loop
- 173. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
- 174. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
- 175. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 176. http://www.karlrunge.com/x11vnc/index.html#faq-headless
- 177. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 178. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
- 179. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
- 180. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
- 181. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
- 182. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 183. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 184. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 185. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
- 186. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
- 187. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 188. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
- 189. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
- 190. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
- 191. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
- 192. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 193. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
- 194. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 195. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
- 196. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
- 197. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
- 198. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
- 199. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
- 200. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock
- 201. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
- 202. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 203. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 204. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
- 205. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
- 206. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
- 207. http://www.karlrunge.com/x11vnc/index.html#faq-rotate
- 208. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
- 209. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 210. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
- 211. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 212. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 213. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 214. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
- 215. http://www.karlrunge.com/x11vnc/index.html#faq-no-x11
- 216. http://www.karlrunge.com/x11vnc/index.html#faq-record-swf
- 217. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
- 218. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
- 219. http://www.karlrunge.com/x11vnc/index.html#faq-sound
- 220. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
- 221. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 223. http://www.tldp.org/HOWTO/Remote-X-Apps.html
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 225. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 227. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 228. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 229. http://www.karlrunge.com/x11vnc/index.html#building
- 230. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 231. http://packages.debian.org/x11vnc
- 232. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 233. http://dag.wieers.com/packages/x11vnc/
- 234. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html
- 235. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
- 236. http://www.sunfreeware.com/
- 237. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
- 238. http://www.freshports.org/net/x11vnc
- 239. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html
- 240. http://pkgsrc.se/x11/x11vnc
- 241. http://mike.saunby.net/770/x11vnc/
- 242. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc
- 243. http://www.focv.com/ipkg/
- 244. http://www.karlrunge.com/x11vnc/bins
- 245. http://www.tightvnc.com/download.html
- 246. http://www.realvnc.com/download-free.html
- 247. http://sourceforge.net/projects/cotvnc/
- 248. http://www.ultravnc.com/
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 251. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 255. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 257. http://fredrik.hubbe.net/x2vnc.html
- 258. http://www.hubbe.net/~hubbe/win2vnc.html
- 259. http://www.deboer.gmxhome.de/
- 260. http://sourceforge.net/projects/win2vnc/
- 261. http://fredrik.hubbe.net/x2vnc.html
- 262. http://freshmeat.net/projects/x2x/
- 263. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 264. http://zapek.com/software/zvnc/
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 269. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+  34. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+  35. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file
+  36. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+  37. http://www.karlrunge.com/x11vnc/index.html#tightvnc_via
+  38. http://www.karlrunge.com/x11vnc/chainingssh.html
+  39. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+  40. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+  41. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+  42. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+  43. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+  44. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+  45. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+  46. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+  47. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
+  48. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+  49. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
+  50. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+  51. http://www.stunnel.org/
+  52. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+  53. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+  54. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+  55. http://sourceforge.net/projects/libvncserver/
+  56. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=431725
+  57. http://sourceforge.net/project/shownotes.php?release_id=431725&group_id=32584
+  58. http://www.karlrunge.com/x11vnc/x11vnc-0.8.3.tar.gz
+  59. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
+  60. http://www.tightvnc.com/download.html
+  61. http://www.realvnc.com/download-free.html
+  62. http://sourceforge.net/projects/cotvnc/
+  63. http://www.ultravnc.com/
+  64. http://www.karlrunge.com/x11vnc/rx11vnc
+  65. http://www.karlrunge.com/x11vnc/rx11vnc.pl
+  66. http://www.sunfreeware.com/
+  67. http://www.karlrunge.com/x11vnc/bins
+  68. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+  69. http://www.karlrunge.com/x11vnc/miscbuild.html
+  70. ftp://ftp.uu.net/graphics/jpeg/
+  71. http://www.gzip.org/zlib/
+  72. http://www.sunfreeware.com/
+  73. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
+  74. http://www.karlrunge.com/x11vnc/x11vnc-0.8.3.tar.gz
+  75. http://www.karlrunge.com/x11vnc/bins
+  76. mailto:x11vnc-beta@karlrunge.com
+  77. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+  78. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+  79. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+  80. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+  81. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+  82. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+  83. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+  84. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+  85. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+  86. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkdb
+  87. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
+  88. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allowedcmds
+  89. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocmds
+  90. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-env
+  91. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allinput
+  92. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+  93. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-license
+  94. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+  95. http://www.openssl.org/
+  96. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+  97. http://www.stunnel.org/
+  98. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
+  99. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 100. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+ 101. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 102. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 103. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 104. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 105. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 106. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 107. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
+ 108. http://www.karlrunge.com/x11vnc/prevrels.html
+ 109. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 110. http://www.tightvnc.com/
+ 111. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 112. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 113. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 114. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
+ 115. http://wwws.sun.com/sunray/index.html
+ 116. http://www.karlrunge.com/x11vnc/sunray.html
+ 117. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 118. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 119. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 120. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 121. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 122. http://www.karlrunge.com/x11vnc/index.html#faq-sound
+ 123. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 124. mailto:xvml@karlrunge.com
+ 125. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 126. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
+ 127. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 128. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest
+ 129. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
+ 130. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
+ 131. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
+ 132. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
+ 133. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
+ 134. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 135. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
+ 136. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
+ 137. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations
+ 138. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
+ 139. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
+ 140. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 141. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 142. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
+ 143. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
+ 144. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
+ 145. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 146. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 147. http://www.karlrunge.com/x11vnc/index.html#faq-sunrays
+ 148. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
+ 149. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
+ 150. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 151. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho
+ 152. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 153. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd
+ 154. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 155. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
+ 156. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
+ 157. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 158. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
+ 159. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
+ 160. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
+ 161. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 162. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
+ 163. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
+ 164. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
+ 165. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
+ 166. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
+ 167. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 168. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+ 169. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 170. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy
+ 171. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
+ 172. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-ca
+ 173. http://www.karlrunge.com/x11vnc/index.html#faq-service
+ 174. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 175. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 176. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 177. http://www.karlrunge.com/x11vnc/index.html#faq-loop
+ 178. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
+ 179. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
+ 180. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 181. http://www.karlrunge.com/x11vnc/index.html#faq-headless
+ 182. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 183. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
+ 184. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
+ 185. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
+ 186. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
+ 187. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 188. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 189. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 190. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
+ 191. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
+ 192. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 193. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
+ 194. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
+ 195. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
+ 196. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
+ 197. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 198. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
+ 199. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 200. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
+ 201. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
+ 202. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
+ 203. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
+ 204. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
+ 205. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock
+ 206. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
+ 207. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 208. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 209. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
+ 210. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
+ 211. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
+ 212. http://www.karlrunge.com/x11vnc/index.html#faq-rotate
+ 213. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
+ 214. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 215. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
+ 216. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 217. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 218. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 219. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
+ 220. http://www.karlrunge.com/x11vnc/index.html#faq-no-x11
+ 221. http://www.karlrunge.com/x11vnc/index.html#faq-record-swf
+ 222. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
+ 223. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
+ 224. http://www.karlrunge.com/x11vnc/index.html#faq-sound
+ 225. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
+ 226. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 228. http://www.tldp.org/HOWTO/Remote-X-Apps.html
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 230. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 232. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 233. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 234. http://www.karlrunge.com/x11vnc/index.html#building
+ 235. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 236. http://packages.debian.org/x11vnc
+ 237. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 238. http://dag.wieers.com/packages/x11vnc/
+ 239. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html
+ 240. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
+ 241. http://www.sunfreeware.com/
+ 242. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
+ 243. http://www.freshports.org/net/x11vnc
+ 244. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html
+ 245. http://pkgsrc.se/x11/x11vnc
+ 246. http://mike.saunby.net/770/x11vnc/
+ 247. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc
+ 248. http://www.focv.com/ipkg/
+ 249. http://www.karlrunge.com/x11vnc/bins
+ 250. http://www.tightvnc.com/download.html
+ 251. http://www.realvnc.com/download-free.html
+ 252. http://sourceforge.net/projects/cotvnc/
+ 253. http://www.ultravnc.com/
+ 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 256. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 260. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 262. http://fredrik.hubbe.net/x2vnc.html
+ 263. http://www.hubbe.net/~hubbe/win2vnc.html
+ 264. http://www.deboer.gmxhome.de/
+ 265. http://sourceforge.net/projects/win2vnc/
+ 266. http://fredrik.hubbe.net/x2vnc.html
+ 267. http://freshmeat.net/projects/x2x/
+ 268. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 269. http://zapek.com/software/zvnc/
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 274. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
  276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
  278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 280. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 288. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 289. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 290. http://wwws.sun.com/sunray/index.html
- 291. http://www.karlrunge.com/x11vnc/sunray.html
- 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 303. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
- 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 317. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 318. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 285. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 293. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 294. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 295. http://wwws.sun.com/sunray/index.html
+ 296. http://www.karlrunge.com/x11vnc/sunray.html
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 308. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
  322. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 324. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 325. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 328. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 329. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 323. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel
+ 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 327. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 329. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 330. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
  331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
  332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 338. ftp://ftp.x.org/
- 339. http://www.karlrunge.com/x11vnc/dtVncPopup
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 343. http://www.karlrunge.com/x11vnc/blockdpy.c
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 333. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 334. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 343. ftp://ftp.x.org/
+ 344. http://www.karlrunge.com/x11vnc/dtVncPopup
  345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 348. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 349. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 353. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
- 354. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 356. http://www.stunnel.org/
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
- 360. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
- 361. http://www.stunnel.org/
- 362. http://www.karlrunge.com/x11vnc/ssl.html
- 363. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
- 364. http://www.karlrunge.com/x11vnc/ssl.html
- 365. http://www.securityfocus.com/infocus/1677
- 366. http://www.karlrunge.com/x11vnc/ssl.html
- 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 368. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 375. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
- 376. http://www.karlrunge.com/x11vnc/enhanced_tight_vncviewer.html
- 377. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 348. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 353. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 354. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 355. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 356. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 360. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
+ 361. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 363. http://www.stunnel.org/
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
+ 367. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+ 368. http://www.stunnel.org/
+ 369. http://www.karlrunge.com/x11vnc/ssl.html
+ 370. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+ 371. http://www.karlrunge.com/x11vnc/ssl.html
+ 372. http://www.securityfocus.com/infocus/1677
+ 373. http://www.karlrunge.com/x11vnc/ssl.html
+ 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 375. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
  378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 380. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
  381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 382. http://www.openssl.org/
- 383. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 384. http://www.stunnel.org/
- 385. http://www.karlrunge.com/x11vnc/ssl.html
- 386. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
- 387. http://www.karlrunge.com/x11vnc/ssl.html
- 388. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 392. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
- 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 394. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
- 395. http://www.karlrunge.com/x11vnc/ssl_vncviewer
- 396. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 397. http://www.karlrunge.com/x11vnc/ssl.html
- 398. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
- 399. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 400. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 401. http://www.karlrunge.com/x11vnc/ssl.html
- 402. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 403. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 404. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 405. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 407. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 408. http://www.jirka.org/gdm-documentation/x241.html
- 409. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 411. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 382. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+ 383. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 384. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 387. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 389. http://www.openssl.org/
+ 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 391. http://www.stunnel.org/
+ 392. http://www.karlrunge.com/x11vnc/ssl.html
+ 393. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+ 394. http://www.karlrunge.com/x11vnc/ssl.html
+ 395. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 399. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
+ 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 401. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 402. http://www.karlrunge.com/x11vnc/ssl_vncviewer
+ 403. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 404. http://www.karlrunge.com/x11vnc/ssl.html
+ 405. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 406. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer
+ 407. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 408. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 409. http://www.karlrunge.com/x11vnc/ssl.html
+ 410. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 411. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 412. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 413. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
  414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 415. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 416. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 419. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd
- 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 422. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 424. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
- 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 432. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 433. http://www.karlrunge.com/x11vnc/Xdummy
- 434. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 435. http://www.karlrunge.com/x11vnc/shm_clear
- 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 438. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
- 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 450. http://www.tightvnc.com/
- 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
- 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 465. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 466. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 470. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 476. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 477. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 478. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 479. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 483. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 487. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 495. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 496. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 497. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 503. http://www.tightvnc.com/
- 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
- 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 512. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 513. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 520. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 522. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 536. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 415. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 416. http://www.jirka.org/gdm-documentation/x241.html
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 419. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 423. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 424. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 427. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd
+ 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 430. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 432. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+ 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 440. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 441. http://www.karlrunge.com/x11vnc/Xdummy
+ 442. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 443. http://www.karlrunge.com/x11vnc/shm_clear
+ 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 446. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
+ 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 458. http://www.tightvnc.com/
+ 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
+ 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 465. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 474. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 478. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 484. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 485. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 486. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 487. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 491. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 495. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 503. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 504. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 505. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 511. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 512. http://www.tightvnc.com/
+ 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 521. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 522. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 529. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 531. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
  538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
  540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
- 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
- 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
- 545. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 547. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 556. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 560. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
- 566. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 567. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 568. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 574. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 575. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 576. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
- 577. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 579. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 580. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 581. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
- 582. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 584. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
- 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
- 591. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 595. http://www.unixuser.org/~euske/vnc2swf/
- 596. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
- 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
- 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 603. http://www.karlrunge.com/x11vnc/index.html#faq-sound
+ 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 545. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
+ 554. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 556. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 565. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 569. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
+ 575. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 576. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 577. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 583. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 584. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 585. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
+ 586. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 588. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 589. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 590. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
+ 591. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 593. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
+ 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
+ 600. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 604. http://www.unixuser.org/~euske/vnc2swf/
+ 605. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
+ 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
+ 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 612. http://www.karlrunge.com/x11vnc/index.html#faq-sound
 	
 =======================================================================
 http://www.karlrunge.com/x11vnc/chainingssh.html:
@@ -7423,6 +7463,305 @@ References
   14. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_ssl
 	
 =======================================================================
+http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html:
+
+
+     _________________________________________________________________
+
+Enhanced TightVNC Viewer
+
+   The Enhanced TightVNC Viewer package is an attempt to add some patches
+   to the long neglected Unix Tight VNC Viewer. It also adds a simple GUI
+   for Windows that automatically starts up a STUNNEL SSL tunnel for SSL
+   connections to [1]x11vnc (or any other VNC Server also running STUNNEL
+   at their end), and then launches the Windows Tight VNC Viewer. A
+   wrapper and gui for SSH connections is also provided.
+
+   Patches were created for the TightVNC 1.3dev7 vnc_unixsrc tree to add
+   these features:
+     * SSL support for connections using the co-bundled stunnel program.
+     * Automatic SSH connections from the GUI (system ssh is used on
+       Unix; co-bundled plink is used on Windows)
+     * rfbNewFBSize VNC support on Unix (screen resizing)
+     * cursor alphablending with x11vnc at 32bpp (-alpha option)
+     * xgrabserver support for fullscreen mode, for old window managers
+       (-grab option).
+
+   The Viewer SSL support is done via a wrapper script
+   (bin/ssl_tightvncviewer) that starts up the STUNNEL tunnel first and
+   then starts the Tight VNC viewer pointed at that tunnel. The
+   bin/ssl_vnc_gui program is a simple gui front-end to that script. See
+   [2]this FAQ for more details on SSL tunnelling.
+
+   The rfbNewFBSize support allows the enhanced TightVNC Unix viewer to
+   resize when the server does (e.g. "x11vnc -R scale=3/4" remote control
+   command).
+
+   The cursor alphablending is [3]described here.
+
+   For Windows SSL Viewer support is provided by a simple program
+   Windows/ssl_tightvncviewer.exe that prompts for the VNC display and
+   then starts up STUNNEL followed by the Stock TightVNC Windows Viewer.
+   When the connection is finished, you will need to manually stop the
+   STUNNEL program by clicking on the icon in the System Tray (sorry
+   about that, I still don't know how to script-hack on Windows).
+
+   Hopefully these binaries will make it convenient for people to help
+   test and use the [4]built-in SSL support in x11vnc. Extra testing of
+   this feature is much appreciated! Thanks.
+
+   For the heck of it, some wrapper scripts and gui interfaces where also
+   added to automatically set up a SSH tunnel instead of STUNNEL SSL.
+   This works on Unix and Windows (and more smoothly on Unix of course).
+
+   This package can be downloaded here:
+    [5]enhanced_tightvnc_viewer-1.0.zip                 All Unix and Windows bi
+naries and source.  (~5MB)
+    [6]enhanced_tightvnc_viewer-1.0.tar.gz              All Unix and Windows bi
+naries and source.  (~5MB)
+    [7]enhanced_tightvnc_viewer-1.0.zip                 All Unix and Windows bi
+naries and source and full archives in zip dir. (~8MB)
+    [8]enhanced_tightvnc_viewer_windows_only-1.0.zip    Only the Windows binari
+es. (~3MB)
+    [9]enhanced_tightvnc_viewer_no_windows-1.0.tar.gz   No Windows binaries. (~
+3MB)
+
+   Sorry for the inconvenience of lumping all the Unix binaries and
+   source together in one archive. They will be split up if there is
+   sufficient interest.
+
+   Current Unix binaries in the above archives:
+    FreeBSD.i386
+    Linux.alpha
+    Linux.i686
+    Linux.ppc64
+    Linux.x86_64
+    NetBSD.i386
+    OpenBSD.i386
+    SunOS.sun4u
+
+   You can also run the included build.unix script to try to
+   automatically build the binaries if your OS is not in the above list
+   or the included binary does not run properly on your system. Let me
+   know how that goes.
+
+   IMPORTANT: there may be restrictions for you do download the above
+   because of cryptographic software they contain. Please check out your
+   situation and information at the following and related sites:
+        [10]http://www.tightvnc.com
+        [11]http://www.realvnc.com
+        [12]http://www.stunnel.org
+        [13]http://www.openssl.org
+        [14]http://www.chiark.greenend.org.uk/~sgtatham/putty/
+
+   It is my belief (but I cannot be sure) that the bundle.
+   enhanced_tightvnc_viewer_no_windows-1.0.tar.gz contains no
+   cryptographic software (again, if your situation warrants, you will
+   need to check). The "no_windows" tarball only contains software (from
+   the above URL's and elsewhere) that will use cryptographic software
+   (libraries) already installed on your system.
+
+   Here is the toplevel README from the package:
+
+                  Enhanced TightVNC Viewer package
+
+Copyright (c) Karl J. Runge
+All rights reserved.
+
+These packages provide 1) An enhanced TightVNC Viewer on Unix, 2) Binaries
+for many Operating Systems, including Windows, for your convenience,
+3) Wrapper scripts and etc. for gluing them all together.
+
+One can straight-forwardly download all of the components and get them
+to work together by oneself: this package is mostly for your convenience
+to combine and wrap up freely available software.
+
+Bundled software co-shipped in this package is copyright and licensed
+by others.  See these sites and related ones for more information:
+
+        http://www.tightvnc.com
+        http://www.realvnc.com
+        http://www.stunnel.org
+        http://www.openssl.org
+        http://www.chiark.greenend.org.uk/~sgtatham/putty/
+
+Some of the Windows binaries included contain cryptographic software
+that you may not be allowed to download and/or use.  Please check your
+situation first before downloading.  The Unix programs do not contain
+cryptographic software, but rather will make use of cryptographic
+libraries that need to be installed on your Unix system.
+
+All work by Karl J. Runge in this package is Copyright (c) Karl J. Runge
+and is licensed under the GPL as described in the file COPYING in this
+directory.
+
+All the files and information in this package are provided "AS IS"
+without any warranty.  Use them at your own risk.
+
+
+-----------------------------------------------------------------------------
+This package contains a convenient collection of enhanced TightVNC viewers
+and stunnel binaries for different flavors of Unix and wrapper scripts,
+etc to glue them together.
+
+Also, a Windows SSL wrapper for a co-bundled TightVNC binary and other
+utilities is provided.  (ssl_tightvncviewer.exe: look in the Windows
+subdirectory).
+
+The enhanced TightVNC viewer features are:
+
+        - SSL support for connections using the co-bundled stunnel program.
+
+        - Automatic SSH connections from the GUI (ssh must already be
+          installed on Unix; co-bundled plink is used on Windows)
+
+        - rfbNewFBSize VNC support on Unix (screen resizing)
+
+        - cursor alphablending with x11vnc at 32bpp (-alpha option)
+
+        - xgrabserver support for fullscreen mode, for old window
+          managers (-grab option).
+
+(some of these are only available on Unix).
+
+Your package should have included binaries for many OS's: Linux, Solaris,
+FreeBSD, etc.  See the subdirectories of
+
+        ./bin
+
+for the ones that were shipped in this package, e.g. ./bin/Linux.i686
+Run "uname -sm" to see your OS+arch combination. (See the
+./bin/tightvncviewer -h output for how to override platform autodection
+via the UNAME env. var).
+
+
+If your OS/arch is not included, the script "build.unix" may be able to
+successfully build on for you and desposit the binaries down in ./bin/...
+using the included source code.
+
+You must run the build.unix script from this directory (that this toplevel
+README is in) and like this:
+
+        ./build.unix
+
+
+The wrapper scripts:
+
+        ./bin/ssl_tightvncviewer
+        ./bin/tightvncviewer
+
+are the main programs you will run and will try to autodetect your OS+arch
+combination and if binaries are present for it automatically use them.
+(if not found try the running the build.unix script).
+
+If you prefer a GUI to prompt for parameters and then start ssl_tightvncviewer
+run this this script:
+
+        ./bin/ssl_vnc_gui
+
+this is basically the same GUI that is run on Windows.
+
+
+Brief description of the subdirectories:
+
+        ./bin/util              some utility scripts, e.g. ssl_vncviewer
+                                and ssl_tightvncviewer.tcl
+
+        ./src                   source code and patches.
+        ./src/zips              zip files of source code and binaries.
+
+        ./src/vnc_unixsrc       unpacked tightvnc source code tree.
+        ./src/stunnel-4.14      unpacked stunnel source code tree.
+        ./src/patches           patches to TightVNC viewer for the new
+                                features on Unix (used by build.unix).
+        ./src/tmp               temporary build dir for build.unix
+                                (the last four are used by build.unix)
+
+
+        ./man                   man pages for TightVNC viewer and stunnel.
+
+        ./Windows               Stock TightVNC viewer and Stunnel, Openssl
+                                etc Windows binaries. ssl_tightvncviewer.exe
+                                is the program to run.
+
+Since they are large, depending on which package you use not all of the
+above may be present in your package.
+
+
+Examples:
+
+Use enhanced TightVNC unix viewer to connect to x11vnc via SSL:
+
+        ./bin/ssl_tightvncviewer   far-away.east:0
+
+        ./bin/tightvncviewer -ssl  far-away.east:0   (same)
+
+        ./bin/ssl_vnc_gui                            (start gui launcher)
+
+
+Use enhanced TightVNC unix viewer without SSL:
+
+        ./bin/tightvncviewer far-away.east:0
+
+
+Use SSL to connect to a x11vnc server, and also verify the server's
+identity using the SSL Certificate in the file ./x11vnc.pem:
+
+        ./bin/ssl_tightvncviewer -alpha -verify ./x11vnc.pem far-away.east:0
+
+(also turns on the viewer-side cursor alphablending hack).
+
+
+For more help on other options and usage patters run these:
+
+        ./bin/ssl_tightvncviewer -h
+        ./bin/tightvncviewer -h
+        ./bin/util/ssl_vncviewer -h
+
+See also:
+
+        http://www.karlrunge.com/x11vnc
+        http://www.karlrunge.com/x11vnc/#faq
+        x11vnc -h | more
+
+        http://www.stunnel.org
+        http://www.openssl.org
+        http://www.tightvnc.com
+        http://www.realvnc.com
+        http://www.chiark.greenend.org.uk/~sgtatham/putty/
+
+
+Windows:
+
+        A wrapper to create a STUNNEL tunnel and then launch the
+        Windows TightVNC viewer is provided in:
+
+                Windows/ssl_tightvncviewer.exe
+
+        Just launch it and fill in the remote VNC display.
+
+        On Windows you may need to terminate the STUNNEL process
+        from the System Tray if the tool cannot terminate it
+        by itself.
+
+References
+
+   1. http://www.karlrunge.com/x11vnc/index.html
+   2. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+   3. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+   4. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+   5. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer-1.0.zip
+   6. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer-1.0.tar.gz
+   7. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer_all-1.0.zip
+   8. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer_windows_only-1.0.zip
+   9. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer_no_windows-1.0.tar.gz
+  10. http://www.tightvnc.com/
+  11. http://www.realvnc.com/
+  12. http://www.stunnel.org/
+  13. http://www.openssl.org/
+  14. http://www.chiark.greenend.org.uk/~sgtatham/putty/
+	
+=======================================================================
 http://www.karlrunge.com/x11vnc/x11vnc_opts.html:
 
 
@@ -7433,7 +7772,7 @@ x11vnc: a VNC server for real X displays
    Here are all of x11vnc command line options:
 % x11vnc -opts      (see below for -help long descriptions)
 
-x11vnc: allow VNC connections to real X11 displays. 0.8.3 lastmod: 2006-07-28
+x11vnc: allow VNC connections to real X11 displays. 0.8.3 lastmod: 2006-07-30
 
 x11vnc options:
   -display disp            -auth file               -id windowid           
@@ -7532,7 +7871,7 @@ libvncserver-tight-extension options:
 
 % x11vnc -help
 
-x11vnc: allow VNC connections to real X11 displays. 0.8.3 lastmod: 2006-07-28
+x11vnc: allow VNC connections to real X11 displays. 0.8.3 lastmod: 2006-07-30
 
 (type "x11vnc -opts" to just list the options.)
 
diff --git a/x11vnc/pointer.c b/x11vnc/pointer.c
index 700fda0..0fa2919 100644
--- a/x11vnc/pointer.c
+++ b/x11vnc/pointer.c
@@ -14,6 +14,7 @@
 #include "v4l.h"
 #include "linuxfb.h"
 #include "uinput.h"
+#include "scan.h"
 
 int pointer_queued_sent = 0;
 
diff --git a/x11vnc/scan.c b/x11vnc/scan.c
index 313f53e..96d0eaa 100644
--- a/x11vnc/scan.c
+++ b/x11vnc/scan.c
@@ -32,7 +32,9 @@ int copy_snap(void);
 void nap_sleep(int ms, int split);
 void set_offset(void);
 int scan_for_updates(int count_only);
-
+void rotate_curs(char *dst_0, char *src_0, int Dx, int Dy, int Bpp);
+void rotate_coords(int x, int y, int *xo, int *yo, int dxi, int dyi);
+void rotate_coords_inverse(int x, int y, int *xo, int *yo, int dxi, int dyi);
 
 static void set_fs_factor(int max);
 static char *flip_ximage_byte_order(XImage *xim);
diff --git a/x11vnc/scan.h b/x11vnc/scan.h
index f2765e1..98bd148 100644
--- a/x11vnc/scan.h
+++ b/x11vnc/scan.h
@@ -21,5 +21,8 @@ extern int copy_snap(void);
 extern void nap_sleep(int ms, int split);
 extern void set_offset(void);
 extern int scan_for_updates(int count_only);
+extern void rotate_curs(char *dst_0, char *src_0, int Dx, int Dy, int Bpp);
+extern void rotate_coords(int x, int y, int *xo, int *yo, int dxi, int dyi);
+extern void rotate_coords_inverse(int x, int y, int *xo, int *yo, int dxi, int dyi);
 
 #endif /* _X11VNC_SCAN_H */
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index cf025b1..be5b72c 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -2,7 +2,7 @@
 .TH X11VNC "1" "July 2006" "x11vnc " "User Commands"
 .SH NAME
 x11vnc - allow VNC connections to real X11 displays
-         version: 0.8.3, lastmod: 2006-07-28
+         version: 0.8.3, lastmod: 2006-07-30
 .SH SYNOPSIS
 .B x11vnc
 [OPTION]...
diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c
index b45e17e..fffc53b 100644
--- a/x11vnc/x11vnc_defs.c
+++ b/x11vnc/x11vnc_defs.c
@@ -15,7 +15,7 @@ int xtrap_base_event_type = 0;
 int xdamage_base_event_type = 0;
 
 /*               date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.8.3 lastmod: 2006-07-28";
+char lastmod[] = "0.8.3 lastmod: 2006-07-30";
 
 /* X display info */