• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Anyone that is thinking about installing Seti on a K6-2 233 with 64 mb of RAM

LastKnight

Senior member
Needs to reconsider. I frankensteined several broken pcs together this morning to make a functional one, and figured that I'd install Seti on it to see how long it would take to do a WU, I figured, hey, a work unit every 20 hrs would be fine with me.

Oh, no. This guy's due to finish his first work unit at 1am on the 29th. Maybe i should just shoot it.
 
Yeah, tell me about it! :Q

Although mine was a K6 233!

It took nearly 3 days for a WU

It's now running Genome @ home for TA and i'm 7th out of 9 in the weekly standings! :Q

That shows how small the G@H team is 🙁

Try it on another project like G@H or ECCp-109 (on F@H it won't submit the WUs within their time limit)

ConfusedBW
 
ECC-p it is. Now it's throwing up a bunch of large numbers...why do I get the feeling it's still going slowly...

Gotta wait till it finishes its first WU before I join ECC-p TA.
 
On my Celeron 400 machine, i get about 180,000 iterations/second, and from the total Iterations and total DPs, it takes about 560,000,000 iterations per DP.

So wait for the total iterations to go up! 🙂

On my 400 i get about 25 DPs per day, not much, but better than nothing 🙂

ConfusedBW
 
i have the very same thing going on here......turn it on and forget about for a couple of weeks.......every w/u counts..
 
I have one at work, K6-2 300 and it took 34+ hours to finish 1 Wu at 6.3 AR. And it has 192 mb of pc-100 ram in it!! :Q
I took off the client from that 'puter.

From what I've been reading I might put eccp on it and let go with that !
 
Those K6's would do good at either OGR....................a DNet thing

Or try the K6 Optimized client for ECCp.............

But let them do something...............old comps are like old people............they need to stay active to have a longer, happier life 🙂
 
I ran S@H on a K6-233 w/ 64MB ram for quite a while.. avg time was 48 hours.... Now he just sits on my desk, awaiting the time when I have the desire to play old DOS games....
 


<< I ran S@H on a K6-233 w/ 64MB ram for quite a while.. avg time was 48 hours.... Now he just sits on my desk, awaiting the time when I have the desire to play old DOS games.... >>



Whatttt??!

Get it running ECCp!! 🙂
 
I got Seti running on 2 of my machines, both that slow. One is a K6 233, and a k6/2 300. Both do a WU in just onder 2 days. I know your pain 😀
 
K6-2's don't have very good floating point performance, which is what SETI loves. My sister's K6-2 450 does a WU in about 25 hours. My dad's computer, once a K6 300, took more like 40 hours. It's not a T-bird 700. MUCH faster.😀
 

Also K6-2's have to relie on the L2 cache running at the slow FSB speed.

Btw LastKnight AMD never made a K6-2 233 AFAIK ,it would be the K6 233.The K6-2's started at 266.The main differences are that the K6 doesn't have 3Dnow instructions (no difference to SETI) & they are on a 0.25u process instead of 0.35u.Though the CXT's K6-2's are slightly different again ,they started from 350 upwards.
Don't ever be tempted to overclock that K6 233!😉

paf007

I have one at work, K6-2 300 and it took 34+ hours to finish 1 Wu at 6.3 AR. And it has 192 mb of pc-100 ram in it!!

Man thats bad!:Q ,are you sure that K6-2 is running on a 100MHz FSB?,looking at the WU time it would seem to be on a 66MHz FSB

Btw my Pentium 233MMX@266 does average WU's in 30.5hrs ,I know the better FPU of the Pentium MMX's certainly helps there🙂.
It runs on a TX chipset ,76MHz FSB,CAS2,SDRAM.M/brd won't run at 83MHz FSB🙁
 
Back
Top