• 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.

how necessary is the seti driver?

joeld

Senior member
If its something nice that will run seti in a system tray or something like that, I'd use it, but right now I'm just using the pure cli seti. Any real reason to run the driver?
 
It has several benefits:

1) Can cache WUs for your machine (helpful when Berkeley has problems sending/receiving WUs)
2) Lets you easily configure settings for connecting to a SetiQueue
3) Lets you easily configure for dual CPU machines
4) Lets you easily adjust the processing priority for the SETI CLI
5) Lets you monitor the progress of the current WU
 
Alot of people don't like having something laying in the task bar all the time. SETI Driver will get rid of that & put an icon in the system tray. It will also cache work units in case you have a hard time connecting to the servers at Berkeley.
There are any numbers of add-ons you can use, alot of people feel Driver is easiest to use. So do i.

SETI@home Links & Add-ons Page
 
Thanks guys - system tray is all I need it for at the moment, although the priority may come in handy...
 
It's nice. I couln'dt bear CLI taking up a taskbar button constantly. The CLI also adds enough interfacing so I can track the progress and keep up with what the CLI is doing 🙂
 
Originally posted by: joeld
Thanks guys - system tray is all I need it for at the moment, although the priority may come in handy...
After a little fiddling around i found it best to leave the priority on 'Low' in SETI Driver. SETI will only take spare cycles anyway. Setting it to 'High' will only interfere with your normal computing.
 
Also helps to keep a Setilog.csv file, which Seti Driver can do.

I use mine with Seti Watch and I have a SetiQ running here also, I keep a cache on each machine with Seti Driver and each connects to Seti Q to send & receive WU's.
If Berkley goes offline for ten days I have enough WU's to keep all my machines running.
I think the most they have been offline at one time was 3 or 4 days, but that would be a long time to be without Work Units.
If you are connecting to a TeAm Queue then that takes care of your WU needs, then it's just a matter of personal preferance.
Of corse if you are running a multiple cpu rig then you can use Seti Driver to run multiple instances of Seti Cli.
 
Back
Top