home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!jamie
- From: jamie@cdevil.unx.sas.com (James Cooper)
- Subject: Re: system call to get AmigaDos PATH string(s) ?
- Originator: jamie@cdevil.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <C181M3.GvF@unx.sas.com>
- Date: Thu, 21 Jan 1993 20:44:27 GMT
- References: <1993Jan17.230704.27737@philips.oz.au> <paulk.3cz7@terapin.com> <51604@shamash.cdc.com>
- Nntp-Posting-Host: cdevil.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 41
-
-
- In article <51604@shamash.cdc.com>, app@shamash.cdc.com (CDII Advanced Pkg/Processes) writes:
- >In article <paulk.3cz7@terapin.com> paulk@terapin.com (Paul Kienitz) writes:
- >>> system call to get AmigaDos PATH string(s) ?
- >>
- >>> One klugey way is :-
- >>>
- >>> Execute ("PATH >T:file", 0L,0L);
- >>>
- >>> then parse T:file.
- >>>
- >>> But there's got to be a neater way.
- >
- >Speaking of the Execute command, why does something like this NOT work?:
- >
- > Execute ("Path Sys:Utilities Add", 0,0);
- >
- >Does the path info get assigned somewhere other than the current CLI?
-
- Yes. Execute is creating a background process, the Path is added to that proc
- only, then it goes away == no change to the current CLI.
-
- >Is
- >there a way to set the path for all CLI's with AmigaDos1.3?
-
- No, not without either editing your Startup-Sequence, or mucking around in
- private areas of the system - not recommended.
-
- >I'll need to check again to be sure, but I don't think Stack works with the
- >Execute command either. What gives?
-
- Same thing - the stack is only set in the background process, not in the current
- one.
-
- --
- ---------------
- Jim Cooper
- (jamie@unx.sas.com) bix: jcooper
-
- Any opinions expressed herein are mine (Mine, all mine! Ha, ha, ha!),
- and not necessarily those of my employer.
-