Thank you for the prompt replay. I'm familiar with that feature and I've been using it. I was asking for a way to cycle through the available pools without the need to change the contents of the .txt files.

@Claymore: Feature request  
Can you please consider the possibility of introducing some kind of pool management mechanism? Allowing us to move to one of the failover pools without having to restart the miner or change the config file?
Right now, dcr.suprnova is not displaying my hashrate so I would like to temporarily move to my failover DCR pool. But I can only do that by restarting the miner and changing the config files.
Not a practical solution, right?
Can you please give it some thought?
Thanks!

@Claymore Can you implement it to where we can change pools without restarting the miner? I can do this in other miners by using a .conf, but haven't seen how to do it with your miners.....unless I have just missed how to do it.

sometimes the miner hangs but not totally
if you press S key it shows stat and then says that it is really hanging and then restarts itself

why this happens and why the miner does not detect such kind of hanging(tough it's still running because it can process user input) and does not restart without user actions

@claymore
Wrong calculations with 1 GPU? Total and GPU0 should be same with 1 GPU only right?

Any chance to make it working? Is it problem with RX460 id's or what? Can I help?

Claymore, ASM is not suitable for RX460? It is not working, still only etha 0.

I apologize if this has been asked before (probably has).  On dual mining Claymore software like ETH/SIA (for example), if one of my miners has 6 cards, with 2 dual mining and 4 single mining, how will I be charged? Will I be charged 2% on all six?  Or will I be charged 2% on two and 1% on four?  Thanks for your reply and patience with any redundant questions.

Hello all, and thanks Claymore for new miner version!

Though, I have a problem and hopefully one can help me about that.
I got several rigs of 3x470, 4x470 (4 GB) and 4x470 (8 GB) videocards.
After updating the Claymore ETH from 7.4 version to 9.0 I got a strange problem.
Decred increased *2, that's a fact, but hashrate of both ETH and DCR became floating. Usually my cards give 21 or 24 Mh/s (nothing is overclocked/modded, all stock) depending on whether its Asus strix 4gb or Sapphire nitro 8gb, but now once in several seconds one or two cards in the rig drops hashrate to 17-18 mh/s on eth and to 400 mhs (instead of usual 600 mhs) on dcr.

Any update on other coins getting new Algo?  

Hi Claymore, RX580 8G is not working good in stock just giving 22-23 Mh. Is it because your miner does not support this card yet?

Thanks however can you also add this feature for people who mine with both ZEC and ETH with your miners.
If a rig has 6 GPUs say ( 280X,280X,280X, 480, 480, 480)
The 280X usually mine ZEC and the 480 usually mine ETH
However if someone runs ZEC with the first 3 GPUs (GPU0, GPU1, GPU2) and runs ETH with the rest ( GPU3, GPU4, GPU5)
Then the second program ETH-Miner will incorrectly label the GPUs. Instead of GPU3,GPU4, GPU5, they will start at GPU0,GPU1,GPU2 and it will read the temperatures from the first 3 cards and not the latter 3 and if GPU0 from ZEC overheats, then GPU0 and GPU3 will also throttle (using TTLI)
THis is hard to explain, let me know if you need photos.

i tried that

with -dcri 30 i get 142 on eth and 4200 on dcr
with -dcri 35 i get 132 on eth and 4600 on dcr

it's stable but eth hashrate is much lower

Yes it is stable with dcri 50, however it decreases eth hashrate in greater amount.
Instead, if possible could you please double check miner code and see if miner works stable, without sacrificing ETH hashrate? For me "-dcri 30" is the most for ETH >> 29.3 ETH, 875 DCR but when using this value, gpus randomly have memory controller load deviations in GPU-Z, and this is seen through miner console. As a result lower effective hashrate is calculated on pool.

Claymore, run some test on rx480 to fix the fluctuation problem on rx480 cards.