Path: utzoo!utgpu!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ubvax!ardent!rap
From: rap@ardent.UUCP (Rob Peck)
Newsgroups: comp.sys.amiga
Subject: Re: Execute command bug with T: and :T/
Message-ID: <621@ardent.UUCP>
Date: 6 Oct 88 17:07:59 GMT
References: <4412@louie.udel.EDU> <7519@gryphon.CTS.COM>
Organization: Dana Computer, Inc., Sunnyvale, CA
Lines: 29

In article <7519@gryphon.CTS.COM>, jdow@gryphon.CTS.COM (J. Dow) writes:
> In article <4412@louie.udel.EDU> dan-hankins%cup.portal.com@UDEL.EDU writes:
> >I am nesting Execute commands in my startup-sequence.  Execute wants to
> >write to :T/Command-T-xx whenever I do.  Creating RAM:T and assigning T:
> >to RAM:T doesn't work.
> >IF NOT EXISTS RAM:T
> >  makedir RAM:T
> >ENDIF
> >Assign T: RAM:T
> That "if" is your problem. During startup-sequence RAM: does NOT exist so
> 1) it is not needed and 2) it forces a command-t-xx file into the current
> sys:t or t: directory. The solution is pull the makedir ram:t outa the if
> clause and do it every startup near the beginning - before any if's.

If RAM:T already exists, there might be an error code generated by
the MAKEDIR, potentially causing the script to fail unless FAILAT
is set to a high enough value.

One of the simplest ways of causing RAM: to exist at the start of
the world is the following in the startup-sequence.  The nice part
about it is that it won't cause a script failure if RAM: does not
exist:

	DIR > NIL: RAM:




Rob Peck