fix some non-gcc compiler warnings and signals in x11vnc

8 files changed, 1210 insertions, 890 deletions

diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index d6343ed..8acda7c 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,3 +1,8 @@
+2006-02-20  Karl Runge <[email protected]>
+	* x11vnc: add SIGINT SIGQUIT handling for run_user_command(),
+	  set some signal handlers to SIG_DLF for forked children, 
+	  put a timeout on port 113 connection to viewer machine.
+
 2006-02-06  Karl Runge <[email protected]>
 	* x11vnc: fix AIX build wrt h_errno.
 
diff --git a/x11vnc/README b/x11vnc/README
index 7f40425..89fdf8a 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
 
-x11vnc README file                         Date: Mon Feb  6 12:56:16 EST 2006
+x11vnc README file                         Date: Mon Feb 20 13:57:38 EST 2006
 
 The following information is taken from these URLs:
 
@@ -358,12 +358,12 @@ exec /usr/bin/ssh -t -L 5900:localhost:5900 $gateway \
    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 2005, the [38]x11vnc-0.7.2.tar.gz source package is
-   released (recommended download) . The [39]x11vnc 0.7.2 release notes.
+   link. As of Feb 2006, the [38]x11vnc-0.8.tar.gz source package is
+   released (recommended download). The [39]x11vnc 0.8 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 [40]x11vnc-0.8.tar.gz tarball to build the most up to
+   bleeding edge [40]x11vnc-0.8.1.tar.gz tarball to build the most up to
    date one.
 
    Precompiled Binaries/Packages:  See the [41]FAQ below for information
@@ -393,13 +393,13 @@ exec /usr/bin/ssh -t -L 5900:localhost:5900 $gateway \
     Building x11vnc:
 
    If your OS has libjpeg.so and libz.so in standard locations you can
-   build as follows (example given for the 0.7.2 release of x11vnc:
-   replace with the version you downloaded):
+   build as follows (example given for the 0.8 release of x11vnc: replace
+   with the version you downloaded):
 (un-tar the x11vnc+libvncserver tarball)
-# gzip -dc x11vnc-0.7.2.tar.gz | tar -xvf -
+# gzip -dc x11vnc-0.8.tar.gz | tar -xvf -
 
 (cd to the source directory)
-# cd x11vnc-0.7.2
+# cd x11vnc-0.8
 
 (run configure and then run make)
 # ./configure
@@ -413,17 +413,39 @@ exec /usr/bin/ssh -t -L 5900:localhost:5900 $gateway \
    e.g. --prefix=/my/place). You can now run it via typing "x11vnc",
    "x11vnc -help | more", "x11vnc -forever -shared -display :0", etc.
 
+
    Note: Currently gcc is required to build libvncserver. In some cases
-   it will build with non-gcc compilers, but the resulting binary often
-   fails to run properly. For Solaris pre-built gcc binaries are at
-   [47]http://www.sunfreeware.com/   However, one user reports it does
-   work fine when built with Sun Studio 10, so YMMV.
+   it will build with non-gcc compilers, but the resulting binary
+   sometimes fails to run properly. For Solaris pre-built gcc binaries
+   are at [47]http://www.sunfreeware.com/. Some Solaris pre-built x11vnc
+   binaries are [48]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
+   Solaris 10:
+#!/bin/sh
+PATH=/usr/ccs/bin:/opt/SUNWspro/bin:$PATH; export PATH
+
+CC='cc' \
+CFLAGS='-xO4' \
+LDFLAGS='-L/usr/sfw/lib -L/usr/X11/lib -R/usr/sfw/lib -R/usr/X11/lib' \
+CPPFLAGS='-I /usr/sfw/include -I/usr/X11/include' \
+./configure
+
+MAKE="make -e"
+AM_CFLAGS=""
+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 [49]build scripts below
+   for more ideas.
 
      _________________________________________________________________
 
    Misc. Build problems:   We collect here rare build problems some users
    have reported and the corresponding workarounds. See also the
-   [48]FAQ's on building.
+   [50]FAQ's on building.
 
    One user had a problem where the build script below was failing
    because his work environment had the ENV variable set to a script that
@@ -481,9 +503,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
-   [49]ftp://ftp.uu.net/graphics/jpeg/ and zlib at
-   [50]http://www.gzip.org/zlib/. See also
-   [51]http://www.sunfreeware.com/ for Solaris binary packages of these
+   [51]ftp://ftp.uu.net/graphics/jpeg/ and zlib at
+   [52]http://www.gzip.org/zlib/. See also
+   [53]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.
@@ -549,7 +571,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 [52]this workaround FAQ.
+   OS's, see [54]this workaround FAQ.
 
 
    Building on FreeBSD, OpenBSD, ...:   The jpeg libraries seem to be in
@@ -584,45 +606,46 @@ make
    I don't have any formal beta-testers for the releases of x11vnc, so
    I'd appreciate any additional testing very much!
 
-   Please help test and debug the 0.8 version for release sometime in
-   Feb/2006.
+   Thanks to those who helped beta test x11vnc 0.8 released in Feb 2006!
 
-      [53]x11vnc-0.8.tar.gz
+   The version 0.8.1 beta tarball is kept here    [55]x11vnc-0.8.1.tar.gz
+   (no current plans for what features will be in it or when it will be
+   released.)
 
    There are also some Linux, Solaris, and other OS test binaries
-   [54]here. Please kick the tires and report bugs, performance
-   regressions, undesired behavior, etc. to [55]me.
+   [56]here. Please kick the tires and report bugs, performance
+   regressions, undesired behavior, etc. to [57]me.
 
-   Here is what is shaping up to be the release notes for 0.8:
+   Here are the release notes for the recent 0.8 release:
 
      * TightVNC file transfer added to libvncserver by Rohit Kumar is
-       enabled (use [56]-nofilexfer to disable).
-     * The [57]-passwdfile option has been enhanced to handle any number
+       enabled (use [58]-nofilexfer to disable).
+     * The [59]-passwdfile option has been enhanced to handle any number
        of full-access and view only passwords in an easy to maintain
        format. Automatic rereading or file removal can be enabled.
-     * The [58]-8to24 option enables some multi-depth viewing on systems
-       that don't support [59]-overlay. The 8bpp regions are transformed
+     * The [60]-8to24 option enables some multi-depth viewing on systems
+       that don't support [61]-overlay. The 8bpp regions are transformed
        to depth 24 TrueColor.
-     * The [60]-loop option will run x11vnc in an outer loop restarting
+     * The [62]-loop option will run x11vnc in an outer loop restarting
        each time (useful for situations where the X server restarts
        often).
-     * The [61]-afteraccept option is like [62]-accept however it enables
+     * The [63]-afteraccept option is like [64]-accept however it enables
        running a user supplied command after client authentication has
        taken place. The RFB_* environment variables have been extended.
-     * The [63]-slow_fb allows for slow polling for special purpose
+     * The [65]-slow_fb allows for slow polling for special purpose
        applications (e.g. video).
-     * [64]-blackout noptr,WxH+X+Y,... will prevent the pointer from
+     * [66]-blackout noptr,WxH+X+Y,... will prevent the pointer from
        going into a blacked out region.
      * The x11vnc source code has gone through a major reorganization.
        The build has been enhanced and many bugs fixed.
 
    Here are some notes about features added in 0.7.2. Checking/Testing
-   them is still useful and appreciated:
+   them is still useful and appreciated!
 
-   Note that the [65]X DAMAGE feature will be on by default and so I am
+   Note that the [67]X DAMAGE feature will be on by default and so I am
    interested if that causes any problems. I'd also like to have the new
-   [66]wireframe move/resize, the [67]wireframe copyrect translation, and
-   the [68]scroll detection+copyrect features all on by default as well
+   [68]wireframe move/resize, the [69]wireframe copyrect translation, and
+   the [70]scroll detection+copyrect features all on by default as well
    since when they work they give a great speedup! (CopyRect is a VNC
    encoding and is very fast because the viewer already has the image
    data that needs to be copied: e.g. it just moves it to another part of
@@ -658,10 +681,10 @@ make
    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 in the libvncserver CVS, x11vnc has the
-   [69]-solid [color] option that works on recent GNOME, KDE, and CDE and
+   [71]-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 [70]TightVNC encoding gives the best response for my
+   I also find the [72]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.
 
@@ -673,16 +696,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 "[71]-rfbport NNNN"
+   far-away.east:1. You can force the port with the "[73]-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 [72]command line options. Useful options are, e.g., -scale to
+   via its [74]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
-   [73]-storepasswd option can be used to create the password file).
+   [75]-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
@@ -709,26 +732,31 @@ 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 [74]even more interesting
+   window manager decorations. There will be an [76]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 much use: you will
    normally run and display the viewer on a different machine!
 
+
    SunRay notes:   You can run x11vnc on your (connected or disconnected)
-   [75]SunRay session (Please remember to use [76]-nap and maybe
-   [77]-wait 200 to avoid being a resource hog! It also helps to have a
-   solid background color). You have to know the name of the machine your
-   SunRay session X server is running on. You also need to know the X11
-   DISPLAY number for the session: on a SunRay it could be a large
-   number, e.g. :137, since there are many people with X sessions (Xsun
-   processes) on the same machine. If you don't know it, you can get it
-   by running who(1) in a shell on the SunRay server and looking for the
-   dtlocal entry with your username (and if you don't even know which
-   server machine has your session, you could login to all possible ones
-   looking at the who output for your username...).
-
-   I put some code in my ~/.xsession script that stores $DISPLAY in my
+   [77]SunRay session (Please remember to use settings like [78]-wait
+   200, [79]-sb 15, and not running a screensaver animation (blank
+   instead) to avoid being a resource hog! x11vnc does induce a lot of
+   memory I/O from polling the X server. It also helps to have a solid
+   background color, e.g. [80]-solid).
+
+   You have to know the name of the machine your SunRay session X server
+   is running on (so you can ssh into it and start x11vnc). You also need
+   to know the X11 DISPLAY number for the session: on a SunRay it could
+   be a large number, e.g. :137, since there are many people with X
+   sessions (Xsun processes) on the same machine. If you don't know it,
+   you can get it by running who(1) in a shell on the SunRay server and
+   looking for the dtlocal entry with your username (and if you don't
+   even know which server machine has your session, you could login to
+   all possible ones looking at the who output for your username...).
+
+   I put some code in my ~/.dtprofile script that stores $DISPLAY in my
    ~/.sunray_current file at session startup and deletes it when the
    session ends to make it easy to get at the hostname and X11 display
    number info for my current X sessions.
@@ -740,7 +768,17 @@ make
    sunray-server:0   (note the :0 corresponding to port 5900, it is not
    :137). If it cannot get 5900, it tries for 5901, and so on. You can
    also try to force the port (and thereby the VNC display) using the
-   [78]-rfbport NNNN option.
+   [81]-rfbport NNNN option.
+
+   Especially on a busy Sun Ray server it is often difficult to find free
+   ports for both VNC and the HTTP Java applet server to listen on. This
+   script, [82]vnc_findports may be of use for doing this automatically.
+   It suggests x11vnc command line options based on netstat output that
+   lists the occupied ports. It is even more difficult to start
+   vncserver/Xvnc on a busy Sun Ray because then 3 ports (HTTP, VNC, and
+   X11), all separated by 100 are needed! This script, [83]findvncports
+   may be helpful as well. Both scripts start at VNC display :10 and work
+   their way up.
 
    SunRay Gotcha #2:   If you get an error like:
         shmget(tile) failed.
@@ -753,12 +791,186 @@ make
    dies) the slot is not reclaimed. You can view the shm slots with the
    "ipcs -mA" command. If there are about 100 then you've probably hit
    this problem. They can be cleaned out (by the owner or by root) using
-   the ipcrm command. I wrote a script [79]shm_clear that finds the
+   the ipcrm command. I wrote a script [84]shm_clear that finds the
    orphans and lists or removes them. Longer term, have your SunRay
    sysadmin add something like this to /etc/system:
         set shmsys:shminfo_shmmax = 0x2000000
         set shmsys:shminfo_shmmni = 0x1000
 
