John,

It appears you have two issues here.  First, BOINC truely runs at priority
1, but the SETI Classic CLI runs at priority 4.  The BOINC client will be
CPU starved in this situation.  To run the two together, download the
current version of SETI Driver and set the SETI Client Priority to "Idle".
SETI Driver will force the client to priority 1.  As to the SETI Driver
cache size, I run 3-5 days of cache.  To do this, you need to know how long
it takes your PC to process a WU.  Then divide that time into 24 hours to
get a day's cache size.  Multiply by the number of days you want to cache
and round up.  On a multi-processor or HT enabled machine, don't forget to
multiply this result by the number of logical processors in your system.  On
an HT enabled machine, don't check the "Set Affinity" checkbox.

Mike Ober.

"John Rehill" <iwp52@hotmail.com> wrote in message
news:AOOMc.400$q91.20@newsfe6-gui.ntli.net...

Hi all,

Have transferred over to BOINC but it just seems to sit there and do
nothing, says it has a work unit but the time scale for completion and the
progress report just dont' change so decided to switch back to classic

until

all major problems (ie server down, no wu's, program bugs) have been
resolved.

But my question is this:

How high as anyone set the cache in Setidrive to?  I normally varify

between

15-21 as some weeks i use my pc a lot other times not so much and i don't
want to be stocking up on wu's when there's no need.

I'm heading over for about 3 weeks and was gonna but it to 65 as i reckon

my

pc would work 1 wu in about 8hrs give or take so figure that's a good bet.

Any ideas to what i'm just throwing out there?

-- 





________________________
John Rehill
ICQ #: 57150168