OK, that took some digging through several layers of BOINC code.

Your startup messages should be telling you that you have an app_version which uses coprocs that are missing.
Did you change cards or drivers?

Since you are on anon and a ATI GPU is detected (only one mind you!) the client asks for work for the card. when the tasks arrives the client tries to find the right app_version for it. that app_version however uses a coproc BOINC couln't find in the first place. The task gets aborted with 'err missig coproc' and the server gets told on the next contact.

This effectively ensures you do not get new tasks you won't be able to crunch. This is different from the situation when you have tasks on board but lose the GPU - then those tasks will wait for the GPU to become available again.

Now you need to find out why BOINC doesn't see the card(s) properly or thinks they are not suitable for crunching (e.g. OpenCL stuff missing).

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Please check your startup messages for

a) what GPU are detected with what features (post the relevant lines)

b) lines that start 'app version refers to missing GPU type ... ' -please post the rest of those lines and how many of them there are

We will also need the contents of your app_info.xml and sched_reply_setiathome.berkeley.edu.xml files.
On second thought, scratch the last one, unless you can catch the reply directly after you received an AP task and before the 5 min later when it gets reported as dead again. the latter reply will only hold the ack for the report and not the details of the task that won't run [to compare against app_info].

Are you sure you have the right driver and installed the right app for the card you are trying to crunch on?

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

have Lunatics installed for use on 3450 & 3650 cards...4 Brook+ calculations...but got some errors:
http://setiathome.berkeley.edu/results.php?userid=9989358&offset=0&show_names=0&state=6&appid=

all ERRORs are: 201 (0xc9) EXIT_MISSING_COPROC
:/

Above link will only work for you when logged in. Please use links with this form when posting :
http://setiathome.berkeley.edu/result.php?resultid=4444476507

Check the first few lines (20-30 after restart of BOINC) of your event log if your GPUs have been detected correct. The error you found points to a problem with BOINC not recognizing the GPUs.

both GPUs were detected correct! even though my computer r @ home right now...will post u d results! ;)

errors:
http://setiathome.berkeley.edu/result.php?resultid=4444579790
http://setiathome.berkeley.edu/result.php?resultid=4444476507
http://setiathome.berkeley.edu/result.php?resultid=4444476532
http://setiathome.berkeley.edu/result.php?resultid=4440182981
http://setiathome.berkeley.edu/result.php?resultid=4437764137
http://setiathome.berkeley.edu/result.php?resultid=4437649661
those r only 6/13

No traces of app's own part of STDERR. Seems like they were aborted before app got them for processing.

Exactly. There are many curious things about this report, which we've been discussing offline.

BOINC should detect the GPU at startup, and from that point onwards, either the GPU is present, or it's absent - continually.

This host appears to have a GPU detected by BOINC - otherwise it wouldn't request work for "AstroPulse v7 Anonymous platform (ATI GPU)". Yet, all the tasks are failed immediately - error report five minutes later, whatever time of day they were assigned - with 'EXIT_MISSING_COPROC'. We've checked the code, and that is the expected response if a newly assigned task is received but references a coproc (GPU) that the client doesn't know about. The 'Aborted by user' bit is misleading - it would have been aborted by the BOINC client before the user had a chance to see it.

An added complication is that BOINC v7.2.47 is a special version that was only released in World Community Grid skinning - there's no generic BOINC version available for download. It should be entirely compatible, but it may have some of the early v7.4 code included, out of sequence.

KLiK posted that 'both GPUs were detected', but looking at the host record, only a single GPU has been reported. That's where the startup messages from the Event Log would be useful. I was intending to read the full history of the case before posting, but I got called out, and maintenance is coming up.

And there's the question of the older (Brook-only) GPUs. We didn't distribute those for AP v7 originally, but added them back later. Maybe there's an OpenCL problem lurking there - it would be helpful to see from app_info.xml exactly what app(s) are currently active.

Maybe more later.

My freshly created host experiences many task erros with CUDA/
OpenCL NV apps. But that time app discovers missing GPU before BOINC does.

Not quite sure what going on there and could it be connected with other "missing GPU" errors. Did smth change in latest BOINC builds?

