Well, I've run quite a few 604s using the stock SETI app astropulse_6.04_windows_intelx86__opencl_ati_100.exe with the command line -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp. Everyone of them has passed. I did have to change part of the entry to keep it from idling one of the CPU cores doing optimized 603 work. When it began a 604, a CPU core went idle. It was due to this setting;
<avg_ncpus>1.0</avg_ncpus>
<max_ncpus>1.0</max_ncpus>
I changed it to this;
<avg_ncpus>0.06</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
The core came back, but then it began downloading AP 601s again. I found you had to have the 604 CPU value higher than the 601 CPU value or BOINC would use the app with the higher CPU value. Shouldn't the app astropulse_6.04_windows_intelx86__opencl_ati_100.exe be able to run 601 tasks as well as 604s? I never could get the app AP6_win_x86_SSE2_OpenCL_ATI_r555.exe to run at more than 50-60% GPU load. Even with it running at only 40-50% GPU load, I never got the error I was getting with the Stock SETI 604 app. From my understanding, AP6_win_x86_SSE2_OpenCL_ATI_r555.exe is just an older version of astropulse_6.04_windows_intelx86__opencl_ati_100.exe. So, you would think astropulse_6.04_windows_intelx86__opencl_ati_100.exe would run AP 601s. Or, maybe I'm thinking wrong...

You can see the results here http://setiathome.berkeley.edu/results.php?hostid=6797524&offset=0&show_names=0&state=0&appid=12 The tasks run with astropulse_6.04_windows_intelx86__opencl_ati_100.exe are the ones with times around 2500, the ones using AP6_win_x86_SSE2_OpenCL_ATI_r555.exe have times around 3500. The advantage of running 601s is they appear to be more available than 604s, so, when the 604 drought hits you can run 601s with your ATI.

Well, I've run quite a few 604s using the stock SETI app astropulse_6.04_windows_intelx86__opencl_ati_100.exe with the command line -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp. Everyone of them has passed. I did have to change part of the entry to keep it from idling one of the CPU cores doing optimized 603 work. When it began a 604, a CPU core went idle. It was due to this setting;
<avg_ncpus>1.0</avg_ncpus>
<max_ncpus>1.0</max_ncpus>
I changed it to this;
<avg_ncpus>0.06</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
The core came back, but then it began downloading AP 601s again. I found you had to have the 604 CPU value higher than the 601 CPU value or BOINC would use the app with the higher CPU value. Shouldn't the app astropulse_6.04_windows_intelx86__opencl_ati_100.exe be able to run 601 tasks as well as 604s? I never could get the app AP6_win_x86_SSE2_OpenCL_ATI_r555.exe to run at more than 50-60% GPU load. Even with it running at only 40-50% GPU load, I never got the error I was getting with the Stock SETI 604 app. From my understanding, AP6_win_x86_SSE2_OpenCL_ATI_r555.exe is just an older version of astropulse_6.04_windows_intelx86__opencl_ati_100.exe. So, you would think astropulse_6.04_windows_intelx86__opencl_ati_100.exe would run AP 601s. Or, maybe I'm thinking wrong...

You can see the results here http://setiathome.berkeley.edu/results.php?hostid=6797524&offset=0&show_names=0&state=0&appid=12 The tasks run with astropulse_6.04_windows_intelx86__opencl_ati_100.exe are the ones with times around 2500, the ones using AP6_win_x86_SSE2_OpenCL_ATI_r555.exe have times around 3500. The advantage of running 601s is they appear to be more available than 604s, so, when the 604 drought hits you can run 601s with your ATI.

I had the <avg_ncpus>1.0</avg_ncpus> and <max_ncpus>1.0</max_ncpus> set like that because of the ATI Low GPU usage Bug, freeing at least one core cures this, the Nvidia app with recent drivers is similar, needing a core free for full performance,

There is no such thing as 601 or 604 Wu's, they are all Astropulse_v6 Wu's, they just get sent to different app versions, be it Stock CPU 6.01, 6.02 or 6.03, or ATI 6.04 or Nvidia 6.04,
or sent to whatever app_version value in your app_info, you should really make both app_versions entries the same (except for 604 for one, and 601 for the other) so they both use the lastest app,
changing the <avg_ncpus>1.0</avg_ncpus> and <max_ncpus>1.0</max_ncpus> entries just make Boinc prefere one app_version over the other,

