Quote from: manc on April 10, 2018, 08:35:12 PM

Quote from: MrPlus on April 10, 2018, 05:40:12 PM

Quote from: manc on April 10, 2018, 04:43:15 PM

Quote from: MrPlus on April 10, 2018, 11:13:46 AM

Quote from: jimmykl on April 10, 2018, 10:18:53 AM

Quote from: Enkrypt on April 09, 2018, 09:30:09 PM

Is it normal to loose focus when miners switch? It brings up windows taskbar while in Chrome YouTube Fullscreen.

Yep it's normal. Many people mine on dedicated rigs where it's not an issue. A while ago I remember someone managed to set the miner going on one account and switch to another one to work/watch videos/whatever but not sure if that still works.

The different account trick works.
However, i'm working on ways to avoid this in some future version.

Any chance that this one is coming along? This is the only complaint that I have with with NemosPlus.

https://github.com/nemosminer/NemosMiner/issues/450

I kind of do not agree on the proposed solution on this one.
One, monitoring WerFault would trigger even if another process triggers it. This is not specific enough.
Second, I feel that if ccminer (or others) are crashing, there are things to fix on the rig to get it stable.
One example might be to review OC settings or use the prerun feature to set algo specific OC settings.

So this, to me, and until i'm proven wrong, is a rig issue and not a product issue.
Note that i'm honestly opened to be proven wrong here. I just haven't seen any occurrences of this on any of my Rigs

MrPlus

I can see your point. It is almost certainly tied to OC values in my case.

That kind of turns it into a discussion about the definition of stability then... As an example: I'll have a machine up for days when suddenly a known stable algo will cause ccminer to fail. Anecdotally I've had one run solely x16r for 30 hours straight before erroring out. I've had it happen on Skein (after ~1.5 hours) & x17 (after 10+ hours) as well. I closed out the error message popup, restarted NemosPlus, and it went back to work unhindered. No changes to algoOC.bat

On the other hand I've got one machine who has been up for 75 hours at the moment without any issues or OC failures.

I suppose this is probably not an issue for you guys to resolve with a public facing code update or feature request.

Thanks for yout insights.
It is still a nice discussion to have. I might not get the full scale of the issue.
Any other argumented insights, please keep posting.