First of all, thank you for providing such a good open source program. The edit file window that saves and uploads when finished is very helpful!
I just have a couple questions:
When downloading large files over FTP or FTPS as a background transfer, the wi-fi internet kept dropping and re-logging in and this crashed WinSCP several times. When I logged into the FTP(S) server again later I was not sure how to resume the download from where it left off. Are there instructions for doing this? Could WinSCP automatically check if there is a file with the same name in the folder and whether to resume or overwrite?
The second request is very minor/low priority:
Your edit/save/upload window makes WinSCP very useful for modifying files from a remote location where local copies of the files should not be kept. I am currently using Migale Eraser (open source) to securely erase the downloaded files from WinSCP's temporary folder, but it would be good to have a built-in setting that will securely erase all temporary files. The standard is currently Department of Defense Manual 5220.22 M or Gutman.
I'm using Win XP Home SP3 on an Asus Eee PC (Intel Atom 1.6 GHz, 1 GB RAM). The FTP server is IIS Publishing Service 7.5.
I should also mention that the main file was over 600 MB but the protocol was FTPS, not SFTP or FTP. After I re-logged in, the file was listed in the background transfer queue at 55% but the only option on the right-click menu was Suspend even though it was not downloading. Clicking Suspend did not change anything (it did not change the menu to Resume). When I dragged & dropped the file, it overwrote the file and did not ask to resume.
WinSCP does automatically resume after automatic reconnect. There may a bug though. There's no way to explicitly ask for resume when starting background transfer manually. Either you need to enable confirmation for background transfer or use foreground transfer to manually resume. _________________ Martin Prikryl