How to avoid creating hidden files like SyncToy_*.dat in synchronized folders?

All replies

• 

  

  1

  Sign in to vote

  Hi,

  I’m afraid we cannot avoid these files being created because SyncToy need to work with them. SyncToy stores metadata which represents information such as “which files have been synced” and “how new they were when last syncing” and so on. This information helps SyncToy decide which file and which folder do not need to update, thus reduce the duplicate work.

  The “SyncToy_*.dat” files is the only way that SyncToy 2.0/2.1 stores such metadata for each folder.

   

  Thanks.

  ---

  This posting is provided "AS IS" with no warranties, and confers no rights.

  • Proposed as answer by JiGuang Thursday, November 12, 2009 7:14 AM

  Thursday, November 12, 2009 7:14 AM
• 

  

  0

  Sign in to vote

  Hi,

  I’m afraid we cannot avoid these files being created because SyncToy need to work with them. SyncToy stores metadata which represents information such as “which files have been synced” and “how new they were when last syncing” and so on. This information helps SyncToy decide which file and which folder do not need to update, thus reduce the duplicate work.

  The “SyncToy_*.dat” files is the only way that SyncToy 2.0/2.1 stores such metadata for each folder.

  But there are some different ways to store this information: registry, config-files in user profile directory, for expample. Anyway these dat-files cannot be useful for other users if they are synchronizing the same target directory that's why these service files can be stored in any other place instead of synchronization  target directory.
  

  Friday, November 13, 2009 9:34 AM
• 

  

  1

  Sign in to vote

  Hi t0lik75,
  
  Thank you again for being concerned about SyncToy! And sorry that I have not replied you in time (I was in a vacation).

  There is a reason that something must stay with each sync folder. That is the driver letters of sync folder may be changed.
  
  For instance, a sync folder is located in a USB storage device and was marked as “f:\” in a sync session. But in the next sync session, its driver letter has been changed into “g:\” because some other storage device had been loaded as “f:\” already. If there is nothing staying with the sync folder, SyncToy will have no way to make sure which one is the sync folder (“f:\” or “g:\”?), or whether the sync folder is a left folder or a right folder. Thus SyncToy 2.0/2.1 must keep a file or something indicating necessary information in each sync folder.
   
  I am sorry for the inconvenience. But for now, there seems no better way to resolve the driver letter issue, so each sync folder needs to contain its .dat file.

  Thanks

  ---

  This posting is provided "AS IS" with no warranties, and confers no rights.

  • Marked as answer by Yunwen Bai Thursday, December 3, 2009 6:14 PM

  Thursday, December 3, 2009 11:03 AM