Thanks Richard. File is no longer in transfer tab :) How ever in my message log I'm getting
SETI@home[error] State file error: missing application file AP6_win_x86_SSE2_OpenCL_NV_r1316 Have I missed something or is this line ok?

Provided you have corrected every reference to that file, and the text string (every occurrence) in app_info matches the true file name, you should be good to go. You might get that error line once at startup, as BOINC cleans itself up after the previous mistake.

The fact that you told Claggy you're 'still' seeing the error message suggests that one or more typos still exists in the app_info file.

Not so much an error as a "behavioural" comment.
While running a "mixed load" (1MB, 1AP) on my GPU the time to go, and progress appear to increment smoothly, however when the GPU is running 2AP the time to go and progress increment in a strange manner - time_to_go slowly increases for a few minute, then suddenly takes a dive, at the same time progress is frozen, suddenly taking a leap up, the two being synchronised and very confusing....
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

... time_to_go slowly increases for a few minute, then suddenly takes a dive, at the same time progress is frozen, suddenly taking a leap up, the two being synchronised and very confusing....

Not confusing but logical and normal.

AP on GPU update the 'Progress' once per a few minutes (maybe to not slow the processing), everytime about +0.9 % is added to 'Progress'
While the 'Progress' do not move BOINC 'thinks' the app is stuck so "time_to_go slowly increases for a few minute"
Then at once a 'huge' +0.9 % is added to 'Progress' and "time_to_go suddenly takes a dive"

Do I replace the existing AP details with the details for the CUDA AP or add them as additional settings? I added the NVidia samples provided by others here to my app_info file and the event log doesn't report any errors but new AP WU's are still being crunched by CPU so I'm guessing I should have replaced the existing AP CPU settings instead.

Do I replace the existing AP details with the details for the CUDA AP or add them as additional settings? I added the NVidia samples provided by others here to my app_info file and the event log doesn't report any errors but new AP WU's are still being crunched by CPU so I'm guessing I should have replaced the existing AP CPU settings instead.

Nope. Unless you want to stop crunching them on CPU.
The WUs that you already had that were assigned to the CPU will be crunched on CPU. If your GPU version of the app is ok in the ap_info, eventually, you will get new WUs that will be assigned to the GPU, but only when BOINC thinks that needs work for the GPU (and only if there are available AP WUs, obviously).

If you delete the CPU version the already assigned WUs will be deleted from your host... (And it seems that for some reason they might not be resent to the GPU. I did it on one of my hosts hoping to re-get them assigned on the GPU but instead they were all cancelled and marked as "out of time").

It's also possible that there is something wrong in the ap_info, not serious enough to throw an error, if you want to be sure, post here the ap_info section you added so we can see if it's ok.

Don't know why you aborted almost all MB work? (Error=768)
This isn't helpfull in getting new work, wheter it maybe MB and/or AstroPulse.
You can try to leave out MB work in your account preferences, always better
then aborting them!

Third option in preferences:

Run only the selected applications SETI@home Enhanced
Astropulse v505 Y/N
SETI@home v7 Y/N
AstroPulse v6 Y/N
If no work for selected applications is available, accept work from other applications? Y/N

Do I replace the existing AP details with the details for the CUDA AP or add them as additional settings? I added the NVidia samples provided by others here to my app_info file and the event log doesn't report any errors but new AP WU's are still being crunched by CPU so I'm guessing I should have replaced the existing AP CPU settings instead.

Nope. Unless you want to stop crunching them on CPU.
The WUs that you already had that were assigned to the CPU will be crunched on CPU. If your GPU version of the app is ok in the ap_info, eventually, you will get new WUs that will be assigned to the GPU, but only when BOINC thinks that needs work for the GPU (and only if there are available AP WUs, obviously).

If you delete the CPU version the already assigned WUs will be deleted from your host... (And it seems that for some reason they might not be resent to the GPU. I did it on one of my hosts hoping to re-get them assigned on the GPU but instead they were all cancelled and marked as "out of time").

It's also possible that there is something wrong in the ap_info, not serious enough to throw an error, if you want to be sure, post here the ap_info section you added so we can see if it's ok.

Thanks Horacio, I woke up this morning and had 4 CUDA AP's downloaded so I was just being impatient it seems.

I think the reason why you aren't able to process any AP work on your GPU is because you have the AP NV app section in 3 times try deleting the section in your app info i put in Red

It doesn't matter, the app_versions sections are different, one having the windows_intelx86 platform and the other the windows_x86_64 platform,
But he should modify the cmd line parameters so they are the same.

What i find strange is why is he running a x40 Cuda4 app? surely he should have upgraded to x41g when it became available.

I've noticed that some WUs are getting low credits, is there a problem somewhere? It's not happening only with the latest app, it also happened with previous versions, not sure when I first noticed it.