Did you do something special to be able to delete the files manually? When I try to delete them I get an "unexpected error. error 0x80070052 the directory or file cannot be created.
No, I have no trouble in using Windows Explorer to select the directory "RecycleBin.ffs_tmp" and delete it. Maybe ...
Search found 5 matches
- 08 May 2016, 19:08
- Forum: Help
- Topic: FFS cannot cleanout recycleBin.ffs_tmp
- Replies: 17
- Views: 11443
- 17 Apr 2016, 21:36
- Forum: Help
- Topic: FFS cannot cleanout recycleBin.ffs_tmp
- Replies: 17
- Views: 11443
Re: FFS cannot cleanout recycleBin.ffs_tmp
I have been getting this error, too, for a long time. Currently on FFS 8.0. Only on my Vista SP2 system, not my XP SP3 system. I always end up having to go into the parent source directory and manually delete the RecycleBin.ffs_tmp directory.
I do not see any pattern regarding when or why this ...
I do not see any pattern regarding when or why this ...
- 28 Aug 2015, 16:47
- Forum: General Discussion
- Topic: Request: Fix parsing of volume GUIDs in pathnames
- Replies: 5
- Views: 1459
Re: Request: Fix parsing of volume GUIDs in pathnames
The volume GUID syntax is not supported by most higher-level Windows APIs. It should work for lower-level kernel APIs though, which comprise most of what is required for synchronization. Things like showing file icons, or recycle bin usage OTOH won't work.
If desperately needed, and using unique ...
If desperately needed, and using unique ...
- 28 Aug 2015, 03:30
- Forum: General Discussion
- Topic: Request: Fix parsing of volume GUIDs in pathnames
- Replies: 5
- Views: 1459
Re: Request: Fix parsing of volume GUIDs in pathnames
I'm surprised this was ever working, at least support for path by volume id was not deliberate functionality. The proposed solution for this scenario is to specify the path by volume name: see help file chapter " Variable drive letters ".
It would be worth looking at the old code to see if volume ...
It would be worth looking at the old code to see if volume ...
- 26 Aug 2015, 03:28
- Forum: General Discussion
- Topic: Request: Fix parsing of volume GUIDs in pathnames
- Replies: 5
- Views: 1459
Request: Fix parsing of volume GUIDs in pathnames
In the pathnames for FreeFileSync, I used to use volume GUIDs to avoid ambiguity about the source and destination. Volume GUIDs are almost-permanently assigned to storage devices. For example:
The left pathname: \\?\Volume{*GUID A*}\DocsToRead
The right pathname: \\?\Volume{*GUID B*}\ReadThis ...
The left pathname: \\?\Volume{*GUID A*}\DocsToRead
The right pathname: \\?\Volume{*GUID B*}\ReadThis ...