Title says it all!! No doubt we'll find out what was wrong with 4.39 in due course.

---

Cheers,
Gary.

that was fast Gary, good job.

Warning: 4.40 is Developmental software, and as such, can do some funny things. Please stick with Official release software if you're not willing to take the risks.

4.39 was gone so quick it must have been maiming people...

<blockquote>that was fast Gary, good job.

Warning: 4.40 is Developmental software, and as such, can do some funny things. Please stick with Official release software if you're not willing to take the risks.

</blockquote>

Thanks for adding the warning early in the thread. I know what you mean by people thinking the advice that something is available is a command to go use it :(.

There must have been something seriously wrong with 4.39 for it to be replaced so quickly. Anybody who has installed 4.39 would probably be wise to upgrade really quickly. (or downgrade for that matter if the bleeding edge is a bit too bleeding :).

---

Cheers,
Gary.

4.39 didn't allow for attaching to new projects.

---

<blockquote>4.39 didn't allow for attaching to new projects. </blockquote>

HMMM, I had detached from burp a while ago. 4.39 just let me "Add new project", I then click the "no work" button.

<blockquote>HMMM, I had detached from burp a while ago. 4.39 just let me "Add new project", I then click the "no work" button.</blockquote>
Double Hmmmm.... I had been detached from Pirates for a while, just reattached...

Manual update works, Installation much smoother for me. so far so good.

tony

<blockquote>Title says it all!! No doubt we'll find out what was wrong with 4.39 in due course.</blockquote>

Ha ha ha ha.......

back to the drawing board....

---

I just install 4.40 and notice

5/12/2005 8:01:08 PM||Starting BOINC client version 4.37 for windows_intelx86
5/12/2005 8:01:08 PM||Data directory: C:\Program Files\BOINC

At least i thought it was 4.40, help about says its so. But message doesnt, O Well... maybe is 4.37 that wants to be 4.40. :) :)

---

BOINC SYNERGY is an International Team and We Welcome All BOINC Participants!
BOINC Synergy Click to Join BOINC Synergy

<blockquote>4.39 didn't allow for attaching to new projects. </blockquote>

Huh? Hmm, a quick test doesn't show any problems to attach to another project in v4.39...

Anyway, only changes in v4.40 is a bug-fix for one alpha-project that didn't clean out everything in slots-directory, parsing unused active_task-entries to avoid error-messages, and 2 bug-fixes for screensaver.

<blockquote><blockquote>4.39 didn't allow for attaching to new projects. </blockquote>

Huh? Hmm, a quick test doesn't show any problems to attach to another project in v4.39...</blockquote>
I took it from the dev_list. Not that many people read it or that anyone cares about it these days, unless it's between you dev&test people. :-(

---

<blockquote>I just install 4.40 and notice

5/12/2005 8:01:08 PM||Starting BOINC client version 4.37 for windows_intelx86
5/12/2005 8:01:08 PM||Data directory: C:Program FilesBOINC

At least i thought it was 4.40, help about says its so. But message doesnt, O Well... maybe is 4.37 that wants to be 4.40. :) :)

</blockquote>Oops... i was wrong, once i rebooted it now said 4.40, must been message from old 4.37....

---

BOINC SYNERGY is an International Team and We Welcome All BOINC Participants!
BOINC Synergy Click to Join BOINC Synergy

Martin, might have been a corrupted install, try shutting down puter and restarting. This is mine:

5/12/2005 9:58:10 PM||Starting BOINC client version 4.40 for windows_intelx86
5/12/2005 9:58:10 PM||Data directory: C:\Program Files\BOINC
5/12/2005 9:58:11 PM||Version Change Detected (4.39 -> 4.40); running CPU benchmarks

Just installed 4.40 on one machine, so far no problems...

I wonder if the screensaver fix(es) address this issue: (i hope..?)

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=14549

---

Looks good so far on Win98se and Win2kPro, with minor exceptions. Got rid of all my "Ready to Report" before I even managed to get the GUI initialized

if you suspend Boinc (which I still have to do on the Win2K box before anything else will start), after setting it back to Z"Run Based on Preferences" it says it is resuming, but the science app gets no time as reported in task manager.
maybe it's time for a clean install if W2K to see if that helps


One other thing. On Win99se, you have to close out BOINCMgr before Shutdown or Logoff will proceed. I don't remember that with 4.1x or 4.2x, but it has been around since 4.35. And I had to reboot the Win98 box before the science apps would start running. One (LHC) was labeled as "Running", but ProcessExplorer showed no cycles going to that app.

Why is everyone scrambling to development releases? Nothing above 4.2x is released.

So please, move the whole "I got 4.36 and it did this, I got 4.37 and it didn't do that, I got 4.40 and it did this and that" stuff to the proper place - the beta site!

The FACT that 4.39 and 4.40 both came out TODAY indicates that this stuff isn't ready for "prime time", and therefore, should be kept off the "prime time" forum, and most users should NOT install it.

I've seen countless threads from newbies who seem darn confused. It's simple - download the CC that is released, and don't bother with untested versions!

For those of you with untested versions that have a clue, report it to the proper place - the development/beta forums! You're just confusing the world by posting "4.40, 4.39, etc" crap to people who are just trying to get boinc/seti to work, and doing the project a great disservice.....

---

<blockquote>Why is everyone scrambling to development releases? Nothing above 4.2x is released.

So please, move the whole "I got 4.36 and it did this, I got 4.37 and it didn't do that, I got 4.40 and it did this and that" stuff to the proper place - the beta site!

The FACT that 4.39 and 4.40 both came out TODAY indicates that this stuff isn't ready for "prime time", and therefore, should be kept off the "prime time" forum, and most users should NOT install it.

I've seen countless threads from newbies who seem darn confused. It's simple - download the CC that is released, and don't bother with untested versions!

For those of you with untested versions that have a clue, report it to the proper place - the development/beta forums! You're just confusing the world by posting "4.40, 4.39, etc" crap to people who are just trying to get boinc/seti to work, and doing the project a great disservice.....</blockquote>

Not sure what you're going on about Woody. It doesn't look as if everybody is scrambling. There are a few that like to try out the new stuff and reporting what they find. Why is that such a bad thing?

Calling these posts a disservice to the project is just stupid. Sure, some new users might see a post that a new version is out and go to find it, (I like the concept of disclaimers at the start of the thread) but they have to scroll past the clearly marked recommended versions before they get to the clearly marked development versions. That should give them a clue, don't you think?

As for posting at the beta site, that's a great idea! Get them to turn it back on...

---

There is no Beta site. Nor is there an Alpha site, only an Alpha mailing list.
In the past the developers only released the alpha units to the alpha people and when nothing much between them went wrong, they released it to the public... Only to then find that it caused problems with this, that, that. left, right and middle.

So now alpha releases are available for us as well, for us to post problems with here, where the alpha people will read up on it and post it back to their masters (as you will ;)). Or try to ask us what we did with it, get us to make it better as well.

---

I certainly don't mind testing the new stuff as it comes out. To me it's part of the adventure...

Besides, the more people who are willing to test on different platforms, the quicker the bugs will be found, and the sooner everyone else will get the "real release".

You just have to be willing to risk losing your work, and possibly more. At my job, we put what we call a "scary warning message" in the splash screen for debug versions and such -- in the message it says "...unrecoverable file damage may result...". The same applies here.

---