🚀 go-pugleaf

I am running it on two different systems here. when it is running in the
background, waiting for screen saver or I am doing something else, I have
not noticed any lost in speed. I put it on when I am not using the system or
let the screen saver function take over. On a 5x86 133MHz(win95), it has yet
to finish the first block of data, its been running for 496 hours and its
now near 96%. This system is used all the time and has 32 meg ram. On the
pent 200 MHz system(Win98) it has finished 7 blocks or data averaging 56
hours each block, that system has 128 meg ram and is used by walk in traffic
for internet use, or recording real audio files.
Both seem to work well with it in the background. I will be not using the
5x86 system after this run as it is too slow for seti use. We will be give a
p166 MHz system with 16 meg ram a try with linux next to see how well that
works.

dale


Woden wrote in message ...
>I'm  running it at work on NT4 Workstation (P2 350 Dual, ~200Mb RAM) and it
>takes about 12 hours to
>complete a data set.  I can run anything (Corel, Pagemaker...) without any
>great loss of performance.
>CPU utilization stays at 100%.  At home I am using it on a P2 333, ~210 Mb
>RAM and I do find it slows
>the system down.  It can take as much as 50 hours to complete a data set,
>but I often close it to improve
>speed.
>
>S.D.C. <gempac@hotmaildeletethis.com> wrote in message
>news:377596c8.160075586@news.magmacom.com...
>> "Aninoquisi" <star@watcher.invalid> wrote:
>> >automatically, except in screensaver mode. A 133MHz system should
average
>> >about 60 hours, to process a block (if set to run all the time, and
blank
>> >the screen immediately). My 233 takes an average of 35 hrs.
>>
>> Okay, there we are.  Setting the screen to blank speeds up SETI@HOME
>> by approximately 20%.
>>
>> Thanks for that information.
>> Shawn
>>
>>
>
>