Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-cs!crayview!imp
From: imp@crayview.msi.umn.edu (Chuck Lukaszewski)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Using VBL Tasks in Inits...
Summary: Must lock the init
Message-ID: <10569@umn-cs.CS.UMN.EDU>
Date: 27 Dec 88 22:58:33 GMT
References: <6865@netnews.upenn.edu>
Sender: news@umn-cs.CS.UMN.EDU
Lines: 17

In article <6865@netnews.upenn.edu>, bell@eniac.seas.upenn.edu (Mike Bell) writes:
> 
>    I've written an init that Installs a VBL task. Unfortunately, the procedure
> is executed exactly once. It would seem that the vblcount value is not being
> reinitialized, so the routine is being removed from the Queque; I am updating
> it though. Are there any special precautions that must be taken to install a
> VBL task from within an INIT.

Since the VBL task must be executed in order to refresh the queue entry, I
would surmise that the code itself is no longer present.  You will want to
put your code in the system heap, or drop BufPtr and install it in high 
memory.  This will ensure that it doesn't go away.  If your process is intended
to be permanent once the system is booted, you ought to go with the high
memory option.

______________________________________________________________________________
Chuck Lukaszewski          imp@crayview.msi.umn.edu               612 789 0931