startup-seq

[lionstorm]

Hi all,
I added buffers to some drives on my startup-sequence but if drive is missing, I get the message can not find device and have to press retry or cancel.
ex : addbuffers df1: 50
But how to avoid this message and let the s-s go on when the df1 is disconnected ? How to tell the system "well if the device is not there just forget" instead of "well the device is not there, what should I do : ask the guy who switch me on" ?
lio

[scholle]

Hi, lio!

Try the following:

assign >NIL: DF1: exists
IF NOT WARN
    ADDBUFFERS >NIL: DF1: 50
ENDIF

[lionstorm]

Thanks, it looks good.
what the >NIL: is supposed to do ? (I am no developper)
Lio

[Thomas]

The ">" sign redirects the output to the file following the sign. NIL: is the AmigaDOS trashcan, it trashes everything written to it.

So if the addbuffers command does not stop the script the addition of ">NIL:" to the command will be sufficient. You may also add the line

failat 21

to the top of the script so it will bever be stopped by a failing command. (Failat sets the smallest return code which will stop the script. And a failing command usually returns 20.)

Bye,
Thomas

[lionstorm]

Thanks Thomas for sharing this. So I should put the failat 21 before the assign ?
Lio

[zipper]

I use failat 21 on the top of startup scripts, so they do not freeze even if I forget to remove obsolete lines from them...

[that_punk_guy]

zipper wrote:
I use failat 21 on the top of startup scripts, so they do not freeze even if I forget to remove obsolete lines from them...

That's akin to painting over rising damp, really though... I never used a failat in five years of constant (and I mean constant) Amiga use. It's better to know if something's going wrong.

[zipper]

Yeah, you do know when using RTG screenmode you get black screen by startup and begin to change monitor/lead/boot partition etc etc. to see what's happening...