Well is there some way to make my computer's numbercrunching SETI workunits more efficiently I would be glad to know. I use Mac OS X 10.4.7 on a PowerPC G5 with two 2.7 GHz processors and Darwin 8.7.0 core.
Neubaum

---

Well is there some way to make my computer's numbercrunching SETI workunits more efficiently I would be glad to know. I use Mac OS X 10.4.7 on a PowerPC G5 with two 2.7 GHz processors and Darwin 8.7.0 core.

You could install Alex Kan’s G5-optimized application, which is more than twice as fast as the standard version on my dual-core 2.3-GHz G5. If you do, though, it will be your responsibility to keep it up to date, as BOINC won’t automatically download any new versions that are issued by the project in future. See the New Optimized Apps thread in the Number Crunching forum; look for Alex’s download links for the v6-g5 and v6-g5-nographics (slightly faster, but without the screensaver) applications. Quit BOINC, copy the contents of the archive into the S@h folder (in Library/Application Support/BOINC Data/projects/) and relaunch BOINC.

---

Well is there some way to make my computer's numbercrunching SETI workunits more efficiently I would be glad to know. I use Mac OS X 10.4.7 on a PowerPC G5 with two 2.7 GHz processors and Darwin 8.7.0 core.

You could install Alex Kan’s G5-optimized application, which is more than twice as fast as the standard version on my dual-core 2.3-GHz G5. If you do, though, it will be your responsibility to keep it up to date, as BOINC won’t automatically download any new versions that are issued by the project in future. See the New Optimized Apps thread in the Number Crunching forum; look for Alex’s download links for the v6-g5 and v6-g5-nographics (slightly faster, but without the screensaver) applications. Quit BOINC, copy the contents of the archive into the S@h folder (in Library/Application Support/BOINC Data/projects/) and relaunch BOINC.

Thank you Odysseus, but I'm afraid I've got no Intels inside my computer and that seems to be a requirement for using Alex's applications. But I'll look for applications with a ppc-prefix. By the way how do you put those cool stats in your signature. My greetings to Penelope,
Neubaum

---

[…] I’ve got no Intels inside my computer and that seems to be a requirement for using Alex's applications.

Not at all, although he makes “i386” versions as well. I'm running his “seti_enhanced-ppc-v6” apps on my G5 at home, and on three G4s at work.

But I'll look for applications with a ppc-prefix.

The names of both the archives and the executable files have “-ppc-” in them, but the links in that thread just say “-g4-” or “-g5-”. While I’m going back to check, though, I might as well copy-and-paste download links to the v6 (~= S@h Enhanced v5.13) G5 .zip files: the earlier version with and the later version without screensaver graphics.

By the way how do you put those cool stats in your signature.

I see that you’ve found BOINCstats. There’s a (partial?) list of providers of sig-graphics somewhere around here; offhand I’m not sure whether it’s under Statistics or Community, but it shouldn’t be too hard to find. I chose Neil Munday’s because they let me use my own background images—I made a different ‘team icon’ for each of my projects. (There may be other sites that let you do that as well now, but when I set it up that was the only one I could find.) You have to register an account at the site to configure the graphics.

My greetings to Penelope,

You may see her before I do. ;)

---

[…] I’ve got no Intels inside my computer and that seems to be a requirement for using Alex's applications.

Not at all, although he makes “i386” versions as well. I'm running his “seti_enhanced-ppc-v6” apps on my G5 at home, and on three G4s at work.

But I'll look for applications with a ppc-prefix.

The names of both the archives and the executable files have “-ppc-” in them, but the links in that thread just say “-g4-” or “-g5-”. While I’m going back to check, though, I might as well copy-and-paste download links to the v6 (~= S@h Enhanced v5.13) G5 .zip files: the earlier version with and the later version without screensaver graphics.

By the way how do you put those cool stats in your signature.

I see that you’ve found BOINCstats. There’s a (partial?) list of providers of sig-graphics somewhere around here; offhand I’m not sure whether it’s under Statistics or Community, but it shouldn’t be too hard to find. I chose Neil Munday’s because they let me use my own background images—I made a different ‘team icon’ for each of my projects. (There may be other sites that let you do that as well now, but when I set it up that was the only one I could find.) You have to register an account at the site to configure the graphics.

My greetings to Penelope,

You may see her before I do. ;)

