Posts by Swordfish

1) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383922)
Posted 23 Jun 2013 by Profile Swordfish
Post:
Good suggestion Alinator, I had already installed Lunatics, but I'll keep your suggestion in mind for the future.

After installation I edited the app_info, and I'm again running 2 GPU tasks, as well as the 2 cpu.

Wife's just taken over her computer, so I'm unable to do much more, other than to monitor it from Boinc Tasks from mine.

Not that will do much at the moment as CPU and GPU tasks are set to suspend on both main computers, when we are actively using them.

I have experimented, and that is the best solution, as both main computers are getting a bit long in the tooth now 2005 era for mainboard/cpu/ram.

But until they actually fail, I can't justify an upgrade.

When they actually do, then both systems will be updated probably to 8 core FX8350, sabertooth r2 with 32gb ram and a new grahics card to be determined as yet. Then, there's the case, cooling etc,etc, the list goes on and on, lmaooo :)
2) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383914)
Posted 23 Jun 2013 by Profile Swordfish
Post:
Ok TBar your suggestion regarding atiman uninstall seems to have worked, as I tried out Claggy's suggestion regarding switching to stock.

I uninstalled Lunatics and 90 seti@home v7 (opencl_ati_sah) tasks came down along with 30 resent cpu tasks and a couple of cpu astropulse tasks.

I assume when I re-install Lunatics later, that the app_info.xml file will reappear, as at the moment it seems to have disappeared.

As can be seen in my first post I edit this file to <count>0.5<count> in order to run 2 GPU tasks at a time.

Thanks to TBar and Claggy for getting me up and running again.
3) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383901)
Posted 23 Jun 2013 by Profile Swordfish
Post:
OK, I've used Atiman uninstaller to clean windows 8, and re-installed the 12.10 driver. GPUZ is showing opencl ticked.

Still getting same astropulse notice, and of course the server won't download any ati gpu wu's as its saying I've exceeded daily quota of 1 tasks.

So it looks like I'll have to wait yet another 24hrs till the server will allow me new wu's, and only then will I know if it's working or not.

This is a damn annoying.

These quota restrictions are a real pain, when it comes to sorting problems out.
4) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383890)
Posted 23 Jun 2013 by Profile Swordfish
Post:
Oh by the way thanks for you help as well Tbar, I'll look into that option, tomorrow, when my wife is at work. After all its her desktop I'm using as one of the hosts.
5) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383889)
Posted 23 Jun 2013 by Profile Swordfish
Post:
Ok guys the computer concerned attempted to download 6.04 astropulse_v6(ati_opencl_100) tasks and 7.03 setihome_v7 (opencl_ati5_sah) and all tasks aborted as soon as they downloaded with error 201.

I'm at a loss whats going on here.

I'm now back in the situation, where I've downloaded my quota for the day.
6) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383827)
Posted 23 Jun 2013 by Profile Swordfish
Post:
Ok guys I'll wait to 1 pm UK time for 24 hours to pass, and see if this notice / error stops.

Thanks for the assistance. :)
7) Message boards : Number crunching : Your app_info.xml file doesnt have a usable version of AstroPulse v6 (Message 1383637)
Posted 22 Jun 2013 by Profile Swordfish
Post:
Why is this happening.

I've tried re-installing the 13.4 drivers, get the above error.

Removed the 13.4 drivers, and the windows generic HD6670 driver, and still get the error.

I've now removed those drivers from the machine, and installed 12.10.

Still getting this error.

Because over 250 tasks have aborted, I've now used up my day's quota of ATI tasks.

I've pasted a copy of the app_info.xml , for anyone who could give me a clue to what needs to be done to rectify this.

<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSE2x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSE2x.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSE2x.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_SSE2x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</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_SSE2x.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_SSE2x.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_SSE2x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSE2x.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_SSE2x.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_SSE2x.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_SSE2x.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_SSE2x.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_ATI_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_ATI.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>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_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_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.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_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_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>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_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_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.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>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</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.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</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.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</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.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
</app_info>
8) Message boards : Number crunching : Ati tasks suspending themselves. (Message 1379882)
Posted 11 Jun 2013 by Profile Swordfish
Post:
Yes Richard they are VLAR tasks.

And yes again I am running BOINC Tasks.

Funny, I just upgraded to the beta version 1.48, about 5 minutes before you replied.

Lets see if this sorts it out.

Thanks for you input :)
9) Message boards : Number crunching : Ati tasks suspending themselves. (Message 1379875)
Posted 11 Jun 2013 by Profile Swordfish
Post:
Anyone having trouble with v7 ati multibeam tasks suspending themselves without any apparent cause.

I am getting this problem since upgrading on the 2 computers running these tasks.

It's not all the time, just periodically.

