~misfit~ wrote:

John Donson wrote:

~misfit~ wrote:

Bob wrote:

~misfit~ wrote:

Bob, see my post in the thread "yahoo...... i got some". You can
quite happilly leave both clients running, (You are using the
CLI version with SETIDriver right?) especially if you have
Windows XP. When BOINC has work it will take all spare CPU
cycles and when it hasn't then Classic will run. Classic WU's
don't expire.

Misfit,

Interesting thought, I may give that a try.  I still have about 4
work units to crunch through from classic, and yes, I have both
SetiDriver & SetiSpy handing the CLI version.  (It's a PIII-850
running Windows 2K Server/ISA Server as the firewall box for my
home network.)  Might launch BOINC tomorrow, and see how many
work units it can grab, and see how well the two work together.

Hi Bob,

It's working well here. My XP machine has run out of BOINC WU's
and has just started crunching Classic again. I wish I'd tried it
last week, machines have been idle for days.

No work from project again?

It's fine now. Just today all machines have full caches. I'm just
installing 98SE on a Celeron 900, might as well get that crunching
as well. --

Ah, thanks. I was just wondering if they can keep the work coming now.

I've got a 200 mhz MMX laying about here somewhere. Any idea how long that
machine will take to do a WU?