As an alternative, enclosing the full path to the secondary program in double-quotes might work as well. That should make it be interpreted as a single string rather than being tokenized on whitespace. I've just always been careful about spaces, since many things in Windows share the Unix shell's pickiness about quotes and whitespace when parsing command lines.
The game of "How many of which kinds of quotes, in what order, do I need to prevent tokenizing in this case?" is never fun.
__________________
"Hey! I'm not illiterate. I had a book once. ...could've used some ketchup though..."
|