Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!shadooby!accuvax.nwu.edu!tank!ncar!ames!pasteur!helios.ee.lbl.gov!ux3.lbl.gov!beard
From: beard@ux3.lbl.gov (Patrick C Beard)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ?? TSR in a Mac? If not DA.
Message-ID: <2350@helios.ee.lbl.gov>
Date: 6 Apr 89 16:47:38 GMT
References: <1474@ccnysci.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: beard@ux3.lbl.gov (Patrick C Beard)
Distribution: comp.sys.mac.programmer
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 17

A recent BYTE issue covered the ins and outs of writing INITs, CDEVs, and
other ilk.  This is the best method for installing code that hangs around
for subsequent use.  I find that the best way to load this code is to
use a separately compiled code resource of my own type, set the system heap
bit, GetResource & DetachResource, and hook the data collection part into
VBL.  Patch a trap like SystemTask to get time from the system to for example
open a file and write the data to it.  Then use your application to merely
examine the data file.  Use a CDEV to control the behaviour of the code.

Anyway, check out that issue of BYTE.  A couple of months back.


+----------------------------------------------------------------+
 \   Patrick Beard                 "Badges?                       \
  \    Berkeley Systems, Inc.        I ain't got to show you...    \
   \      PCBeard@lbl.gov                 ...NO STINKING BADGES!"   \
    + ---------------------------------------------------------------+