As per Joes guideness I've installed SSSEX app with the faster cuda dlls.


<app_info>
<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>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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.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>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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.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>608</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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.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>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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.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>608</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>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>

What part do I need to copy & what files do I need go get fermi 6.10 app to work?

Thanks in advance

---

I understand connectivity from New Zealand to the rest of the world often involves paying a premium for anything beyond a specific amount per month.

                                                             Joe

Yes you are right theres no such thing as a high speed (more than 256/128kb) unlimited cap to my knowledge

If there is can you let me know?

---

...
What part do I need to copy & what files do I need go get fermi 6.10 app to work?

Thanks in advance

I'm going to let someone with actual experience give the final answer, but replacing cudart.dll with cudart32_30_14.dll, cufft.dll with cufft32_30_14.dll, MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe with setiathome_6.10_windows_intelx86__cuda_fermi.exe, and cuda23 with cuda_fermi are the primary needed changes. There are 5 places for each file name change, two for the plan_class change.

Because you have no "in progress" work on the host the version_num for the cuda_fermi app_versions could have been left at 608, but just to be consistent with what others are using I've changed it to 610 in the following edited app_info.xml.

<app_info>
    <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>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>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>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>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_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>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>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>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>
        <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>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>

You'll also need to be sure that the cudart32_30_14.dll, cufft32_30_14.dll, and setiathome_6.10_windows_intelx86__cuda_fermi.exe files are present. The Lunatics installer doesn't remove them, but if you've started BOINC since having an app_info.xml in place it will have removed them. If so, copy them back from the oldApp_backup folder.

Please wait for someone else to check this before trying to use it.

                                                                 Joe

You have read anonymous platform, haven't you? It doesn't help much with the practical nitty-gritty you're wrestling with here, but it should give you a feel for the shape of how it's supposed to work.

This was very helpful. It gives a few of the variables that can be used. Are there more, and if so is there a complete list? I will be looking through the archives from those 3 lists mentioned later. I am getting an understanding of how things are linked together and controlled. I have now seen a variety of app_info files, and there are definitly consistancies, and big differences. From what I'm seeing, there are several ways they can be written to accomplish the same thing, as long as the basic information is there.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

You have read anonymous platform, haven't you? It doesn't help much with the practical nitty-gritty you're wrestling with here, but it should give you a feel for the shape of how it's supposed to work.

This was very helpful. It gives a few of the variables that can be used. Are there more, and if so is there a complete list? I will be looking through the archives from those 3 lists mentioned later. I am getting an understanding of how things are linked together and controlled. I have now seen a variety of app_info files, and there are definitly consistancies, and big differences. From what I'm seeing, there are several ways they can be written to accomplish the same thing, as long as the basic information is there.

Steve

There are more, but not a list as such. Essentially, the fact that BOINC is open source means the most detailed documentation is the source code. The overall parsing of app_info.xml is in boinc/client/cs_statefile.cpp and the parsing of <app>, <file_info>, <app_version>, and <file_ref> elements is in boinc/client/client_types.cpp. Of course many other source files would need to be examined to really figure out what effects the variables have.

                                                               Joe

There are more, but not a list as such. Essentially, the fact that BOINC is open source means the most detailed documentation is the source code. The overall parsing of app_info.xml is in boinc/client/cs_statefile.cpp and the parsing of <app>, <file_info>, <app_version>, and <file_ref> elements is in boinc/client/client_types.cpp. Of course many other source files would need to be examined to really figure out what effects the variables have.

                                                               Joe

Thank you! I will be looking at the source code over the next few days, weeks, months, etc. and see what I can gleam from it. I realize I have a huge learning curve ahead of me, but I'm going to wade right in and test the water. I am fully prepared for mistakes, success, and lots of study. This is really interesting how the whole system is tied together. The more I learn, the more I become intrigued.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

The "out of disk space" situation has one advantage!

After crunching about 140 WU's I now know they average about 20 minutes and 12 seconds on the GTX470. I didn't calculate the shorties or the 2 WU's that ended after 25 seconds.

