The first invalid result of my machine (The WU was calculated correct! I'm a beta tester and the app is running very well on my system.), because of two wingman with 'SETI@home v7 v7.03 (opencl_ati5_sah)' apps and wrong results. :-(
So this WU is uncrunched and lost?

Is there a problem with v7(opencl)? I am running Cuda42 and if my wingman is also running Cuda then the results are validated. But if my wingman is running opencl then the result is marked as inconclusive and if the 2nd wingman is also running opencl then result becomes invalid but if they are running cuda then the result is valid. Any suggestions?

Richards posts is about Boinc 6 that can't (and for now shouldn't) get ATI OpenCL MB v7 tasks at all. These SDK 2.5 clients runs Boinc 7, and they can get ATI OpenCL MB v7 tasks, but the problem is that they do get these tasks despite not having at least SDK 2.6 drivers.This is a test of the Emergency Moron System. Had there been a real moron in the room, there would've been a small mushroom cloud in the place where the idiot had been standing.

Does this mean that apart from the waste of computer time, a lot of good results are being discarded as invalid whilst others that should be discarded are being marked as valid and therefore included in the database

All my inconclusives are paired with hosts using the AMD-APP-SDK-v2.5... and they all ended in -9 overflow (except one with no data in the stderr)...
It seems something that needs to be addressed ASAP...

Does this mean that apart from the waste of computer time, a lot of good results are being discarded as invalid whilst others that should be discarded are being marked as valid and therefore included in the database

At the moment, that seems to be what happens yes. I do hope, for the sake of scientific accuracy, that those SDK 2.5 hosts are stopped ASAP from getting any new ATI MB v7 tasks.This is a test of the Emergency Moron System. Had there been a real moron in the room, there would've been a small mushroom cloud in the place where the idiot had been standing.

Richards posts is about Boinc 6 that can't (and for now shouldn't) get ATI OpenCL MB v7 tasks at all. These SDK 2.5 clients runs Boinc 7, and they can get ATI OpenCL MB v7 tasks, but the problem is that they do get these tasks despite not having at least SDK 2.6 drivers.

AFAIK this typo in plan class eradicated already. So look for new work assigment to those hosts. They should not get new MB v7 tasks...SETI apps news
We're not gonna fight them. We're gonna transcend them.

So far my Windows 680 host and Linux 7970 host have successfully completed the new version 7 tasks. The 680 host picked up the CUDA 5 application. I just built an app_info.xml file for my Linux host so that I can run both setiathome_7.04_x86_64-pc-linux-gnu__opencl_ati5_linux and ap_6.07r1844_sse2_clATI_linux64. GPU load is in the range of 91-93% on both cards.

i dont know what is wrong but i have the new version 7 and now 118 errors in download from the 3021448212 1256148716 5879391 30 May 2013, 9:22:09 UTC 30 May 2013, 10:42:06 UTC Error while downloading 0.00 0.00 --- SETI@home v7 v7.03 (opencl_ati5_sah)
hmmm need to sort this out lucky im still crunching the old system

i dont know what is wrong but i have the new version 7 and now 118 errors in download from the 3021448212 1256148716 5879391 30 May 2013, 9:22:09 UTC 30 May 2013, 10:42:06 UTC Error while downloading 0.00 0.00 --- SETI@home v7 v7.03 (opencl_ati5_sah)
hmmm need to sort this out lucky im still crunching the old system

This is a news thread......
If you would like help with your difficulty, please post your question in the Number Crunching thread.
Lots of folks there working on various questions with the v7 rollout.