I am glad to inform you that TightVNC 2.0 Beta 3 is available for download. The files can be downloaded here:
TightVNC 2.0 will deliver completely new TightVNC Server for Windows. It was redesigned and reimplemented from scratch. It features new component-based architecture which is perfectly compatible with the latest operating systems, Windows 7 and Windows 2008 Server R2. Older versions of Windows are supported as well – the minimum requirement is Windows 2000. More information on new TightVNC Server can be found in the TightVNC 2.0 Beta 1 announcement.
TightVNC 2.0 Beta 3 is another public preview of the upcoming TightVNC 2.0 release. As compared to the previous Beta version, it features improved keyboard handling and a number of bugfixes. For more details, see the section What's New?, below.
Give it a chance! And do not hesitate to fill in bug reports. ;)
With Best Wishes,
Part 1. Improved Keyboard Handling
This Beta version is focused on keyboard handling. There have been a lot of problems in this area, so we've decided to put more effort into this. New version comes with a lot of keyboard-related enhancements in both server and viewer code. In particular, new version should provide better support for national keyboard layouts. What we are trying to achieve is to enable international characters to be passed via the RFB protocol correctly. Unfortunately, the protocol works with characters, not key codes, and that makes things very complicated.
In addition, we've fixed a number of bugs, including major ones causing TightVNC to crash under certain circumstances. Most important bugfixes are listed below.
Part 2. TightVNC Server
- A bug with clipboard handling has been fixed. When running as a service, TightVNC Server could crash if a user copied something to the clipboard.
- There was a bug which caused the control interface to crash if the server had a lot of IP addresses. This bug was experienced by users of software that uses to add a number of "virtual" network interfaces and addresses, such as VMWare. The problem has been resolved.
- File uploads could fail at changing file modification timestamps. Fixed now.
- Web access should be enabled by default. It was a bug that it defaulted to the disabled state.
Part 3. TightVNC Viewer
- When run with the -help command-line option, the viewer listed a lot of options it actually does not support. This has been fixed. Unsupported options have been removed, while supported options have received better documentation.
- Unsupported command-line options were treated as host names to connect to. Now the viewer will report error messages on discovering unknown options in the command line.
- The viewer used to connect to nowhere if it could not read the specified .vnc file. Now it should exit correctly after showing the error message.
- In connection options, the check box "Request shared session" should be disabled after the connection has been established, as it makes sense only on entering the session. Now its state should be set correctly.