> Here's the thing I am wondering about:
>
> In bash, in a " " quoted string, backslash acts kind of as in C and may
> need to be escaped (doubled). It can be tricky/painful to find the
> right quoting/escaping combination to get what is necessary. In a
> ' ' quoted string, you get what you type.
> Could you post the command line(s) you used? Maybe
> we can spot something EM
>
Usage: tkfPush port tkf_file_name_path launch_java(t/f)
C:\Users\jar>tkfpush 4879 Bar.tkf t
Client: WSAStartup() is OK.
jar location="C:\Users\jar\Tekdraw2\tekPlot\dist\tekPlot.jar"
Client: WSAStartup(
> Yes, the responder *is* saying that you need to run this as
> administrator. I can't speak for the difference with MinGW.
>
> Eliot Moss
I reran this in a Windows 7 command window as an
administrator, using the Windows style paths using \\,
and still get the same result. It cannot find the j
Larry Hall (Cygwin cygwin.com> writes:
>
> To the OP, run the same from an elevated prompt and these
> errors should disappear.
>
I tried it also with windows style paths, both using \\ and / as
separators with the same results.
What does "to the OP" mean? And are you implying it has to be r
4 matches
Mail list logo
