I notice that the current offerings are all win-x86, are there plans for win-64 versions?
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Second big change - there is ap_cmdline.txt file that can be used to add command line parameters to app.
Put params there as you would put them in corresponding tag in app_info.App_info tag supported too so use a way that more convenient to you.

Second big change - there is ap_cmdline.txt file that can be used to add command line parameters to app.
Put params there as you would put them in corresponding tag in app_info.App_info tag supported too so use a way that more convenient to you.

I think I need second 'copy' section with:
<version_num>601</version_num>

P.S.
It will be good to supply APATI.aistub (two of them - for 32 and 64 bit) in the .7z

1) If I remember correct text file processed after command line so params will be overwritten. It's easy to check cause app reports if default param replaced.
2) yes, better to make copy or just create this new section leaving old one untouched.
3) I think aistub will be supplied in next installer release. It's standalone app release.

Regarding what to mention in app_info file: for stock users upgrading to this release it would be better to include libfftw3f-3.dll in app_info.
That's because stock version could mention it already. If you have this file in project dir then you need to mention it to save it from deletion. It's BOINC's paranoid "kill all I know" approach - quite useless cause nothing prevents to accumulate not known to BOINC trash in that folders.

In general, upgrading with big cache of tasks is not recommended cause chances to lost all accumulated work and work in progress quite big (the same "wipe all" approach in action). I would recommend to finish current GPU AP work, set to "no new task", do update then enable work fetch. In this case errors in app_info will cause minimal damage.

Completed my first Task. It ran very fast - was on track for about an hour running with 2 MB 6.10 tasks at the same time, but exited early at the 35 minute mark with "Found 30 single pulses and 30 repeating pulses, exiting." Was only split tonight so it won't validate for a long time. CPU use was high - about 21% with driver 301.42 (I'm not currently reserving a CPU core for the GPU).

There are several warnings in the StdErr you might want to review. One seems to be about the BOINC version I'm using, and I'm not concerned after your earlier comments. The other has to do with inability to open a file:

"INFO: can't open binary kernel file: C:\BoincData/projects/setiathome.berkeley.edu\AstroPulse_Kernels_r1316.cl_GeForceGTX670.bin_V6, continue with recompile..." and another similar message labeled "Warning". Maybe because it's the first time? Or my non=standard data directory location?

Guess my app_info.xml section is okay. Anyone looking at that earlier in this thread needs to make the fix that Mike pointed out - CUDA needs to be upper case on the Type line.

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

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Yes, cause nothing was done in drivers still. They still use busy-wait loop.

Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now?

It can be called in different ways, but the facts are:
1) there is 2 fundamental ways for CPU to communicate with hardware: to read from port or mapped memory and to process hardware interrupt. First one result in busy wait loop.
2) Earlier drivers work on the same hardware with the same software and low CPU usage method. Current ones use lot of CPU. So, apparently, method for synching was changed.
3) Both methods are possible technically, even with new drivers, CUDA runtime demonstrate this. But NV did not expose ability to switch over driver modes into OpenCL runtime.

"INFO: can't open binary kernel file: C:\BoincData/projects/setiathome.berkeley.edu\AstroPulse_Kernels_r1316.cl_GeForceGTX670.bin_V6, continue with recompile..." and another similar message labeled "Warning". Maybe because it's the first time?

Yes, such output should appear at first running of new versionBut if one sees it always it would mean that kernels binary cache was not saved.
First time app compiles OpenCL kernels from CL file (and oclFFT kernels) into binary representation and saves those binary representations into project directory.
In case of NV those "binary representations" are mostly text one actually - PTX assembly saved so one who interesting can look and see what assembly instructions were generated from original OpenCL code.