my 2 cents:
[post=40930][/post]
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
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
The plugin cannot be loaded please check its name integrity
Re: The plugin cannot be loaded please check its name integr
Hi everyone!
This is quite the discussion. I fought with this one for quite some time. I realized the answer to this problem when I decided to take a look at the source of the plugin (ya, that is how frustrated I was). When I saw all the C++ source files I realized that uVNC plugins are not simple scripting plugins but rather full fledged binaries that are run by uVNC. That is when I realized that it is likely that the plugin is only a 32bit binary and wouldn't work properly with the 64bit version of uVNC. Uninstalling uVNC 64 bit and reinstalling the 32 bit version fixed all these strange errors.
Hope that helps : ).
This is quite the discussion. I fought with this one for quite some time. I realized the answer to this problem when I decided to take a look at the source of the plugin (ya, that is how frustrated I was). When I saw all the C++ source files I realized that uVNC plugins are not simple scripting plugins but rather full fledged binaries that are run by uVNC. That is when I realized that it is likely that the plugin is only a 32bit binary and wouldn't work properly with the 64bit version of uVNC. Uninstalling uVNC 64 bit and reinstalling the 32 bit version fixed all these strange errors.
Hope that helps : ).
Re: The plugin cannot be loaded please check its name integr
I have Windows Vista 64-bit Desktop (running viewer in listen mode) and a Windows Vista 32-bit Laptop (running uvnc sc). I was getting the plugin error message too while testing UltraVNC SC Update 2011 from this thread:
[topic=27653][/topic]
I never had a problem running UltraVNC SC on my Laptop to my UltraVNC 64-bit Viewer (in listen mode) on my desktop in non-encryption mode, but had major problems with encryption mode.
After trying various combinations of UltraVNC 32-bit and UltraVNC 64-bit viewers along with SecureVNCPlugin.dsm, SecureVNCPlugin64.dsm, MSRC4Plugin.dsm, and MSRC4Plugin_NoReg.dsm (a lot of file swaping and renaming), I finally got UltraVNC SC working properly in encryption mode.
I'll confirm what Thinker77 found: the 32-bit version of UVNC Viewer must be used when the MSRC4Plugin.dsm encryption plugin is used. If no encryption plugin is used, then either the 32-bit or 64-bit viewers work fine.
Btw, I never could get any of the SecureVNCPluginXX.dsm plugins to work no matter what I tried, so save yourself the grief and stick with the MSRC4 one.
[topic=27653][/topic]
I never had a problem running UltraVNC SC on my Laptop to my UltraVNC 64-bit Viewer (in listen mode) on my desktop in non-encryption mode, but had major problems with encryption mode.
After trying various combinations of UltraVNC 32-bit and UltraVNC 64-bit viewers along with SecureVNCPlugin.dsm, SecureVNCPlugin64.dsm, MSRC4Plugin.dsm, and MSRC4Plugin_NoReg.dsm (a lot of file swaping and renaming), I finally got UltraVNC SC working properly in encryption mode.
I'll confirm what Thinker77 found: the 32-bit version of UVNC Viewer must be used when the MSRC4Plugin.dsm encryption plugin is used. If no encryption plugin is used, then either the 32-bit or 64-bit viewers work fine.
Btw, I never could get any of the SecureVNCPluginXX.dsm plugins to work no matter what I tried, so save yourself the grief and stick with the MSRC4 one.
-
Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: The plugin cannot be loaded please check its name integr
It isn't that hard...
viewer/server bins need to use the same bit for the plugins.
A plugin is a dll, and a dll always need to be the same as the exe.
if viewer = 32bit -> dsmplugin also need to be 32bit.
Independed if you run it on a 32 or 64 bit OS.
if viewer = 64bit -> dsmplugin also need to be 64bit.
You can mix a server 32bit with a viewer 64 bit.
server32+plugin32 can connect to a viewer64+plugin64
server64+plugin64 can connect to a viewer32+plugin32
server and viewer need to use the same type of plugin.
(SecureVNC,MSRC4)
1096 had a few bugs with the older plugins, solved in fixes.
[topic=27951][/topic]
viewer/server bins need to use the same bit for the plugins.
A plugin is a dll, and a dll always need to be the same as the exe.
if viewer = 32bit -> dsmplugin also need to be 32bit.
Independed if you run it on a 32 or 64 bit OS.
if viewer = 64bit -> dsmplugin also need to be 64bit.
You can mix a server 32bit with a viewer 64 bit.
server32+plugin32 can connect to a viewer64+plugin64
server64+plugin64 can connect to a viewer32+plugin32
server and viewer need to use the same type of plugin.
(SecureVNC,MSRC4)
1096 had a few bugs with the older plugins, solved in fixes.
[topic=27951][/topic]
Last edited by Rudi De Vos on 2011-04-24 22:20, edited 2 times in total.