Also, what behavior of BOINC/Windows 7 regarding GPU detection when Windows locked (but user doesn't switched)?

For Windows 2008 Server I know answer - GPU will be available while user locked but not switched out. Never had to check this for Win7 before...

EDIT: at least 2 tasks started, processed and finished completely in Win7 user locked state. So, perhaps Win7 behaves simiularly to Win2008 and issues with card disappearance in something else...

I believe it is more complicated.

There is a GPU, yes - but not for the app_version that's present in app_info.xml.
I'm not quite sure how BOINC can get into such a schizophrenic state :D, but we will need to see both the startup messages and the content of app_info.xml before we can figure out what might be going wrong.

I suspect that app_version is referencing a GPU feature, that his particular GPU (or driver) doesn't have.

I can think up an NV test case but I don't have a suitable test bed.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

For all Windows versions Vista and onwards, and BOINC v7 and onwards - i.e. where WDDM driver model is active - there will need to be a user logged in for GPU detection to work. For workstation variants, that's probably why RDP doesn't work - the remote session automatically logs out the foreground console session. That might be different on a server version which allows multiple concurrent logins - I think 2003 did, haven't been an active user of servers later than that.

Apart from that, I don't think servers and desktops should differ. I think they should both keep running (and support repeated GPU detections - client once per session, application once per task) while locked but still logged in.

There were major problems with "Fast User Switching" - it was basically broken throughout the v7.2 version sequence. We blitzed that during the v7.3 alpha sequence, so release v7.4 versions - say May 2014 onwards - have better multi-user support (still not perfect).

My freshly created host experiences many task erros with CUDA/
OpenCL NV apps. But that time app discovers missing GPU before BOINC does.

Err, no boinc looks first, it's the app that then realises it can't quite use that GPU, despite what boinc thinks

this host?

setiathome_CUDA: Found 1 CUDA device(s):
  Device 1: Device Emulation (CPU), 0 MiB, regsPerBlock 8192
     computeCap 9999.9999, multiProcs 16 
setiathome_CUDA: device 1 is emulation device and should not be used, supports 9999.9999
In cudaAcc_initializeDevice(): Boinc passed DevPref 1
setiathome_CUDA: CUDA Device 1 specified, checking...
   Device cannot be used
  Cuda device initialisation retry 4 of 6, waiting 5 secs...

Interesting compute cap ...
you appear to be ending up on the wrong device.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Ah, the old emulation fallback device. Been a long time since we saw one of those.

The emulation fails at the app's attempt at detection - so we end up with a compute error and "Exit status -226 (0xffffffffffffff1e) ERR_TOO_MANY_EXITS".

That's quite different from the client abort that KLiK is reporting.

YEs, this host. And yes, it's different. And not quite on topic cause it's MB app. Though it has some in common cause GPU missed here too... Why it missed still unknown...

Please check your startup messages for

a) what GPU are detected with what features (post the relevant lines)

b) lines that start 'app version refers to missing GPU type ... ' -please post the rest of those lines and how many of them there are

We will also need the contents of your app_info.xml and sched_reply_setiathome.berkeley.edu.xml files.
On second thought, scratch the last one, unless you can catch the reply directly after you received an AP task and before the 5 min later when it gets reported as dead again. the latter reply will only hold the ack for the report and not the details of the task that won't run [to compare against app_info].

Are you sure you have the right driver and installed the right app for the card you are trying to crunch on?

after maintenance of d site was over here is a post... ;)

from a client which uses ATi HD3650:

