Want to stop gpu tasks when watching a video or playing a game?

Try this:

-->Upgrade your Boinc client into latest Version (6.10.19-6.10.24) here: http://boinc.berkeley.edu/download_all.php

-->Create a custom cc_config.xml and wrote inside:

<cc_config>
<options>
<exclusive_gpu_app>mplayer.exe</exclusive_gpu_app>
<exclusive_gpu_app>mpc-hc.exe</exclusive_gpu_app>
<exclusive_gpu_app>iw4sp.exe</exclusive_gpu_app>
<exclusive_gpu_app>SHIFT.exe</exclusive_gpu_app>
<exclusive_gpu_app>GRID.exe</exclusive_gpu_app>
<exclusive_gpu_app>DIRT2.exe</exclusive_gpu_app>
<exclusive_gpu_app>daorigins.exe</exclusive_gpu_app>
<exclusive_gpu_app>Diablo II.exe</exclusive_gpu_app>
<exclusive_gpu_app>halo.exe</exclusive_gpu_app>
</options>
</cc_config> 

this is just an example!

Now when one of the exclusive applications runs, gpu will be free for it! CPU still crunches in low priority ;)

---

Firegate_13 Was Here!
BeWare!
Patras Wireless Metropolitan NetWork

very nice. I've been annoyed with Collatz failing if I forget to stop the GPU when I game. This is going to be sweet

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

very nice. I've been annoyed with Collatz failing if I forget to stop the GPU when I game. This is going to be sweet

I've had problems with the Collatz cruncher not stopping when the Boinc Manager tells it to, leading to multiple crunchers working on the same work unit, leading to all sorts of nastiness. So I've stopped crunching for Collatz. I don't think these settings will help with Collatz as it is the BM that tells the client to start/stop based on these settings.

These settings work nicely with Seti though, as it is a better behaved cruncher.

---

this is a CC_config so it should work with any BOINC project.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

this is a CC_config so it should work with any BOINC project.

Yes, but what I'm saying is that it isn't the project cruncher that reads and pays attention to that, it is the manager, and if the project cruncher (like collatz) doesn't pay attention to the manager it doesn't really matter what you put in there :p

---

I don't think these settings will help with Collatz as it is the BM that tells the client to start/stop based on these settings.

You're giving way too much credit to BOINC Manager. It's merely a GUI. Yes, with some advanced options, but it won't order the client to do anything. The CC in cc_config.xml stands for core client. So you're 'programming' the client with extra options, not the GUI.

---

But still, if the application doesn't obey the client, the option is useless.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

I don't think these settings will help with Collatz as it is the BM that tells the client to start/stop based on these settings.

You're giving way too much credit to BOINC Manager. It's merely a GUI. Yes, with some advanced options, but it won't order the client to do anything. The CC in cc_config.xml stands for core client. So you're 'programming' the client with extra options, not the GUI.

While "boinc.exe" is called the "client", it doesn't actually do any of the work other than spawning the actual project cruncher and uploading/downloading, so I consider it to be the scheduler portion of the manager, it just runs in a seperate process.

Potaytoh, potahtoh

your milage may vary :p

---

you do understand that the CC_config works for seti once its put into the project folder. Likewise for other projects. Since they all work with BOINC there shouldn't be any difference in the cc_config working.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

you do understand that the CC_config works for seti once its put into the project folder. Likewise for other projects. Since they all work with BOINC there shouldn't be any difference in the cc_config working.

Yes, but some projects are NOT well behaved.

---

BOINC WIKI

While "boinc.exe" is called the "client", it doesn't actually do any of the work other than spawning the actual project cruncher and uploading/downloading, so I consider it to be the scheduler portion of the manager, it just runs in a seperate process.

Wow... you do give too much credit to BOINC Manager. Here's a little something for you.

The <exclusive_app> and <exclusive_gpu_app> options run from the app.cpp code, with use of the log_flags.cpp code, both part of the client code. Not Manager code. Not clientGUI code. Go on, hover your mouse over the blue words and look at the link. See that "client" in there?

Now compare it to the ClientGUI portion of the source code. See how it's called clientgui? That's the Manager.

BOINC Manager as it is, is nothing more than a glorified GUI that allows you to easily give small commands to the client and control parts of it. You can do much the same with the Boinccmd command. (Is that then also the BOINC Manager? Or the BOINC Commander?)

Any scheduling is done by the client. As you can see here, Scheduler_op.cpp lives in the client section of the source code.

It's really not that difficult to follow. Although you can ask John there, if it is easy to make so it all works. ;-)

---

BOINC.exe is the BOINC daemon. It does CPU scheduling, work fetch, and application control.
BOINCMgr.exe is the BOINC Manager. It is a GUI that can send user initiated commands to BOINC daemons on different computers.
BOINCtray.exe is the mouse / keyboard activity detector.

---

BOINC WIKI

BOINC.exe is the BOINC daemon. It does CPU scheduling, work fetch, and application control.
BOINCMgr.exe is the BOINC Manager. It is a GUI that can send user initiated commands to BOINC daemons on different computers.
BOINCtray.exe is the mouse / keyboard activity detector.

And further:
Boinccmd.exe is the command line tool to give extra commands to Boinc.exe
Boinc.scr is the Windows screen saver code.
Boincscr.exe is the new BOINC screen saver executable. (This as opposed to the graphics applications supplied by projects, the Boinc screen saver can be run independently of any project's graphics).
Boincsvcctrl.exe is the BOINC Service controller, in case you installed it as a service.

---

Ageless wrote:
blah blah

Wow. You seem to be stuck on a pedantic nitpicking binge about semantics. Yes, each individual program on your computer has a different name. Yes, I refer to the boinc programs installed on your computer collectively as "client" vs all the individual programs at Berkeley as the "server".

What is your point about going on and on about whether the manager is the GUI or not? Did you even read the original post? Do you know what this thread is about?

At least I answered the original post instead of trolling like you.

I'm glad this board has an ignore feature.

---

and it worked fine with collatz while i was playing left 4 dead. So yes it works on other projects. It appears to leave the WU in memory but doesn't appear to be working it while there. I only played for 20 minutes. The WU time continued to run but it didn't error out on any work

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

What is your point about going on and on about whether the manager is the GUI or not? Did you even read the original post? Do you know what this thread is about?

Oh, I know what it is about.
You know who got everyone that function? No, really... guess.

All I was trying to do was teach you what BOINC's parts are. Since you try to help people, but are ignorant on what does what. Too bad. Your loss.

I'm glad this board has an ignore feature.

Me too. You're officially pl0nked.

---