[Coco] Re: Path command wasRe: OS-9 LVL II

[Kevin Diggs]

John,

	I don't have shell plus so probably can't help. What is test? Could it 
be case sensitive (PASCAL_CMDS vs Pascal_cmds)?

John Donaldson wrote:
> Kevin,
>   The PATH command does not seem to work for me. I have it in my Startup as
> PATH= /DD/CMDS  /DD/PASCAL_CMDS
> 
> I even typed the same thing from the command prompt and I can do a 
> PATH=?  and it will print
> /DD/CMDS
> /DD/PASCAL_CMDS
> 
> BUT when I try and execute a executable file in Pascal_cmds called test, 
> I get ERROR 216 - Path Not
> Found. Only if I move it to the /DD/CMDS  or do a CHX /dd/PASCAL_CMDS 
> will it execute.
> 
> John Donaldson

I think you mean exec (or F$Fork for OS9) not open. Some of the exec 
LIBRARY routines do know how to search the PATH ENV for a command. I 
don't think the exec syscall does.

>>
>> But if a program tries to open a file by name, it is going thru the 
>> OS, but  not the Shell, so PATH expansion might not be available.  The 
>> F$Open OS  call is restricted to what Microware built into OS9, and 
>> does not have access to  the powers of ShellPlus.  Even the Linux 
>> C-Library open() command has  limitations in this regard.
>>