Configure Windows TightVNC-Server with configuration file instead of registry keys

Hi there,

I wonder if there is any way (or plan) to make the TightVNC-Server for 
Windows systems configurable via a configuration file - something like a 
"server.ini". If I understand the documentation correctly, on Windows 
systems all configuration options are stored in the Registry.

Either in the HKLM tree - for the system wide service. Or in the HKCU 
tree - for a server process started by a user.


I know there are some command line options (documented here: 
https://www.tightvnc.com/doc/win/TightVNC_2.7_for_Windows_Server_Command-Line_Options.pdf), 
but all changes are still save to the registry.

I found a feature request from 2017, but I do not see any indication if 
this is on the roadmap for a release 
(https://sourceforge.net/p/vnc-tight/feature-requests/727/). There is a 
mentioning of a "beta" version with this feature, yet I do not know 
where to find this "beta". Do I have to compile a current working branch 
myself to get this "beta" version?


My goal is to start a TightVNC-Server from the command line and 
configure it completely *without* using registry keys. I want to set the 
port, password, mode and so on. Is something like this possible?

Any help is be appreciated, thank you for your efforts!


-- 
PerFact Signatur

With best regards

Thorsten Südbrock

___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list