The GTX470 is doing 3 at a time, so that gives me an output of about 9 WU's every hour. I thinks that's not bad for a non-optimized app and in the next months there should be room to increase with 20 or 30% (?) if an optimized app comes available (?).

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

20 or 30% (?) if an optimized app comes available (?).

Looks like about 10% on Fermi in current experimental builds, available 'soon-ish'. 20% already at low angle ranges. Considering the architecture improvements, likely 20-30% overall in ~1 month, and probably a bit more after the cheaper variants are out (and I can get one :P). That's if nVidia engineers don't beat us to it ( It helps to have the hardware you're working on, and be paid to do it ;) )

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

20 or 30% (?) if an optimized app comes available (?).

Looks like about 10% on Fermi in current experimental builds, available 'soon-ish'. 20% already at low angle ranges. Considering the architecture improvements, likely 20-30% overall in ~1 month, and probably a bit more after the cheaper variants are out (and I can get one :P). That's if nVidia engineers don't beat us to it ( It helps to have the hardware you're working on, and be paid to do it ;) )

Jason

If I had the resources left after what I built, I would gladly buy one and send it to you. I'm still thinking of a way to do it.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

If I had the resources left after what I built, I would gladly buy one and send it to you. I'm still thinking of a way to do it.

Steve

The current models are a 'bit much' for me in power usage. I reckon when either the 460 or rumoured 475 materialise, I'll have saved enough pennies to grab one (working on it ;) )

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Please wait for someone else to check this before trying to use it.

                                                                 Joe

Thanks Joe for your help. I will await more assistance before firing up Seti

---

Came home yesterday and saw that all my CUDA WU's errored out after 32m17s.
Luckily I made a backup of my Boinc-data and the rig wasn't connected to the internet so it couldn't upload any results.

Put back my backup, removed the FLOPS from the app_info and it didn't happen again :)

---

Rig name: "x6Crunchy"
OS: Win 7 x64
MB: Asus M4N98TD EVO
CPU: AMD X6 1055T 2.8(1,2v)
GPU: 2x Asus GTX560ti
Member of: Dutch Power Cows

Please wait for someone else to check this before trying to use it.

                                                                 Joe

Thanks Joe for your help. I will await more assistance before firing up Seti

I'm actually fairly confident I got it right, if it were my machine I'd certainly fire it up now and try for some of the work while the spigot is on. I rather suspect they'll have to turn some capabilities off again, it would be a pity to miss this opportunity.

                                                              Joe

Ok I`m running 8 units at once, is this a bad thing?
All of my cpu`s are working at 100% and my gpu is constantly going.
I`m running an Asus cg9250 i7 core 2.67 gh and 12 gig of memory witha gtx 260 vid card.

---

Sounds good to me :) Did you expect anything else?

---

I would have expected nine - eight on the CPU cores, and a ninth on the GTX 260

But the GTX 260 isn't a Fermi card, so - although I'm delighted to see you're doing well - it doesn't really belong in this thread.

Thanks to Josef W. Segur for correcting my app_info file. My 1st gpu using a optimised cpu app Task 1643724208 took 12.15 minutes at an true angle range of: 0.385434

---

I dont suppose theres any eta or info on when a beta might show up for the 480 that'll work on a regular ole non-optimised client? (the kind without an app_info)

---

I dont suppose theres any eta or info on when a beta might show up for the 480 that'll work on a regular ole non-optimised client? (the kind without an app_info)

The client for a 480 (fermi) is already out.
Windows/x86 6.10 (cuda_fermi) 8 Jun 2010 22:50:03 UTC

See http://setiathome.berkeley.edu/apps.php

If you are running non app_info and have a 480/470/465 installed with correct drivers you should pick up work units (When they are available/project is up of course)

Once you have the card installed and recognised by BOINC you will get the workunits assuming you have

Use NVIDIA GPU
Enforced by version 6.10+ yes

set in your project preferences (or local preferences if set).

---

GPU Users Group

Wow, so much info in this thread. Hard to pick out what I am looking for.

Is there currently a location to download an app_info setup for Fermi? I've got one working but it was based off of the stuff posted in May.

Is there a way, or any benefit, to have my 480 work in more than 1 WU at a time?

---