Ultimate Guide To Folding@home

Originally posted by nigel123@3 February 2004 - 21:31
:o Watch out Clocker...Livy is catching up with you.....fast! :o
Click to expand...
YEP, only 32 points in it now. :)

come on peeps were now past the 1000 mark, and just about comin on 900, fold on, and get team klf up the ranks.
 
Originally posted by 4th gen@19 March 2004 - 07:56
Just got my first 2500 part WU. My other 4 up until now have been 500 parts, so this one is gonna take a long, long time...

Just out of interest, how long (on average) does it take you chaps to complete a 500 part WU, and what CPU have you got?
Click to expand...
 
Thanks Nigel.

:01:
cert50000.jpg
:01:
 
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)"

:(
Click to expand...
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.
 
At last, project 638 has been given it's proper score.

I've done about a dozen of these over the last few weeks, but it was only given a score of 128. Yet p639 which takes exactly the same amount of time was correctly recieving a score of 239.

I reckon I've lost about 1500 points in the last month, although I don't suppose I'm the only one so it probably has not affected my position much.
 
Woot, finished my first WU, was a 1000 one, only took like 8 hours on my athlon XP 1900, but yet the I'm doing a 2500 on my Athlon XP 3200+ and I'm still at 934/2500 after 24 hours???!!!???
 
Back
Top