I'm running SETI 24/7 all the time. SETI is almost always using 100% of my
processor [as it should]. I tried running the WINNT Text-only deal, but that
said I 'could not open file'.. Oh well..

TJ

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Broc Olson
Sent: Thursday, January 31, 2002 6:54 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Difference in WU's



Is data analysis always running? You have enough ram to run Seti all the
time.  If you hit ctrl- alt- del you should be able to get into the task
manager and find out whats hitting your CPU so hard.  Given what I can see
you have the hardware to pull 18-20 hrs on a WU ( And less)

Im running the Graphical client, (Yea yea I know), Screen Saver:  No

Broc Olson < Byark!>

----- Original Message -----
From: ssfmhou <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 31, 2002 3:22 PM
Subject: RE: Difference in WU's


>
> My Stats:
> os[Windows 2000 Professional, Service Pack 2 (5.0 - 2195)] uptime[21h 12m
> 58s] cpu[1-Intel Pentium III, 448MHz, 512KB (100% Load)] mem[Usage:
> 189/384MB (49.22%)]
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Broc Olson
> Sent: Thursday, January 31, 2002 5:15 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Difference in WU's
>
>
>
> How much Ram you got? My landlord is a p3 450 mhz w/ 96 megs of ram and is
> pulling 16-18 hrs on a WU. She had 32 megs and was pulling 40 hrs till she
> got another 64 megs  She's a Gateway and has no clue what she's doing
....so
> I help :-)
>
> Broc Olson < Byark!>
>


==
Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
This list sponsored by talkspace.net: building space communities online.
Mailing list services provided by klx.communications -- www.klx.com


==
Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
This list sponsored by talkspace.net: building space communities online.
Mailing list services provided by klx.communications -- www.klx.com

Reply via email to