mak wrote:

But where is the link you posted last time. On this Forum Page I did not find any link.

Here:

martin wrote:

Please read F.A.Q.

A more issue is that WinSCP could not deal with temporay files created by MS office (e.g ~wrl00359.tmp) , (I think these are not files but link to other files). Also Thumbs.db files (these files created by Windows for thumbnail view of files.) can not be copied by WinSCP. Beacuase each time WinSCP encounters these these files it aks for (skip, abort, retry) therefore it takes too much time to press button to proceed these message. Either these should be copied or there should be option (skip all) to skip all theses file.

That's probably because the files are locked by the office, so they cannot be read by other application. I'll check it.

martin wrote:

So it is not slower, it just downloads more files that it should, am I right? That's what the link I've posted the last time should help you to avoid.

Yes it downloads more files. But where is the link you posted last time. On this Forum Page I did not find any link.
-----------------------------------------
A more issue is that WinSCP could not deal with temporay files created by MS office (e.g ~wrl00359.tmp) , (I think these are not files but link to other files). Also Thumbs.db files (these files created by Windows for thumbnail view of files.) can not be copied by WinSCP. Beacuase each time WinSCP encounters these these files it aks for (skip, abort, retry) therefore it takes too much time to press button to proceed these message. Either these should be copied or there should be option (skip all) to skip all theses file.

mak wrote:

yes.
I think this is because of the way unix and windows deals with timestamps of files. I noticed that WinSCP also overwrites those files which have not been modified.

So it is not slower, it just downloads more files that it should, am I right? That's what the link I've posted the last time should help you to avoid.

martin wrote:

mak wrote:

Synchrozie local work very slow in WinSCP.

Do you mean that it is slower then "synchronize remote"?

yes.
I think this is because of the way unix and windows deals with timestamps of files. I noticed that WinSCP also overwrites those files which have not been modified. (there is free software SyncBack, it is able to deal with this problem but unfortunately SyncBack does not support SFTP protocol, which WinSCP supports, I wish WinSCP and SyncBack could combine their good features)

mak wrote:

Synchrozie local work very slow in WinSCP.

Do you mean that it is slower then "synchronize remote"?

I think it even overwrite thoses file in local that are not changed.

Please read F.A.Q.

Synchrozie local work very slow in WinSCP.
I think it even overwrite thoses file in local that are not changed.
please check this issue.

Thanks for info. However I believe that the file is actually downloaded once. It is just wrongly printed twice on the screen. I'll fix it in the next release.

When running WinSCP in batch/console mode, and using synchronize local, it always downloads files twice. One time just as file.whatever, the second time as /.../file.whatever. It is exactly the (source) same file, the only difference is the /.../.

When synchronizing for a second time and the file is unmodified, it skips it, so it is not a timestamp issue between the client and server. The problem does not occur when using sftp (v3) for transfer.

I'm using WinXP SP2 with WinSCP 3.7.1 as a client, and FreeBSD 4.10 with OpenSSH3.9p as a server. Connection is made through SSH2 (AES encryption, SCP2 transfer).