Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!caip!lll-crg!seismo!gatech!gitpyr!cc100jr From: cc100jr@gitpyr.UUCP (Joel Rives) Newsgroups: net.micro.amiga Subject: Re: Re: Locking LC1 {was Kermit, also Workbench Suggestion} Message-ID: <1899@gitpyr.UUCP> Date: Wed, 25-Jun-86 11:45:44 EDT Article-I.D.: gitpyr.1899 Posted: Wed Jun 25 11:45:44 1986 Date-Received: Sat, 28-Jun-86 04:10:40 EDT References: <8606191919.AA13745@cory.Berkeley.EDU> <1884@gitpyr.UUCP> <3402@amdahl.UUCP> Reply-To: cc100jr@gitpyr.UUCP (Joel Rives) Organization: Georgia Institute of Technology, Atlanta Georgia Lines: 27 In article <3402@amdahl.UUCP> acs@amdahl.UUCP (Tony Sumrall) writes: >In article <1884@gitpyr.UUCP> cc100jr@gitpyr.UUCP (Joel M. Rives) writes: > >> As an aside, I was not aware - until a couple of days ago - that any- >> thing loaded in ram via copy to ram: can be invoked without >> the ram: path extension. >> >To the best of my knowledge this is not true under 1.1. What *is* true is >that the current directory is searched prior to C:. Could this be your >situation? >-- Nope. My current directory at the time is a subdirectory on df1:. I have an Execute file called make which is located in ram:. I can type execute make and it works! Ya got me!?! -- Joel Rives USMAIL: Georgia Insitute of Technology, Atlanta Georgia, 30332 USENET: gatech!gitpyr!cc100jr BITNET: gatech!gitvm1!cc100jr "Remember, no matter where you go, there you are!" << Buckaroo Banzai >>