FreeFileSync Forum

That's kind of like retail pricing, isn't it...? ;-)

Sounds good to me. Don't forget the edge cases like doggrunner's.

Thanks,
Jeff Bowman
Fairbanks, Alaska

It's good to see you again, Dave :-)

A word about my accusation of lackluster support...

This was based on my impressions from approximately a year ago, when such was the case. As with everything, though, times and events change, demanding more or less of our attention as they ebb and flow. I understand.

But you're johnny-on-the-spot ...

Damn it Zenju!

When are you going to stop dragging everyone through this Adware/ExpiringDonationWare/BrokenInstall crap and just simply start selling licenses for your software?

What... are you afraid people won't pay money for it? Well I'm telling you WE WILL. This is hands down THE BEST file ...

have you tried the
Synchronization / Detect moved files
and either of the non-Permanent Delete-Files: options ?

I'm wondering if you aren't asking for something that is already there
FYI I've decided to abandon FFS for automation tasks, for these reasons . So I won't be performing the test ...

It'd be nice to hear from you on this, Zenju.

As it stands, it looks like I'm going to have to switch to RoboCopy for my automated sync jobs.

FFS still remains the best for one-off, ad-hoc projects, but for repetitive CLI-based actions there just seem to be too many problems. Can't run FFS from ...

Zenju... if you'd charge money for FFS, as I requested here, you'd be able to justify the time to find and fix problems like this.

With the proper attention, I imagine it could be fixed in a week. Not a year.

Thanks,
Jeff Bowman
Fairbanks, Alaska

Hi Stefan,
I have had a look at the filters but unfortunately I have no idea how to do exclusions. I have a vague idea how to type in a file path, but it doesn't work in this case. I think that this is a step too far as far as my computer ability is concerned.
I will stick with my old method of ...

have you tried the
Synchronization / Detect moved files
and either of the non-Permanent Delete-Files: options ?

I'm wondering if you aren't asking for something that is already there
Thanks for the lead: I'll try to work up some tests for these asap. It might be a day or two.

Thanks,
Jeff Bowman ...

at the moment FFS doesn't need .NET

it would be a step backwards for portable people and those not on Win OS's if it became a requirement
I probably erred in not being clear that I'm not proposing a .NET dependency--I'm simply using the Log4Net Pattern Layout architecture as an example of the ...

Profit is not a dirty word.

Zenju has already confessed to a passion for perfecting his craft; it shows clearly in FFS. But because it's freely available, he's not able to put as much time into it as he'd like.

FFS already meets or exceeds the level of quality found in many retail packages in its ...

Parsing the logs is made more difficult by the extra lines that occasionally appear for an individual entry in a file.

One line per entry will significantly ease the task.

Given that this would likely be a breaking change for existing code, perhaps it could be made a configurable option with the ...

Currently when FFS deletes a folder, a log entry is created for that folder only--not the files that were in it.

This high-level overview makes it difficult to track the history of a given file when parsing the logs and storing the entries in a database for detailed analysis.

Granted, one could do ...

Log filename masking benefits all of us. It relieves Zenju of the burden of trying to appeal to everyone (he who builds by every man's advice is going to end up with a crooked house).

Folks doing things like parsing the logs and saving the info to a database are confident that their implementation ...

I have the same issues here.

FFS runs on two computers, one with WinXP Pro SP3, and the other one with Windows 7 Pro SP1, both running the current FFS version, v6.14! Both sync their files and save the logfiles to the same local drive, connected to my WinXP-PC through USB, while it is shared in my ...

Thank you Zenju, IMO the only alternative to FFS is Syncovery but after I setup all the logs notification system etc. I'd really really like to stick to this one.

Now, OT, the only thing missing is limiting the number of the days of the revision copies but that's another discussion :)
> IMO the ...

Alright, since there are obviously a number of users doing path evaluations with programs that are not Unicode-aware, most notably cmd.exe, and the new log file name is just cosmetics, I'll revert to the old naming convention in the next release.
> I'll revert to the old naming convention in the ...

I've been using FFS for nearly five years now and I love it.

After closer examination, however, I find I must correct my original claim. The new character in the log files name is actually NOT a colon. It's U+02F8 on Windows' Character Map application.

Nevertheless, still it's causing trouble. It ...

The recent attention to the time portion of the log file name is appreciated, but the implementation has a problem. On the Windows platform, the colon (:) is an illegal character.

Request: Could you use a period (.) instead.

Thanks,
Jeff Bowman
Fairbanks, Alaska