Windows error code 3

[Anonymous]

I've been stuck on 3.18 because I've been getting

"Error copying file:
"" ->
"J:\Podcasts\.ffs_tmp"

Windows Error Code 3: The system cannot find the path specified."

on versions 3.19 and 3.20 when a folder deletion occurs in the master
directory that I mirror to my mp3 player. At this point I consider this to be
a petty annoyance but I'm still left to wonder why.

-- DSW

[Zenju]

Can you give me a bit more information about this? What are the actual
filenames. Is this reproducible? What are the conditions, is it dependent on
settings? What is the smallest scenario that reproduces this?

Thanks, Zenju

[Zenju]

Is this still reproducible with v3.21?

[Anonymous]

So far no problems with 3.21 so thank you for sorting out whatever might have
been the issue.

One question as long as I've got your ear. I use mirroring for my syncing,
however when I delete a folder in the master directory, while the file in the
mirrored folder on the slave side is deleted, the folder itself is not,
leaving an empty folder on the slave side.

Just wondering...

-- DSW

[Zenju]

> sorting out whatever might have been the issue.
I was most definitely what's called "undefined behavior" in C++ and caused by
a seemingly unrelated bug I fixed in 3.21.

> leaving an empty folder on the slave side.
Surely not the intended behavior. Can you give me a "minimal" example that
allows me to reproduce this?

[Anonymous]

Here's my working example. I sync a podcast folder on my c drive to a
comparable folder in my mp3 player daily (recognized as a separate external
drive by my vistabox). I use FFS in mirroring mode for syncing but, as I
mentioned above, when I delete a folder on the c drive, while the comparable
files are deleted on the player, the empty folder remains.

It would be great if the folder was likewise deleted... that's all.

Thanx for bending your ear to this.

-- DSW

[Zenju]

I cannot imagine that this could be due to some bug in FFS. Have you done a
few test, e.g. deleting with explorer and see if this is some general issue?

[Anonymous]

One final point before putting the non-deletion of folders to be as it were. I
can get empty folders deleted when I use the FFS as a stand-alone application,
however I almost always use a batch syncing file I created from FFS and in
that case empty folders on the synced side of the equation still exist.

As I said when we first started discussing this, it only ever amounts to a
petty annoyance for me, but I appreciate you taking an interest in this
anyway.

-- DSW

[Zenju]

There isn't any technical difference in batch (= starting ffs_batch files) or
GUI mode, both run the same synchronization algorithm. So there must be some
difference in the synchronization settings, or it is some side-effect
unrelated to FFS.