Seti Cruncher" <SetiCruncher@"NOSPAM wrote:

"J. Tibbetts" <jt327gir@earthlink.net> wrote in message
news:AoaBc.7925$w07.5567@newsread2.news.pas.earthlink.net...

I forgot to mention that I'm running Seti@home version 3.08 in
Windows XP professional w/ SP1.


Jt

J,

Your time is not that bad.  The only thing I can suggest is switching
to the CLI version, that should give you about a 25% - 30% reduction
in processing time.

My main computer is a AMD Athlon 2400+ running XP Pro clocked at 2009
Mhtz with the Seti 3.08 Gui Client and I'm getting process times of
just over 4 hours per WU.

To speed up use the 3.03 CLI client.  I've stuck with the 3.08 GUI
just because I'm stubborn, using a cacheing program such as Queue or
SetiGate, will also save you time in the sending and receiving of
WU's.

The g/f has an XP2500 on a 200 FSB for 2.2Ghz (XP3200+ speed). Using
EasySETI CLI (SETIDriver, SETISpy and the CLI client all in one
easy-to-set-up package), them replacing the CLI version for 3.03, (EastSETI
installs 3.08) it averages around 2 hours 12 minutes. The good thing about
the CLI is that it's working while you are, using spare CPU cycles that
you're not using while you surf the web (for instance). This machine used to
used the GUI and it took around 3 1/2 hours per WU. Also, because it was
only active when the computer wasn't *in use* it only returned 1-2 units a
day. With the CLI running all the time it's returning 4-6 units a day.
(Turned off at night).
--
~misfit~