Are you mounting the TrueCrypt container as "read-only" or not?
If not then there is no way to avoid the conflicted copies.
When mounting the container in full-access the access-time and date of the files you browse (in the filesystem) are always changed (within the container). This will result in a change in container-file. You can check this by doing a file-compare on the container (and copy) after mounting and dismounting (with fc.exe or other utility). Any change in the container will result in an upload by Dropbox. When multiple machines have the file open you get the conflicted copies.
The only way around this might be to open the container as "read-only".
(In that case you can't change any files. When you need to change files you need to dismount and mount the container again with full-access)
In the Windows-version you can choose Volumes
, Mount Volume with Options
.
Then choose Mount volume as read-only
:
Edit:
You can set the "read-only" as default for all future mounts. When you need to change files you can use the method above to mount with full-access (by unticking the box). To set "read-only" as default choose Settings
, Preferences
and tick Mount volumes as read-only
.
Edit 2:
Even if you can set Windows to not update the file-system (and effectively the container) on access of a file (for the access-timestamp) TrueCrypt itself updates the container also when mounting as not read-only. See this image of a container right after mounting it (78KB written) with full-access without even accessing it:
(so there is no point in looking at the access-timestamp as TrueCrypt itself updates the container too) So you're only left with the read-only option.