Conference hydra::amiga_v1

3229.0. "startup-question" by FRSOLD::ZIMMERMANN (Ralf, DTN *861-3236, @FRS) Mon Dec 18 1989 15:42

I have a little STARTUP-question: The following was my dh0:s/startup-sequence
until OCT-1989. After some changes (see 18-DEC-1989) i receive the following
error message during startup from DF0:s/startup-sequence:

        EXECUTE failed: no K directive !

        
The last is my DF0:s/startup-sequence. I'm sure, the error must be in the new
startup-sequence, because executing  S:(mean DH0:s)test.com generates
NO error, and replacing the new startup with the startup from OCT-1989 brings
up NO error too.
Can anybody explain me this Error-message? In the docs are only the ex-
planations of the '.'-parameters.

Thanks in advance,

Ralf


;
; ===== Startup-Sequence [RZ] 09-Oct-1989 =====
;
;
resident C:echo                         ; damits schneller geht
;
ECHO " [ Begin Startup-Sequence ]"
;
;
;Addbuffers df0: 10                      ;
;c:SetPatch >NIL:                        ; Systemroutinen korrigieren
cd c:                                   ; wg. Command-Image-Aktiv.
;Sys:System/FastMemFirst                 ; C00000-Speicher an Listenende
;BindDrivers                             ;
;
SYS:SYSTEM/setfont pearl 8              ; neue Schrift
;
SetClock load                           ; Systemzeit aus Uhr laden
FF >NIL: -0                             ; Textausgabe beschleunigen
;
resident CLI L:Shell-Seg SYSTEM pure add     ; Shell aktivieren
mount newcon:
;
failat 11
run execute s:StartupII                      ; Resident-Befehle aktivieren
wait >NIL: 5 mins                            ; Warten auf Ende von StartupII
;
;;makedir RAM:C                                ; fuer spaeter
;
;;path RAM:C c: sys:utilities sys:system s: sys:prefs ADD ; Pfad festlegen
path c: SYS:SEDT sys:utilities sys:system s: sys:TERM sys:tools sys:prefs ADD
;
RELABEL DRIVE RAM: NAME RAM
;;ECHO "   - COMMAND-Images --> RAM:C"
;;COPY C:#? RAM:C quiet
;;COPY SYS:SEDT/sedt RAM:C quiet                ; spaeter
;
;;ECHO "   - RAD-Ram-Disk Installation"
;;MOUNT RAD:
;;RELABEL DRIVE RAD: NAME RAD
;;;DISKCHANGE RAD:
;
;;;LoadWB delay                                 ; Vor Weitermachen warten
;;;endcli >NIL:                                 ; HIER NO WORKBENCH
;
;;cd s:                                         ; was tun ...
CD RALF:                                        ; oder sonstwohin
;
NEWSHELL NEWCON:0/0/640/256/AmigaShell          ; zusaetzlich oeffnen
;
ECHO "   - Start VirusX"
run SYS:system/VIRUSX32 87 0
;
ECHO "   - Start Utilities"
run SYS:utilities/CLOCK DIGITAL2=396,0 24HOUR
;run SYS:utilities/PERFMON
;
ECHO "   - Checking for Memos"
run APPLIC:MEMOPAD/checkmemo
;
;
ECHO " [ Startup-Sequence complete ]"
;
;
;===== End of Startup-Sequence [RZ] =====
;

;
; ===== Startup-Sequence [RZ] 18-Dec-1989 =====
;
;
Resident c:Echo               ; damits schneller geht
ECHO " [ Begin Startup-Sequence ]"
;
SYS:system/FastMemFirst                 ; C00000-Speicher an Listenende
SetPatch >NIL:                    ; Systemroutinen korrigieren
;
;
Addbuffers DF0: 10
Addbuffers DF1: 10
;
cd c:                                   ; wg. Command-Image-Aktiv.
;
SYS:system/SetFont Pearl 8              ; neue Schrift
;
SetClock load                           ; Systemzeit aus Uhr laden
FF >NIL: -0                             ; Textausgabe beschleunigen
;
resident CLI L:Shell-Seg SYSTEM pure add     ; Shell aktivieren
mount newcon:
;
failat 11
run execute s:StartupII                      ; Resident-Befehle aktivieren
wait >NIL: 5 mins                            ; Warten auf Ende von StartupII
;
;;makedir RAM:C                                ; fuer spaeter
;
;;path RAM:C c: sys:utilities sys:system s: sys:prefs ADD ; Pfad festlegen
path c: SYS:SEDT sys:utilities sys:system s: sys:TERM sys:tools sys:prefs ADD
;
RELABEL DRIVE RAM: NAME RAM
;;ECHO "   - COMMAND-Images --> RAM:C"
;;COPY C:#? RAM:C quiet
;;COPY SYS:SEDT/sedt RAM:C quiet                ; spaeter
;
;;ECHO "   - RAD-Ram-Disk Installation"
;;MOUNT RAD:
;;RELABEL DRIVE RAD: NAME RAD
;;;DISKCHANGE RAD:
;
;;;LoadWB delay                                 ; Vor Weitermachen warten
;;;endcli >NIL:                                 ; HIER NO WORKBENCH
;
CD RALF:                                        ; oder sonstwohin
STACK 10000                                     ;
;
NEWSHELL NEWCON:0/0/640/256/AmigaShell          ; zusaetzlich oeffnen
;
ECHO "   - Start Utilities"
run >NIL: SYS:utilities/CLOCK DIGITAL2=396,0 24HOUR
DMouse -a4 -l1 -s250             ; deaktivieren mit DMouse quit
run >NIL: memgauge 640 57
;run QMouse -An -K0 -S250 -Z0    ; deaktivieren mit <CTRL><LA><ESC>
;run SYS:utilities/PERFMON
;
ECHO "   - Start VirusX"
run SYS:system/VIRUSX40 -x87 -y0
;
ECHO "   - Checking for Memos"
run APPLIC:MEMOPAD/checkmemo
;
;;  Dial-In-Line klarmachen REM:
;
;
ECHO " [ Startup-Sequence complete ]"
;
;
;===== End of Startup-Sequence [RZ] =====
;

