The literal translation of the Scottish phrase "Auld Lang Syne" is "old long since". Put into more common speech it's more like "long long ago". Either way, it's fitting that we have work for the New Year under that title with cube 6.07.

I was not able to build a new version of the cube app with the christmas tree, so I simply dug out my backups and recovered the binaries from two years ago. So cube 6.07 is the same binary as cube 6.01 (or 6.02 for Linux). Early indications are that these binaries still work (they are not stale) but may have some problems with the newest release of the BOINC client. Hopefully after we run for a bit a pattern will emerge.

It's not an important test of BOINC, but it may prove interesting nonetheless. Let's hope so.

In any case, best wishes for the new year to all the crew.
____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

They are crunching OK for me (the last version of 6.10 of the CC) but I can't check graphics because any time (still) I try to show graphics, the manager crashes. Same as before.

Someday I might get this box updated to a new version of Fedora (unlikely) or a new distro (probably aptosid I as told you before).
____________
Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System

Yes, Thanks alot for the new work, arrrh...

and a Happy New Year to all crew-members ;-)

greetz from Switzerland
littleBouncer
____________

The tree is nicely rotating on my screen (Win 7 x64), the system already swallowed some 6 cubes today/yesterday.

Interestingly, if no GPU task is running, the cube_graphics_6.07_windows_intelx86.exe process is consuming just some 0-1% of CPU time. But while "SETI@home Beta Test's Enhanced 6.09 (cuda23)" task was active, the graphics process was consuming 30-70% of a core (10-second sampling with Process Explorer), with 0.5-second sampling the CPU usage graph looked nearly like a tooth-saw, the shark-like teeth going from zero to 80% and back... a good example of a conflict of interests (a GPU)? ,-) Maybe something to be tested with subsequent cubes?

After the cube task was finished and reported (the tree remained open and rotating), I've resumed GPU crunching. Some other SETI (not Beta, but the same application name) task continued to run, but the cube graphics process did not consume that much CPU time anymore. Was it a) because its task did not run anymore, or b) the other SETI GPU task was in a different computing phase (although it used just 4% of CPU, not 20% like minutes before) and the contention for GPU was not that bad, or ...??

After the other SETI task finished, again the former SETI Beta task continued, but again no CPU stealing. So let's force start a new cube... Shortly prior to starting it, the old cube graphics already did consume the CPU time again. So maybe indeed the SETI computation phases... And a newly started cube's graphics process is also requiring a lot of CPU - currently two hungry trees spinning on my screen .-)
____________
Peter .-)