MSRC4 Plugin Configuration locations are corrupt

[docfxit]

I am instilling all programs in Win7 32bit into C:\Programs. (My own creation because I don't know what programs will work and what programs won't work within the Windows 7 security)
When I first install Ultravnc 1.0.9.6.1 I expect when I go to configure the DSM Plugin that it will know the install went to C:\Programs\Ultravnc. It doesn't, It configures all 4 locations to C:\Program Files\Ultravnc. So I change all 4 locations to point to the correct location. After clicking Ok it looks corrected. After clicking on Apply at the UltraVNC Server Property Page and then clicking on OK the screen goes away. If I go back into Admin Properties and click on DSM Plugin Config button I see all 4 locations are corrupt. Every time I re-boot a message comes up saying that it's looking in C:\Program Files\Ultravnc for RC4.

Is the C:\Program Files\Ultravnc hard coded and can't be changed? Why would someone hard code that? Is there a work around for that?

Thanks for all the great work everyone does on this program.

Docfxit

[docfxit]

I tried un-installing Ultravnc from c:\programs\ultravnc. And then installing into the default c:\Program Files\Ultravnc. After a re-boot the DSM Plugin locations are corrupt again.

[Rudi De Vos]

If you copy ultravnc.exe 10961 in a folder A, he looks for the plugins in this same folder.
You can copy the exe + dsm even on a usb stick, it run perfect from the usb stick.
Search path for plugin is start location of exe.

Verify the about if you are realy starting the 10961 version and not some older winvnc.exe is auto started via a service or startup.
Check via taskmanager ( show all users) and verify properties of winvnc.exe

[docfxit]

Thank you for the reply...

> If you copy ultravnc.exe 10961 in a folder A, he looks for the plugins in this same folder.

In win7 my experience is that it doesn't always work.

> You can copy the exe + dsm even on a usb stick, it run perfect from the usb stick.
> Search path for plugin is start location of exe.

Are you going by the source program or have you actually tested it in Win7?
I you are testing it in Win7 there must be something different between yours and mine.

> Verify the about if you are realy starting the 10961 version and not some older winvnc.exe is auto started via a service or startup.

After right clicking on the icon in the task bar and choosing about WinVNC shows 1.0.0.6.1 build May 18 2011 22:24:10

> Check via taskmanager ( show all users) and verify properties of winvnc.exe

In TaskManager I see two winvinc.exe. Both show Product Version 1.0.9.6.1

I did find a work around. If I create a folder in C:\Program Files\UltraVNC
and copy rc4.key into it all works fine. That file is the only file in the folder.

So my question is what is different on my installation from all your testers.
Do you have a way to turn on logging or debugging on my installation to point out what might be the cause?

Thanks,

Docfxit

[Rudi De Vos]

I'm using win7 X64 for testing.
Dsm is checked in run folder.
Load key run folder
save key propose run folder.

test secureVNCplugin.dsm/msrc4plugin +10961winvnc

Vnc check for plugins in his run folder.
The plugin looks for his own key.
Possible the plugin version you use use the registry to save the key location...

[docfxit]

> I'm using win7 X64 for testing.

I'm using both x64 and x32 win7.

> Dsm is checked in run folder.

Use is checked in the DSM Plugin box. I don't know where the run folder is.

> Load key run folder

I have the file rc4.key in the same folder as vncviewer.exe and winvnc.exe it's in c:\programs\Ultravnc

> save key propose run folder.

> test secureVNCplugin.dsm/msrc4plugin +10961winvnc

I'm using MSRC4Plugin0118.dsm

> Vnc check for plugins in his run folder.

I wish it did. It only checks for the file in C:\Program Files\Ultravnc

> The plugin looks for his own key.

Yes. The key I created.

> Possible the plugin version you use use the registry to save the key location...

I think it does. Since the install was from C:\Programs\Ultravnc I would expect the registry to use that path.

Thank you for a great program,

Docfxit

[redge]

try last version (6 July 2009) msrc4plugin 1.2.4.0 (no more update after this build)
fixed issue with path and %temp% if i'm not wrong from what i remember from mind.

[docfxit]

try last version (6 July 2009) msrc4plugin 1.2.4.0 (no more update after this build)
fixed issue with path and %temp% if i'm not wrong from what i remember from mind.

Thank you for the reply.

If that works I would need to change 27 PC'S to that version. If that is going to be the last update there must be a preferred method to replace it. If there is a preferred method I would rather make the switch once to the preferred method than having to make the switch twice.

Any information you can give me on the most secure method would be great.

Thanks,

Docfxit

[redge]

rename old one and add new one in case of failure.
anyway, you need to try on test computer first
no have best method, everybody work on their style and requirement.

[andypeters]

I also had the same problem but after updating to msrc4plugin 1.2.4.0, i no longer have that problem.