Search found 13 matches
- 17 Apr 2020, 10:02
- Forum: Help
- Topic: Can't See Veracrypt Container File
- Replies: 5
- Views: 1412
Re: Can't See Veracrypt Container File
I don't remember what is the option's checked state (I don't have VC on this machine to check), but it should be set to change the container time according to last write/access time. FFS checks if the file has been modified by it's modification time (in the file's metadata) and size*. VC containers ...
- 16 Apr 2020, 09:25
- Forum: Help
- Topic: Can't See Veracrypt Container File
- Replies: 5
- Views: 1412
Re: Can't See Veracrypt Container File
Also make sure VeraCrypt's option to not update container file modification time is unchecked. It will prevent FFS from detecting that the files has been changed, and it will not sync. I had this problem.
- 08 Apr 2020, 06:37
- Forum: Help
- Topic: Stop Checking For Updates?
- Replies: 12
- Views: 5007
Re: Stop Checking For Updates?
I too have this problem in version 10.19 Donation. Whenever I disable the "Check for updates" option, it will enable itself after a week or two. This is really annoying and disrespectful towards the paying users, that it hasn't been fixed for so long.
- 20 Feb 2020, 15:25
- Forum: General Discussion
- Topic: Option to define conflict resolution for two-side sync
- Replies: 7
- Views: 1273
Re: Option to define conflict resolution for two-side sync
Hi, it works now. You are right, in the second sync there are only conflicts left, so FFS doesn't have to distinguish between a conflict and an updated file.
That solves the problem for me. Thank you.
That solves the problem for me. Thank you.
- 20 Feb 2020, 06:33
- Forum: General Discussion
- Topic: Option to define conflict resolution for two-side sync
- Replies: 7
- Views: 1273
Re: Option to define conflict resolution for two-side sync
Thank you Plerry for the idea of solution. I just tried it, and sadly it doesn't work. When I run the second custom sync, it marks all the files as "do nothing", because for this sync FFS ignores the database, so it doesn't detect a conflict, but a newer file. I would have to manually chan...
- 18 Feb 2020, 16:37
- Forum: General Discussion
- Topic: Option to define conflict resolution for two-side sync
- Replies: 7
- Views: 1273
Re: Option to define conflict resolution for two-side sync
No comments?
Of course I meant "two-way", not "two-side". I had to translate from my localized version :)
Of course I meant "two-way", not "two-side". I had to translate from my localized version :)
- 13 Feb 2020, 16:36
- Forum: General Discussion
- Topic: Option to define conflict resolution for two-side sync
- Replies: 7
- Views: 1273
Option to define conflict resolution for two-side sync
Hi, I need FFS to behave like this, but it doesn't seem possible. I want a <-- two-side --> sync for a directory pair, but without having to manually resolve conflicts. I just want all conflicts to be resolved by copying from left to right side. So in the directory pair settings I choose the "c...
- 12 Oct 2016, 08:04
- Forum: Help
- Topic: 8.5 still has the install.dat issue/problem
- Replies: 11
- Views: 3314
Re: 8.5 still has the install.dat issue/problem
I also have a problem with the install.dat file, but slightly different one. I use FFS mainly from a portable drive, to sync the drive's contents with three different computers. On all of the computers there is also a local installation of FFS that is used to sync stuff locally. When I upgrade FFS t...
- 12 Oct 2016, 07:40
- Forum: Help
- Topic: FFS should does not keep the sessions list in portable version
- Replies: 6
- Views: 1325
Re: FFS should does not keep the sessions list in portable version
Thank you very much! Despite the fix the program was still losing the session list while moving between computers. Only recently I have discovered that it was due to the fact that I used a wrong directory for the saved sessions. I have FFS installed both on my portable drive (to sync the drive with ...
- 04 Aug 2014, 05:33
- Forum: Help
- Topic: FFS should does not keep the sessions list in portable version
- Replies: 6
- Views: 1325
Re: FFS should does not keep the sessions list in portable version
Hi again. Two new versions have been released, and this is still an issue!
Zenju, have you seen this report? Can you confirm if this is a bug, or give other suggestions as to what may be wrong at my side?
Zenju, have you seen this report? Can you confirm if this is a bug, or give other suggestions as to what may be wrong at my side?
- 01 Apr 2014, 09:43
- Forum: Help
- Topic: FFS should does not keep the sessions list in portable version
- Replies: 6
- Views: 1325
Re: FFS should does not keep the sessions list in portable version
Okay, tried both options and none works.
1. When running FFS by shortexe, it still loses the recent sessions list when moving to another machine.
2. Vdrive does not detect my USB disk ("No removable drive"), even when run from the drive itself, and run as administrator (Windows 7 32-bit).
1. When running FFS by shortexe, it still loses the recent sessions list when moving to another machine.
2. Vdrive does not detect my USB disk ("No removable drive"), even when run from the drive itself, and run as administrator (Windows 7 32-bit).
- 31 Mar 2014, 09:03
- Forum: Help
- Topic: FFS should does not keep the sessions list in portable version
- Replies: 6
- Views: 1325
Re: FFS should does not keep the sessions list in portable version
Yes, I can open the ffs_gui files, they are not missing, they are in the correct place on the portable drive. Even more: when I click "open", the starting directory is the correct saved sessions directory (namely the FFS dir). Thanks for the suggestions. I installed the shortexe, and will ...
- 31 Mar 2014, 07:00
- Forum: Help
- Topic: FFS should does not keep the sessions list in portable version
- Replies: 6
- Views: 1325
FFS should does not keep the sessions list in portable version
I have installed the portable version of FFS on my portable had drive, that is synced against three computers (two Windows 7 and one Windows XP). I have created a shortcut to it in the drive's main directory, that works somehow due to Windows magic (because the dirve's letter is different on each co...