Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!cs225bx
From: cs225bx@ux1.cso.uiuc.edu
Newsgroups: comp.sys.mac.misc
Subject: Re: An INIT Chooser
Message-ID: <18000076@ux1.cso.uiuc.edu>
Date: 8 Oct 90 17:41:00 GMT
References: <12385@chaph.usc.edu>
Lines: 16
Nf-ID: #R:chaph.usc.edu:12385:ux1.cso.uiuc.edu:18000076:000:851
Nf-From: ux1.cso.uiuc.edu!cs225bx    Oct  8 12:41:00 1990


>Basically ALL of the INIT picking programs I've tried (init cdev, INITPicker,
>etc.) is either a) changing the filetype or b) altering the "No INIT"
>resource bit (mess with ResEdit). I'm sure SAM takes that all into account,
>so  basically: there is no way, unless someone's thought of some
>ingenious way to patch into the system and selectively launch files (a
>beastly task, at best). You may want to try an init manager which can say,
>move the INITs in and out of a folder instead of altering the resources.

I use INITpicker and SAM never goes off at all.  INITpicker allows you
ON STARTUP to selectively choose which INITS you wish to run.  You can also
choose which INITS to run at anytime by accessing its cdev, and when you change
an INIT's "selection  to run or not to run" SAM NEVER INTERCEPTS that.

ALan Levy
cs225bx@ux1.cso.uiuc.edu