03-Oct-2015 17:00:29 [---] Starting BOINC client version 7.2.47 for windows_x86_64
03-Oct-2015 17:00:29 [---] log flags: file_xfer, sched_ops, task
03-Oct-2015 17:00:29 [---] Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
03-Oct-2015 17:00:29 [---] Data directory: C:\ProgramData\BOINC
03-Oct-2015 17:00:29 [---] Running under account Luka Marinovic
03-Oct-2015 17:00:29 [---] CAL: ATI GPU 0: ATI Radeon HD 2600/3650 (RV630/RV635) (CAL version 1.4.1734, 512MB, 480MB available, 348 GFLOPS peak)
03-Oct-2015 17:00:29 [---] OpenCL CPU: Intel(R) Xeon(R) CPU           X3360  @ 2.83GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 2.0 (sse2), device version OpenCL 1.2 AMD-APP (937.2))
03-Oct-2015 17:00:29 [SETI@home] Found app_info.xml; using anonymous platform
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 17:00:29 [---] Host name: DP35DP
03-Oct-2015 17:00:29 [---] Processor: 4 GenuineIntel Intel(R) Xeon(R) CPU           X3360  @ 2.83GHz [Family 6 Model 23 Stepping 7]
03-Oct-2015 17:00:29 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 nx lm vmx smx tm2 pbe
03-Oct-2015 17:00:29 [---] OS: Microsoft Windows 8.1: Professional x64 Edition, (06.03.9600.00)
03-Oct-2015 17:00:29 [---] Memory: 3.93 GB physical, 4.62 GB virtual
03-Oct-2015 17:00:29 [---] Disk: 232.10 GB total, 186.43 GB free
03-Oct-2015 17:00:29 [---] Local time is UTC +2 hours
03-Oct-2015 17:00:29 [World Community Grid] Found app_config.xml
03-Oct-2015 17:00:29 [SETI@home] URL http://setiathome.berkeley.edu/; Computer ID 7785610; resource share 100
03-Oct-2015 17:00:29 [World Community Grid] URL http://www.worldcommunitygrid.org/; Computer ID 3251766; resource share 100
03-Oct-2015 17:00:29 [World Community Grid] General prefs: from World Community Grid (last modified 24-Sep-2015 08:05:05)
03-Oct-2015 17:00:29 [World Community Grid] Host location: none
03-Oct-2015 17:00:29 [World Community Grid] General prefs: using your defaults
03-Oct-2015 17:00:29 [---] Reading preferences override file
03-Oct-2015 17:00:29 [---] Preferences:
03-Oct-2015 17:00:29 [---]    max memory usage when active: 3021.89MB
03-Oct-2015 17:00:29 [---]    max memory usage when idle: 3626.27MB
03-Oct-2015 17:00:29 [---]    max disk usage: 10.00GB
03-Oct-2015 17:00:29 [---]    suspend work if non-BOINC CPU load exceeds 80%
03-Oct-2015 17:00:29 [---]    max download rate: 409600 bytes/sec
03-Oct-2015 17:00:29 [---]    max upload rate: 20480 bytes/sec
03-Oct-2015 17:00:29 [---]    (to change preferences, visit a project web site or select Preferences in the Manager)
03-Oct-2015 17:00:29 [---] Not using a proxy
03-Oct-2015 17:00:39 Initialization completed

& from a client which uses ATi 3450M:

03-Oct-2015 18:43:45 [---] Starting BOINC client version 7.2.47 for windows_x86_64
03-Oct-2015 18:43:45 [---] log flags: file_xfer, sched_ops, task
03-Oct-2015 18:43:45 [---] Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
03-Oct-2015 18:43:45 [---] Data directory: C:\ProgramData\BOINC
03-Oct-2015 18:43:45 [---] Running under account Luka
03-Oct-2015 18:43:45 [---] CAL: ATI GPU 0: ATI Radeon HD 2300/2400/3200/4200 (RV610) (CAL version 1.4.1734, 256MB, 224MB available, 80 GFLOPS peak)
03-Oct-2015 18:43:45 [SETI@home] Found app_info.xml; using anonymous platform
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] App version needs OpenCL but GPU doesn't support it
03-Oct-2015 18:43:45 [---] Host name: dell-s1575
03-Oct-2015 18:43:45 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU     T8100  @ 2.10GHz [Family 6 Model 23 Stepping 6]
03-Oct-2015 18:43:45 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 nx lm vmx tm2 pbe
03-Oct-2015 18:43:45 [---] OS: Microsoft Windows 8.1: Professional x64 Edition, (06.03.9600.00)
03-Oct-2015 18:43:45 [---] Memory: 4.00 GB physical, 4.69 GB virtual
03-Oct-2015 18:43:45 [---] Disk: 232.10 GB total, 164.53 GB free
03-Oct-2015 18:43:45 [---] Local time is UTC +2 hours
03-Oct-2015 18:43:45 [Einstein@Home] URL http://einstein.phys.uwm.edu/; Computer ID 11719695; resource share 25
03-Oct-2015 18:43:45 [Milkyway@Home] URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 618965; resource share 20
03-Oct-2015 18:43:45 [SETI@home] URL http://setiathome.berkeley.edu/; Computer ID 7422247; resource share 100
03-Oct-2015 18:43:45 [SETI@home Beta Test] URL http://setiweb.ssl.berkeley.edu/beta/; Computer ID 73805; resource share 10
03-Oct-2015 18:43:45 [World Community Grid] URL http://www.worldcommunitygrid.org/; Computer ID 3182136; resource share 100
03-Oct-2015 18:43:45 [World Community Grid] General prefs: from World Community Grid (last modified 03-Oct-2015 17:33:39)
03-Oct-2015 18:43:45 [World Community Grid] Host location: none
03-Oct-2015 18:43:45 [World Community Grid] General prefs: using your defaults
03-Oct-2015 18:43:45 [---] Reading preferences override file
03-Oct-2015 18:43:45 [---] Preferences:
03-Oct-2015 18:43:45 [---]    max memory usage when active: 3070.47MB
03-Oct-2015 18:43:45 [---]    max memory usage when idle: 3684.57MB
03-Oct-2015 18:43:45 [---]    max disk usage: 10.00GB
03-Oct-2015 18:43:45 [---]    suspend work if non-BOINC CPU load exceeds 80%
03-Oct-2015 18:43:45 [---]    max download rate: 409600 bytes/sec
03-Oct-2015 18:43:45 [---]    max upload rate: 20480 bytes/sec
03-Oct-2015 18:43:45 [---]    (to change preferences, visit a project web site or select Preferences in the Manager)
03-Oct-2015 18:43:45 [---] Not using a proxy
03-Oct-2015 18:43:47 Initialization completed

