Feel free to use it. We just need to wait a little be before we can suggest it.
gdf

Also for me 6.5.0 works fine on both CUDA computers (on Grid and SETI)

I think I found two bugs with the 6.5.0, which I installed yesterday.
First:
When I suspend a WU (for gaming e.g.) and later want to continue the WU, it doesn't. The GPU stays idle.
Second:
A manager problem. When I want to exit, a message pops up with the choice to "Stop running applications when exiting".
Doesn't matter if it's checked or not, the apps stay in memory, independent from the preferences settings "Leave app in memory". :-\

The second problem seems to directly affect problem one, because the acemd_655.exe can't be restarted.
I had to abort it per task manager to make the GPU working again on another WU.

---

Member of BOINC@Heidelberg and ATA!

I think I found two bugs with the 6.5.0, which I installed yesterday.
First:
When I suspend a WU (for gaming e.g.) and later want to continue the WU, it doesn't. The GPU stays idle.
Second:
A manager problem. When I want to exit, a message pops up with the choice to "Stop running applications when exiting".
Doesn't matter if it's checked or not, the apps stay in memory, independent from the preferences settings "Leave app in memory". :-\

The second problem seems to directly affect problem one, because the acemd_655.exe can't be restarted.
I had to abort it per task manager to make the GPU working again on another WU.

I understand ur problem, but I have to say, that I haven`t similar situation. I`m using 6.5.0 on 2 different maschines. I can suspend project, e.g. for OC (as you know for OC GPUGrid shouldn`t work, on my maschines if I`ll try to OC without suspending, then OS will crash), and continue after OC without any problems. Pls write more about specification of your maschine (AMD/Intel, OS, driver, graph card, OC?). Without these data it will be difficult to wonder if it`s bug or maybe just small problem with configuration of your maschine (with full respect ofc).

---

Pls write more about specification of your maschine (AMD/Intel, OS, driver, graph card, OC?). Without these data it will be difficult to wonder if it`s bug or maybe just small problem with configuration of your maschine (with full respect ofc).

Sorry, forgot about that because I hadn't much time this morning.
It's an AMD 64 X2 5200 with a 9600GT (factory overclocked) and driver 180.48 on Windows 32-Bit.
So far the newest I think. ;-)
Thus I don't think it's a problem with the config of my system because I never had a suspend problem before, so it's pretty obvious in my eyes that it is the client.

---

Member of BOINC@Heidelberg and ATA!

6.5.0 is finally available for 64bit Linux:
http://boinc.berkeley.edu/dl/boinc_6.5.0_x86_64-pc-linux-gnu.sh

Thus I don't think it's a problem with the config of my system because I never had a suspend problem before, so it's pretty obvious in my eyes that it is the client.

I have the 6.5.0 running on 3 Vista 64, 2 XP 32 and one Linux 64 boxes and have this bug never seen.

---

Well, I should have tested it much longer, before I reported the little problem, but I was in a hurry yesterday morning and thought to let you all know. ;-)

I tried to suspend some WUs this morning again (also SETI Cuda-tasks), and they resumed without problem.
Seems it was only a minor glitch, caused by whatever...
Sorry.

---

Member of BOINC@Heidelberg and ATA!

Can people with 6.5.0 try to reproduce the issue described here? Any comments should go into the other thread.

MrS

---

Scanning for our furry friends since Jan 2002