Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!dawg6844
From: dawg6844@uxa.cso.uiuc.edu (Dan Walkowski)
Newsgroups: comp.sys.mac.system
Subject: Re: System 7 (More Ideas for INITS)
Message-ID: <1991Apr30.221102.27943@ux1.cso.uiuc.edu>
Date: 30 Apr 91 22:11:02 GMT
References: <1991Apr30.085554.18064@uokmax.ecn.uoknor.edu> <18839@sdcc6.ucsd.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 30

bochen@sdcc13.ucsd.edu (Meathead) writes:

>As I understand it, one of the best things about system 7.0 is that
>it should eventually improve compatibility.  95% of my bugs with
>6.07 can be traced to some damn INIT that I can't live without.  I'm
>hoping that I can cut at least 70% of my INIT's when I get 7.0.  In
>summary, I think that writing INIT's are not the greatest idea and
>perhaps a program could be made that runs in conjunction with MF
>rather than an INIT.  


Yes. Yes. Yes. 
Lets stop Init (Ok, System Extension) Proliferation.  Now that every Mac
will be running 'Multifinder' (as it were), lets make small PROGRAMS
that do neat things, instead of Init hacks that patch stuff better left
unpatched.
I was able to eliminate about 14 Inits when I went to 7.0.
The only ones I run are:
After Dark
PopChar
Disinfectant
SoundMaster
SuperClock


--
_______________________________________________________________________________
Dan Walkowski                          | To understand recursion, 
Univ. of Illinois, Dept. of Comp. Sci. |   you must first understand recursion.
walkowsk@cs.uiuc.edu                   |