OK. Thanks very much for your kind answers! :D
And thanks for the great program! :wink:

Anonymous wrote:

I guess what I was more interested in is this:
- if I start winscp with no /passive switch, but somewhere on the way I issue a

call PASV

command, will winscp "recognize it" and use passive mode from than on?

No.

Also somewhat related to this... I noticed that whenever Filezilla notices that a

PORT *,*,*,*,*,*

command results in a 5** response it automatically switches to passive mode. It's kind of logical to do so too. Is there a way to reach to this kind of "result" with WinSCP?

No. Though the next version will suggest you to use passive mode in error message, when the server fails to open active connection.

I guess what I was more interested in is this:
- if I start winscp with no /passive switch, but somewhere on the way I issue a command, will winscp "recognize it" and use passive mode from than on?

Also somewhat related to this... I noticed that whenever Filezilla notices that a command results in a 5** response it automatically switches to passive mode. It's kind of logical to do so too. Is there a way to reach to this kind of "result" with WinSCP?

You can do:

Though WinSCP won't use the setting as it explicitly sets transfer mode before each transfer. Use option transfer to set transfer mode in script.

Is there a way to specify ftp commands in scripts?
Like how do I send a command. If I can specify commands will the client be aware of those commands (better said of their effect)?