oh hey, look at that!

Apparently it's a known issue with vb 4.2.2 that didn't show up in their pre-release testing. I've applied one of the fixes (namely: ignoring E_STRICT and E_DEPRECATED messages), which should suppress that.

Thanks for mentioning it!