I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%.
Normal ?

Update : It wil run on two cores but only if no other project is running.

Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC.

I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%.
Normal ?

Update : It wil run on two cores but only if no other project is running.

Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC.

You would need to use an app_info file to specify that you only want to use 2 cores max.

---

And where to find ?

I'm a N00B programming.

I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%.
Normal ?

Update : It wil run on two cores but only if no other project is running.

Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC.

Okay let's start at the beginning...by default Boinc will NOT run on only two cores and some other project run on the other two cores when you are running multiple projects on a quad core pc. But BY DEFAULT if you set Boinc to only use 50% of your cpu's it does respect your 50% running by running using all 4 cores for 50% of the time, so it DOES use only 50% of the pc's total cpu usage, just not like you thought it might.

MOST people that use an app_info file get it from someone else and then modify it so it works for them. In this case I do not use any modification files here so I am going to step back and let Arkayn take the reins, as I have no clue about this.

I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%.
Normal ?

Update : It wil run on two cores but only if no other project is running.

Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC.

Okay let's start at the beginning...by default Boinc will NOT run on only two cores and some other project run on the other two cores when you are running multiple projects on a quad core pc. But BY DEFAULT if you set Boinc to only use 50% of your cpu's it does respect your 50% running by running using all 4 cores for 50% of the time, so it DOES use only 50% of the pc's total cpu usage, just not like you thought it might.

MOST people that use an app_info file get it from someone else and then modify it so it works for them. In this case I do not use any modification files here so I am going to step back and let Arkayn take the reins, as I have no clue about this.

And what about "On multiprocessors, use at most 2 processors" ?
It seems to me that if you use the above on a certain project it should only use those 2 cores and no more. And thus leaving 2 cores to use somewhere else.

I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%.
Normal ?

Update : It wil run on two cores but only if no other project is running.

Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC.

Okay let's start at the beginning...by default Boinc will NOT run on only two cores and some other project run on the other two cores when you are running multiple projects on a quad core pc. But BY DEFAULT if you set Boinc to only use 50% of your cpu's it does respect your 50% running by running using all 4 cores for 50% of the time, so it DOES use only 50% of the pc's total cpu usage, just not like you thought it might.

MOST people that use an app_info file get it from someone else and then modify it so it works for them. In this case I do not use any modification files here so I am going to step back and let Arkayn take the reins, as I have no clue about this.

And what about "On multiprocessors, use at most 2 processors" ?
It seems to me that if you use the above on a certain project it should only use those 2 cores and no more. And thus leaving 2 cores to use somewhere else.

But it is NOT a by project setting, yes it will work, but only for the pc in general. Meaning if you set a quad core to only use 2 cores in Boinc sure you have 2 unused cores for gaming, emailing, photo-shopping whatever, but you CANNOT then use those other two cores for another Boinc project!

And where to find ?

I'm a N00B programming.

You would need to create the file in notepad and paste in this info.

<app_info>

<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>82</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>cuda</plan_class>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_0.82_windows_intelx86__cuda_opencl.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app><!-- CPU app for N-Body 0.80 mt 32bit -->
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.80_windows_intelx86__mt.exe</name>
<executable/>
</file_info>
<file_info>
<name>libgomp_nbody_0.80.dll</name>
<executable/>
</file_info>
<file_info>
<name>pthreadGC2_nbody_0.80.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>80</version_num>
<plan_class>mt</plan_class>
<avg_ncpus>2</avg_ncpus>
<max_ncpus>2</max_ncpus>
<cmdline>--nthreads=2</cmdline>
<file_ref>
<file_name>milkyway_nbody_0.80_windows_intelx86__mt.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libgomp_nbody_0.80.dll</file_name>
<open_name>libgomp-1.dll</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>pthreadGC2_nbody_0.80.dll</file_name>
<open_name>pthreadGC2.dll</open_name>
</file_ref>

</app_info>

Save the name of the file as app_info.xml, make certain that you select all files as the save as type.

Then you will need to shut BOINC down(make certain that you select shut down connected client from the advance menu) and copy the app_info file into
Documents and Settings\All Users\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway

Then you can restart the client.

I added the OpenCL app since you also have some of that on board as well right now.

---

Thanks !

Can you give me also the needed lines for adding GPU-crunching for if I want to use cpu and gpu to do MW@H ?

And what if I want my gpu's to crunch on SETI and Milkyway simultaniously ?
Are gpu-crunching M@H at the moment but would like to start S@H again also.

Is it possible you have forgotten a </app_version> at the end ?
I'm getting a "parse error in app_info.xml; check XML syntax".

And I saw in the app you already added the lines for gpu ?

It looks as if cpu wu's will not download if gpu is running and also I don't get anymore gpu wu's while trying to download cpu wu's.

And what if I want my gpu's to crunch on SETI and Milkyway simultaniously ?

This is a Boinc thing and I am not sure you can MAKE both crunch 24/7/365 but you can average out to that. Boinc manages itself thru 'debt management' meaning if MW is out of work it will crunch Seti units, in your case, and the Boinc will track that it 'owes' MW crunching time. Over the long run this works out okay, but that long run can be 1 week, 1 month or even longer depending on how long one project does not have any, or enough, units to keep your pc busy.

Looks like I did, it should be just before the </app_info>

---