Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kiwiwings opened this issue Apr 26, 2024 · 1 comment
Assignees
Labels
Rudi Rudi answer is needed

Comments

@kiwiwings
Copy link

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?

@Neustradamus Neustradamus added the Rudi Rudi answer is needed label Apr 27, 2024
@RudiDeVos
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rudi Rudi answer is needed
Development

No branches or pull requests

3 participants