...my client stopped working when I had finished about 4200 of 5000 work units and then started from zero again picking up a new work unit from zero.I had been running it for 6 days so it was a little irritating.
Sorry you lost your work, Shonghow.
Sounds like your work unit was 84% complete, 4200/5000 frames or steps of the unit.
Is your operating system WinXP? or some other version?
When something like this happens it is often the result of corrupted files in the F@H folder. An OS can corrupt the files if shut down at inopportune time in the folding process.
I got no points for it.
Stanford awards points for partiallly completed work units, whenever enough of the folding records survive to determine what work unit, and point value, and how long the work unit was worked. If you receive no points at all then the work files must have been obliterated.
What should I do to prevent this from happening?It happens when I turn off my computer but not always.
Did you stop the client with the controls available within the client, before turning off the computer? Which client are you using, Graphical Windows, version 5.03?
Normally, stopping and starting the F@H client causes no problems if it is stopped within the client itself. WinXP seems pretty good at closing applications during shut down without corrupting files, but Win98 and WinME could regularily corrupt files by shutting down the OS without first stopping the client software. In any event it is best to stop the client with the client command "Quit" before turning off a computer.
In the folding folder is a file called FAHlog.txt, this file contains records of events that occur during the folding process. FAHlog.txt can be valuable for determining what happens when problems do occur.
Here is an excerpt from FAHlog.txt:
[00:11:35] Preparing to commence simulation
[00:11:35] - Looking at optimizations...
[00:11:35] - Created dyn
[00:11:35] - Files status OK
[00:11:35] - Expanded 18105 -> 126519 (decompressed 698.8 percent)
[00:11:35]
[00:11:35] Project: 4545 (Run 66, Clone 92, Gen 0)
[00:11:35]
[00:11:35] Assembly optimizations on if available.
[00:11:35] Entering M.D.
[00:11:41] Protein: p4545_T0396_2-16_minout
[00:11:41]
[00:11:41] Completed 0 out of 2500000 steps (0)
[00:18:30] Writing local files
[00:18:30] Completed 25000 out of 2500000 steps (1)
You may wish to start examining FAHlog.txt on your computer, looking for anomalies. If you have another loss of work unit, try to find the area in the FAHlog.txt where it indicates a problem and post it here. The FAHlog.txt can contain records from previous work units. You may find in the current log where the client was working step 83 or 84 of previous work unit, then examine log contents afterward. This may provide clues as to what happened.