Claggy

Well, I've run quite a few 604s using the stock SETI app astropulse_6.04_windows_intelx86__opencl_ati_100.exe with the command line -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp. Everyone of them has passed. I did have to change part of the entry to keep it from idling one of the CPU cores doing optimized 603 work. When it began a 604, a CPU core went idle. It was due to this setting;
<avg_ncpus>1.0</avg_ncpus>
<max_ncpus>1.0</max_ncpus>
I changed it to this;
<avg_ncpus>0.06</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
The core came back, but then it began downloading AP 601s again. I found you had to have the 604 CPU value higher than the 601 CPU value or BOINC would use the app with the higher CPU value. Shouldn't the app astropulse_6.04_windows_intelx86__opencl_ati_100.exe be able to run 601 tasks as well as 604s? I never could get the app AP6_win_x86_SSE2_OpenCL_ATI_r555.exe to run at more than 50-60% GPU load. Even with it running at only 40-50% GPU load, I never got the error I was getting with the Stock SETI 604 app. From my understanding, AP6_win_x86_SSE2_OpenCL_ATI_r555.exe is just an older version of astropulse_6.04_windows_intelx86__opencl_ati_100.exe. So, you would think astropulse_6.04_windows_intelx86__opencl_ati_100.exe would run AP 601s. Or, maybe I'm thinking wrong...

You can see the results here http://setiathome.berkeley.edu/results.php?hostid=6797524&offset=0&show_names=0&state=0&appid=12 The tasks run with astropulse_6.04_windows_intelx86__opencl_ati_100.exe are the ones with times around 2500, the ones using AP6_win_x86_SSE2_OpenCL_ATI_r555.exe have times around 3500. The advantage of running 601s is they appear to be more available than 604s, so, when the 604 drought hits you can run 601s with your ATI.

I had the <avg_ncpus>1.0</avg_ncpus> and <max_ncpus>1.0</max_ncpus> set like that because of the ATI Low GPU usage Bug, freeing at least one core cures this, the Nvidia app with recent drivers is similar, needing a core free for full performance,

There is no such thing as 601 or 604 Wu's, they are all Astropulse_v6 Wu's, they just get sent to different app versions, be it Stock CPU 6.01, 6.02 or 6.03, or ATI 6.04 or Nvidia 6.04,
or sent to whatever app_version value in your app_info, you should really make both app_versions entries the same (except for 604 for one, and 601 for the other) so they both use the lastest app,
changing the <avg_ncpus>1.0</avg_ncpus> and <max_ncpus>1.0</max_ncpus> entries just make Boinc prefere one app_version over the other,

Claggy

OK, so in theory, when the APs labeled for the 604 app dry up, the APs labeled for app 601 shouldn't be far behind. Is there anyway to set the MB6 ATI app to a lower priority than the AP ATI app? That way when the APs run out ATI can fall back to MB6 tasks. When I first began using the app.info, I was flooded with MB6 tasks and wasn't receiving any AstroPulse tasks. I completely removed the MB6_win_x86_SSE3_OpenCL_ATi_r390.exe entry from app.info and then began receiving AstroPulse tasks. I prefer the AP tasks for the GPUs. I've never received any Nvidia 6.04 tasks for my NV8800GT, would they work?

Is there anyway to set the MB6 ATI app to a lower priority than the AP ATI app? That way when the APs run out ATI can fall back to MB6 tasks. When I first began using the app.info, I was flooded with MB6 tasks and wasn't receiving any AstroPulse tasks.

Set your setiathome preferences like this, and you'll get AP v6 Wu's in preference to MB, and only get MB when there's no AP v6 to send:

Run only the selected applications

SETI@home Enhanced: no
Astropulse v505: no
SETI@home v7: no
AstroPulse v6: yes

If no work for selected applications is available, accept work from other applications? yes

I've never received any Nvidia 6.04 tasks for my NV8800GT, would they work?

Yes, as long as you put the correct info in the app_info, BUT, the pre-fermi GPUs are no where near as good at doing AP as Fermi or ATI GPUs are,
my 9800GTX+ is a lot slower than my HD5770 is at AP, But a lot faster at MB than the HD5770 was,

Claggy