Path: utzoo!attcan!uunet!munnari!phi
From: phi@munnari.oz (Philip F. Hingston)
Newsgroups: comp.sys.amiga
Subject: Problem with paths and Execute()
Message-ID: <2347@munnari.oz>
Date: 6 Sep 88 23:20:54 GMT
Organization: Comp Sci, Melbourne Uni, Australia
Lines: 25


	Sorry to bore you all by re-posting this. I posted this query a week or
so back. I got one very helpful reply from Bill Kinnersley ( thanks Bill ),
which explained very clearly what was happening. Since then I've tried some
unsuccessful experiments based on that explaination. Basically whenever I
try to tinker with my process's cli_CommandDir I get guru # 0000008.xxxxx .
I guess this means I aren't allowed to do that.
	So how does sys:cli do it??? I guess this query might be better
directed to comp.sys.amiga.tech but I don't have access. Thanks in advance
for any assistance.
	
>	I've got this really neat C program that uses Execute() to run shell
>scripts. It's nearly finished but I've come across a last minute hitch.
>	When the program is run from a cli, the processes created by Execute()
>inherit the search path from that cli. However, when run from the workbench,
>they get the default search path ( CurrentDirectory + C: ). This is very
>painful as I don't want to have to set a path for each process, possibly
>causing "Please insert volume xxx" requesters and annoying the user.
>	The program sys:cli seems to have some way of picking up the path that
>was in effect when loadwb was run ( I think ).
>	Can anyone tell me how to do this or suggest another solution to my
>problem?


						(phi%munnari.oz@uunet.uu.net)