Anybody know if your WU's are recoverable when Folding crashes and accidentially starts up another Core. I had 2 cores running, than realized one was 70%done and the other 30% ... I quit and killed the xtra core, restarted Folding ... and I was back to 0% ... very upsetting. I guess all I'm saying is be careful : )
-Chris

[wheeles]

A similar thing happened to me when I had a background CLI job running and accidentally fired up the GUI. I lost a day's work as a result.

In the end I removed the GUI app from my machine and have written a wrapper which I use to fire up folding from the CLI. If one for the CPU is already running it doesn't start a new one up.

[Michael A. Peters]

Originally posted by wheeles:
<STRONG>A similar thing happened to me when I had a background CLI job running and accidentally fired up the GUI. I lost a day's work as a result.

In the end I removed the GUI app from my machine and have written a wrapper which I use to fire up folding from the CLI. If one for the CPU is already running it doesn't start a new one up.</STRONG>

I do know that for my athlon, there was a situation where the server was sending units out but not receiving new ones back.

There were 3 cores running- two for finished units in Q and one for unit being processed.

I killed folding completely, started one core, and that started the other two (I guess from the que)

Eventually they all got sent, and now only one core is running.
So you have to be careful about killing cores that you think are in excess- they might not be.