• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Seti Speed up

JimmyEatWorld

Platinum Member
Hey guys, I'm new to Seti, and to this forum, TwoFace just kindly directed me here
I searched for some threads but I can't find a good keyword I guess, but I want to know how to tweak my machine into a Seti beast (or as much of one as it can be)
I'm on a Duron 1 gig with 128 megs ram, under Win98SE
thanks in advance!

Edit: I just joined RC5 as well...
please keep in mind I have no idea about anything whatsoever about either of these too things, so keep the newbie and llama cracks to min. 🙂
 
First off make sure you are using the seti command line client instead of the gui, it's quite a bit faster. Make sure you kill any uneeded programs that might be running in the background, disable all the power saving features & make sure your memory timing is tweaked. 🙂

I'd also highly recommend running either setiQ or setiDriver to cache a few wu's so if the seti servers go down you won't run out of wu's. I don't have the link on hand but I think there are links to the download sites on our team website just follow some of the links in my sig for more information. 😉

Edit: After reading your other thread I am assuming you must be running the gui in screensaver mode with the graphics displayed. If you are, at least set the seti client to always run in the background & disable the screensaver mode. Even better would be to run the command line client.

BTW my P3-667 averages around 7.8 hrs per wu.
 
Yes, use the cli if you can. I shaved off over an hour on my wu times on my 950 duron @ 8 hours.
 
I'd strongly suggest the CLI and SetiDriver. Here's the quick way to get that running. This assumes you have a basic (no proxy) setup with modem, cable, or DSL:

Download setidriver and unzip it in an empty directory where you will run it from http://www.wakeassoc.com/setidriver/SETIDriver.zip

Download the Seti CLI client to the same directory ftp://ftp.cdrom.com/pub/setiathome/setiathome-3.03.i386-winnt-cmdline.exe

Run setidriver. Set these options and leave the rest alone:

"desired cache size" = 10

"Create Setilog.csv" = check it (you can get setilog later)

"auto transmit" = check it if you're on cable or DSL, dont check it if you're on a modem


You're done. Now just click the transmit button. This will prompt you to login to your seti account. Choose option #2 if you already have an account and give it the proper info. This will start setidriver filling the cache, which you set to 10 work units.

SetiDriver now should have 10 work units to play with. If the seti servers go down for a few days, you'll be OK. If you're on a modem, just "transmit" every few days to keep the cache full.

You may want to put the setidriver link in your windows startup group on the start menu. You should also find a file named "conagent.exe" in your windows directory, and change the properties on this file to not "warn if still active" (or something like that, it's on the far right tab in the properties for that file). That last change will keep the seti CLI from stalling when you try to shutdown the machine, which is REALLY annoying (fix not necessary on NT or win2k).

Did I miss anything???

Your duron should probably do just over 2 WU's per day.
 
JimmyEatWorld
Hi🙂 ,someone mentioned tweaking your RAM settings which makes a noticeable difference to SETI.What RAM do you have?What is your CAS latency set to? & also memory speed settings?
Going from CAS 3 down to 2 makes the biggest difference ,if your RAM can handle it.
 
Back
Top