Quote from: Waytoogo on October 05, 2020, 11:05:07 PM

Quote from: patrike on October 05, 2020, 01:10:13 PM

Quote from: Waytoogo on October 03, 2020, 06:49:03 PM

I am having trouble with batch files after a miner stops on a remote machine. It will run any command I give it when starting the miner, but nothing happens when Awesome Miner changes to another algorithm. I also tried putting a command in the before stopping miner area, and it won't run from there either. I can enter commands from the tools menu at any time and they will execute on the remote machine just fine. I just can't get it to execute a command when changing from one miner to an other. After playing with it some more, I found out that if I stop the miner manually then it will run the batch file. But it won't run it if I manually restart it, or if profit switching changes miners.

I was trying to reproduce this without success. Have you defined the commands to run on the Managed Profit Miner itself (Properties, Command Line section) or via the Profit Profile, where you can configure this per algorithm? If configured on the Profit Profile - is it configured different per algorithm?

The configuration in the Profit Profile will only be used if the Managed Profit Miner doesn't have any commands defined.

I looked at "Options / Managed Miner / edit" and the miner, has no extra commands there. I'm having trouble with the Profit Profile. It's has a check mark "Batch Commands" and a button "Configure". The button brings up a menu with 3 boxes to enter commands. if I use a new profit profile with only 2 algorithms in it. Then on one algorithm, I put commands in the three boxes like this, one in each box. "@echo before start&&pause" "@echo before stopping&&pause" "@echo after stopping&&pause" I don't use any commands on the second algorithm. If I start the miner my first command opens, and then the miner opens. If I manually stop or restart on the miner, the second and third commands work fine. If Profit Switching changes the miner to the other algorithm, something total different happens. The second and third commands don't run when the first algorithm stops, they only run if the miner later switches back to the first algorithm. After the switch back, both the second and third commands run, then the first command, then the miner. I hope I've made my self a little more clear this time. Thank you for your help.

Many thanks for the detailed description. I was able to reproduce the problem and the next release will correct the problem.