Hello everyone,

I'm pleased to announce new TightVNC 1.2.5 release.

TightVNC is an improved version of VNC, free cross-platform remote
desktop package. It offers many new features, improvements and
bugfixes. Unlike the original VNC, it can work well over slow Internet
connections, and allows more configuration options in the GUI.
TightVNC can be used to perform remote administration tasks in
Windows, Unix/Linux and mixed network environments. It can be useful
in distance learning and remote customer support. TightVNC is freely
available under the terms of the GNU General Public License, and is
fully compatible with the standard VNC. For more details, please visit
the TightVNC Web site:

                       http://www.tightvnc.com/

Both Win32 and Unix/Linux versions are available, in both binary and
source forms. Also, you can download TightVNC Java viewer which is
already present in server parts of Win32 and Unix versions. To
download new release, follow the links at the download page:

                http://www.tightvnc.com/download.html

As compared to the previous version, TightVNC 1.2.5 includes important
performance fix in WinVNC, adds a number of new features, improvements
and bugfixes in Win32 and Unix/Linux versions, and in the Java viewer.
Here is a summary of changes introduced in TightVNC 1.2.5:

  - Win32 version: Fixed a problem in the I/O subsystem that was
    introduced in TightVNC 1.2.2 and was causing major slowdown in
    communication with clients.

  - Win32 version: Enabled remote upgrade in the installation script. 
    Also, the installer will install a copy of the TightVNC Web site,
    and will create shortcuts to most important documentation pages.

  - Win32 version: Implemented new feature to specify applet
    parameters in URL requests being sent to the built-in HTTP server. 
    Added support for new "EnableURLParams" registry setting which can
    be used to enable this feature.

  - Win32 version: Added support for the NewFBSize pseudo-encoding
    allowing to change framebuffer geometry on the fly on server's
    request.

  - Win32 version: Included "solution" and "project" files for MS
    Visual Studio 7, from Andrew van der Stock, applied a set of minor
    fixes to suppress compilation warnings under MS Visual Studio 7.

  - Win32 version: The viewer now tries to preserve the size and
    position of the desktop window after applying new connection
    options.

  - Unix version: Implemented new feature to specify applet parameters
    in URL requests being sent to the built-in HTTP server. Added
    support for new $PARAMS variable in .vnc HTML templates.

  - Unix version: Added the possibility to keep users' vnc directories
    under /tmp, as suggested by Ivan Popov. This mode can be enabled
    by editing the $vncUserDir variable in the vncserver script. Also,
    new -t option has been implemented in the vncpasswd utility which
    allows to change VNC password files under /tmp.

  - Unix version: Applied Xvnc -viewonly patch from Ehud Karni.

  - Unix version: Applied Linux/PowerPC Xvnc fix from Peter A. Castro.

  - Unix version: Bug fixed: Xvnc failed to reset compression level
    and JPEG image quality on reading lists of encodings supported by
    clients.

  - Unix version: Made the viewer handle XCursor encoding operating on
    the framebuffer instead of setting new cursors directly in X.

  - Unix version: Applied a number of porting fixes from Ki Networks,
    Inc.

  - Java viewer: Added new feature allowing to save RFB sessions in
    FBS files compatible with rfbproxy. This feature works only if JVM
    security manager allows access to the local filesystem, which is
    usually true only when the viewer is used as a standalone
    application or if the viewer applet is cryptographically signed.
    New "Record" button will appear in the button panel if this
    feature is enabled.

  - Java viewer: Added new "ENCPASSWORD" parameter, modified patch
    from Peter Astrand.

  - Java viewer: Applied patch from Peter Astrand to fix problems with
    Swedish keys and broken JVMs.

  - Other minor fixes and cleanups.

I'd like to thank everyone who contributed the TightVNC project. The
project could not live without your help.

-- 
With Best Wishes,
Constantin

P.S. I'm about to start working on a number of major changes in TightVNC,
     and I'll describe my plans in one of the following messages.
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to