I'm on OSX, I will look into the applescript route.
It's a shame there doesn't seem to be any direct access within Max itself, it would be nice to be able to dump the max window into a log file for debugging long performances, especially when they crash Max...
As it is I've used m.marcoll's nifty uconsole object to display and create a logfile of sorts. Naturally this only reflects what I choose to display, not the more useful error and warning messages in the max window.
The error message was complaining pretty specifically that it was
trying to load MathLib without success. MathLib was the pre-Carbon
library, and normally the only externals trying to load it are
But if the combo updater actually managed to screw up existing Carbon
libs so that they tried to load MathLib, well, with sufficient screw
ups anything's possible.
Okay, so this is a known issue. After I saw the first few reports of
the issue on this list I began poking at the problem. The patch
updater nukes the resource fork on the vecLib CFM stub during the
install. Unfortunately CFM needs the resource fork to locate symbols
in the corresponding mach-o. In the future, we're going to be more
careful about the way we patch binaries with this issue in mind. The
vecLib library appears to be the only library that was affected, but
enough folks use vecLib from CFM that there was massive bustage.
In the meantime, the Combo update is infact the recommended
workaround. If your auto update reports the download size to be under
65mb, please manually install the Combo update instead.