Ah, thank you! I will try that.
Just so that I understand correctly, during upload FFS first copies the file to the temp file, when transfer is completed correctly it will delete existing copy and rename the temp file to correct extension. This is to prevent overwriting an existing copy with a ...
Search found 5 matches
- 07 Apr 2022, 07:57
- Forum: Help
- Topic: fixed sub-folder for temp files?
- Replies: 2
- Views: 596
- 05 Apr 2022, 17:09
- Forum: Help
- Topic: fixed sub-folder for temp files?
- Replies: 2
- Views: 596
fixed sub-folder for temp files?
Dang, I hit a snag (and it was going so well!). FFS works really well for my use case, but I have a problem with the temp files that get created in the target folder during syncing.
My target folder is set to append only and that of course throws a spanner in the works. Before I used a tool that ...
My target folder is set to append only and that of course throws a spanner in the works. Before I used a tool that ...
- 04 Apr 2022, 14:13
- Forum: Help
- Topic: Win10 Home 32-bit: Installation files are corrupted....
- Replies: 4
- Views: 350
Re: Win10 Home 32-bit: Installation files are corrupted....
Understood, I am investigating, but apart from this the system is showing no other symptoms.
- 04 Apr 2022, 13:45
- Forum: Help
- Topic: Win10 Home 32-bit: Installation files are corrupted....
- Replies: 4
- Views: 350
- 01 Apr 2022, 16:02
- Forum: Help
- Topic: Win10 Home 32-bit: Installation files are corrupted....
- Replies: 4
- Views: 350
Win10 Home 32-bit: Installation files are corrupted....
Hi,
Unfortunately I have a legacy Windows 10 HOME 32-bit instance. I've downloaded the local and the portable version and have both installed. Installation of the local version went through without any warnings, but when I try to run the executable a window pops up (the same when I try to launch ...
Unfortunately I have a legacy Windows 10 HOME 32-bit instance. I've downloaded the local and the portable version and have both installed. Installation of the local version went through without any warnings, but when I try to run the executable a window pops up (the same when I try to launch ...