BOINC Account is open and a new Version 1.04 is out

[SirUlli]

so who has no Account to BOINC Astropulse go to this Side

http://setiboinc.ssl.berkeley.edu/ap/

and get one, and also the new Clinet Version 1.04 is there

http://setiboinc.ssl.berkeley.edu/ap/download/

but he can get a response for the Scheduler, i hope they fix this soon, or this Version is to new.

only for Info

regards
Sir Ulli

 

[Soggysocks]

So , Is this the replacement program for Seti at home?

 

[SirUlli]

Originally posted by: Soggysocks
So , Is this the replacement program for Seti at home?

no that is BOINC Astropulse, a new projekct from Berkeley the future at Seti tought

http://www.planetary.org/html/UPDATES/seti/SETI@home/Update_110501.htm

regards
Sir Ulli

 

[Spacehead]

Thanks for the information SirUlli.




Soggy,
AstroPulse is a different project than SETI, though it uses the same S@H data. They're reanalyzing the data to look for short period pulsars, or something like that.

 

[Soggysocks]

Ahhhhh, "Now I see" said the blind man to the deaf/mute :Q

 

[Idoxash]

So when is Team Anandtech going to have a team for it? I notice there is no team with that name. I'm going want to join some team but if Team Anandtech not going to do a team I prob just join Phoenix Rising but dang they already got memebers that's not even putting out points... hrm.

--IDD--

 

[Confused]

I have just created a team for us, named TeAm AnandTech

Windows 1.04


Confused

 

[Coolkid]

YAY!

Im second to join

 

[Confused]

Yeah, scheduler is down

I will keep it open and trying to connect every minute or so, and will see what happens

/me thought I was setting it up wrong :s

OK, how to get it (to at least try) to sign up for Astropulse:
Sign up and activate account
Download and install from link above
Go to Settings, Log in to project
Enter the URL of http://maggie.ssl.berkeley.edu/ap/ - THE ADDRESS EMAILED TO YOU IS WRONG - Remove the last t from the address emailed to you
Enter your Account key as emailed to you

Wait for it to connect once the Scheduler server is responding


Confused

 

[Coolkid]

I noticed that

 

[Idoxash]

I've kept the client open for a few hrs now and it still has not download any type of work unit. Hmm guess something might be wrong.

--IDD--

 

[JWMiddleton]

I just joined, but as others have said the Beta system is down.

This is the replacement client for SETI@Home. I sure hope the release client is easier to use! For those who have not seen it, you have to enter a URL for the project you want then a VERY long password string to start the client. I'm hoping that once you connect and get work that this authentication will cease. If not, and if this is how they plan to stop cheating then it will make it very hard to get the casual or corporate user involved.

 

[TAandy]

I've joined up.
Just waiting for something to happen

 

[Idoxash]

Originally posted by: JWMiddleton
I just joined, but as others have said the Beta system is down.

This is the replacement client for SETI@Home. I sure hope the release client is easier to use! For those who have not seen it, you have to enter a URL for the project you want then a VERY long password string to start the client. I'm hoping that once you connect and get work that this authentication will cease. If not, and if this is how they plan to stop cheating then it will make it very hard to get the casual or corporate user involved.

Yeah well at least it would help crack down on cheatting and don't allow teams to become so huge by useing 100s of computers that are not theres.

--IDD--

 

[TAandy]

Originally posted by: Confused
Yeah, scheduler is down

I will keep it open and trying to connect every minute or so, and will see what happens

/me thought I was setting it up wrong :s

OK, how to get it (to at least try) to sign up for Astropulse:
Sign up and activate account
Download and install from link above
Go to Settings, Log in to project
Enter the URL of http://setiboinc.ssl.berkeley.edu/ap/
Enter your Account key as emailed to you

Wait for it to connect once the Scheduler server is responding


Confused

Why have you got the address

http://setiboinc.ssl.berkeley.edu/ap/

when I got in my email

