Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!andy From: andy@cbmvax.commodore.com (Andy Finkel) Newsgroups: comp.sys.amiga.programmer Subject: Re: CLI path Message-ID: <18603@cbmvax.commodore.com> Date: 6 Feb 91 00:05:45 GMT References: <18122@cbmvax.commodore.com> Reply-To: andy@cbmvax.commodore.com (Andy Finkel) Organization: Commodore, West Chester, PA Lines: 22 In article chris@genly.UUCP (Chris Hind Genly) writes: >Thanks for the reply. But I was interested in the mechanism by which the >inheritance takes place. How can a program I write discover what the path >is. How can a program I write pass a new path onto a CLI it starts up? DOS (or under 1.3 the Shell) copies the path list for the new CLI process, if it was started from a CLI process. The path list is hanging off your CLI process structure, and is basically a lined list of Locks. andy -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. "God was able to create the world in only seven days because there was no installed base to consider." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.