I'm far from Ithaka at the moment so it may take a while. Anyhow I downloaded the zip-archive and unzipped a folder with "seti_enhanced-ppc-v6 plus" and some textfiles in it. Should I copy that folder into the S@h folder (in Library/Application Support/BOINC Data/projects/) or just the "exe-file"? Why do they put a exe-logo in the icon — because Tiger is Unixfied I guess, but it still scares me as I'm not used to tinker with OS X, to say the least. — One last (I hope) question. Can I count on Berkeley informing about new versions of BOINCManager ? I guess I must check if there may be any problem with Kan's application before I install a new version of BOINCManager. If so, do I just take his application out of the s@h-folder again and wait and see if he may uppgrade?
Neubaum

---

Anyhow I downloaded the zip-archive and unzipped a folder with "seti_enhanced-ppc-v6 plus" and some textfiles in it. Should I copy that folder into the S@h folder (in Library/Application Support/BOINC Data/projects/) or just the "exe-file"? Why do they put a exe-logo in the icon — because Tiger is Unixfied I guess, but it still scares me as I'm not used to tinker with OS X, to say the least.

Once it’s installed and running the icon will turn into a pretty green dish. I’m a novice when it comes to the Unix-y aspects of X, too, but I muddle along … It’s my impression that all binaries whose nature is unknown to the system get the Terminal icon at first.

The files must go directly into projects/setiathome.berkeley.edu/, not enclosed in their ‘shipping folder’. The text files don’t do anything (they’re required to be distributed with the app, under the terms of Berkeley’s open-source GNU licensing) but the app_info.xml file is vital. That’s what tells BOINC Manager to use seti_enhanced_ppc_v6 for work that would normally be assigned to setiathome_5.13_powerpc-apple-darwin. Remember to quit BOINC completely before you do anything to its files. (It’s not a bad idea to back up the entire BOINC Data folder, in case anything goes wrong.)

One last (I hope) question. Can I count on Berkeley informing about new versions of BOINCManager ? I guess I must check if there may be any problem with Kan's application before I install a new version of BOINCManager. If so, do I just take his application out of the s@h-folder again and wait and see if he may uppgrade?
Neubaum

I imagine any optimized app will be tested on all available versions of BOINC before release, but if there are problems they will very likely be mentioned by users here or in the Number Crunching forum. Berkeley takes no responsibility for the maintenance of third-party applications. I’ve only been doing SETI/BOINC for a few months, but I’ve never heard of a significant incompatibility between any BOINC version and any science app, except that BOINC versions older than v5.2.6 don’t support S@h Enhanced’s method of claiming credit, using benchmarks instead. (The quorum system usually prevents this from affecting the amount granted.)

If Berkeley releases a new S@h Enhanced version that isn’t compatible with v5.13, the servers will stop sending you work. There may well be a new optimized version available by that time or shortly afterward, in which case it will just be a matter of downloading the new app and then substituting it, with its app_info.xml file, for the old versions. Otherwise you’ll have to switch back to the standard app.

To stop using an optimized app, quit BOINC and remove the app_info.xml file; on relaunch BOINC should continue using the optimized app for the work it has already cached (if any), but next time it gets new work it will automatically download the current standard app. As an extra precaution, to be absolutely sure no work will be lost: set the project to “No new tasks”, wait for all the cached work to be completed, Update the project to get it all reported, then quit, make your changes, and “Allow new tasks” on relaunching. (You may wish to do the same before installing the optimized version, but it shouldn’t be necessary in either case—however, a little pessimism can be healthy.)

---

Anyhow I downloaded the zip-archive and unzipped a folder with "seti_enhanced-ppc-v6 plus" and some textfiles in it. Should I copy that folder into the S@h folder (in Library/Application Support/BOINC Data/projects/) or just the "exe-file"? Why do they put a exe-logo in the icon — because Tiger is Unixfied I guess, but it still scares me as I'm not used to tinker with OS X, to say the least.

Once it’s installed and running the icon will turn into a pretty green dish. I’m a novice when it comes to the Unix-y aspects of X, too, but I muddle along … It’s my impression that all binaries whose nature is unknown to the system get the Terminal icon at first.

