It's a UNIX executable.
If you look at the permissions in the terminal you'll see a trailing -x.

To execute in the terminal type:
./S@h_Uninstall_Script
or
sh S@h_Uninstall_Script

You'll be prompted to override permissions unless you modify the script... ;)

[I couldn't get the uninstall script to run, though ... it kept asking what application to use to open it.

I've been playing with that, and it's one of those "OS X is really Unix" things that drive me nuts. There is _no_ metadata or extension or assigned application on that script; when _I_ do a "get info", it says it's a "unix script", but I have no idea how the system knows that. If I change it in any way, it turns into a plain text file, or worse yet a "document". I can't open it either before or after editing in Terminal, but if I open it with TextEdit, copy the contents, then _paste_ them in Terminal, it works...

Find file and dragging to trash and rebooting is frankly easier than figuring out how to make a "unix script" work when it doesn't want to.

In the "Commands" menu, there are choices for "Run always", "Run based on preferences', and "Suspend". The message you're getting means that is either set for "Suspend", or you have set the preferences on the website such that it isn't able to run right now. Either because of a time span you've set, or because you've said not to run when the computer is busy. For debugging, I recommend "Run always".

If, with "Run always", any projects or work has a status of "Suspended", you can hit the "Resume" button. Unless you've hit the "Suspend" button for that project or work unit, that shouldn't be necessary.

Thanks Bill. It's all good now. I also searched for and deleted all "s@h" and "seti@h" files, then rebooted to get rid of the annoying warning that the classic SETI kept generating. I couldn't get the uninstall script to run, though ... it kept asking what application to use to open it. I tried ScriptEditor, but that wouldn't work.

---

In the "Commands" menu, there are choices for "Run always", "Run based on preferences', and "Suspend". The message you're getting means that is either set for "Suspend", or you have set the preferences on the website such that it isn't able to run right now. Either because of a time span you've set, or because you've said not to run when the computer is busy. For debugging, I recommend "Run always".

If, with "Run always", any projects or work has a status of "Suspended", you can hit the "Resume" button. Unless you've hit the "Suspend" button for that project or work unit, that shouldn't be necessary.

I thought I made the transition from classic to BOINC OK, but when I just tried to launch the screensaver it said activities were suspended. In the BOINC application it says the same thing and I can't view the graphics under the "work" tab. How do I "unsuspend" activitities and get it running again?

---