- lib: Fix a bug where information that was meant for stdout was being written to stderr instead.

- lib: Keep track of the rough estimate of stdout and stderr by incrementing internal variables instead of doing a stat on each log write. stat() on Windows is converted to a FindFirstFile?() call which in turn looks up the file size information in the directory structure file system entry. The directory structure information is only updated periodically. This lead to larger than expected log file for both the manager and core client. This has the added advantage of reducing the overall number of file I/O operations when logging information.

- MGR: Eliminate QuickDraw calls for OS 10.8 compatibility.

- diagnostics lib: Store file sizes as double rather than int

- If we're appending to log files, initialize the size variables to the current size.

I have posted BONC 7.0.29 for the Mac to the Download All page. Version 7.0.29 is for the Macintosh only.

The BOINC Manager and Client are identical to version 7.0.28. The only differences from 7.0.28 are the installer and uninstaller, which have fixes for situations where BOINC is installed for multiple users under OS 10.7.x Lion and the upcoming OS 10.8 Mountain Lion. It fixes the setting of the screensaver for multiple users, and the setting and deleting of Login Items for multiple users. (Login Items are used to automatically launch BOINC Manager when a user logs in to the Mac.)

If you are running 7.0.28 on the Mac, please upgrade to 7.0.29. Except for issues with the installer or uninstaller, tests you have already run on 7.0.28 are applicable to 7.0.29.

Thank you for your support of BOINC.

Cheers,
--Charlie

- MGR: Remove the visuals in the wizard for multi-core and opencl. This area will get a bunch of work in a future commit.

- client: show <vbox_window> option in log, and give warning if include this while in sandbox mode.

- MGR: Wait until there is valid data in the list box before processing the OnProjectSelected() event.

- client: added the definitions for the new Windows 7/2008r2 preSP1 and Windows 8/2012 SKUs based on the winnt.h from the Windows 8 RC SKD (also added as proof). Added the detection for some more Windows SKU

- client: split GPU detection code into separate files

- client: rename coproc_detect.cpp to gpu_detect.cpp

- client: compile fixes

- client: for NVIDIA, make an array of the PCI info for all usable GPUs

- client: it's possible for a host to get app versions for a given app that have different platforms and different version #s. The client was erroneously deleting the one w/ the lower version when it was no longer in use. Fix: in garbage collection, consider one version to supercede another only if they have the same platform

- client: AMD GPU detection addition (from [P3D] Crashtest)

- Mac: Update XCode project with new source files.

- Mac: Fix displayed names of BOINC installer, uninstaller, etc.

- Mac: Code sign the BOINC installer and uninstaller if we have a valid code signing identity. Code signing using a registered Apple Developer ID is necessary for GateKeeper with default settings to allow running downloaded applications under OS 10.8.

Rom has withdrawn 7.0.30 due to a bug with the Nvidia code. There will be a new version out soon.

Strangely, the two machines I'm running v7.0.30 on (one 32-bit, one 64-bit) seem to be running just fine - fetching, crunching, and reporting NVidia tasks as usual.

There was a reported problem for computers attached to the BAM account manager, so avoid this version if you use that. Otherwise, there seems to be no need to uninstall v7.0.30 if you have it running already.

I believe all that was wrong was the end tag. 7.0.31 is out now with the fix for it.

Rom has withdrawn 7.0.30 due to a bug with the Nvidia code. There will be a new version out soon.

Strangely, the two machines I'm running v7.0.30 on (one 32-bit, one 64-bit) seem to be running just fine - fetching, crunching, and reporting NVidia tasks as usual.

There was a reported problem for computers attached to the BAM account manager, so avoid this version if you use that. Otherwise, there seems to be no need to uninstall v7.0.30 if you have it running already.

- When the client makes a scheduler RPC without requesting work, and there's a simple reason (e.g. the project is suspended, no-new-tasks, downloads stalled, etc.) show it in the event log. If the reason is more complex, don't try to explain.

- client: in the job scheduler, there's a check to prevent overcommitting the CPUs if an MT is scheduled. Skip this check for GPU jobs.

- Client (Win): in file_size(), use _stat64() instead of stat(). Otherwise it doesn't work for files >= 2GB

- Client: TIME_STATS::trim_stats_log() wasn't working because it's called in the constructor of TIME_STATS, which is called before we've done a chdir() to the data dir. Note: for this reason, no disk access should be done in constructors of global objects. A quick scan found no instances of this.

- client: remove "device" entry from CUDA_DEVICE_PROP, and change types of mem-size fields from int to double. These fields are size_t in NVIDIA's version of this; however, cuDeviceGetAttribute() returns them as int, so I don't see where this makes any difference.

- client: fix bug in handling of <no_rsc_apps> element.

- Mac: update script which builds our installer to work with Xcode 4.3 for Lion and later. Because PackageMaker is now distributed separately from Xcode, we emulate it using low-level tools.

- Mac: update build script to work with Xcode 4.3 for Lion and later. Xcode and the Mac OS X SDKs are no longer installed at fixed locations.

- lib: treat MINGW32 like CYGWIN32 (in 1 place - should do everywhere?) from Oliver

- client: delete sticky files when reset project

