ARRRGH!!! Why is Folding freaking out on me?

[flounder43]

My main comp's folding client is freaking out...it just keeps downloading data....
It says "downloading new core: Core_65.exe" then it counts the bytes up to about 300k or so, then it starts all over again...

It might have been doing this all night!!!

What is going on? I restarted it, rebooted my comp, still it is in this loop...I think the other comps are fine...

Ideas????

[Allan Nielsen]

Time for reinstalling the client I think!

[Kendan]

here is what is working for most.

Update your ver. to newest 2.17. You might still have to do the steps.


If you have 2.15 then you can just

1. Shut down client
2. delete work folder, que, core65( if their are two core65 with different extentions delete it too.
3. restart client.
4. Fold.

hope this helps you get back to folding!!!

[Ebola]

there's a 2.17. man why didnt anyone post this before. next week after i get my new rig set up i'll post the newer versions on the website to download.

[Kendan]

It is still a beta but here is the link. I have it running on two of my machines.
http://folding.stanford.edu/beta/
there you go now go Fold:burn:

I have it on my main rig and I think it is faster I will keep an eye on it and pot a thread in a few days with the times.

[flounder43]

I did an uninstall and installed the newest version, that seems to have fixed it.

What he heck is up with that anyway? Was it some pitiful attempt on Stanford's part to do an auto update? Imagine how many people don't have a clue how to fix it...and are just going to quit folding...

Stanford should really buck up, they just making more and more people mad with their half-a$$ed client.. I try to convince people that the problems aren't that bad and everything is fixed, etc. But it just isn't true. GRRRRRR :mad:

[The Coolest]

It did happen to me a couple of weeks ago, I just deleted all the files that were mentioned above, then restarted the client downloaded the core65.exe 1 & only 1 time and continued folding. I think its just a bug or the core65 or some other file got corrupted in some way

[Ploaf]

This same thing happened with all of my machines last night. I just let it go for a while and it turned out alright.