[texas booster]

Shutting down the 4.0 GUI version will save a check point in the log so that you can take off from where you last folded.

In case of a system shutdown I would think that you would only lose the points since the last check point, not the results from the entire fold. Let me look into that.

See if you can set the GUI to save a check point every 5 minutes or so.

[brityank]

Thanks; my checkpoint is set for 15Min, but it only seems to do them at each step anyway:

[12:36:37] + Working...
[13:34:40] Writing local files
[13:34:40] Completed 12200000 out of 20000000 steps (61)
[15:45:36] Writing local files
[15:45:36] Completed 12400000 out of 20000000 steps (62)
[18:01:26] Writing local files
[18:01:26] Completed 12600000 out of 20000000 steps (63)
[18:36:34] + Working...


Not a problem; I learned on my company's laptop not to allow the IT mavens to upload/reboot my machine after they clobbered five hours I had devoted into a spreadsheet.

Oh, yes. They did hear me now! ;^)

[HangThemHigh]

My power company sees fit to provide power here at the house most of the time. A year or so ago, if I lost power or even a brief flicker, I had about a 30% chance of losing the WU in progress. The checkpoint file seemed to be getting corrupted in a power loss. It got bad enough that I wrote a script to back up the whole directory about once an hour to preclude massive losses.

Lately Stanford seems to have fixed the console version so that on lost power the previously saved checkpoint isn't corrupted. I'm assuming they have "fixed" this as I haven't had to restore the F@H directory from my backups in 6 mo. or so.

Perhaps the GUI version hasn't gotten the fix, or Windows ME (I run XP) prevents the fix from working somehow. Even before the fix, if I shut down the computer normally (vs. a power failure or hitting the reset button) the checkpoint file would survive.

Not sure this helps, just an observation.