+   SunRay Gotcha #3:   Some SunRay installations have implemented
+   suspending certain applications when a SunRay session is in a
+   disconnected state (e.g. Java Badge pulled out, utdetach, etc). This
+   is a good thing because it limits hoggy or runaway apps from wasting
+   the shared CPU resource. Think how much CPU and memory I/O is wasted
+   by a bunch of Firefox windows running worthless Flash animations while
+   your session is disconnected!
+
+   So some sites have implemented scripts to suspend (e.g. kill -STOP)
+   certain apps when your badge is removed from the SunRay terminal. When
+   you reattach, it kill -CONT them. This causes problems for viewing the
+   detached SunRay session via x11vnc: those suspended apps will not
+   respond (their windows will be blank or otherwise inactive).
+
+   What to do? Well, since you are going to be using the application you
+   might as well unfreeze it rather than starting up a 2nd instance. Here
+   is one way to do it using the kill -CONT mechanism:
+   kill -CONT `ps -ealf | grep ' T ' | grep $LOGNAME | awk '{print $4}'`
+
+   If you want to be a good citizen and re-freeze them before you exit
+   x11vnc this script could be of use:
+#!/bin/sh
+#
+# kill -STOP/-CONT script for x11vnc (or other) SunRay usage ("freezes"
+# certain apps from hogging resources when disconnected).
+#
+# Put here a pattern that matches the apps that are frozen:
+#
+appmatch="java_vm|jre|netscape-bin|firefox-bin|realplay|acroread|mozilla-bin"
+
+if [ "X$1" = "Xfreeze" ]; then
+        pkill -STOP -U $LOGNAME "$appmatch"
+elif [ "X$1" = "Xthaw" ]; then
+        pkill -CONT -U $LOGNAME "$appmatch"
+
+elif [ "$RFB_MODE" = "afteraccept" -a "$RFB_STATE" = "NORMAL" ]; then
+        # a valid x11vnc login.
+        if [ "$RFB_CLIENT_COUNT" = "1" ]; then
+                # only one client present.
+                pkill -CONT -U $LOGNAME "$appmatch"
+        fi
+elif [ "$RFB_MODE" = "gone" -a "$RFB_STATE" = "NORMAL" ]; then
+        # a valid x11vnc login.
+        if [ "$RFB_CLIENT_COUNT" = "0" ]; then
+                # last client present has just left.
+                pkill -STOP -U $LOGNAME "$appmatch"
+        fi
+fi
+exit 0
+
+   If you called the script "goodcitizen" you could type "goodcitizen
+   thaw" to unfreeze them, and then "goodcitizen freeze" to refreeze
+   them. One could also use these x11vnc options "-afteraccept
+   goodcitizen -gone goodcitizen" to do it automatically.
+
+   SunRay Gotcha #4:   Recent versions of the Sun Ray Server Software
+   SRSS (seems to be version 3.0 or 3.1) have a "misfeature" that when
+   the session is disconnected (i.e. badge/smartcard out) the screen
+   locker (xscreensaver) will freeze the X server just when the "Enter
+   Password" dialog box appears. So you cannot unlock the screen remotely
+   via x11vnc!
+
+   Here "freeze" means "stop other X clients from inserting keyboard and
+   mouse input and from viewing the current contents of the screen". Or
+   something like that; the upshot is x11vnc can't do its normal thing.
+
+   There are several workarounds for this.
+
+   1) The easiest one by far is to put these lines in your
+   $HOME/.dtprofile file:
+SUN_SUNRAY_UTXLOCK_PREF="/usr/openwin/bin/xlock -mode blank"
+export SUN_SUNRAY_UTXLOCK_PREF
+
+   One might argue that xlock isn't particularly "pretty". (Just IMHO,
+   but if something like this not being pretty actually gets in the way
+   of your work I think some introspection may be in order. :-)
+
+   2) The problem has been traced to the pam_sunray.so PAM module.
+   Evidently xscreensaver invokes this pam module and it communicates
+   with utsessiond who in turn instructs the Xsun server to not process
+   any synthetic mouse/keyboard input or to update the screen
+   framebuffer. It is not clear if this is by design (security?) or
+   something else.
+
+   In any event, the problem can be avoided by commenting out the
+   corresponding line in /etc/pam.conf:
+#xscreensaver auth sufficient /opt/SUNWut/lib/pam_sunray.so syncondisplay
+
+   Leave the other xscreensaver pam authentication lines unchanged. The
+   dtsession-SunRay line may also need to be commented out to avoid the
+   problem for CDE sessions. N.B. it is possible the application of a
+   SSRS patch, etc, may re-enable that /etc/pam.conf line.
+
+   3) A more drastic way is to kill the xscreensaver process from a shell
+   prompt whenever you connect via x11vnc and the screen is in a locked
+   state:
+pkill -U $LOGNAME '^xscreensaver$'
+
+   And then after you are in be sure to restart it by typing something
+   like:
+xscreensaver &
+
+   You may want to avoid restarting it until you are about to disconnect
+   your VNC viewer (since if it locks the screen while you are working
+   you'll be stuck again).
+
+   3') The above idea can be done a bit more cleanly by having x11vnc do
+   it. Suppose we called the following script xss_killer:
+#!/bin/sh
+#
+# xss_killer: kill xscreensaver after a valid x11vnc client logs in.
+#             Restart xscreensaver and lock it when the last client
+#             disconnects.
+
+PATH=/usr/openwin/bin:/usr/bin:$PATH
+export PATH
+
+if [ "$RFB_MODE" = "afteraccept" -a "$RFB_STATE" = "NORMAL" ]; then
+        # a valid x11vnc login.
+        if [ "$RFB_CLIENT_COUNT" = "1" ]; then
+                # only one client present.
+                pkill -U $LOGNAME '^xscreensaver$'
+                pkill -KILL -U $LOGNAME -f xscreensaver/hacks
+        fi
+elif [ "$RFB_MODE" = "gone" -a "$RFB_STATE" = "NORMAL" ]; then
+        # a valid x11vnc login.
+        if [ "$RFB_CLIENT_COUNT" = "0" ]; then
+                # last client present has just left.
+                xscreensaver -nosplash &
+                sleep 1
+                xscreensaver-command -lock &
+        fi
+fi
+
+   Then we would run x11vnc with these options: "-afteraccept xss_killer
+   -gone xss_killer". The [85]-afteraccept option (introduced in version
+   0.8) is used to run a command after a vncviewer has successfully
+   logged in (note that this is a VNC login, not a Unix login, so you may
+   not want to do this if you are really paranoid...)
+
+   Note if you use the above script and also plan to Ctrl-C (SIGINT)
+   x11vnc you have to run the xscreensaver in a new process group to
+   avoid killing it as well. One way to do this is via this kludge:
+perl -e 'setpgrp(0,0); exec "xscreensaver -nosplash &"'
+
+   in the above script.
+
+   4) There appears to be a bug in pam_sunray.so in that it doesn't seem
+   to honor the convention that, say, DISPLAY=unix:3 means to use Unix
+   sockets to connect to display 3 on the local machine (this is a bit
+   faster than TCP sockets). Rather, it thinks the display is a non-local
+   one to a machine named "unix" (that usually does not resolve to an IP
+   address).
+
+   Amusingly, this can be used to bypass the pam_sunray.so blocking of
+   Xsun that prevents one from unlocking the screen remotely via x11vnc.
+   One could put something like this in $HOME/.dtprofile to kill any
+   existing xscreensavers and then start up a fresh xscreensaver using
+   DISPLAY=unix:N
+# stop/kill any running xscreensavers (probably not running yet, but to be sure
+)
+xscreensaver-command -exit
+pkill -U $LOGNAME '^xscreensaver$'
+env DISPLAY=`echo $DISPLAY | sed -e 's/^.*:/unix:/'` xscreensaver &
+
+
+   Note that all of the above workarounds side-step the pam_sunray.so PAM
+   module in one way or another. You'll need to see if that is
+   appropriate for your site's SunRay / smartcard usage. Also, these
+   hacks may break other things and so you may want to test various
+   scenarios carefully. E.g. check corner cases like XDMCP/dtremote,
+   NSCM, etc.
+
+
     Limitations:
 
      * Due to the polling nature, some activities (opaque window moves,
@@ -767,7 +979,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
-       [80]-scrollcopyrect and [81]-wireframe speedups using the CopyRect
+       [86]-scrollcopyrect and [87]-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
@@ -797,15 +1009,14 @@ make
        framebuffer read speed considerably (5-100 times) by using the
        Shadow Framebuffer (a copy of the framebuffer is kept in main
        memory and this can be read much more quickly). To do this one
-       puts the line Option "ShadowFB" "true" (and depending on video
-       card driver, Option "NoAccel" "true" may be needed too) in the
-       Device section of the /etc/X11/XF86Config or /etc/X11/xorg.conf
-       file. Note that this disables 2D acceleration at the physical
-       display and so likely defeats the purpose. Nevertheless this could
-       be handy in some circumstances, e.g. if the slower speed while
-       sitting at the physical display was acceptable (this seems to be
-       true for most video cards these days). Unfortunately it does not
-       seem shadowfb can be turned on and off dynamically...
+       puts the line Option "ShadowFB" "true" in the Device section of
+       the /etc/X11/XF86Config or /etc/X11/xorg.conf file. Note that this
+       disables 2D acceleration at the physical display and so likely
+       defeats the purpose. Nevertheless this could be handy in some
+       circumstances, e.g. if the slower speed while sitting at the
+       physical display was acceptable (this seems to be true for most
+       video cards these days). Unfortunately it does not seem shadowfb
+       can be turned on and off dynamically...
        Another amusing thing one can do is use Xvfb as the X server, e.g.
        "xinit $HOME/.xinitrc -- /usr/X11R6/bin/Xvfb :1 -screen 0
        1024x768x16" x11vnc can poll Xvfb efficiently via main memory.
@@ -815,14 +1026,14 @@ make
        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
-       [82]this FAQ for details.
+       [88]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" [83]options, however, for a partial hack for
+       X" and "-cursor some" [89]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 [84]-overlay option is also supplied. A similar thing is done
+       the [90]-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
@@ -834,16 +1045,16 @@ make
        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 [85]-scrollcopyrect option
+     * The scroll detection algorithm for the [91]-scrollcopyrect option
        can give choppy or bunched up transient output and occasionally
        painting errors.
      * Occasionally a patch of tiles will not get updated correctly.
        Evidently a timing related bug and difficult to reproduce...
      * Using -threads can expose some bugs in libvncserver.
 
-   Please feel free to [86]contact me if you have any questions,
+   Please feel free to [92]contact me if you have any questions,
    problems, or comments about x11vnc, etc.
-   Also, some people ask if they can make a donation, see [87]this link
+   Also, some people ask if they can make a donation, see [93]this link
    for that.
      _________________________________________________________________
 
@@ -852,297 +1063,301 @@ make
 
    [Building and Starting]
 
-   [88]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed
+   [94]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? 
 
-   [89]Q-2: I can't get x11vnc and/or libvncserver to compile. 
+   [95]Q-2: I can't get x11vnc and/or libvncserver to compile. 
 
-   [90]Q-3: I just built x11vnc successfully, but when I use it my
+   [96]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). 
 
-   [91]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old
+   [97]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old
    Unix/Linux) and it doesn't compile! 
 
-   [92]Q-5: Where can I get a precompiled x11vnc binary for my Operating
+   [98]Q-5: Where can I get a precompiled x11vnc binary for my Operating
    System? 
 
-   [93]Q-6: Where can I get a VNC Viewer binary (or source code) for the
+   [99]Q-6: Where can I get a VNC Viewer binary (or source code) for the
    Operating System I will be viewing from? 
 
-   [94]Q-7: How can I see all of x11vnc's command line options and
+   [100]Q-7: How can I see all of x11vnc's command line options and
    documentation on how to use them? 
 
-   [95]Q-8: I don't like typing arcane command line options every time I
+   [101]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? 
 
-   [96]Q-9: How can I get the GUI to run in the System Tray, or at least
+   [102]Q-9: How can I get the GUI to run in the System Tray, or at least
    be a smaller, simpler icon? 
 
-   [97]Q-10: Can I make x11vnc more quiet and also go into the background
-   after starting up? 
+   [103]Q-10: Can I make x11vnc more quiet and also go into the
+   background after starting up? 
 
-   [98]Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies
+   [104]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. 
 
-   [99]Q-12: Are there any build-time customizations possible, e.g.
+   [105]Q-12: Are there any build-time customizations possible, e.g.
    change defaults, create a smaller binary, etc? 
 
    [Win2VNC Related]
 
-   [100]Q-13: I have two separate machine displays in front of me, one
+   [106]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? 
 
-   [101]Q-14: I am running Win2VNC on my Windows machine and "x11vnc
+   [107]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]
 
-   [102]Q-15: The X display I run x11vnc on is only 8 bits per pixel
+   [108]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. 
 
-   [103]Q-16: Color problems: Why are the colors for some windows
+   [109]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. 
 
-   [104]Q-17: How do I figure out the window id to supply to the -id
+   [110]Q-17: How do I figure out the window id to supply to the -id
    windowid option? 
 
-   [105]Q-18: Why don't menus or other transient windows come up when I
+   [111]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? 
 
-   [106]Q-19: My X display is depth 24 at 24bpp (instead of the normal
+   [112]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]
 
-   [107]Q-20: Can I use x11vnc to view and interact with an Xterminal
+   [113]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? 
 
-   [108]Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file)
+   [114]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]
+
+   [115]Q-22: I'm having trouble using x11vnc with my Sun Ray session. 
+
    [Remote Control]
 
-   [109]Q-22: How do I stop x11vnc once it is running in the background? 
+   [116]Q-23: How do I stop x11vnc once it is running in the background? 
 
-   [110]Q-23: Can I change settings in x11vnc without having to restart
+   [117]Q-24: Can I change settings in x11vnc without having to restart
    it? Can I remote control it? 
 
    [Security and Permissions]
 
-   [111]Q-24: How do I create a VNC password for use with x11vnc? 
+   [118]Q-25: How do I create a VNC password for use with x11vnc? 
 
-   [112]Q-25: Can I make it so -storepasswd doesn't show my password on
+   [119]Q-26: Can I make it so -storepasswd doesn't show my password on
    the screen? 
 
-   [113]Q-26: Can I have two passwords for VNC viewers, one for full
+   [120]Q-27: Can I have two passwords for VNC viewers, one for full
    access and the other for view-only access to the display? 
 
-   [114]Q-27: Can I have as many full-access and view-only passwords as I
+   [121]Q-28: Can I have as many full-access and view-only passwords as I
    like? 
 
-   [115]Q-28: Can I fine tune what types of user input are allowed? E.g.
+   [122]Q-29: 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? 
 
-   [116]Q-29: Why does x11vnc exit as soon as the VNC viewer disconnects?
+   [123]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? 
 
-   [117]Q-30: Can I limit which machines incoming VNC clients can connect
+   [124]Q-31: Can I limit which machines incoming VNC clients can connect
    from? 
 
-   [118]Q-31: How do I build x11vnc/libvncserver with libwrap
+   [125]Q-32: How do I build x11vnc/libvncserver with libwrap
    (tcp_wrappers) support? 
 
-   [119]Q-32: Can I have x11vnc only listen on one network interface
+   [126]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? 
 
-   [120]Q-33: Now that -localhost implies listening only on the loopback
+   [127]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? 
 
-   [121]Q-34: How can I tunnel my connection to x11vnc via an encrypted
+   [128]Q-35: How can I tunnel my connection to x11vnc via an encrypted
    SSH channel between two Unix machines? 
 
-   [122]Q-35: How can I tunnel my connection to x11vnc via an encrypted
+   [129]Q-36: How can I tunnel my connection to x11vnc via an encrypted
    SSH channel from Windows using an SSH client like Putty? 
 
-   [123]Q-36: Can I prompt the user at the local X display whether the
+   [130]Q-37: 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? 
 
-   [124]Q-37: Does x11vnc support Unix usernames and passwords? Can I
+   [131]Q-38: Does x11vnc support Unix usernames and passwords? Can I
    further limit the set of Unix usernames who can connect to the VNC
    desktop? 
 
