Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!brutus.cs.uiuc.edu!apple!portal!portal!cup.portal.com!Sullivan
From: Sullivan@cup.portal.com (sullivan - segall)
Newsgroups: comp.sys.amiga
Subject: Re: Help!  K directive!
Message-ID: <26875@cup.portal.com>
Date: 13 Feb 90 04:20:22 GMT
References: <9002120640.AA29085@astro.psu.edu>
Distribution: na
Organization: The Portal System (TM)
Lines: 50

>sequence" it errors out, saying
>EXECUTE no K directive
>execute failed returncode 20

Put the following lines at the beginning of your startup sequence:

.bra {
.ket }

Normally the bracket pairs are defined as "<" and ">".  If you redirect
both the input and output of any programs in your startup sequence, even
if it happens on separate lines, the pair is interpreted as a reference
to a script variable.  Since that script variable wasn't declared (via
a ".key" directive) you get the error shown.

>
>Now, at this point if I manually type "execute dh1:s/startup-sequence" it
>continues along fine.

This has to do with the differences between the first execute performed, 
and each subsequent one.

Btw: I find it much more useful to use --

    Newcli "NEWCON:0/40/639/359/Shell" from s:startup

which has the dual benefit of completeing my startup sequence from the
FFS partition, and leaving me with a shell that is sized optimally.

One revision level deeper, I've now changed this to --

    Ashell from s:startup
    wsize 1000 1000 AShell
    
Which works whether or not I'm using overscan.  
---

                           -Sullivan Segall
_________________________________________________________________

/V\  Sullivan  was the first to learn how to jump  without moving.
 '   Is it not proper that the student should surpass the teacher?
To Quote the immortal Socrates: "I drank what?" -Sullivan
_________________________________________________________________

Mail to: ...sun!portal!cup.portal.com!Sullivan or
         Sullivan@cup.portal.com