spexx miner work fine for me. i am BUSTING the hash. cheers spexx!
Not sure how, supposedly it's using the generic miner. have you tried the previous one with the right feature set for your CPU?
Yes it is using the generic 64 bit Windows miner, which works on any 64 bit CPU running Windows 7 SP1 or higher, Windows Server 2008 SP1 or higher for best results. The miner is compiled from the code provided by Noncepool and the source can be found at:-
https://github.com/noncepool/m7magi-cpuminerThe compiled minerd.exe might be called "generic" but that does not mean that it is an under-performer. As I understand it, the compiled code contains multiple program streams to support a range of CPU architectures and instruction sets, which simply means that the executable file is much larger than any version compiled for a specific CPU.
According to my benchmarks, the generic miner compiled (by me) under Cygwin, when run according to my advices i.e. starting multiple instances of minerd with a single thread, as opposed to a single instance of minerd with multiple threads, runs at a higher hashrate than any of the processor-specific miners EXCEPT the one for Intel Haswell class processors, where that one has the edge by 4 percent. I should admit that the idea of running multiple instances of minerd instead of multiple threads was not my original idea, but something I picked up on that was posted here by somebody else. There is a wealth of information to be found in this forum, but I do appreciate that nobody is going to read through the whole lot of it (or even understand a lot of it) so I created automine.bat et al to try and make it easy for people to get their wallet and miner setup just right for best performance.
Anybody having trouble just running up automine.bat is kindly asked to specify the problem they have with it. I cannot assist or begin to diagnose the problem without information about the hardware/software environment and the error messages you are getting. Certainly every machine I tried the package on worked first time and others have it working too. The one person who reported their problem precisely (i.e. it didn't support 40 processors) was provided with a patched version within minutes of me seeing their post. What more am I expected to do? It is no use just sitting there, arms folded with a stern expression on your face, saying it doesn't work. Is it plugged in? Is it switched on? Is it online? Has it got paper in it? Has it got ink/toner in it? Did you mess with it? I can't see what you are seeing and I'm not making housecalls
There was a good reason for having the default behavior of automine.bat to open multiple windows and it is easy to change that behavior via Setup.bat, or you could also run automine.bat with parameters - parameter 8 controls that behavior and is fully documented in the file header if you take a look at the code. There is also a good reason for every question asked by Setup.bat and in fact, depending on what type of mode you choose to operate, it will skip certain questions anyway. For example, if you are setting up mining with the wallet on the same computer AND have just completed the section to set up the magi.conf file, it will not ask you for the rpcuser, rpcpassword and rpcport again - it will take the info you just provided (or the defaults if that was what you selected). If you are very experienced with mining under Windows, you must surely see the sense of every question. Every question includes explanatory text and suggests a default. One thing that it does not ask about is whether you are mining via a proxy. If you have to do that, you will have to edit the file failover.bat manually and this is documented in the read.me file. There are various proxies that work in different ways and I did not want to open that can of worms.
Setup.bat does not ask for a pool
username. It asks for a pool
login name, worker name and worker password, all of which are required to construct the correct minerd.exe command line e.g. --user loginname.workername --pass workerpassword so your gripe there is noncense old boy (yes I deliberately mis-spelled that)
Maybe you are attempting to be too clever with it? It was designed to be mostly foolproof, not geniusproof.
The package included cpuz (four files) because I had it lying around. It is not required as such. Take it or leave it, or delete it - it's irrelevant. Maybe I will leave it out of the next package if it is so annoying. Every other file is required. Maybe having a large number of required dll files does not look good, but who said it had to look pretty? The new algo coming up requires one more dll file.
Finally, If you want to use another minerd.exe version, go right ahead with my blessings. I have tested and benchmarked all of them. If you try it on its own with multiple threads, benchmark it, then try it again using automine.bat as a "wrapper" instead you might just find an improvement in hashrate. That was my finding.
Still not sure why my pool login is needed. Stratum only requires Pool URL, Pool worker name and worker password.
Also, the generic miner if I recall only utilizes SSE2 and no further instruction sets. I strongly suggest removing the requirement for Pool login name and compiling multiple versions of your miner and then include logic to detect the instruction sets the cpu supports. I can assist with that. Also you can move the files into a subfolder. As it stands it is just a giant mess and hard to make work.
I can assist with rewriting it to be simpler\making it more user friendly. I even have a way to have you have your multiple instances vs multiple threads run silent as well as including a script to kill the silent tasks in the background.
As for why multiple instances runs faster than multiple threads that tells me the thread management in minerd is pretty shitty and that windows' built in thread scheduling is more efficient.
and don't forget the PoM (