;
mount dh0:
;
   SYS:system/DefDisk DH0:
   DH0:C/makedir ram:tr
    DH0:C/assign t: ram:tr
;;   dh0:c/run DH0:C/execute DH0:s/Startup-Sequence
   execute s:Startup-sequence
;

    Ralf,
    
         It looks like you added a hard drive, congrats.  At the end 
    of your new startup it looks like you're transferring control by
    executing s:startup-sequence.  Are you using ARP?  I can't remember
    for sure, but I have seen that error message before.  It might have
    to do with some sort of incompatibility between ARP's Execute, and
    AmigaDOS's Execute.  Perhaps Run'ning Execute will do the trick.
    Maybe I'm grasping at straws.
    
         Generally speaking, my floppy df0:s/startup-sequence is _very_
    small.  I do a Binddrivers (or Mount in your case), and then transfer
    control.  This won't solve your problem, but it will speed up your
    boot time.
    
    ~Steve

I experienced this myself when I tried to nest execute files. If you look in
the documentation for the execute command you will find that they provide
for KEYS. I believe that is the missing "K" directive. Keys are referenced
in the command file with matching "<" ">" pairs. It appears that the search
for these characters includes the comments also.  To fix this problem the
execute command provides the "BRA" and "KET" options. When you are at the 
command level there is no need for keys. When you are nested there is. I
haven't looked at this careful enough to give a complete explanation but I 
think this will help.

The error message
        EXECUTE failed: no K directive !

One of the offending lines from the nested file
	;run QMouse -An -K0 -S250 -Z0    ; deaktivieren mit <CTRL><LA><ESC>
        						    ^    ^^  ^^   ^

Hope this helps and someone doesn't tell me I'm all wet.

-Tom-

    I haven't got my manuals here so I'm working from memory but I'm sure
    I've seen this problem too.
    
    The doco states that the .KEY parameters are identified in
    executable scripts by the <...> characters surrounding the parameter,
    and that they can be changed using the 
    
    	.BRA
    	.KET
    
    directives at the top of the script. What I found was that if I used
    the < or > *anywhere* in the script for I/O redirection (or anything
    else) the Execute command seemed to think I wanted to do some parameter
    substitution, and of course my boot floppy df0:s/startup-sequence
    didn't have any parameters, so CRUNCH!!! It may even be the case that
    the < and > characters in commented lines ;;; will cause this to occur.
    
    The solution I used was to place the lines
    
    	.BRA {
    	.KET }
    
    at the top of the script. This solved the problem. That was under v1.3,
    and it still works for me since I changed to v1.3.2 and ARP 1.3
    although I haven't gone back to check whether the error would still
    occur under the new environment (if it ain't busted, don't fix it!).
    
    I have one problem with my startup: I boot from floppy which mounts
    vd0: and dh0: and then Executes dh0:s/startup-sequence. The problem is
    that Execute creates vd0:t/Command-0-T01 (or whatever) and does not
    automatically delete it after it finishes. Annoying, but it doesn't
    seem to cause any problems, but it may be a result of the fiddle I used
    above.
    
    On the whole, I find Execute scripts to be pretty useless and I use
    ARexx to do anything like that.
    
    Hope that helps some. All the best for the New Year!

    
    I believe that if you 'run' the batch file, the tempory file is not
    created.  Here's my floppy boot file...
    
    	c:SetPatch >NIL: -r
   	Sys:System/FastMemFirst
    	c:BindDrivers
    	c:Run Execute dh0:s/HDBoot
    	c:EndCLI >NIL:
    
    This batch file transfers the boot process over the hard drive without
    any hassles.
    
    Ed.
    
    
    

OK friends,

it's fixed.

1.) YES, if i RUN EXECUTE s:startup-sequence it's ok. (don't forget to send
the break signal from STARTUPII to the right process number !)

2.) next solution: insert .BRA and .KET at the top of the command-file

3.) and last not least, the main reason for the trouble was my extreme doc-
umentation-'mania'. I removed the '<>' within the ;comment-line and it
works too.


THANK YOU VERY MUCH for the quick response. I wish a merry Christmas and
a happy new year to all AMIGAS/AMIGOS in the universe.


thanks again,

Ralf
====

    I'll tack this on here since it deals with startup-sequences.
    What exactly does FF (FastFonts) buy me (or not buy me)? I've had
    it in and out of my startup-sequence and can't detect a difference
    whether I use it or not. (1Meg A500 - WB 1.3.2).

						-Dom

    According to the Enhancer docs:

"FF (FastFonts) is a program written by Charlie Heath, of Microsmiths,Inc.
 FF speeds up the display of text on the Amiga."

    Sorry, but that's as much as I know about it. If it makes you feel any
    better, I don't notice any difference either. I believe you need it if
    you want to use Charlie Heath's SIESTA font, or VLT's slightly modified
    MYSIESTA version.

    Pete