Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 1162. (Read 2375926 times)

Cool.  Love the documentation.  I'm kind of a compile it myself if possible kind of guy and work under Ubuntu, but I enjoyed the verbose read, with obvious effort to build something worthwhile, so I sent you at tip. The dll's are almost tempting enough to make me switch back to Windows

One of the joys of software developing is: “making software that pisses off any annoys less”.  Kudos to anyone with ample documentation.  Lol.   

Spexx and MarcusDe, can you help to compile the new miner for windows? Thx

https://github.com/noncepool/m7m-cpuminer-v2

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-cpuminer
The 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.

I think it's not going to last very long
Dev'll answer this.

question. does anyone know when POW is ending? approx

Not sure how, supposedly it's using the generic miner. have you tried the previous one with the right feature set for your CPU?

spexx miner work fine for me. i am BUSTING the hash. cheers spexx!

After the hardfork I think all existing miners will need to be recompiled to include the new module for the modifications to the algo

been hassling with the new miner too, but could not get it working.
so switched back to the marcus miner again. what to do after the hardfork? will this miner still work?

The problem was it was prompting for a pool username and I've never had to use one with stratum. Also it isn't optimized as its using the generic miner.

If you switch to a better language you can include detection of CPU features. It also appeared to open a new window for each thread by default.

The existing miner that was 64 bit worked great for me. That's what I am planning on using with simplicity when I port it.

Also why did you include CPU-z and have some other stuff included? The whole package just doesn't make sense. I've been a long time miner and that package asks too many questions. People want it to be as simple as possible. There is a lot you can do to simplify that still.

Thanks for that. It will give me something to play with when I get back from work today. I have started up the new wallet and it synced ok. It will be running idle for the next 12 hours or so, then I will be testing the latest minerd with it. It says it is not staking because I don't have any mature coins, even though I have over 3000 testnet XMG in it.

Ok - done that. Including support for any number that is a multiple of four is a cinch. I have called it automine40.bat so when you have downloaded it, rename your existing automine.bat to something like automine-max32.bat and then rename automine40.bat to automine.bat and you should be good to go. Here is the link for the file:-

https://www.dropbox.com/s/cqjbvjp2klkqkl2/automine40.bat?dl=0

Anybody else got more than 32 processors? Lucky you

Crikey! You got 40. OK I can extend it to support 40 but it will take a while with a pen and calculator. It supports a maximum of 32 at the moment and I did plan to extend it to 64 anyway, so I'll get on it. It will take rather less time to make a version that supports exactly 40 processors, just for you, than it would to make a version that supports any number of processors up to 40 (and beyond). I'll be back ...

Yes Magi is on the right track

gar!

***************************************

          XMG Magi Autominer

***************************************

40 processors not supported yet - sorry
Press any key to continue . . .

seems to be working fine for me. Loving this coin and its progress so far! time to get more investors in!

i give this a green!

I'm doing well with his miner so far.

just saw this post. Pretty impressed by the outlook from other contributors. Great work Spexx! 

aceoyame, just had a rough looking over the things, not quite getting the tasks to be done to get this work, but guess we'll need a miner (Spexx's miner should work the way as easy as the miners other people provided) and a P2P (or NOMP, I think), unfortunately we don't have these two options yet.

Anyone else may give a hand on this. Thx.

Spexx, I've done the testnet, you can run the wallet now, will need to download a new wallet though (from here: http://cryptomagic.com/files/magi-release/testnet/ (v1.0.0.4)), cause I just made a hardfork to implement the new difficulty adjustment algo. If you can detect any difficulty change/network hashrate variation that is more stable than before, let me know. I will be expecting this is what we'll get but testnet has much less hashrate and may hardly tell the truth probably.