Project 8057 isn't showing on the list anymore
http://fah-web.stanford.edu/psummary.html

Beta projects are added to this summary
http://fah-web.stanford.edu/psummaryC.html
 
Also I clocked my 580's to 900 mhz and now they are at 158k PPD

I updated projects on one of my HFM.net today 8057 showed up as being added I'm using psummaryC .

jkefalas
Still no QRB units here with 2 gpus running beta 24/7. Anyone?

4 Fermi GPU running. No QRB yet.

No QRB still, although 2 GPUs switched off after AX1200 in for RMA

Just a quick GPU Console Client question regarding this 8057 WU.  Is anyone using the GPU Console Client (6.41), with a Kepler and receiving the 8057?  I've never been able to even get Kepler and Console Client to work, but just wanted to see if someone has done it.  I know that V7 has all this covered, but I still prefer the Console. 

jkefalas
I'm being innundated with 804x wu's for SMP and gpu currently. Points scheme is about 30% less. These should be labeled as qrp: quick return penalty, lol.

Couple of thoughts for you based on my recent experience with SMP WUs. 

• For Windows, use the Console SMP Client (6.34) and do not set -advmethods in the startup string.  I've been getting a steady diet of 694x through 699x SMP WUs that way.
• Alternately, if you can, Fold under Linux which also yields the same results as above.

Afterburner
All I am getting with my 680's are 7623/7624/7625... 

Well at least I am getting something, I should not complain... I do have the feeling every-time I look at the low PPD and want to scream "Show me the BETA's" 

Maybe I should work out, put on a pair of shorts with no shirt, and call an agent so it can happen... Hmmmmm

If the "agent" starts calling you "Mr. Anderson"...run!!!  

texinga

Just a quick GPU Console Client question regarding this 8057 WU.  Is anyone using the GPU Console Client (6.41), with a Kepler and receiving the 8057?  I've never been able to even get Kepler and Console Client to work, but just wanted to see if someone has done it.  I know that V7 has all this covered, but I still prefer the Console. 

 
i would direct you to my earlier post on betateam flag for v6
someone at FF has received them using the gpu client
 

i was just checking and i got a 8057 on my 470 at 70,000ppd tpf of 3:04 now just waiting for the 2 460's in that rig to snag them 

got another
 
8057(0,137,0)
tpf 2m2s
shortest 2m2s
longest 2m3s
est credit 18322
est PPD 129756 
 
same settings as before as my previous post (except I have 2 670ftw running in SLI)
 

I set the flags, but what doesn't make since is it gave me a 7626 forced a core update to 2.25 over v2.22 for this project.
TPF w/ 2.22 5:09 est PPD 14.5k
TPF w/ 2.25 7:19 est PPD 10.2k
 
As you can see what once took 8 hours & 35 mins. to do now takes 12 hours & 6 mins.
Hardware:
MSI 480GTX stock clocks
2600K @ 4.2Ghz
8GB ram 1600Mhz
How is that helping science or even QRB if it was imposed ?

Well I'll work this one, but if it doesn't give me something better on the next I'll be shutting the GPU's back down.
Many are like me and will not fold if it will take more time to do something than it should.
Look at the extra time & cost this will place on people not counting the extra heat these WU's put on the hardware its being ran on.
Now I have to do a extra 3.25 hours to return a WU & for less ppd & more strain on my hardware & power bill.
Sorry its not going to happen. I sure many others feel the same, so what you say may pay off later on IF they get this fixed, but its hurting the fold now..

you need to DISABLE -advmethods and manually add -betateam to the extra_params= section of client.cfg 

Has anyone gotten the "-betateam" parameter to work with GPU Tracker?
 
My clients don't want to start back up after the modification.
 
 
 

I just picked up 8057s on all 3 GPUs