I have tried several times to download and run Boinc. NADA! (Running XP, Intel Pent, w/1gb mem)

Never once had a problem with Classic. With all of the other problems I see others write about, you might as well outsource Boinc to India with all of the rest of the computer jobs!

Credit for 682 units and over 20000 computer time hours gone.

And I thought I was being a part of something. Thanks!

---

But it is broke.

Trust me classics had its problems before as well. I still remember it was last year that there was a huge outage where my SETISPY cache ran dry despite being set with a 20 WU unit cache.

And dont forget those with screensaver client which many many people use, you would just sit idle with no work since you had no cache. At least BOINC overcomes this problem by allowing users to setup a cache in the standard client. Or if you happen to run another project, your really prepared for these outages.

Another thing abot the screensaver version, try running that with the screensaver running and tell me how long it takes to finish a WU. I know on my XP 2500 it was at least 8-10 times longer due to the load the pretty graphics put on the CPU. The BOINC versions was designed at least to offload the graphics to the GPU of the computer, causing little to no impact on WU crunch times.

Also some of the things that don't appear broken to us the volunteers were broken for those that actually use the info.

Users who would overclock their machine way past the ability to turn in useful results now no longer receive credit for their junk results.

The people at berkely discover they want to update something in the science app to speed up the completion times, or to tell the application to check for other info in the radio signals can now just release a new app that will automatically be updated by BOINC. With the classic version, you'd have to first go to the SETI@home website and see that a new client was released. Then you'd have to install it. Most people wouldn't do this also because the newer client might take longer to crunch a WU, and since all WUs were worth 1 point, they wouldn't see any reason to do more work for the same credit.

---

BOINC WIKI
Overclockers.com's Forum

Your credits aren't gone. They appear on your account page.

Account data for Mark Maurer

SETI@home member since 5 Nov 2003
Country United States
SETI@home classic workunits
as of 15 March 2005 543
SETI@home classic CPU time
as of 15 March 2005 17,231 hours

A final snapshot will be taken when classic is closed.

Your credits aren't gone. They appear on your account page.

Account data for Mark Maurer

SETI@home member since 5 Nov 2003
Country United States
SETI@home classic workunits
as of 15 March 2005 543
SETI@home classic CPU time
as of 15 March 2005 17,231 hours

A final snapshot will be taken when classic is closed.

According to my latest Seti@home Classic, it shows 682 units and 20137 hours. So now to my other problem....

I finally got Boinc loaded and it seems that it is crunching the data, but when I look at the messages, there are several that "Suspending work fetch because computer is overcommitted." Considering that Boinc is only using 28% of my ram and the cpu is being used at 100% since Boinc is the only thing running, I don't understand what is being overcommitted?

---

Read up on file fetch and over committed in the all knowing and all seeing BOINC WIKI>>>>>>>>>>

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.