have you tried putting the URL in double quotes?
that *may* prevent the program from treating ftp://blah as 3 maybe 2 arguments 
(ftp: / /blah or ftp: //blah).  I should think it would be 3.


also, if this is djgpp, you need to turn off globbing because / ? * . [ ] is 
speclal (this is or almost is a regexp)!  even in msdos, / is special and 
denotes a command-line switch, so funny things may happen?  only cure I know 
of, if this is not djgpp (see below because double quotes won't work) is to use 
double quotes around the URL.



#if defined(__MINGW32__)
/*mingw-w64 toolchain sezero configures
the CRT using --enable-wildcard which enables globbing. To disable it, you
can either add a global to your source, like "int _dowildcard = 0;" or you
can add CRT_noglob.o to your list of objects to be linked.*/

int _dowildcard = 0; /*disable globbing in mingw-w64 sezero toolchain*/
#elif defined(__DJGPP__)
/*http://www.delorie.com/djgpp/v2faq/faq16_2.html*/
char **__crt0_glob_function(char *_argument) {
    return 0; //cause no expansion
}
#endif







>________________________________
>From: Michael B. Brutman <mbbrut...@brutman.com>
>To: freedos-devel@lists.sourceforge.net
>Sent: Thursday, July 7, 2011 5:13 AM
>Subject: Re: [Freedos-devel] mTCP FTP URIs (was: watcom tcp
>
>On 7/6/2011 7:10 PM, Bernd Blaauw wrote:
>> That funny URI syntax was grafted on. What exact URI are you using? Are
>>> you adding "ftp://"; or just "//" ?
>> FreeCOM (maybe also MSDOS command.com or 4DOS) seem to split arguments
>> at the "/" level. See the "FOR LOOP" in my batchfile, with batchfile
>> called as: ftp.exe ftp://ftp.xs4all.nl/pub/test/10mb.bin
>>
>> resulting in:
>> ftp.exe //ftp.xs4all.nl
>> (on which it chokes, not knowing how to handle //).
>>
>> Basicly there are 2 options:
>> 1) find a way to strip the prepending "//" before feeding to FTP
>> 2) allow FTP to accept them and strip it themselves, requiring code changes.
>>
>
>Ah - I forgot to take the command line parsing into account.  What 
>happened to the "ftp:" before the "//" in this case?
>
>Let me see how this behaves on my other systems before deciding what to 
>do.  I don't want to build in workarounds for strange command line 
>parsing into the code.  A more general solution might be to allow the 
>parameter to be quoted on the command line so that I can just handle 
>standard URI syntax.
>
>
>Mike
>
>
>
>------------------------------------------------------------------------------
>All of the data generated in your IT infrastructure is seriously valuable.
>Why? It contains a definitive record of application performance, security 
>threats, fraudulent activity, and more. Splunk takes this data and makes 
>sense of it. IT sense. And common sense.
>http://p.sf.net/sfu/splunk-d2d-c2
>_______________________________________________
>Freedos-devel mailing list
>Freedos-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to