These new versions have support for the Intel AVX 256bit SSE extensions. They generate compatible results, so there's no need to reset the project or abort workunits. Unless you have a sandybridge processor and want to see if AVX works. I have no way to test that code here.

---

x86_64 version coming soon. Let me know if there's any major speed changes with the new apps.

---

Why is setigraphics_6.94_windows_intelx86.exe so big at 53.73Mb? when setigraphics_6.91_windows_intelx86.exe was only 1.01Mb?

Claggy

About new 32bit linux version

Doing some standalone testing some behaviour is not so good. It seems there are no "state.sah"-files created/written and runtime is overly long when compared to v6.93 (runtime ca. 8 minutes). Stopped the test after one hour without finishing.
Edit:
Seems to work normal under BOINC.

---

_\|/_
U r s

About new 32bit linux version

Doing some standalone testing some behaviour is not so good. It seems there are no "state.sah"-files created/written and runtime is overly long when compared to v6.93 (runtime ca. 8 minutes). Stopped the test after one hour without finishing.
Edit:
Seems to work normal under BOINC.

Answering to myself after some wus are done (or should be done) :
No, it is not. Picking up and continueing a wu, that was started by an older version (6.91, 6.92 or 6.93), led to, v6.94 finishes the wu normal while updating the "state.sah" properly.
But, starting a new wu, there is no real progressing. After one hour under boinc there is only 0.018% progress shown in BOINC manager. At that speed a wu at AR=1.24 would take more than 230 days.

---

_\|/_
U r s

Download in by mistake because every time it fails to download:

setigraphics_6.94_windows_intelx86.exe

which more than 53 mo

10/06/2011 20:00:16 | SETI@home Beta Test | [error] Signature verification failed for setigraphics_6.94_windows_intelx86.exe
10/06/2011 20:00:16 | SETI@home Beta Test | [error] Checksum or signature error for setigraphics_6.94_windows_intelx86.exe

---

Although setigraphics_6.94_windows_intelx86.exe took nearly 5 hours of download time on my dial-up connection, the file did pass its signature check. Checking the top computers list shows that some have completed tasks with the Windows 6.94 build, and BOINC won't start those tasks until all required files have been successfully downloaded.

Obviously a 53 MB file won't do for main, with many active hosts there it would really impact the download of work too much. With fewer than 2000 active Windows hosts here, my rough calculations suggest it may be using about 10% of the download bandwidth which is unfortunate but not disastrous.

                                                                    Joe

setigraphics_6.94_windows_intelx86.exe passed it's check here too, i've put it on a USB stick and copied it into my Beta project folder on some of my other hosts, so i don't have to download it again,

Claggy

anyone have the url to download? except this one

http://boinc2.ssl.berkeley.edu/beta/download_fanout/setigraphics_6.94_windows_intelx86.exe

---

x86_64 version coming soon. Let me know if there's any major speed changes with the new apps.

Done a offline benchrun on the 6.94 Windows app over at Lunatics on the shortened v7 test Wu's, there's a nice speedup even on non AVX CPU's,

Claggy

I'm trying to decided whether to deprecate the windows version. The fftw dll didn't get checked into the app_version table, and I don't think I can successfully add it after the fact. If the windows version is working for you, it's probably because you still have the dll in your boinc project direction.

Eventually it will fail for someone.

Regarding file sizes. The windows exes will get stripped and compressed before it's released to the main project. It's also possible that statically linked versions of some dlls are getting linked in rather than the dynamic versions.

---

Eric, thank you for the explanation. Now I know why the 2 WUs I tried on my Sandy Bridge (I7-2820QM) laptop both terminated immediately with an exit code of C0000135.

Since reading your post, I have manually downloaded the libfftw3f-3-1-1a_upx.dll file and modified an app_info.xml file I found in an earlier post (Thank you, Sutaru.) to run the setiathome_6.94_windows_intelx86.exe using Anonymous Platform.

I have seen the first WU finish early due to a -9 result_overflow, but at least WUs are now running. Several more have now finished and are awaiting validation.

If you decide to proceed with the creation of x86_64 versions of the programs kindly send them in my direction.

All 6.94 tasks on my Win7_64 host end in a computation error within seconds.(exit code -1073741515 (0xffffffffc0000135))

---

All 6.94 tasks on my Win7_64 host end in a computation error within seconds.(exit code -1073741515 (0xffffffffc0000135))

You can get 6.94 to work by downloading libfftw3f-3-1-1a_upx.dll and dropping the file in your Beta project folder,

Claggy

That didn't solve the issue. This is from the message tab:

11-6-2011 15:14:57	SETI@home Beta Test	Starting 07mr11ah.3292.12746.206158430212.14.123_2
11-6-2011 15:14:57	SETI@home Beta Test	Starting task 07mr11ah.3292.12746.206158430212.14.123_2 using setiathome_v7 version 694
11-6-2011 15:14:58	SETI@home Beta Test	Computation for task 07mr11ah.3292.12746.206158430212.14.123_2 finished
11-6-2011 15:14:58	SETI@home Beta Test	Output file 07mr11ah.3292.12746.206158430212.14.123_2_0 for task 07mr11ah.3292.12746.206158430212.14.123_2 absent

These are the messages with the <task_debug> flag active:

11-6-2011 15:45:46	SETI@home Beta Test	Starting task 07mr11ah.3292.12746.206158430212.14.201_2 using setiathome_v7 version 694
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] Process for 07mr11ah.3292.12746.206158430212.14.201_2 exited
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] task_state=EXITED for 07mr11ah.3292.12746.206158430212.14.201_2 from handle_exited_app
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] result state=COMPUTE_ERROR for 07mr11ah.3292.12746.206158430212.14.201_2 from CS::report_result_error
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] Process for 07mr11ah.3292.12746.206158430212.14.201_2 exited
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] exit code -1073741701 (0xc000007b): 
11-6-2011 15:45:48	SETI@home Beta Test	Computation for task 07mr11ah.3292.12746.206158430212.14.201_2 finished
11-6-2011 15:45:48	SETI@home Beta Test	Output file 07mr11ah.3292.12746.206158430212.14.201_2_0 for task 07mr11ah.3292.12746.206158430212.14.201_2 absent
11-6-2011 15:45:48	SETI@home Beta Test	[task_debug] result state=COMPUTE_ERROR for 07mr11ah.3292.12746.206158430212.14.201_2 from CS::app_finished

Any other flags I can set to diagnose this?

Note that the exit code changed to -1073741701 (0xc000007b) after adding the libfftw3f-3-1-1a_upx.dll file.

I'd try redownloading the dll, overwrite the last one, you could also try restarting Boinc and Windows, (0xc000007b) and (0xc0000135) are both initialization problems,
and make sure the dll is in your Beta project directory, that should be on your host C:\ProgramData\BOINC\projects\setiweb.ssl.berkeley.edu_beta\

Boinc debug flags won't help, this is an app problem,

Claggy

I'd try redownloading the dll, overwrite the last one

Thanks Claggy, that worked. The dll I downloaded before was 260 kB, and the new one is 439 kB.

I'd try redownloading the dll, overwrite the last one

Thanks Claggy, that worked. The dll I downloaded before was 260 kB, and the new one is 439 kB.

Brilliant,

Claggy

x86_64 version coming soon. Let me know if there's any major speed changes with the new apps.

Seeing about an 8% improvement over the 6.91 app with the Lunatics shortened test wu's