Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!cbmvax!andy
From: andy@cbmvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: run & path questions
Message-ID: <2454@cbmvax.UUCP>
Date: Fri, 2-Oct-87 14:51:54 EDT
Article-I.D.: cbmvax.2454
Posted: Fri Oct  2 14:51:54 1987
Date-Received: Sat, 3-Oct-87 11:45:31 EDT
References: <1775@cadovax.UUCP>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 35
Keywords: run path

In article <1775@cadovax.UUCP> kaz@cadovax.UUCP (Kerry Zimmerman) writes:
>A couple of questions:
>
>1.  Since the code   
>       error = Execute( "RUN  whatever ...", 0L, 0L);
>    always returns a success, how can your program tell if the
>    program you wanted to run was found or not? 

Its a kluge, I know, but under 1.2 you can get some indication
from IoErr();

>
>2.  How can you find out what the current PATH is set to within
>    a program?

Paths are stored as a BPTR to a BCPL list stored off of the 
CommandDir entry of the CommandLineInterface

>3.  It seems that both Execute and Run will search through the current
>    PATH.  Does LoadSeg also do this search, or do you have to specify
>    the path in the LoadSeg call?

LoadSeg doeesn't do this search.  You'll have to do it yourself.  And,
as a nice gesture for the user, I suggest that you turn off the requesters
and search quietly. (set Process->WindowPtr to -1)

-- 
andy finkel		{ihnp4|seismo|allegra}!cbmvax!andy 
Commodore-Amiga, Inc.

"Interfere?  Of course we'll interfere.  Always do what you're best at,
 I always say."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.