TRIGGERcmd not starting at boot
-
@TheConfax, I tried rebooting the VM many times and I have not seen the problem.
I did an experiment though - I disconnected the VM from the Internet, then quit and re-launched the TRIGGERcmd agent, and I found that it automatically quit because it couldn't connect to the server.
I wonder if that's what's happening to you. Is it possible your TRIGGERcmd agent is launching before your computer is connected to the Internet during boot?
-
@Russ Yes, it is very much possible, because my Wi-Fi card connects only after user login.
In my .bat fix i included a 30 second delay, that could explain why even that sometimes is not working.
You could try implementing a little loop at boot checking for network more than one time and it should be fixed ^^ -
@TheConfax, ok, yea I think I can fix this.
-
Thank you @Russ !
Let me know when it's done and thanks again for the very useful application! -
@TheConfax, I fixed it. Please update your agent. Now it will retry every 10 seconds if there's no Internet. I tested by rebooting the VM while it was disconnected from the network, then I enabled the network a while after the agent started. It connected within 10 seconds.
-
@Russ Thanks for the fix! I will test it during the next days and I'll let you know if it hangs again, hopefully should be ok.
-
I'm from Brazil and I have the same problem, the fix doesn't work here. If anyone knows the fix about the .exe (.bat file in the background doesnt appearing the black box of CMD) help me please.
-
@Paulo-Filho Try uninstalling and removing the .bat fix, then reinstall the latest version and make sure it is in the automatic run folder.
It is your PC connected to the internet at launch?@Russ For me it never broke up to now
-
@TheConfax Yes, its connected at launch. The .bat fix finally worked here, now how i can transform in a .exe to not show the cmd in the intro?
-
@Paulo-Filho You can use any exe-bat converter. But Russ updated the software, now it should work even without the bat fix
