Dear developer.
It will be great if can be added "Run a command before".
Useful for command line, like to map drive, vpn connection (rasdial.exe) etc.
Kind regards
Run a command before
- Posts: 9
- Joined: 4 Dec 2019
-
- Posts: 2451
- Joined: 22 Aug 2012
It is not my call, but this is likely not easy.
A "Run a command before" would need to be finished before FFS can "run".
This means that whatever command is "to be run before" needs to have proper handshakes/exit codes. But as this command may be any unknown command ....
Obviously that is no a problem with a "Run a command on completion".
Then FFS can launch the command and instantly exit.
I also doubt the need to have a "Run a command before".
If you have that need, you can invoke a script, e.g a *.cmd-file, instead of directly invoking FFS.
That script can then then perform all required "Run a command before" commands, wait until those have completed, and only then, from the script file, invoke FFS to open the desired *.ffs_batch file.
Waiting for completion of the previous tasks can then simply be tailored to the command(s) "to be run before" in your script file.
A "Run a command before" would need to be finished before FFS can "run".
This means that whatever command is "to be run before" needs to have proper handshakes/exit codes. But as this command may be any unknown command ....
Obviously that is no a problem with a "Run a command on completion".
Then FFS can launch the command and instantly exit.
I also doubt the need to have a "Run a command before".
If you have that need, you can invoke a script, e.g a *.cmd-file, instead of directly invoking FFS.
That script can then then perform all required "Run a command before" commands, wait until those have completed, and only then, from the script file, invoke FFS to open the desired *.ffs_batch file.
Waiting for completion of the previous tasks can then simply be tailored to the command(s) "to be run before" in your script file.
- Posts: 62
- Joined: 22 Apr 2018
I use syncback free for this feature and put ffs_batch at the end of first .cmd or .bat
I think there should be some ERROR / STOP messages in batches
like thresholds for # or files deleted exceed etc..
SOMETHING has WIPED out a ton of my files and I'm not sure as to what
I think there should be some ERROR / STOP messages in batches
like thresholds for # or files deleted exceed etc..
SOMETHING has WIPED out a ton of my files and I'm not sure as to what
