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

Remotedesktop support

Post Reply
Prisma
100
100
Posts: 321
Joined: 2005-10-27 15:50

Remotedesktop support

Post by Prisma »

Hello Rudi,

previously we already wrote about the long time it takes before winvnc comes back to the repeater when closing the viewer during rdp=1 and an existing rdp session.
I'm not absolutely sure, but I think we figured out that one exe is waiting for the other exe a fixed time instead of waiting only the shortest possible and necessary time.

This behaviour is not only a beauty mistake. It is really confusing and obstructive.
As far as I can remember there could be a fix but this fix wasn't applied until now. (?)

Am I right? It's been a while...
We would very very appreciate if this would be fixed.

Cheers Greg
Post Reply