I installed version 4 in readiness for when the project goes over. This is what I get when I reset the project with the new version (with personal details changed, of course!). I copied and pasted in the URL and account number from the account confirmation e-mail I got when I started BOINC 3.20, so they should be correct. I'm wondering if everyone is getting the same message before the project goes over to BOINC 4.05.

Computer-name:~ myname$ /Applications/setiathome-BOINC/boinc_4.05_powerpc-apple-darwin
2004-08-28 10:53:58 [---] Starting BOINC client version 4.05 for powerpc-apple-darwin
Enter the URL of the project: http://setiathome.berkeley.edu
You should have already registered with the project
and received an account key by email.
Paste the account key here: ****************etc
2004-08-28 10:55:00 [http://setiathome.berkeley.edu/] Project prefs: using your defaults
2004-08-28 10:55:00 [http://setiathome.berkeley.edu/] Host ID not assigned yet
2004-08-28 10:55:00 [---] No general preferences found - using BOINC defaults
2004-08-28 10:55:00 [---] Running CPU benchmarks
2004-08-28 10:55:00 [---] Suspending computation and network activity - running CPU benchmarks

- details of benchmarks are then given here -

2004-08-28 10:56:01 [---] Finished CPU benchmarks
2004-08-28 10:56:02 [---] Resuming computation and network activity
2004-08-28 10:56:02 [---] Insufficient work; requesting more
2004-08-28 10:56:03 [---] Insufficient work; requesting more
2004-08-28 10:56:03 [http://setiathome.berkeley.edu/] Requesting 17280 seconds of work
2004-08-28 10:56:03 [http://setiathome.berkeley.edu/] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] No schedulers responded
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] No schedulers responded
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] Deferring communication with project for 1 minutes and 0 seconds
2004-08-28 10:57:18 [http://setiathome.berkeley.edu/] Deferring communication with project for 1 minutes and 0 seconds
2004-08-28 10:58:18 [http://setiathome.berkeley.edu/] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2004-08-28 10:58:41 [http://setiathome.berkeley.edu/] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-08-28 10:58:41 [SETI@home] Message from server: To participate in this project, you must use major version 3 of the BOINC core client. Your core client is major version 4.

- fair enough. We've not been told it's started with version 4 -

BOINC failed to log in to http://setiathome.berkeley.edu/.
Please check your account ID and try again.
2004-08-28 10:58:41 [SETI@home] Resetting project
2004-08-28 10:58:41 [SETI@home] Detaching from project
Computer-name:~ myname$

- as there's no way the account ID is wrong, I'm hoping it will be OK when version 4 has started up.

You jumped the gun. While there is an announcement that they are ready for the new version, they had hardware issues and could not upgrade.

I haven't had work for the version 3 in the last 24 hours or so. They call it teething problems. Murphy's Law. Just when everything looks good to go, something wrong happens.

We have to allow them to get the kinks out. It is a waiting game.

> You jumped the gun. While there is an announcement that they are ready for the
> new version, they had hardware issues and could not upgrade.
>
> I haven't had work for the version 3 in the last 24 hours or so. They call it
> teething problems. Murphy's Law. Just when everything looks good to go,
> something wrong happens.
>
> We have to allow them to get the kinks out. It is a waiting game.

Yes, I realise it's not up and running yet, so wasn't surprised to get the message I should still be using version 3. As I've not had any WUs for 3 since I uploaded the last completed work several days ago, I thought I might just as well upgrade now as wait. Meanwhile, I'm still running SETI Classic as a screensaver which I always have been doing whenever BOINC hasn't had enough work available to give me anything.

What WAS bothering me was that it didn't recognise my account number and I was wondering if the same had happened to anyone else. I've seen in the Windows forum that someone has had the same problem when all they've done is re-install version 3, so goodness only knows what's happening!

As you say, Cheryl, it's a waiting game with BOINC.

It is too bad this project isn't being run like most software projects that have a large user base and multiple systems that must be integrated.

Instead of having a project plan that includes stress testing, load testing, hardware testing, etc. the SETI/BOINC project management allows developers to just put equipment and code into production and wait and see what happens. Of course Murphy's Law kicks in. What would one expect if you don't do full system testing? No one writes perfect code, that's why it is essential to have a stabilization and performance tuning phase of any rollout of a system before it goes into production. Otherwise, you force your end users into being the testers, and most end users aren't equipped to test or have the desire or skills to test. On top of that, direct communication between the end users and the project is awkward, terse, and seldom accurate. The "news" announcements are generally made late and seldom reflect what will happen. There is no way to report "bugs" directly to the developers and to get the status and resolution of the bug fixes.

This project is in dire need of professional project management. The technical side is probably excellent. The project planning, rollout criteria, test criteria, performance criteria etc. leave a lot to be desired.

>
> What WAS bothering me was that it didn't recognise my account number and I was
> wondering if the same had happened to anyone else. I've seen in the Windows
> forum that someone has had the same problem when all they've done is
> re-install version 3, so goodness only knows what's happening!
>
> As you say, Cheryl, it's a waiting game with BOINC.

It's working fine now and I've just had the new version of setiathome automatically downloaded along with my first WUs. Hurrah!

Pity we still don't have a GUI yet for Macs. I've got seticontrol but that's all there is for now by the look of things.