Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!snll-arpagw!paolucci From: paolucci@snll-arpagw.UUCP (Sam Paolucci) Newsgroups: comp.sys.amiga Subject: Re: No K directive? Message-ID: <87@snll-arpagw.UUCP> Date: 31 Mar 89 19:50:47 GMT References: <9888@polyslo.CalPoly.EDU> <7650@super.ORG> <16494@cos.com> Reply-To: paolucci@snll-arpagw.UUCP (Sam Paolucci) Distribution: usa Organization: Sandia National Labs, Livermore, CA Lines: 26 In article <16494@cos.com> andrews@cos.com (Andrew R. Scholnick) writes: ->> In article mp1u+@andrew.cmu.edu (Michael Portuesi) writes: ->>Funny, I had this problem too -- only it happened with my ->>startup-sequence. When writing scripts for the EXECUTE command, the K ->>or "KEY" directive is used to determine what the argument template for -> ->How come if the same file that got the 'K' error is rerun from CLI manually ->once or twice it will suddenly start to work again? I have done this (Arne ->Saknussem - {obscure joke}8-). Seriously, I set failat to 50 and run the ->offending file two or three times, each time it gets a little further ->until it runs through.... How come? Furthermore, I had one that used to work until I edited a couple of lines. Now when I execute the next procedure I get the KEY directive error. I think that this is a BUG in the execute command. I got around it by putting ".k foobar/k" on the first line of the procedure that is called (as suggested by somebody recently) and now works fine. Can somebody at CATS shed some light on this problem? -- -+= SAM =+- "the best things in life are free" ARPA: paolucci@snll-arpagw.llnl.gov