The files must go directly into projects/setiathome.berkeley.edu/, not enclosed in their ‘shipping folder’. The text files don’t do anything (they’re required to be distributed with the app, under the terms of Berkeley’s open-source GNU licensing) but the app_info.xml file is vital. That’s what tells BOINC Manager to use seti_enhanced_ppc_v6 for work that would normally be assigned to setiathome_5.13_powerpc-apple-darwin. Remember to quit BOINC completely before you do anything to its files. (It’s not a bad idea to back up the entire BOINC Data folder, in case anything goes wrong.)

One last (I hope) question. Can I count on Berkeley informing about new versions of BOINCManager ? I guess I must check if there may be any problem with Kan's application before I install a new version of BOINCManager. If so, do I just take his application out of the s@h-folder again and wait and see if he may uppgrade?
Neubaum

I imagine any optimized app will be tested on all available versions of BOINC before release, but if there are problems they will very likely be mentioned by users here or in the Number Crunching forum. Berkeley takes no responsibility for the maintenance of third-party applications. I’ve only been doing SETI/BOINC for a few months, but I’ve never heard of a significant incompatibility between any BOINC version and any science app, except that BOINC versions older than v5.2.6 don’t support S@h Enhanced’s method of claiming credit, using benchmarks instead. (The quorum system usually prevents this from affecting the amount granted.)

If Berkeley releases a new S@h Enhanced version that isn’t compatible with v5.13, the servers will stop sending you work. There may well be a new optimized version available by that time or shortly afterward, in which case it will just be a matter of downloading the new app and then substituting it, with its app_info.xml file, for the old versions. Otherwise you’ll have to switch back to the standard app.

To stop using an optimized app, quit BOINC and remove the app_info.xml file; on relaunch BOINC should continue using the optimized app for the work it has already cached (if any), but next time it gets new work it will automatically download the current standard app. As an extra precaution, to be absolutely sure no work will be lost: set the project to “No new tasks”, wait for all the cached work to be completed, Update the project to get it all reported, then quit, make your changes, and “Allow new tasks” on relaunching. (You may wish to do the same before installing the optimized version, but it shouldn’t be necessary in either case—however, a little pessimism can be healthy.)

Thanks for a very informative answer. I've now told s@h not to send me more jobs and wait for those allready delivered to be crunched through until I go on and install my new applicication. (By the way what is that kind of application called that dwells in the library and adds to, or replaces, some of the funcionality of another application?) On my way of doing this I unfortunatley tried pausing the ongoing crunching of two work-units and caused a freezeing of one of them (it was said to be "removed from the memory", but I've put my SOS into another thread so you don't risk beeing completely weared out from trying to curtail my ignorance.

---

Anyhow I downloaded the zip-archive and unzipped a folder with "seti_enhanced-ppc-v6 plus" and some textfiles in it. Should I copy that folder into the S@h folder (in Library/Application Support/BOINC Data/projects/) or just the "exe-file"? Why do they put a exe-logo in the icon — because Tiger is Unixfied I guess, but it still scares me as I'm not used to tinker with OS X, to say the least.

Once it’s installed and running the icon will turn into a pretty green dish. I’m a novice when it comes to the Unix-y aspects of X, too, but I muddle along … It’s my impression that all binaries whose nature is unknown to the system get the Terminal icon at first.

The files must go directly into projects/setiathome.berkeley.edu/, not enclosed in their ‘shipping folder’. The text files don’t do anything (they’re required to be distributed with the app, under the terms of Berkeley’s open-source GNU licensing) but the app_info.xml file is vital. That’s what tells BOINC Manager to use seti_enhanced_ppc_v6 for work that would normally be assigned to setiathome_5.13_powerpc-apple-darwin. Remember to quit BOINC completely before you do anything to its files. (It’s not a bad idea to back up the entire BOINC Data folder, in case anything goes wrong.)

One last (I hope) question. Can I count on Berkeley informing about new versions of BOINCManager ? I guess I must check if there may be any problem with Kan's application before I install a new version of BOINCManager. If so, do I just take his application out of the s@h-folder again and wait and see if he may uppgrade?
Neubaum

I imagine any optimized app will be tested on all available versions of BOINC before release, but if there are problems they will very likely be mentioned by users here or in the Number Crunching forum. Berkeley takes no responsibility for the maintenance of third-party applications. I’ve only been doing SETI/BOINC for a few months, but I’ve never heard of a significant incompatibility between any BOINC version and any science app, except that BOINC versions older than v5.2.6 don’t support S@h Enhanced’s method of claiming credit, using benchmarks instead. (The quorum system usually prevents this from affecting the amount granted.)