Particularly annoying if it happens during the night, and find tasks suspended in the morning, and no ati work processed.
10) Message boards : Number crunching : What does notice supposed to mean (Message 1373818)
Posted 30 May 2013 by Profile Swordfish
Post:
Ok Mike thanks for that, I trying to sift through the threads, but got confused by the discussions.
11) Message boards : Number crunching : What does notice supposed to mean (Message 1373810)
Posted 30 May 2013 by Profile Swordfish
Post:
SETI@home: Notice from server
Your app_info.xml file doesn't have a usable version of SETI@home v7.

I'm using Lunatics 0.40 on Boinc 7.0.64 (64bit) running a ATI HD6670 set with a count of 0.5 (effectively running 2 ATI tasks), and 2 CPU tasks from my AMD dual core processor.

and this notice this has recently started to come up regarding Seti version 7

I'm not sure what I must do to run version 7.

Do I just run Lunatics 0.41 on Monday when it's released ?

Sorry, but I'm confused :(
12) Message boards : Number crunching : changing app_info.xml after upgrade to 7.0.64 (Message 1364378)
Posted 4 May 2013 by Profile Swordfish
Post:
I've just tried the site, and its up and running
13) Message boards : Number crunching : Boinc 7.0.64 Available , faffed up my ATi tasks (Message 1361193)
Posted 25 Apr 2013 by Profile Swordfish
Post:
Thanks for the info.

I've been rather busy, and not seen these posts.

Anyway I know now what is to be done when I decide to upgrade again.

Thanks again

14) Message boards : Number crunching : Boinc 7.0.64 Available , faffed up my ATi tasks (Message 1361185)
Posted 25 Apr 2013 by Profile Swordfish
Post:
I upgraded from 7.0.28 earlier today, after being advised by BOINC Manager that a newer version was available.

Upgrade appeared to be successful, until I came back to the project a few hours later to find all ATi gpu tasks had errored out with computational error 197.

I haven't got the time at present to faff around with this, so I just simple done a system restore, BOINC update being the last restore point.

Reverted back to and running 7.0.28 and the ATi gpu tasks are reporting again without error.

Surely its, not a case of haven't to run out all the GPU tasks before a BOINC upgrade.

Never had to do that previously.

Any comments guys
15) Message boards : Number crunching : Apologies 500+ WU's abondoned (Message 1352856)
Posted 1 Apr 2013 by Profile Swordfish
Post:
I managed to get the machine up back up several hours ago.

Fortunately, I had backed up the system prior to my problems, and It's all up and running again.

Windows 8 has known issues with sound buzzing, and I'd been faffing around trying to sort that issue out.

I also reinstalled the ATI graphics drivers, and that really put a spanner in the works and caused all my ATI tasks to error out.

Couldn't resolve the issue, and then the sound became even worse.

Hence the drastic measures, mentioned in my last post.

Anyway, everything appears sorted, now, for the time being.
16) Message boards : Number crunching : Apologies 500+ WU's abondoned (Message 1352446)
Posted 31 Mar 2013 by Profile Swordfish
Post:
I'm resetting windows 8 on one of my machines , due to driver problems and other quirks which have resulted in such a drastic measure.

Over 500 WU's have been abandoned.

The reset procedure in windows 8 can take an extreme length of time.

I'm currently at 23% after nearly 3 hrs.

Just hope I can get this machine up and running before the big move at SETI

Apologies to any wing people affected.

17) Message boards : Number crunching : Seti android app (Message 1351268)
Posted 27 Mar 2013 by Profile Swordfish
Post:
Samsung Tablets, don't even get warm, when crunching.

Then again, the tablets are only set to crunch when connected to the power adapters.

18) Message boards : Number crunching : Seti android app (Message 1351215)
Posted 27 Mar 2013 by Profile Swordfish
Post:
First 2 WU's on Samsung Galaxy Tab2 10.1 have validated successfully.

Still awaiting completion of first WU's on Galaxy Note 10.1 Tab 2.
19) Message boards : Number crunching : Seti android app (Message 1351115)
Posted 27 Mar 2013 by Profile Swordfish
Post:
Yep, 2 WU's reported OK overnight on the Samsung Galaxy Tab 2 10.1 , just waiting for verification. They took just over 7 hours each to complete.

Several other WU's downloaded overnight. 2 currently running.

On that basis, I set up my wife's Samsung Galaxy Tab Note 2 as above.

Its Quad core, so 4 tasks are currently running.

I've also set both tablets, to only run, when the power line is connected, and that's usually when we are not using the devices.
20) Message boards : Number crunching : Seti android app (Message 1350995)
Posted 26 Mar 2013 by Profile Swordfish
Post:
Just fired up my Samsung Galaxy Tab 2 10.1 with nativeboinc 7.0.36

Both Wu's are about 3.2% after 16 minutes.

I'll leave it running overnight, to see if they run successfully to completion.


Next 20


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.