Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!ukma!psuvm.bitnet!cunyvm!STEVEG!MAINE.Bitnet!NAVPGS!4526P
From: 4526P@NAVPGS.UUCP
Newsgroups: comp.sys.amiga
Subject: ASSIGN T: RAM:T, and write-protect you boot disk
Message-ID: <0174526P@NAVPGS>
Date: Tue, 28-Apr-87 03:18:00 EDT
Article-I.D.: NAVPGS.0174526P
Posted: Tue Apr 28 03:18:00 1987
Date-Received: Fri, 1-May-87 02:24:46 EDT
Organization: Naval Postgraduate School
Lines: 19

I wanted to flip the write-protect tab on my workbench disk to
"protect" so I couldn't shoot myself in the foot.  The disk is
just about full, so I can't write anything useful to it anyway.
     
Unfortunately, I EXECUTE some things in my startup-sequence, so I
need a T directory.  A few days ago, I hit on the way out of the
trouble.  Just ASSIGN T: RAM: in the startup, and I can write
protect my Workbench disk.  A couple of questions for the net:
     
- Am I harming myself subtley by not having t/ on a non-volatile
device?  I don't use ED, so I'm not worried about t/ed-backup
     
- Why does EXECUTE need a t/ directory?
     
- Why hasn't anyone mentioned this method before?  Does everyone
work off of their workbench disk?  Or is it so obvious that only
dolts like me can't think of it?  :-b
     
Scott Norton 4526p.NavPGS.BITNET