Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Bug #454 not really solved?

Thanks for your post. This bug has been added to tracker.
Rolf

Bug #454 not really solved?

I use WinSCP 4.2.3. on Windows Server 2003 R2 Standard Edition Service Pack 2.
From an application I call a batchfile called WinSCP_send.cmd as follows:
Winscp_send hostname username password "/usr/sapio/BE2/c4/dtaus/" "D:\dir withblank\filename"

I need the double-quotes here, because the path\filename within the double-quotes is one command line parameter.

In the batchfile, I take the command line parameters and invoke WinSCP as follows:

WinSCP.com /command "option batch on" "option confirm off" "open %2%:%3%@%1%" "put %5% %6%" "exit" >> %RESPONSEFILE% 2>>&1

In the RESPONSEFILE I 'echo' the filename and see, that the filename is complete including the double-quotes.

Here, WinSCP takes D:\dir as the file and withblank\filename as an unknown command. This behavior does NOT change if I use additional double quotes around Parameter 5, like:

WinSCP.com /command "option batch on" "option confirm off" "open %2%:%3%@%1%" "put "%5%" "%6%"" "exit" >> %RESPONSEFILE% 2>>&1


or additional double double-quotes, like

WinSCP.com /command "option batch on" "option confirm off" "open %2%:%3%@%1%" "put ""%5%"" ""%6%""" "exit" >> %RESPONSEFILE% 2>>&1

It never works.
If I open a dos-box (cmd) and call WinSCP.com without using a batchfile, it works.

Am I doing wrong, or is bug 454 only partly fixed?