The files are binary and smart files comparison is not checked.
I must add another symptom that may be related to this but the opposite result. I have a 7.5GB file that I copied to another system and compared them across the network as being the same via the DOS FC command with the "/b" option.
But when I use Synchronize It with the Compare by "Content" option it immediately (no time to read any significant part, if any, of the two 7.5GB files) comes back and wants to copy this file from the source to the target as if they were NOT equal even though they are equal.
The reason these two cases may be similiar is for some reason the comparison appears to be aborting early in both cases. The first time maybe giving up before encountering different bytes in the two files and the second time maybe giving up immediately before comparing anything and assuming the files are different.
Note that this issue may or may not be related to the posting I did in two other threads thinking there was a problem when I upgraded from V3.1 to V3.4. Apparently, the issue I raised in those posting with the network connection being destroyed during a synch operation may actually be outside Synchronize It with my suspicion being on some Microsoft SMB network security fixes which I applied about the same time I upgraded to V3.4 and which all my problems started.
The other two threads are noted below:
"Delayed Write Error":
"Losing network connection during Synch operation":
If the issues are related to the Microsoft fixes I have not noticed any issues outside of using Synchronize It but of course I probably don't have another app that is stressing the network connection as much either.
Hope this helps,