Hi,
Core FTP LE (Version 1.3c build 1447.4) seems to have a problem when determining time stamps. When uploading I get the message box informing me about the fact that a file with that name already exists. It tells me that the remote file is 10:08 and my local file is 8:16. Naturally, the "overwrite if newer" does nothing in such a case. However, the remote file time displayed in the dir listing is 8:08 (which is the true of my last forced download).
My settings are:
1. Convert files to GMT=true
2. Hour offset for file/folder date=+1
3. No use of MDTM
The faulty display of 10:16 also would explain why the -ON option from the commandline doesnt work.
Any ideas? Any thing I am overlooking?
Thanks
Friedrich
Overwrite Newer
My first suggestion would be to try installing build 1458 (or if there's a newer since I last installed). There have been quite a few fixes since your build.
You can find the latest build on the downloads' page on the developer's build, or click the following link:
http://www.coreftp.com/download/setup.exe
Any settings you have in your current install will be applied to the newest install. Installing over the current software won't harm anything (in my experience - ever). Since the install can make a backup as well anyway, it couldn't hurt to try this first.
You can find the latest build on the downloads' page on the developer's build, or click the following link:
http://www.coreftp.com/download/setup.exe
Any settings you have in your current install will be applied to the newest install. Installing over the current software won't harm anything (in my experience - ever). Since the install can make a backup as well anyway, it couldn't hurt to try this first.
Thanks for the quick response.
However, the problem still persists with 1458. I found out something more curious: After downloading the file from the server, it will have a timestamp of 10:16 displayed on my windows, even though on the server dir listing it appears as 8:16. When trying to upload the same file back to the server it will show a message stating that both files have a time stamp 10:16. So I gather that CoreFTP is internally working with a different time stamp than displayed in the dir listing and additionally it remains a mystery to me how it has been calculated. The only thing I can think of is that I am 1 hour ahead of Greenwich time and we have summer time now, so that gives me another hour before GMT. Basically my time right now is GMT+2 (although only GMT+1 is displayed)....Still something smells sort of fishy....
Friedrich
However, the problem still persists with 1458. I found out something more curious: After downloading the file from the server, it will have a timestamp of 10:16 displayed on my windows, even though on the server dir listing it appears as 8:16. When trying to upload the same file back to the server it will show a message stating that both files have a time stamp 10:16. So I gather that CoreFTP is internally working with a different time stamp than displayed in the dir listing and additionally it remains a mystery to me how it has been calculated. The only thing I can think of is that I am 1 hour ahead of Greenwich time and we have summer time now, so that gives me another hour before GMT. Basically my time right now is GMT+2 (although only GMT+1 is displayed)....Still something smells sort of fishy....
Friedrich
Ok, by turning off the "Convert time to GMT" flag and doing a manual +2 I was able to get the timings to work internally: just the times on the dir listing are off, but it seems that I can work with the -ON flag from the command line [and that is really what I am after! No other FTP program so far had that option in its command line prompt, and I need to execute some kind of batch file after doing a CVS commit ]
If this issue is ever resolved I will sure be willing to test it out.
Thanks
Friedrich
If this issue is ever resolved I will sure be willing to test it out.
Thanks
Friedrich