drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr) (09/28/90)
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 )
lron@easy.HIAM (Dwight Hubbard) (09/29/90)
>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 ) The problem is most likely that you have some redirection characters run < nil: >nil: dummyprogram this causes problems because when the file gets executed the Ami sees the two < > and figures the text (nil:) in the middle is the name of a variable it then printes the no K directive message since you don't have a K directive to define the variable. There are two solutions to this, you can change the order of the redirection characters in the line. run > nil: < nil: dummyprogram or you can add the following to the top two lines of the file. .bra [ .ket ] This tells the Amiga to use the [ ] characters instead of the < > and is the easier solution if you have more than one line with the redirection characters. -- -Dwight Hubbard -Kaneohe, HI -UseNet: uunet.uu.net!easy!lron Genie: D.Hubbard1 GT-Power: 029/004 -------------
billsey@agora.uucp (Bill Seymour) (10/03/90)
In article <1990Sep28.144454.24937@uokmax.ecn.uoknor.edu> drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr) writes:
: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.
When you get a 'no K directive' it's happening when you are trying
to execute a script. Probably during the 'Execute S:User-Startup' line in
the 2.0 Startup-Sequence. Check to make sure you don't have any redirected
commands in the User-Startup (Run >nil: <nil: someFile). If you do, you need
to add the .bra and .ket commands at the start of the User-Startup. (ie.,
.bra {
.ket }
) All new commands you want to add should probably be done within the User-
Startup, since that way when Commodore provides an update, you can just copy
their disks onto your system. (I don't think they're including a User-Startup
file anymore...)
:Rick Tillery (the much maligned but ever present displaced (and mourning the
:loss ) Razorback )
--
-Bill Seymour billsey@agora
***** American People/Link Amiga Zone Hardware Specialist NES*BILL *****
Bejed, Inc. NES, Inc. Northwest Amiga Group At Home Sometimes
(503) 281-8153 (503) 246-9311 (503) 656-7393 BBS (503) 640-0842