both have Lunatics 0.43b installed with only BROOK+...with app_info.xml from 3650:

<app_info> 
    <app>
        <name>astropulse_v7</name>
    </app>
    <file_info>
        <name>AP7_win_x86_SSE_Brook_r2904.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>brook.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>brook_cal.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>709</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>ati_opencl_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>709</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
         <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
         <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>ati_opencl_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
</app_info> 

& from 3450M:

<app_info> 
    <app>
        <name>astropulse_v7</name>
    </app>
    <file_info>
        <name>AP7_win_x86_SSE_Brook_r2904.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>brook.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>brook_cal.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>709</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>ati_opencl_100</plan_class>
	<platform>windows_intelx86</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>709</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
         <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>opencl_ati_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
         <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v7</app_name>
        <version_num>704</version_num>
        <avg_ncpus>0.8</avg_ncpus>
        <max_ncpus>0.8</max_ncpus>
        <plan_class>ati_opencl_100</plan_class>
	<platform>windows_x86_64</platform>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP7_win_x86_SSE_Brook_r2904.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>brook.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>brook_cal.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
    </app_version>
</app_info> 

---

non-profit org. Play4Life in Zagreb, Croatia, EU

In testing there was no OpenCL plan class in use, but set up as CPU app, see for example :

AstroPulse v7
Anonyme Plattform (CPU)

Test : delete plan classes from app_info.xml

current : <plan_class>opencl_ati_100</plan_class>
after change : <plan_class></plan_class>

---

_\|/_
U r s

If that doesn't work, second test:

Simplify app_info.xml by cutting down to a single

<app_version>
...
</app_version>

block - that'll make it less confusing.

In that single <app_version> section, make up a plan_class like

<plan_class>ati_999</plan_class>

- with reference to ati, but no mention of opencl.

In testing there was no OpenCL plan class in use, but set up as CPU app, see for example :

AstroPulse v7
Anonyme Plattform (CPU)

Test : delete plan classes from app_info.xml

current : <plan_class>opencl_ati_100</plan_class>
after change : <plan_class></plan_class>

deleted...waiting 4 another WUs now! ;)

---

non-profit org. Play4Life in Zagreb, Croatia, EU

guys, now I have this problem:

10/17/2015 9:54:51 AM | SETI@home | update requested by user
10/17/2015 9:54:54 AM | SETI@home | Sending scheduler request: Requested by user.
10/17/2015 9:54:54 AM | SETI@home | Requesting new tasks for ATI
10/17/2015 9:54:56 AM | SETI@home | Scheduler request completed: got 0 new tasks
10/17/2015 9:54:56 AM | SETI@home | No tasks sent
10/17/2015 9:54:56 AM | SETI@home | No tasks are available for SETI@home v7
10/17/2015 9:54:56 AM | SETI@home | No tasks are available for AstroPulse v7
10/17/2015 9:54:56 AM | SETI@home | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v7.

