Hey Tutulino,
latest beta release as of right now is defaulting to ahash pool no matter what pool is selected.
tried on 99 all pools but again it just shows profits screen for ahash and the miner is connecting to ahash too.
it was working fine up to the last commit yesterday.
so one of the commits today has chopped the other pools checking out.
Ill keep you posted if i find out where.
thanks again for the support.
this megaminer sure is getting better by the days.
Nevermind think you just fixed it with that commit you posted as i typed.
yep that sorted it.
Another small issue is :
on the dual mining getting :
NVIDIA Cards available: 1
CUDA Driver Version/Runtime Version: 9.1/8.0
GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
Total cards: 1
DUAL MINING MODE ENABLED: ETHEREUM+LBRY
ETH: Stratum - connecting to 'europe.ethash-hub.miningpoolhub.com' <139.162.131.165> port 20535
ETH: eth-proxy stratum mode
LBC: Stratum - connecting to 'lbry.suprnova.cc' <193.70.45.182> port 6256
"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
Watchdog enabled
LBC: Stratum - Connected (lbry.suprnova.cc:6256)
Remote management is enabled on port 2850
ETH: Stratum - Connected (europe.ethash-hub.miningpoolhub.com:20535)
LBC: Authorized
Received unknown response: {"id":null,"method":"mining.notify","params":["4256","0x0104c5a89bebf0d9f172e73d272363d7677670ccfe95a1c101b43d69180d8ad3","0xc5f7a893e7fb670ce12bfe6ae0892bea15e5a43f1f03f29a788c31b49f76bd53","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7",true]}
Received unknown response: {"id":null,"method":"mining.notify","params":["4257","0x5d337919844d046c5126aa9f5b7de06bc00dac7e7f7d84bc8208c87149954683","0xc5f7a893e7fb670ce12bfe6ae0892bea15e5a43f1f03f29a788c31b49f76bd53","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7",true]}
GPU0 t=41C fan=33%
LBC: 12/12/17-18:31:42 - New job from lbry.suprnova.cc:6256
and repeats through this error.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
temporary solution for others getting this problem just cut the virtual pool out of its folder and paste it in a different folder for now.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Nanopool on initial load up of all pools i get this error too doesnt effect anything mining wise. think its just looking for other coins that it doesnt support.
Add-Member : Cannot add a member with the name "Name" because a member with that name already exists. To overwrite the
member anyway, add the Force parameter to your command.
At C:\Users\Fred\Desktop\miners\megaminer master 12.12.17 18.11\Megaminer-master\Include.ps1:483 char:95
+ ... ent -ne $null) {$_.Content | Add-Member @{Name = $_.Name} -PassThru}}
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (@{Algorithm=CRY... Name=NANOPOOL}:PSObject) [Add-Member], InvalidOper
ationException
+ FullyQualifiedErrorId : MemberAlreadyExists,Microsoft.PowerShell.Commands.AddMemberCommand