Well I completed the instruction(properly I think)....
and recieved this error:
Seti@home: Notice from BOINC
File referenced in app_info.xml does not exist: AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe

I went ahead and edited the r1339 to read r1363 in the app_info.xml file.

Unfortunatly about the same time I was making all these changes looks like a server took it on the chin. My system hasn't communitcated with the server since I made the original change...Is it possible something we changed messed up Boinc's ability to communicate with the server? Just poor timing?
http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-250/gigabitethernet2_3&ranges=d%3Aw&view=Octets

Sorry for the typo, it was the end of a long day, yes just change r1339 to r1363.

Just poor timing, the server are having issues since maintenance, i've managed to report most of my finished Wu's (with NNT set), but can't get through to the server when asking for work,

Claggy

Well I completed the instruction(properly I think)....
and recieved this error:
Seti@home: Notice from BOINC
File referenced in app_info.xml does not exist: AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe

I went ahead and edited the r1339 to read r1363 in the app_info.xml file.

Unfortunatly about the same time I was making all these changes looks like a server took it on the chin. My system hasn't communitcated with the server since I made the original change...Is it possible something we changed messed up Boinc's ability to communicate with the server? Just poor timing?
http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-250/gigabitethernet2_3&ranges=d%3Aw&view=Octets

---

1 quick note...I will be getting the neccesary cables to make the 5870 work. so in a few days I will install it unless the consensus is otherwise.

Opp and I just went over 700,000 credits :)

---

Well regardless I went ahead and followed the instructions...
Seti@home: Notice from BOINC
File referenced in app_info.xml does not exist: AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe


Please advise.
Should I edit the r1339 to read r1363 in the app_info.xml file?



I think it would have gotten there with the 8800gts but my system just went over an average daily credit crunched of 10,000 for the first time ever :) WEEEEEEEEEEEEEEEEEEEE

OH and I bumped the 8800 Ultra up to 666Mhz from 612Mhz

---

So I'm short 1 pcie power cable. So I can't install the the 5870....which is probably fine as I ran out of ATI work units.

Would the above instruction still work with the 5770?

---

I forgot to add the flops value to the ATI MB app, here's the app_info with it added, you should try and finish all your ATI MB tasks before you use the app_info with the flops values entered, otherwise existing ATI MB Wu's might error with Maximum Time exceeded:

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</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>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-unroll 10 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-unroll 10 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>ap_6.01r557_SSE2_331_AVX.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r390.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<flops>70e09</flops>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<flops>70e09</flops>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>

Claggy

O.K, If you go to this thread and download the r1363 AP apps, and extract them into a folder with 7zip,
You'll need the AP6_win_x86_SSE2_OpenCL_ATI_r1363.exe the AP6_win_x86_SSE2_OpenCL_ATI.pdb the AstroPulse_Kernels_r1363.cl and the libfftw3f-3.dll files, just copy them across into your setiathome project directory,
then make your self a new app_info.xml with Notepad with the following in it (make sure you Save As, then select Save as Type: All files (*.*) , encoding set to ANSI, and the filename is app_info.xml and not app_info.xml.txt)

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</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>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-unroll 10 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-unroll 10 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1339.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>ap_6.01r557_SSE2_331_AVX.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r390.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>

The changes i've made are replace the ATI r555 app with the ATI r1363 app, remove the obsolete sections for Astropulse_v505, removed the -instances_per_device 1 for the r1363 AP app (It's not needed on this app),
and increased the -unroll value to 10 (this will better load the HD5870)

Claggy

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</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>AK_v8b2_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<platform>windows_x86_64</platform>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>ap_6.01r557_SSE2_331_AVX.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<cmdline>-v505</cmdline>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<cmdline>-v505</cmdline>
<file_ref>
<file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r390.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB6_win_x86_SSE3_OpenCL_ATi_HD5_r390.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r390.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</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_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>


I will change to the 8800ultra
(and despite my earlier statments) If you all really think the 5870 is bettter used then sold then I will install it. Please make the neccesary changes accordingly.

---

BilBg: "'Use NVIDIA GPU' no
(this 'Use' means in fact: 'Get tasks for NVIDIA GPU' no
It will not stop your NVIDIA GPU from computing tasks you already have.)"

