Timestamp errors, Impossible to solve?

[enonod]

I have read the posts regarding timestamp error. The problem is wider than expressed. Setting the DST 1 hour and FAT 2 seconds etc do not solve the problem.

I have a FAT32 drive connected to a network and it works fine.
Copying files from NTFS to the FAT32 means that the file at the FAT32 target have 1 hour added because FAT does not account for DST. Setting the profile to allow for the hour is fine if the file is again updated with 2 secs.

What actually happens is...
Source time 10.30 copied to Target 10.30 stamped 11.30
New Source 10.31 copied to Target 10.31 stamped 11.31
New Source 10.45 tries to copy over Target 11.31 gives error because it is no longer 1 hour difference. Waiting until after 11.31 would of course permit the synchronisation to work again.

This seems like a problem with no solution except CRC which takes for ever. Is there one please?

[TGRMN Software]