Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lanl!opus!ksitze From: ksitze@nmsu.edu (Kevin Sitze) Newsgroups: comp.sys.mac.programmer Subject: Re: Installing CODE as aVBL -- PART 2 Message-ID: Date: 25 May 89 13:26:57 GMT References: <5595@hubcap.clemson.edu> Sender: news@nmsu.edu Organization: NMSU Computer Science Lines: 27 In article: Michael writes: >Anyway, why would the machine crash if the installing program exits before the >VBL task comes up to go? I tried allocating my VBLTask record as a handle >and locking it in case the fact that it got disposed of was the problem, but >this didn't help. Read this again. Your problem lies in the fact that your exiting your program before dequeueing the VBL task. In other words, your entire application heap has suddenly gone to vapor-land and since the VBL manager is trying to run a task in this invalid region of memory, where there no longer is a task, the machine decides to upchuck it's problems directly to the user. The answer to your problem is to allocate the resource into the system heap. Go into ResEdit and enable the 'allocate in system heap' (?InSysZone?)flag for that resource. You shouldn't have any problem from there. -Kelesi -- +--------------------------------------------------------------------+ | From the Macintosh of: Kevin L. Sitze. This is ME: ksitze@NMSU.edu | +------------------------------------------------------+-------------+ | The difference between intelligence and stupidity is | Is this | | that intelligence has a limit. -- anonymous | better? | +------------------------------------------------------+-------------+