Re: lolMiner Equihash&Grin Miner, 0.8.7 (Aug 15th): Added Beam-II for older AMD card
Just pushed lolMiner 0.8.8 
Now the "invalid work group size" problem on Beam should be gone and I added some example bats for those who do not like the config files.
-------------------
Sry, I do not get what exactly the problem is - if you run them all at the same time they conflict and close? I have to admit that I did not try that but it may indeed happen when they try to use overlapping GPUs ... not sure.
You are aware that I am advisor for Beam and heavily involved in that - Grimm is nothing but a 1:1 copy of an older Beam code base... maybe I will push an update that will re-enable BeamHash I with Grimm personalization, but that has not much prio atm - first experimenting with ways to make this Beam Hash II faster on AMDs...
Now the "invalid work group size" problem on Beam should be gone and I added some example bats for those who do not like the config files.
-------------------
I have three miners - lol, Claim and Gminer. Their work on Nice without using the Nicehash shell. And only Lolminer at the same time all three are turned off and closed. I understand that this happens after a disconnect with a pool. How to make sure that this does not happen? Claimor and Gminer have no problems. Claimore on the ETH network and amd 470 video card, but lolminer (HD7950) and Gminer (1070) do the calculations on the Beam network. lolminer 0.8.7
Sry, I do not get what exactly the problem is - if you run them all at the same time they conflict and close? I have to admit that I did not try that but it may indeed happen when they try to use overlapping GPUs ... not sure.
Hi! What about Grimm, man? 
You are aware that I am advisor for Beam and heavily involved in that - Grimm is nothing but a 1:1 copy of an older Beam code base... maybe I will push an update that will re-enable BeamHash I with Grimm personalization, but that has not much prio atm - first experimenting with ways to make this Beam Hash II faster on AMDs...