Folding@Home Client v2 not stable???

[lennytiger]

My client version two is not stable on my laptop the old version worked fine but now I notice that if I do a CTRL + C and exit it doesn't like it when I turn it on again, and it then sends its results and gets new work...
any idea why??~#

The laptop is an 850Mhz P3 with Windows ME.

[Dunga Bee]

That is a known bug :(

Try the graphical version. I have not heard or anyone having that problem with that version.

And (correct me guys if I am wrong), but I believe that the text version really is not any faster than the graphical version (as long as you keep it minimized). The only time the graphical version slows is when you show the graphics.

[Ebola]

the graphic version has bugs too. the whole caching thing is a joke. in 1.34 a wu would resume where you left off if you quit but this one it starts over. the wu counter on the program does not match with the stanford stats either.

stanford still needs to pull their heads out of their butts and realease a version 2.2 with bug fixes.

[Dunga Bee]

Yeah, I think the WU counter just counts the number of "results" files in your work directory, not anything from the Stanford servers.

[sfa ok]

Yes, I'd like a text console that works well soon, especially because 2/3 of my computers are running Linux.

[asmodean]

I noticed one thing while testing higher FSBs... I usually forget to turn the FireDaemon service that I use to run the F@H client off, so I'm forced to kill fah... It usually leaves the core (core_65.exe) running... Same thing happens when I run the client manually and ctrl-c out of it.

I hope they fix that soon.

[Dunga Bee]

I have the same problem on a machine that I run F@H as a service.

Pain in the butt...

[Ploaf]

Yeah there are still a few bugs. i noticed a newer version is out already, but they still have a couple of issues to sort out before it's completely stable. Things seem to be going well here, but it took some effort to get it just right.