This was where I was confused since in the BOINC manager, "Use GPU" means allow the GPU to run and in this case it means allowed tasks to be fetched for that type of device. Misinterpreting the meaning of that setting, the only way I knew how to stop fetching a task for a particular device was ripping out that portion of the app_info file, a virtual pull of the device in a sense.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

Which of your FOUR computers are we talking about?

He is talking about:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6738595

6738595: The one which reports as having an Nvidia card. Reports as having 605 tasks "in progress", but worryingly 211 tasks are shown as having ended in errors. These errors appear to have been fairly recent, and so will affect that cruncher's ability to get new work.

All of them (errors) are from 20 Aug 2012, probably a reboot cured the issue.
The 'Aborted by user' are old (11 Aug 2012 - before starting this thread)

6204850: The one that reports having an ATI card. Reports 77 in progress, but has 15 errors, all aborted by user - this can affect a cruncher's ability to get new work.

The 'Aborted by user' are very old (28 Jul 2012)
The effect of errors on 'ability to get new work' lasts for a day.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I haven't downloaded and installed SIV as thats some seriously strong medicine I probably shouldn't be playing with.

SIV doesn't need installing, you just download and extract it to a folder, then run it from there.

If Snowmain simply sticks <flops>80e9</flops> into the MB ATI portion of his app_info (I put it right before the <coproc> line in both ATI sections) he should get a bucket load of MB ATI work units. The 80e9 value is a SWAG on my part, if someone is already running an HD 5770 and actually has an average processing rate for it please share.

Please keep in mind that I am not an IT professional and need detailed instruction.

Just post your app_info (open it with Notepad), and one of use will mod it for you, if you want i can update it with the latest r1316/r1363 AP app too.

Its a little to late tonight for me to pull the rig appart and I already have plans for tomorrow night. So the rig will get another 48 hours as it stands. Stoped over at my buddies place today for that 8800gts....Only he gave me an 8800ultra instead and an ATI HD 5870! So if the situation continues to improve I can run these cards for a substantial increase in performance. If not the 5770 and the 5870 will get me a good chunck of the way to the 200$ neccesary for a brand new GTX480.

