So will there still be v6.03 and v6.72 WUs? If so I think the merging is a bad idea. Some machines run v6.72 better and some (especially older cards) run v6.03 better. Merging the two types into 1 queue will make us do the babysit and abort shuffle again. Much more work for us, less output for the project.

We will use only one application in two versions, cuda2.2 (for old drivers) and cuda3.0 for new drivers and fermi.

I don't actually know. It is BOINC that select if the driver is CUDA3 compatible.
I guess that it is the one suggested in the cuda development page.
gdf

I think for CUDA 3.0 you need at least driver 197.xx, and that's the point where the reduced available memory starts to kick in.

Driver 190.xx / CUDA 2.2 seems a nice stable combination for older cards, but have you ruled out CUDA 2.3 (or just decided it doesn't offer any improvement over 2.2 for GPUGrid)?

6.03 will disappear as it is old by now. There is no reason why it should work better than 6.72.
We will use only one application in two versions, cuda2.2 (for old drivers) and cuda3.0 for new drivers and fermi.

gdf

Since v6.03 was shut down I've had to move a 9600GSO and a GT 8800 to Collatz, too many errors with the v6.05 WUs. They ran the v6.03 WUs fine. A 3rd GPU, another 9600GSO that ran well with v6.03 can't get work at all now, probably since it has 384MB of ram, also moved to Collatz. That's 3 decent cards moved from GPUGRID due to problems with the transition. Also problems getting work with the faster cards for the last day. No work at all available for any apps for the last few hours. Things aren't looking good :-(

Since v6.03 was shut down I've had to move a 9600GSO and a GT 8800 to Collatz, too many errors with the v6.05 WUs. They ran the v6.03 WUs fine. A 3rd GPU, another 9600GSO that ran well with v6.03 can't get work at all now, probably since it has 384MB of ram, also moved to Collatz. That's 3 decent cards moved from GPUGRID due to problems with the transition. Also problems getting work with the faster cards for the last day. No work at all available for any apps for the last few hours. Things aren't looking good :-(

We will solve this problem in the next release. I'll keep you informed.
gdf

Since v6.03 was shut down I've had to move a 9600GSO and a GT 8800 to Collatz, too many errors with the v6.05 WUs. They ran the v6.03 WUs fine. A 3rd GPU, another 9600GSO that ran well with v6.03 can't get work at all now, probably since it has 384MB of ram, also moved to Collatz. That's 3 decent cards moved from GPUGRID due to problems with the transition. Also problems getting work with the faster cards for the last day. No work at all available for any apps for the last few hours. Things aren't looking good :-(

I'm experiencing something similar when I'm trying to run seti & collatz.
Do you have the same thing as I wrote here ?
http://lunatics.kwsn.net/gpu-testing/ati-sse3-astropulse-app-openclbrook-beta-testing.msg27299.html#msg27299

Link doesn't work:

"An Error Has Occurred! The topic or board you are looking for appears to be either missing or off limits to you."

I'm having a small problem wit rev 420 and collatz.
While collatz 2.09 ati13ati is running, I'm getting [sched_op_debug] ATI GPU work request: 0.00 seconds; 0.00 GPUs
I have to suspend collatz in order to have [sched_op_debug] ATI GPU work request: 8640.00 seconds; 1.00 GPUs
It seems as collatz is bullying ati, despite having 90/10 share for seti/collatz.
Can somebody test this on their rig (.56 x64, SETI rev 420 + Collatz 2.09, only gpu)?
I'm afraid it might be smth with the app_info.

He wrote:

[quote]I'm having a small problem wit rev 420 and collatz.
While collatz 2.09 ati13ati is running, I'm getting [sched_op_debug] ATI GPU work request: 0.00 seconds; 0.00 GPUs
I have to suspend collatz in order to have [sched_op_debug] ATI GPU work request: 8640.00 seconds; 1.00 GPUs
It seems as collatz is bullying ati, despite having 90/10 share for seti/collatz.
Can somebody test this on their rig (.56 x64, SETI rev 420 + Collatz 2.09, only gpu)?
I'm afraid it might be smth with the app_info.

I don't think it is anything to do with the app_info.xml file: sounds more like BOINC long-term debt, aka 'ATI work fetch priority'.

I'm using 6.10.56 x64 but it's not working.
How do I use a VERY SMALL queue size?

Configure Boinc to keep 0.05 days of work units (for example):
Open Boinc in Advanced View,
Advanced,
Preferences,
Network Usage,
Additional work buffer (0.05) days.

I don't think it is anything to do with the app_info.xml file: sounds more like BOINC long-term debt, aka 'ATI work fetch priority'.