It says waiting to start. Ill take a screenshot.

---

GPU Still wont start.

Have you modified your app_info.xml to run multiple GPU tasks at once? Or have you created a app_config.xml so to run multiple GPU tasks at once?

Claggy

I tried setting the GPU count to 2.



Uploaded with ImageShack.us[/img]

---

I tried setting the GPU count to 2.



Uploaded with ImageShack.us[/img]

What <count>?</count> value exactly did you put in your app_info.xml? or what <gpu_usage>?</gpu_usage> value exactly did you put in your app_config.xml?

Claggy

I tried setting the GPU count to 2.



Uploaded with ImageShack.us[/img]

What <count>?</count> value exactly did you put in your app_info.xml? or what <gpu_usage>?</gpu_usage> value exactly did you put in your app_config.xml?

Claggy

With a GPU count of 2, you are telling BOINC to use 2 GPU's to process the work.

You really want the count set to either 0.5 for 2 at a time or 0.33 for 3 at a time.

---

I tried setting the GPU count to 2.



Uploaded with ImageShack.us[/img]

What <count>?</count> value exactly did you put in your app_info.xml? or what <gpu_usage>?</gpu_usage> value exactly did you put in your app_config.xml?

Claggy

With a GPU count of 2, you are telling BOINC to use 2 GPU's to process the work.

You really want the count set to either 0.5 for 2 at a time or 0.33 for 3 at a time.

And of cause, his picture says 6 GPUs required per Wu, which isn't what he said.

Claggy

I tried setting the GPU count to 2.



Uploaded with ImageShack.us[/img]

This shows you are running 8 CPU cores for 8 CPU work units.

Each GPU application requires some CPU time and you are giving it none.

Set your BOINC computing preferences to use 50% of your CPU and see what happens.

You may be able to set the CPU to 75%, but try 50% first.

