Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!imagen!atari!portal!cup.portal.com!dan-hankins
From: dan-hankins@cup.portal.com
Newsgroups: comp.sys.amiga
Subject: Re: Execute bug with :T and T:
Message-ID: <9999@cup.portal.com>
Date: 13 Oct 88 00:46:52 GMT
References: <9840@cup.portal.com> <18672@cs.tcd.ie>
Organization: The Portal System (TM)
Lines: 26
XPortal-User-Id: 1.1001.5361

In article <18672@cs.tcd.ie> ecarroll@cs.tcd.ie (Eddy Carroll) writes:

>Maybe I'm missing something subtle here, but why not just do a CD RAM:
>before you Execute the sub-batch file? I just tried it, and it seems to
>work fine. And it'll create your ram disk for you quicker than DIR >NIL: RAM:
>will as well :-)

Yes, I'm afraid you did miss something subtle.  I want my directory
assignment to remain SYS: when I exit from the first-level Execute script.
I tried what you suggested;  but instead of leaving the directory
assignment at RAM: when I finish with the second-level scripts, I did the
following:

     cd RAM:
     execute script-1
     execute script-2
     cd SYS:

When the first-level script finished, Execute tried to delete Command-0-Txx
from the current disk, as in :T/Command-0-Txx.  I hit CANCEL on the
requester, and the script finished quietly.

I'll just wait for 1.3.


Dan Hankins