Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- 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

Search found 4 matches

by aldogg254
2004-10-06 15:03
Forum: DSM plugin
Topic: DSMPlugin cannot be configured
Replies: 19
Views: 32134

byteboon.. you're beautiful.. finally, a solution to this annoying problem... thank you very much.. you saved me tons of time. Everyone who has this problem: you should definitely download Keypal from http://www.jensign.com/JavaScience/dotnet/keypal/ Run the program and it will show you a list of ...
by aldogg254
2004-10-04 21:02
Forum: DSM plugin
Topic: DSMPlugin cannot be configured
Replies: 19
Views: 32134

the troubled user on my computer is an administrator who installed the program.. so it should have all the registry access it needs. I think i found a temporary workaround though. I created another administrator user with no password, logged into that user, and ultravnc worked (i'm using RC11 ...
by aldogg254
2004-10-04 18:36
Forum: DSM plugin
Topic: DSMPlugin cannot be configured
Replies: 19
Views: 32134

I wish someone would be able to fix this. I've spent hours and hours trying to figure out the source of the problem. I recently noticed that my DSM Plugin binary value in my registry was different from another computer's. That computer's vnc viewer worked, so i took the binary value and used it to ...
by aldogg254
2004-10-01 17:16
Forum: DSM plugin
Topic: DSMPlugin cannot be configured
Replies: 19
Views: 32134

I have the exact same problem... even after uninstalling and reinstalling it doesn't go away.. I also think it has something to do with the MSLogin changes. I got that error message on one of my windows login names, and on the other name it would work fine. I changed the password of the other name ...