Or, if you mean the pool I was connected to and the flags etc, I'm using AOCLBF (although I was using GUIminer with the same issue), connected to bloody's at the moment, using Phoenix with -k phatk VECTORS BFI_INT AGGRESSION=13 WORKSIZE=256 FASTLOOP=false

Ok, back up and running. Couldn't connect to guiminer at all for a while until I noticed it had changed itself to port 8332 and solo mining for whatever reason. Changed that stuff back (took a few goes to stick) and we're back up and running. Will monitor for dropouts and post the output if it happens again. Ta

gnaget are you hopping them or riding 247?Hasn't been a bad time to be 247, tbh.Also, I've been running with Cherry Picker on more and more rigs for the last day or so. BitClockers doesn't seem to block, delay, QOS, etc. using CP. Interesting data point.

This site appears to be using javascript to display the pool stats. I'm not sure how to pull that into bithopper.

-grassfed all the way-

But, since I couldn't help you with that, re-add bitcoinpool.com

Here's why:After looking at my account settings I realized that if you donate 1% or more to the pool they will not implement any anti-hopping measures on your account. I think that's a good system and we should look into making similar arrangements with other pools. I'd be willing to donate up to 5% at some pools, to be able to hop freely. The pool can keep it or redistribute it to their full time miners. Just a thought....

I guess it could be... i just remember a lot of people in the phatk thread having the exact same idle problem..i'm not.. I'm also on bloody.. but it might still be.

Quote

This site appears to be using javascript to display the pool stats. I'm not sure how to pull that into bithopper.

ryouiki says it needs a cookie to pull the stats.I was using ff 'view selection source".. which looks a bit different than "view source" and it had already pulled in the javascript. .. eh lesson learned. wish i had noticed before I pulled my hair out on it.