Re: lolMiner Equihash Miner, Update: Jan 18th: lolMiner 0.7 alpha2 (Beam!)
Hi Folks,
sorry for the silence - I do not write so much when busy with coding.
So, what I got for you is lolMiner 0.7 alpha 2 for mining BEAM.
Changes over alpha 1:
- Memory consumption reduced from 3.9 to 3.4G (so now more stable on 4G cards even with screen attached)
- Performance increased about 15%
- Experimentally the API now shows submitted and rejected shares per card
Download link:
https://github.com/Lolliedieb/lolMiner-preview/releases/tag/0.7_a2
MD5 Hashes of release files:
Windows: 12efcea8836eb7ec482a056c4b653fac
Linux: c2529dd0e2dc2816a5cd51506938b075
Notes:
- HiveOS, Pimp OS and others are informed
- No idea yet about Nvidia performance - any comment welcome
Regarding all here where the OpenSource miner was stable but this one not: Check out new version - the reduced memory usage should help in those cases where one card was slow (4G cards).
sorry for the silence - I do not write so much when busy with coding.
So, what I got for you is lolMiner 0.7 alpha 2 for mining BEAM.
Changes over alpha 1:
- Memory consumption reduced from 3.9 to 3.4G (so now more stable on 4G cards even with screen attached)
- Performance increased about 15%
- Experimentally the API now shows submitted and rejected shares per card
Download link:
https://github.com/Lolliedieb/lolMiner-preview/releases/tag/0.7_a2
MD5 Hashes of release files:
Windows: 12efcea8836eb7ec482a056c4b653fac
Linux: c2529dd0e2dc2816a5cd51506938b075
Notes:
- HiveOS, Pimp OS and others are informed
- No idea yet about Nvidia performance - any comment welcome
Regarding all here where the OpenSource miner was stable but this one not: Check out new version - the reduced memory usage should help in those cases where one card was slow (4G cards).
Last version have a problem. when miner lost connection with pool he closes with message from windows"your app have a problem and will be close"! Many different rigs on win 10 and all closes when pool lost connection. On Win 7 it fine and miner reconnection sucsesfully after 3 second. Any idea what wrong?