-   [125]Q-38: I start x11vnc as root because it is launched via inetd(1)
+   [132]Q-39: I start x11vnc as root because it is launched via inetd(1)
    or a display manager like gdm(1). Can I have x11vnc later switch to a
    different user? 
 
-   [126]Q-39: I use a screen-lock when I leave my workstation (e.g.
+   [133]Q-40: 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? 
 
-   [127]Q-40: Can I have x11vnc automatically lock the screen when I
+   [134]Q-41: Can I have x11vnc automatically lock the screen when I
    disconnect the VNC viewer? 
 
    [Display Managers and Services]
 
-   [128]Q-41: How can I run x11vnc as a "service" that is always
+   [135]Q-42: How can I run x11vnc as a "service" that is always
    available? 
 
-   [129]Q-42: How can I use x11vnc to connect to an X login screen like
+   [136]Q-43: 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). 
 
-   [130]Q-43: Can I run x11vnc out of inetd(1)? How about xinetd(1)? 
+   [137]Q-44: Can I run x11vnc out of inetd(1)? How about xinetd(1)? 
 
-   [131]Q-44: Can I have x11vnc restart itself after it terminates? 
+   [138]Q-45: Can I have x11vnc restart itself after it terminates? 
 
-   [132]Q-45: How do I make x11vnc work with the Java VNC viewer applet
+   [139]Q-46: How do I make x11vnc work with the Java VNC viewer applet
    in a web browser? 
 
-   [133]Q-46: Are reverse connections (i.e. the VNC server connecting to
+   [140]Q-47: Are reverse connections (i.e. the VNC server connecting to
    the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
    
-   [134]Q-47: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
+   [141]Q-48: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
    real display, but for a virtual one I keep around). 
 
-   [135]Q-48: How can I use x11vnc on "headless" machines? Why might I
+   [142]Q-49: How can I use x11vnc on "headless" machines? Why might I
    want to? 
 
    [Resource Usage and Performance]
 
-   [136]Q-49: I have lots of memory, but why does x11vnc fail with
+   [143]Q-50: 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)? 
 
-   [137]Q-50: How can I make x11vnc use less system resources? 
+   [144]Q-51: How can I make x11vnc use less system resources? 
 
-   [138]Q-51: How can I make x11vnc use MORE system resources? 
+   [145]Q-52: How can I make x11vnc use MORE system resources? 
 
-   [139]Q-52: I use x11vnc over a slow link with high latency (e.g.
+   [146]Q-53: I use x11vnc over a slow link with high latency (e.g.
    dialup modem), is there anything I can do to speed things up? 
 
-   [140]Q-53: Does x11vnc support the X DAMAGE Xserver extension to find
+   [147]Q-54: Does x11vnc support the X DAMAGE Xserver extension to find
    modified regions of the screen quickly and efficiently? 
 
-   [141]Q-54: When I drag windows around with the mouse or scroll up and
+   [148]Q-55: 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? 
 
-   [142]Q-55: Why not do something like wireframe animations to avoid the
+   [149]Q-56: Why not do something like wireframe animations to avoid the
    windows "lurching" when being moved or resized? 
 
-   [143]Q-56: Can x11vnc try to apply heuristics to detect when an window
+   [150]Q-57: Can x11vnc try to apply heuristics to detect when an window
    is scrolling its contents and use the CopyRect encoding for a speedup?
    
    [Mouse Cursor Shapes]
 
-   [144]Q-57: Why isn't the mouse cursor shape (the little icon shape
+   [151]Q-58: Why isn't the mouse cursor shape (the little icon shape
    where the mouse pointer is) correct as I move from window to window? 
 
-   [145]Q-58: When using XFIXES cursorshape mode, some of the cursors
+   [152]Q-59: 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? 
 
-   [146]Q-59: In XFIXES mode, are there any hacks to handle cursor
+   [153]Q-60: In XFIXES mode, are there any hacks to handle cursor
    transparency ("alpha channel") exactly? 
 
    [Mouse Pointer]
 
-   [147]Q-60: Why does the mouse arrow just stay in one corner in my
+   [154]Q-61: Why does the mouse arrow just stay in one corner in my
    vncviewer, whereas my cursor (that does move) is just a dot? 
 
-   [148]Q-61: Can I take advantage of the TightVNC extension to the VNC
+   [155]Q-62: 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)? 
 
-   [149]Q-62: Is it possible to swap the mouse buttons (e.g. left-handed
+   [156]Q-63: 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]
 
-   [150]Q-63: How can I get my AltGr and Shift modifiers to work between
+   [157]Q-64: How can I get my AltGr and Shift modifiers to work between
    keyboards for different languages? 
 
-   [151]Q-64: When I try to type a "<" (i.e. less than) instead I get ">"
+   [158]Q-65: When I try to type a "<" (i.e. less than) instead I get ">"
    (i.e. greater than)! Strangely, typing ">" works OK!! 
 
-   [152]Q-65: When I try to type a "<" (i.e. less than) instead I get
+   [159]Q-66: When I try to type a "<" (i.e. less than) instead I get
    "<," (i.e. an extra comma). 
 
-   [153]Q-66: I'm using an "international" keyboard (e.g. German "de", or
+   [160]Q-67: 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? 
 
-   [154]Q-67: When typing I sometimes get double, triple, or more of my
+   [161]Q-68: 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? 
 
-   [155]Q-68: The x11vnc -norepeat mode is in effect, but I still get
+   [162]Q-69: The x11vnc -norepeat mode is in effect, but I still get
    repeated keystrokes!! 
 
-   [156]Q-69: The machine where I run x11vnc has an AltGr key, but the
+   [163]Q-70: 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? 
 
-   [157]Q-70: I have a Sun machine I run x11vnc on. Its Sun keyboard has
+   [164]Q-71: 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) 
 
-   [158]Q-71: Can I map a keystroke to a mouse button click on the remote
+   [165]Q-72: Can I map a keystroke to a mouse button click on the remote
    machine? 
 
    [Screen Related Issues and Features]
 
-   [159]Q-72: The remote display is larger (in number of pixels) than the
+   [166]Q-73: 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? 
 
-   [160]Q-73: Does x11vnc support server-side framebuffer scaling? (E.g.
+   [167]Q-74: Does x11vnc support server-side framebuffer scaling? (E.g.
    to make the desktop smaller). 
 
-   [161]Q-74: Does x11vnc work with Xinerama? (i.e. multiple monitors
+   [168]Q-75: Does x11vnc work with Xinerama? (i.e. multiple monitors
    joined together to form one big, single screen). 
 
-   [162]Q-75: Can I use x11vnc on a multi-headed display that is not
+   [169]Q-76: Can I use x11vnc on a multi-headed display that is not
    Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? 
 
-   [163]Q-76: Can x11vnc show only a portion of the display? (E.g. for a
+   [170]Q-77: Can x11vnc show only a portion of the display? (E.g. for a
    special purpose rfb application). 
 
-   [164]Q-77: Does x11vnc support the XRANDR (X Resize, Rotate and
+   [171]Q-78: Does x11vnc support the XRANDR (X Resize, Rotate and
    Reflection) extension? Whenever I rotate or resize the screen x11vnc
    just seems to crash. 
 
-   [165]Q-78: Why is the view in my VNC viewer completely black? Or why
+   [172]Q-79: Why is the view in my VNC viewer completely black? Or why
    is everything flashing around randomly? 
 
-   [166]Q-79: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+   [173]Q-80: 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
@@ -1150,12 +1365,12 @@ make
    otherwise all messed up unless the X session x11vnc is attached to is
    in the active VC? 
 
-   [167]Q-80: Can I use x11vnc to view my VMWare session remotely? 
+   [174]Q-81: Can I use x11vnc to view my VMWare session remotely? 
 
-   [168]Q-81: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
+   [175]Q-82: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
    controlled by x11vnc? 
 
-   [169]Q-82: I am using x11vnc where my local machine has "popup/hidden
+   [176]Q-83: 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
@@ -1163,15 +1378,15 @@ make
 
    [Misc: Clipboard, Beeps, Thanks, etc.]
 
-   [170]Q-83: Does the Clipboard/Selection get transferred between the
+   [177]Q-84: Does the Clipboard/Selection get transferred between the
    vncviewer and the X display? 
 
-   [171]Q-84: Can I transfer files back and forth with x11vnc? 
+   [178]Q-85: Can I transfer files back and forth with x11vnc? 
 
-   [172]Q-85: Why don't I hear the "Beeps" in my X session (e.g. when
+   [179]Q-86: Why don't I hear the "Beeps" in my X session (e.g. when
    typing tput bel in an xterm)? 
 
-   [173]Q-86: Thanks for your program and for your help! Can I make a
+   [180]Q-87: Thanks for your program and for your help! Can I make a
    donation? 
      _________________________________________________________________
 
@@ -1184,7 +1399,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 [174]-display
+   on). Set your DISPLAY environment variable or use the [181]-display
    option to specify it. Nearly always the correct value will be ":0"
 
 
@@ -1201,7 +1416,7 @@ make
 
    How to Solve:  See the xauth(1), Xsecurity(7), and xhost(1) man pages
    for much info on X11 permissions. For example, you may need to set
-   your XAUTHORITY environment variable or use the [175]-auth option to
+   your XAUTHORITY environment variable or use the [182]-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 simply be sure
    you run x11vnc as the correct user (i.e. the user who is logged into
@@ -1219,7 +1434,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 [176]this faq for other display manager
+   read the gdm cookie file, see [183]this faq for other display manager
    cookie file names).
 
    Less safe, but to avoid figuring out where the correct XAUTHORITY file
@@ -1228,7 +1443,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 [177]-users option).
+   (please read the documentation on the [184]-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
@@ -1340,7 +1555,7 @@ h
    earlier and perhaps non-Solaris):
 
    First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
-   above [178]Solaris build script to run the configure command. That
+   above [185]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
@@ -1366,7 +1581,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
-   [179]SunOS 4.x
+   [186]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
@@ -1376,23 +1591,23 @@ typedef unsigned int in_addr_t;
    Q-5: Where can I get a precompiled x11vnc binary for my Operating
    System?
 
-   Hopefully the [180]build steps above and [181]FAQ provide enough info
+   Hopefully the [187]build steps above and [188]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)  [182]http://packages.debian.org/x11vnc
+    Debian:         (.deb)  [189]http://packages.debian.org/x11vnc
 
-   Slackware: (.tgz) [183]http://www.linuxpackages.net/ Redhat/Fedora:
-   (.rpm) [184]http://dag.wieers.com/packages/x11vnc/ SuSE: (.rpm)
-   [185]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
-   [186]http://www.sunfreeware.com/ wwexptools: (.tgz)
-   [187]http://www.bell-labs.com/project/wwexptools/packages.html
+   Slackware: (.tgz) [190]http://www.linuxpackages.net/ Redhat/Fedora:
+   (.rpm) [191]http://dag.wieers.com/packages/x11vnc/ SuSE: (.rpm)
+   [192]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
+   [193]http://www.sunfreeware.com/ wwexptools: (.tgz)
+   [194]http://www.bell-labs.com/project/wwexptools/packages.html
 
    If the above binaries don't work and building x11vnc on your OS fails
-   (and all else fails!) you can try one of [188]my collection of
+   (and all else fails!) you can try one of [195]my collection of
    binaries for various OS's and x11vnc releases.
 
    As a general note, the x11vnc program is simple enough you don't
@@ -1413,9 +1628,9 @@ typedef unsigned int in_addr_t;
 
    To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
    try here:
-     * [189]http://www.tightvnc.com/download.html
-     * [190]http://www.realvnc.com/download-free.html
-     * [191]http://sourceforge.net/projects/cotvnc/
+     * [196]http://www.tightvnc.com/download.html
+     * [197]http://www.realvnc.com/download-free.html
+     * [198]http://sourceforge.net/projects/cotvnc/
 
 
    Q-7: How can I see all of x11vnc's command line options and
@@ -1423,7 +1638,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
-   [192]here as well.
+   [199]here as well.
 
 
    Q-8: I don't like typing arcane command line options every time I
@@ -1454,10 +1669,10 @@ display :0
    The /usr/bin/wish 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. See the
-   [193]-gui option for more info. Examples: "x11vnc ... -gui" and
+   [200]-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
-   "[194]-gui tray" system tray mode.
+   "[201]-gui tray" system tray mode.
 
 
    Q-9: How can I get the GUI to run in the System Tray, or at least be a
@@ -1484,11 +1699,11 @@ display :0
    Q-10: Can I make x11vnc more quiet and also go into the background
    after starting up?
 
