Hello,
I have a batch file that kicks off quite a few .ffs_gui configs. However, usually they do not start scanning automatically and I have to click scan on each one. I looked for command line switches to force it but there doesn't seem to be any.
I want to GUI to run for each one, I just want to kick them all off via a batch file.
If I just double click on the .ffs_gui file it launches but does not initiate a scan.
Any thoughts on how to better troubleshoot this? I did some searching, but didn't find anything in the discussion archives.
Thank you.
Frosty
Auto Scanning on Startup
- Posts: 3
- Joined: 16 Jun 2000
-
- Posts: 2520
- Joined: 22 Aug 2012
That's what the *.ffs_batch files are for ...
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Double-clicking a .ffs_gui file starts FreeFileSync and automatically invokes the comparison, unless:
1. At least one of the directories to sync is not available.
2. It cannot be determined in the time span of 500 ms that all directories are available (e.g. slow network access). In this case FreeFileSync assumes a directory is not existing rather than block the FreeFileSync start up any longer.
In these cases FreeFileSync assumes the user first wants to correct this error, e.g. plug in an external hard drive or log in to a network share. Otherwise the first thing the user would see is an error message "cannot find folder" and that could be annoying.
That said, you're saying this design does not suit your needs?
1. At least one of the directories to sync is not available.
2. It cannot be determined in the time span of 500 ms that all directories are available (e.g. slow network access). In this case FreeFileSync assumes a directory is not existing rather than block the FreeFileSync start up any longer.
In these cases FreeFileSync assumes the user first wants to correct this error, e.g. plug in an external hard drive or log in to a network share. Otherwise the first thing the user would see is an error message "cannot find folder" and that could be annoying.
That said, you're saying this design does not suit your needs?
- Posts: 3
- Joined: 16 Jun 2000
Zenju, thank you for the response. I guess I'd love the ability to force a scan at startup. A command line switch to bypass the (usually very appropriate) logic and just start a scan.
It's just a suggestion. FFS is pretty much perfect, but that is one feature that I would like, although I might be the only one.
Is this a fairly easy things to add in some future release?
Plerry, as for the .ffs_batch I have not looked at that to solve this problem as I didn't think it started a GUI per my needs. However, it may be something look at in more detail.
Thank you for the great utility.
Michael
It's just a suggestion. FFS is pretty much perfect, but that is one feature that I would like, although I might be the only one.
Is this a fairly easy things to add in some future release?
Plerry, as for the .ffs_batch I have not looked at that to solve this problem as I didn't think it started a GUI per my needs. However, it may be something look at in more detail.
Thank you for the great utility.
Michael
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
You expect the comparison to start directly and the FreeFileSync .ffs_gui file is designed to do so. Since it's not working in your scenario, this indicates you have at least one "slow" device which exists but accessing the folder takes longer than 500ms. Is this the case?Zenju, thank you for the response. I guess I'd love the ability to force a scan at startup. A command line switch to bypass the (usually very appropriate) logic and just start a scan.
It's just a suggestion. FFS is pretty much perfect, but that is one feature that I would like, although I might be the only one.
Is this a fairly easy things to add in some future release?
Plerry, as for the .ffs_batch I have not looked at that to solve this problem as I didn't think it started a GUI per my needs. However, it may be something look at in more detail.
Thank you for the great utility.
Michaelfrosty
The current design distinguishes three cases:
1. all folders are existing => open main dialog, start comparison
2. at least one folder not existing => open main dialog only
3. could not check status for all folders after 500 ms => open main dialog only
In the case of an existing but very slow device 3 should behave like 1.
- Posts: 3
- Joined: 16 Jun 2000
Hello Zenju,
I have to look into it, but I think I know what is happening. My batch file looks for an existing connection to the destination server. If it is found, it starts all the *.ffs_gui files in a specific directory. If not, it asks for a password, establishes the connection, then starts the .ffs_gui files.
What is happening on my Windows 7 computer is that if a connection exists, the batch file immediately launches the files, but the network connection is present but very slow the first time it is used. I'll update the batch file to perform a quick activity and when it returns then start the .ffs_gui files.
I just did a test and doing a dir on the destination machine from the primary machines caused about a 5 second delay the first time I issues the command.
I'll confirm and let you know.
Thank you very much for the help.
Michael
I have to look into it, but I think I know what is happening. My batch file looks for an existing connection to the destination server. If it is found, it starts all the *.ffs_gui files in a specific directory. If not, it asks for a password, establishes the connection, then starts the .ffs_gui files.
What is happening on my Windows 7 computer is that if a connection exists, the batch file immediately launches the files, but the network connection is present but very slow the first time it is used. I'll update the batch file to perform a quick activity and when it returns then start the .ffs_gui files.
I just did a test and doing a dir on the destination machine from the primary machines caused about a 5 second delay the first time I issues the command.
I'll confirm and let you know.
Thank you very much for the help.
Michael
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
I have no strong tendencies about case 3. Considering that running a .ffs_gui file should mirror behavior of a .ffs_batch file it probably makes sense to just start comparison in this case, too, just as if all directories were available.
Even if this could be annoying in the error case where accessing a slow device fails only after some time and FFS starts comparing and then stops with an error message, this is still a more transparent behavior. Users won't be confused as much anymore with regards to why FFS sometimes starts comparison and not in other cases. Here's the updated beta:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_6.14_beta_Windows_Setup.exe]
Even if this could be annoying in the error case where accessing a slow device fails only after some time and FFS starts comparing and then stops with an error message, this is still a more transparent behavior. Users won't be confused as much anymore with regards to why FFS sometimes starts comparison and not in other cases. Here's the updated beta:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_6.14_beta_Windows_Setup.exe]
