Ah, thanks; I'm learning. This sequence should be robust for any valid config parm: - independently modify HKLM registry for PortNumber (doing this first avoids the unknown of when changes become active) (seems this could also be done after -register but before -start) - winvnc4 -register - winvnc4 -start - vncconfig -service (optional verify that PortNumber was changed) (modifying HKLM can work here for some, but not all, settings) - use VNC in service mode - winvnc4 -stop - winvnc4 -unregister
Remaining question; why does the following fail? >winvnc4 -register PortNumber=5977 where 'PortNumber=5977' could be any setting. According to what I read in the docs, command-line config settings take precedence over settings like this placed in config files so the the command-line method should be the simplest of form of command-line methods for changes to settings prior to starting the service. In this case, the requested value is different from either the 'user' value or the 'service' value so it is clear that any parm other than the '-register' switch is simply being ignored. Neither 'user' nor 'service' settings are affected. I'm curious as to why. If there is an additional command-line switch or a setting elsewhere to enable command-line config data settings I have been unable to find it. What did I miss? Thanks in advance. Dave _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
