...yeah...the WIN41 thing threw me as well...dont know where the he77 that came from.

I typoed. should be 32. ok no need to panic, it's the 6.08 appversion entry, so unless somebody on 64 bit was getting 6.08 stock the entry won't be needed.

You can manually edit the 41 to 32 and we'll get a fixed copy up.

Windows 41?

Edit: Looks as if it'll only affect people who were running Cuda 6.08 with a windows_x86_64 platform tag,

Claggy

Well done Claggy - yes, that's it. Typo in an AIstub. 64-bit installer only, that version number only.

HOLD on 64-bit installs, we'll get that file refreshed and notify y'all when it's ready.

A fresh, fixed copy is now available.

Thank you for spotting the error.

..just a comment...in the next go-around, why not have a user-entry field asking for how many iterations per GPU to run. That way when the app_info file is generated, a user doesnt have to go in and modify it?

Thanks for all you have done so far!

---

..just a comment...in the next go-around, why not have a user-entry field asking for how many iterations per GPU to run. That way when the app_info file is generated, a user doesnt have to go in and modify it?

Thanks for all you have done so far!

That's a good suggestion, but it would be quite clumsy to do using the present installer code - we just copy complete files at the moment, without having any tools to modify their contents as we go along. The current thinking is perhaps to ship a separate tool which could modify not only the <count> number, but also <flops>, and the wider range of command-line settings used for the ATI OpenCL applications: we could then launch that tool at the end of the main installation. But it all depends on having enough volunteer programmers to do that, on top of the optimisation work.

Thanks - keep the ideas coming.

Tests on V7 tasks everytime gave false positive autocorrelation signals on each V7 task tested. On both Cat 11.10 and 11.11.
So I consider these driver badly broken (there is at least one another application for wich invalid computations already reported under these drivers). And recommend to stay away from them if possible. AMD trying to fix, but they do any software improvements VERY slow (and break working things very quickly...).

But looks likeon V6 tasks app give correct results. So, if you absolutely need to install new crappy Catalyst you may be as "after release" tester and check if all v6 processed OK or I was just lucky...

