Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!mp1u+ From: mp1u+@andrew.cmu.edu (Michael Portuesi) Newsgroups: comp.sys.amiga Subject: Re: No K directive? Message-ID: Date: 29 Mar 89 19:31:43 GMT References: <9888@polyslo.CalPoly.EDU> Distribution: usa Organization: Mathematics, Carnegie Mellon, Pittsburgh, PA Lines: 35 In-Reply-To: <9888@polyslo.CalPoly.EDU> nschultz@polyslo.CalPoly.EDU (Ned W. Schultz) writes: > Could someone please explain the message, "No K directive."? A friend > is getting this when using the hd startup sequence from the 1.3 disks. > He tries to "execute dh0:s/hd-startup" and execute fails, breaking > out to a CLI with the above message. He has a 2090 (original model), > has 1.3 running (under a 1.2 ROM) and has one standard and two FFS > partitions, if those facts matter. 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 the Execute script is to look like. An example from the AmigaDOS manual: .k filename/a run copy to prt:+ echo "Printing of done" I boot off a floppy, whose startup-sequence transfers control to the hard disk as soon as possible. It EXECUTEs a startup-sequence on the hard disk. For some reason I have never been able to determine, the startup-sequence on my hard disk would fail to run with the "No K directive" error. I eventually fixed the problem by putting .k foobar/k as the first line in my startup-sequence, though someday I would like to know why I had to do that. It certainly didn't seem necessary. -- Michael Portuesi / Information Technology Center / Carnegie Mellon University INET: mp1u+@andrew.cmu.edu / BITNET: mp1u+@andrew UUCP: ...harvard!andrew.cmu.edu!mp1u+ The Amiga 1000 -- Support classic Amiga technology.