-   Use the [195]-q and [196]-bg options, respectively.  (also: -quiet is
+   Use the [202]-q and [203]-bg options, respectively.  (also: -quiet is
    an alias for -q)
 
    Note that under -bg the stderr messages will be lost unless you use
-   the "[197]-o logfile" option.
+   the "[204]-o logfile" option.
 
 
    Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
@@ -1509,7 +1724,7 @@ display :0
 
    As of Mar/2004 in the libvncserver cvs there are a few such options.
    They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS
-   environment variable before running configure (see the [198]build
+   environment variable before running configure (see the [205]build
    notes for general background).
      * -DVNCSHARED=1   make -shared the default.
      * -DFOREVER=1   make -forever the default.
@@ -1558,21 +1773,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 "[199]-nofb" option
+   Yes, for best response start up x11vnc with the "[206]-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 [200]x2vnc, however you would
+   This will also work X11 to X11 using [207]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:
-     * [201]Original Win2VNC
-     * [202]Enhanced Win2VNC and [203]sourceforge link
-     * [204]x2vnc
-     * [205]x2x also [206]here
-     * [207]zvnc (MorphOS)
+     * [208]Original Win2VNC
+     * [209]Enhanced Win2VNC and [210]sourceforge link
+     * [211]x2vnc
+     * [212]x2x also [213]here
+     * [214]zvnc (MorphOS)
 
    All of them will work with x11vnc (except x2x where it is not needed).
 
@@ -1592,7 +1807,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, in the
-   libvncserver CVS, x11vnc has the [208]-visual option to allow you to
+   libvncserver CVS, x11vnc has the [215]-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:
@@ -1607,7 +1822,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 [209]-flashcmap option to have x11vnc watch for changes in the
+   Use the [216]-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
@@ -1616,13 +1831,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 [210]-8to24 (Jan/2006) can often remove the need
+   Also note the option [217]-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 [211]-notruecolor option has corrected colors
+   In some rare cases the [218]-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.
@@ -1633,13 +1848,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 [212]previous question regarding 8 bpp
+   You may want to review the [219]previous question regarding 8 bpp
    PseudoColor.
 
-   On some hardware (Sun/SPARC and SGI), the [213]-overlay option
+   On some hardware (Sun/SPARC and SGI), the [220]-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
-   [214]-8to24 option may help (also discussed below).
+   [221]-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
@@ -1675,7 +1890,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 [215]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+   use the [222]-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
@@ -1700,7 +1915,7 @@ TrueColor defdepth 24
    Xsun, e.g. in your /etc/dt/config/Xservers file).
 
 
-   The -8to24 mode: The [216]-8to24 x11vnc option (Jan/2006) is a kludge
+   The -8to24 mode: The [223]-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
@@ -1714,11 +1929,11 @@ TrueColor defdepth 24
    32bpp view is exported via VNC.
 
    Even on pure 8bpp displays it can be used as an alternative to
-   [217]-flashcmap to avoid color flashing completely.
+   [224]-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: [218]-fixscreen V=3.0 to
+   row, or by using something like: [225]-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.
@@ -1731,23 +1946,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 [219]-8to24 help description for information on
+   speedup. See the [226]-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 [220]-id option to
+   possible workaround in this case is to use the [227]-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 [221]-8to24 method
+   for x11vnc to be able to do so in real time. The [228]-8to24 method
    does this approximately and is somewhat usable. Fortunately the
-   [222]-overlay option works for Solaris machines with overlay visuals
+   [229]-overlay option works for Solaris machines with overlay visuals
    where most of this problem occurs.
 
 
@@ -1758,9 +1973,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 [223]color problems.
+   debugging x11vnc [230]color problems.
 
-   Also, as of Dec/2004 libvncserver CVS you can use "[224]-id pick" to
+   Also, as of Dec/2004 libvncserver CVS you can use "[231]-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.
@@ -1778,7 +1993,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 [225]-sid windowid option ("shifted" windowid).
+   polling, try the [232]-sid windowid option ("shifted" windowid).
 
 
    Q-19: My X display is depth 24 at 24bpp (instead of the normal depth
@@ -1828,15 +2043,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 [226]-display option to point the display to that of
+   machine. Use the [233]-display option to point the display to that of
    the Xterminal (you'll of course need basic X11 permission to do that)
-   and also supply the [227]-noshm option (this enables the polling over
+   and also supply the [234]-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 [228]-flipbyteorder if the
+   on the polling rate. You may also need [235]-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
@@ -1860,7 +2075,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
-   [229]-auth option to point to the correct file). Other options include
+   [236]-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 -
 
@@ -1872,7 +2087,7 @@ TrueColor defdepth 24
    details.
 
    If the display name in the cookie file needs to be changed between the
-   two hosts, see [230]this note on the "xauth add ..." command.
+   two hosts, see [237]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
@@ -1886,7 +2101,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 [231]poll
+   Not recommended, but as a last resort, you could have x11vnc [238]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...)
@@ -1911,23 +2126,36 @@ TrueColor defdepth 24
    above permission, etc, problems: both vncviewer and x11vnc are X
    client apps desired to be run on the Xterminal box).
 
+   [Sun Rays]
+
+   Q-22: I'm having trouble using x11vnc with my Sun Ray session.
+
+   The [239]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 [240]this discussion of Sun Ray issues above
+   for solutions to problems.
+
    [Remote Control]
 
-   Q-22: How do I stop x11vnc once it is running in the background?
+   Q-23: How do I stop x11vnc once it is running in the background?
 
    As of Dec/2004 in the libvncserver CVS there is a remote control
    feature. It can change a huge amount of things on the fly: see the
-   [232]-remote and [233]-query options. To shut down the running x11vnc
+   [241]-remote and [242]-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 [234]-forever option has not been supplied, x11vnc will
+   If the [243]-forever option has not been supplied, x11vnc will
    automatically exit after the first client disconnects. In general 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 [235]-bg option
+   If you have not put x11vnc in the background via the [244]-bg option
    or shell & operator, then simply press Ctrl-C in the shell where
    x11vnc is running to stop it.
 
@@ -1937,15 +2165,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 [236]-clear_mods
-   option and [237]-clear_keys option can be used to release pressed keys
+   by tapping Ctrl, Shift, and Alt. Alternatively, the [245]-clear_mods
+   option and [246]-clear_keys option can be used to release pressed keys
    at startup and exit.
 
 
-   Q-23: Can I change settings in x11vnc without having to restart it?
+   Q-24: Can I change settings in x11vnc without having to restart it?
    Can I remote control it?
 
-   Look at the [238]-remote (same as -R) and [239]-query (same as -Q)
+   Look at the [247]-remote (same as -R) and [248]-query (same as -Q)
    options added in the Dec/2004 libvncserver CVS. They allow nearly
    everything to be changed dynamically and settings to be queried.
    Examples: "x11vnc -R shared", "x11vnc -R forever", "x11vnc -R
@@ -1957,14 +2185,14 @@ TrueColor defdepth 24
    be possible.
 
    There is also a simple Tcl/Tk gui based on this remote control
-   mechanism. See the [240]-gui option for more info. You will need to
+   mechanism. See the [249]-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".
 
    [Security and Permissions]
 
-   Q-24: How do I create a VNC password for use with x11vnc?
+   Q-25: How do I create a VNC password for use with x11vnc?
 
    You may already have one in $HOME/.vnc/passwd if you have used, say,
    the vncserver program from the regular RealVNC or TightVNC packages
@@ -1972,12 +2200,12 @@ TrueColor defdepth 24
    vncpasswd(1) program from those packages. The libvncserver package
    also comes with a simple program: storepasswd in the examples
    directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports
-   the -storepasswd "pass" "file" [241]option, which is the the same
+   the -storepasswd "pass" "file" [250]option, which is the 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: [242]-rfbauth
+   You then use the password via the x11vnc option: [251]-rfbauth
    $HOME/myvncpasswd
 
    Compared to vncpasswd(1) the latter two methods are a somewhat unsafe
@@ -1986,18 +2214,18 @@ TrueColor defdepth 24
    out for the command winding up in your shell's history file (history
    -c is often a way to clear it).
 
-   x11vnc also has the [243]-passwdfile and -passwd/-viewpasswd plain
+   x11vnc also has the [252]-passwdfile and -passwd/-viewpasswd plain
    text (i.e. not obscured like the -rfbauth VNC passwords) password
    options.
 
 
-   Q-25: Can I make it so -storepasswd doesn't show my password on the
+   Q-26: Can I make it so -storepasswd doesn't show my password on the
    screen?
 
    You can use the vncpasswd program from RealVNC or TightVNC mentioned
    above..
 
-   Alternatively, this script should keep your [244]-storepasswd more
+   Alternatively, this script should keep your [253]-storepasswd more
    private:
 #!/bin/sh
 # usage: x11vnc_pw [file]  (default: ~/.vnc/passwd)
@@ -2028,17 +2256,17 @@ ls -l "$file"
    running that someone could snoop the value using ps(1).
 
 
-   Q-26: Can I have two passwords for VNC viewers, one for full access
+   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 in the libvncserver CVS there is the
-   [245]-viewpasswd option to supply the view-only password. Note the
-   full-access password option [246]-passwd must be supplied at the same
+   [254]-viewpasswd option to supply the view-only password. Note the
+   full-access password option [255]-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
-   [247]-passwdfile option to specify a file containing plain text
+   [256]-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
@@ -2046,7 +2274,7 @@ ls -l "$file"
    it is taken as the view-only password. (use "__EMPTY__" to supply an
    empty one).
 
-   View-only passwords currently do not work for the [248]-rfbauth
+   View-only passwords currently do not work for the [257]-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
@@ -2056,10 +2284,10 @@ ls -l "$file"
    straight-forward to work out what to do from the VNC source code.
 
 
-   Q-27: Can I have as many full-access and view-only passwords as I
+   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 [249]-passwdfile
+   Yes, as of Jan/2006 in the libvncserver CVS the [258]-passwdfile
    option has been extended to handle as many passwords as you like. You
    put the view-only passwords after a line __BEGIN_VIEWONLY__.
 
@@ -2067,11 +2295,11 @@ ls -l "$file"
    You can have x11vnc re-read the file dynamically when it is modified.
 
 
-   Q-28: Can I fine tune what types of user input are allowed? E.g. have
+   Q-29: 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?
 
-   As of Feb/2005, the [250]-input option allows you to do this. "K",
+   As of Feb/2005, the [259]-input option allows you to do this. "K",
    "M", and "B" stand for Keystroke, Mouse-motion, and Button-clicks,
    respectively. The setting: "-input M" makes attached viewers only able
    to move the mouse. "-input KMB,M" lets normal clients do everything
@@ -2081,29 +2309,29 @@ ls -l "$file"
    remote control mechanism or the GUI. E.g. x11vnc -R input:hostname:M
 
 
-   Q-29: Why does x11vnc exit as soon as the VNC viewer disconnects? And
+   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?
 
    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 [251]-forever option (aka -many) to have
+   periods of time. Use the [260]-forever option (aka -many) to have
    x11vnc wait for more connections after the first client disconnects.
-   Use the [252]-shared option to have x11vnc allow multiple clients to
+   Use the [261]-shared option to have x11vnc allow multiple clients to
    connect simultaneously.
 
