FreeFileSync Forum

Perhaps modifying the rule for MTP filesystems so that an offset is kept for the modification time from the true modification time, and applied during the comparison, would keep the model intact while helping with the issue (except with GS4)?

Hi Zenju, is MTP support possible? A lot of us have Android phones now which only support MTP. I tried some of the SMB servers for Android but they are buggy.

My new phone also only supports MTP. Please add support for MTP to FFS because I'm pulling my hair out over how to sync pictures with my phone now.

>In essence, after synchronization, you need to compare at least once more, to freeze file times of last modified files.

Does FFS do this now? Or do I need to do this manually?

Also, I see that there are two options in FFS to skip syncing a file - "space" prevents the file from being synced ...

I have a bunch of image files on my phone's SD card that I synced before the US switch to daylight savings time. Now when I do a "compare" FFS wants to re-copy these files. Wasn't the whole point of the weird creation dates that FFS puts on FAT files to prevent this issue?

Right-click on the files and there will be options for that.

Why does the date get changed when doing a Compare?

Yes. *\cap\ matches

\cap\

\downloads\cap\

etc.

cap\ only matches directories at the top level named cap

Even weirder, if I copy files to the SD card from Windows explorer, then check the creation date, it is the current date/time. Then if I run FFS and do just a compare operation, the creation dates of the files are changed to 2052.

Even the synch.fss_db file has a creation date of 2/25/2052 8:30AM

I'm syncing files to my Android phone's SD card from my Windows 8 VM running under Parallels (OSX) and the files that are created there get created with a date between Feb 19 2052 (tomorrow) and June 2052. When I copy files using Windows Explorer the date is Feb 18th (current time). The modified ...

Exclude all folders (not files) named "cap"

*\cap\

Exclude all folders (not files) named "cap" which are located in the same path (so, they are sub folder or a sub sub folder and so on) after a folder named "Downloader"

*\Downloader*\cap\

*\Downloader*\*\cap\

I'm confused. If I understand the scenario, it's something like:

1. Folder pair is created to mirror local PC client files to network
* FFS runs and syncs a bunch of files from local PC to network
* User deletes a bunch of files on local PC client
+ User hibernates while FFS is running
+ FFS temp ...

Argh. Thanks :-)

I created the files on the left by copying them from the PC NTFS file system to a USB hard drive formatted as NTFS, then copied from USB hard drive to MAC OS. MAC OS must have removed the space I guess?

I'm confused. If I understand the scenario, it's something like:

1. Folder pair is created to mirror local PC client files to network
* FFS runs and syncs a bunch of files from local PC to network
* User deletes a bunch of files on local PC client
+ User hibernates while FFS is running
+ FFS temp ...

Here is the file list.csv:

Legend
Both sides are equal,'==
Copy new item to left,create <-
Copy new item to right,create ->
Overwrite left item,update <-
Overwrite right item,update ->
Delete left item,delete <-
Delete right item,delete ->
Do nothing, -
Conflict/item cannot be categorized,conflict ...

I have a sync job to copy some video files. After running "Compare", nine of 29 files are to be copied in both directions. The other 20 are not being touched. As far as I can tell the nine files have the same byte count and date to the second.

Why would FFS copy files from right to left then from ...

Some additional interesting info here:
http://channel9.msdn.com/Shows/Going+Deep/UAC-What-How-Why#c633305694960000000

1) Mapped drives get interesting in combination with the "split-token" account, because of a weird dichotomy in the system (in large part historical) -- the drive letters are per ...

See this workaround:
http://support.microsoft.com/kb/937624

I've found that elevated processes can't access network resources, at least on my home machine. Try accessing the network from an elevated command prompt.