Folding Forum

BuddhaChu wrote:The correct way to stop the CPU client not installed as a service is:

Code: Select all

taskkill /F /IM Folding@home-Win32-x86.exe

Folding@home-Win32-x86.exe is the controlling program that starts the cores running. Stop that and you stop the cores. You don't really need to use the /T switch to stop the child processes (the cores), but it can't hurt I guess.

yes ofcourse, there is no need to kill the child process' aswell.

Not trying to jump on the "Why?" bandwagon, because options are a great thing. But, wouldn't alacrityPC do the same thing?
(Spam filters understandably wouldn't let me post a link because I'm new. I swear this isn't spam or malicious.)

For the sake of completeness:

Anyone using a Mac - check out InCrease from www.calxalot.net. It will pause Folding when an application on the user-constructed list is opened. Note that it doesn't shut Folding off, so your FahCore(s) will still hang on to the RAM they were using before the pause.

I don't use this feature of InCrease, but several friends have found it useful when doing demanding video processing tasks.

ashrack wrote:

BuddhaChu wrote:The correct way to stop the CPU client not installed as a service is:

Code: Select all

taskkill /F /IM Folding@home-Win32-x86.exe

Folding@home-Win32-x86.exe is the controlling program that starts the cores running. Stop that and you stop the cores. You don't really need to use the /T switch to stop the child processes (the cores), but it can't hurt I guess.

yes ofcourse, there is no need to kill the child process' aswell.

Where did you get this from? Afaik the only correct way to kill a windows-win32 is with a wm_close command, since this triggers the only proper exit for the client ( as in it signals the core that the client is exiting! ),

And again afaik this command is not how taskkill ends a process? And forcefully closing child processes in this manner could hurt checkpointing? Since the exiting procedure isn't called the client could corrupt open files?

Edit: just to clarify I been away some time there might have been some changes I am not aware off so the above is a question as much as a statement.

Also, the need for such a feature is evident with gpu folding, the faster cards can meet their deadlines so easy that you can game while processing a wu ( meaning it should pause automaticly and then continue when the application is closed ) without risking having wu's time out. And folding will stick to more people when something like this is implemented.

MtM wrote: Also, the need for such a feature is evident with gpu folding, the faster cards can meet their deadlines so easy that you can game while processing a wu ( meaning it should pause automaticly and then continue when the application is closed ) without risking having wu's time out. And folding will stick to more people when something like this is implemented.

couldn't agree with you more.

Would be better if you adressed the more important part of my post as well seeing you're advertising an application which does things which I believe are not conform recommodations made by PG?

MtM
there was no interest in the program so it is made to just suite my needs. I use FAH SMP and it sends the NET STOP FAH command when entering a game and after exiting a game it issues the NET START FAH command. It's been like this since I started this thread and no packets were lost.

Ahh sorry there ashrack, the question wasn't even ment for you but BuddaChu

As the quote contradicts itself, one should not force child process to close as it CAN hurt a lot ( checkpoint corruption ).

But it was you who even said the correct thing, sorry for wrongly addressing you.