Get Involved! Start Analyzing the SETI@Home Source Code…

So, do you want to join the FPGA@Home effort and don’t know where to begin?  If you like analyzing source code, this post is for you.  Our next step is to find spots that can be accelerated by an FPGA. Below are instructions for how to download and run the SETI@Home source code.  All you cheap nfl jerseys need is a Windows machine with Visual Studio 2005.

Note: You must have Visual Studio 2005 as there are certain deprecated libraries that are no longer available in later version of Visual Studio.

How to Run SETI@Home from its source code on Windows XP SP3

Step 1 – Run Windows Update and Install Fake Oakleys Visual Studio 2005

Please run Windows Update just to be safe, and make sure that you have installed Visual Studio 2005 onto your machine.  I used the Standard Edition for testing these instructions, any edition should work, although I am not sure if the free edition – the Express Edition – will work or not.  If you have the Express Edition and try this out please let me know either way.

Note: In case you were wondering where you can get the Visual C++ 2005 Express Edition, you can download it from, as Microsoft has removed it from their website in an effort to make you use the latest version of their products…

Step 2 – Install TortoiseSVN (for your favorite subversion client)

Download and run the installer from here:
(click Downloads and select “Download Now”)

Step 3 – Install git

The people over at BOINC have set up some pretty good instructions for setting up git on your machine. You can access these instructions here:

Step 4 – Checkout SETI@Home source code using Subversion

It is easiest if you create a directory in the root of your partition called “Boinc” as so we will (1) make a directory called C:\Boinc, (2) in that directory right-click and select “Checkout Project” and use the following options:
URL of repository:
Checkout directory:
or you can issue the command line version:
cd c:\boinc
svn co

Step 5 – Clone BOINC git repository into C:\Boinc

You can use Git gui, or you can use the command line version.  Personally I would just use the Git Bash command line and get it over with!  Do the following from a Git Bash command prompt window:
Start->Run->All Programs->Git->Git Bash
cd /c/Boinc
git clone git://
git clone git://
This will create 2 directories under C:\Boinc, one named boinc, and the other named boinc_depends_win_vs2005.  The Visual C++ projects located in the C:\boinc\seti_boinc directory reference the projects and files that are located in these newly created boinc directories.
Note: boinc_depends_win_vs2005 is a pretty large download (over 750MB) so go take a break, get some organic tea, you have some free time on your hands.

Step 6 – Fix the Source Code

That’s right… the code doesn’t work out of the box for building with Visual Studio 2005, so I have recorded all of the changes that I made for this to work.  Perhaps somebody from the SETI@Home project team can work with me to incorporate these changes into the trunk of their subversion repository.
You can use the following patch file custom jerseys to apply the appropriate changes to the seti_boinc subversion directory in order for it to build under Visual Studio 2005 maroc viagra.
Download this file:
Right-click on the folder seti_boinc and select “Apply-Patch” then click “Patch all items” and Cheap Ray Ban Sunglasses click exit.
Or you can use the following command line:
 svn patch Patch_SETIatHome.patch seti_boinc

Step 7 – Open and Run!

Open the Visual Studio 2005 Solution file in
Now you can issue a “Rebuild Solution” command and wait a few minutes for the build to finish, then make sure that the seti_boinc project is video the default startup project by right-clicking on it and selecting “Set as Startup Project”.  Then click “Debug” at the top of your window and let it run!
Now… I suggest letting it run for about 30 seconds, and Wholesale nfl Jerseys then just pressing “Pause” on the debugger, and from there you can examine the call stack and see exactly where the code was.  I suggest you start analyzing the code by setting a breakpoint in the function seti_analyze() in analyzeFuncs.cpp, and once the code stops there step through it and work your way through the analysis of a work unit.

Leave a Reply

Your email address will not be published. Required fields are marked *