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

SetiDriver and dual procs

Not that i know of.

But, if you use SetiWatch, then you can tell it if it's using a caching program, and it looks at which directory it's running from, so maybe it will also tell you if running on 2 processors...


If i get my 2 celeron 400s from GWN today, then i'll have a look and see 🙂

Obviously i'd like to know this as well, so if this doesn't work, consider it as a bump! 😉

ConfusedBW
 
I never found a way either. One method would be to put SETISpy into each of the numbered folders, uncheck the "Hide processing" checkbox to find out which of the clients are currently running, and go to those folders and start SETISpy there. Obviously this introduces a bit of overhead and wouldn't be optimal for the long haul.

What I've never understood is the "Use SETI Spy" checkbox in "Progress Monitoring." And I'm too lazy to go hunting for the answer right now. 😉 Anyone know what it does...?
 
The "Use SetiSpy" option puts all of the current status info into the directory with SetiDriver so that SetiSpy doesn't have to go hunting for the WU being processed... At least, that's how it works for single-CPU systems. 😉
 
Back
Top