The "BOINC API library" Bruce wrote about is that part of BOINC that gets linked into the App. So you don't need a new BOINC Core Client, you just need to download an install the new App, version 0.11, from the Test App page.
I think "The BOINC Monitor app" you were talking about is part of the "BOINC Stat Viewer"? Sorry, I'm not familiar with the various Add-ons and have to admit that I have no idea what exactly this "Checking" status means. Can anyone else help out?
Hm. Did you check the md5 sum of the package you downloaded? To me this "Checking" seems like the usual checking of the signature of the App. But as anonymous Apps doesn't have a signature, well, I don't really know what it's doing there.
You should be able to find and start the Activity Monitor (in /Applications/Utilities). Select the process you're interested in, click "inspect", then "sample". It should give you a "call stack" and a clue of what it's doing.
Yep. This is the freeze we expected with the 0.08 App, actually in __vfprintf().
You can do the following:
- Stop the BOINC client.
- Open the einstein project folder (where you put the files from the test package in)
- Delete the einstein_0.08_powerpc-apple-darwin App.
- Make a copy of the einstein_0.11_powerpc-apple-darwin App and name it einstein_0.08_powerpc-apple-darwin
- Start the client again.
He will actually use the 0.11 App (though running as 0.08) to finish the result.
It seems the fix from David Anderson was good enough for single-CPU machines, but I still get bug reports from dual ones. We're working on this, there will probably be another beta test version put up next week.
I have a single processor G4 (450mHz) but am getting the same 'hanging' problem with Einstein 0.11 as with 0.08. I didn't have the problem with the earlier beta versions 0.02 and 0.05, which let BOINC switch between Einstein and SETI seamlessly. As it takes so long for my Mac to run Einstein anyway, and the hanging means nothing gets processed at all, I'm sorry to say I've suspended Einstein till my current SETI units have finished.
I am not completely surprised by this. As I suggested in my earlier post David Anderson's "fix" to the BOINC API library was a bit of a hack, and in fact apparently has not really fixed the problem. I've talked with him about a better way to fix it; he'll implement that soon and we'll have a revised version available.
The "BOINC API library" Bruce
)
The "BOINC API library" Bruce wrote about is that part of BOINC that gets linked into the App. So you don't need a new BOINC Core Client, you just need to download an install the new App, version 0.11, from the Test App page.
BM
BM
Phil, I think "The BOINC
)
Phil,
I think "The BOINC Monitor app" you were talking about is part of the "BOINC Stat Viewer"? Sorry, I'm not familiar with the various Add-ons and have to admit that I have no idea what exactly this "Checking" status means. Can anyone else help out?
BM
BM
Hm. Did you check the md5 sum
)
Hm. Did you check the md5 sum of the package you downloaded? To me this "Checking" seems like the usual checking of the signature of the App. But as anonymous Apps doesn't have a signature, well, I don't really know what it's doing there.
You should be able to find and start the Activity Monitor (in /Applications/Utilities). Select the process you're interested in, click "inspect", then "sample". It should give you a "call stack" and a clue of what it's doing.
BM
BM
Yep. This is the freeze we
)
Yep. This is the freeze we expected with the 0.08 App, actually in __vfprintf().
You can do the following:
- Stop the BOINC client.
- Open the einstein project folder (where you put the files from the test package in)
- Delete the einstein_0.08_powerpc-apple-darwin App.
- Make a copy of the einstein_0.11_powerpc-apple-darwin App and name it einstein_0.08_powerpc-apple-darwin
- Start the client again.
He will actually use the 0.11 App (though running as 0.08) to finish the result.
BM
BM
It seems the fix from David
)
It seems the fix from David Anderson was good enough for single-CPU machines, but I still get bug reports from dual ones. We're working on this, there will probably be another beta test version put up next week.
BM
BM
RE: I have a single
)
I am not completely surprised by this. As I suggested in my earlier post David Anderson's "fix" to the BOINC API library was a bit of a hack, and in fact apparently has not really fixed the problem. I've talked with him about a better way to fix it; he'll implement that soon and we'll have a revised version available.
Bruce
old obsolete posts go here BM
)
old obsolete posts go here
BM
BM