AceBIT

I created a TAR file of a large WinXP file structure, uploaded the TAR file to a Linux shared server and extracted the files. I then ran a Wise-FTP 3.1.0 Synchronize against the two systems and got lots of differences. At first, it appeared that the extracted files had the wrong timestamp. I am on EST (currently daylight savings), which is GMT -4. For example, the local file had a timestamp of 10:50am, while Wise-FTP showed a timestamp of 2:50pm on the remote file. However, this proved to be a red herring - when I logged into the Linux server, I verified that it was set to EST and that all file timestamps matched the WinXP values.

Disabling the date/time check in Synchronize still showed errors. After some digging, I believe Wise-FTP Synchronize has problems with 3-level directory structures. If I compare \local\a\b\ with /remote/a/b/ starting at the highest level directory, files in the 'b' subdirectory are always flagged as different (local overwrites remote). Files in the 'local' and 'a' subdirectores are not flagged. Furthermore, if I start the compare at the 'a' subdirectory level, no files in 'b' are marked as different. Enabling or disabling date/time check has no impact.
Regards, Norbert

PS. It would be useful if Synchronize showed why it had flagged a file as different (name, date/time, size). In the case above, the local file appeared to be older than the remote file (according to the timestamp displayed by Wise-FTP), which further confused the issue (newer files overwrite older files).