winvnc server always uses default UtraVNC.ini instead of registry or -inifile command line parameter

[kiwiwings]

Version: 1.4.3.6 or latest 1.5 snapshot

Despite of UseRegistry=1 setting or -inifile command line parameter, winvnc always uses the default UltraVNC.ini settings.
Storing the values with UseRegistry=1 result in an UAC popup and eventually saving to the default UltraVNC.ini.
Removing the registry keys for recreating it via admin properties didn't work.

I've updated from version 1.3.8.1, where this was still possible.
We'd like to run one winvnc per windows session with an unique port and ms auth - so basically everything in the default config can be the same except the port - maybe introduce a port command line parameter or get -inifile working.

Could it be, that the WinVNCAppMain - settings/SettingsManager is already initialized before g_szIniFile is set?

[RudiDeVos]

This require a trace of the full ini loading process, need to make time for it.
Don't have a direct answers

[RudiDeVos]

We'd like to run one winvnc per windows session, you mean one vncserver for each rdp session ?
In that case the vncserver need to be started by the logon process and not as service. A service always share the console while winvnc running as application share the current session.

What you can do
create several UltraVNC folders each with there own exe and ini file. (session1UltraVNC session2UltraVNC session3UltraVNC)
Each window session start his own winvnc in his own folder, using his own ultravnc.ini in that folder. This allow to customize each winvnc.

[kiwiwings]

thank you for looking into it.
So to confirm your assumption: yes it's about vnc session per rdp session and we start it in the rdp session.

your workaround could be done, but I'd rather like to wait for you to restore the registry loading or alternatively get the -inifile switch working.

no rush ... if you provide a snapshot, I'm happy to test it - until then, we stick with the old version or keep vnc disabled on those hosts.