@All (having this screensaver/Win10 issue and wanting to investigate)

What happens if you manually start SETI@home screensaver?

- While some SETI@home CPU task is running (you see process in memory with name like setiathome_8.00_windows_intelx86.exe)
Go to SETI@home directory (<BOINC_Data>\projects\setiathome.berkeley.edu\) and start the SETI@home screensaver, name like:
setigraphics_8.00_windows_intelx86.exe

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Double-clicking on the graphics executable results in a black box (the command prompt) opening and closing immediately.

Me Too Same thing; Gess; was fine before the end all 10 developers upgrade. now a mess
A quad4 and a 2 and Err. Oh ya Nvidia 1050tis new drivers and err The 4 wont seem to go.
Its a pain HUH Install Re in and gawd I thought it was over years ago.
But you know what; we will get it working again because we do not quit.
That's what we do. And I was just a dumb plumber-lol ;G

Me to Gess. Did all the NVidia Drivers clean; still sits there not crunching on my box. S saver will pop and go away.
Now my other I did not let it do the new Developers cut ; But its a Intel cpu and the Quad4 is AMD ; HMM.
Well if you figure it please let us know.. Thank you for the input; G

Double-clicking on the graphics executable results in a black box (the command prompt) opening and closing immediately.

It is not really "command prompt" but the window of setigraphics itself.

If you want to play a little more (you can do the same on a "bad" and "good" Windows 10 system to see the difference):

For the next test I used v7 files as I have them, as you guess your filenames will be a little different.
I used Process Explorer to monitor and kill processes.

A)
- Snooze BOINC
- Make an empty directory (e.g. ...\projects\setiathome.berkeley.edu\SetiGraphicsTest\)
- Copy in it setigraphics_7.00_windows_intelx86.exe
- Start it (setigraphics*.exe)

On a "good" system (Windows XP) I see this and it stays open until I close it:



- Close setigraphics*.exe (if needed)
File stderrgfx.txt is created (the last 2 lines appear only after I close the window of setigraphics):

14:27:47 (3412): Can't open init data file - running in standalone mode
14:27:47 (3412): Starting graphics application.
Warning: unable to load JPEG file. File size=0
Failed to load 'user_logo'.
Failed to load 'background'.
14:33:03 (3412): Close event (WM_CLOSE) detected, shutting down.
14:33:03 (3412): Shutting down graphics application.

B)
- Copy 3 additional files:
setiathome_7.00_windows_intelx86.exe
libfftw3f-3-3_upx.dll
work_unit.sah         (this is any WU file ~356 KB renamed to work_unit.sah)

- Start setiathome_*.exe
Wait 1-2 minutes and see how some 4-5 files are created.

- Start setigraphics*.exe



- Close setigraphics*.exe (if needed)
- Kill setiathome_*.exe (by Process Explorer)

- UnSnooze BOINC

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Following those same steps on my Windows 10 Creators Update system still shows the application terminating. I see a file was created named stderrgfx.txt. I'm seeing entries like this:

17:34:17 (16224): Can't open init data file - running in standalone mode
17:34:17 (16224): Starting graphics application.
Warning: unable to load JPEG file. File size=0
Failed to load 'user_logo'.
Failed to load 'background'.
Warning: unable to load JPEG file. File size=0
Failed to load 'user_logo'.
Failed to load 'background'.
shared memory segment missing

YUP!

---

Those who fail to remember the past are DOOMED to repeat it!

Try downloading Slim Drivers. It is a free updater. If you do make sure you set it to back up your previous drivers. Then once I get any and all driver updates I uninstall it, and also go into the registry and remove all traces of the program. I likes to run in the back ground and gets annoying so it goes bye-bye. And no it won't fix the screen saver problem!

---

Those who fail to remember the past are DOOMED to repeat it!

I see a file was created named stderrgfx.txt. I'm seeing entries like this:
...
shared memory segment missing

That is the problem.
Now someone who makes applications and knows enough about programming in Windows have to figure-out why "shared memory segment missing" on Windows 10 Creators Update.
(is this a bug made by Microsoft or is it some new change in Windows, e.g. "for security"?)

