I had seen an old post from Sciman Stev on where he put the file but have been unable to tack down his post.

---

Did you follow the FAQ on the subject? It says where to put these files.

If that's not written clearly enough, let me know and I'll change the text.

---

Richard,
Thanks for your time and effects.

I would recommend the following changes to the guide.

Install the Lunatic
FreeBSD science apps first as the app_info file does not exist with out it.
(Newbei info like me)

I Installed the FreeBSD 64bit Science Apps
(64bit AstroPulse_V505)
I am running a Intel 920 cpu ( It would help if you provided links in the FAQ)
to the follow your guide.

I am assumming That I have done this correctly as the Boinc Manager in messages now reports

Seti@Home (date/Time) Found app_info.xml; Using Anonymous platform
(What can a user expect to see if install correctly)

A complete XML text that can be copy and pasted into the app_info would be helpful

As most people are going to be unsure what a completed info_app.xml should look like.

(Under Win 7 64 bit the xml data and dll where put in c:\programdata\Boinc\projects\setiahome.berkeley.ed
I do not know if the file structure changes between windows versions.

I will keep the project on no ne tasks until I hear from you that I have installed coorectly.

I really do appreciate you time a efforts.

Below is the XML as modified is this correct?

<app_info>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.06r237_sse3_x86_64-pc-freebsd</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<file_ref>
<file_name>ap_5.06r237_sse3_x86_64-pc-freebsd</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>0.200000</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<file_ref>
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
<file_info>
<name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>


thanks once again for all your efforts

---

John, you CAN'T use FreeBSD, Linux or any Other OS's apps on Windows, use the Lunatics Installer to install the WINDOWS apps, then modify the app_info for Fermi,

Claggy

can you provide a link and the the file name?

---

is Astropulse 5.05 win32 rev 409 sse4 the coorect file?

---

can you provide a link and the the file name?

Lunatics Downloads

Choose the Installer according to your OS,

Win98me Lunatics' Unified Installer v0.36 is for Win98 or Me

Win32 Lunatics' Unified Installer v0.36 is for 32bit Windows

Win64 Lunatics' Unified Installer v0.36 is for 64bit Windows

Make sure you only use the 64bit Version with the 64bit version of Boinc,

Claggy

OK I see the Win64 Lunatic's Unified Installer V0.36 should be the coreect one.

---

installed win64 Lunatics Unified Installed V0.36
my info_app.xml looks like this is this correct?
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_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_v8b_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_v8b_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.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>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Thanks in advance

---

Rerun the Installer, and choose SSSE3 (instead of SSE3),

Claggy

Sorry about that I did not remodify after Unified installed Update.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_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_v8b_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_v8b_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r409_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>ap_5.05r409_SSE.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>
<file_ref>
<file_name>ap_5.05r409_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>0.200000</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<file_ref>
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
<file_info>
<name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>

---

John,
As Claggy asked you, please rerun the unified installer and choose SSSE3, that's three S's not just two. Other than that, to my untrained eyes that looks pretty good.

---

PROUD MEMBER OF Team Starfire World BOINC

Your app_info won't work, you can't just tag the fermi stuff on the end, after the </app_info> close tag,
the <file_info>'s also need to be at the start of the fermi section after the <app><name>setiathome_enhanced</name></app> tags (that you don't have).

