FreeFileSync Forum

couldn't even find ~/.config/FreeFileSync Were you looking for ~ literally, or, /home/jeannie/ ? I'm running the official version and the globalsettings.xml has gone missing again! Did ~/.config/FreeFileSync/ also go missing? I managed to get globalsettings.xml back by uninstalling FFS, then ...

Is this NSSM - the Non-Sucking Service Manager?

Why are you attempting to run RTS as a service?
What are looking to benefit from by doing so?

Is RTS even meant to be run in such a manner?
(I'd think not.)

FreeFileSync.exe is simply a "stub" whose only purpose is to call either FreeFileSync_x64.exe or FreeFileSync_Win32.exe (depending on circumstances).

So that you are seeing 2 "FreeFileSync .exe" is normal & expected.

(Odd how this "text" copies from my pdf viewer, an old Foxit. And it does seem there are actual "spacings", be they $20$ or otherwise in there?) 5. Use a di fferent GlobalSet t ings.xml fi le B y default, F r eeF ileSync uses a single G lobal S ettings. xml file containing options that apply to all ...

I believe the idea was, you run the "chunk" first, & if does not compare, you're done (as in the files are not identical, so no need to compare any further).

If it does compare, then you run a full comparison on the file pairs.

temporarily Missed that the first time. Well, aside from that, if you remove the path to the sounds (in Tools | Options), or if you instead enter a path to a "sound" that does not make a sound ;-). On the temporary part, you could automate something (batch file) that leaves the paths to the sounds ...

Just to note, this is Everything.

Just noting... Force terminating Firefox (taskkill /f) potentially could lead to corruption. Better, IMO, to heed the "or [Q] to quit" (& manually close FF). (Likewise, taskkill will close all instances of FF [if you happen to run multiple instances simultaneously - perhaps not too common, but I am ...

The date column was blank in both FreeFileSync and Windows. On my end (Win7), FFS does see the "correct date" [of the file, "D"] (it is dated 12/31/1969), but Windows Explorer shows it as "blank". https://i.postimg.cc/RFzS6Bf8/Invalid-Dated-File-lt-1970-non-date.png (Looks like 2038 is OK ;-).)

(The pic, https://i.imgur.com/WE8By0f.jpeg.)

If you are in a New (already in a New) & have not yet changed anything; like by setting paths or changing the Comparison mode, the New button will remain grayed until you do.

In his example, he is not checking for success, (0), rather for "something went wrong", so NOT 0 is correct in that regard. If, "you want to know errorlevel 0", i.e., success (in your second paragraph), that is different from what his example describes, & so the check for that would need to be ...

What are the source file dates?

1-1-1970 is a "special" date (epoch date on Unix systems).

So maybe if source file dates are before that?
Or, some sort of bug somewhere along the line, that is causing an invalid date, so being set to '0', hence 1-1-1970?

See, viewtopic.php?p=44454#p44454.

What version of FFS? Are you running the GUI or a .ffs_batch or ... ? On the completion dialog, there is an "autoclose" checkbox. If you ticked that, it sets in: GlobalSettings.xml <ProgressDialog AutoClose="true"/> Don't know if there is a GUI to change that, but with FFS closed, if you change that ...

I'll only add that it is odd, that looking at the UI, you would expect to be able to set any or all of the 3 conditions (& that they be retained, of course). <PostSyncCommand Condition="Success">c:\success.bat </PostSyncCommand> <PostSyncCommand Condition="Error">c:\error.bat </PostSyncCommand ...

Are you running freefilesync.exe ?
Or a .ffs_gui or a .ffs_batch?

If freefilesync.exe, does your shortcut have any command-line arguments along with it?

Try: *\.* . matches a literal dot * matches zero or more characters So things like .out .metadata-v2 .startup-incomplete .padding .usage should all be excluded. (And I take it that you're wanting to exclude "filenames" that start with a (.), rather then files that have the hidden attribute set.)

A hacky way to go about it, perhaps... Start a New Enter something simple for the source & target, like 'C' Save that as ALWAYSNEW.ffs_gui Quit FFS Edit ALWAYSNEW.ffs_gui, changing the Folder Pairs: <FolderPairs> <Pair> <Left></Left> <Right></Right> </Pair> Set the attributes for ALWAYSNEW.ffs_gui ...

\\mylaptopname\c$\users\myname\Documents Is your Target location? Are you able to access that from the source computer using (oh, Linux) - using not sure, but some equivalent to Windows Explorer (& outside of any "docker container")? I'd think that C$ to be an atypical way to access a share. If you ...

What OS are we running? With an initially empty Target, when you initiate the Compare, do you get a message, "The following folders do not exist: K:\Bilder (for instance) The folders are created automatically when needed." (I suppose that might not be shown if sometime in the past you ticked the ...

adding some trash characters to the end

Example?

What I saw, was to add square brackets around the address.
So if IPv6 is:
fe80::219:99ff:fe20:c251
use:
[fe80::219:99ff:fe20:c251]

(I have no way of testing.)

Not quite understanding what you're after (maybe a sample screenshot)?

But I think you're going to want to set up folder pairs, then only sync particular pairs instead of all of them?


(image isn't exactly representative, but...)

Oops, what I said was pertaining to IPv4. Not familiar & don't know if that holds with IPv6? the last four hex digits Hex? In any case, aren't they going to be the "Port" number, & those 4 digits should be place in the Port: box, & not included directly into the Server/IP: box. https://freefilesync ...

Screenshot of your comparison results?

What you describe, & your sync settings do look to be correct (to coincide with one another).

Simply upload the image, somewhere, & post a link to it (& or hotlink it in the forum).

(From Mozillaine) Posting a screenshot on the forum

https://i.postimg.cc/CKHYFWFY/XXX-EXIF-sample.jpg

What OS & version?

Maybe UAC is turned off & that is somehow affecting things?

What OS (& version at that) are we talking about?

Wonder if something changed in the installer process between 13.6 & 13.7 ?

Or maybe some sort of permissions issue where the old 13.6 install.dat couldn't be replaced by the newer 13.7 install.dat ?

even in open hard drive dock With recent heat here, I found that the open HDD dock actually ran hotter then putting the same drive in a caddy, into a drive bay in the computer itself. As it was, I got a new HDD that I threw into a dock, & as I'm copying files to it, it disappeared. And I'm thinking ...