-   Recommended additional safety measures include using ssh ([253]see
+   Recommended additional safety measures include using ssh ([262]see
    above), stunnel, or a VPN to authenticate and encrypt the viewer
-   connections or to at least use the -rfbauth passwd-file [254]option to
-   use VNC password protection (or [255]-passwdfile) It is up to YOU to
+   connections or to at least use the -rfbauth passwd-file [263]option to
+   use VNC password protection (or [264]-passwdfile) It is up to YOU to
    apply these security measures, they will not be done for you
    automatically.
 
 
-   Q-30: Can I limit which machines incoming VNC clients can connect
+   Q-31: Can I limit which machines incoming VNC clients can connect
    from?
 
-   Yes, look at the [256]-allow and [257]-localhost options to limit
+   Yes, look at the [265]-allow and [266]-localhost options to limit
    connections by hostname or IP address. E.g.
   x11vnc -allow 192.168.0.1,192.168.0.2
 
@@ -2115,11 +2343,11 @@ ls -l "$file"
    Note that -localhost is the same as "-allow 127.0.0.1"
 
    For more control, build libvncserver with libwrap support
-   [258](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+   [267](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
    for complete details.
 
 
-   Q-31: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
+   Q-32: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
    support?
 
    Here is one way to pass this information to the configure script:
@@ -2135,50 +2363,50 @@ ls -l "$file"
    is "vnc", e.g.:
   vnc: 192.168.100.3 .example.com
 
-   Note that if you run x11vnc out of [259]inetd you do not need to build
+   Note that if you run x11vnc out of [268]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.
 
 
-   Q-32: Can I have x11vnc only listen on one network interface (e.g.
+   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?
 
-   As of Mar/2005 in the libvncserver CVS, there is the "[260]-listen
+   As of Mar/2005 in the libvncserver CVS, there is the "[269]-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 "[261]-allow host1,..." option to allow only specific hosts
+   use the "[270]-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 [262]-localhost now implies "-listen localhost" since that
+   The option [271]-localhost now implies "-listen localhost" since that
    is what most people expect it to do.
 
 
-   Q-33: Now that -localhost implies listening only on the loopback
+   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?
 
-   To do this specify "[263]-allow localhost". Unlike [264]-localhost
+   To do this specify "[272]-allow localhost". Unlike [273]-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
    connection from a remote host.
 
    Note that if you do a lot of changing of the listening interface
-   ([265]-listen option) via remote control or gui, you may need to also
-   manually adjust the [266]-allow list if you unexpectedly get into a
+   ([274]-listen option) via remote control or gui, you may need to also
+   manually adjust the [275]-allow list if you unexpectedly get into a
    state where the allow list cannot match any hosts that would be coming
-   in on the listening interface. If you just toggle [267]-localhost on
+   in on the listening interface. If you just toggle [276]-localhost on
    and off x11vnc should see to it that you never get into such a state.
 
 
-   Q-34: How can I tunnel my connection to x11vnc via an encrypted SSH
+   Q-35: 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 [268]how to tunnel VNC via
+   See the description earlier on this page on [277]how to tunnel VNC via
    SSH from Unix to Unix. A number of ways are described along with some
    issues you may encounter.
 
@@ -2186,10 +2414,10 @@ ls -l "$file"
    VPNs, etc.
 
 
-   Q-35: How can I tunnel my connection to x11vnc via an encrypted SSH
+   Q-36: How can I tunnel my connection to x11vnc via an encrypted SSH
    channel from Windows using an SSH client like Putty?
 
-   [269]Above we described how to tunnel VNC via SSH from Unix to Unix,
+   [278]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
@@ -2212,8 +2440,8 @@ ls -l "$file"
    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.
 
-   For extra protection feel free to run x11vnc with the [270]-localhost
-   and [271]-rfbauth/[272]-passwdfile options.
+   For extra protection feel free to run x11vnc with the [279]-localhost
+   and [280]-rfbauth/[281]-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
@@ -2221,22 +2449,22 @@ ls -l "$file"
    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 [273]chaining ssh's.
+   automated by [282]chaining ssh's.
 
-   As discussed [274]above another option is to first start the VNC
+   As discussed [283]above another option is to first start the VNC
    viewer in "listen" mode, and then launch x11vnc with the
-   "[275]-connect localhost" option to establish the reverse connection.
+   "[284]-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).
 
 
-   Q-36: Can I prompt the user at the local X display whether the
+   Q-37: 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?
 
-   Yes, look at the "[276]-accept command" option, it allows you to
+   Yes, look at the "[285]-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
@@ -2255,7 +2483,7 @@ ls -l "$file"
    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 [277]-viewonly option has been
+   mouse on the "View" button. If the [286]-viewonly option has been
    supplied, the "View" action will not be present: the whole display is
    view only in that case.
 
@@ -2271,7 +2499,7 @@ ls -l "$file"
    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 [278]ftp://ftp.x.org/
+   is available at [287]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
@@ -2310,7 +2538,7 @@ elif [ $rc = 4 ]; then
 fi
 exit 1
 
-   Stefan Radman has written a nice dtksh script [279]dtVncPopup for use
+   Stefan Radman has written a nice dtksh script [288]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.
@@ -2319,14 +2547,14 @@ 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 "[280]-gone
+   To run a command when a client disconnects, use the "[289]-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").
 
 
-   Q-37: Does x11vnc support Unix usernames and passwords? Can I further
+   Q-38: Does x11vnc support Unix usernames and passwords? Can I further
    limit the set of Unix usernames who can connect to the VNC desktop?
 
    Until the VNC protocol and libvncserver support this things will be
@@ -2334,13 +2562,13 @@ exit 1
    such support.
 
    One approximate method involves starting x11vnc with the
-   [281]-localhost option. This basically requires the viewer user to log
+   [290]-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 username
    -L 5900:localhost:5900 hostname ..." See the ssh wrapper scripts
-   mentioned [282]elsewhere on this page. Of course a malicious user
+   mentioned [291]elsewhere on this page. 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 watch out for is a
    malicious user on the viewer side (where ssh is running) trying to
@@ -2349,7 +2577,7 @@ exit 1
    Regarding limiting the set of Unix usernames who can connect, the
    traditional way would be to further require a VNC password to supplied
    (-rfbauth, -passwd, etc). A scheme that avoids a second password
-   involves using the [283]-accept option that runs a program to examine
+   involves using the [292]-accept option that runs a program to examine
    the connection information to determine which user is connecting from
    the local machine. For example, the program could use the ident
    service on the local machine (normally ident should not be trusted
@@ -2378,11 +2606,11 @@ exit 1  # reject it
    UsePrivilegeSeparation must be enabled.
 
 
-   Q-38: I start x11vnc as root because it is launched via inetd(1) or a
+   Q-39: I start x11vnc as root because it is launched via inetd(1) or a
    display manager like gdm(1). Can I have x11vnc later switch to a
    different user?
 
-   As of Feb/2005 x11vnc has the [284]-users option that allows things
+   As of Feb/2005 x11vnc has the [293]-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.
@@ -2391,7 +2619,7 @@ exit 1  # reject it
    user nobody right after connections to the X display are established.
 
 
-   Q-39: I use a screen-lock when I leave my workstation (e.g.
+   Q-40: 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
@@ -2404,7 +2632,7 @@ exit 1  # reject it
 
    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 [285]blockdpy.c The idea behind it is simple (but
+   source for it is [294]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
@@ -2420,16 +2648,16 @@ exit 1  # reject it
    bulletproof. A really robust solution would likely require X server
    and perhaps even video hardware support.
 
-   The blockdpy utility is launched by the [286]-accept option and told
-   to exit via the [287]-gone option (the vnc client user should
+   The blockdpy utility is launched by the [295]-accept option and told
+   to exit via the [296]-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.
 
 
-   Q-40: Can I have x11vnc automatically lock the screen when I
+   Q-41: Can I have x11vnc automatically lock the screen when I
    disconnect the VNC viewer?
 
-   Yes, a user mentions he uses the [288]-gone option under CDE to run a
+   Yes, a user mentions he uses the [297]-gone option under CDE to run a
    screen lock program:
   x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
 
@@ -2438,7 +2666,7 @@ exit 1  # reject it
   x11vnc -display :0 -forever -gone 'kdesktop_lock'
   x11vnc -display :0 -forever -gone 'xlock &'
 
-   Here is a scheme using the [289]-afteraccept option (in version 0.7.3)
+   Here is a scheme using the [298]-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
@@ -2466,7 +2694,7 @@ fi
 
    [Display Managers and Services]
 
-   Q-41: How can I run x11vnc as a "service" that is always available?
+   Q-42: How can I run x11vnc as a "service" that is always available?
 
    There are a number of ways to do this. The primary thing you need to
    decide is whether you want x11vnc to connect to the X session on the
@@ -2477,11 +2705,11 @@ fi
    need to have sufficient permissions to connect to the X display.
 
    Here are some ideas:
-     * Use the description under "Continuously" in the [290]FAQ on x11vnc
+     * Use the description under "Continuously" in the [299]FAQ on x11vnc
        and Display Managers
-     * Use the description in the [291]FAQ on x11vnc and inetd(1)
+     * Use the description in the [300]FAQ on x11vnc and inetd(1)
      * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
-     * Although less reliable, see the [292]x11vnc_loop rc.local hack
+     * Although less reliable, see the [301]x11vnc_loop rc.local hack
        below.
 
    The display manager scheme will not be specific to which user has the
@@ -2500,7 +2728,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
    plus any other options you desire.
 
 
-   Q-42: How can I use x11vnc to connect to an X login screen like xdm,
+   Q-43: 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).
 
@@ -2512,7 +2740,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 [293]-auth option sets the XAUTHORITY variable for you).
+   (the [302]-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
@@ -2537,7 +2765,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
-   [294]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+   [303]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
@@ -2600,7 +2828,7 @@ rever -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 [295]full details
+   killed immediately after the user logs in. Here are [304]full details
    on how to configure gdm
      _________________________________________________________________
 
@@ -2642,23 +2870,23 @@ rever -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: [296]x11vnc_loop It will need some local
+   file like rc.local: [305]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.
 
    If the machine is a traditional Xterminal you may want to read
-   [297]this FAQ.
+   [306]this FAQ.
 
 
-   Q-43: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
+   Q-44: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
 
    Yes, perhaps a line something like this in /etc/inetd.conf will do it
    for you:
 
   5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
 
-   where the shell script /usr/local/bin/x11vnc_sh uses the [298]-inetd
+   where the shell script /usr/local/bin/x11vnc_sh uses the [307]-inetd
    option and looks something like (you'll need to customize to your
    settings).
 #!/bin/sh
@@ -2671,7 +2899,7 @@ rever -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 [299]-quiet) option: "/usr/local/bin/x11vnc -q
+   specify the -q (aka [308]-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
@@ -2679,7 +2907,7 @@ rever -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 [300]-auth to point to the
+   Note also the need to set XAUTHORITY via [309]-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
@@ -2743,21 +2971,21 @@ service x11vncservice
    capture a log)
 
 
-   Q-44: Can I have x11vnc restart itself after it terminates?
+   Q-45: Can I have x11vnc restart itself after it terminates?
 
    One could do this in a shell script, but now there is an option
-   [301]-loop that makes it easier. Of course when x11vnc restarts it
+   [310]-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"
    to sleep 2000 ms and only restart 5 times.
 
 
-   Q-45: How do I make x11vnc work with the Java VNC viewer applet in a
+   Q-46: How do I make x11vnc work with the Java VNC viewer applet in a
    web browser?
 
    To have x11vnc serve up a Java VNC viewer applet to any web browsers
-   that connect to it, run x11vnc with this [302]option:
+   that connect to it, run x11vnc with this [311]option:
   -httpdir /path/to/the/java/classes/dir
 
    (this directory will contain the files index.vnc and, for example,
@@ -2776,7 +3004,7 @@ service x11vncservice
    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 [303]-http option will try to guess where the Java
+   As of May/2005 the [312]-http option will try to guess where the Java
    classes jar file is by looking a expected locations.
 
    Also note that if you wanted to, you could also start the Java viewer
@@ -2784,13 +3012,13 @@ service x11vncservice
    either the java or appletviewer commands to run the program.
 
 
-   Q-46: Are reverse connections (i.e. the VNC server connecting to the
+   Q-47: Are reverse connections (i.e. the VNC server connecting to the
    VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
 
    As of Mar/2004 in the libvncserver CVS 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 [304]-connect option. To connect immediately
+   starts up x11vnc with the [313]-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). If a file is specified instead: -connect /path/to/some/file
@@ -2798,7 +3026,7 @@ service x11vncservice
    hosts to connect to.
 
    To use the vncconnect(1) program (from the core VNC package at
-   www.realvnc.com) specify the [305]-vncconnect option to x11vnc (Note:
+   www.realvnc.com) specify the [314]-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
@@ -2812,7 +3040,7 @@ service x11vncservice
 xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
 
 
-   Q-47: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
+   Q-48: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
    display, but for a virtual one I keep around).
 
    You can, but you would not be doing this for performance reasons (for
@@ -2842,7 +3070,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
-   [306]-add_keysyms option to have keysyms added automatically. Also, to
+   [315]-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"
@@ -2864,11 +3092,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) [307]switching even though it
+   Linux Virtual Console/Terminal (VC/VT) [316]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 [308]Xdummy that allows you to
+   Jul/2005 we have an LD_PRELOAD script [317]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
@@ -2888,7 +3116,7 @@ startx -- /path/to/Xdummy :1
    testing x11vnc).
 
 
-   Q-48: How can I use x11vnc on "headless" machines? Why might I want
+   Q-49: How can I use x11vnc on "headless" machines? Why might I want
    to?
 
    An interesting application of x11vnc is to let it export displays of
@@ -2900,7 +3128,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 [309]this FAQ) and access it from
+   display via x11vnc (e.g. see [318]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
@@ -2925,7 +3153,7 @@ startx -- /path/to/Xdummy :1
 
    [Resource Usage and Performance]
 
-   Q-49: I have lots of memory, but why does x11vnc fail with    shmget:
+   Q-50: 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)?
 
@@ -2943,7 +3171,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 [310]shm_clear to list and prompt for removal
+   Here is a shell script [319]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,
@@ -2977,40 +3205,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
-   [311]-onetile option (corresponds to only 3 shm segments used, and
+   [320]-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
-   [312]-noshm option. Performance will be somewhat degraded but when
+   [321]-noshm option. Performance will be somewhat degraded but when
    done over local machine sockets it should be acceptable (see an
-   [313]earlier question discussing -noshm).
+   [322]earlier question discussing -noshm).
 
 
-   Q-50: How can I make x11vnc use less system resources?
+   Q-51: How can I make x11vnc use less system resources?
 
-   The [314]-nap and "[315]-wait n" (where n is the sleep between polls
+   The [323]-nap and "[324]-wait n" (where n is the sleep between polls
    in milliseconds, the default is 30 or so) option are good places to
    start. 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
-   [316]-onetile option will use less memory and use fewer shared memory
-   slots (add [317]-fs 1.0 for one less slot).
+   [325]-onetile option will use less memory and use fewer shared memory
+   slots (add [326]-fs 1.0 for one less slot).
 
 
-   Q-51: How can I make x11vnc use MORE system resources?
+   Q-52: How can I make x11vnc use MORE system resources?
 
-   You can try [318]-threads and dial down the wait time (e.g. -wait 1)
-   and possibly dial down [319]-defer as well. Note that if you try to
+   You can try [327]-threads and dial down the wait time (e.g. -wait 1)
+   and possibly dial down [328]-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 [320]-id option) can be streamed over a LAN or wireless at
+   the x11vnc [329]-id option) can be streamed over a LAN or wireless at
    a reasonable frame rate.
 
 
-   Q-52: I use x11vnc over a slow link with high latency (e.g. dialup
+   Q-53: I use x11vnc over a slow link with high latency (e.g. dialup
    modem), is there anything I can do to speed things up?
 
    Some things you might want to experiment with (many of which will help
@@ -3022,16 +3250,16 @@ 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
-       [321]-solid [color] option to try to do this automatically.
+       [330]-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
        bandwidth" theme you can easily switch into and out of.
      * 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 [322]-scrollcopyrect is active and
+       problem in x11vnc 0.7.2 if [331]-scrollcopyrect is active and
        detecting scrolls for the application).
-     * If the [323]-wireframe option is not available (earlier than
+     * If the [332]-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)
@@ -3051,7 +3279,7 @@ ied)
        noticed.
 
      VNC viewer parameters:
-     * Use a [324]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+     * Use a [333]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
@@ -3074,32 +3302,32 @@ ied)
        file.
 
      x11vnc parameters:
-     * Try using [325]-nodragging (no screen updates when dragging mouse,
+     * Try using [334]-nodragging (no screen updates when dragging mouse,
        but sometimes you miss visual feedback)
-     * Make sure the [326]-wireframe option is active (it should be on by
+     * Make sure the [335]-wireframe option is active (it should be on by
        default) and you have Opaque Moves/Resizes Enabled in the window
        manager.
-     * Make sure the [327]-scrollcopyrect option is active (it should be
+     * Make sure the [336]-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.
-     * Set [328]-fs 1.0 (disables fullscreen updates)
-     * Try increasing [329]-wait or [330]-defer (reduces the maximum
+     * Set [337]-fs 1.0 (disables fullscreen updates)
+     * Try increasing [338]-wait or [339]-defer (reduces the maximum
        "frame rate", but won't help much for large screen changes)
-     * Try the [331]-progressive pixelheight mode with the block
+     * Try the [340]-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 [332]-id (cuts
+     * If you just want to watch one (simple) window use [341]-id (cuts
        down extraneous polling and updates, but can be buggy or
        insufficient)
-     * Set [333]-nosel (disables all clipboard selection exchange)
-     * Use [334]-nocursor and [335]-nocursorpos (repainting the remote
+     * Set [342]-nosel (disables all clipboard selection exchange)
+     * Use [343]-nocursor and [344]-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
-       [336]-readtimeout n setting if it sometimes takes more than 20sec
+       [345]-readtimeout n setting if it sometimes takes more than 20sec
        to paint the full screen, etc.
 
 
-   Q-53: Does x11vnc support the X DAMAGE Xserver extension to find
+   Q-54: Does x11vnc support the X DAMAGE Xserver extension to find
    modified regions of the screen quickly and efficiently?
 
    Yes, as of Mar/2005 in the libvncserver CVS x11vnc will use the X
@@ -3117,7 +3345,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 [337]slow (e.g.
+   in main memory. So reading the fb is still painfully [346]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
@@ -3135,27 +3363,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 "[338]-xd_area A" option to adjust the size
+   skipped). You can use the "[347]-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 "[339]-xd_mem f" may also be of use in tuning the
-   algorithm. To disable using DAMAGE entirely use "[340]-noxdamage".
+   The option "[348]-xd_mem f" may also be of use in tuning the
+   algorithm. To disable using DAMAGE entirely use "[349]-noxdamage".
 
 
-   Q-54: When I drag windows around with the mouse or scroll up and down
+   Q-55: 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 [341]slow hardware read rates from
+   This problem is primarily due to [350]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
-   [342]-pointer_mode option for more info. The next bottleneck is
+   [351]-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
@@ -3165,31 +3393,31 @@ ied)
    tree. The 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 "[343]-pointer_mode 1" option.
+   way via the "[352]-pointer_mode 1" option.
 
-   Also added was the [344]-nodragging option that disables all screen
+   Also added was the [353]-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 in the libvncserver CVS the [345]-pointer_mode n option
+   As of Dec/2004 in the libvncserver CVS the [354]-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 [346]-threads option can improve
+   Also, in some circumstances the [355]-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 in the libvncserver CVS two new options (see the
-   [347]wireframe FAQ and [348]scrollcopyrect FAQ below) provide schemes
+   [356]wireframe FAQ and [357]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.
 
 
-   Q-55: Why not do something like wireframe animations to avoid the
+   Q-56: Why not do something like wireframe animations to avoid the
    windows "lurching" when being moved or resized?
 
    Nice idea for a hack! As of Apr/2005 in the libvncserver CVS x11vnc by
@@ -3200,8 +3428,8 @@ ied)
    shown. When 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 [349]slow video
-   card read rates (see [350]here too). A displacement, even a small one,
+   of the intermediate steps. BTW the lurching is due to [358]slow video
+   card read rates (see [359]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.
 
@@ -3209,7 +3437,7 @@ ied)
    for -wireframe to do any good.
 
    The mode is currently on by default because most people are inflicted
-   with the problem. It can be disabled with the [351]-nowireframe option
+   with the problem. It can be disabled with the [360]-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
@@ -3254,13 +3482,13 @@ ied)
      * Maximum time to show a wireframe animation.
      * Minimum time between sending wireframe outlines.
 
-   See the [352]"-wireframe tweaks" option for more details. On a slow
+   See the [361]"-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
-   [353]"-wirecopyrect mode" option. It is also on by default. This
+   [362]"-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
@@ -3291,7 +3519,7 @@ ied)
    -nowirecopyrect if this or other painting errors are unacceptable.
 
 
-   Q-56: Can x11vnc try to apply heuristics to detect when an window is
+   Q-57: Can x11vnc try to apply heuristics to detect when an window is
    scrolling its contents and use the CopyRect encoding for a speedup?
 
    Another nice idea for a hack! As of May/2005 in the libvncserver CVS
@@ -3308,7 +3536,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 [354]slow).
+   the hardware framebuffer is [363]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.
@@ -3330,10 +3558,10 @@ ied)
    the X server display: if one falls too far behind it could become a
    mess...
 
-   The initial implementation of [355]-scrollcopyrect option is useful in
+   The initial implementation of [364]-scrollcopyrect option is useful in
    that it detects many scrolls and thus gives a much nicer working
-   environment (especially when combined with the [356]-wireframe
-   [357]-wirecopyrect [358]options, which are also on by default; and if
+   environment (especially when combined with the [365]-wireframe
+   [366]-wirecopyrect [367]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.
@@ -3366,10 +3594,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: [359]-fixscreen
+       also: [368]-fixscreen
      * Some applications, notably OpenOffice, do XCopyArea scrolls in
        weird ways that assume ancestor window clipping is taking place.
-       See the [360]-scr_skip option for ways to tweak this on a
+       See the [369]-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
@@ -3386,7 +3614,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 [361]-scale option there will be a quick CopyRect
+     * When using the [370]-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
@@ -3399,7 +3627,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 [362]-noscrollcopyrect (or -noscr for short). If you find
+   with the [371]-noscrollcopyrect (or -noscr for short). If you find
    some extremely bad and repeatable behavior for -scrollcopyrect please
    report a bug.
 
@@ -3423,7 +3651,7 @@ ied)
 
    [Mouse Cursor Shapes]
 
-   Q-57: Why isn't the mouse cursor shape (the little icon shape where
+   Q-58: Why isn't the mouse cursor shape (the little icon shape where
    the mouse pointer is) correct as I move from window to window?
 
    On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it
@@ -3438,16 +3666,16 @@ 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 "[363]-cursor X" option that
+   A simple kludge is provided by the "[372]-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 "[364]-cursor some" option for
+   work for those cases. Also see the "[373]-cursor some" option for
    additional kludges.
 
    Note that as of Aug/2004 in the libvncserver CVS, on Solaris using the
    SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse
-   cursor when the [365]-overlay option is supplied. See [366]this FAQ
+   cursor when the [374]-overlay option is supplied. See [375]this FAQ
    for more info.
 
    Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support
@@ -3455,7 +3683,7 @@ ied)
    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 [367]Solaris 10.
+   distros and [376]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
@@ -3463,10 +3691,10 @@ 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. [368]Details can be found here.
+   hidden alpha channel data under 32bpp. [377]Details can be found here.
 
 
-   Q-58: When using XFIXES cursorshape mode, some of the cursors look
+   Q-59: 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?
 
@@ -3496,17 +3724,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 "[369]-alphacut n" option lets
+   course!) some tunable parameters. The "[378]-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 "[370]-alphafrac f" option tries to correct individual
+   240. The "[379]-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 [371]-alpharemove that is useful for
+   Finally, there is an option [380]-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
@@ -3524,7 +3752,7 @@ ied)
    heavily on redglass) look fine with the apparent default of alphacut:255.
 
 
