Ultimate Guide To Folding@home

Ok, was chatting about this with a friend on tha Chat.

Apparently this app might heat up the CPU if left alone,
any opinions on that?

I will install some CPU-temperature-controlling software now,
just to make my PC to shut down if it heats up too much.

:cool2:
 
Originally posted by Livy+7 February 2004 - 01:37-->QUOTE (Livy @ 7 February 2004 - 01:37)
I'll be 4th within the next day or two :P :D [/b]

88 points in it

are you going for 3rd? [/b][/quote]
Well, yourself and IC have three CPUs; I know yours are slightly better than mine, and I don't know about IC but he seems to do well, so I'll be hard pressed to catch up with you. I'll overtake Clocker at some point though :devil:
 
Originally posted by summerlinda@25 January 2004 - 14:36
You have to take better care of that Protein of yours, nurture it, talk to it, feed it etc.
....
Mmmmm, :frusty: always thought proteins were supposed to nurture ME :rolleyes:
 
Originally posted by Ariel_001@31 March 2004 - 18:04
Has anyone tryed running this as a service in win nt/2k/xp?

Anyways here are some direction on how to do it. It seems to work for me. Don't blame me if your comp blows up or something if this does something weird.

First make sure the folding@home Client is properly setup.

Then download the consol version of the client and this. Make sure the consol client is working properly first (run it first).

1. Then make a folder somewhere on your hard drive e.g
 
hmmmmm ..........

My school has over 100 new G5's .... I have a little idea. Stay tuned :P
 
Twice now since I've been using F@H, it's crashed taking hours of CPU time with it. The first time I lost about 71% of a work unit, due to a communications error with the server:

"[06:21:45] Completed 355000 out of 500000 steps (71)
[06:33:02] CoreStatus = 1 (1)
[06:33:02] Client-core communications error: ERROR 0x1
[06:33:02] Deleting current work unit & continuing...
[06:33:22] - Preparing to get new work unit...
[06:33:24] + Attempting to get work packet
[06:33:24] - Connecting to assignment server
[06:33:27] + Could not connect to Assignment Server
[06:33:27] + Could not connect to Assignment Server 2
[06:33:27] + Couldn't get work instructions.
[06:33:27] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry."

Which prompted me to stop using it. I retried it the other day, got one WU completed. My PC crashed again today, and no surprise, F@H lost its WU again:

"[16:33:30] Completed 480000 out of 500000 steps (96)"

:(
 
Originally posted by 4th gen@16 March 2004 - 17:22
Twice now since I've been using F@H, it's crashed taking hours of CPU time with it. The first time I lost about 71% of a work unit, due to a communications error with the server:

"[06:21:45] Completed 355000 out of 500000 steps (71)
[06:33:02] CoreStatus = 1 (1)
[06:33:02] Client-core communications error: ERROR 0x1
[06:33:02] Deleting current work unit & continuing...
[06:33:22] - Preparing to get new work unit...
[06:33:24] + Attempting to get work packet
[06:33:24] - Connecting to assignment server
[06:33:27] + Could not connect to Assignment Server
[06:33:27] + Could not connect to Assignment Server 2
[06:33:27] + Couldn't get work instructions.
[06:33:27] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry."

Which prompted me to stop using it. I retried it the other day, got one WU completed. My PC crashed again today, and no surprise, F@H lost its WU again:

"[16:33:30] Completed 480000 out of 500000 steps (96)"

:(
The first bit (up to [06:33:02]) indicates some sort of file system error, not a communication error. Basically it could not write the results to the disk, presumably because it thought the file was corrupt. Rather than send bad results back to the source it deleted them.

The next part (up to [06:33:27]) is an attempt to get another WU. First of all it has to connect to an assignment server. This then routes the request to a Work Unit server, but as the error messages suggest it could not even connect to the assignment server.

Both of these events occuring together suggest you have some inherent instability in your system, which is causing the crash. I'm guessing that you are using FAT32 file system. When your system crashes with FAT32, the last part of the file will be lost (just like with Kazaa). So F@H thinks your results are corrupt and discards them (again, like Kazaa downloads).

Suggestions:
Convert to NTFS if you are using FAT32. It won't cure the crash but it may stop you from losing your work.
Sort out your system instability - I've found from experience that raising Vcore slightly (0.025V is usually enough) can cure this problem, even though the system is theoretically running at the correct settings. Watch your temps though.
 
_JOHN_LENNON_:
1. Doing ANYTHING stresses the life of your processor, but this F@H (Folding @ Home) uses spare CPU cycles, so you dont notice it while your playing BF 1942, or while im playing Halo. But if say you leave your computer for a bit, it will notice the free processor, and pick up the slack.

2. It really doesnt hurt your computer like I said above, I konw people that have this running on no less than 20 machines and have been doing for awhile.

3. Yes, I said 20 MACHINES. People take this very seriously, as over at AMDMB.com.

4. I have been folding for over a year now for the AMDMB.com team, and I think were maybe 5th or 6th world wide. I know from our forums that we have several people like I said with the 20+ Computers running 24/7 just to fold for cancer. (yes the electric bill gets raised a few ticks) I know that also we have taken donation on 4 complete machines, and then given them to people to they can be Folding for the team in the privacy of their own homes. I think were currently taking donations for the 5th one.

5. You guys should all get into this, haha Bigdawg, being about my age I know your parents have asked you around the house at times (whats your computer doing on right now, when your not even infront of it.) Well, atleast now you could say Fighting Cancer Mom! Heh, no but serious guys, every computer can help, even if its just a few work units a month. And we all have Spare CPU Cycles to spare because none of us are maxing out our PC all day. Half the time I have my PC on im just tinkering with some and I have WMP on and Folding @ Home.

6. Now everyone go download the folding at home command Client

OC TEAM:
What are the system requirements for folding?
You will need to have the equivalent of a 200MHz Pentium to be able to process the work in time. The time limits for turning in completed work vary depending on the size and complexity of the protein that you are given to work on. NOTE: in some cases users have gotten even slower computers than this to fold and get units on time. The slowest i have seen get units in on time is a P166 mhz. If you think it is too slow to fold, give it a chance, what's that worse that can happen.




--------------------------------------------------------------------------------
 
why dont you just update the first page of the old topic?

{I}{K}{E}

btw. wasnt this spammed before on all the worlds?

I move this to the lounge because I think it fits there better.
 
No idea, your using the graphical version. I use the command line only version, and I have it set in the background to run as a service. Thus if I need to stop it, all I have to do is use the Net commands in the command prompt, and I just have a link to the FAH log, and the info log to check my progress.

Quite handy.
 
stopped using it srry, it was causing to much 'errors' and 'lags' on my custom GUI. even on the lowest CPU

{I}{K}{E}
 
Back
Top