And that goes as I have said numerous times for all 64-bit versions of the app. 32-bit versions works. How many times do we have to go through this same discussion really?

And do you know that for rabbits (for example) brain reaction "I already saw it" formed after 11th iteration? ;D

Those iGPU hosts - are all dual-GPUs ones or some has only iGPU as videocard?

---

News about SETI opt app releases: https://twitter.com/Raistmer

Those iGPU hosts - are all dual-GPUs ones or some has only iGPU as videocard?

Mine was iGPU only.

Those iGPU hosts - are all dual-GPUs ones or some has only iGPU as videocard?

Mine was iGPU only.

Mine too

One interesting thing about this "no graph in big box" problem can be mentioned:

If I start the graphics when having the monitor on the GTX 980, where it works, and then without closing the graphics window
turn off the monitor (no hotplug changing for me, even if it is said to be OK) and change the monitor to the HD 4600 GPU, then the graphics in the "big box" continues to run.

However, if I close the graphics window (still connected to the HD 4600), and start it up again, the graphics in the "big box" will not start again.

Interesting or not, but that's how it behaves.

I can see something similar with my notebook.
The Nvidia driver lets me select with GPU an app uses. So I added setigraphics_8.07_windows_x86_64.exe


If I leave it default, which uses the iGPU, then I get an empty box.
http://i.imgur.com/6ZiwUCX.png

If I switch it to use the Nvidia GPU then I will get the graphics.
http://i.imgur.com/H98MIgD.png
I do have to close the graphics window and reopen it.

8.08 (alt) released, with the 32-bit setigraphics file.
Works fine on my Intel HD 4600 now.

I'll check in the morning. Bit late here.

Yeah, the graphics works fine, but the graphics "window", does not shut down when the task is done.
Still leaving stderrgfx.txt in the slot directory.

But I guess that issue wasn't meant to be fixed now.

8.08 (alt) released, with the 32-bit setigraphics file.
Works fine on my Intel HD 4600 now.

Works on my Intel HD 530 too :)

Unsurprisingly, it works for me too.

Although the graphics app is 32-bit, I see it's been named x86_64 to match the 64-bit executable it ships with. That might cause confusion if we're still using it when Microsoft finally removes 32-bit support from Windows - and if none of us are around to remember this conversation.

Release it to main. There's nothing more to test here, since the app itself has been thorougly tested here before.
Although, if the app "Windows/x86 running on an AMD x86_64 or Intel EM64T CPU 8.05" is to be kept on main,
the same graphics "hack" (32-bit) is needed on main too, for v8.05.

Edit: And of course, it also needs the same update for the *jpg files as here on Beta.

Any chance to get binary released before project end?

---

News about SETI opt app releases: https://twitter.com/Raistmer

It'll be released tuesday following the outage.

---

It'll be released tuesday following the outage.

Good!!

By then v8.08 (alt) will be the fastest CPU app, easily passing v8.05

Windows/x86 running on an AMD x86_64 or Intel EM64T CPU 8.05 10 Feb 2017, 20:57:18 UTC 226 GigaFLOPS
Windows/x86 running on an AMD x86_64 or Intel EM64T CPU 8.08 (alt) 10 Jul 2017, 19:56:19 UTC 218 GigaFLOPS

I had to leave the lab before the database came back up after the outage. It'll be out first thing in the morning.

---

It will happen when it happens. Not one second earlier.....or later. :-)

It has happened.

---

It has happened.

Yes, thank you Eric. I'm running it now on main.
Since I've already crunched a gazillion of 8.00's, and 8.05's on main, I aborted the 8.05's I had.
I haven't been getting any 8.00's since the last ice age :-)

So beta for Windows x64 CPU app is closed now.

---

News about SETI opt app releases: https://twitter.com/Raistmer

I thought I'd remind people about the problem with the new OSX High Sierra OS and the Mac ATI SoG App 8.20 seen here, https://setiathome.berkeley.edu/forum_thread.php?id=81773. As mentioned back around 31 Jul 2017 via PM the SoG App fails with CL build. The Other Mac ATI App 8.19 doesn't have this problem as can be seen here, https://setiweb.ssl.berkeley.edu/beta/results.php?hostid=82822. The Apps were built last year with the Exact same defines with the exception the 8.20 App used the SoG path. Since the 8.19 version has been in Beta for Almost a year, it would seem a quick solution to the High Sierra problem. I did build a newer version of the non-SoG app a while back and post it here, http://www.arkayn.us/forum/index.php?topic=191.msg4368#msg4368. The r3610 ATI5 App is basically the same as the older 8.19r3552 App with the exception that it uses the newer 3610 version of AKv8.

I would recommend the Mac 8.20 App on main be replaced with the Tested 8.19r3552 version now at Beta, and the 8.20 App be removed from Beta and replaced with the r3610 version from Crunchers Anonymous. The 8.19r3552 & r3610 Apps are compatible with Darwin 11.4.2 and above whereas the current 8.20r3556 requires Darwin 13.0 and above.

I thought I'd remind people about the problem with the new OSX High Sierra OS and the Mac ATI SoG App 8.20 seen here, https://setiathome.berkeley.edu/forum_thread.php?id=81773. As mentioned back around 31 Jul 2017 via PM the SoG App fails with CL build. The Other Mac ATI App 8.19 doesn't have this problem as can be seen here, https://setiweb.ssl.berkeley.edu/beta/results.php?hostid=82822. The Apps were built last year with the Exact same defines with the exception the 8.20 App used the SoG path. Since the 8.19 version has been in Beta for Almost a year, it would seem a quick solution to the High Sierra problem. I did build a newer version of the non-SoG app a while back and post it here, http://www.arkayn.us/forum/index.php?topic=191.msg4368#msg4368. The r3610 ATI5 App is basically the same as the older 8.19r3552 App with the exception that it uses the newer 3610 version of AKv8.

I would recommend the Mac 8.20 App on main be replaced with the Tested 8.19r3552 version now at Beta, and the 8.20 App be removed from Beta and replaced with the r3610 version from Crunchers Anonymous. The 8.19r3552 & r3610 Apps are compatible with Darwin 11.4.2 and above whereas the current 8.20r3556 requires Darwin 13.0 and above.

1) What version number of "High Sierra" ?
EDIT: Looked into Q&A thread I saw 10.13 number. Does it mean it's Darwin 13.0.xx ? Or what?


2)

The 8.19r3552 & r3610 Apps are compatible with Darwin 11.4.2 and above whereas the current 8.20r3556 requires Darwin 13.0 and above.

All 3 are non-SoG ?

3) http://www.arkayn.us/forum/index.php?PHPSESSID=qg2ujvtrk8jp1rte5605lb7fq6&topic=191.msg4368#msg4368
I see only AVX+ here. Does it mean that all Mac CPUs support at least AVX ?

4) What about this app/plan class:
Mac OS X/64-bit Intel 8.10 (opencl_ati_mac) 7 Apr 2016, 1:01:54 UTC 6 GigaFLOPS

5)
On main this app/plan class has biggest impact on ATi GPU on Mac:
Mac OS X/64-bit Intel 8.20 (opencl_ati5_SoG_mac) 28 Dec 2016, 23:34:07 UTC 18,732 GigaFLOPS
As I understand you propose to remove app with highest yield. It seems counterproductive. We should just improve plan class limitations instead to exclude hosts with failures.

---

News about SETI opt app releases: https://twitter.com/Raistmer