Topic: [ANN] NicerMiner 0.5.8 - MPH mining app based on NHML v1.9.0.5 - page 6. (Read 2434 times)
cheers, I had scratch around at the file structure myself but couldn't find anything, over my head.
It's not a bug, it's a feature 
I'll take another look when I get a chance.
I will need to run both instances and debug the source code to see if there's another switch somewhere to override that switch
I'll take another look when I get a chance.
I will need to run both instances and debug the source code to see if there's another switch somewhere to override that switch
I just downloaded the source code for NH 1.8.1.9 and I can see the code your talking about, makes sense.
What I don't understand is why the window doesn't stay open when I run xmr-stak-cpu in NiceHash 1.8.1.9
What I don't understand is why the window doesn't stay open when I run xmr-stak-cpu in NiceHash 1.8.1.9
I went to look at the source code and found this:
public XmrStackCPUMiner()
: base("XmrStackCPUMiner") {
this.ConectionType = NhmConectionType.NONE;
IsNeverHideMiningWindow = true;
}
The bold line basically override the app's settings, and will prevent the window hiding logic.
I suppose this is intentional, and was coded to work around some issue - maybe it affected performance, or blocked the API calls...
public XmrStackCPUMiner()
: base("XmrStackCPUMiner") {
this.ConectionType = NhmConectionType.NONE;
IsNeverHideMiningWindow = true;
}
The bold line basically override the app's settings, and will prevent the window hiding logic.
I suppose this is intentional, and was coded to work around some issue - maybe it affected performance, or blocked the API calls...
@mobileanarchy
I've been running the miner for 3 days straight now and from what I can tell it hasn't missed a beat, the stability looks solid
The only thing that I can pick with it is that the CPU miner window (specifically only the xmr-stak-cpu miner window) wont auto-hide like it should.
For every single other miner the cmd window stays hidden but for xmr-stak-cpu it pops up every time, is there any way to fix this?
I've been running the miner for 3 days straight now and from what I can tell it hasn't missed a beat, the stability looks solid
The only thing that I can pick with it is that the CPU miner window (specifically only the xmr-stak-cpu miner window) wont auto-hide like it should.
For every single other miner the cmd window stays hidden but for xmr-stak-cpu it pops up every time, is there any way to fix this?
As far as i could tell the CPU miner was still working yes as i was monitoring it remotely.
Not sure about the other miner as the logs have been overwritten but they were started at different times and different locations so id think its unlikely.
I did think the same thing about Claymore, will do a re-bench on this clean 0.3.1 install and try without 11.5, hopefully its stable.
Thanks for the update ethminer seems to be working now, will let you know how the old claymore goes after more thorough testing.
Not sure about the other miner as the logs have been overwritten but they were started at different times and different locations so id think its unlikely.
I did think the same thing about Claymore, will do a re-bench on this clean 0.3.1 install and try without 11.5, hopefully its stable.
Thanks for the update ethminer seems to be working now, will let you know how the old claymore goes after more thorough testing.
I see where you are coming from, but here is NHML license:
https://raw.githubusercontent.com/nicehash/NiceHashMinerLegacy/master/LICENSE.txt
In any case, changing an open source project is not considered stealing if you meet the project's license terms.
Which only applied to 59 commits on that repo according to first line. So are you using _only_ those or do you just reading selectively?https://raw.githubusercontent.com/nicehash/NiceHashMinerLegacy/master/LICENSE.txt
In any case, changing an open source project is not considered stealing if you meet the project's license terms.
I'm willing to take this whole thing down if DillonN reach out and ask me to.
I'm also trying to be a good citizen and contribute back to the NHML repo as much as I can.
Did the CPU miner actually stayed open?
Did both computers stop at the same time?
There's nothing in the logs that pops up as a potential issue.
Anyway, I created a quick fix for the ethminer issue - version 0.3.1:
https://github.com/odedolive/NicerMiner/raw/master/releases/NicerMiner%200.3.1.zip
I wonder if it's a Claymore comparability issue, you can give ethminer a try now that it's supposed to be working properly.
Did both computers stop at the same time?
There's nothing in the logs that pops up as a potential issue.
Anyway, I created a quick fix for the ethminer issue - version 0.3.1:
https://github.com/odedolive/NicerMiner/raw/master/releases/NicerMiner%200.3.1.zip
I wonder if it's a Claymore comparability issue, you can give ethminer a try now that it's supposed to be working properly.
I see where you are coming from, but here is NHML license:
https://raw.githubusercontent.com/nicehash/NiceHashMinerLegacy/master/LICENSE.txt
In any case, changing an open source project is not considered stealing if you meet the project's license terms.
Which only applied to 59 commits on that repo according to first line. So are you using _only_ those or do you just reading selectively? https://raw.githubusercontent.com/nicehash/NiceHashMinerLegacy/master/LICENSE.txt
In any case, changing an open source project is not considered stealing if you meet the project's license terms.
@mobileanarchy
I left v0.3 going last night but the gpu miner just seems to have stopped at around 19.35. not sure why coz i could see that the cpu miner was still going via MPH monitor until this morning. The log just seems to stop abruptly with a blank spot until I started it again this morning.
=https://pastebin.com/gSkDV9hW
any ideas?
EDIT:
also had it running on another separate rig at a different location and it did the same thing so i don't think its hardware. I don't have the logs for that one as it was restarted last night and they don't go back that far.
I left v0.3 going last night but the gpu miner just seems to have stopped at around 19.35. not sure why coz i could see that the cpu miner was still going via MPH monitor until this morning. The log just seems to stop abruptly with a blank spot until I started it again this morning.
=https://pastebin.com/gSkDV9hW
any ideas?
EDIT:
also had it running on another separate rig at a different location and it did the same thing so i don't think its hardware. I don't have the logs for that one as it was restarted last night and they don't go back that far.
New project looks interesting... When are you expecting a release?
I'm not sure to be honest, it depends on how much "gold-plating" I want to put into the dashboard page.
But like I said, the "core" is ready and running on all my rigs (all 3 of them
) and I'm pretty happy with the returns it's bringing me.I never thought about mining Phi, Tribus, Xeven, X16r before building this tool for myself... so it was a nice learning experience if anything else.
A few of reasons, MPH has much lower fees than NH for one. It also has auto exchange and auto withdraw features so you can get your chosen coin to your chosen wallet automatically without the expense or delays of moving BTC. There's also a great MPH monitor for android which I've found to be more reliable than the NH ones I've tried.
Why would you mine on MiningPoolHub instead of NiceHash?
NiceHash has higher profits for the most profitable algorithms and uses pay per share, which is much better for algo and coin switching. MiningPoolHub is garbage.
NiceHash has higher profits for the most profitable algorithms and uses pay per share, which is much better for algo and coin switching. MiningPoolHub is garbage.
No problems, at least its an easy fix. 
New project looks interesting... When are you expecting a release?
New project looks interesting... When are you expecting a release?
I see what the problem is now:
Starting miner [pid(18020)|bin(bin\ethminer\ethminer.exe)] --cuda -S b.miningpoolhub.com:17020
NiceHash had some code to strip the first 14 chars from the pool's URL (basically the stratum+tcp:// prefix, because ethminer doesn't need it)
I'll create a fix for it ASAP. probably tomorrow, as it's getting late on my end.
Thanks again for your feedback.
Here's a little tease for what I'm working on now
https://imgur.com/a/wXsdD
It's been in the works for a few months now, and I think there's more to do, although the core functionality is done (profit-switching, process watch-dog etc.)
Now I'm working on basically the fluff - graphs, and dashboard stuff...
Starting miner [pid(18020)|bin(bin\ethminer\ethminer.exe)] --cuda -S b.miningpoolhub.com:17020
NiceHash had some code to strip the first 14 chars from the pool's URL (basically the stratum+tcp:// prefix, because ethminer doesn't need it)
I'll create a fix for it ASAP. probably tomorrow, as it's getting late on my end.
Thanks again for your feedback.
Here's a little tease for what I'm working on now
https://imgur.com/a/wXsdD
It's been in the works for a few months now, and I think there's more to do, although the core functionality is done (profit-switching, process watch-dog etc.)
Now I'm working on basically the fluff - graphs, and dashboard stuff...
Sure can
https://pastebin.com/rQrhWCHC
https://imgur.com/a/2RcCJ
I'm using Nvidia rig as well so that wouldn't be it.
https://pastebin.com/rQrhWCHC
https://imgur.com/a/2RcCJ
I'm using Nvidia rig as well so that wouldn't be it.
I just double checked Dagger using ethminer and DaggerKeccak using Claymore's Dual Miner and they both seem to work on my end...
Can I bother you with log files/messages again please?
(I'm testing on a Nvidia rig BTW if it makes any difference)
Can I bother you with log files/messages again please?
(I'm testing on a Nvidia rig BTW if it makes any difference)
Nice work, just tested and its fixed cryptonight, keccak, lyra2v2 and neoscrypt!
Just daggerhashimoto (ethminer) and daggerkeccak are the only 2 not working now so I've just left them disabled for the time being.
DaggerHashimoto seems to run fine with Claymore 11.5 override in claymore-dual folder also.
EDIT:
Did a re-bench after moving Claymore Dual 11.5 into the claymore_dual folder and now DaggerKeccak works too!
So now its just daggerhash (ethminer) which doesn't work. I tried re-benching that also but no luck.
Just daggerhashimoto (ethminer) and daggerkeccak are the only 2 not working now so I've just left them disabled for the time being.
DaggerHashimoto seems to run fine with Claymore 11.5 override in claymore-dual folder also.
EDIT:
Did a re-bench after moving Claymore Dual 11.5 into the claymore_dual folder and now DaggerKeccak works too!
So now its just daggerhash (ethminer) which doesn't work. I tried re-benching that also but no luck.
Release 0.3 - 2018-03-21
Fixing an issue with misconfigured ccminer arguments (affecting Neoscript and other algorithms)
Fixing an issue with truncating the server url on Ethminer
This release is still based on NHML v1.8.1.9 due to mixed reviews for the new profitability switching refactoring that took place on NHML v1.8.1.10, I will evaluate the next version to decide if it will be kept in sync with NHML down the road.
https://github.com/odedolive/NicerMiner/blob/master/releases/NicerMiner%200.3.zip?raw=true
Fixing an issue with misconfigured ccminer arguments (affecting Neoscript and other algorithms)
Fixing an issue with truncating the server url on Ethminer
This release is still based on NHML v1.8.1.9 due to mixed reviews for the new profitability switching refactoring that took place on NHML v1.8.1.10, I will evaluate the next version to decide if it will be kept in sync with NHML down the road.
https://github.com/odedolive/NicerMiner/blob/master/releases/NicerMiner%200.3.zip?raw=true
I'm looking into it.
I see a problem in the ccminer arguments builder... so I fixed that and that should resolve all ccminer-related algos.
I'll take a look at the Claymore dual miner now (to make sure it works with version 11.5) and will post an update as soon as possible (probably in a couple of hours)
Thanks for the heads up.
I see a problem in the ccminer arguments builder... so I fixed that and that should resolve all ccminer-related algos.
I'll take a look at the Claymore dual miner now (to make sure it works with version 11.5) and will post an update as soon as possible (probably in a couple of hours)
Thanks for the heads up.
Jump to: