Help me! Keep loosing my work!
Hello all of you,
I lost all of my first WU again...this time I didn't delete any files but I had to kill the FahCore_65.exe program from the Task Manager as I couldn't access it.
When I re-launched the application it opened 2 sessions with my work still there. I closed both of them, re-launched and at that moment it started again from 0%!!
:bawling:
In this directory: C:\Program Files\Folding@Home is there any files saved with my work on it?
Is the work information saved locally, or on a server?
Should I change client and use the console?
Please help!
Peace,
requin
I lost all of my first WU again...this time I didn't delete any files but I had to kill the FahCore_65.exe program from the Task Manager as I couldn't access it.
When I re-launched the application it opened 2 sessions with my work still there. I closed both of them, re-launched and at that moment it started again from 0%!!
:bawling:In this directory: C:\Program Files\Folding@Home is there any files saved with my work on it?
Is the work information saved locally, or on a server?
Should I change client and use the console?
Please help!
Peace,
requin
0
Comments
Here are the 2 I have FAHlog.txt and FAHlog-Prev.txt
[07:35:44] CoreStatus = 1 (1)
[07:35:44] Client-core communications error: ERROR 0x1
[07:35:44] Deleting current work unit & continuing...
Thats prolly when the client wasnt able to communicate with the core since it was closed.
Requin, you can get that if you doubleclick instead of click, and if your box is OC'd too much-- and in your case, you had a client still running because you did not kill winFAH.exe also, so two clients got running when you started another one-- they fought over your WU data. To close the folding and keep your work, do this:
Right click on the red cog by the clock.
Choose quit.
This tells the client that you WANT it to stop folding. The Client, in this case winFAH.exe, will shut down the core for you, and then save the work, and THEN shut itself down. folding is TWO processes, client is master process and core is what calcs WUs. Different WUs need different calc cores. Client is master controller and co-ordinator. When you kill the core, you leave the master control porcess for folding sitting there in a very unstable state. You MIGHT have lost your WU data right as you killed the core, but probably not. Getting two clients running with same Work directory WILL cause a fight over the .cp file that will get you a WU restart. .cp file ends up missing. Next time you start just one client, it says to itself (essentially) in its coded way: "hmmm... no .cp file, lets make a new one for holding completed folding." Then it restarts WU from scratch.
SUMMARY:
That is what happened, as easily as I can explain it(and I left some details out in order not to write a book). You got a data file fight, two clients wanted the .cp file at once, and XP will NOT let two same-name processes access a file registered -- checked out and reserved by XP -- to first running process of same name happen. Then you got a client full recover, client reworked things so it could run, and result was a new .cp file with nothing in it until client saved work. Client, when you ran it aftwer the two tried to run at once. did a WU reset.
John D.