Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!ur-tut!dmw3
From: dmw3@ur-tut.UUCP (David M Walsh Jr.)
Newsgroups: comp.sys.mac
Subject: Re: Yet more INIT questions
Message-ID: <390@ur-tut.UUCP>
Date: Mon, 2-Nov-87 17:02:38 EST
Article-I.D.: ur-tut.390
Posted: Mon Nov  2 17:02:38 1987
Date-Received: Sun, 8-Nov-87 15:35:07 EST
References: <3988@watdragon.waterloo.edu>
Reply-To: dmw3@tut.cc.rochester.edu.UUCP (David M Walsh Jr.)
Organization: Univ. of Rochester Computing Center
Lines: 29

In article <3988@watdragon.waterloo.edu> palarson@watdragon.waterloo.edu (Paul Larson) writes:
>I have two questions.
>
>1. What should not be done by an INIT?   Are there any managers or drivers which are not initialized at the time of INIT execution?  Is there anything which is absolutely verboten?
>
>2. How doest one go about installing a background task with an INIT 
>(as per JClock (a clock in the menu-bar))?  Any suggestions would be 
>appreciated; source would be manna from heaven (Pascal preferred, but under 
>duress, I'll read anything.)
>
>Thanx in advance,
>	Johan Larson

I too am interested in these arcane resources.  If someone could post a simple
INIT to the net that installs a little routine that needs some time from the
system from time to time I would be in heaven.

My other question about INITs is how do they handle variables from say a
Pascal routine??  I'd love to be able to keep some data around, but I have
no ideas on how to go about this.

If anyone cares, I'm writing (trying at least) it in LightSpeed Pascal 1.0 and
I can generate the code resources easily enough, but it's making the program
keep itself in memory and keeping the variables intact that are the major
stumbling blocks here.

Any info will be greatly appreciated,

  Dave Walsh - still trying to be a Mac hacker...