-   Q-59: In XFIXES mode, are there any hacks to handle cursor
+   Q-60: In XFIXES mode, are there any hacks to handle cursor
    transparency ("alpha channel") exactly?
 
    As of Jan/2005 in the CVS, libvncserver has been modified to allow an
@@ -3532,11 +3760,11 @@ ied)
    send the 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 [372]-nocursorshape x11vnc option.
+   disabled for all clients with the [381]-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
-   [373]-noalphablend option to disable this behavior (always approximate
+   [382]-noalphablend option to disable this behavior (always approximate
    transparent cursors with opaque RGB values).
 
    The CursorShapeUpdates VNC extension complicates matters because the
@@ -3561,12 +3789,12 @@ ied)
 
    [Mouse Pointer]
 
-   Q-60: Why does the mouse arrow just stay in one corner in my
+   Q-61: 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 [374]tightvnc extension
+   This default takes advantage of a [383]tightvnc extension
    (CursorShapeUpdates) that allows specifying a cursor image shape for
-   the local VNC viewer. You may disable it with the [375]-nocursor
+   the local VNC viewer. You may disable it with the [384]-nocursor
    option to x11vnc if your viewer does not have this extension.
 
    Note: as of Aug/2004 in the libvncserver CVS this should be fixed: the
@@ -3575,23 +3803,23 @@ ied)
    framebuffer. This can also be disabled via -nocursor.
 
 
-   Q-61: Can I take advantage of the TightVNC extension to the VNC
+   Q-62: 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)?
 
-   Use the [376]-cursorpos option when starting x11vnc. A VNC viewer must
+   Use the [385]-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 in the
-   libvncserver CVS -cursorpos is the default. See also [377]-nocursorpos
-   and [378]-nocursorshape.
+   libvncserver CVS -cursorpos is the default. See also [386]-nocursorpos
+   and [387]-nocursorshape.
 
 
-   Q-62: Is it possible to swap the mouse buttons (e.g. left-handed
+   Q-63: 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: [379]-buttonmap
+   You can remap the mouse buttons via something like: [388]-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.
@@ -3599,7 +3827,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 [380]-debug_pointer option prints out much info for
+   Note that the [389]-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
@@ -3621,7 +3849,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 [381]-buttonmap but rather configuring the X server
+   consider not using [390]-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"').
 
@@ -3648,10 +3876,10 @@ ied)
    "click" usually gives a multi-line scroll).
    [Keyboard Issues]
 
-   Q-63: How can I get my AltGr and Shift modifiers to work between
+   Q-64: How can I get my AltGr and Shift modifiers to work between
    keyboards for different languages?
 
-   The option [382]-modtweak should help here. It is a mode that monitors
+   The option [391]-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.
@@ -3660,21 +3888,21 @@ ied)
    default (use -nomodtweak 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 [383]this FAQ
+   and ">" it. This key does not exist on the keyboard (see [392]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 [384]FAQ about the -xkb option for a more powerful method
+   Also see the [393]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
-   [385]-debug_keyboard option prints out much info for every keystroke
+   [394]-debug_keyboard option prints out much info for every keystroke
    and so can be useful debugging things.
 
 
-   Q-64: When I try to type a "<" (i.e. less than) instead I get ">"
+   Q-65: When I try to type a "<" (i.e. less than) instead I get ">"
    (i.e. greater than)! Strangely, typing ">" works OK!!
 
    Does your keyboard have a single key with both "<" and ">" on it? Even
@@ -3682,9 +3910,9 @@ ied)
    (e.g. pc105 in the XF86Config file when it should be something else,
    say pc104).
 
-   Short Cut: Try the [386]-xkb or [387]-sloppy_keys options and see if
+   Short Cut: Try the [395]-xkb or [396]-sloppy_keys options and see if
    that helps the situation. The discussion below is a bit outdated (e.g.
-   [388]-modtweak is now the default) but is useful reference for various
+   [397]-modtweak is now the default) but is useful reference for various
    tricks and so is kept.
 
 
@@ -3727,34 +3955,34 @@ ied)
    -remap less-comma
 
    These are convenient in that they do not modify the actual X server
-   settings. The former ([389]-modtweak) is a mode that monitors the
+   settings. The former ([398]-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 ([390]-remap less-comma) is an immediate remapping of the
+   The latter ([399]-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 [391]FAQ about the -xkb option as a possible workaround
+   See also the [400]FAQ about the -xkb option as a possible workaround
    using the XKEYBOARD extension.
 
-   Note that the [392]-debug_keyboard option prints out much info for
+   Note that the [401]-debug_keyboard option prints out much info for
    every keystroke to aid debugging keyboard problems.
 
 
-   Q-65: When I try to type a "<" (i.e. less than) instead I get "<,"
+   Q-66: When I try to type a "<" (i.e. less than) instead I get "<,"
    (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 [393]keymapping
+   the Shift key before releasing the "<". Because of a [402]keymapping
    ambiguity the last event "< up" is interpreted as "," because that key
    unshifted is the comma.
 
-   This should not happen in [394]-xkb mode, because it works hard to
+   This should not happen in [403]-xkb mode, because it works hard to
    resolve the ambiguities. If you do not want to use -xkb, try the
-   option [395]-sloppy_keys to attempt a similar type of algorithm.
+   option [404]-sloppy_keys to attempt a similar type of algorithm.
 
 
-   Q-66: I'm using an "international" keyboard (e.g. German "de", or
+   Q-67: 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
@@ -3775,7 +4003,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 [396]-modtweak
+   This all worked fine with x11vnc running with the [405]-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
@@ -3793,7 +4021,7 @@ ied)
      * there is a new option -xkb to use the XKEYBOARD extension API to
        do the Modifier key tweaking.
 
-   The [397]-xkb option seems to fix all of the missing keys: "@", "<",
+   The [406]-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
@@ -3801,7 +4029,7 @@ ied)
    debugging output (send it along with any problems you report).
 
    Update: as of Jun/2005 x11vnc will try to automatically enable
-   [398]-xkb if it appears that would be beneficial (e.g. if it sees any
+   [407]-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.
 
@@ -3816,7 +4044,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:
-       [399]-skip_keycodes 93
+       [408]-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
@@ -3833,16 +4061,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 [400]-remap x11vnc option:
+       created using the [409]-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
-       [401]-add_keysyms option in the next paragraph.
-       Update: for convenience "[402]-remap DEAD" does many of these
+       [410]-add_keysyms option in the next paragraph.
+       Update: for convenience "[411]-remap DEAD" does many of these
        mappings at once.
-     * To complement the above workaround using the [403]-remap, an
-       option [404]-add_keysyms was added. This option instructs x11vnc
+     * To complement the above workaround using the [412]-remap, an
+       option [413]-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
@@ -3853,7 +4081,7 @@ ied)
        disable.
 
 
-   Q-67: When typing I sometimes get double, triple, or more of my
+   Q-68: 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?
 
    This may be due to an interplay between your X server's key autorepeat
@@ -3861,7 +4089,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) [405]-norepeat x11vnc option. You will still
+   use the new (Jul/2004) [414]-norepeat x11vnc option. You will still
    have autorepeating because that is taken care of on your VNC viewer
    side.
 
@@ -3885,18 +4113,18 @@ 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 [406]-norepeat (which has since Dec/2004 been
+   needed, or to use the [415]-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
    working at the physical display and misses his autorepeating.
 
 
-   Q-68: The x11vnc -norepeat mode is in effect, but I still get repeated
+   Q-69: The x11vnc -norepeat mode is in effect, but I still get repeated
    keystrokes!!
 
    Are you using x11vnc to log in to an X session? (as described in
-   [407]this FAQ) If so, x11vnc is starting before your session and it
+   [416]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 trying to be
@@ -3916,11 +4144,11 @@ ied)
    should figure out how to disable that somehow.
 
 
-   Q-69: The machine where I run x11vnc has an AltGr key, but the local
+   Q-70: 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?
 
-   Something like "[408]-remap Super_R-Mode_switch" x11vnc option may
+   Something like "[417]-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)).
@@ -3931,7 +4159,7 @@ ied)
    specify remappings from a file.
 
 
-   Q-70: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
+   Q-71: 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)
@@ -3943,18 +4171,18 @@ 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 [409]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+   the [418]-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.
 
 
-   Q-71: Can I map a keystroke to a mouse button click on the remote
+   Q-72: Can I map a keystroke to a mouse button click on the remote
    machine?
 
    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 [410]-remap
+   have x11vnc do the remapping. This can be done via the [419]-remap
    option using the fake "keysyms" Button1, Button2, etc. as the "to"
    keys (i.e. the ones after the "-")
 
@@ -3963,7 +4191,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:
-  [411]-remap Super_R-Button2
+  [420]-remap Super_R-Button2
 
    maps the Super_R "flag" key press to the Button2 click, thereby making
    X pasting a bit easier.
