From your discussion, I can see there's a confusion or misunderstanding
in command line options. As far as I can see, some options to winvnc4 are
mutually exclusive. For example, when you use -start, PortNumber is
ignored. In other words,
winvnc4 -start PortNumber=12345
only starts winvnc4
00:27
To: vnc-list@realvnc.com
Subject: winvnc4 commandline sequence/syntax
Remaining question; why does the following fail?
winvnc4 -register PortNumber=5977
It doesn't. What makes you think it's not working for you?
--
Wez @ RealVNC Ltd
Here's the sequence; the values
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
On Dec 7, 2007 11:24 AM, Dave [EMAIL PROTECTED] wrote:
Thanks for everyone's contributions. I looked at the various
suggestions, claims and facts and
experimented a bit to discover the following:
1 - winvnc4.exe runs the same from any directory
2 - command-line execution of vncconfig.exe
Thanks for everyone's contributions. I looked at the various
suggestions, claims and facts and
experimented a bit to discover the following:
1 - winvnc4.exe runs the same from any directory
2 - command-line execution of vncconfig.exe only applies to 'user' mode
not to 'service' mode
3 - only
Dave wrote:
Thanks for everyone's contributions. I looked at the various
suggestions, claims and facts and
experimented a bit to discover the following:
[ snip ]
While I will write the scripts to modifying HKLM to configure the vnc4
service, I'd
expected something a bit more usable from the
[snip]
2 - command-line execution of vncconfig.exe only applies to
'user' mode not to 'service' mode
3 - only the rt-click : Options... will look at 'service'
mode config data
This is not true. You need to supply the -service command-line option to
VNC Config see the Service-Mode settings.
Remaining question; why does the following fail?
winvnc4 -register PortNumber=5977
It doesn't. What makes you think it's not working for you?
--
Wez @ RealVNC Ltd
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list
Remaining question; why does the following fail?
winvnc4 -register PortNumber=5977
It doesn't. What makes you think it's not working for you?
--
Wez @ RealVNC Ltd
Here's the sequence; the values are arbitrary.
HKLM shows the value to be 5980
HKU shows the value to be 5970 (not that it
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
-
:[EMAIL PROTECTED] On Behalf Of Dave Stoft
Sent: 05 December 2007 00:10
To: vnc-list@realvnc.com
Subject: Re: winvnc4 commandline sequence/syntax
James, thanks for the clarification.Could you add a bit more detail?
I'd originally submitted my questions to the support center
for the product I own
Cc: vnc-list@realvnc.com
Subject: Re: winvnc4 commandline sequence/syntax
On Tue, Dec 04, 2007 at 04:09:56PM -0800, Dave Stoft wrote:
My conclusion has been that I have misunderstood the syntax or
application of the syntax with the command-line method but
I have been
unable to locate
On Tue, Dec 04, 2007 at 04:09:56PM -0800, Dave Stoft wrote:
My conclusion has been that I have misunderstood the syntax or
application
of the syntax with the command-line method but I have been unable to
locate
explicit examples to show where I made the error(s). Can you point to
the
James, thanks for the clarification.Could you add a bit more detail?
I'd originally submitted my questions to the support center for the
product I own, but never received a response. This list appeared to be the
more active alternative. It's helpful, and appreciated, to have feedback
from RealVNC.
@realvnc.com
Subject: winvnc4 commandline sequence/syntax
I've been unable to find a clear reference for programatic
start, config and stop of a vnc4.3.2 server. My guess at the
syntax and sequence does not control the server settings that
were created via the windows interface.
- On Win2k
).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Stoft
Sent: Saturday, 1 December 2007 1:24 PM
To: vnc-list@realvnc.com
Subject: winvnc4 commandline sequence/syntax
I've been unable to find a clear reference for programatic start, config
and stop of a vnc4.3.2
D. Thanks; your description fits the symptoms.
Would have been nice if VNC4 had included this in the docs; maybe it's
a legacy 'feature'. I did wander the path of editing the registry and that
does look like the best alternative. I'd assumed I should be able to config
at the time of registering
I've been unable to find a clear reference for programatic start, config and
stop
of a vnc4.3.2 server. My guess at the syntax and sequence does not control
the server settings that were created via the windows interface.
- On Win2k or XP
- The VNC4.3.2 package installed correctly
- The
18 matches
Mail list logo
