Quote from: yurez83 on March 23, 2018, 07:17:50 AM

hi. I have a question for you. Is it possible to make the --optim and --set-work-batch parameter set for each video card separately? This is necessary if there are different video cards.

At the moment this won't work, but for the next version it will likely be. For work batch I can guaranty it, with optim I am not sure because I will do some rework of the OpenCL code and therefore the exact way optim will work is not yet fixed Wink

Quote from: john1010 on March 23, 2018, 08:33:22 AM

Mine is stable with 4gpu's i remove the other gpu in shift to eth algo, I hope the 8gpu limit will resolve soon by the @Dev

As you may have read in the previous page: There is no limit by lolMiner. It can use all cards it gets reported by the OpenCL drivers without any internal restriction, therefore there is nothing I can fix.
When running Windows you must have recent Windows 10 version and recent GPU drivers. Additionally if you have AMD GPUs it seems that the blockchain drivers have problems with more then 8 GPUs. On the regular AMD Crimson drivers you still have to set the GPU profile to "Compute", here is a manual how it is done:

http://www.aurelp.com/2017/11/01/solved-how-to-add-more-than-8-gpus-in-windows-10-step-by-stepfix/

Quote from: WinstonBlue on March 23, 2018, 08:20:52 AM

The newest version 0.32beta has a problem staying connected to pool. After a few hours (totaly random) miner continues hashing (and spending electricity) but worker is not connected to the pool (not mining for me).

Why so bold? No need to highlight your text that way - I am reading every post here! Can you send me the console log of your miner when this happens? Usually when the connection does down I should be able to see something in this logs. Also miner should reconnect or something like this when a share is send but it doesn't get an answer from pool. So either something is broken on pool side or one of my many safety mechanisms is not working properly (e.g. Reconnect to pool when no new job for 10 minutes, reconnect when no response to send share for 10 seconds, miner should stop sending work to GPU when there is no connection on the user connector (when fee one is broken it should get slower but not stop working) ... ) You see there are certain things that should prevent this, but I can not say why this does not work, so your config file and the text log of the miner in such a situation would be great so I can hunt down this bug.