I noticed I was not able to use the start /wait command on ffs_batch files
anymore. It would start them asynchronously.
That is due to FreeFileSync.exe redirecting to either bin\FreeFileSync_x64 or
bin\FreeFileSync_Win32.exe, which starts the job and terminates the original
FreeFileSync.exe.
Just in case it would save someone some time, the solutions are simple:
1) Modify the associated program with ffs_batch directly to the proper binary
(x64 or x32)
2) Specify the binary in your batch: Start /wait "c:\Program
Files\FreeFileSync\bin\FreeFileSync_x64.exe" %1
batch with start /wait
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
Ha, I knew it would break somewhere :) All my tests went through right from
the start. It couldn't be true.
the start. It couldn't be true.
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
Fixed for v3.18: Launcher will be running synchronously and will return target
executable's error code.
executable's error code.
Wow, that was fast. Thanks for your great work.