---
Alright, humor me this.
My _real read:"C:\DEV\BACKUP\FreeFileSync_XP\FreeFileSync.exe" "C:\DEV\BACKUP\FFS_PROFILES\JCS.2.NAS_DB_BU.ffs_batch"
And I think, FreeFileSync.exe ?
And so I run that directly from a C: prompt.
And I see (2) FreeFileSync*.exe fire up (as processes), then disappear.
And I think, FreeFileSync.exe ?
So then I try:"C:\DEV\BACKUP\FreeFileSync_XP\realtimeSync.exe" "C:\DEV\BACKUP\FFS_PROFILES\JCS.2.NAS_DB_BU.ffs_batch"
And I see (2) RealTimeSync*.exe process fire up.
And then I see the lock files being created in one of the sync'd directories.
And I see a .log file being created.
And I'm syncing :-).
So... what am I missing?
Why had this worked ever since I had a pretty good feel for what was going on.
Only to stop, about a week ago, & with the same, existing _real files (that read FreeFileSync.exe - it didn't work?
Should _real be calling FreeFileSync.exe or RealTimeSync.exe ?
---
When I double-click on JCS.2.NAS_DB_BU.ffs_real, RealTimeSync*.exe (processes) run.
Yet I don't sync?
---
I have another _real that reads:
C:\DEV\BACKUP\FreeFileSync_XP\FreeFileSync.exe" "C:\DEV\BACKUP\FFS_PROFILES\LIB.2.NAS.ffs_batch
And that one does sync. (Happened to be nothing to sync, so it just created a .log)
---
Yet I don't sync?
Actually, it did, just now, quite a bit of time - after the fact.
So maybe it was "busy" & hadn't met the threshold?
That, I can kind of understand.
But what happened between last week, through yesterday, & initially this morning?
---
.ffs_real looks to be associated properly.
---> "C:\DEV\BACKUP\FreeFileSync_XP\RealTimeSync.exe" "%1"
]]>