After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
File Transfer UVNC compatible with tightVNC flavor ?
File Transfer UVNC compatible with tightVNC flavor ?
it is possible to do it software compatibility for file transfer with UltraVNC and TightVNC ?
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
The TightVNC FT is not ugly or badly implemented... and it seems to work, which is the primary goal in software developpement
It is simply not compatible with UltraVNC FT from the bottom.
To my knowledge, Tight FT started in 2003 (?) and has become more and more different from Ultra FT until now. I don't know if their protocole is "finished" or not right now.
UltraVNC FT protocole was initialiy designed in February 2002. At this time I proposed it to the Tight team as a wasn't planning to do my own public VNC version... they refused it for some reason.
Supporting the 2 FT protocoles would be too heavy in the current UltraVNC code base. We could do this but the weight of both the viewer and server would increase consequently. And I'm not sure their protocole is not going to change again.
Maybe later.
FYI, in UltraVNC 2 I plan to redisign the FT protocole or at least improve it in such a manner that backward compatibility with UltraVNC V1 will be broken.

It is simply not compatible with UltraVNC FT from the bottom.
To my knowledge, Tight FT started in 2003 (?) and has become more and more different from Ultra FT until now. I don't know if their protocole is "finished" or not right now.
UltraVNC FT protocole was initialiy designed in February 2002. At this time I proposed it to the Tight team as a wasn't planning to do my own public VNC version... they refused it for some reason.
Supporting the 2 FT protocoles would be too heavy in the current UltraVNC code base. We could do this but the weight of both the viewer and server would increase consequently. And I'm not sure their protocole is not going to change again.
Maybe later.
FYI, in UltraVNC 2 I plan to redisign the FT protocole or at least improve it in such a manner that backward compatibility with UltraVNC V1 will be broken.