Here are osecl-402 (Optimized Setiathome Enhanced Client for Linux 4.02). Sorry for the delay.. all are statically linked, but graphics are disabled.

osecl-402-mmx-r41.tar.gz mmx version. For P2 and processors not supporting SSE

osecl-402-sse-r41.tar.gz sse version. For P3, Athlon XP and SSE enabled processors.

osecl-402-sse2-r41.tar.gz sse2 version. For P4 w/o SSE3, Pentium M, Athlon64, and others with SSE2.

osecl-402-sse3-r41.tar.gz sse3 version. For P4 w/SSE3.

usage: as usual, make a full backup copy of the directory, stop the boinc core client, then put the contents (app_info.xml setiathome-4.2.i686-pc-linux-gnu) in the project directory. Restart boinc. Since the version number is the same 4.02, your WUs are preserved...but make sure to make a backup copy before using these!

Happy crunching!

---

Luckiest in the world. WMD = Weapon of Mass Distraction

To tell the truth my Linux box is compiled/optimized for P4 as a whole (it's a Gentoo) and it's a bit troublesome to build statically linked binaries for sse/mmx (but possible on vmware.) So next time (if any chance) I will distribute a necessary object and libraries and a shell script so anyone can link on his/her own machine for sse/mmx. It will be easier and quicker.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

Just a test distribution.

For P3, AthlonXp and other SSE enabled processors. Two Intel library files and a seti object file, readme.txt and building shell script are inside. You can link by yourself with this shell script very easily. By doing this, I hope I can distribute clients for any x86 processors very easily and quickly (because if I link, the binary will contain SSE2 instructions.)

osecl-402-sse-r41-obj.tar.gz (2mb)

This is fully fftw enabled and Intel object files are redistributable.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

hrmm you're talking greek to me... All I know is how to put the file in the directory and run it :). I guess if it's too much trouble I'll have to stick with the generic binaries. Plus the machine I am running on is so stripped down it probably won't have all the necessary files. I know your version is the only optimized version I could get to run on it. Also I tried downloading "osecl-402-sse-r41-obj.tar.gz" and got CRC errors.

forget it

---

Luckiest in the world. WMD = Weapon of Mass Distraction

forget it

I assumed I can only run your optimized versions since they are statically linked. I assume this gets around the limitation of my system not having all the files it needs. I gather from reading your previous post you will stop doing this? :(

The official linux client is already nice. So I don't think this is necessary.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

since there are only a few linux users here, I may stop releasing LInux clients....I'm reluctant on this....(personally I'm developing on Linux, though) On my machine, everything is optimized for P4. So building for other processors takes a bit more time, and the official one is already nice. If you need and let me know (on this message board) I will make one. Please specify which processor you are using. But I think I've made 4.02 clients for all x86 processors :)

---

Luckiest in the world. WMD = Weapon of Mass Distraction

since there are only a few linux users here, I may stop releasing LInux clients....I'm reluctant on this....(personally I'm developing on Linux, though) On my machine, everything is optimized for P4. So building for other processors takes a bit more time, and the official one is already nice. If you need and let me know (on this message board) I will make one. Please specify which processor you are using. But I think I've made 4.02 clients for all x86 processors :)

Is it possible to make an AMD64 client?

---

Linux Users Everywhere @ BOINC

no

no

Why?

---

Linux Users Everywhere @ BOINC

no

Why?

if you use a 32bit client with Athlon64, sse2 version will work for you, because cpu checking is off in the client. I cannot build 64 bit versions because I'm using p4's, and that it's Intel compiler.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

Is the source code of seti enhanced not public?

---

Linux Users Everywhere @ BOINC

It's public.

I asked on the dev's mailing list and Eric replied. See this post.

But be careful, Eric has upgraded to 4.05 (chirpfft.cpp is modified), so you need to download Jul-13 (or around then) version instead of the latest one to obtain source of 4.02.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

It's public.

I asked on the dev's mailing list and Eric replied. See <a href="http://www.ssl.berkeley.edu/pipermail/boinc_dev/2005-June/002940.html">this post</a>.

But be careful, Eric has upgraded to 4.05 (chirpfft.cpp is modified), so you need to download Jul-13 (or around then) version instead of the latest one to obtain source of 4.02.

Thanks :-)

---

Linux Users Everywhere @ BOINC

and I hope this client won't be upgraded to 4.05 for the time being because the deadline of WUs available now is mid-October (believe or not, it's intentional.)

Mixture of clients of different versions in a WU is real messy...for ex, as for this WU, I aborted this one intentionally because two had already crunched with 4.00 clients (4.11 is my misnumbered optimized 4.00 client.) I suffer from my own clients...very ironical.


So when you use optimized clients, you need to check the version upgrade everyday to synchronize with the official client, especially on beta site. On public seti@home, this isn't a problem at all because any version does the same math there.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

It would be very useful if the anonymous platform code could be updated to at least check for a base level version value and enforce sending new work to that host or not based on project minimums. Simply turning a blind eye as soon as the app_info.xml file is detected creates all kinds of problems for projects that allow customization and have evolving standard application versions. Sure, it’s a value that the creator of the optimized app (and even the end-user with creative editing of the app_info.xml file) can arbitrarily set, but at least it’s something that could give a small degree of control over home grown applications.

---

Well, I think the anonymous platform functionality was more or less designed with an established project in mind. Look at classic. Once things really got rolling, apps didn't change very often.

....tired of making clients for various processors.....

---

Luckiest in the world. WMD = Weapon of Mass Distraction

no

Why?

just a moment.....I may be able to make 64 bit binary. I have a question; does a binary mixture of 64bit objects and 32bit libraries run on AMD64? I wish I had an EM64T box....

Another problem is..ICC can produce objects for Itanium/EM64T, but it means the code contains SSE3 instructions..I've never tried to disable it. Anyway I will try it..

EDIT: hmmm...now it looks impossible.....;( but I will try. I don't have so much knowledge on 64bit architecture, so I'm learning it.

EDIT2: If you give me a shell account for an AMD64 Linux box using ssh, I can build 64bit version with Intel compiler....

---

Luckiest in the world. WMD = Weapon of Mass Distraction