Woohoo! After two weeks -
RAC: 2.98 Total Credit: 35.15

And all this time I thought it was just a worthless POS. Who knew?


<a>

great !

what was the processing time?

asking because got old pentium notebook with 120 MHz
so I could have an estimate how many hours (days?) i will take

greetings

ric

i got a P166MMX with 128M ram and under win98se it used to take about 60 hours to process a WU.

I at the moment converting it over to RHL 9.0 and soon beable to tell you how long it takes to process a WU under that OS when able to dl a WU from berkeley



Cheers Quail

<a> [/url]

Wireless Signals of the Past

Processing time? I think I stopped paying attention after 5 days. Let me say it like this: I set up BOINC on that PC on July 8th and as of this posting it was 62% through its third workunit.

That said, the first two WU's it crunched were the so-called 'super WU's'; on its last update, it downloaded 4 Wu's, which based on my cache should be enough for 3-7 days. So we shall see.


<a>

ok I see, thanks 4 info.

so I guess the p120 with 48 MB ram and w2k & setiQ.classic running
can make 1 wu in 1 week, 4-6 in a month or 60 in a year??

the gain 4me, seen in troughput wu per day, will be less than 1%,

maybe wondering what's the slowest cpu which can completed a wu
in the 14 day delay

it's nice to see, old cpu can do still work of today (excluding time factor)

ric

Have an old Mac Performa 5200 PPC 603 75 MHz 40 MB RAM
Process time 225 Hours

By comparison I have stuck on a Cyrex (god so old I can not remember how to spell it) 333. Actually reports as 258 hz, This manged some workunits in about 40 hours!

A lot of the machines at school I having chugging are 500 Mhz laptops and they are doing a unit a day each roughly.

Julian Rouse

It's spelled Cyrix. Unfortunately, I AM old enough to remember...

A couple years ago I bought a 133MHz Cyrix computer from a rural Indiana school district for a couple dollars. I think it did a Seti Classic unit in just under two weeks :)

> A couple years ago I bought a 133MHz Cyrix computer from a rural Indiana
> school district for a couple dollars. I think it did a Seti Classic unit in
> just under two weeks :)
>
>

I have an old 386 SX-2 16mhz machine with Seti classic installed on it. Without the math co-processor (sold separately) it takes about 3 years per workunit. Adding a co-processor drops the time to about 1 year. :)

------------------------------------------------------
We are Borgholio. You will be assimilated...bunghole!

Before I upgraded BOINC onto my 200Mhz, I was running Seti@home on an old TI Scientific Calculator. Top THAT!


<a>

> I have an old 386 SX-2 16mhz machine with Seti classic installed on it.
> Without the math co-processor (sold separately) it takes about 3 years per
> workunit. Adding a co-processor drops the time to about 1 year. :)

Did you actually do/complete units on that computer? :o

> Before I upgraded BOINC onto my 200Mhz, I was running Seti@home on an old TI
> Scientific Calculator. Top THAT!

I do Seti@home work unit computations with a pencil and paper.

>Before I upgraded BOINC onto my 200Mhz, I was running Seti@home on an old TI >Scientific Calculator. Top THAT!

4-bit? a PET? was this running under cpm?

anywhere in the basement in a bag still my "first compi"
a commodore64.
He is still working. also able to read from floppy

think this could top (down) but I'm not sure if there was a "official" cloient for it.

Well for displaying following messages even a 64 has
enough cpu power.

SETI@home - 2004-07-21 01:42:53 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-21 01:43:04 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-21 02:13:02 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-21 02:13:12 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-21 03:47:46 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-21 03:47:50 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded

If everybody uses a 386, but with copro,

then the demand could be keping on

b.t.w.
had also in the last centaury a Cyrix 200 Mhz, could "overclock"
to stable 225 MHz, this without a fan. the passiv cooling device
could easy tok off while the pc was running for mantenance an so,
It was the time of no noise CPUs and no heaten cpu...

ric

> > Before I upgraded BOINC onto my 200Mhz, I was running Seti@home on an old
> TI
> > Scientific Calculator. Top THAT!
>
> I do Seti@home work unit computations with a pencil and paper.
>
>


LMAO!

> > I have an old 386 SX-2 16mhz machine with Seti classic installed on it.
> > Without the math co-processor (sold separately) it takes about 3 years
> per
> > workunit. Adding a co-processor drops the time to about 1 year. :)
>
> Did you actually do/complete units on that computer? :o
>
>

Do, yes. Complete, no. :)
----------------------------------------------------------------
We are Borgholio. You will be assimilated...bunghole!

Impressive. I've been trying to figure out how to get my 386sx-16 to do SETI@HOME - hard when the max ram is 4mb. (Not counting the memory on my gigantic Intel Aboveboards, 2mb each using on 72 120ns chips). Most schemes so far involve a soldering iron :/

> > > I have an old 386 SX-2 16mhz machine with Seti classic installed on
> it.
> > > Without the math co-processor (sold separately) it takes about 3
> years
> > per
> > > workunit. Adding a co-processor drops the time to about 1 year.
> :)
> >
> > Did you actually do/complete units on that computer? :o
> >
> >
>
> Do, yes. Complete, no. :)
> ----------------------------------------------------------------
> We are Borgholio. You will be assimilated...bunghole!
>

Owner's manual

Website Owner's Manual

Bah!!! I am in it for the money.

Message from the Head ;o) of the
Horse Head Nebula Branch of Seti@Home,

Check is in the mail

> By comparison I have stuck on a Cyrex (god so old I can not remember how to
> spell it) 333. Actually reports as 258 hz, This manged some workunits in about
> 40 hours!

Cyrix (that's how it is spelled) actually invented PR rating (what AMD uses for CPU speeds)... except instead of doing it like AMD (reporting what the CPU is actually comperable to), they reported it as about twice what the CPU was comperable to.

I had a Cyrix PR200+ back in the day... a 150MHz CPU. It was about the crappiest CPU in the whole world... the things (to this day, no less) have the crappiest FPUs imaginable. That's why they take so long to crunch a workunit. Forty hours is actually pretty damned good for such a thing. :-)

> A lot of the machines at school I having chugging are 500 Mhz laptops and they
> are doing a unit a day each roughly.

That's a bit longer than I would have expected - my Athlon 550 does a workunit every thirteen hours, give or take.

Rob

> > By comparison I have stuck on a Cyrex (god so old I can not remember how
> to
> > spell it) 333. Actually reports as 258 hz, This manged some workunits in
> about
> > 40 hours!
>
> Cyrix (that's how it is spelled) actually invented PR rating (what AMD uses
> for CPU speeds)... except instead of doing it like AMD (reporting what the CPU
> is actually comperable to), they reported it as about twice what the CPU was
> comperable to.
>
> I had a Cyrix PR200+ back in the day... a 150MHz CPU. It was about the
> crappiest CPU in the whole world... the things (to this day, no less) have the
> crappiest FPUs imaginable. That's why they take so long to crunch a workunit.
> Forty hours is actually pretty damned good for such a thing. :-)
>
> > A lot of the machines at school I having chugging are 500 Mhz laptops and
> they
> > are doing a unit a day each roughly.
>
> That's a bit longer than I would have expected - my Athlon 550 does a workunit
> every thirteen hours, give or take.
>
> Rob
> <img> src="http://uml.no-ip-here.net/stats/sig.php?id=27&project=alpha">
>