Re: P4 2.4C times

 
 On Wed, 03 Sep 2003 15:34:21 GMT, "Stratcat�" <nobody@no.org> wrote:

I solved this by installing one instance of SetiWatch in the folder with
everything else. I now use SetiWatch as my results log. I saw a post by
f/fgeorge suggesting SetiWatch as well, although I'm not sure how he
configures his. Either way, this was my solution, FWIW.


I do it the same way you do. I have one instance of Seti Driver, and
one instance of SetiWatch. I do have one minor change though....I have
4 selected in the "desired cache size" section of SetiDriver. It was
suggested by Mike Ober the writer of the program. Rarely both work
units will finish at exactly the same time, or at least within the
time it takes to transmit and get a new work unit. When that happens
the program will hang if there are no work units in the cache. Having
a local cache such as SetiQue will not help. So he suggested that on
machines with more than 1 cpu or with HT enabled that the cache size
in SetiDriver be double what is actually being processed.
IOW, in your case it would be 4. Mine is also 4 since I have an actual
dual processor machine.

-- Have you checked your Smoke Detector...LATELY?