Forum > Discussion Forum
SAH V7 app_info Questions
Terror Australis:
Hi All
I'm posting here because the entire SAH site is locked up due to the current upgrade in progress and I can't get through to them.
I'm trying to cobble an app_info file together for the new SAH V7 and have the following questions.
1) What do I put in the <app_name> line to avoid junking the V7 CPU units I've already downloaded ? Is <name>setiathome_enhanced</name> still current, or does it have to be changed to something else ?
2) What is the correct entry for the <version_num>xxx</version_num> line ? Is "700"
right for both CPU and GPU entries ?
3) Is there anything else I should watch out for ?
Currently running BOINC V6.10.58, CUDA V4.2, Nvidia V310.7 on XP-Pro, QX9650 +3 x GTX580's
T.A.
Mike:
<name>setiathome_v7</name>
<version_num>700</version_num> for CPU and cuda.
ATI would be 703 for example.
Mike
Dirk:
1.) setiathome_v7
2.) 700, yes - for Windows CPU and GPU CUDA.
Linux and OpenCL apps have other numbers.
3.) make a correct app_info.xml file ;)
Or take just this ;D :
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE3.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_SSE3.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_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda42.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_42_9.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_42_9.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>.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_42_9.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>.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.00_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-3_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3_upx.dll</file_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>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3_upx.dll</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda42.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_42_9.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_42_9.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>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_42_9.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>.5</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_42_9.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
</app_info>
I guess this will trash the 'setigraphics_7.00_windows_intelx86.exe'.
But, who want look to the SAH Screensaver and want reduce crunching speed? ;)
Terror Australis:
Thanks Phil
That worked. All I had to do was change the x64 entries back to x86 and change it to the SSSE3 version of AK_v8b2
You also solved 2 problems for me, with the one I was debugging, (the CPU app was erroring out with no output file) and answered my wonderings if the "graphics" file was the GPU app or the screensaver :D
Your help is appreciated
BTW - On the CPU (I haven't been able to download any GPU units yet), V7 is taking ~3 hours to crunch as against ~2 hours for V6.03
T.A.
Claggy:
--- Quote from: Terror Australis on 01 Jun 2013, 04:42:06 am ---BTW - On the CPU (I haven't been able to download any GPU units yet), V7 is taking ~3 hours to crunch as against ~2 hours for V6.03
T.A.
--- End quote ---
What CPU is that?
Edit: I see, a QX9650
How long would Stock 6.03 take?
Claggy
Navigation
[0] Message Index
[#] Next page
Go to full version