- client: if we get a job for which a GPU is missing, keep the RESULT record so that we can report it to the scheduler. Otherwise we'll keep getting the same job if the project has <resend_lost_results> set.

- Mac: Minor corrections to documentation and sample code.

- client: Re-introduce the WM_QUERYENDSESSION window message handler to the power management window proc, it was removed during one of the Win9x code scrubs. When we see it, inform the client it is time to shutdown.

- lib: Adjust #include files as requested by Oliver Bock.

- lib: fix typo

- client: don't request work for backup project for a processor type unless there are idle instances of that type

- client: improve "new version available" notice

- Mac: Eliminate extra output from wxMac build script.

- MGR: Use the same fix for the simple gui that we used on the advanced gui with regards to the menu on Ubuntu's interface.

I've just installed the 32-bit Windows version of v7.0.33 over the top of v7.0.31

All existing CUDA tasks (anonymous platform - Lunatics applications) showed with a much smaller estimate, and started to error out with the dreaded 'Maximum elapsed time exceeded'. New work was fetched with the correct estimates.

Hold on - I'm investigating.

ARGH - I think it must be changeset 25905:

•client: when estimating FLOPS for an anonymous-platform app version
for which no estimate has been supplied by user,
use (CPU speed)*(cpu_usage + 10*gpu_usage)
(add the 10*)

All existing CUDA tasks (anonymous platform - Lunatics applications) showed with a much smaller estimate, and started to error out with the dreaded 'Maximum elapsed time exceeded'. New work was fetched with the correct estimates.

That's what i found too, Edit: Actually it wasn't all, just most CUDA tasks that ended in 'Maximum elapsed time exceeded'

I had the same.
Over 30 computation errors in one day with some completing but most GPU apps error out.
I removed .33 and went back to .31 and not one error
even the tasks that downloaded while I was running .33 error out

What is up with the OSX only 7.0.34 build?(At least as of the time I post this) It has been 4 days and I have seen no release notes posted on it yet. Is this going to stay an OSX only release or are follow up versions for the other OSs coming. What was the big Bug in 7.033 that made it necessary to put out a special bug fix for OSX?

What is up with the OSX only 7.0.34 build?(At least as of the time I post this) It has been 4 days and I have seen no release notes posted on it yet. Is this going to stay an OSX only release or are follow up versions for the other OSs coming. What was the big Bug in 7.033 that made it necessary to put out a special bug fix for OSX?

It's probably more a case of "what are they waiting for, before they finish the job and build the Windows and Linux versions?"

There were something like 15 general tweaks and fixes copied across, before the code was tagged for v7.0.34

The Mac builds are done by Charlie Fenton, the Windows (and Linux) builds by Rom Walton. They work in different places, each to their own timetable. Charlie has been particularly active recently, because of the new release of the Mac Mountain Lion OS, which required some installer changes. I think he was just quick off the mark because of that.

What is up with the OSX only 7.0.34 build?(At least as of the time I post this) It has been 4 days and I have seen no release notes posted on it yet. Is this going to stay an OSX only release or are follow up versions for the other OSs coming. What was the big Bug in 7.033 that made it necessary to put out a special bug fix for OSX?

It's probably more a case of "what are they waiting for, before they finish the job and build the Windows and Linux versions?"

There were something like 15 general tweaks and fixes copied across, before the code was tagged for v7.0.34

The Mac builds are done by Charlie Fenton, the Windows (and Linux) builds by Rom Walton. They work in different places, each to their own timetable. Charlie has been particularly active recently, because of the new release of the Mac Mountain Lion OS, which required some installer changes. I think he was just quick off the mark because of that.

OK any bugs in 7.00.34 I need to watch out for in the new version? I'm looking to update my system to a newer version of BOINC in the next few days. I'm on 7.00.27 on OSX. I was told that 7.00.33 had some hard to swallow bugs in it. Is 7.00.34 mostly bug free so far? Is it worth jumping to? I am sort of looking for a list of bug fixes to be put out like it is for most new builds.

What is up with the OSX only 7.0.34 build?(At least as of the time I post this) It has been 4 days and I have seen no release notes posted on it yet. Is this going to stay an OSX only release or are follow up versions for the other OSs coming. What was the big Bug in 7.033 that made it necessary to put out a special bug fix for OSX?

It's probably more a case of "what are they waiting for, before they finish the job and build the Windows and Linux versions?"

There were something like 15 general tweaks and fixes copied across, before the code was tagged for v7.0.34

The Mac builds are done by Charlie Fenton, the Windows (and Linux) builds by Rom Walton. They work in different places, each to their own timetable. Charlie has been particularly active recently, because of the new release of the Mac Mountain Lion OS, which required some installer changes. I think he was just quick off the mark because of that.

OK any bugs in 7.00.34 I need to watch out for in the new version? I'm looking to update my system to a newer version of BOINC in the next few days. I'm on 7.00.27 on OSX. I was told that 7.00.33 had some hard to swallow bugs in it. Is 7.00.34 mostly bug free so far? Is it worth jumping to? I am sort of looking for a list of bug fixes to be put out like it is for most new builds.

Just look at Trac, just before a new Boinc is Tagged for release there will be a rapid number of changeset that'll be applied to the new version.