I am trying to upload a large file over several sesssions so need resume. I first tested it to see how it works. Didn't want to find out I misunderstood something 9 hours into the process and there is nothing in the CoreFTP help about the resume feature so I realized I would have to start guessing and experimenting.
I found if I press the break button it aborted the upload but I could not then resume. No sensible error message - it just would neither resume nor overwrite nor sing me a song. So I closed CoreFTP. When I opened it again I could then select upload for the file again and it offered 'resume' as an option. So that seems to work except I don't know why I had to close and re-open the program.
Then I tried deliberately disconnecting from the net to simulate my ISP cutoff. This time the file part already uploaded seemed to be gone. This is a worry as it means (a) that I would have to attend the program, anticipate my cutoff, and abort the upload manually, etc. All the time fingers crossed that there is not an unanticipated cutoff!
I tried to copy and paste an odd file on my website so I might at least make a backup during the process and thus resume from my last manual abort but it seems there is no way to copy a file on the site that I can see.
I tried some other stuff like renaming a different file to the same name to see if CoreFTP would try to resume by adding on to that and it did. I was merely exploring what was possible.
Then I noticed an odd file called -pureftpxxxxx something or other and dated today. I guess it must be CoreFTP that made it, maybe a leftover of the failed upload.
Not knowing if I had botched things up I preferred a fresh start so tried to delete it. No you can't - it's prohibited. Tried to rename it - you can't. So here's fine kettle of fish - a 1Mb file wasting space on my website for the next 10 years.
So I come here for a little light on all the above and NOW notice when looking for the odd 'pureftp' file to get its exact name that I can't find it! Maybe CoreFTP deleted it after a while?
Tell me about resume and prohibited names
UPDATE: Tried again last night and left it running. Got up this morning and this time there is a true part file, I mean with the normal name, on the site. The upload got cutoff after 3 hours. So without even closing CoreFTP I reconnected and clicked upload again and got offered resume so this time all looks well.
UPDATE: Uploaded the whole 90Mb OK now. I set it going late last night. This morning it had disconnected after 3 hours of course but had uploaded over a third. It resumed OK as soon as I connected again and simply selected upload then resume. Repeated in one more session and was done just after midday. Nice one.
Getting to like this CoreFTP better than WS_FTP which I used for years.
Getting to like this CoreFTP better than WS_FTP which I used for years.
I am just uploading an update and it is a pain. I see this pureftp server needs 15 minutes to rename its temporary name back to the true name. I can then proceed with the upload. This upload will need four resumes so this will add at least an hour to the total time when I can do nothing but wait. Is there any workaround? What is the server actually waiting for? What I mean is, both CoreFTP and this PureFTP server both support resume once the part already uploaded renames itself. So how does PureFTP expect resume to work correctly?