If Berkeley releases a new S@h Enhanced version that isn’t compatible with v5.13, the servers will stop sending you work. There may well be a new optimized version available by that time or shortly afterward, in which case it will just be a matter of downloading the new app and then substituting it, with its app_info.xml file, for the old versions. Otherwise you’ll have to switch back to the standard app.

To stop using an optimized app, quit BOINC and remove the app_info.xml file; on relaunch BOINC should continue using the optimized app for the work it has already cached (if any), but next time it gets new work it will automatically download the current standard app. As an extra precaution, to be absolutely sure no work will be lost: set the project to “No new tasks”, wait for all the cached work to be completed, Update the project to get it all reported, then quit, make your changes, and “Allow new tasks” on relaunching. (You may wish to do the same before installing the optimized version, but it shouldn’t be necessary in either case—however, a little pessimism can be healthy.)

Thanks for a very informative answer. I've now told s@h not to send me more jobs and wait for those allready delivered to be crunched through until I go on and install my new applicication. (By the way what is that kind of application called that dwells in the library and adds to, or replaces, some of the funcionality of another application?) On my way of doing this I unfortunatley tried pausing the ongoing crunching of two work-units and caused a freezeing of one of them (it was said to be "removed from the memory", but I've put my SOS into another thread so you don't risk beeing completely weared out from trying to curtail my ignorance.

Well, now I'm here again, asking about "Waiting for WUs" (could be a jazz-tune). After having crunched on a never emptying stack of WUs since my Dual G5 started on August 19th, it suddenly was forced to wait, and when I manually sent a request for more WUs I was told that "... Not sending work - last request too recent: 571 sec". Why's that? There have until now allways been one or two WUs wainting to be crunched. Could this imbalance between demand and supply on the WU market somehow be caused by the raised crunchingspeed due to Alex Kan’s G5-optimized application. How do I do to correct that? By changing some parameter in the preferences? Or will s@h/BOINC notify the increase in demand and take measures. When I got another three WUs at last, after allmost half an hour, there could also be read in the message pad that I had been "requesting 18839 seconds of new work" so somehow my crunching-capacity is measured up. Well we see.

---

Well, now I'm here again, asking about "Waiting for WUs" (could be a jazz-tune). After having crunched on a never emptying stack of WUs since my Dual G5 started on August 19th, it suddenly was forced to wait, and when I manually sent a request for more WUs I was told that "... Not sending work - last request too recent: 571 sec". Why's that? There have until now allways been one or two WUs wainting to be crunched. Could this imbalance between demand and supply on the WU market somehow be caused by the raised crunchingspeed due to Alex Kan’s G5-optimized application. How do I do to correct that? By changing some parameter in the preferences? Or will s@h/BOINC notify the increase in demand and take measures. When I got another three WUs at last, after allmost half an hour, there could also be read in the message pad that I had been "requesting 18839 seconds of new work" so somehow my crunching-capacity is measured up. Well we see.

It does take BOINC a while to adjust to changes in crunching efficiency. For safety’s sake, it’s slower to increase its demands for work when times drop than it is to decrease them when times rise. Since S@h’s WUs are quite variable in length and not easy to estimate in advance, your increased productivity will be masked to a degree, at first, but BOINC should adapt over the next few days.

The SETI@home servers are taken off-line for maintenance for a few hours every Tuesday morning (Berkeley time), which may have contributed to your delay in getting work today. If you join another project you can be sure your system will always have something to do during outages; otherwise, you can increase the “connect every X days” setting in your preferences, which will cause BOINC to cache more work and make it less likely that you’ll run out if your system can’t ‘phone home’ for a day or two.

---