<?xml version="1.0"?>
-<app_info>-<app><name>setiathome_v7</name></app>-<file_info><name>AKv8c_Bb_r1846_winx86_AVXx.exe</name><executable/></file_info>-<file_info><name>libfftw3f-3.dll</name><executable/></file_info>-<file_info><name>AKv8c_Bb_r1846_winx86_AVXx.txt</name></file_info>+<app_version>----<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name><open_name>mb_cmdline.txt</open_name></file_ref></app_version>-<app><name>setiathome_enhanced</name></app>-<file_info><name>AKv8c_Bb_r1846_winx86_AVXx.exe</name><executable/></file_info>-<file_info><name>libfftw3f-3.dll</name><executable/></file_info>-<file_info><name>AKv8c_Bb_r1846_winx86_AVXx.txt</name></file_info>-<app_version><app_name>setiathome_enhanced</app_name><version_num>603</version_num><platform>windows_intelx86</platform>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name><open_name>mb_cmdline.txt</open_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>603</version_num><platform>windows_x86_64</platform>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name><open_name>mb_cmdline.txt</open_name></file_ref></app_version>-<app><name>astropulse_v6</name></app>-<file_info><name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</name><executable/></file_info>-<file_info><name>libfftw3f-3.dll</name><executable/></file_info>-<file_info><name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name></file_info>-<file_info><name>AstroPulse_Kernels_r1843.cl</name></file_info>-<app_version><app_name>astropulse_v6</app_name><version_num>604</version_num><platform>windows_intelx86</platform><avg_ncpus>0.04</avg_ncpus><max_ncpus>0.2</max_ncpus><plan_class>cuda_opencl_100</plan_class><cmdline/>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref>-<file_ref><file_name>AstroPulse_Kernels_r1843.cl</file_name></file_ref></app_version>-<app_version><app_name>astropulse_v6</app_name><version_num>604</version_num><platform>windows_intelx86</platform><avg_ncpus>0.04</avg_ncpus><max_ncpus>0.2</max_ncpus><plan_class>opencl_nvidia_100</plan_class><cmdline/>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref>-<file_ref><file_name>AstroPulse_Kernels_r1843.cl</file_name></file_ref></app_version>-<app_version><app_name>astropulse_v6</app_name><version_num>604</version_num><platform>windows_x86_64</platform><avg_ncpus>0.04</avg_ncpus><max_ncpus>0.2</max_ncpus><plan_class>cuda_opencl_100</plan_class><cmdline/>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref>-<file_ref><file_name>AstroPulse_Kernels_r1843.cl</file_name></file_ref></app_version>-<app_version><app_name>astropulse_v6</app_name><version_num>604</version_num><platform>windows_x86_64</platform><avg_ncpus>0.04</avg_ncpus><max_ncpus>0.2</max_ncpus><plan_class>opencl_nvidia_100</plan_class><cmdline/>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref>-<file_ref><file_name>AstroPulse_Kernels_r1843.cl</file_name></file_ref></app_version>-<app><name>astropulse_v6</name></app>-<file_info><name>AP6_win_x86_SSE_CPU_r1797.exe</name><executable/></file_info>-<file_info><name>libfftw3f-3.dll</name><executable/></file_info>-<file_info><name>ap_cmdline_win_x86_SSE_CPU.txt</name></file_info>-<app_version><app_name>astropulse_v6</app_name><version_num>601</version_num><platform>windows_intelx86</platform><cmdline/>-<file_ref><file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref></app_version>-<app_version><app_name>astropulse_v6</app_name><version_num>601</version_num><platform>windows_x86_64</platform><cmdline/>-<file_ref><file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name><main_program/></file_ref>-<file_ref><file_name>libfftw3f-3.dll</file_name></file_ref>-<file_ref><file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name><open_name>ap_cmdline.txt</open_name></file_ref></app_version>-<app><name>setiathome_v7</name></app>-<file_info><name>Lunatics_x41zc_win32_cuda50.exe</name><executable/></file_info>-<file_info><name>cudart32_50_35.dll</name><executable/></file_info>-<file_info><name>cufft32_50_35.dll</name><executable/></file_info>-<file_info><name>mbcuda.cfg</name></file_info>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_intelx86</platform><plan_class>cuda50</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_intelx86</platform><plan_class>cuda22</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type>ccc </coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_intelx86</platform><plan_class>cuda23</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_intelx86</platform><plan_class>cuda32</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_intelx86</platform><plan_class>cuda42</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform><plan_class>cuda50</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform><plan_class>cuda22</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform><plan_class>cuda23</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform><plan_class>cuda32</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_v7</app_name><version_num>700</version_num><platform>windows_x86_64</platform><plan_class>cuda42</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app><name>setiathome_enhanced</name></app>-<file_info><name>Lunatics_x41zc_win32_cuda50.exe</name><executable/></file_info>-<file_info><name>cudart32_50_35.dll</name><executable/></file_info>-<file_info><name>cufft32_50_35.dll</name><executable/></file_info>-<file_info><name>mbcuda.cfg</name></file_info>-<app_version><app_name>setiathome_enhanced</app_name><version_num>610</version_num><platform>windows_intelx86</platform><plan_class>cuda_fermi</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>609</version_num><platform>windows_intelx86</platform><plan_class>cuda23</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>608</version_num><platform>windows_intelx86</platform><plan_class>cuda</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>610</version_num><platform>windows_x86_64</platform><plan_class>cuda_fermi</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>609</version_num><platform>windows_x86_64</platform><plan_class>cuda23</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version>-<app_version><app_name>setiathome_enhanced</app_name><version_num>608</version_num><platform>windows_x86_64</platform><plan_class>cuda</plan_class><avg_ncpus>0.040000</avg_ncpus><max_ncpus>0.040000</max_ncpus>-<coproc><type>CUDA</type><count>1</count></coproc>-<file_ref><file_name>Lunatics_x41zc_win32_cuda50.exe</file_name><main_program/></file_ref>-<file_ref><file_name>cudart32_50_35.dll</file_name></file_ref>-<file_ref><file_name>cufft32_50_35.dll</file_name></file_ref>-<file_ref><file_name>mbcuda.cfg</file_name></file_ref></app_version></app_info>


I uninstalled and reinstalled, now both GPUs are working. How can I run multiples instances on each GPU?

---

You have:
...
<coproc><type>CUDA</type>
<count>1</count>
...


set count to 0.5 to run 2 instances or 0.33 to run 3 instances.

This would run 2 instances per GPU:
...
<coproc><type>CUDA</type>
<count>0.5</count>
...

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

I uninstalled and reinstalled, now both GPUs are working. How can I run multiples instances on each GPU?

The first line:

<?xml version="1.0"?>

suggests that you have edited the file with something other than Notepad or comparable ascii editor. Did you use a xml editor? That line should not be in app_info.xml. I would run the install one more time to get a clean app_info.xml file. Then, edit with notepad and change the count values from 1
to the fraction of the gpu that you want each task to use. For 2 at a time per gpu, use .5 to give the task half a gpu. Use .33 for 3 at a time per gpu.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I uninstalled and reinstalled, now both GPUs are working. How can I run multiples instances on each GPU?