preferences are set to accept seti@home & astropulse...for CPU & all GPUs...
what is the problem?

---

non-profit org. Play4Life in Zagreb, Croatia, EU

guys, now I have this problem:

10/17/2015 9:54:51 AM | SETI@home | update requested by user
10/17/2015 9:54:54 AM | SETI@home | Sending scheduler request: Requested by user.
10/17/2015 9:54:54 AM | SETI@home | Requesting new tasks for ATI
10/17/2015 9:54:56 AM | SETI@home | Scheduler request completed: got 0 new tasks
10/17/2015 9:54:56 AM | SETI@home | No tasks sent
10/17/2015 9:54:56 AM | SETI@home | No tasks are available for SETI@home v7
10/17/2015 9:54:56 AM | SETI@home | No tasks are available for AstroPulse v7
10/17/2015 9:54:56 AM | SETI@home | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v7.

preferences are set to accept seti@home & astropulse...for CPU & all GPUs...
what is the problem?

I assume you're still running the same app_info.xml file you posted? The server is right: you only chose the Brook app in the installer, so you can only attempt AP tasks on ATI. Preferences are irrelevant, if you don't install the app.

03-Oct-2015 17:00:29 [---] CAL: ATI GPU 0: ATI Radeon HD 2600/3650 (RV630/RV635) (CAL version 1.4.1734, 512MB, 480MB available, 348 GFLOPS peak)
03-Oct-2015 17:00:29 [---] OS: Microsoft Windows 8.1: Professional x64 Edition, (06.03.9600.00)

Unless things have changed, I believe you're going to eventually discover the above pair will Not work with the Brook App. Back in my testing I found the Brook App requires a Pre-Catalyst 12.2 driver. The older drivers actually worked better. Since you can't use that old of a driver in 8.1, it will never work. I placed my 3650 and 4670 in XP with Cat 12.1 and it worked, it would Not work in Win 8/8.1 with the legacy driver. In fact, before they pulled the Brook App from main, Every machine trying it with the Legacy driver would Fail...Lots of Errors on Main.

I believe if you ever do get it to work in an older system you will find it would be faster just to run the task with the CPU. It will be faster than using the old GPU and CPU combined...it's that way with the older GPUs and newer CPUs. It might be beneficial IF you had an old machine with a Slow CPU, otherwise it would be faster to just use the CPU.
Your mileage May vary...but I doubt it.

I will run out of APs for my CPU tomorrow if Aps aren't split soon.

---

03-Oct-2015 17:00:29 [---] CAL: ATI GPU 0: ATI Radeon HD 2600/3650 (RV630/RV635) (CAL version 1.4.1734, 512MB, 480MB available, 348 GFLOPS peak)
03-Oct-2015 17:00:29 [---] OS: Microsoft Windows 8.1: Professional x64 Edition, (06.03.9600.00)

Unless things have changed, I believe you're going to eventually discover the above pair will Not work with the Brook App. Back in my testing I found the Brook App requires a Pre-Catalyst 12.2 driver. The older drivers actually worked better. Since you can't use that old of a driver in 8.1, it will never work. I placed my 3650 and 4670 in XP with Cat 12.1 and it worked, it would Not work in Win 8/8.1 with the legacy driver. In fact, before they pulled the Brook App from main, Every machine trying it with the Legacy driver would Fail...Lots of Errors on Main.

I believe if you ever do get it to work in an older system you will find it would be faster just to run the task with the CPU. It will be faster than using the old GPU and CPU combined...it's that way with the older GPUs and newer CPUs. It might be beneficial IF you had an old machine with a Slow CPU, otherwise it would be faster to just use the CPU.
Your mileage May vary...but I doubt it.

Back on Beta test this combination of OS/driver worked successful :

Coprozessor	AMD ATI Radeon HD 2600/3650 (RV630/RV635) (512MB) driver: 1.4.1720
OS	Microsoft Windows 7
Professional x64 Edition, Service Pack 1, (06.01.7601.00)

That is Catalyst 12.4, the last version that supports legacy ATI HD4000 Series GPUs and newer GPUs in the same driver. It is available for Win 7 and 8(, probably also works in 8.1).

---

_\|/_
U r s