Unfortunatly M$ removed this command but ...

C:\\WINDOZE>CD\\
C:>DELTREE *.*
C:OS repaired>

Unfortunatly M$ removed this command but ...

C:\\WINDOZE>CD\\
C:>DELTREE *.*
C:OS repaired>

LOL!

---

Is that a genuine Pentium 60MHz computer? Does it have the FDIV bug?

Wow, that's really cool. I love the smell of old hardware in the morning!

There is more Opteron with Crashing/freezing bug out there than Pentium with FDIV bug.

who?
PS:that is the truth and from now on, will be my answer on the FDIV 15 years old bug. the Opteron Bug is only 1 years old.

There is more Opteron with Crashing/freezing bug out there than Pentium with FDIV bug.

who?
PS:that is the truth and from now on, will be my answer on the FDIV 15 years old bug. the Opteron Bug is only 1 years old.

who?:

You don't have to become defensive and point the fingers at the opposition every time someone mentions the fact that Intel screwed up a long time ago. It's not a personal attack against you nor Intel, but simply to mention a fact that happened no matter how long ago.

Come on! I love all x86 hardware. Political mud-slinging does nothing for the rest of us. It would be bigger of you to simply accept that it is a fact from over 15 years ago and people will talk about it and leave it be.

Besides, why would anyone bring up the Opteron bug in a thread specifically about the Pentium 60? That particular CPU did indeed have the FDIV bug and I was just wondering if his had it or not. It was a valid question and it was not meant to stir the pot.

---

153:26:27 cpu time
19.429%
135:15:04 to comp

did I mention that the mouse on this has NO ergo design, just two switches, NO scroll, NO buttons of any kind, and some funky black superball(that doesn't bounce much) inside it.

and some funky black superball(that doesn't bounce much) inside it.

LOL 8-)

---

153:26:27 cpu time
19.429%
135:15:04 to comp

did I mention that the mouse on this has NO ergo design, just two switches, NO scroll, NO buttons of any kind, and some funky black superball(that doesn't bounce much) inside it.

And No big "S" on It either, But It does work.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

153:26:27 cpu time
19.429%
135:15:04 to comp

Are you worried that it will run out of work before Thumper comes back?

LOL

---

Calm Chaos Forum...Join Calm Chaos Now

153:26:27 cpu time
19.429%
135:15:04 to comp

Are you worried that it will run out of work before Thumper comes back?

LOL

nope :), according to my calcs I still have 628 hours to go on this task, or 26.17 days. Deadline is still the 25th of May (18 days away).

according to my calcs I still have 628 hours to go on this task, or 26.17 days. Deadline is still the 25th of May (18 days away).

Any bets that this will still finish on time?

---

my farm has been in flux so I couldn't to some stuff easily. Now that I've got them all (except one) back into windows and my network is functioning, I put together a little progress chart.



now if I could just figure out how to make the x axis not be fixed to 1 unit/record, and have it scale to the numbers. This is why I collected the data at roughly the same time every morning and posted them. The funkiness in the first day is due to multiple records. After that it was recorded once/day.

Earlier I had mentioned I might be losing this machine to the needy inlaws kids. I fixed up (upgraded memory, installed CD writer, and a modem/sound combo card) a PII 400 Deschutes for them. So, I'll be able to play with this one as long as the smoke stays inside.

here's the benchmarks:

4/30/07 5:38:58 PM||[error] CPU benchmarks timed out, using default values
4/30/07 5:38:58 PM||[error] Benchmark: FP unexpectedly zero; ignoring
4/30/07 5:38:58 PM||[error] Benchmark: int unexpectedly zero; ignoring
4/30/07 5:38:58 PM||Benchmark results:
4/30/07 5:38:58 PM|| Number of CPUs: 1
4/30/07 5:38:58 PM|| 1000 floating point MIPS (Whetstone) per CPU
4/30/07 5:38:58 PM|| 1000 integer MIPS (Dhrystone) per CPU


this must be the ideal golden machine for benchamrks. Mr. Cobbs mythical standard.

OK

here's the second run:
4/30/07 5:44:28 PM||Running CPU benchmarks
4/30/07 5:44:29 PM||Suspending computation - running CPU benchmarks
4/30/07 5:45:30 PM||Benchmark results:
4/30/07 5:45:30 PM|| Number of CPUs: 1
4/30/07 5:45:30 PM|| 38 floating point MIPS (Whetstone) per CPU
4/30/07 5:45:30 PM|| 56 integer MIPS (Dhrystone) per CPU


anyone claime a lower benchmark????

Some time ago, I tried to get my old 486 (DX2 80MHz 64MB RAM) to crunch.


But after the benchmark results, BOINC/SETI refused to let this old shoebox do any crunching - it was estimated to be too slow.

---

"Are you suggesting coconuts migrate?"

Some time ago, I tried to get my old 486 (DX2 80MHz 64MB RAM) to crunch.

But after the benchmark results, BOINC/SETI refused to let this old shoebox do any crunching - it was estimated to be too slow.

It may have been the reported 61.09 MB of RAM. http://setiathome.berkeley.edu/sah_participate.php states 64MB min.

---

Sir Arthur C Clarke 1917-2008

64M ram was the min. I believe the newer enhanced will run on 32M(useable ram). Not to mention this puter only has 48M.

Update (with fancy new graphics)

Oooo.. that'll be nice to see if the completion % keeps progessing linearly, or speeds up toward the middle / end. The boinc prediction seems to be levelling off :D

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

64M ram was the min. I believe the newer enhanced will run on 32M(useable ram). Not to mention this puter only has 48M.

Before this thread, I thought I was pushing it with my 2 Win98 boxes. You can see all the results they have done on SETI Beta here. They have both run out of SETI main work now, last result finished on Friday night.

I thought you had 48MB, should have looked further up the thread :-)

You will get better results by using PNG or GIF instead of JPG for posting images with sharp edges.

Keith.

It may have been the reported 61.09 MB of RAM. http://setiathome.berkeley.edu/sah_participate.php states 64MB min.

Now that you mention it, I think that's what actually happened.

My initial efforts stranded due to a timeout during the CPU speed tests. I then picked up an optimized BOINC client, and was able to finish the performance tests, only to find that SETI@home required 64MB or more...

---

"Are you suggesting coconuts migrate?"