.:(Seti@home):..

TC@SETI: (want to join, scroll down!)

What IS SETI ?: University of Harvard SETI Page

I WANT TO JOIN FAST TC-SETI!

if all this is already too complicated and you just want to join here is the fast 2 steps to join in, and deal with all later.

1. download THIS and install.

2. go here to enter TC-SETI team

3. click Team Rankings to check where you stand in Team Crunch rankings.

--(countine here if you want even more speed else continue more infos section)------------

4. download RamdiskNT create a ramdisk Z. Make it to save the ramdisk IMG on shutdown, and load the image on reboot. Copy your Seti stuff (seti command line client + driver / spy /etc ) and make an icon, or update your setispy/driver icon in prorieties to the new location on drive Z. let it run on ramdisk. some % to 15% more speed are reported. Why? Seti writes a lot down in the state.txt file while proceeding. Especially if you have many concurrent fragmented downloads running Kazaa/edonkey/whatever in background this slows the process down, due to the head movements of your hard disks.

• If you use linux use linux included ramdisk like this:
  # create a mount point:
  mkdir ~/setidisk0
  # create a filesystem:
  mke2fs /dev/ram0
  # mount the ramdisk:
  mount /dev/ram0 ~/setidisk0

5. Reduce downtime. If you dont have 24h inet connection install together with setispy, or without setispy the SetiDriver so that he queues work units. This means he downloads 5 work units (if you make a queue of 5) and will transmit either manually by your choice, or when he finished crunching 5 results.

6. More Linux related

The client runs fastest if you cancel ANY output, as even the support takes ressources. Thats why we will use /dev/null for our unix/linux starting. something like this will be fastest:

• nice --10 ./setiathome -proxy your-evtl-needed.proxy:80 >/dev/null 2> /dev/null &

why? : nice = changing prio (lower=faster) - if you encounter lockups change to --19

>/dev/null = redirect all output text to null

2> /dev/null = redir error messages to null

& = run as background process

on my maincomp i use to login on the linux comp and im using a batch like this:

• while true
• do
• cat state.sah | grep prog=
• cp ~/seti/ramdisk0/*.sah ~/seti/temp
• sleep 9000
• done

MORE INFOS

Best combination for me turns to be SetiSpy with SetiDriver (you find a link to it on SetiSpy page which you find on right navbar.

While SetiSpy gives you sophisticated information about your performance and what you research exactly (Starmaps, and link to Starmap Lexicons, Setiqueue can queue Work units and works together with Setispy. That means if your machine needs like 5 hours for a work unit you download saying 5 Work units and he can continue working on the next one even if you dont have a permanent connection running.

SetiDrivers needs the command line interface Client to work. There is no graphical analysis of what you do but its faster.

If you wish to help and participate to this very young and new Team simply download the SETI client by cfollowing "client download" link on right site.

Than you create an account when starting the seti client so you are listed as person (i made an error before, dont use my email or it gets added on my results, but you wishto be part of the team) so you go to the site

 here and join our Group. (Thanks Cyrik_DA for correction)

After we get some results in we will make also an online Spreadsheet to show how our team results over the time :)