I've used Freefilesync for years now, and I've never had problems with updates. But upgrading to 6.12 was tragic. It won't read the old .ffs files anymore (I get a long message about the software not being able to read the xml config files), the Compare function won't detect variations unless I create a new ffs file, and the compare results won't update after syncing (files with different time stamps still show as different time stamps). But I haven't found similar issues in this forum, apparently.
I had to revert to 5.5, which is perfect, and I think I'll stick to it for a long time now.
Cheers.
Big issues with 6.12
- Posts: 1
- Joined: 2 Jan 2015
- Posts: 1
- Joined: 6 Jan 2015
I appear to have a related problem with version 6.12
I tried to mirror local drive (L) to local USB stick (U)
1. Compared "L" to "U" using "file time and size" option - numerous "unsynchronized" files were found. (manual comparison revealed differences in the time stamps only)
2. Synchronized the drives using the "Mirror" option
3. Again compared "L" to "U" using "file time and size" option - and the same "unsynchronized" files were found.
Obviously "something is amiss here....
Next, I re-loaded version 6.11
I tried the same operations and received the same results i.e. the "mirror" option apparently did not re-write the files so I would end up with identical files with identical time stamps.
I then synchronized the drives using the "Update" option. - This time the files were synchronized properly and all is well.
I have not tried this work-around using version 6.12 (and, since the files are in sync now, I can't try it right now) but I suspect that work-around might work under 6.12 as well.
Of course, in the long-term, this is a problem that needs to be investigated by the FreeFileSync gurus.
I tried to mirror local drive (L) to local USB stick (U)
1. Compared "L" to "U" using "file time and size" option - numerous "unsynchronized" files were found. (manual comparison revealed differences in the time stamps only)
2. Synchronized the drives using the "Mirror" option
3. Again compared "L" to "U" using "file time and size" option - and the same "unsynchronized" files were found.
Obviously "something is amiss here....
Next, I re-loaded version 6.11
I tried the same operations and received the same results i.e. the "mirror" option apparently did not re-write the files so I would end up with identical files with identical time stamps.
I then synchronized the drives using the "Update" option. - This time the files were synchronized properly and all is well.
I have not tried this work-around using version 6.12 (and, since the files are in sync now, I can't try it right now) but I suspect that work-around might work under 6.12 as well.
Of course, in the long-term, this is a problem that needs to be investigated by the FreeFileSync gurus.
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
There's no difference between the sync variants when it comes to file copying and setting time stamps. FreeFileSync consistently checks for errors, but it's sometimes possible that no error is shown and still file times are not updated:
1. This behavior can be caused by a hardware problem.
2. It's also possible that some anti virus software is messing with the files after copy! For example the most recent release of Comodo Anti Virus tries to sneak-in hidden alternate data streams to newly copied files. The end result is that the time stamp is updated once again, but with the current time.
1. This behavior can be caused by a hardware problem.
2. It's also possible that some anti virus software is messing with the files after copy! For example the most recent release of Comodo Anti Virus tries to sneak-in hidden alternate data streams to newly copied files. The end result is that the time stamp is updated once again, but with the current time.
