antunes@ASTRO.PSU.EDU (Alex Antunes) (02/12/90)
Hello. Serious problem time.
I have an A500 with kickstart1.2 and a hard drive. I have my bootup disk
run bindrivers, mount dh1:, then execute startup-sequence on dh1: which
then handles everything else.
I had a system lockup. I couldn't fix it, so I turned off the computer,
then turned it backon 30 seconds later.
Now, when it gets to the line of the bootup disk of "execute dh1:s/startup-
sequence" it errors out, saying
EXECUTE no K directive
execute failed returncode 20
Now, at this point if I manually type "execute dh1:s/startup-sequence" it
continues along fine.
Well,not really fine... it crashes at my next execute in the startup
file, but i found if i start GOMF3.0 running it never has a problem there.
So, how can I fix this K directive problem? And, as a bonus question, why
does it guru at the next execute if I don't have gomf running, but works
fine if I do?
thanks, one and all. sandy
------------
Sandy Antunes "the Waupelani Kid" 'cause that's where I live...
antunes@astro.psu.edu Penn State Astronomy Dept
--- "once in a lifetime there comes a time... but this ain't it" ---Sullivan@cup.portal.com (sullivan - segall) (02/13/90)
>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