Upgrade to both of those if you can, the HD5870 will do Astropulse at something like the speed of my GTX460, OpenCL Multibeam performance will be no where near the GTX460's Cuda performance through,
so best to run the apps that are particuly suited to a device, ie the x41g Cuda32 app on the 8800GTS/8800ultra, (If you were to run the Nvidia OpenCL AP app on those, you'd find they take +4hrs per Wu),
and ATI OpenCL AP on the HD5770/HD5870 (~1hr30mins on the HD5770, ~45mins on the HD5870, and about 10 minutes faster on the later revision apps)

Claggy

He could just send me his appinfo and i would adjust it for him if he dont feel comfortable to do it himself.

Both Claggy and me knowing fully well how those apps work.
We have tested this app back and forth.

---

With each crime and every kindness we birth our future.

Sorry if I come off as angry, just frustrated that in this and my thread the general response was do nothing it'll get better or that it's a run of bad work units, give it more time.

The problem is that for you and for Snowmain (and for some other people) the server do not compute/update this:
SETI@home Enhanced (anonymous platform, ATI GPU)
- Number of tasks completed 0

Yes, this is some server bug and have to be addressed in the SETI lab.
You/Snowmain can just wait (months?) for it to be found/fixed.

But he "Just want the ATI to work" now.
So all the advices given (including your <flops>80e9</flops>) was aimed at:
"How, NOW, to workaround server/BOINC glitches"

PS: Thanks for the info on SIV. I'm not using the auto retry feature ...

The 'Auto Retry' of SIV is safe to use.

The author of SIV implemented this at first for himself.
SIV does not do some black magic (it does not 'hack' BOINC).
SIV calls boinccmd.exe with appropriate switches to control BOINC
(which is very standard/approved way to control BOINC)

It's not "some seriously strong medicine" as Snowmain thinks.
(Snowmain: "I haven't downloaded and installed SIV as thats some seriously strong medicine I probably shouldn't be playing with."
BilBg: "2) Use SIV (you have the link (Message 1272722)) - no install needed:"
)


@Snowmain:
Do you want instructions where (app_info.xml - in 2 'proper' places/lines) and how (Notepad) to add <flops>70e9</flops> ?
(value corrected according to:
"69.76e09 is what i got from my HD5770 when it was running MB."
Claggy
)

I wasn't interested in shutting down the work unit fetcher for my nvidia card.

I wonder why?

Claggy: "Snowmain has 5 days of Nvidia work, he can survive at least 3 days without asking for any Nvidia work, at which point he can re-enable Nvidia GPU work fetch."
tbret: "So, yes, telling BOINC you don't *want* anymore NVIDIA or CPU tasks really does improve your odds of getting ATI tasks in an almost accidental way."

BilBg: "'Use NVIDIA GPU' no
(this 'Use' means in fact: 'Get tasks for NVIDIA GPU' no
It will not stop your NVIDIA GPU from computing tasks you already have.)"

Claggy: "You don't understand, By deselecting 'Use Nvidia GPU' in your Setiathome Preferences doesn't stop Nvidia GPU computing"
Snowmain: "I understood the motivation behind this advise. I just don't think it will work."

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Which of your FOUR computers are we talking about?

6738595: The one which reports as having an Nvidia card. Reports as having 605 tasks "in progress", but worryingly 211 tasks are shown as having ended in errors. These errors appear to have been fairly recent, and so will affect that cruncher's ability to get new work.

6723881: The dual core i5, 2.4GHz. Reports as having 124 tasks in progress - about right for a dual core machine.

6729982: The i3, 2.2GHz. Reports 16 in progress, but 5 errors in recent days, again this will affect that cruncher's ability to get new work.

6204850: The one that reports having an ATI card. Reports 77 in progress, but has 15 errors, all aborted by user - this can affect a cruncher's ability to get new work.

Perhaps those trying to help should have been told the whole story, rather than a cherry picked section of the story?

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Nobody tried to convince him, he convinced himself!
(despite all advices - most of which he didn't follow)

BilBg I don't think thats fair.
I wasn't interested in shutting down the work unit fetcher for my nvidia card.
I haven't downloaded and installed SIV as thats some seriously strong medicine I probably shouldn't be playing with.
Other than that I tried to follow ever instruction.
As fare as convincing myself....I can install drivers..and work a screw driver...I Don't understand much of the "edit this file" portion of this discussion.

... run a background utility to keep retrying the servers for more work

NOT "for more work", but to (more often) retry the downloads you already have.

My download Que is empty 95% of the time. Its only during that last outage that I had any issue at all with the que. Which was understandable considering how long seti was down.

If Snowmain simply sticks <flops>80e9</flops> into the MB ATI portion of his app_info (I put it right before the <coproc> line in both ATI sections) he should get a bucket load of MB ATI work units. The 80e9 value is a SWAG on my part, if someone is already running an HD 5770 and actually has an average processing rate for it please share.

Please keep in mind that I am not an IT professional and need detailed instruction.

My system has stayed in ATI work all day proving my earlier post wrong. However it now seems to download about 20 units instead of only 10...which is better but I have 300 cuda units down right now. So whatever another 48 hours if there is 30 wu I guess we might have something...



Its a little to late tonight for me to pull the rig appart and I already have plans for tomorrow night. So the rig will get another 48 hours as it stands. Stoped over at my buddies place today for that 8800gts....Only he gave me an 8800ultra instead and an ATI HD 5870! So if the situation continues to improve I can run these cards for a substantial increase in performance. If not the 5770 and the 5870 will get me a good chunck of the way to the 200$ neccesary for a brand new GTX480.


Mike and Claggy,
I do appretiate that you took the time to read my posts and try to help me.
This line from Keith sums my perceptions up well: "People have been trying to treat the symptoms and not the underlying cause. "


My computer has been online with Boinc for 3 weeks. If that isn't long enough for the system to have gotten all the info it needs on my setup than the solution to this problem is better code. Since I sell software and don't write it my solution is to change cards. Why? because it will work, not someday, but the same day I do it.

Thank you all, well almost all of you.

---

So does that check box control just the fetching of units for that kind of app or does it control if it runs as well?

It only affects work fetch. Existing tasks will continue to run. I use this about once a week to rebalance my cache when I don't want more gpu work. This pref will pass to BOINC on the next update and BOINC will stop asking for that kind of work. The wording should be changed.

For future reference, is there a way to disable say a GPU accelerated Astropulse task while keeping the CPU version of Astropulse and a GPU MB running or is it only all Astropulse apps and all GPU apps?

Not that I know of with the way the prefs are structured.

---

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

Ah, I've only used the computing preferences page, never even noticed that page before. Never needed to look at that page before. Wouldn't know that was what he was referring to when he said disable nVidia GPU.

So does that check box control just the fetching of units for that kind of app or does it control if it runs as well?

For future reference, is there a way to disable say a GPU accelerated Astropulse task while keeping the CPU version of Astropulse and a GPU MB running or is it only all Astropulse apps and all GPU apps?

Sorry for being short but in 7 plus years I've never needed to anything other than install BOINC, add SETI@Home, install the latest optimized apps for my CPU and set my queue to 6 days. Everything just worked without any hand waving.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

Sorry, slight exaggeration on my part. Snowmain wants to get more work for his ATI card and someone suggested disabling the nVidia MB app. The exact quote was ...
[quote]Your hardware isn´t to shabby to be honest.
I would simply disable nvidia GPU in your preferences and only fetch ATI for a while.

Which part of disabling Nvidia work fetch didn't you understand? Snowmain has 5 days of Nvidia work, he can survive at least 3 days without asking for any Nvidia work, at which point he can re-enable Nvidia GPU work fetch.

Claggy

Sorry, how do you disable work fetch for a particular app and not the entire machine? I can shut down gpu apps, which I guess since your aren't finishing units there would be no need to fetch more but wouldn't that would shut down ALL GPU apps and not just the nVidia one? I also don't see any setting either in the manager or the preferences page that suggests you can just disable fetch for one of the available apps.

It may seem obvious to you what to do but it's not to me. Please share this dark knowledge.

All projects have their own project preferences page, where you can select Use CPU, Use ATI GPU or Use NVIDIA GPU as applicable, (subject to them having CPU/ATI/Nvidia Stock apps otherwise they don't all appear),
as well as which apps you want to run,

Claggy

Sorry, slight exaggeration on my part. Snowmain wants to get more work for his ATI card and someone suggested disabling the nVidia MB app. The exact quote was ...
[quote]Your hardware isn´t to shabby to be honest.
I would simply disable nvidia GPU in your preferences and only fetch ATI for a while.

Which part of disabling Nvidia work fetch didn't you understand? Snowmain has 5 days of Nvidia work, he can survive at least 3 days without asking for any Nvidia work, at which point he can re-enable Nvidia GPU work fetch.

Claggy

Sorry, how do you disable work fetch for a particular app and not the entire machine? I can shut down gpu apps, which I guess since your aren't finishing units there would be no need to fetch more but wouldn't that would shut down ALL GPU apps and not just the nVidia one? I also don't see any setting either in the manager or the preferences page that suggests you can just disable fetch for one of the available apps.

It may seem obvious to you what to do but it's not to me. Please share this dark knowledge.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

Well the nVidia technocrati wins again as an ATI cruncher is convinced it's not worth trying anymore.

Well played.

There seems to be a simple solution that doesn't required a beta of BOINC, switching to the AP ATI app, pulling his nVidia card (good one), run a background utility to keep retrying the servers for more work, I surprised nobody suggested reinstalling Windows with this shotgun approach.

If Snowmain simply sticks <flops>80e9</flops> into the MB ATI portion of his app_info (I put it right before the <coproc> line in both ATI sections) he should get a bucket load of MB ATI work units. The 80e9 value is a SWAG on my part, if someone is already running an HD 5770 and actually has an average processing rate for it please share.

Of course editing of the app_info file requires a full shutdown of the BOINC manager yada yada, YMMV, yada yada.

What harm is it to try?

I tried but he didn´t listen.

I dont waste my time.

---

With each crime and every kindness we birth our future.