https://bt.irlbtc.com/view/735170.msg9310611#msg9310611

Assuming I understood what dev meant (let say there is 50% chance I did... but from recent experiences I am rather pessimistic at that level and I guess I could add a 2 dice rolls and remove the numbers from 50% , so it 50% - 2 random numbers between 1 and 6  )

I would say never (or in about a year at pow phase-II) (however since it is below 50% because of the dice roll... the most probable answer is "yes sometimes between next week and a year")

I have been through this before. The problem is something to do with the Cygwin compiler not handling pthreads very well so I do not recommend using my minerd with --threads greater than 1. The trick is to start multiple instances of minerd instead i.e. if you have 4 cores then start minerd.exe four times with --threads=1 and then you will find the CPU is 100% used. My Windows batch file "wrapper" automine.bat does this for you.

There is a bug in my Windows batch file  "wrapper" for minerd due to Suprnova changing the stratum port number they use for connections with the new algorithm. They changed from port 7127 to port 7128 so I have patched my batch files automine.bat and setup.bat accordingly. I have also modified the read.me file. Updated versions are available on the same links as before:-

Windows 64 bit .rar file https://www.dropbox.com/s/hiadf8o5u7bsit7/XMGpoolminerWin64.rar?dl=0

Windows 64 bit self-extracting .exe https://www.dropbox.com/s/dw7yjssjrrqp0m1/XMGpoolminerWin64.exe?dl=0

Windows 32 bit .rar file https://www.dropbox.com/s/dii8cvz7lp8xuey/XMGpoolminerWin32.rar?dl=0

Windows 32 bit self-extracting .exe https://www.dropbox.com/s/qlak24sxn6ookaz/XMGpoolminerWin32.exe?dl=0

If you are using my software and have trouble connecting to Suprnova pool, this is the reason for it. Sorry about that. Download the package from the appropriate link above. Stop any minerd processes currently running. Unzip and overwrite all files. Run the setup.bat again and provide your pool login, worker name(s) etc to fix the problem, then run XMGminer.bat (or Myminer.bat) to restart the minerd processes.

ah ok so i just have to create about 1000 workers 

It is totally correct and normal that the pool varies your diff to get your miner send a share every x seconds, its not necessary to send a low diff every second if you can also work on a share 10 times that hard which gives you 10 times the credit but you only submit every 10 seconds which lowers the load on the pool greatly.

try it - your payout estimates will be the same.

If you are running 1000 CPU cores then that is what I am suggesting - yes

I found that setting up 32 workers did not take too much time, but 1000 is another matter

Try setting up a few extra workers first and point some single-threaded minerds at them. You will see what I mean - you should see a greater rate of accepted shares compared to having multi-threaded minerds pointing at a single worker. It is up to you to decide if you think it worthwhile to invest some time in setting up multiple workers on the pools, based on your results of testing with your particular hardware/software environment.

No problem with the wallet. Do you have the latest version?
What kind of error?

Thank you qiwoman2!
Looks very good. Nice job and welcome in this great community!

Which miner you're using, vps, windows?