• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

A little help needed please.

BLenderhedd

BLenderhedd

Gawd
Joined
May 1, 2002
Messages
731
I've got a PIII 650/Win 98 system sitting around, that my daughter uses sometimes, and I figured that since it's there, it should be doing something, so I tried to get it folding. I know this is a slow system, and don't expect it to be a top producer, by any means, but it's been running for a little over a month now and has yet to complete a single work unit.

I monitor it w/ EM, and I know that it is working, but it will get part way through a unit and dump it. I don't know if it's just missing deadlines, and so starting a new unit, or if it's corrupting them and dumping them off, or just what. The stuff in the log files means little to me, though I do see that every entry says "previous termination of core was improper," but it picks up at the checkpoints and seems to continue.

So, is it just too slow and can't complete in time? Or is there a trick to configuring a slower system such as this? I see others in here folding on 400mhz procs, so I know it can be done.

Any help is greatly appreciated.

 
Look through the logs (or post a link and I'll do it) for where a unit either finished or died. It'll tell you whether it was a proper end or not.
 
BLenderhedd said:
<snip> though I do see that every entry says "previous termination of core was improper," but it picks up at the checkpoints and seems to continue.

<snip>

Click to expand...
That message usually means the core is getting killed. One of the things that often happens then is that all optimized assembly is turned off and it will take twice as long to finish a frame.
This may be happening because other users are running an app that kill the process.
I'd suggest you try a timeless to make sure it will complete work.
How much RAM do you have?

 
Thanks for the replies, guys. Here's some of the info requested.

320MB RAM.

snip from log where a problems seems to have occurred:

# Windows Graphical Edition ###################################################
###############################################################################

Folding@home Client Version 4.00

http://folding.stanford.edu

###############################################################################
###############################################################################



[17:24:38] - Ask before connecting: No
[17:24:38] - Use IE connection settings: Yes
[17:24:38] - User name: Blender[H]edd (Team 33)
[17:24:38] - User ID = 44F120BD24777C01
[17:24:38] - Machine ID: 1
[17:24:38]
[17:24:39] Loaded queue successfully.
[17:24:39] Initialization complete
[17:24:39] + Benchmarking ...
[17:24:43]
[17:24:43] + Processing work unit
[17:24:43] Core required: FahCore_78.exe
[17:24:43] Core found.
[17:24:43] Working on Unit 01 [May 29 17:24:43]
[17:24:43] + Working ...
[17:24:49]
[17:24:49] *------------------------------*
[17:24:49] Folding@Home Gromacs Core
[17:24:49] Version 1.81 (April 6, 2005)
[17:24:49]
[17:24:49] Preparing to commence simulation
[17:24:49] - Ensuring status. Please wait.
[17:25:06] - Looking at optimizations...
[17:25:06] - Working with standard loops on this execution.
[17:25:06] Examination of work files indicates 8 consecutive improper terminations of core.
[17:25:08] - Expanded 387002 -> 1849013 (decompressed 477.7 percent)
[17:25:09] - Checksums don't match (work/wudata_01.xtc)
[17:25:10] - Starting from initial work packet
[17:25:10]
[17:25:10] Project: 800 (Run 30, Clone 91, Gen 3)
[17:25:10]
[17:25:10] Entering M.D.
[17:25:19] Protein: p800_p53dimer800
[17:25:19]
[17:25:19] Writing local files
[17:25:22] Writing local files
[17:25:23] Completed 0 out of 2500000 steps (0)
[23:24:40] + Working...
[05:24:37] + Working...
[11:24:34] + Working...
[17:24:31] + Working...
[23:24:28] + Working...
[05:24:24] + Working...
[11:24:21] + Working...
[16:42:52] Writing local files
[16:42:53] Completed 25000 out of 2500000 steps (1)
[17:24:18] + Working...
[23:24:15] + Working...
[05:24:11] + Working...
[11:24:08] + Working...
[17:24:05] + Working...
[23:24:02] + Working...
[05:23:59] + Working...
[06:45:40] Writing local files
[06:45:41] Completed 50000 out of 2500000 steps (2)
[09:49:59] Writing local files
[09:49:59] Completed 75000 out of 2500000 steps (3)
[11:23:55] + Working...
[12:54:44] Writing local files
[12:54:44] Completed 100000 out of 2500000 steps (4)
[15:59:30] Writing local files
[15:59:30] Completed 125000 out of 2500000 steps (5)
[17:23:52] + Working...
[19:04:04] Writing local files
[19:04:05] Completed 150000 out of 2500000 steps (6)
[22:08:31] Writing local files
[22:08:31] Completed 175000 out of 2500000 steps (7)
[23:23:49] + Working...
[01:12:38] Writing local files
[01:12:39] Completed 200000 out of 2500000 steps (8)
[04:16:58] Writing local files
[04:16:58] Completed 225000 out of 2500000 steps (9)
[05:23:46] + Working...
[07:21:27] Writing local files
[07:21:27] Completed 250000 out of 2500000 steps (10)
[10:25:44] Writing local files
[10:25:44] Completed 275000 out of 2500000 steps (11)
[11:23:42] + Working...
[13:30:07] Writing local files
[13:30:07] Completed 300000 out of 2500000 steps (12)
[16:34:29] Writing local files
[16:34:29] Completed 325000 out of 2500000 steps (13)
[17:23:39] + Working...
[19:38:49] Writing local files
[19:38:49] Completed 350000 out of 2500000 steps (14)
[22:43:35] Writing local files
[22:43:35] Completed 375000 out of 2500000 steps (15)
[23:23:36] + Working...
[01:47:49] Writing local files
[01:47:49] Completed 400000 out of 2500000 steps (16)
[04:51:59] Writing local files
[04:51:59] Completed 425000 out of 2500000 steps (17)
[05:23:33] + Working...
[07:55:57] Writing local files
[07:55:57] Completed 450000 out of 2500000 steps (18)
Click to expand...

 
Could be hard disk problems; if the files get corrupted that would explain it. It could also be memory problems, and that's the easier one to check. Run memtest86 for a while (24 hours is the definitive time) and see what turns up.

It could also be temperature problems; is there temp monitoring on that chip?
 
gnewbury said:
I'd suggest you try a timeless to make sure it will complete work.


Click to expand...


Not sure how to do that. As I understand it I can't anyway, as I am running the graphical client.

 
The graphical is not quite as stable as the text based one. You can still configure the graph client to run timeless. Right click on the f@h gear/flower icon and click on configure. As I start telling you this I realize that it has been a long time since I ran the graph one. Here is a link with more info...link .

I would again say that the console/text based client is better.

 
That also looks like someone is turning off the computer without shutting down the folding program. This will cause that error in win98 boxen.

T-3
 
You must log in or register to reply here.
Back
Top