The first line:

<?xml version="1.0"?>

suggests that you have edited the file with something other than Notepad or comparable ascii editor. Did you use a xml editor? That line should not be in app_info.xml. I would run the install one more time to get a clean app_info.xml file. Then, edit with notepad and change the count values from 1
to the fraction of the gpu that you want each task to use. For 2 at a time per gpu, use .5 to give the task half a gpu. Use .33 for 3 at a time per gpu.

The file was created by the optimized installed.

---

I uninstalled and reinstalled, now both GPUs are working. How can I run multiples instances on each GPU?

The first line:

<?xml version="1.0"?>

suggests that you have edited the file with something other than Notepad or comparable ascii editor. Did you use a xml editor? That line should not be in app_info.xml. I would run the install one more time to get a clean app_info.xml file. Then, edit with notepad and change the count values from 1
to the fraction of the gpu that you want each task to use. For 2 at a time per gpu, use .5 to give the task half a gpu. Use .33 for 3 at a time per gpu.

The file was created by the optimized installed.

Of cause it was,

But what program did you use to open it to post to this thread? Only Notepad should be used as the file is a pure text file.

Claggy

I uninstalled and reinstalled, now both GPUs are working. How can I run multiples instances on each GPU?

The first line:

<?xml version="1.0"?>

suggests that you have edited the file with something other than Notepad or comparable ascii editor. Did you use a xml editor? That line should not be in app_info.xml. I would run the install one more time to get a clean app_info.xml file. Then, edit with notepad and change the count values from 1
to the fraction of the gpu that you want each task to use. For 2 at a time per gpu, use .5 to give the task half a gpu. Use .33 for 3 at a time per gpu.

The file was created by the optimized installed.

Of cause it was,

But what program did you use to open it to post to this thread? Only Notepad should be used as the file is a pure text file.

Claggy

Even the very common problem of double-clicking on the file in Windows Explorer, and having it open automatically in Internet Explorer - which is safe, if confusing, because IE is a read-only view - doesn't display that <?xml version="1.0"?> at the top (even if it does show the tree expansion marks, and allow then to be copied - they are also present in this case)

<snip>
Even the very common problem of double-clicking on the file in Windows Explorer, and having it open automatically in Internet Explorer - which is safe, if confusing, because IE is a read-only view - doesn't display that <?xml version="1.0"?> at the top (even if it does show the tree expansion marks, and allow then to be copied - they are also present in this case)

So, in this case, is the file buggered or not?

The problem is that (according to the screen shots) he wants 6 GPUs for each GPU WU, and he hasn't got that many, so --- Surprise! --- they don't start. BOINC will look for the 6 GPUs forever without finding them.

User has to find out where the 6 came from, and set it to 1 (or 0.5 or 0.33) to get the WUs to start.

My guess would be that since he has 2 670s and was thinking about 3 WU/GPU, and he got the number 6 from that (2x3=6). So he has to fix that in his app_info.xml, I would assume.

---

<snip>
Even the very common problem of double-clicking on the file in Windows Explorer, and having it open automatically in Internet Explorer - which is safe, if confusing, because IE is a read-only view - doesn't display that <?xml version="1.0"?> at the top (even if it does show the tree expansion marks, and allow then to be copied - they are also present in this case)

So, in this case, is the file buggered or not?

It's hard to read in the current display format.

It depends very much whether that is an accurate transcription of the true content of the file (in which case it is most certainly buggered, because of those tree controls), or whether those are display artefacts from whatever tool he used to render the contents visible (in which case, the real contents might be OK).

A little bit more narrative description of what he did, and what programs he used, wouldn't go amiss.

The problem is that (according to the screen shots) he wants 6 GPUs for each GPU WU, and he hasn't got that many, so --- Surprise! --- they don't start. BOINC will look for the 6 GPUs forever without finding them.

User has to find out where the 6 came from, and set it to 1 (or 0.5 or 0.33) to get the WUs to start.

We can at least see <count>1</count> throughout the posted app_info file, which is much newer than the screenshots. So that much, at least, has changed for the better since he first posted.

<snip>
A little bit more narrative description of what he did, and what programs he used, wouldn't go amiss.

Oh heaven forbid that a poster with a problem come forward
with the information to fix his problem without 20 Questions
being played. Where's the fun in that?

What does AP and MB mean?

---

What does AP and MB mean?

AP= Astropulse
MB= Multibeam

---