Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!zardoz.cpd.com!tmiuv0!rick
From: rick@tmiuv0.uucp
Newsgroups: comp.sys.amiga
Subject: Re: ARRRRRRRRRRGGGGGGGGGHHHHHHHHHHHH!!!!!!!!!!!
Message-ID: <3754@tmiuv0.uucp>
Date: 30 Jul 90 11:07:34 GMT
References: <2649@mindlink.UUCP> <3413@leah.Albany.Edu>
Organization: Technology Marketing Inc., Irvine, CA
Lines: 40

In article <3413@leah.Albany.Edu>, wfh58@leah.Albany.Edu (William F. Hammond) writes:
> In article <2649@mindlink.UUCP> a217@mindlink.UUCP (Vincent Lim) writes:
>> ...
>>> >      EXECUTE: No K directive
>>> Ah, the dreaded "No K directive".  Try putting the following two lines in
>>>     .bra <
>>>     .ket >
>> ...
>>I'm not CBM but I do have an observation which I'd like to share. I've noticed
>>that if your script performs an Execute and you have no T: directory assigned
>>and no SYS:t directory exists or is not writable then you will get the bogus
>    My versions of "execute", both standard and ARP, attempt to create a "T"
> directory in the root above the current directory.  (Additionally, ARP's
> "execute" will assign "T:" to it.)  I am unable to provoke a "no K directive"
> message by eliminating ":T" and "T:".
>    My suspicion is that the message is triggered by the appearance in the
> script of both the '>' and '<' characters for input/output diversion.  Since
> these are the default "bra" and "ket" characters, "execute" is yelling about
> the absence of a ".key" at the top of the script.  For this most of the time
> redefining the "bra" and "ket" characters will take care of the problem.
> ----------------------------------------------------------------------
> William F. Hammond                   Dept. of Mathematics & Statistics
> 518-442-4625                         SUNYA, Albany, NY 12222
> wfh58@leah.albany.edu                wfh58@albnyvms.bitnet
> ----------------------------------------------------------------------

I don't mean to include all this stuff, but background is necessary.

Bill, that still doesn't explain why the SAME disk that's worked for God-
knows-how-long suddenly stops.  I've used the same beblistered disk for
over a year, and suddenly it stopped working.  The disk is fine, no bugaboos
on it (it's only used to boot), but she dinna wanna work no more.  Strange,
eh?  I'm sure stumped.
----------------------------------------------------------------------------
[- O] Rick Stevens
  ?   EMail: uunet!zardoz!tmiuv0!rick -or- uunet!zardoz!xyclone!sysop
  V   CIS: 75006,1355 (75006.1355@compuserve.com from Internet)

"A fertsneet without a gleekzorp is like a quobble without a fromm (sort of)"
----------------------------------------------------------------------------