copel wrote:

1. I switched off compare by file size as I understood there is not way to handle that.

There is. Force binary transfer mode. File size will then be the same.

2. about the time - I read what you suggested but you wrote there that the time problem should not occur in SFTP so how does that apply to me?

Sorry, I have not noticed that you use SFTP already. I suppose that when you upload manualy one local file to remote directory, the timestamp is different. What is the difference?

Thank you, but

1. I switched off compare by file size as I understood there is not way to handle that.
2. about the time - I read what you suggested but you wrote there that the time problem should not occur in SFTP so how does that apply to me?
Besides that - I have no way to absolutly synchronize the time on the server and on WinSCP.

How can I prevent the massive upload for every changed file?

Noam.

copel wrote:

1) the server is in a different time zone

Please read timestamp problems topics for more details.

2) there is a small different in the file sizes (as WinSCP displays it) between the local and remote.

From Preferences window you may turn off using file size as compare criterion. However it is off by default.

Hi all,

the problem is with WinSCP 3.5 (SFTP v3).
I use "keep remote folder up to date" to synch some php code on my PC with a remote unix folder.
The problem is that every time I modify one file on my PC, ALL of the files on that folder are uploaded to be synchronized - and they havn't been changed at all. this is causing me to wait much to long for 1 file to be udated.
I don't know if it's relevant but
1) the server is in a different time zone
2) there is a small different in the file sizes (as WinSCP displays it) between the local and remote.

I use Win XP.

Thanks for your time.

Copel.