[…] I unfortunatley tried pausing the ongoing crunching of two work-units and caused a freezeing of one of them (it was said to be "removed from the memory" […]

Just a note on this: if you have a comfortable amount of RAM on your system, you can set your preferences to “keep applications in memory” without hurting performance in other activities. This lets the app resume more smoothly and quickly after being interrupted. Some projects’ apps require this preference to be turned on, because otherwise they can lose track of their place in the current WU or fail to account for the time correctly. AFAIK that doesn’t apply to S@h, but unless your other programs consume all of your available RAM, it can’t hurt.

---

I've got a new problem I'm afraid. Following a suggestion of your's I attached to another project — s@hβ —by the command in BOINCs tools-menu and from then on no new s@hWUS were accepted to be delivered. Every request for new tasks was denied and accompanied by redline-messages in the Messages-pan. I cannot memorize those messages I'm afraid, because after I later quitted and restarted BOINC (to change language to Enlish) there had been a replacement of the former list of messages with the one added below (A). I've now stopped BOINC from delivering new tasks to any of the two projects and at the moment my Mac is crunching the last s@hβWU with a pace that curiously seems as swift as formerly the enhanced s@h-crunching. What am I to do? Replace "setiathome-5.17.powerpc-apple-darwin" in the s@hβ-folder with "seti_enhanced-ppc-v6" plus the "app_info.xml" from my backup? — I resumed connection with s@h for a moment and asked for more tasks just to show you what the red lines look like. See below (B). May it be that some instruction in one of the xml-files in ../BOINC data/Projects/ added or changed by installing s@hβ overrides the proper use of "app_info.xml" in the s@h-folder?

(A) "Thu Aug 31 21:11:19 2006||Starting BOINC client version 5.4.9 for powerpc-apple-darwin
Thu Aug 31 21:11:19 2006||libcurl/7.15.3 OpenSSL/0.9.7i zlib/1.2.3
Thu Aug 31 21:11:19 2006||Data directory: /Library/Application Support/BOINC Data
Thu Aug 31 21:11:19 2006|SETI@home|Found app_info.xml; using anonymous platform
Thu Aug 31 21:11:19 2006||Processor: 2 Power Macintosh PowerMac7,3
Thu Aug 31 21:11:19 2006||Memory: 1.50 GB physical, 0 bytes virtual
Thu Aug 31 21:11:19 2006||Disk: 233.64 GB total, 159.29 GB free
Thu Aug 31 21:11:19 2006|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2615602; location: home; project prefs: default
Thu Aug 31 21:11:19 2006|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 9029; location: ; project prefs: default
Thu Aug 31 21:11:19 2006||General prefs: from SETI@home (last modified 2006-08-30 08:36:19)
Thu Aug 31 21:11:19 2006||General prefs: no separate prefs for home; using your defaults
Thu Aug 31 21:11:19 2006||Listening on port 31416
Thu Aug 31 21:11:19 2006|SETI@home Beta Test|Resuming task 02ap05aa.3731.2145.342308.3.238_3 using setiathome_enhanced version 517"

(B) "Thu Aug 31 22:08:34 2006|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Thu Aug 31 22:08:34 2006|SETI@home|Reason: Requested by user
Thu Aug 31 22:08:34 2006|SETI@home|Requesting 8640 seconds of new work
Thu Aug 31 22:08:39 2006|SETI@home|Scheduler request succeeded
Thu Aug 31 22:08:39 2006|SETI@home|State file error: no application version setiathome_enhanced 517
Thu Aug 31 22:08:39 2006|SETI@home|Can't handle task 02my06ab.4663.6800.459638.3.111 in scheduler reply
Thu Aug 31 22:08:39 2006|SETI@home|State file error: no application version setiathome_enhanced 517
Thu Aug 31 22:08:39 2006|SETI@home|Can't handle task 01my06aa.7491.21472.140892.3.21 in scheduler reply
Thu Aug 31 22:08:39 2006|SETI@home|State file error: missing task 02my06ab.4663.6800.459638.3.111
Thu Aug 31 22:08:39 2006|SETI@home|Can't handle task 02my06ab.4663.6800.459638.3.111_2 in scheduler reply
Thu Aug 31 22:08:39 2006|SETI@home|State file error: missing task 01my06aa.7491.21472.140892.3.21
Thu Aug 31 22:08:39 2006|SETI@home|Can't handle task 01my06aa.7491.21472.140892.3.21_3 in scheduler reply"

---

I've got a new problem I'm afraid. Following a suggestion of your's I attached to another project — s@hβ —by the command in BOINCs tools-menu and from then on no new s@hWUS were accepted to be delivered. Every request for new tasks was denied […]

Thu Aug 31 22:08:39 2006|SETI@home|State file error: no application version setiathome_enhanced 517

You just had to pick that one, didn’t you! ;)

