winvnc4 commandline sequence/syntax

[Dave Stoft]

Ok. So I should think of command-line parms like temporary settings that
over-write what winvnc4 reads from the registry and vncconfig can only
read from (and write only via manual GUI changes to) the registry. This leaves
a final question.

When winvnc4 is started, the tray icon (created by starting winvnc4) provides
the "Options..." menu list which appears to start the vncconfig utility. Since
I do not see the command-line parm changes listed in the "Options..." copy
of vncconfig, I'm now assuming the "Options..." access is equivalent to
doing a command-line vncconfig -- which only reads the registry as you described.

Since the HKLM registry lists the service-mode parms (which are not affected
by the command-line) and vncconfig does not display the command-line
parm values, are the service-mode command-line parms non-viewable settings?
I could understand command-line parms to be single-instance values that
take precidence over registry based values, but I'd not expected command-line
based configuration values to be non-viewable in the config utility -- maybe
not "sticky" (no change to the registry config values) but still viewable as
validation that the command-line changes were accepted and active.

Thanks for your clarifications.

Dave

>
>Dave,
>
>Specifying parameters on the command-line when starting winvnc4.exe
 doesn't
>cause them to be written to the registry, it just causes that copy of
>winvnc4.exe to use them instead of the corresponding value from the
>configuration in the registry.  vncconfig.exe uses the same mechanism,
 so if
>you specify different command-lines to the two programs (or even to two
>separate copies of vncconfig.exe) you'll get different results.
>
>Regards,
>
->-
>Wez @ RealVNC Ltd