I am attempting to automate installation/setup of the WinVNC server and the MSRC4Plugin.dsm.
Can somebody explain the DSMPlugin registry value fo me? The documentation appears to conflict with the actual usage.
The example at http:\WWWdownloads\UltraVNC\UltraVNC_Registry_settings.mht states:
"DSMPlugin : The filename of the DSM Plugin to be used to modify the communication data stream (PluginName.dsm)".
I interpret this to mean that it should be a Reg_SZ string value. However, having manually configured the MSRC4Plugin.dsm from the VNCviewer popup window, the registry entry is a REG_BINARY containing (when exported):
"DSMPlugin"=hex:4d,53,52,43,34,50,6c,75,67,69,6e,2e,64,73,6d,00,78,01,3f,00,00,\
00,00,00,00,00,00,00,00,00,00,00,28,73,02,00,c8,67,48,00,94,fe,12,00,03,00,\
00,00,18,00,00,00,00,00,40,00,c8,67,48,00,94,fe,12,00,18,00,00,00,fc,fe,12,\
00,f8,52,3f,00,00,00,3f,00,80,fc,12,00,0d,52,75,6e,6e,69,6e,67,00,88,fa,77,\
78,1c,f5,77,ff,ff,ff,ff,3a,8a,f5,77,8b,84,44,00,00,00,3f,00,00,00,00,00,10,\
00,00,00,ab,f1,a9,70,58,54,3f,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,b0,ff,12,00,04,d9,44,00,98,eb,45,00,ff,ff,ff,ff,00,00,00,00,82,83,44,\
00,0b,00,00,00,6f,83,44,00,0b,00,00,00,ab,f1,a9,70,ec,65,45,00,f8,52,3f,00,\
44,d0,46,00,fc,70,40,00,f8,cf,46,00,20,ff,12,00,b0,ff,12,00,b5,84,45,00,01,\
00,00,00,d6,5d,43,00,ab,f1,a9,70,00,00,00,00,c0,ff,12,00,00,f0,fd,7f,ff,ff,\
ff,ff,00,00,00,00,df,9b,44,00
Of this, only the first 15 hex bytes seem relevant.
Are any of the remaining hex bytes relevant?
If not, can the hex string be truncated after the terminating "00" byte?
Otherwise, how is the hex string constructed?
Edward
After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
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.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
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
DSMPlugin registry value?
Re: DSMPlugin registry value?
I'm not an expert on this by any means but I have exported the registry after a clean install with dsm plugin set and i exported ORL under current user and ORL under Local Machine.edward wrote:I am attempting to automate installation/setup of the WinVNC server and the MSRC4Plugin.dsm.
Can somebody explain the DSMPlugin registry value fo me? The documentation appears to conflict with the actual usage.
The example at http:\WWWdownloads\UltraVNC\UltraVNC_Registry_settings.mht states:
"DSMPlugin : The filename of the DSM Plugin to be used to modify the communication data stream (PluginName.dsm)".
I interpret this to mean that it should be a Reg_SZ string value. However, having manually configured the MSRC4Plugin.dsm from the VNCviewer popup window, the registry entry is a REG_BINARY containing (when exported):
"DSMPlugin"=hex:4d,53,52,43,34,50,6c,75,67,69,6e,2e,64,73,6d,00,78,01,3f,00,00,\
00,00,00,00,00,00,00,00,00,00,00,28,73,02,00,c8,67,48,00,94,fe,12,00,03,00,\
00,00,18,00,00,00,00,00,40,00,c8,67,48,00,94,fe,12,00,18,00,00,00,fc,fe,12,\
00,f8,52,3f,00,00,00,3f,00,80,fc,12,00,0d,52,75,6e,6e,69,6e,67,00,88,fa,77,\
78,1c,f5,77,ff,ff,ff,ff,3a,8a,f5,77,8b,84,44,00,00,00,3f,00,00,00,00,00,10,\
00,00,00,ab,f1,a9,70,58,54,3f,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,b0,ff,12,00,04,d9,44,00,98,eb,45,00,ff,ff,ff,ff,00,00,00,00,82,83,44,\
00,0b,00,00,00,6f,83,44,00,0b,00,00,00,ab,f1,a9,70,ec,65,45,00,f8,52,3f,00,\
44,d0,46,00,fc,70,40,00,f8,cf,46,00,20,ff,12,00,b0,ff,12,00,b5,84,45,00,01,\
00,00,00,d6,5d,43,00,ab,f1,a9,70,00,00,00,00,c0,ff,12,00,00,f0,fd,7f,ff,ff,\
ff,ff,00,00,00,00,df,9b,44,00
Of this, only the first 15 hex bytes seem relevant.
Are any of the remaining hex bytes relevant?
If not, can the hex string be truncated after the terminating "00" byte?
Otherwise, how is the hex string constructed?
Edward
When I then pushed this registry to another machine it seemed to work, but I have had other machines give me wierd errors.
I just have the properties screen come up and have the user set it real quick the first time and then be done with it.
-
Guest

