Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ncrlnk!ncr-sd!tw-rnd!johnl From: johnl@tw-rnd.SanDiego.NCR.COM (John Lindwall) Newsgroups: comp.sys.amiga Subject: Re: ARP1.3 Assign queries Message-ID: <185@tw-rnd.SanDiego.NCR.COM> Date: 15 Dec 89 18:57:35 GMT References: <3030@usceast.UUCP> Reply-To: johnl@tw-rnd.SanDiego.NCR.COM (John Lindwall) Distribution: comp.sys.amiga Organization: NCR Corporation - Distributed Systems Lab Lines: 20 In article <3030@usceast.UUCP> yarnall@usceast.UUCP (Ken Yarnall) writes: > >Makedir creates all three directories (as it should), but Assign only performs >the first assignment (T: is the only of the 3 logicals that is attached to >anything after the machine boots). >The weird thing is, that if I perform the Assignment from the CLI after the >machine has booted, Assign is more than happy to play with multiple arguments. Sounds like you've got two versions of Assign in your system. It is possible that the startup-sequence is executing the C= Assign (which does not handle multiple assignments), then it sets up your path so that any further calls to assign invoke the ARP assign. Does this sound possible? Try typing which assign to see how many versions of assign are in your path and in what order they are accessed. -- John Lindwall | "Not my employer opinions; mine" johnl@tw-rnd.SanDiego.NCR.COM | a man, a plan, a beer, reeban alpa nama ----------------------------------+--------------------------------------------