Thanks for the feedback. I'm glad you found the instructions understandable.
It's good to see you back here posting again :). We need lots of people to help any ex-Seti classic users who might wander through here looking for help on how to get started with BOINC. It should become interesting as December 15 (or whenever final shutdown actually occurs) approaches :).
Thanks for the feedback. I'm glad you found the instructions understandable.
It's good to see you back here posting again :). We need lots of people to help any ex-Seti classic users who might wander through here looking for help on how to get started with BOINC. It should become interesting as December 15 (or whenever final shutdown actually occurs) approaches :).
Hi Gary. I've been faithfully reading the boards for all of my projects. Everyone's problems have been too complex for me to deal with. But I'll be ready and willing the help the ex-classic people when they arrive. I'm learning more everyday thanks to you all.
By the way, I have a quick question. I have a Rosetta result ready to report. Is there a change in the 5.x version that results don't report as soon as finished or is this a problem on my end?
I don't want to force it to upload if it is going to do it automatically at some point in the future.
By the way, I have a quick question. I have a Rosetta result ready to report. Is there a change in the 5.x version that results don't report as soon as finished or is this a problem on my end?
I don't want to force it to upload if it is going to do it automatically at some point in the future.
There has been a very rapid transition from 5.2.8 to 5.2.13 with several new versions coming out on the same day. Hopefully, things do seem to be slowing down a bit now.
Do people need to go through all these rapid version changes? Probably not!! It all depends on whether or not you are experiencing the problems that these new releases are attempting to solve.
With the impending demise of Seti Classic, the Seti/BOINC project has uncovered bugs in the installation and attaching to projects procedures which have been thrown up by the unusually high rate of new users trying to join the system. These problems are exacerbated by conditions of server overload. If you are an existing user, not experiencing any particular problems, wait until the dust settles and then make one upgrade to take advantage of the bug fixes that have occurred.
If you are about to join BOINC for the first time or if you are a recent arrival and you think you may be being affected by connection difficulties, sudden request for proxy information when you don't need to use a proxy, etc, please make sure that you are using the very latest version of BOINC, currently 5.2.13.
HI Gary,
This is NOT DIRECTED AT YOU! It is aimed at the developers, who have been spending a lot of time, but not thinking it through. Why are there so many new versions? For those of us just wanting to crunch data this is a particular bother! It looks like there has been an average of 1 or 2 new versions A WEEK! for the past several weeks. It wans't too long ago that 5.2.2 was the final version! What is going wrong with the delevopers? If Microsoft was doing this the world would be up in arms. Let a stable version emerge, before having everone use it!
Hi Joe,
I'm sure glad you mentioned that!! Otherwise I might have been heading off into the sunset with my tail between my legs :).
Quote:
Why are there so many new versions?
Actually, I thought I'd anticipated that complaint and already answered it!! :).
Quote:
For those of us just wanting to crunch data this is a particular bother! It looks like there has been an average of 1 or 2 new versions A WEEK! for the past several weeks. It wans't too long ago that 5.2.2 was the final version! What is going wrong with the delevopers? If Microsoft was doing this the world would be up in arms. Let a stable version emerge, before having everone use it!
I fully understand and sympathize with your point of view. However please note:-
1. If it ain't broke, don't fix it. If your version is working, stay with it.
2. If you were a new user just starting, wouldn't you like an immediate fix to a "just now" discovered problem?
3. If you were a "helper" (like me and many others) wouldn't you like to avoid having to keep explaining a problem to an evergrowing list of new users?
Please realise that the rapid fire releases have limited the damage to just those "early adopters" who came in around 5.2.7 or 5.2.8 through to 5.2.12. Hopefully all the new people joining each day and downloading 5.2.13 wont be so much of a "nightmare" for the helpers, unless some other "showstopper" is discovered, of course :).
Hi Kathryn, Thanks for the
)
Hi Kathryn,
Thanks for the feedback. I'm glad you found the instructions understandable.
It's good to see you back here posting again :). We need lots of people to help any ex-Seti classic users who might wander through here looking for help on how to get started with BOINC. It should become interesting as December 15 (or whenever final shutdown actually occurs) approaches :).
Cheers,
Gary.
RE: Hi Kathryn, Thanks for
)
Hi Gary. I've been faithfully reading the boards for all of my projects. Everyone's problems have been too complex for me to deal with. But I'll be ready and willing the help the ex-classic people when they arrive. I'm learning more everyday thanks to you all.
By the way, I have a quick question. I have a Rosetta result ready to report. Is there a change in the 5.x version that results don't report as soon as finished or is this a problem on my end?
I don't want to force it to upload if it is going to do it automatically at some point in the future.
Thanks in advance :)
Kathryn
edit for clarity
Kathryn :o)
Einstein@Home Moderator
RE: By the way, I have a
)
Kathryn,
This thread does a good job of explaining the new BOINC reporting process: Message boards : Cruncher's Corner : Updates.
Stick
Just noticed that 5.2.8 is
)
Just noticed that 5.2.8 is out.
Anyone having problems they think might be 5.2.7 specific might care to try the new release and let us know how it goes.
Cheers,
Gary.
BOINC Version 5.2.13 is now
)
BOINC Version 5.2.13 is now out.
There has been a very rapid transition from 5.2.8 to 5.2.13 with several new versions coming out on the same day. Hopefully, things do seem to be slowing down a bit now.
Do people need to go through all these rapid version changes? Probably not!! It all depends on whether or not you are experiencing the problems that these new releases are attempting to solve.
With the impending demise of Seti Classic, the Seti/BOINC project has uncovered bugs in the installation and attaching to projects procedures which have been thrown up by the unusually high rate of new users trying to join the system. These problems are exacerbated by conditions of server overload. If you are an existing user, not experiencing any particular problems, wait until the dust settles and then make one upgrade to take advantage of the bug fixes that have occurred.
If you are about to join BOINC for the first time or if you are a recent arrival and you think you may be being affected by connection difficulties, sudden request for proxy information when you don't need to use a proxy, etc, please make sure that you are using the very latest version of BOINC, currently 5.2.13.
Cheers,
Gary.
HI Gary, This is NOT
)
HI Gary,
This is NOT DIRECTED AT YOU! It is aimed at the developers, who have been spending a lot of time, but not thinking it through. Why are there so many new versions? For those of us just wanting to crunch data this is a particular bother! It looks like there has been an average of 1 or 2 new versions A WEEK! for the past several weeks. It wans't too long ago that 5.2.2 was the final version! What is going wrong with the delevopers? If Microsoft was doing this the world would be up in arms. Let a stable version emerge, before having everone use it!
Joe B
RE: HI Gary, This is
)
Hi Joe,
I'm sure glad you mentioned that!! Otherwise I might have been heading off into the sunset with my tail between my legs :).
Actually, I thought I'd anticipated that complaint and already answered it!! :).
I fully understand and sympathize with your point of view. However please note:-
1. If it ain't broke, don't fix it. If your version is working, stay with it.
2. If you were a new user just starting, wouldn't you like an immediate fix to a "just now" discovered problem?
3. If you were a "helper" (like me and many others) wouldn't you like to avoid having to keep explaining a problem to an evergrowing list of new users?
Please realise that the rapid fire releases have limited the damage to just those "early adopters" who came in around 5.2.7 or 5.2.8 through to 5.2.12. Hopefully all the new people joining each day and downloading 5.2.13 wont be so much of a "nightmare" for the helpers, unless some other "showstopper" is discovered, of course :).
Cheers,
Gary.