• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BOINC Account is open and a new Version 1.04 is out

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.
 
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--
 
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
 
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--
 
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.
 
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.
Click to expand...

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--
 
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
Click to expand...
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 ?😕
 
*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--
 
Originally posted by: Smokeball
Somebody let me know how, when, and if this works. 😉
Click to expand...

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 🙁
 
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.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top