Quote from: natminer on June 19, 2017, 02:35:41 AM

Hi

I bump bensam1231's suggestion about having a way to identify a failed miner (not only if .exe stops running).

I have a different question, about the ability to use the MSI Afterburner remote server. How would you set it up for a scenario where if you mine for ETH it sets certain power/memory/core settings, but if you set your ZEC miner it sets a different set of power/memory/core settings.

Is that possible to do? I have very GPU different settings for ETH and ZEC.

(p.s - I really love the software so far, I purchased the Premium edition today and now I have email notifications and a web server

Hi,
The scenario that bensam1231 describes is when you use the Generic Miner concept in Awesome Miner, where there at no API's to detect any failures. For all other mining software, Awesome Miner uses the concept of Rules (Options dialog, Rules section) where you can define what action to take when you have low hashrate, no accepted shares and so on. In these cases you can define actions like notifications, restart mining process or rebooting the computer. More about rules:
http://www.awesomeminer.com/help/rules.aspx

You question on Afterburner is good, and I do understand the need of this scenario. I already have that one on my list of things to implement, because it makes perfect sense. Today you can still use the command line parameters to the Claymore miners for example, to do GPU clocking operations on start. However, this can get complex with command line parameters when you start using other mining software as well, and they all have different or no support for clocking. This is the reason why it makes sense to define "GPU Clock Profiles" in Awesome Miner in the future.