Hello,
Hope all the traffic I'm generating on this list eventually does some
good e.g. for anyone else who may run into similar situations.
I'm more of a unix guy writing an MSDOS batch wrapper on my WinME
machine for the vncviewer. Eventually, I will replace all my slightly
different shortcuts to the vncviewer with the wrapper. Since the
wrapper takes care of most of the desired options, it would be easy
to compare the different shortcuts and modify them when needed. It is
also easy to do global modifications on the wrapper itself. I also
avoid having a listening daemon on the system tray, just to retain
my favoured default settings.
After doing some reading on MSDOS (and ruling out the possibility
of cygwin bash wrappers for various reasons), I came up with a one-line
wrapper:
c:\progra~1\tightvnc\vncviewer.exe -encoding hextile
-compresslevel 9 -quality 0 -noshared -noemulate3
-fullscreen %1 %2 %3 %4 %5 %6 %7 %8 %9
If I invoke this wrapper without any arguments,
VNC complains that it failed to connect. It works fine
if I leave out the % variables, but that doesn't allow the wrapper
to be supplied with additional options (possibly overriding the
hard coded options in the wrapper). It also works if I specify
a server after all the % variables, but that makes the wrapper
too specific.
I thought that the problem is that the series of
spaces after the -fullscreen option is being mistaken for a
server specification, but I don't get the error if I type the command
at the DOS prompt (with spaces at the end instead of the
% variables).
I even replaced the vncviewer.exe with an
invocation of my own debugging script just to see whether
those extra end spaces were being meaningfully interpretted
(e.g. as a server specification), but all argument variables
after -fullscreen have zero length (confirmed with
the command "echo %%3=_%3_", for example). The arguments
beyond -fullscreen were obtained by 10 consecutive MSDOS "shift"
commands, and I verified that I was looking at them
by adding a few extra dummy arguments after -fullscreen.
Anyway, I'm at a loss as to why I'm getting the error, and it
seems to be an interplay between how MSDOS passes
arguments to a binary executable, and how the executable
handles extra spaces at the end of the command line. If
anyone more experienced in MSDOS scripting can suggest
an explanation (and maybe a workaround), that'd be great.
Thanks.
Fred
--------------------------------------------------------------------------
Fred Ma
Department of Electronics
Carleton University, Mackenzie Building
1125 Colonel By Drive
Ottawa, Ontario
Canada K1S 5B6
[EMAIL PROTECTED]
==========================================================================
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
