Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!sgi!scotth@harlie.SGI.COM From: scotth@harlie.SGI.COM (Scott Henry) Newsgroups: comp.sys.amiga Subject: Re: Using the PATH: device Message-ID: <23134@sgi.SGI.COM> Date: 9 Dec 88 17:07:20 GMT References: <401@solaria.csun.edu> Sender: daemon@sgi.SGI.COM Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 23 From article <401@solaria.csun.edu>, by ecphssrw@solaria.csun.edu (Stephen Walton): > > One warning about PATH: the ARP Assign command won't assign C: to > a file. "Assign C: PATH:C" gives you a "PATH:C Not a directory" > error. The 1.2 and 1.3 CBM Assign's work fine. > -- > Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge > RCKG01M@CALSTATE.BITNET ecphssrw@afws.csun.edu > swalton@solar.stanford.edu ...!csun!afws.csun.edu!bcphssrw I've been using the ARP assign to PATH: in my startup sequence for several weeks now. Which release of ARP are you using? I am using the latest that I know of: ARP Rel 2 (aka v1.(1?)). I am sure that I am not accidentally using the amigados assign, because I am doing the about following: "Assign c: path:c rexx: path:rexx", which only ARP will do. This is kind of a silly question, but are you sure you are doing the copy to PATH: BEFORE you do the assign? Scott Henry -- Scott Henry{or, also on the Internet:} #include