I have installed the new version of Boinc 4.25 and 4.26. 4.26 is the one that is now installed on my PC. When I try to run the screen saver I get a red box with the message "Boinc Screensaver is loading Please Wait ..." It takes a few seconds this goes away and the all I get is a black screen. No the Black screen option is not selected. The screen saver worked fine in version 4.19. Any suggestions?
--> Sam D
Copyright © 2024 Einstein@Home. All rights reserved.
Screen Saver won't Start
)
I also have the same problem after upgrading to 4.25.
> I have installed the new
)
> I have installed the new version of Boinc 4.25 and 4.26. 4.26 is the one that
> is now installed on my PC. When I try to run the screen saver I get a red box
> with the message "Boinc Screensaver is loading Please Wait ..." It takes a few
> seconds this goes away and the all I get is a black screen. No the Black
> screen option is not selected. The screen saver worked fine in version 4.19.
> Any suggestions?
>
> --> Sam D
>
Im using BOINC 4.25, the
)
Im using BOINC 4.25, the screen saver wont start. I get the message 'BbOINC is currently idle". Help
I installed 4.25 both on my
)
I installed 4.25 both on my home PC and the notebook. The screansaver works fine on the latter but it just doesn't work on my PC (neither the graphics starts if I click on "Show graphics"). I have a Sapphire Radeon 9600 in my PC and Intel 82852/82855 GM/GME in the notebook (centrino technology). My guess is that it matters. What's yours guys?
ATI 9600 Pro 256mb No
)
ATI 9600 Pro 256mb
No Graphics!
*I still know CRAP when I see it.
Same problem, screen saver is
)
Same problem, screen saver is blank! ATI 9600SE 128mb
Does anybody read that? There
)
Does anybody read that? There has been no reply... why? If somebody asked, I have already installed the latest drivers from www.ati.com. Didn't help...
Same problem here...no
)
Same problem here...no graphics window, no screen saver when upgraded to 4.25. Both worked perfectly in 4.19. I miss them!
This is a known problem,
)
This is a known problem, although Rom can't duplicate the problem on his machines, so fixing it might take some time.
The problem is with BOINC, not E@H.
> This is a known problem,
)
> This is a known problem, although Rom can't duplicate the problem on his
> machines, so fixing it might take some time.
>
> The problem is with BOINC, not E@H.
Is there any system information that we can supply that might help isolate the problem? Is it limited to one OS or is it across platforms?