Quote from: Travis9x on October 15, 2014, 01:57:57 AM

Quote from: djm34 on October 15, 2014, 01:16:25 AM

I must admit I never heard of miner control before so I can't really be of any help (just read a few message on their thread where they tell "us" to put our shit together (to summarize... ) may-be they should first explain what they want to do with others application rather than complaining... (especially when they never put any message here to describe what they intended to do Grin

)

Not sure where you're getting the idea that the MinerControl thread just complains about ccMiner. Aside from a single comment about the GIThub repository, almost all comments in that thread about ccMiner (and everyone involved in it) have been praise, and encouraging donations. Also, I believe the creator did indeed announce in this thread what he was making, and what it was supposed to do, when he released the very first alpha version of it (started out called "NiceHash Control").
In short, Miner Control allows people to use ccMiner (or nvMiner, or any other derivative) to automatically switch pools & algorithms, based on profitability. It was initially built specifically for ccMiner and NVIDIA GPU's, because there was not yet any support for such auto-switching with NVIDIA GPU's, and at first only supported NiceHash (now supports several pools, and can be used with other mining apps). It simply checks various pool API's, and starts the miner (ccMiner, or whatever mining app the user wishes) pointed at the most profitable pool/algorithm. It continues to check API's, and if another pool/algorithm becomes more profitable than the one currently being mined, then it will shut down the current miner, and start it again pointed at the new pool/algorithm.

djm, your reply on the Miner Control thread was a little brusque, and being that I doubt you are following that thread I'll reply over here.

I haven't been following the ccminer thread too closely the last couple of months but for a while I did see that several people were working independently on ccminer (doing great things) and a couple of people were then trying to merge together the best of each work into a unified product. A little haphazard but it was still making progress. That was the source of my musing that a single github repository would be a nice baseline for continuing to improve ccminer being that cbuchner has moved on to other things. If your branch is now the most complete then hopefully others will submit pull requests to you rather than forking and releasing even more variants. I'll probably try switching over to it myself soon as the latest version of nvminer I'm using is experiencing occasional crashes that I wasn't seeing before.

As for kalen37, a couple of us ~~here~~ over there directed him towards the ccminer thread being that the problem he is experiencing appears to be ccminer related and nothing to do with Miner Control. I had him try launching ccminer from a batch file a few days ago to get Miner Control completely out of the equation and he still had the same problem with it not starting up correctly. At that point it became apparent he would likely get better help on the ccminer thread.

Miner Control is generic and not dependent on ccminer or any other specific miner program. It is just a tool to launch whichever miner someone chooses to configure under it. The releases don't even have a real miner bundled in, just a fake one used to demonstrate how to configure the program.

Good luck with your continuing work on ccminer.