• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

F@H - Pause?

beatle

Diamond Member
Ok, I went to shut off the service, as I wanted to test prime on this computer. Stopping or pausing the service does not keep FAH from crunching, so I blew away the processes in task manager. This was apparently not a good idea, as it looks like I lost the protein I was working on. Is there an easy way to stop FAH? Is there a way to recover that WU? 🙂
 
You made me curious, so I ran the firedaemon service manager, selected f@H then service -> stop. It did

then I ran the firedaemon service manager again, selected f@H then service -> start. It did. The folding began at the proper place and nothing was lost.

I really don't know how you tried to stop the service, but I suspect you used the windows service manager instead of the firedaemon service manager.

-Sid

(of course, all this assumes you used firedaemon to install F@H as a service)
 
you might not need to pause the service while running Prime95. I have seen ppl done that before and they reported no problem. Other choice just stop the service at once I mean use Ctrl+Atl+Del, then restart the service manually.

In case of losing WU, I don't think you can recover the old WU after new WU been download to folder.
 
Sid, I'm not running FireDaemon anymore. See this thread to see why.

Yai, P95 will only get 10-20% of my cpu cycles when the F@H core is running. I first killed the process in task manager, but then saw that F@H had started up again after a few min, so I stopped the F@H service from the service manager and then killed the process again. This ensured F@H didn't start up again while I was testing my system, but apparently it also ensured that I wasn't allowed to finish my WU.
 
Did you kill the FahCore_xx process or the Fah3console process? Not that that would make a difference, and it should stop when told to through the firedaemon service manager, so I'm not sure what's going on here. Sorry. 🙁
 
I ended up killing both. I think I killed the core first and saw that cpu usage was still @ 100%, so I killed the console also.
 
Back
Top