Path: utzoo!attcan!uunet!husc6!ukma!uflorida!haven!cvl!eneevax!smaug
From: smaug@eneevax.UUCP (Kurt Lidl)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Execute command bug with T: and :T/
Summary: Ram: problem?
Message-ID: <1804@eneevax.UUCP>
Date: 2 Oct 88 16:46:00 GMT
References: <9550@cup.portal.com>
Reply-To: smaug@eneevax.umd.edu.UUCP (Kurt Lidl)
Followup-To: comp.sys.amiga.tech
Distribution: na
Organization: University of Merryland, EE Computer Staff
Lines: 33

In article <9550@cup.portal.com> dan-hankins@cup.portal.com writes:
>HELP!!!!!!!
>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

Is the Ram: disk already activated (by a previous access) at this point
in the startup-sequence?  I do the same type of thing in my startup
files, and have not problem...  My idea is simply that the first access
to Ram: is often swallowed...

Of course, a much better solution is to use Matt Dillon's csh/shell program
to do all your system housekeeping.  I personally use teh modified one that
has command-recall and editing...  It works great...

>Execute Setup1 ;Requester is put up at this point.  Clicking on CANCEL causes
>               ;execution to continue normally
>Execute Setup2 ;No requester asked for.

Kurt Lidl
>Dan Hankins


-- 
==================================================================
==  Kurt J. Lidl  (smaug@eneevax.umd.edu)	(301)454-3184	==
==  UUCP: [seismo,allegra]!umcp-cs!eneevax!smaug		==
========"It's after 3am, no point in going to sleep now..."=======