• 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.

help - Folding@home has stopped saving progress

goat_face

n00b
Joined
Mar 28, 2006
Messages
2
hello, i think this is the right place to ask, but if not a pointer to where to go would be great.

right now, i am running Folding@Home 5.03 on amd3000+ winxp sp2, it runs about 16 hours a day
so i only get like 1 WU every day or 2, but i just noticed for the last few days i had been reworking beginning of the same unit over and over
p1815_Collagen_Brodsky
AMBER core
i have changed the Core priority, cpu usage percent and checkpointing frequency to different amounts but it still isn't saving.
 
chances are that the GUI version is just messing up on you...have you tried switching to the console version?

or...you may also may just be getting the same protien too...check your FAHlog.txt
 
I'd only change the CPU percent, not the core priority. I always leave the priority at "idle". Never have heard of a reason to change the priority.

I'd also suggest taking a look at your FAHlog.txt

Ex:
Code:
[13:26:51] Preparing to commence simulation
[13:26:51] - Looking at optimizations...
[13:26:51] - Files status OK
[13:26:51] - Expanded 132536 -> 684763 (decompressed 516.6 percent)
[13:26:51] 
[13:26:51] Project: 2099 (Run 65, Clone 0, Gen 23)
[13:26:51] 
[13:26:51] Assembly optimizations on if available.
[13:26:51] Entering M.D.
[13:27:12] (Starting from checkpoint)
[13:27:12] Protein: p2099_abeta_4mer_agbnp
[13:27:12] 
[13:27:12] Writing local files
[13:27:12] GB activated
[13:27:12] Completed 262500 out of 750000 steps  (35)


Look and see if the Run, Clone, Gen are the same. Also check and make sure that you are not getting any early unit ends errors. Early unit ends are often caused by having an unstable overclock, or stopping and starting the service really fast repeatably.


 
Code:
[11:35:29] - Ask before connecting: No
[11:35:29] - User name: Goat_Face (Team 33)
[11:35:29] - User ID: 43202F70038E270B
[11:35:29] - Machine ID: 1
[11:35:29] 
[11:35:30] Loaded queue successfully.
[11:35:30] Initialization complete
[11:35:30] + Benchmarking ...
[11:35:34] 
[11:35:34] + Processing work unit
[11:35:34] Core required: FahCore_82.exe
[11:35:34] Core found.
[11:35:34] Working on Unit 04 [July 25 11:35:34]
[11:35:34] + Working ...
[11:35:45] 
[11:35:45] *------------------------------*
[11:35:45] Folding@Home PMD Core
[11:35:45] Version 1.03 (September 7, 2005)
[11:35:45] 
[11:35:45] Preparing to commence simulation
[11:35:45] - Looking at optimizations...
[11:35:45] - Files status OK
[11:35:45] - Expanded 83142 -> 561874 (decompressed 675.8 percent)
[11:35:45] - Checksums don't match (work/wudata_04CP.arc)
[11:35:47] - Starting from initial work packet
[11:35:47] 
[11:35:47] Project: 1815 (Run 4, Clone 361, Gen 3)
[11:35:47] 
[11:35:47] Assembly optimizations on if available.
[11:35:47] Entering M.D.
[11:35:55] Protein: p1815_Collagen_Brodskymore_refolding
[11:35:55] 
[11:35:55] Completed 0 out of 500000 steps  (0)
[11:41:48] Writing checkpoint files
[11:48:24] Writing checkpoint files
[11:54:24] Writing checkpoint files

what would cause checksums problem? I checked the harddrive for errors, defraged, and ran memtest86. All were fine. I might try the console, but i don't know anything about that yet :)
 
oh man...you got a big one...YURT stats are showing it takes about 3 days to finish that one...so basicallly it is still probably waiting to finish that frame....i would defiantly switch to the console version. If you run the console version from the same directory it will continue with the same work. Just be sure to delete the startup item for F@H in the start menu. If you need, i can break it down further for you.
 
Back
Top