Am I doing it wrong?

[{PMS}fishy]

This is my first time using seti, but it seems like it is taking way to long for my computer to do 1 wu. It took almost 21 hours to do one, and you can see my computer in the sig. But friends have told me that there PIII 800s are doing 1 wu in 11 hours or so. Whats the deal. Im runing version 3.03 with the always on option.

[TC]

Dump the gui version and get the command line client. There's a difference of up to several hours regardless of how you configure the gui. Also keep in mind that using your computer for even simple tasks will increase completion times.

[rogerdugans]

If you are running the gui version it takes a lot longer to process a wu.

Try the command line client (clc) and it should speed up a lot.

I have a couple of old rigs (400/450 mhz) that are right around 18.5 hours, so you should definitely be able to do better!

Get more info HERE (http://www.ocsetiteam.com)

*** thats what I get for being long winded: TC beat me to it! <LOL>***

[Yodums]

The PIII 800 should be doing WU's in 8 hours.

Setup a CLC and you'll be crunching 3x as faster as the slow GUI interface.

http://www.ocsetiteam.com/Instr1.htm

Theres the addy to setup the Command line Version.

Good Luck.
Happy Crunching.

[XprincoX]

will that client version work on XP too? its says it known to work on Windows 95, 98, 2000, NT but no XP? http://setiathome.ssl.berkeley.edu/unix.html

[Yodums]

Originally posted by Xprincox
will that client version work on XP too? its says it known to work on Windows 95, 98, 2000, NT but no XP? http://setiathome.ssl.berkeley.edu/unix.html

Use the link I gave you there's a zip for all files.

It works on all Windows and I'm on Windows XP and it works fine.

Yodums

[LandShark]

i've been run the CLC version + SETISpy + SETIDriver on my WinXP machine for 2 months already. didn't have any problem.

crunch on.........;)

[XprincoX]

hmmm... just switched to the clc version and have noticed that my system is reeeally laggy compared to the gui version. Should i just put the priority to low rather than normal?

[LandShark]

yup. if you DO use your computer.

i set all my rigs in "low" 'cos most of them are using everyday. and i did notice the lagging when i just set it to "only" normal. tried "high". man, makes me wait for anything forever!!!

[Basher]

Originally posted by Xprincox
hmmm... just switched to the clc version and have noticed that my system is reeeally laggy compared to the gui version. Should i just put the priority to low rather than normal?

Setting to anything other than low does not gain you anything. Low is the best setting else everything to slooooooooooooooow, setting it to high dows not really gain you any speed either.

[TC]

Use task manager to set the priority to "real time" :p I actually tried that once and the system promptly froze - only time NTx has frozen on me:eek:

[hallen]

Originally posted by {PMS}fishy
It took almost 21 hours to do one

FAQ says changing screen density while SETI is running can slow it to a crawl. 256 color uses less resources.

http://setiathome.ssl.berkeley.edu/faq.html

[lonewolf1983]

that screen res tweak is only to do with the GUI version
nothing to do with the CLC
:)

[hallen]

Originally posted by TC
Dump the gui version and get the command line client.

By command line you mean: setiathome-3.03.i386-winnt-cmdline?

When I execute I get:

------------------------- clip -------------------------------
options:
-version show version info
-login log in
-countries show list of country codes
-proxy hostname:port connect to SH server through specified
proxy server
-stop_after_process stop after current WU - do NOT send result
-stop_after_xfer stop after current WU - DO send result
-verbose print running status
-nolock skip multiple-instance check
-socks_server hostname:port SOCKS proxy
-socks_user name SOCKS user name
-socks_passwd passwd SOCKS password
-cpu N set client to run on CPU N
------------------------- clip -------------------------------

Can you point me to some instructions and examples on how to use this to replace the GUI driver?

Thanks

Harvey

[Basher]

CLC install (http://www.ocsetiteam.com/Instr1.htm)

[hallen]

Thank you Basher. I done that and it was helpful getting me started.
When I'm running it's with:

SETI Driver
SETI Spy

and when transmitting/receiving

setiathome-3.03.i386-winnt-cmdline kicks in.

I thought references to a non-GUI environment would mean eliminating SETI Driver and SETI Spy, which are GUI to me. and doing everything using

setiathome-3.03.i386-winnt-cmdline

which I can't find instructions on how to do anywhere.

[deez]

hallen...you are running command line with driver and spy...the GUI they are talking about is the screensaver mode which tends to increase times 33-50% over command line

driver and spy do not slow down the client

[rogerdugans]

Originally posted by deez
driver and spy do not slow down the client

Much. Maybe like a wu a year or something!

[hallen]

deez- Got it. Thanks. I'd love to do it in DOS with 32mb extended memory. With the big caches starting to appear I'd like to see the stats on keeping it all in L1 and L2 cache.

HP has a new 3mb L1 32mb L2 cache system:

http://www.lostcircuits.com/cpu/hp_pa8800/

Maybe that's what benz4140 is using