See also: press release
I am glad to inform you that TightVNC 2.0 Beta 1 is available for download. This is the first public preview of the upcoming TightVNC 2.0 release. The files can be downloaded here:
This Beta version delivers 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.
The final release of TightVNC 2.0 for Windows is scheduled to April, 2010. There will be minimum changes between this Beta version and the final release – ideally, that should be bugfixes only.
Note: Beta versions of TightVNC 2.0 do not include components for Unix/Linux. These components will be worked on once TightVNC 2.0 for Windows goes out from Beta stage.
Below is a list of major improvements in TightVNC 2.0 Beta 1:
- Introducing new file transfer subsystem based on new protocol extensions. Multiple files and directories can be copied at once, directories are processed recursively. Data compression is used to speed-up copying. Files can be renamed or removed, new directories can be created. File sizes are not limited by 4 Gb any more.
- Implemented new server architecture which separates service code from the user interface. This enables service-mode operation under Windows Vista and Windows 7. Also, this fixes all known problems with multi-user features of modern Windows systems like Fast User Switching and Terminal Services.
- Screen updates have become reliable. If something went wrong and the picture in the viewer is garbled, incomplete or outdated, it will be recovered in reasonable time. There should be no more hidden menus or destructive window movements. If fast update detection methods fail, full-screen polling will keep updates going.
- Featuring new secure administrative interface. What was called "TightVNC tray icon" in previous versions is now a separate process which acts as a control interface to the TightVNC service. Control interface can be optionally protected with a password to make sure users cannot reconfigure or shut down the service unless they know the password (or have administrator privileges).
- There should be no more confusion between "default settings" and "user settings". In TightVNC 2.0, there is only one service-mode configuration and it is not affected by any per-user settings. The "Configure..." menu item of the service always shows the effective configuration. From the other side, TightVNC Server can be started as an application, and in that case each user has his/her own configuration.
- Featuring IP-based access control for incoming connections. Previous versions of TightVNC did allow similar IP filtering, but now everything is easily configurable. You can even test the rules on specific IP addresses, prior to applying new rules.
- TightVNC 2.0 distribution has been packaged with new installer. It's smarter and more efficient. It tries to prevent reboots whenever possible. It invites to set passwords so that TightVNC Server would be ready to work right at the moment of finishing the installation. From the other side, it can operate silently (when run with /S option in the command line). Finally, the complete self-installing TightVNC package (both server and viewer parts, and the uninstall tool) is only 550 kilobytes in size.
- This list of changes is not full. TightVNC Server 2.0 for Windows has been completely rewritten by the TightVNC team. It does not include old TightVNC 1.3 code. So the right answer to the "What's New?" question must be "Everything!".
With Best Wishes,