Megaminer 6.3 - Multi pool / Multi Algo launcher

[tutulfo]

6.3 Release

---FEATURES CHANGES:
* Added Automatic EThLargementPill for Nvidia hashrate booster for 1080/1080ti
* New message at start if new Megaminer release available
* Updated nvdia-smi (needed for nvidia cards identification) to 397.64 release
* Added hamsi,bmw,whirpool and echo Algos for AMD
* Added allium algo for NVIDIA
* Added x16r for CPU



---MINERS CHANGES:

* Updated AMD SgminerAver to 1.4 Release
* Updated CPU cpuminer Jayddee to 3.8.8.1
* Updated CPU xmrig to 2.6.2
* Added NVDIA SuprminerSP 4a
* Added NVDIA Ccminer for Allium


---BUG FIXES:
* X16r,Blake2s and Neoscrypt not working for Unimining.net
* Nicehash not using europe location



--RELEASE NOTES
If you want to reuse your old config.txt file, and you want to use new EthLargementPill feature you must add this section @@ETHLARGEMENTPILL=ENABLED
If you use new ETHlargementpill feature you must delete ETHASH

[bitcoinminer0319]

there is no enemy miner available to ddl cause there is no url.  how do i add it to the mine x16r?

[CjMapope]

Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program

[alucard20724]

Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program

to add to that, it's also using RVN on blazepool to try and bench x16s for SuprminerSP/a

in addition, 6.3 is not accepting additional algo's that i add, such as sha256t (supported by both Jayddee(cpu) and Tpruvot(gpu)).  it worked fine in mm 6.2.1 and earlier.

[tutulfo]

there is no enemy miner available to ddl cause there is no url.  how do i add it to the mine x16r?

Enemy miner is included as ccminerX16r

[tutulfo]

Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program

to add to that, it's also using RVN on blazepool to try and bench x16s for SuprminerSP/a

in addition, 6.3 is not accepting additional algo's that i add, such as sha256t (supported by both Jayddee(cpu) and Tpruvot(gpu)).  it worked fine in mm 6.2.1 and earlier.

Check last master code, first bug fixed and sha256t included

[Pandoraaaaa]

Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks. 

[tutulfo]

Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks. 

Something is going wrong, check log files from logs folder

[Pandoraaaaa]

Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks. 

Something is going wrong, check log files from logs folder

Hi,

I am making some progress, isolating and capturing errors. I will create thread on github/issues to continue convo. Thanks for your reply, see you over there.

[stunvn]

What should I do now?

[Pandoraaaaa]

Oh I've had that same error. The only way I made it go away was by removing offending alogorithm in config.txt. It's been a lot of trial and error. For instance, the amd algo list includes hooks into a miner that only works for vega hardware.

Anyway, for me it has been a grueling process of pools and algos. I think it is worth the effort because this software profit switching looks en pointe. I'm still collecting data for my rigs, both amd and nvidia, but it looks good so far. I'm still trying to figure it out.

[alucard20724]

What should I do now?

wait until benchmarking completes... and then wait more.   there's really nothing more for you to do except look at the screen.

[tutulfo]

What should I do now?

This is visual only error, all works fine.

If you want to avoid this remove miningpoolhub.ps1 line

Remove-variable request

[alucard20724]

megaminer is not showing hashrate of mkxminer.  hashrate is being shown at pool, just not in megaminer.

[celofan]

A few wishes for the next releases of the megaminer.
Some miners not work with some pools.For example: zfast miner is a best miner for zcoin minig but it is a fork optimized for miningpoolhub only. And in the same time new releases of excavator not works with miningpoolhub due to change stratum protocol supported.Can you sort the miners on the list of the best miners specifically for a particular pool? For example: zfast miner works with miningpoolhub but not works with ahashpool and nicehash, so for miningpoolhub zcoin mining will use zfast miner and for ahashpool and nicehash will use tpruvot etc? For lyra2v2 best results for miningpoolhub have by tpruvot miner with -submit stale option, but the best results for ahashpool and nicehash will be with excavator miner.Sorting miners for specific pools will increase profitability!

[densm]

1) "If you use new ETHlargementpill feature you must delete ETHASH"
Does this mean I should delete all Ethash-related files from Stats folder if I have any?

2) Stats-files (not benchmarks) are used to calculate profits more accurately and as Megaminer runs it gathers more stats and its accuracy increases. Did I get it right?

[densm]

2. Ethlargement pill works not only for ethereum, for cryptonight algo's too.So can you add autostart ethlargement pill when cryptonight algo starts (for Nvidia Cards)?

Doesn't it just start if you have @@ETHLARGEMENTPILL=REVB(REVA) in config.txt?

[celofan]

2. Ethlargement pill works not only for ethereum, for cryptonight algo's too.So can you add autostart ethlargement pill when cryptonight algo starts (for Nvidia Cards)?

Doesn't it just start if you have @@ETHLARGEMENTPILL=REVB(REVA) in config.txt?

There was my fault in parameter line.
All is O.K. now

[twente-mining]

Zpool changed something for NIST5 algo, i tried to delete the stats for the cards, and benchmarked again, but that does not work.

https://twitter.com/_zpool_

It shows wrong values because of the change to mBTC.
So now rigs are mining NIST5 non stop on zpool, that isnt's ok.

Any tips how to change the settings ?

[Surgut2006]

Zpool changed something for NIST5 algo, i tried to delete the stats for the cards, and benchmarked again, but that does not work.

https://twitter.com/_zpool_

It shows wrong values because of the change to mBTC.
So now rigs are mining NIST5 non stop on zpool, that isnt's ok.

Any tips how to change the settings ?

just disable the algorithm