@@ -3974,7 +4202,7 @@ ied)
 
    [Screen Related Issues and Features]
 
-   Q-72: The remote display is larger (in number of pixels) than the
+   Q-73: 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?
 
@@ -3993,15 +4221,15 @@ 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
-   [412]this FAQ on x11vnc scaling.
+   [421]this FAQ on x11vnc scaling.
 
 
-   Q-73: Does x11vnc support server-side framebuffer scaling? (E.g. to
+   Q-74: Does x11vnc support server-side framebuffer scaling? (E.g. to
    make the desktop smaller).
 
    As of Jun/2004 in the libvncserver CVS x11vnc provides basic
    server-side scaling. It is a global scaling of the desktop, not a
-   per-client setting. To enable it use the "[413]-scale fraction"
+   per-client setting. To enable it use the "[422]-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 2/3). Note
    that if fraction is greater than one the display is magnified.
@@ -4022,7 +4250,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
-   [414]applications. Since with integer scale factors the framebuffers
+   [423]applications. Since with integer scale factors the framebuffers
    become huge and scaling operations time consuming, be sure to use
    ":nb" for the fastest response.
 
@@ -4048,12 +4276,12 @@ 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 ([415]-rfbport option,
+   different scalings listening on separate ports ([424]-rfbport option,
    etc.).
 
    BTW, whenever you run two or more x11vnc's on the same X display and
-   use the [416]GUI, then to avoid all of the x11vnc's simultaneously
-   answering the gui you will need to use something like [417]"-connect
+   use the [425]GUI, then to avoid all of the x11vnc's simultaneously
+   answering the gui you will need to use something like [426]"-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
@@ -4062,12 +4290,12 @@ ied)
 
    Update: As of Mar/2005 in the libvncserver CVS x11vnc now scales the
    mouse cursor with the same scale factor as the screen. If you don't
-   want that, use the [418]"-scale_cursor frac" option to set the cursor
+   want that, use the [427]"-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).
 
 
-   Q-74: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
+   Q-75: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
    together to form one big, single screen).
 
    Yes, it should generally work because it simply polls the big
@@ -4084,23 +4312,23 @@ 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 [419]-blackout x11vnc option
+   may be distracting to the viewer. The [428]-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
-   [420]-xinerama x11vnc option can be used to have it automatically
+   [429]-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).
 
    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 [421]-xwarppointer
+   of the large display. If this happens try using the [430]-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
    Xinerama is enabled).
 
 
-   Q-75: Can I use x11vnc on a multi-headed display that is not Xinerama
+   Q-76: Can I use x11vnc on a multi-headed display that is not Xinerama
    (i.e. separate screens :0.0, :0.1, ... for each monitor)?
 
    You can, but it is a little bit awkward: you must start separate
@@ -4118,32 +4346,32 @@ 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 [422]FAQ to increase the limit. It
-   is probably also a good idea to run with the [423]-onetile option in
+   /etc/system as mentioned in another [431]FAQ to increase the limit. It
+   is probably also a good idea to run with the [432]-onetile option in
    this case (to limit each x11vnc to 3 shm segments), or even
-   [424]-noshm to use no shm segments.
+   [433]-noshm to use no shm segments.
 
 
-   Q-76: Can x11vnc show only a portion of the display? (E.g. for a
+   Q-77: Can x11vnc show only a portion of the display? (E.g. for a
    special purpose rfb application).
 
-   As of Mar/2005 in the libvncserver CVS x11vnc has the "[425]-clip
+   As of Mar/2005 in the libvncserver CVS x11vnc has the "[434]-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 [426]Xinerama screen into two more managable smaller screens.
+   large [435]Xinerama screen into two more managable smaller screens.
 
    This also works to view a sub-region of a single application window if
-   the [427]-id or [428]-sid options are used. The offset is measured
+   the [436]-id or [437]-sid options are used. The offset is measured
    from the upper left corner of the selected window.
 
 
-   Q-77: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection)
+   Q-78: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection)
    extension? Whenever I rotate or resize the screen x11vnc just seems to
    crash.
 
    As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You
-   enable it with the [429]-xrandr option to make x11vnc monitor XRANDR
+   enable it with the [438]-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.
@@ -4153,7 +4381,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 [430]-padgeom option to make the region big
+   viewers you can try the [439]-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
@@ -4162,13 +4390,13 @@ ied)
    terminate.
 
 
-   Q-78: Why is the view in my VNC viewer completely black? Or why is
+   Q-79: Why is the view in my VNC viewer completely black? Or why is
    everything flashing around randomly?
 
    See the next FAQ for a possible explanation.
 
 
-   Q-79: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+   Q-80: 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
@@ -4196,7 +4424,7 @@ ied)
    "chvt 7" for VC #7.
 
 
-   Q-80: Can I use x11vnc to view my VMWare session remotely?
+   Q-81: Can I use x11vnc to view my VMWare session remotely?
 
    Yes, since VMWare is an X application you can view it via x11vnc in
    the normal way.
@@ -4207,9 +4435,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 [431]this FAQ
+   desktop in a separate Virtual Console (e.g. VC 8) (see [440]this FAQ
    on VC's for background). Unfortunately, this Fullscreen VC is not an X
-   server. So x11vnc cannot access it (however, [432]see this for a
+   server. So x11vnc cannot access it (however, [441]see this for a
    possible partial workaround). x11vnc works fine with "Normal X
    application window" and "Quick-Switch mode" because these use X.
 
@@ -4226,13 +4454,13 @@ ied)
    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 [433]is in the active VC.
+   as long as the VMWare X session [442]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 [434]-id windowid option. The
+   the VMWare menu buttons) by use of the [443]-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
@@ -4241,7 +4469,7 @@ ied)
    mouse)).
 
 
-   Q-81: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
+   Q-82: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
    controlled by x11vnc?
 
    As of Apr/2005 in the libvncserver CVS there is rudimentary support
@@ -4313,7 +4541,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. Of course for the case
-   of Xvfb x11vnc can poll it much better via the [435]X API, but you get
+   of Xvfb x11vnc can poll it much better via the [444]X API, but you get
    the idea.
 
    By default in -rawfb mode x11vnc will actually close any X display it
@@ -4366,7 +4594,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 [436]active VC) one
+   view and interact with VC #2 (assuming it is the [445]active VC) one
    can run something like:
   x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
 
@@ -4379,7 +4607,7 @@ ied)
    more accurate and faster LinuxVNC program. The only advantage x11vnc
    -rawfb might have is that it can presumably allow interaction with a
    non-text application, e.g. one based on svgalib. For example the
-   [437]VMWare Fullscreen mode is actually viewable under -rawfb. But
+   [446]VMWare Fullscreen mode is actually viewable under -rawfb. But
    this isn't much use until one figures out how to inject keystrokes and
    mouse events...
 
@@ -4390,7 +4618,7 @@ ied)
    program that passes the framebuffer to libvncserver.
 
 
-   Q-82: I am using x11vnc where my local machine has "popup/hidden
+   Q-83: 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
@@ -4405,31 +4633,31 @@ ied)
 
    [Misc: Clipboard, Beeps, Thanks, etc.]
 
-   Q-83: Does the Clipboard/Selection get transferred between the
+   Q-84: Does the Clipboard/Selection get transferred between the
    vncviewer and the X display?
 
    As of Jan/2004 in the libvncserver CVS x11vnc supports the "CutText"
    part of the rfb protocol. Furthermore, x11vnc is able to hold the
    PRIMARY selection (Xvnc does not seem to do this). If you don't want
-   the Clipboard/Selection exchanged use the [438]-nosel option. If you
+   the Clipboard/Selection exchanged use the [447]-nosel option. If you
    don't want the PRIMARY selection to be polled for changes use the
-   [439]-noprimary option. You can also fine-tune it a bit with the
-   [440]-seldir dir option.
+   [448]-noprimary option. You can also fine-tune it a bit with the
+   [449]-seldir dir option.
 
    You may need to watch out for desktop utilities such as KDE's
    "Klipper" that do odd things with the selection, clipboard, and
    cutbuffers.
 
 
-   Q-84: Can I transfer files back and forth with x11vnc?
+   Q-85: Can I transfer files back and forth with x11vnc?
 
    As of Oct/2005 x11vnc enables the TightVNC file transfer
    implementation that was added to libvncserver. This currently only
    works with TightVNC viewers (and Windows only it appears). It is on by
-   default, to disable it use the [441]-nofilexfer option.
+   default, to disable it use the [450]-nofilexfer option.
 
 
-   Q-85: Why don't I hear the "Beeps" in my X session (e.g. when typing
+   Q-86: Why don't I hear the "Beeps" in my X session (e.g. when typing
    tput bel in an xterm)?
 
    As of Dec/2003 in the libvncserver CVS "Beep" XBell events are tracked
@@ -4437,7 +4665,7 @@ ied)
    not on by default 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 [442]-nobell option. If
+   If you don't want to hear the beeps use the [451]-nobell option. If
    you want to hear the audio from the remote applications, consider
    trying a redirector such as esd.
 
@@ -4446,14 +4674,14 @@ ied)
 
     Contributions:
 
-   Q-86: Thanks for your program and for your help! Can I make a
+   Q-87: Thanks for your program and for your help! Can I make a
    donation?
 
    Please do (any amount is appreciated) and thank you for your support!
    Click on the PayPal button below for more info.
    Also, in general I always enjoy hearing from x11vnc users, how they
    use it, what new features they would like, etc.   Please send me an
-   [443]email!
+   [452]email!
 
    [PayPal]
 
@@ -4496,9 +4724,9 @@ References
   35. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
   36. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
   37. http://sourceforge.net/projects/libvncserver/
-  38. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=341817
-  39. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=341817
-  40. http://www.karlrunge.com/x11vnc/x11vnc-0.8.tar.gz
+  38. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=393257
+  39. http://sourceforge.net/project/shownotes.php?release_id=393257&group_id=32584
+  40. http://www.karlrunge.com/x11vnc/x11vnc-0.8.1.tar.gz
   41. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
   42. http://www.tightvnc.com/download.html
   43. http://www.realvnc.com/download-free.html
@@ -4506,402 +4734,411 @@ References
   45. http://www.karlrunge.com/x11vnc/rx11vnc
   46. http://www.karlrunge.com/x11vnc/rx11vnc.pl
   47. http://www.sunfreeware.com/
