fots wrote:

Ah, I see, I think this is not working for me because I initiate the resume manually. Manually resuming works perfect with SCP but not FTP.

It does not work with SCP neither. Only with SFTP. I'm confused...

martin wrote:

With FTP .filepart is not appended. Hence the resume does not work automatically always. But when connection is lost it should work nevertheless. Please post a log file showing the problem.

Ah, I see, I think this is not working for me because I initiate the resume manually. Manually resuming works perfect with SCP but not FTP.

Thanks for all your help :)
Fots

With FTP .filepart is not appended. Hence the resume does not work automatically always. But when connection is lost it should work nevertheless. Please post a log file showing the problem.

Hello, and thanks so much for your help once again.

I have retested the auto resume with FTP and I'm afraid it doesn't work for me. It does work perfectly with SFTP.

The main difference I noticed with FTP and SFTP when I copied a file is that SFTP creates a .filepart file while the file is copying. FTP doesn't seem to do this.

I tried to rename the file to .filepart and retry with FTP but I'm afraid I had no luck getting it to autoresume once again.

Any ideas?

Best Regards
Fots

Only now I have realized that it should work even with FTP. So now I wonder why it does not work for you. First, make sure you have automatic reconnect enabled in preferences.

Hello and thanks so much for your answer. Yes, what I really would love is auto-resume for FTP, since this would make sure that the transfer of big files doesn't start again.

I think an implementiation similar to the following would be excellent...

If uploading and file exists, do the following...

- Ask
- Overwrite
- Skip
- Resume
- Upload with new filename (maybe Filename.ext1 or something similar)

And the same options for downloads

Thanks very much for your time
Fots

fots wrote:

Regarding 2), the problem is that if I leave it to upload overnight and a transfer loses connectivity half way through, I want it to reconnect and continue automatically, the prompt will mean that I won't see until morning.

Are you using FTP? With FTP WinSCP does not support automatic resume. But if you disable overwrite confirmations, it should at least automatically reconnect and restart the transfer. Automatic resume is supported with SFTP.

Would you consider implementing 2) and 3) ?

The request 3) has been added to tracker.

Hello, thanks for your help.

Regarding 2), the problem is that if I leave it to upload overnight and a transfer loses connectivity half way through, I want it to reconnect and continue automatically, the prompt will mean that I won't see until morning.

Would you consider implementing 2) and 3) ?

Thanks so much for the awesome program :)

Cheers
Fots

fots wrote:

1) Is there a way to view messages being sent to the server (like an FTP log)?

See Logging tab of login dialog.

2) Are there file-exists actions for upload and download? For example to say, resume file upload if the file exists, or skip the download if the file exists .etc

You should bet prompt if the file exists already, giving you all the options. Unless you have turned the prompt off in preferences.

3) Is there a way to make WinSCP shutdown my PC when the download or upload is complete?

No.

bump, anyone?

Hello, I really love this program and have been using it for SCP for a long time.

I am looking to switch to WinSCP for FTP now (I used to use FlashFXP) and can't seem to figure out a few things.

1) Is there a way to view messages being sent to the server (like an FTP log)?

2) Are there file-exists actions for upload and download? For example to say, resume file upload if the file exists, or skip the download if the file exists .etc

3) Is there a way to make WinSCP shutdown my PC when the download or upload is complete?

Thanks very very much! :)

Cheers
Fots

P.S: If anyone is having trouble with FTP disconnecting, it may be due to them not using Passive mode, for me Passive mode is far far more reliable for FTP. I suggest that you make Passive mode default for FTP connections :)

I tested my FTP in 2 WinSCP windows, one was using passive and one was using active. The active timed out after about 5 minutes, but the passive kept going without ever disconnecting, I still have it open now.