Path: utzoo!utgpu!watmath!att!pacbell!ames!apple!bionet!csd4.milw.wisc.edu!uakari.primate.wisc.edu!ark1!nap1!asdcds!staatsvr
From: staatsvr@asdcds.cds.wpafb.af.mil (Vern Staats; ASD/SCED;)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Solution for EXECUTE: No K Directive
Keywords: AmigaDOS, execute, terrible documentation
Message-ID: <248@nap1.cds.wpafb.af.mil>
Date: 2 Aug 89 17:38:03 GMT
References: <3020@blake.acs.washington.edu>
Sender: news@nap1.cds.wpafb.af.mil
Reply-To: staatsvr@asdcds.UUCP (Vern Staats)
Organization: US. Air Force, ASD, Wright-Patterson AFB
Lines: 17

In article <3020@blake.acs.washington.edu> dlarson@blake.acs.washington.edu (Dale Larson) writes:
>Thanks to hcobb@walt.cc.utexas.edu, I solved the problem which was causing
>my script to bomb with the error "EXECUTE: No K Directive"  The solution
>was to begin the file with two lines: ".bra {" and ".ket }".  
>
  I recently installed a hard drive on my A1000 and got the same error message
when the startup-sequence on the slow file system partition tried to execute
the startup-sequence on the fsf partition.  I too could execute the offending
script "manually" with no problem.  After lots and lots of test cases &
reboots I found that if I deleted a big chunk of comments in the startup-seq
the problem went away.  Looks to me like there's a limit to how many ;comment
lines execute can handle.

Boolean orthogonal(char *my_opinions, char *employer_opinions)  {return(TRUE);}
INET:  staatsvr@asd.wpafb.af.mil                          ///    Honey, I
UUCP:  nap1!asd!staatsvr                              \\\///   dereferenced
Vern Staats, ASD/SCED, WPAFB OH 45433, 513-255-2714    \XX/      the kids