Once you're rerun the installer and choosen the SSSE3 (3S's) version of AK_V8 instead of the SSE3 version (2S's), as well as the Astropulse_v505 r409 app,
then you can use this following app_info:

<app_info> 
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.05r409_SSE.exe</name>
        <executable/>
    </file_info>

    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
   <platform>windows_intelx86</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.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>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>

    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AK_v8b_win_x64_SSSE3x.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_v8b_win_x64_SSSE3x.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_v8b_win_x64_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>

    <app>
        <name>setiathome_enhanced</name>
    </app>
      <file_info>
         <name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
         <executable/>
      </file_info>
      <file_info>
         <name>cudart32_30_14.dll</name>
         <executable/>
      </file_info>
      <file_info>
         <name>cufft32_30_14.dll</name>
         <executable/>
      </file_info>
      <file_info>
         <name>libfftw3f-3-1-1a_upx.dll</name>
         <executable/>
      </file_info>

    <app_version>
       <app_name>setiathome_enhanced</app_name>
       <version_num>610</version_num>
       <platform>windows_intelx86</platform>
       <avg_ncpus>0.200000</avg_ncpus>
       <max_ncpus>0.200000</max_ncpus>
       <plan_class>cuda_fermi</plan_class>
       <coproc>
          <type>CUDA</type>
          <count>1</count>
       </coproc>
       <file_ref>
          <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
          <main_program/>
       </file_ref>
       <file_ref>
          <file_name>cudart32_30_14.dll</file_name>
       </file_ref>
       <file_ref>
          <file_name>cufft32_30_14.dll</file_name>
       </file_ref>
       <file_ref>
          <file_name>libfftw3f-3-1-1a_upx.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>
       <avg_ncpus>0.200000</avg_ncpus>
       <max_ncpus>0.200000</max_ncpus>
       <plan_class>cuda_fermi</plan_class>
       <coproc>
          <type>CUDA</type>
          <count>1</count>
       </coproc>
       <file_ref>
          <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
          <main_program/>
       </file_ref>
       <file_ref>
          <file_name>cudart32_30_14.dll</file_name>
       </file_ref>
       <file_ref>
          <file_name>cufft32_30_14.dll</file_name>
       </file_ref>
       <file_ref>
          <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
       </file_ref>
   </app_version>
</app_info>

Claggy

Hi there

Im getting the following messages in my logs everytime I try and run rescheduler?
I have the 610 CUDA app as I can see it in my processes, and my gtx470 is crunching away merrily. Is rescheduler compatible with the latest fermi workunits? Should I stop using it?

06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding

Thanks

---

Hi there

Im getting the following messages in my logs everytime I try and run rescheduler?
I have the 610 CUDA app as I can see it in my processes, and my gtx470 is crunching away merrily. Is rescheduler compatible with the latest fermi workunits? Should I stop using it?

06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding

Thanks

From what I've read and unless It has been updated, No.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Ok, thanks for that - will keep an eye out on the lunatics forum..

---

You should be OK rescheduling from GPU to CPU.

I would expect that ReSchedule would have problems creating entries for plan class cuda_fermi, as specified in the opening post in this thread. If you really feel the need to move tasks from CPU to GPU (and there's no need to do that, if your primary need is simply to process VLAR efficiently), you could:

1) Allow ReSchedule to move tasks to the GPU, but prevent BOINC running afterwards
2) Examine client_state.xml, to see how they've been marked up
3) Make a duplicate <app_version> block for app_info.xml, matching the entries that ReSchedule makes.

Or you could just wait for Marius to publish a new version.....

I suspect that when the ReScheduler operation runs it is taking the tasks that previously have been marked to run with a CPU app that is not present on the system. If you are running another optimized app from Lunatic's (AK's) it should work.

I am not running a specific Fermi app on my system - currently Cuda23 and the AK x64 - but I don't experience the same behavior. My Rescheduling does work, for the most part, properly.

I believe that Richard is correct - those tasks are being marked up to an app other than what is on the system and in the app_Info.xml there is no app available to process those.

His suggestion should work. Best of luck!

---

The Fermi application (v6.10) has become visible on the SETI applications page. That means Fermi users should be able to handle work correctly without using the techniques described in this thread. We need to check that everything's working OK: if anyone has a Fermi they have not yet attached to SETI, feel free to attach now and post your HostID so we can check the results with you.

Thanks for this Richard, I will give this a go...

You should be OK rescheduling from GPU to CPU.

I would expect that ReSchedule would have problems creating entries for plan class cuda_fermi, as specified in the opening post in this thread. If you really feel the need to move tasks from CPU to GPU (and there's no need to do that, if your primary need is simply to process VLAR efficiently), you could:

1) Allow ReSchedule to move tasks to the GPU, but prevent BOINC running afterwards
2) Examine client_state.xml, to see how they've been marked up
3) Make a duplicate <app_version> block for app_info.xml, matching the entries that ReSchedule makes.

Or you could just wait for Marius to publish a new version.....

---