There’s a known bug (which I gather has been fixed in an alpha version of BOINC, yet to be officially released) where BOINC gets confused by having two project apps with the same name but different version numbers, despite the fact that they belong to different projects and reside in different folders. There are a few threads about it in the Number Crunching forums, here and at S@h Beta/Astropulse. The simplest solution is to edit the app_info.xml file that came with Alex Kan’s cruncher; if you make it look exactly like the one I posted in Beta NC you should be back in business. Stop BOINC, edit the file to add the <app_version> section for v5.17 (using TextEdit or similar, saving it as plain text), and relaunch BOINC. Your optimized v5.13 results here will be shown in BOINC Manager as v5.17 and reported that way as well, but the output file will continue to identify them correctly as coming from Alex’s app.

Note that while the above errors were happening, the ‘rejected’ WUs will have been discarded, but they’ll still show up in your Results pages as being in progress. They’ll go away eventually, after their deadlines have passed and other hosts have processed them. When the problem hit my G4 at work (when Beta v5.17 first came out) it was a long weekend here, so I was confronted with a daunting list of failures the next Tuesday morning … I’m still seeing more than a dozen of them, but they’re due to expire on Sept. 2 & 3, so I shouldn’t have to look at them much longer.

---

I've got a new problem I'm afraid. Following a suggestion of your's I attached to another project — s@hβ —by the command in BOINCs tools-menu and from then on no new s@hWUS were accepted to be delivered. Every request for new tasks was denied […]

Thu Aug 31 22:08:39 2006|SETI@home|State file error: no application version setiathome_enhanced 517

You just had to pick that one, didn’t you! ;)

There’s a known bug (which I gather has been fixed in an alpha version of BOINC, yet to be officially released) where BOINC gets confused by having two project apps with the same name but different version numbers, despite the fact that they belong to different projects and reside in different folders. There are a few threads about it in the Number Crunching forums, here and at S@h Beta/Astropulse. The simplest solution is to edit the app_info.xml file that came with Alex Kan’s cruncher; if you make it look exactly like the one I posted in Beta NC you should be back in business. Stop BOINC, edit the file to add the <app_version> section for v5.17 (using TextEdit or similar, saving it as plain text), and relaunch BOINC. Your optimized v5.13 results here will be shown in BOINC Manager as v5.17 and reported that way as well, but the output file will continue to identify them correctly as coming from Alex’s app.

Note that while the above errors were happening, the ‘rejected’ WUs will have been discarded, but they’ll still show up in your Results pages as being in progress. They’ll go away eventually, after their deadlines have passed and other hosts have processed them. When the problem hit my G4 at work (when Beta v5.17 first came out) it was a long weekend here, so I was confronted with a daunting list of failures the next Tuesday morning … I’m still seeing more than a dozen of them, but they’re due to expire on Sept. 2 & 3, so I shouldn’t have to look at them much longer.

Hm ... I've done what I thought was right, but still have those red lines in return for my requests for WUs and they looks the same as before. Now I have restarted once more and am waiting for the next reply from s@h. For your information my original "app_info.xml" was read

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>seti_enhanced-ppc-v6</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