http://maggie.ssl.berkeley.edu/apt/

Are these different projects or has someone made a typo ?

 

[Confused]

BOINC couldn't get the main page for http://maggie.ssl.berkeley.edu/apt/.
Please check URL and try again


Using http://setiboinc.ssl.berkeley.edu/ap/ it at least tries to connect to the server!


Garry

 

[TAandy]

Originally posted by: Confused
BOINC couldn't get the main page for http://maggie.ssl.berkeley.edu/apt/.
Please check URL and try again


Using http://setiboinc.ssl.berkeley.edu/ap/ it at least tries to connect to the server!


Garry

I noticed that too.
Hmmmm??
I'll leave it running anyway and see what happens.

 

[Confused]

OK, just been looking on the OcUK forum, and methinks someone made a typo in the email that was sent out!

http://maggie.ssl.berkeley.edu/ap/ works (notice the lack of t) but again, no scheduler is replying.


Garry

 

[Idoxash]

*yawns

At this rate Anandtech won't be moving up much. Notice BBR? I notice they finally past the team as well in SETI 1. I guess there is no escaping them.

--IDD--

 

[titanmiller]

Good thing its only beta, if all of us cant figure it out, how are general computer users susposed to?

 

[Smoke]

Somebody let me know how, when, and if this works.

 

[TAandy]

Originally posted by: Smokeball
Somebody let me know how, when, and if this works.

We're off to Kilkee in County Clare at 6am tomorrow for the weekend so if nothing happens tonight I won't find out until some time on Monday

 

[TAandy]

After exiting and restarting, the http://maggie.ssl.berkeley.edu/ap/ address just changed to Astropulse Beta, + account name instead of blank space, but the messages tab says "No work from project"
<sigh>

 

[Spacehead]

Yeah, i was waiting to try this after more of the bugs have been worked out. I'm in no hurry

 

[Smoke]

The following is the "Message" stream I've received since downloading and attempting to sign on. Notice the last line.

BOINC - 07/11/03 13:36:51 - Starting BOINC client version 1.04
BOINC - 07/11/03 13:36:51 - Using default preferences
BOINC - 07/11/03 13:36:51 - Running CPU benchmarks
BOINC - 07/11/03 13:36:52 - Suspending activity - running CPU benchmarks
BOINC - 07/11/03 13:37:02 - CPU benchmarks complete
BOINC - 07/11/03 13:37:02 - Resuming activity
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:38:01 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:38:03 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:38:03 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:38:03 - Deferring communication with project for 60 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:39:03 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:39:05 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:39:05 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:39:05 - Deferring communication with project for 60 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:40:05 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:40:07 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:40:07 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:40:07 - Deferring communication with project for 60 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:41:07 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:41:09 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:41:09 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:41:09 - Deferring communication with project for 60 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:42:09 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:42:11 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:42:11 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:42:11 - Deferring communication with project for 111 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:44:02 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:44:04 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:44:04 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:44:04 - Deferring communication with project for 312 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:49:16 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:49:18 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:49:18 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:49:18 - Deferring communication with project for 581 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:58:59 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:59:01 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:59:01 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 13:59:01 - Deferring communication with project for 1627 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:26:08 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:26:13 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:26:13 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:26:13 - Deferring communication with project for 303 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:31:16 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:31:18 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi failed
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:31:18 - No schedulers responded
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 14:31:18 - Deferring communication with project for 6675 seconds
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 16:22:33 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi
http://maggie.ssl.berkeley.edu/ap/ - 07/11/03 16:22:36 - scheduler RPC to http://setiboinc.ssl.berkeley.edu/ap_cgi/cgi succeeded
Astropulse Beta - 07/11/03 16:22:36 - Invalid or missing account ID. Visit this project's web site to get an account ID.


When I go to the Account Creation page I got this message:

Astropulse

Account creation is disabled
Sorry, this project has disabled the creation of new accounts. Please try again later.