I'm confused over this. V7 tasks vs V6 task?
Is there several types of tasks (WU's)?
Maybe I shouldn't worry cause I haven't got any problem with any of the Cat drivers, but perhaps that might change.

Tests on V7 tasks everytime gave false positive autocorrelation signals on each V7 task tested. On both Cat 11.10 and 11.11.
So I consider these driver badly broken (there is at least one another application for wich invalid computations already reported under these drivers). And recommend to stay away from them if possible. AMD trying to fix, but they do any software improvements VERY slow (and break working things very quickly...).

But looks likeon V6 tasks app give correct results. So, if you absolutely need to install new crappy Catalyst you may be as "after release" tester and check if all v6 processed OK or I was just lucky...

I'm confused over this. V7 tasks vs V6 task?
Is there several types of tasks (WU's)?
Maybe I shouldn't worry cause I haven't got any problem with any of the Cat drivers, but perhaps that might change.

V7 will come but is still in beta phase.

---

With each crime and every kindness we birth our future.

and by beta he means Seti@home beta not on Lunatics.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I ran into a problem when I edited the new app_info.xml to add the portion for the AP for Nvidia Beta. On startup, BOINC reported it could not find the application files for the Beta app:

11/28/2011 3:40:30 PM | SETI@home | File referenced in app_info.xml does not exist: ap_5.06_win_x86_SSE3_OpenCL_NV_r521.exe
11/28/2011 3:40:30 PM | SETI@home | File referenced in app_info.xml does not exist: AstroPulse_Kernels_r521.cl

I suspended the project before I exited BOINC for the install/edit, but still got 5 of these for the tasks on hand:

11/28/2011 3:40:30 PM | SETI@home | [error] No application found for task: windows_intelx86 505 cuda; discarding

Found both missing files in the backup directory and moved them to the SETI Project directory, restarted and it looks okay although I can't tell about the AP/Nvidia app yet. I just got resends for the 5 trashed tasks, so should be okay. Anything else I need to fix? (The .pbd file for the beta app was still present.)

I also reinserted my flops entries - I assume those are still recommended per the v0.37 release notes.

Minor thing - the link on the Lunatics website to the v0.39 readme gets the v0.38 readme. However, the v0.39 readme came with the installation package.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I'm confused over this. V7 tasks vs V6 task?
Is there several types of tasks (WU's)?

To explain in a little more detail.

First, for the time being, forget about Astropulse. Nothing I'm going to write here concerns Astropulse at all.

Neglecting Astropulse, there's currently only one type of task: that's the good old search for ET, using an application called setiathome_enhanced, which is currently at version 6 (and various sub-versions - 6.03 runs on CPUs, 6.08/9/10 runs on GPUs, etc.)

There are long-term plans afoot to increase the sensitivity of the search for ET, by using a new version 7 of the application to search for an extra type of possible signals in the same data.

The new v7 application(s) are currently being written, and those that are ready are being tested at the SETI Beta project.

Lunatics are already working on optimised versions of the new applications. The changes between v6 and v7 aren't all that great, so the Lunatics applications, when they're finished, will be able to work on either type of task. But they have to be tested separately for each type of task.

Gradually, new apps introduced here will be of that dual v6-v7 capable variety. But here, on the Main project, they will operate exclusively in version 6 mode, to suit the tasks being issued by the project.

In due course, the Main project will be upgraded to run the new, more sensitive search. When that happens, there'll be lots of announcements and changes needed. But until then, things carry on as normal.

Hope that helps.

Minor thing - the link on the Lunatics website to the v0.39 readme gets the v0.38 readme. However, the v0.39 readme came with the installation package.

Thanks for the report - depending on who's awake in which time-zone, we'll get that fixed asap - should be within 12 hours from now.

I ran into a problem when I edited the new app_info.xml to add the portion for the AP for Nvidia Beta...

Sorry about that. We overlooked that case in the release notes: again, we'll have another look at it in the morning. Yes, if you're used to using <flops> entries, you can put them back in (from the backup files or fresh from APR) as before.

If you have flops and/or command line in the app_info and if you know how to use 7-zip, then extracting the files needed and edit the app_info seems the easiest.

Okay, things seem to be running right. My thanks to Fred E. for pointing out the problem about the missing files for NVIDIA APs. It will be awhile before I get to the one I have but at least it wasn't discarded. Of course I can't do these things without doing at least one thing wrong. I forgot to change my count to run two MBs at a time before starting up again. Quick easy fix and I am now on my way.

Thanks Lunatics, great job as usual.

---

PROUD MEMBER OF Team Starfire World BOINC

Loading it up on one of my hosts now. Well done guys!!!

---

can I also assume that the Linux apps weren't affected by the "bug" that was found?

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

can I also assume that the Linux apps weren't affected by the "bug" that was found?

Yes, Urs Echternacht verified for me that the bug has not propagated to Linux AKv8 builds.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

The current thinking is perhaps to ship a separate tool which could modify not only the <count> number, but also <flops>, and the wider range of command-line settings used for the ATI OpenCL applications: we could then launch that tool at the end of the main installation. But it all depends on having enough volunteer programmers to do that, on top of the optimisation work.

Thanks - keep the ideas coming.

I could do that.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

The current thinking is perhaps to ship a separate tool which could modify not only the <count> number, but also <flops>, and the wider range of command-line settings used for the ATI OpenCL applications: we could then launch that tool at the end of the main installation. But it all depends on having enough volunteer programmers to do that, on top of the optimisation work.

Thanks - keep the ideas coming.

I could do that.

That's a very welcome offer, Fred. Let's discuss it at Lunatics.

Are the files available without the installer ?

EDIT: Please ignore - I got them out with 7-Zip afterall

T.A.