and below is the result of my changes according to your suggestions (I'm pretty sure). I pasted the new lines next to, and above, the bottom line of the original and got this

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>seti_enhanced-ppc-v6</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

And here are the red lines from one of my "updates"

"Fri Sep 1 20:39:05 2006|SETI@home|State file error: no application version setiathome_enhanced 517
Fri Sep 1 20:39:05 2006|SETI@home|Can't handle task 02my06ab.4663.14546.73576.3.197 in scheduler reply
Fri Sep 1 20:39:05 2006|SETI@home|State file error: no application version setiathome_enhanced 517
Fri Sep 1 20:39:05 2006|SETI@home|Can't handle task 01my06aa.7491.28913.804838.3.255 in scheduler reply
Fri Sep 1 20:39:05 2006|SETI@home|State file error: missing task 02my06ab.4663.14546.73576.3.197
Fri Sep 1 20:39:05 2006|SETI@home|Can't handle task 02my06ab.4663.14546.73576.3.197_3 in scheduler reply
Fri Sep 1 20:39:05 2006|SETI@home|State file error: missing task 01my06aa.7491.28913.804838.3.255
Fri Sep 1 20:39:05 2006|SETI@home|Can't handle task 01my06aa.7491.28913.804838.3.255_1 in scheduler reply
Fri Sep 1 20:39:05 2006|SETI@home|No work from project"

So, what could one say? :-(

---

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>seti_enhanced-ppc-v6</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

[…]

Fri Sep 1 20:39:05 2006|SETI@home|State file error: no application version setiathome_enhanced 517

So, what could one say? :-(

Your edited file looks just fine to me—exactly like mine, at least. Are you sure it was saved as plain text (without formatting, and not as RTF or similar), replacing the previous version? Using the same character-encoding as the original? If so, I’m at a loss to explain why it wouldn’t work.

If you open it with a browser (or some other application that parses or verifies XML), does it read “setiathome_enhanced seti_enhanced-ppc-v6 setiathome_enhanced 513 seti_enhanced-ppc-v6 setiathome_enhanced 517 seti_enhanced-ppc-v6” with nothing missing and nothing extraneous? If so, again the file itself would seem fine, implying that BOINC is unable to find or read it for some reason. All I can think of to suggest at the moment is to start over: remove the app_info file (with BOINC stopped), let BOINC download the standard app, verify that it’s back to normal—slow & steady—then have another try with Alex Kan’s app, this time using the new version of the app_info file to start with.

I’m going on vacation for a couple of weeks; I hope someone else can step in with some better advice. Sorry, and good luck!

---

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>seti_enhanced-ppc-v6</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

[…]

Fri Sep 1 20:39:05 2006|SETI@home|State file error: no application version setiathome_enhanced 517

So, what could one say? :-(

Your edited file looks just fine to me—exactly like mine, at least. Are you sure it was saved as plain text (without formatting, and not as RTF or similar), replacing the previous version? Using the same character-encoding as the original? If so, I’m at a loss to explain why it wouldn’t work.

If you open it with a browser (or some other application that parses or verifies XML), does it read “setiathome_enhanced seti_enhanced-ppc-v6 setiathome_enhanced 513 seti_enhanced-ppc-v6 setiathome_enhanced 517 seti_enhanced-ppc-v6” with nothing missing and nothing extraneous? If so, again the file itself would seem fine, implying that BOINC is unable to find or read it for some reason. All I can think of to suggest at the moment is to start over: remove the app_info file (with BOINC stopped), let BOINC download the standard app, verify that it’s back to normal—slow & steady—then have another try with Alex Kan’s app, this time using the new version of the app_info file to start with.

I’m going on vacation for a couple of weeks; I hope someone else can step in with some better advice. Sorry, and good luck!

Hi, whoever replaces Odysseus who has gone fishing. I checked the app_info.xml file shipped with Alex' ppc_v6 and which I had edited according to Odysseus suggestions, by opening it in my browser Safari, and the string seemed to match exactly the one Odysseus shows in his reply nr 413345. So I went on, quitted BOINC, removed the file from the s@h folder, restarted BOINC after having reinstalled the app from my backed up package. What happend after that is not quite retractable I'm afraid. I never tried to reinstall the ppc_v6 since the app seemed still to be residing in the s@h folder. Though Mac seemed to happily crunch both s@hWUs and s@hβWUs at the moment, in both cases using 517 that resided only in the s@hβ folder, there were some problems left wich I cannot remember now. As I would like to make a new install of ppc_v6 in s@h (and hopefully later in s@hβ) with the edited app_info.xml there from the beginning, as suggested by Odysseus, I was not saisfied with having the ppc-6 client left there. So I decided to remove the app and once more reinstall BOINC from my back-up package hoping the original client should now be installed in the s@h folder (as it should have allready been according to Odysseus) and it was, sort of, but another version 513 (?) of set_enhanced. I don't remember if 513 was the one originally shipped with s@h, before my "upgrading" to ppc_v6, or if it came when I attached to
s@hβ and the problems began. Anyhow both 513 and 517 figures in the ppc_v6's app_info.xml file. At the moment 513 governs Mac's crunching s@hWUs and 517 (as before) the s@hβWUs. If I look at the graphics I see some differences between 517 and 513 and the graphic showing the 513 grunching has features that I don't remember to have seen before. So the 513 is a new (but older?) player I guess.

Leaving the question of once more trying to "upgrade" to pp_v6, I would like to have the 517 client working with s@h as well, since it seems to do the job i another and (presumably) better way. How do I accomplish that? If I were not afraid of loosing my credits I'd consider start all over again. Deinstall BOINC etc.

By the way, how come that my signature BOINCstats has not uptaded since 29th?

---

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>seti_enhanced-ppc-v6</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>seti_enhanced-ppc-v6</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

[…]

Fri Sep 1 20:39:05 2006|SETI@home|State file error: no application version setiathome_enhanced 517

So, what could one say? :-(

Your edited file looks just fine to me—exactly like mine, at least. Are you sure it was saved as plain text (without formatting, and not as RTF or similar), replacing the previous version? Using the same character-encoding as the original? If so, I’m at a loss to explain why it wouldn’t work.

If you open it with a browser (or some other application that parses or verifies XML), does it read “setiathome_enhanced seti_enhanced-ppc-v6 setiathome_enhanced 513 seti_enhanced-ppc-v6 setiathome_enhanced 517 seti_enhanced-ppc-v6” with nothing missing and nothing extraneous? If so, again the file itself would seem fine, implying that BOINC is unable to find or read it for some reason. All I can think of to suggest at the moment is to start over: remove the app_info file (with BOINC stopped), let BOINC download the standard app, verify that it’s back to normal—slow & steady—then have another try with Alex Kan’s app, this time using the new version of the app_info file to start with.

I’m going on vacation for a couple of weeks; I hope someone else can step in with some better advice. Sorry, and good luck!

Hi, whoever replaces Odysseus who has gone fishing. I checked the app_info.xml file shipped with Alex' ppc_v6 and which I had edited according to Odysseus suggestions, by opening it in my browser Safari, and the string seemed to match exactly the one Odysseus shows in his reply nr 413345. So I went on, quitted BOINC, removed the file from the s@h folder, restarted BOINC after having reinstalled the app from my backed up package. What happend after that is not quite retractable I'm afraid. I never tried to reinstall the ppc_v6 since the app seemed still to be residing in the s@h folder. Though Mac seemed to happily crunch both s@hWUs and s@hβWUs at the moment, in both cases using 517 that resided only in the s@hβ folder, there were some problems left wich I cannot remember now. As I would like to make a new install of ppc_v6 in s@h (and hopefully later in s@hβ) with the edited app_info.xml there from the beginning, as suggested by Odysseus, I was not saisfied with having the ppc-6 client left there. So I decided to remove the app and once more reinstall BOINC from my back-up package hoping the original client should now be installed in the s@h folder (as it should have allready been according to Odysseus) and it was, sort of, but another version 513 (?) of set_enhanced. I don't remember if 513 was the one originally shipped with s@h, before my "upgrading" to ppc_v6, or if it came when I attached to
s@hβ and the problems began. Anyhow both 513 and 517 figures in the ppc_v6's app_info.xml file. At the moment 513 governs Mac's crunching s@hWUs and 517 (as before) the s@hβWUs. If I look at the graphics I see some differences between 517 and 513 and the graphic showing the 513 grunching has features that I don't remember to have seen before. So the 513 is a new (but older?) player I guess.

Leaving the question of once more trying to "upgrade" to pp_v6, I would like to have the 517 client working with s@h as well, since it seems to do the job i another and (presumably) better way. How do I accomplish that? If I were not afraid of loosing my credits I'd consider start all over again. Deinstall BOINC etc.

By the way, how come that my signature BOINCstats has not uptaded since 29th?

OK, the signature's stats are upgraded now. It just takes some time I suppose. Anyhow, I'd like (1) to have the 517 client crunching my s@hWUs as it was once. I'd like (2) to accomplish that without problems due to continuing crunching my s@hβWUs with 517, as Mac has done satisfactorily all the time. If this cannot be done I'm prepared to quit s@hβ if that would help and attach to s@hβ later. The point is to avoid any problems due to the bug mentioned by Odysseus in his message above, ID: 412401. (3) If leaving s@hβ completely (with no traces left on my computer) is my only safe option, how do I do it? Should I just press the "Detach" button or am I better to "Reset" (if its nessecary to get rid of the s@hβ folder in the ~/Library). Is there still something to be done "by hand"? (4) It would be nice to have my creds at Seti BETA kept safe and added when I attach again. But I guess that cannot be done unless I can stick to the same account number in the s@hβ project. All this is really beyond my horizon.
As to a new effort "upgrading" to ppc_v6 it must wait so I can have some sleep.

---