Folding Forum

The client ran without the icon in the system tray (winXP). I terminated it through the task manager and started it again. It did not continue the work unit and instead fetched a new one.

The above discontinued work unit stopped at 40%. How can I continue this work unit?

It is frustrating to lose several days work. In the past I lost a few partial work units and did not bother checking their status. I just continue with the newly fetched ones. I stopped folding for several weeks after I lost two partially done WUs in a row. This is the first time I will try to continue a stopped WU if it is at all possible. How? I'm currently running a new WU.

Terminating via the task manager is not the right way to close the client, however I think I understand the problem, you are using the icon tray but you can't see the icon to close it down properly? In this case, I'd probably restart the computer but even then there's a good chance that the work will be lost. The best option is to use the console version which is a lot easier to work with and a much safer option if you for example shut down your machines quite often. Unfortunately you won't be able to recover the unit that was at 40%.


Pete

The most probable reason why the icon might be missing from systray is that your desktop had a crash but Windows did not. When explorer terminates (i.e.- the program that shows your desktop) Windows restarts it but the icon does not re-appear in the restarted systray.

Another reason why you might not have an icon is if you're running the console version which you may have installed as a service. It doesn't sound like that applies to you, though.

Thanks for the explanation. I am using the system tray client. I recently (the most recent ones) have three successive partially done WUs that won't continue after shutting down the client and WinXP normally and starting them up the following day. Here are the errors from the log file.

Error: Could not get length of results file work/wuresults_04.dat
[07:46:40] - Error: Could not read unit 04 file. Removing from queue.
----
[07:47:11] Error opening or reading from a file.
[07:47:11] Deleting current work unit & continuing...
-----
00:48:20] - Checksums don't match (work/wudata_08CP.arc)
[00:48:20] - Attempting to revert to backup...
[00:48:20] - Checksums don't match (work/wudata_08CP.arc.b)
[00:48:20] - Could not revert


What could be the reason(s) for these?

We don't necessarily know all of the possible the reasons for a certain error, but the most common problem is that Windows was not properly shut down. Generally speaking, you're talking about limitations in how Windows interacts with your hardware rather than how FAH interacts with Windows.

Part of the normal shutdown sequence closes all files and makes sure the cache has been written to permanent disk before the shutdown is complete. Loss of power or a BSOD or other catastrophic system failure can prevent the cache from being flushed, leaving corrupt files. FAH will not use files which have been corrupted, no matter why they were corrupted.

If your AntiVirus program attacked any of FAH's files, corrupt files will result.

One suggestion: If FAH is running on a FAT volume, there are a lot more chances for corrupted data than if it's running on a NTFS volume.