OK, I think this is due to the (highly) stupid way of double-quote
handling of the Windows "system" command: to be short, if the
command starts with a double-quote, it removes it, as well as any
trailing double-quote. So if your command is
"mycommand.exe" "myarg1" "myarg2"
the system will try to execute
mycomand.exe" "myarg1" "myarg2
and (of course) fail. Up to now, I could not find a reliable way to
avoid this kind of problem (the first double-quote is needed if your
command could contain a space). So, currently there's no
solution.