I too am having these problems and yes I have a wacom tablet which I use regularly for my school work, however wuiting the drivers is not an option for me as when I am using my computer I usually am also using the tablet. are there any other options to correcting this issue while still being able to use the boinc screensaver?

I have been having this same issue. After reading all the posts I did a force quit to "tabletdriver" and the problems all went away. So for me it was a conflict between the Wacom tablet driver and Boinc.

I tried repeating this test on a DP G5 ...
I used Activity Monintor to force quit TabletDriver.
Then I used hot corners to activiate SETI Screensaver - it launched correctly and continued to work normally ! The sceensaver also actiivated correctly after the automatic delay set in the 'Desktop & Screen Saver' prefernce panel.

Next, I re-launched TabletDriver. The original problem returned.
Using HotCorners, I launched SSS - it displayed the screensaver for a few seconds, then quit inelegantly.

So - the TabletDriver app certainly seems to part of the problem.

---

Well, it isn't required; I have never had a Wacom tablet or any tablet for that matter but I do have "the problem." I'll look to see if there are other non-Apple drivers active.

---

Wierd. I used ActivityMonitor to look for drivers and there it was - TabletDriver. But I don't own any tablet!?

I killed the process and removed the startup item. The screensaver now works.

Take nothing for granted, I guess...

---

If you install this screensaver: AppStartSaver (free) you can set it to launch Boinc manager as a screensaver (and also, to quit Boinc when your computer becomes active again).

I have the Wacom problem too and although this method won't run the colourful Seti screensaver, if you simply want the Boinc application itself to run as a screensaver during idle time, then you might find this useful.

Just thought I'd share the info.

---

Thanks for this info.
You might like to check the early parts of this thread - esp Message 442730 (19 May).

When I started this thread, I didn't have Wacom drivers on my system - or any of my other OSX machines. The problem seems to have started when I upgraded to OSX 10.4.

It's interesting that the Wacom drivers seems to have some bearing on the problem, but I suspect that the effect is indirect. Although there may be a conflict between the SETI screen saver and the Wacom drivers on OS 10.4, it can't be the only cause.

Gary

Like Gary, I have had the screen saver problem but it only started a couple of days into running Seti@home without a hitch. I had my Wacom drivers in place throughout (specifically, for the first few (problem free) days) and now the thing just keeps tripping over as it tries to connect and load the graphics. However, Seti seems to be running okay in the background.

Mac OS X 10.4.9
G5 iMac 2.1 GHz
BOINC 5.8.17
Default browser: FireFox 2.0.0.3.

Doug.

Thanks for this info.
You might like to check the early parts of this thread - esp Message 442730 (19 May).

When I started this thread, I didn't have Wacom drivers on my system - or any of my other OSX machines. The problem seems to have started when I upgraded to OSX 10.4.

It's interesting that the Wacom drivers seems to have some bearing on the problem, but I suspect that the effect is indirect. Although there may be a conflict between the SETI screen saver and the Wacom drivers on OS 10.4, it can't be the only cause.

Gary

Like Gary, I have had the screen saver problem but it only started a couple of days into running Seti@home without a hitch. I had my Wacom drivers in place throughout (specifically, for the first few (problem free) days) and now the thing just keeps tripping over as it tries to connect and load the graphics. However, Seti seems to be running okay in the background.

Mac OS X 10.4.9
G5 iMac 2.1 GHz
BOINC 5.8.17
Default browser: FireFox 2.0.0.3.

Doug.

Still having the same issue... even after downloading the latest version, and even after nearly a year after reporting this. I can quit the tablet driver and it works, but I need the tablet driver. Are they even trying to fix it? Very dissapointing...

---

Right, i've had enough. What sort of intelligent life would want to contact a species that can't make a bloody screensaver work? BOINC is off my mac until the problem is FIXED.

Right, i've had enough. What sort of intelligent life would want to contact a species that can't make a bloody screensaver work? BOINC is off my mac until the problem is FIXED.

Sorry, your tone is absolutly deplaced. Your meassuring a great project at problem on the screensaver ? - Sorry this is a arogant and total intolerant !

BOINC is not a screensaver, it is designed to compute in the background. The screensaver is only a funny addon. There would no scientifical benefit from the screensaver.
Also, SETI has a less resources to less budget and to less manpower to do the work. There are a lot of more important things to do, for example to fix the hardware problems, release the multibeam application and the delevlopment of the new astropulse application.
So please be patient.

---

Hey, everybody, it's fixed! On my machine, at least, it turns out it was the tablet driver, not the SETI@home screensaver. I installed the latest Graphire (ET) tablet driver (dated 4/12/07), and the problem went away. Download the latest tablet driver from Wacom and see if it works for you, too. Start here to find the proper driver for your tablet: http://www.wacom.com/productsupport/select.cfm

Good Luck!

---

Hey, everybody, it's fixed! On my machine, at least, it turns out it was the tablet driver, not the SETI@home screensaver. I installed the latest Graphire (ET) tablet driver (dated 4/12/07), and the problem went away. Download the latest tablet driver from Wacom and see if it works for you, too. Start here to find the proper driver for your tablet: http://www.wacom.com/productsupport/select.cfm

Good Luck!

Yes, the problem seems solved after installing the latest Wacom driver.
Thanx for the tip, Shirreyder.

Next question: How long will we have to wait for the option to turn off the static messages? The advantage of a screensaver gets lost…

---