| Subject: Re: S@h on MacIntel? |
| From: Chris Schram |
| Date: 07/08/2006, 02:19 |
On Wed, 02 Aug 2006 09:44:08 +0200, Lars Bausch wrote:
Chris Schram wrote:
Following up to myself and the group. Changing "NO" to "YES" in the
settings does not seem to have any positive effect. If anyone still
cares about SETI@home crashing in MacIntel Machimes, here are the two
local crash logs I've gotten since yesterday. They are concatenated
together into one file. I may update this file if there is any interest
in troubleshooting this issue.
<http://www.webenet.net/~schram/setiathome_5.13_i686-apple-darwin.crash.log.txt>
It is still the problem with the screensaver. - There was some postings in
the forums with the same probelem. Could you please try to deactivate the
screensaver, and let seti crunch in the background. - It helped for the
users which has posted this problem in the SETI forums.
I've had S@h running in the background 24/7 all along, and only kicking in
the screensaver graphic during periods of (my) inactivity. Per your
suggestion, I temporarily switched to another screensaver, and S@h's
crashes ceased. Thanks.
This leaves me in a bit of a dilemma. I really LOVE (?) watching the
Einstein@home screensaver, and E@h has never crashed on me. I think what
I'm inclined to do at this time is to allow SETI to finish up its pending
work units on the MacIntel machine, and then run Einstein exclusively with
the screensaver activated.
SETI runs fine on my older PowerPC machine, so I'll still be crunching
units over there at a slower rate until such a time as the S@H people
debug their software to run properly on MacIntel.