Thanks. ��This is fixed in��VMMaker.oscog-eem.772. ��It was an overzealous bounds check on a relocated call of an interpreter primitive. ��The VM complained and aborted because the interpreter primitive;s address was out of the code zone (as of course it should be; it is in the interpreter) ��i.e. the VM should not have performed the check and should not have exited. ��Apologies. ��I'll be building and uploading new VMs soon.