-  48. http://www.karlrunge.com/x11vnc/index.html#faq-build
-  49. ftp://ftp.uu.net/graphics/jpeg/
-  50. http://www.gzip.org/zlib/
-  51. http://www.sunfreeware.com/
-  52. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
-  53. http://www.karlrunge.com/x11vnc/x11vnc-0.8.tar.gz
-  54. http://www.karlrunge.com/x11vnc/bins
-  55. mailto:[email protected]
-  56. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
-  57. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
-  58. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
-  59. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
-  60. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
-  61. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
-  62. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
-  63. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
-  64. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
-  65. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
-  66. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
-  67. http://www.karlrunge.com/x11vnc/index.html#wirecopyrect
-  68. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
-  69. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
-  70. http://www.tightvnc.com/
-  71. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
-  72. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
-  73. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
-  74. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
-  75. http://wwws.sun.com/sunray/index.html
-  76. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
-  77. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
-  78. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
-  79. http://www.karlrunge.com/x11vnc/shm_clear
-  80. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
-  81. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
-  82. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
-  83. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
-  84. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
-  85. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
-  86. mailto:[email protected]
-  87. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
-  88. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
-  89. http://www.karlrunge.com/x11vnc/index.html#faq-build
-  90. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest
-  91. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
-  92. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
-  93. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
-  94. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
-  95. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
-  96. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
-  97. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
-  98. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
-  99. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations
- 100. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
- 101. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
- 102. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 103. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 104. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
- 105. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
- 106. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
- 107. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 108. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 109. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
- 110. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
- 111. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 112. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho
- 113. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 114. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd
- 115. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
- 116. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
- 117. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
- 118. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 119. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
- 120. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
- 121. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
- 122. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
- 123. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 124. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 125. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
- 126. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
- 127. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
- 128. http://www.karlrunge.com/x11vnc/index.html#faq-service
- 129. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 130. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 131. http://www.karlrunge.com/x11vnc/index.html#faq-loop
- 132. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
- 133. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
- 134. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 135. http://www.karlrunge.com/x11vnc/index.html#faq-headless
- 136. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 137. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
- 138. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
- 139. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
- 140. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
- 141. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 142. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 143. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 144. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
- 145. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
- 146. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 147. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
- 148. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
- 149. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
- 150. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
- 151. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 152. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
- 153. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 154. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
- 155. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
- 156. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
- 157. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
- 158. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
- 159. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
- 160. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 161. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 162. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
- 163. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
- 164. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
- 165. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
- 166. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 167. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 168. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 169. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
- 170. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
- 171. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
- 172. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
- 173. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 176. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 178. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 179. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 180. http://www.karlrunge.com/x11vnc/index.html#building
- 181. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 182. http://packages.debian.org/x11vnc
- 183. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 184. http://dag.wieers.com/packages/x11vnc/
- 185. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
- 186. http://www.sunfreeware.com/
- 187. http://www.bell-labs.com/project/wwexptools/packages.html
- 188. http://www.karlrunge.com/x11vnc/bins
- 189. http://www.tightvnc.com/download.html
- 190. http://www.realvnc.com/download-free.html
- 191. http://sourceforge.net/projects/cotvnc/
- 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 194. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
- 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 198. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 200. http://fredrik.hubbe.net/x2vnc.html
- 201. http://www.hubbe.net/~hubbe/win2vnc.html
- 202. http://www.deboer.gmxhome.de/
- 203. http://sourceforge.net/projects/win2vnc/
- 204. http://fredrik.hubbe.net/x2vnc.html
- 205. http://freshmeat.net/projects/x2x/
- 206. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 207. http://zapek.com/software/zvnc/
- 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 212. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+  48. http://www.karlrunge.com/x11vnc/bins
+  49. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+  50. http://www.karlrunge.com/x11vnc/index.html#faq-build
+  51. ftp://ftp.uu.net/graphics/jpeg/
+  52. http://www.gzip.org/zlib/
+  53. http://www.sunfreeware.com/
+  54. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
+  55. http://www.karlrunge.com/x11vnc/x11vnc-0.8.1.tar.gz
+  56. http://www.karlrunge.com/x11vnc/bins
+  57. mailto:[email protected]
+  58. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
+  59. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+  60. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+  61. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+  62. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+  63. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+  64. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+  65. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
+  66. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+  67. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
+  68. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+  69. http://www.karlrunge.com/x11vnc/index.html#wirecopyrect
+  70. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+  71. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+  72. http://www.tightvnc.com/
+  73. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+  74. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+  75. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+  76. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
+  77. http://wwws.sun.com/sunray/index.html
+  78. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+  79. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
+  80. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+  81. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+  82. http://www.karlrunge.com/x11vnc/vnc_findports
+  83. http://www.karlrunge.com/x11vnc/findvncports
+  84. http://www.karlrunge.com/x11vnc/shm_clear
+  85. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+  86. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+  87. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+  88. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+  89. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+  90. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+  91. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+  92. mailto:[email protected]
+  93. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+  94. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
+  95. http://www.karlrunge.com/x11vnc/index.html#faq-build
+  96. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest
+  97. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
+  98. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
+  99. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
+ 100. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
+ 101. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
+ 102. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 103. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
+ 104. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
+ 105. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations
+ 106. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
+ 107. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
+ 108. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 109. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 110. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
+ 111. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
+ 112. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
+ 113. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 114. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 115. http://www.karlrunge.com/x11vnc/index.html#faq-sunrays
+ 116. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
+ 117. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
+ 118. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 119. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho
+ 120. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 121. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd
+ 122. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
+ 123. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
+ 124. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
+ 125. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 126. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
+ 127. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
+ 128. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
+ 129. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
+ 130. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 131. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 132. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
+ 133. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
+ 134. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
+ 135. http://www.karlrunge.com/x11vnc/index.html#faq-service
+ 136. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 137. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 138. http://www.karlrunge.com/x11vnc/index.html#faq-loop
+ 139. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
+ 140. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
+ 141. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 142. http://www.karlrunge.com/x11vnc/index.html#faq-headless
+ 143. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 144. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
+ 145. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
+ 146. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
+ 147. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
+ 148. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 149. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 150. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 151. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
+ 152. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
+ 153. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 154. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
+ 155. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
+ 156. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
+ 157. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
+ 158. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 159. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
+ 160. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 161. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
+ 162. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
+ 163. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
+ 164. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
+ 165. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
+ 166. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
+ 167. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 168. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 169. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
+ 170. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
+ 171. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
+ 172. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
+ 173. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 174. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 175. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 176. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
+ 177. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
+ 178. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
+ 179. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
+ 180. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 183. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 185. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 186. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 187. http://www.karlrunge.com/x11vnc/index.html#building
+ 188. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 189. http://packages.debian.org/x11vnc
+ 190. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 191. http://dag.wieers.com/packages/x11vnc/
+ 192. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
+ 193. http://www.sunfreeware.com/
+ 194. http://www.bell-labs.com/project/wwexptools/packages.html
+ 195. http://www.karlrunge.com/x11vnc/bins
+ 196. http://www.tightvnc.com/download.html
+ 197. http://www.realvnc.com/download-free.html
+ 198. http://sourceforge.net/projects/cotvnc/
+ 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 201. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 205. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 207. http://fredrik.hubbe.net/x2vnc.html
+ 208. http://www.hubbe.net/~hubbe/win2vnc.html
+ 209. http://www.deboer.gmxhome.de/
+ 210. http://sourceforge.net/projects/win2vnc/
+ 211. http://fredrik.hubbe.net/x2vnc.html
+ 212. http://freshmeat.net/projects/x2x/
+ 213. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 214. http://zapek.com/software/zvnc/
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 219. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
  221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
  222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 223. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 230. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 231. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 243. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 253. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 254. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 255. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 258. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 259. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 268. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 269. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 273. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
- 274. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 278. ftp://ftp.x.org/
- 279. http://www.karlrunge.com/x11vnc/dtVncPopup
- 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 282. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 285. http://www.karlrunge.com/x11vnc/blockdpy.c
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 290. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 291. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 292. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 294. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 295. http://www.jirka.org/gdm-documentation/x241.html
- 296. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 297. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 307. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 308. http://www.karlrunge.com/x11vnc/Xdummy
- 309. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 310. http://www.karlrunge.com/x11vnc/shm_clear
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 313. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 324. http://www.tightvnc.com/
- 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 337. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 341. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 347. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 348. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 349. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 230. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 237. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 238. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 239. http://wwws.sun.com/sunray/index.html
+ 240. http://www.karlrunge.com/x11vnc/index.html#sunray-gotchas
+ 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 252. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
+ 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 262. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 263. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 264. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 267. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 268. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 277. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 278. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 282. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
+ 283. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 287. ftp://ftp.x.org/
+ 288. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 291. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 294. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 299. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 300. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 301. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 303. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 304. http://www.jirka.org/gdm-documentation/x241.html
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 306. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 316. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 317. http://www.karlrunge.com/x11vnc/Xdummy
+ 318. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 319. http://www.karlrunge.com/x11vnc/shm_clear
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 322. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 333. http://www.tightvnc.com/
+ 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 346. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
  350. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 354. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 358. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 366. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 367. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 368. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 374. http://www.tightvnc.com/
- 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
- 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 383. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 384. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 391. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 393. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 407. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 356. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 357. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 358. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 359. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 363. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 367. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 375. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 376. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 377. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 383. http://www.tightvnc.com/
+ 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 392. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 393. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 400. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 402. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
  409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
  411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 412. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 414. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 422. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 426. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 431. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 432. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 433. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 435. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 436. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 437. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
- 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 443. mailto:[email protected]
+ 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 416. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 421. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 423. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 431. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 435. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 440. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 441. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 442. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 444. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 445. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 446. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
+ 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 452. mailto:[email protected]
 
 
 =======================================================================
@@ -4914,7 +5151,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 lastmod: 2006-02-06
+x11vnc: allow VNC connections to real X11 displays. 0.8.1 lastmod: 2006-02-20
 
 x11vnc options:
   -display disp            -auth file             
@@ -5025,7 +5262,7 @@ libvncserver-tight-extension options:
 
 % x11vnc -help
 
-x11vnc: allow VNC connections to real X11 displays. 0.8 lastmod: 2006-02-06
+x11vnc: allow VNC connections to real X11 displays. 0.8.1 lastmod: 2006-02-20
 
 Typical usage is:
 
@@ -5181,7 +5418,7 @@ Options:
 
                        Note that even if there are *no* depth 24 visuals or
                        windows (i.e. pure 8bpp), this mode is potentially
-                       a improvement over -flashcmap because it avoids the
+                       an improvement over -flashcmap because it avoids the
                        flashing and shows each window in the correct color.
 
                        This method appear to work, but may still have bugs
@@ -5191,12 +5428,12 @@ Options:
 
                        There may be painting errors for clipping and switching
                        between windows of depths 8 and 24.  Heuristics are
-                       applied to try to minimize the painting errors.
-                       One can also press 3 Alt_L's in a row to refresh the
-                       screen if the error does not repair itself.  Also the
-                       option -fixscreen 8=3.0 or -fixscreen V=3.0 may be
-                       use to periodically refresh the screen at the cost of
-                       bandwidth (every 3 sec for this example).
+                       applied to try to minimize the painting errors.  One can
+                       also press 3 Alt_L's in a row to refresh the screen
+                       if the error does not repair itself.  Also the option
+                       -fixscreen 8=3.0 or -fixscreen V=3.0 may be used to
+                       periodically refresh the screen at the cost of bandwidth
+                       (every 3 sec for this example).
 
                        The [opts] string can contain the following settings.
                        Multiple settings are separated by commas.
@@ -5229,6 +5466,11 @@ Options:
                        This may lead to the windows being unnoticed for this
                        amount of time when deiconifying, painting errors, etc.
 
+                       While testing on a very old SS20 these options gave
+                       tolerable response: -8to24 poll=0.2,cachewin=5.0. For
+                       this machine -overlay is supported and gives better
+                       response.
+
                        Debugging for this mode can be enabled by setting
                        "dbg=1", "dbg=2", or "dbg=3".
 
diff --git a/x11vnc/connections.c b/x11vnc/connections.c
index 800d443..4415f38 100644
--- a/x11vnc/connections.c
+++ b/x11vnc/connections.c
@@ -431,15 +431,39 @@ static int run_user_command(char *cmd, rfbClientPtr client, char *mode) {
 #if LIBVNCSERVER_HAVE_FORK
 	{
 		pid_t pid, pidw;
-		if ((pid = fork()) > 0) {
-			pidw = waitpid(pid, &rc, 0);
-		} else if (pid == -1) {
-			fprintf(stderr, "could not fork\n");
-			rfbLogPerror("fork");
-			rc = system(cmd);
+		struct sigaction sa, intr, quit;
+		sigset_t omask;
+
+		sa.sa_handler = SIG_IGN;
+		sa.sa_flags = 0;
+		sigemptyset(&sa.sa_mask);
+		sigaction(SIGINT,  &sa, &intr);
+		sigaction(SIGQUIT, &sa, &quit);
+
+		sigaddset(&sa.sa_mask, SIGCHLD);
+		sigprocmask(SIG_BLOCK, &sa.sa_mask, &omask);
+
+		if ((pid = fork()) > 0 || pid == -1) {
+
+			if (pid != -1) {
+				pidw = waitpid(pid, &rc, 0);
+			}
+
+			sigaction(SIGINT,  &intr, (struct sigaction *) NULL);
+			sigaction(SIGQUIT, &quit, (struct sigaction *) NULL);
+			sigprocmask(SIG_SETMASK, &omask, (sigset_t *) NULL);
+
+			if (pid == -1) {
+				fprintf(stderr, "could not fork\n");
+				rfbLogPerror("fork");
+				rc = system(cmd);
+			}
 		} else {
 			/* this should close port 5900, etc.. */
 			int fd;
+			sigaction(SIGINT,  &intr, (struct sigaction *) NULL);
+			sigaction(SIGQUIT, &quit, (struct sigaction *) NULL);
+			sigprocmask(SIG_SETMASK, &omask, (sigset_t *) NULL);
 			for (fd=3; fd<256; fd++) {
 				close(fd);
 			}
diff --git a/x11vnc/inet.c b/x11vnc/inet.c
index 29f4992..12f4fee 100644
--- a/x11vnc/inet.c
+++ b/x11vnc/inet.c
@@ -177,8 +177,47 @@ char *ident_username(rfbClientPtr client) {
 	if (!user || *user == '\0') {
 		char msg[128];
 		int n, sock, ok = 0;
-
-		if ((sock = rfbConnectToTcpAddr(client->host, 113)) < 0) {
+		int block = 0;
+
+		/*
+		 * need to check to see if the operation will block for
+		 * a long time: a firewall may just ignore our packets.
+		 */
+#if LIBVNCSERVER_HAVE_FORK
+	    {	pid_t pid, pidw;
+		int rc;
+		if ((pid = fork()) > 0) {
+			usleep(100 * 1000);	/* 0.1 sec */
+			pidw = waitpid(pid, &rc, WNOHANG);
+			if (pidw <= 0) {
+				usleep(1000 * 1000);	/* 1.0 sec */
+				pidw = waitpid(pid, &rc, WNOHANG);
+				if (pidw <= 0) {
+					block = 1;
+					kill(pid, SIGTERM);
+				}
+			}
+		} else if (pid == -1) {
+			;
+		} else {
+			/* child */
+			signal(SIGHUP,  SIG_DFL);
+			signal(SIGINT,  SIG_DFL);
+			signal(SIGQUIT, SIG_DFL);
+			signal(SIGTERM, SIG_DFL);
+
+			if ((sock = rfbConnectToTcpAddr(client->host, 113)) < 0) {
+				exit(1);
+			} else {
+				close(sock);
+				exit(0);
+			}
+		}
+	    }
+#endif
+		if (block) {
+			;
+		} else if ((sock = rfbConnectToTcpAddr(client->host, 113)) < 0) {
 			rfbLog("could not connect to ident: %s:%d\n",
 			    client->host, 113);
 		} else {
diff --git a/x11vnc/user.c b/x11vnc/user.c
index 6d173ab..5269d50 100644
--- a/x11vnc/user.c
+++ b/x11vnc/user.c
@@ -557,6 +557,11 @@ static int try_user_and_display(uid_t uid, char *dpystr) {
 		Display *dpy2 = NULL;
 		int rc;
 
+		signal(SIGHUP,  SIG_DFL);
+		signal(SIGINT,  SIG_DFL);
+		signal(SIGQUIT, SIG_DFL);
+		signal(SIGTERM, SIG_DFL);
+
 		rc = switch_user_env(uid, name, home, 0); 
 		if (! rc) {
 			exit(1);
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index 8eea209..80c7713 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -2,7 +2,7 @@
 .TH X11VNC "1" "February 2006" "x11vnc " "User Commands"
 .SH NAME
 x11vnc - allow VNC connections to real X11 displays
-         version: 0.8, lastmod: 2006-02-06
+         version: 0.8.1, lastmod: 2006-02-20
 .SH SYNOPSIS
 .B x11vnc
 [OPTION]...
diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c
index a73b8e0..6fcc96e 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 lastmod: 2006-02-06";
+char lastmod[] = "0.8.1 lastmod: 2006-02-20";
 
 /* X display info */
 
diff --git a/x11vnc/xevents.c b/x11vnc/xevents.c
index 5272333..e25a118 100644
--- a/x11vnc/xevents.c
+++ b/x11vnc/xevents.c
@@ -473,6 +473,11 @@ void spawn_grab_buster(void) {
 		fprintf(stderr, "spawn_grab_buster: could not fork\n");
 		rfbLogPerror("fork");
 	} else {
+		signal(SIGHUP,  SIG_DFL);
+		signal(SIGINT,  SIG_DFL);
+		signal(SIGQUIT, SIG_DFL);
+		signal(SIGTERM, SIG_DFL);
+
 		grab_buster_watch(parent, dstr);
 		exit(0);
 	}