[comp.sys.mac.apps] Aask.init: how does it work?

rq02+@andrew.cmu.edu (Richard Quadrel) (12/21/90)

Aask is supposed to let you turn various inits on/off during startup.
So how do you tell it which ones?  My guess is that you need to hold
something down during startup (like the mouse button, or tab key or
something like that), the same way that the Init init works.  But I
don't know what to do... can someone help?
Thanks
Rich Quadrel
rquadrel@cad.cs.cmu.edu

francis@wolfman.cis.ohio-state.edu (RD Francis) (12/21/90)

In article <AbQDxP600WB8QChUNh@andrew.cmu.edu> rq02+@andrew.cmu.edu (Richard Quadrel) writes:
   Aask is supposed to let you turn various inits on/off during startup.
   So how do you tell it which ones?  My guess is that you need to hold
   something down during startup (like the mouse button, or tab key or
   something like that), the same way that the Init init works.  But I
   don't know what to do... can someone help?

Init cdev and Aask init work in an almost identical fashion, at least
as of the last Aask init version I saw (which may have been the
evidently-mistakenly-distributed beta).

To select which files not to load on a temporary basis, hold donw the
space bar (I think) on start-up.  Turn off (or on, for that matter)
the inits you want to temporarily en/disable.  select the button that
indicates your choices are temporary.

To "permanently" (stands up from rebooted to reboot, as opposed to in
an unchangeable fashion) change the status of an init, cdev or rdev
(AppleShare shows up, for instance), either do as above, selecting the
more permanent button (probably the default button), or choose the
init cdev/aask init icon from the control panel, and alter the files
there.  When using the control panel, you will need to reboot before
the init/cdev/rdev(s) become dis/enabled.

This is accomplished by the alteration of the type of the file.  INIT
type file (startup documents) become xNIT type file, and [cr]devs
become xdevs.  Important to note; I'm sure my old company wasn't the
only place where, when this was first noticed, concerns about it being
caused by a nasty virus were running rampant.
--
R David Francis   francis@cis.ohio-state.edu