I got work now and it all seems to be ticking along nicely.

---

Maybe it can power a larger version of the abacus Travis will be sending out? :-P

Do the work of 4 abacus', you know... a quad core. :P

a 4-cylinder TA manually crunching 15 mw wu's an hour. ;)

If mine could crunch, there wouldn't be any for anybody else. It's got 455 ci, top that with your i7's & GPU's. ;P Then again I don't think I could afford that. :D

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Us wabbits are quite talented so we don't have your finger problem (there's a LOT of us!). A true wabbit would NOT nibble a bead. This is just not done, but we have just begun to use the optimized vermilion beads.

Although a quad abacus is nice, we soldier on with the HT version. The puce beads are proving to be useful. Unfortunately the bit bucket is getting full of puce beads. I think we need to purge the bucket more frequently. New work has been delayed while we argue about where it goes on the overfull abacus.

PS: Travis and Dave--Both of you are doing great work on a shoe string budget. Please take my comments in the spirit they were intended. I'm WAY off topic and deserve to be deleted--Beware of the wabbit angst tho. Besides Travis, you started it!

Down the rabbit hole

---

me@rescam.org

Project reset was a good idea, I should have looked here earlier. Couldn't get work for days but now my box is crunching away nicely. Still, I figure it overcommited itself rather heavily ;-)

A project reset can fix many problems. For my 1.3 GHz Celerons (Linux) it might be the kiss of death (or at least the kiss of hurt) tho. They have a DCF of 6. Any reset will result in an over fetch. For them it's days of extra work. Even my AMD64 5600+ X2 and AMD64 3800+ X2 (Linux) have a DCF of 3. Only my Q6600 and T8300 (Windows) are close to one. All are running an optimized app.

By all means reset the project if nothing is working, but be careful. You may get more than you bargained for :)