Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!necntc!linus!philabs!lamont!adam
From: adam@lamont.Columbia.edu (adam levin)
Newsgroups: comp.sys.amiga
Subject: Re: Sys:System vs. System:
Message-ID: <384@lamont.Columbia.edu>
Date: 1 Mar 88 20:28:27 GMT
References: <7025@agate.BERKELEY.EDU> <365@sas.UUCP>
Organization: Lamont-Doherty Geological Observatory N.Y.
Lines: 33
Summary: :t -> t: hack

In article <365@sas.UUCP>, bts@sas.UUCP (Brian T. Schellenberger) writes:
> . . . And why can't AmigaDos put temp files in t: intead of @#*%! 
> <drive>:t for crimenie sake?  It's durned annoying having to hear the
>                                                          --Brian.
> (Brian T. Schellenberger)				 ...!mcnc!rti!sas!bts

I asked myself this same question, and found that the cause of this problem
is c:Execute.  If you have a file-zapping program, here are the changes.

First rename c:Execute to c:Execute_tru (or whatever you like), then file-
zap c:Execute like so:

1) Change the one reference to ":T/Command-0-Tnn" to "TT:Command-0-Tnn"
2) Change the one reference to ":T" to "T:".
And, each time you boot (preferably include this in your Startup-Sequence):
3) Assign T: RAM: (or wherever you like)
4) Assign TT: T:

Note that in step one, zapping it to "T:/Command-0-Tnn " (note the trailing
space) or " T:/Command-0-Tnn" (now note the leading space) will not work.
A trailing space won't work because the "nn" in the string gets modified
(it receives the "unique" tag for this execute job) and everything has been
shifted left one character.  The leading space won't work because it is
considered to be part of the filename.

Hmmm, now that I think about this, you may need to have an undoctored
c:Execute on your boot diskette.  I know I do! :-)

Adam Levin
-- 
Phone:  (914) 359-2900 x340
Post:   Lamont-Doherty Geological Observatory / Palisades, NY 10964
USENET: {ihnp4, decvax, seismo} philabs!lamont!adam
ARPA:   lamont!adam@columbia.edu