@pbox - I'd never seen that error before, so tried it in game with your notebook. At first glance that doesn't look like something generated by the Python scripting. It's not throwing an exception at all, so I'm not sure where exactly to look in the scripts to see what is going on. My guess is that it's being generated in the UI code, either the C code or the AS - I think probably this happens before it ever gets to Python, or possibly the UI is only throwing a 32-bit value to the Python and so it's forced to return an error back to the UI.
In short, I'm just not sure where to look, and it's quite possible the bug is in C where it's completely inaccessible to us, or the AS which is only slightly more accessible.