("shared memory" is used so the applications' screensaver can get data from the running application)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I think better to re-route this question on BOINC forums where those who developed this particular interface (between science app and graphics app) can see issue.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I wouldn't get my hopes up... I just ran the setigraphics_8.00_windows_intelx86.exe standalone on my Windows 7 and got the exact same outcome from stderrgfx.txt:

23:31:02 (4416): Can't open init data file - running in standalone mode
23:31:02 (4416): Starting graphics application.
Warning: unable to load JPEG file. File size=0
Failed to load 'user_logo'.
Failed to load 'background'.
Warning: unable to load JPEG file. File size=0
Failed to load 'user_logo'.
Failed to load 'background'.
shared memory segment missing

Meaning that the shared memory segment missing message isn't something that prohibits the screen saver from showing the graphics in Windows 10 CU exclusively.

---

Linking here some other threads about the same problem:

"Screen saver not working under Windows 10":
https://setiathome.berkeley.edu/forum_thread.php?id=81343

"Boinc screensaver & Creators Update (Microsoft, Win10)"
http://boinc.berkeley.edu/dev/forum_thread.php?id=11560

on GitHub:
"Windows 10 Creators Update broke BOINC screen saver"
https://github.com/BOINC/boinc/issues/1859

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I think the latest Windows 10 Creators fix KB4020102 resolves this.

Since the Creators upgrade (1703) was installed I was having the same problem as everyone else up until today when I installed this latest fix and now the BOINC screen saver is working again. This fix may have been in the pipeline for a few days but I noticed that it kept failing to install on my system so I did a clean shutdown and reboot which allowed the install to proceed. My apologies for imprecise information but I neglected to write down the fix failure details and error code but it had something to do with some process already in progress, hence my decision to reboot.

With this fix installed, my build level is now 15063.332

---

HPetite

The newest win10 update, 1703.15063.332 appears to have resolved the BOINC/SETI screensaver problem.

The newest releases, one for x86(32bit) and one for x64(64bit) are located at
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4020102
Please insure you choose the correct version for your system.

As per the usual SOP a couple of reboots are required to get all the pieces in place. I would also suggest
that you insure you have the latest video drivers from your respective brand vendors as that seems to
be a common problem cause for other issues.

---

Helping where I can. Hindering everywhere else.

boinc screen saver is now compatible on 2 of my laptops

will update to creators on other machines

---

I can confirm that update package KB4020102, released on May 26 fixes the problem.
It's interesting to note however that this update does NOT show up in Windows Update in Settings; you have to download it manually from the Microsoft Update Catalog.

Just downloaded and installed the update (531 MB for 64-bit) and the screensaver function seems to be restored. Thanks all, thanks to Patrik for the link!

---

Yes. Reinstalling Windows10 update kb4020102 fixed the problem for me!!!!

---

BOINC SCREEN SAVER PEOBLEM

Regarding the newest version of Win 10, release 1703 15063.13 is not engaging the BOIC screensaver.
link at https://www.microsoft.com/en-us/software-download/windows10
On three different PCs, after completing the hour+ long windows 10 update, BOINC does not start.
Can't get it to run even after reinstall of BOINC 7.6.33
Curious if others who have performed the same win upgrade have seen similar problems.

Thursday June 8 2017, 12:57 PM

Hi Amtronic,

I first posted this problem on the same day that up-date was released, and, as of yesterday, there has still been no fix for it.

The BOINC Screen Saver's "noise box," my phrase describing the nicely detailed graphic image that, in a rotating display, along with other pages, is KAPUT. Well, the screen saver DOES work, but the "noise box" requiring the graphics, doesn't work.

I asked about and was told that the BOINC graphics display can only be fixed by M$, i.e., Microsoft themselves, and, in the weeks since that "update" they have NOT fixed it. They MAY not even KNOW about the problem? The person who told me M$ had to FIX it seemed vague and didn't tell me WHO at M$ was going to fix it, and when?

Oh, BTW, I should mention that the BOINC Screen Saver, in its entirety, with the "noise box," still works FINE on my older Win 7 PC. It's just Win 10 that is all screwed up.

If YOU can find out who the "fixee" is, please let me and all in the group KNOW, huh?

In the meantime, I'm running the BOINC saver, sans the "noise box. I created a shortcut to the .exe file for it on my desktop. When I leave my 24/7 Win 10 PC, I manually click on the shortcut to bring up BOINC, and then click it to save the screen to my taskbar when I return to work. It is better than NOTHING, vut I greatly MISS the beautiful "noise box."

Good luck in trying to push along a fix!

Stay here on Earth. It's the only planet with DARK CHOCOLATE !!

---

River Song (aka Linda Latte on planet Earth)
"Happy I-Phone girl on the GO GO GO"

It has been fixed by Microsoft however:

If you read some of the the posts is does say

This update does NOT show up in Windows Update in Settings; you have to download it manually from the Microsoft Update Catalog.

The link is HERE

Make sure to download the correct version.