We can trust the dev ?

Som1 did a virustotal ?

cheers

Does it tell you the pool hashrate? or does it say "Not found" for your address?

If it is the former can you see stats on this page? http://mine.moneropool.org:8117/stats

If you can't see that page it may be that you have port 8117 blocked or your IP is still somehow banned.

http://qcn.extremepool.org/ on port 1111

POOL version
Connecting to mine.moneropool.org, port 1111 ...
DevFee: Connecting to mine.moneropool.org, port 1111 ..
Timed out socket
Timed out socket
Failed to connect, retry in 5sec...
DevFee: Failed to connect, retry in 5sec...
DevFee: Connecting to mine.moneropool.org, port 1111 ..
Connecting to mine.moneropool.org, port 1111 ...

Tu veux tuer les coins, c'est ça ? Je te rappelles qu'avec un hashrate plus petit, tu reçois autant, juste plus lentement.
La pool de superresistant est en France - si tu y es aussi (en France) tu auras moins de problème qu'avec d'autres plus éloignées. Et en plus, c'est la quatrième plus grosse.

I get like 650h/s solo mining on an EC2 c3.8xlarge slice, so I would say the gap is far from closed between CPU and GPU miners.

http://monero.crypto-pool.fr/

Recently optimized. Fixed the code. Auto-restart. Less orphan, more blocks, more Monero.

Le premier mineur GPU pour Monero vient d'arriver. La fin d'une époque. https://bitcointalk.org/index.php?topic=638915

We are better than all these cryptos show your super power



https://www.mintpal.com/voting#SUPER

Hi, this is the fix.
I did study a computer that did have stalled working units, I did recoqnise that the percentage you can read in the GUI are really detached from what you find in the log file. What you find in the log file is what results you have from the GPU/WU, that is the true performance. So when a worker are losing sync to a working unit the percentage are increased with the same speed until at reaches 99.99% and stops(in the GUI), thats why you can find out that something is wrong until the timer are reaching 99.99%. So the GUI are not the right place to look for stalled WU's. So if you look deeper in to the computer to the list of processes and particular process FahCore_17.exe, these processes are one for each GPU in your computer. The average CPU usage are around 1-4% and memory size is 200-300 MB ruff numbers.(When the WU are loaded and are folding) When a WU are stalling the CPU activity goes to 0% and stays there until you pause and starts folding again and then the FAHControl.exe are restarting the WU from the last saved file. OK, that's nice you can actually check if the GPU's are folding or not, when the activity are 0% you only need to terminate the stalled FahCore_17.exe and the WU restarts(from last save file). BUT that is hard work to run around and check WU's, so to the end of the story is the automatic solution: Download a software called processlasso and install it. http://bitsum.com/processlasso/
Search and find one process of FahCore_17.exe and right click on it, select menu option "Set watchdog rules for this process", 1: for -CPU, 2: Less than, 3: 1%, 4: 300 sec, 5: terminate the process, 6: Puch button "Create new process watchdog rule". Now the software are terminating the wu that have been inactive for 5 minutes and restarts, this is saved by the software and are restarted every time the computer starts. - YES it works, no more lost hours of stalled WU's

//Aboy68, by the way - if you change in the motherboard bios settings the PCIe version to version 2, that gives you are more stable system, the timing is not that fast as version 3 and verson 2 have the bandwith we need in foldings, I have this setting on all mother boards, Ver 1 is to slow(I have tryed it)

and why? 750ti can still compete easily with those fpga, it's not like they are hashing at 1 giga per board or something

If anyone has features they would like to see changed/added to the client, you may want to start discussing them now.