Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!unmvax!uokmax!drtiller
From: drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr)
Newsgroups: comp.sys.amiga
Subject: Can't run addtools, clkpointer, or starburst in 2.0.
Summary: No, they run, just not from the startup-sequence
Keywords: 2.0 ADDTOOLS CLKPOINTER STARBURST
Message-ID: <1990Sep28.144454.24937@uokmax.ecn.uoknor.edu>
Date: 28 Sep 90 14:44:54 GMT
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK
Lines: 21

OK, I finally found the program to add tools to the 2.0 tools menu.  I even
hit the jackpot and found a hack to give the clock pointer (which replaces
the "zzz" when doing Workbench operations) some life and one to allow CLIs
and Shells (well I know they are the same in 2.0) to recognize the * as a
wild card.  They actually run fine from a Shell, but I can't get them to run
from the startup-sequence.  Whenever I put the commands to run them into my
s:startup-sequence, and then re-boot, I get the "no K directive" response and
the startup-sequence is aborted.  Removing these commands restores the startup-
sequence but I don't want to have to run them after I re-boot.  The commands
work fine in a script file from a CLI too, but if I use and execute for that
script in the startup-sequence, I go back to the "no K directive" and the s-s
aborts wherever the execute is.  I noticed the user-startup which I assume is
for things to be added to (although I've never used it before) and put the
commands into that file.  This way is simply ignored the user-startup file
altogether.  I'm sure that's a different problem, but it's weird too.  I have
added several programs to the 2.0 startup-sequence including no-click and 
VirusX without any problems.  What causes these programs to be so difficult?
Any information would be greatly appreciated.

Rick Tillery (the much maligned but ever present displaced (and mourning the
loss ) Razorback )