Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!ux1.lbl.gov!beard From: beard@ux1.lbl.gov (Patrick C Beard) Newsgroups: comp.sys.mac.programmer Subject: Re: Installing a CODE as a VBL Message-ID: <2727@helios.ee.lbl.gov> Date: 26 May 89 02:53:14 GMT References: <5586@hubcap.clemson.edu> Sender: usenet@helios.ee.lbl.gov Reply-To: beard@ux1.lbl.gov (Patrick C Beard) Organization: Lawrence Berkeley Laboratory, Berkeley Lines: 27 In article ksitze@nmsu.edu (Kevin Sitze) writes: >In article: 02:20:48 GMT> Michael writes: >>I am trying to install a precompiled LSP unit as a VBL task. I compiled it >>as a CODE resource and all it does is a sysbeep(1). >> !!!!!!!!!! ... >>This crashes the machine every time. What's up? > >You might want to lock the handle... Sorry, but the problem is much more fundamental than that: in all new systems SysBeep calls the sound manager, and with all of those clever beeps we can have as 'snd ' resources, most definitely calls the Memory manager for a nice new handle to put them in. VBL routines may NOT call routines that move or allocate memory, period, as the Memory manager is NOT reentrant (i.e. can't be called again while it is processing some other request). Hope that helps. __________________ Patrick Beard PCBeard@lbl.gov BSI, Berkeley, CA ___________________