7.0.64 seems to work fine [for me], except for the little esoteric whine items such as setting CPU load to 5% to pause [who does that?] and certain tasks [GPU?] not pausing when that 5% is exceeded. Oddly it's been that one report, i.e. not considered a showstopper.

The one item I thought of particular interest over the of course [here] much discussed app_config.xml was the item that was checked in for the client [but do not know if in this release], is the RPC feedback of OpenCL detection to the project server, so [HCC] GPU work is not send if OpenCL is not up to snuff [Officially min. level 1.1]. For now academic to WCG since by the time 7.0.xx is declared "endorsed" by WCG, HCC is done.

At this time, think the devs are eager to move onto 7.1 pre-alpha and 7.2 alpha development. Should *must have* things appear they can always be ported back. Saw that knreed now is adding code into the git2 WCG release branch directly, meaning a little less dependency on the Berkeley folk. Still hoping for a <in_progress> tag so we can control buffering at science level [of course, never getting more than the quota would allow, and total buffer has been set to, in computing time].

I run the work units on my laptop and just yesterday installed the latest version which in the tray indicates GPU enabled but I am not sure if any work units are there fo computation. My GPU is the Intel HD 4000.

Can anyone shed some light on this?

Thank you

Intel HD 4000 is an On-CPU GPU. No project at WCG is using this hardware, in fact the enabling to include support for OpenCL at Berkeley developers has only just started.

Same here...seamless transition. Cool.