I have made the mistake suggested by boinc of upgrading to .24 which totally failed,
after a lot of hassel, a few days and Jim´s help I was able to download and open the 6.6.36
now I can not get it to run., it gives me the message of
"waiting for shared....."
could you give me a hand on this thank you

I think when you expand the Status column that the message is "Waiting for shared memory". In that case, check this FAQ, even when you don't see the error messages outlined in it.

---

yes that is the message, but I never had that problem before and have been using this computer for over five years with seti
could there be another side to this problem perhaps in the settings thank you

No. If you'd followed the link to the FAQ, you'd have found a link to where the actual help is given on this subject.

It says there specifically:

The amount of shared memory available on a Mac is configured at boot time. Once the shared memory system has been initialized it is not possible to change the shared memory configuration. At present the same amount of shared memory is configured on any Mac (about 4MB), regardless of the number of processors or the amount of total memory available.

So it's not a BOINC or projects problem, but one on the computer itself.

---

I'm having exactly the same problem, as described by the OP. Having checked the forums, I tried the fix detailed in the link Ageless posted - to no avail: project status is still stuck on 'Waiting for shared memory'. As with the OP, this was not a problem prior to being forced to downgrade. Any further suggestions gratefully received.

I'm having exactly the same problem, as described by the OP. Having checked the forums, I tried the fix detailed in the link Ageless posted - to no avail: project status is still stuck on 'Waiting for shared memory'. As with the OP, this was not a problem prior to being forced to downgrade. Any further suggestions gratefully received.

I see both Beata Dulko and pantera are running Power Mac's not Intel Mac's and single processor machines. Neither show the box indicating the projects to which they are attached. [I don't know if it doesn't show because they aren't attached or if it doesn't show for a single project.]

In any case if after applying the patch, a re-boot, and verifying as per the note in the patch that shared memory did increase and the fact you are both on Power Mac's I'm wondering if there is some real issue with the Power Mac code.

If I remember right, single processor, single project BOINC generally doesn't run more that one work unit at a time and therefore should not be able to run out of shared memory. (Of course something else you run on the machine might run it out, before BOINC can grab it.)

Scratching head.

---

[I don't know if it doesn't show because they aren't attached or if it doesn't show for a single project.]

It's the latter :-)

The list only shows if more than one project is attached (to at least one computer).

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Shared memory could be used by any application on the computer. When this problem occurs you need to consider the needs of any application that communicates between tasks. It might be informative to know which programs users with this problem have running on their system. Activity Monitor (found in the Applications>utilities folder) can be set to show shared memory usage. Just go under view>columns to turn the feature on. If you find something that takes more memory than the OS X applications you may have found the program causing the problem. Boinc only takes about 23mb on my system.

---

[…]I'm wondering if there is some real issue with the Power Mac code.

If there is, it’s only triggered in certain circumstances: I’ve never seen a “waiting for shared memory” message on my G5 or any of my G4s. (OTOH I’ve seen “could not attach shared memory” in messages related to failed communications with BOINC projects, which I take to refer to server-side problems.) Before increasing the shared memory on those of my hosts that are attached to numerous projects, I did occasionally get the -144 or -146 errors, so I’m not at all sure the problem here is the same.

---

[…]I'm wondering if there is some real issue with the Power Mac code.

If there is, it’s only triggered in certain circumstances: I’ve never seen a “waiting for shared memory” message on my G5 or any of my G4s. (OTOH I’ve seen “could not attach shared memory” in messages related to failed communications with BOINC projects, which I take to refer to server-side problems.) Before increasing the shared memory on those of my hosts that are attached to numerous projects, I did occasionally get the -144 or -146 errors, so I’m not at all sure the problem here is the same.

The "could not attach shared memory" message is in the messages tab and indicates a server side problem. The "waiting for shared memory" appears as the status under the tasks tab for the work unit. Normally it will clear by itself as soon as any running work unit completes. The OP didn't say but I got the strong impression he has no running work units.

As he did say he had to downgrade BOINC I suppose it is just possible, but unlikely, that the science app got trashed. IIRC a detach from the project and subsequent attach to project should force a download of the science app. Additional measures are needed to save work units in progress; same as needed when installing an optimized app.

---