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

[John Donaldson]

Robert,
  Like I said ealier, I can move the Test program to /DD/CMDS or do a 
CHX /DD/PASCAL_CMDS, then
the program executes and prints numbers on the screen. I tried a test, I 
moved RunB from /DD/CMDS to
/DD/PASCAL_CMDS. I then did a CHD /dd/PASCAL_CMDS. A dir showed Runb and 
QP, which is
a packed basic09 program. I typed QP, and got an error 216. I then did a 
CHX /DD/PASCAL_CMDS and
the typed QP and it executed. I then did a PATH=? and got
/DD/CMDS
/DD/PASCAL_CMDS

  This proves that only ONE directory can be the CMDS directory. You can 
not have multipy CMDS
directory.

John Donaldson


Robert Gault wrote:

> And it works correctly if you call it from Shell as a command? If not 
> or if Test needs something to be in memory and can't find it, you 
> could see a 216 error.
>
> John Donaldson wrote:
>
>> It is a program that I wrote in Pascal and compiled to executable. 
>> When I do and IDENT it says
>> Size            #428
>> CRC           GOOD
>> Parity           $85
>> Exec Off       #25
>> Data Size       #1058
>> Edition           #1
>> ty/la   at/rv     #11  $81
>> prog Mod, 6809 obj, Ew-en, r/o
>>
>> All it does is calculate numbers and print them to the screen.
>>
>> John Donaldson
>>
>>
>> Robert Gault wrote:
>>
>>> Exactly what is the "test" command or script you are trying to run?
>>>
>>> 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
>>>>
>>>>
>>>>
>>>> KnudsenMJ at aol.com wrote:
>>>>
>>>>> In a message dated 2/19/05 3:11:25 PM Eastern Standard Time,  
>>>>> kevdig at hypersurf.com writes:
>>>>>
>>>>>  
>>>>>
>>>>>>   In Unix (& Linux), path is NOT a command. It is a  feature of 
>>>>>> the command interpreter (i.e. shell) and some of the exec  
>>>>>> LIBRARY routines. It is all built on the ENV variables that the 
>>>>>> Unix  process model includes. Does OS9 have ENV?
>>>>>>   
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> OS9 6809 stock shell does not have ENV or anything like PATH, but 
>>>>> the  rather popular ShellPlus replacement shell does support ENV 
>>>>> variables.  As  does the Shell in OS9/68K.
>>>>>
>>>>>  
>>>>>
>>>>>> A shell is not the only place to launch a shell from.
>>>>>>   
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> This reminds me, that even under ShellPlus, if you type an 
>>>>> executable  program's name, ShellPlus knows how to hunt down the 
>>>>> file via the dirs given in  the PATH variable.
>>>>>
>>>>> 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.
>>>>>
>>>>> So if a Pascal or Basic09 program tries to execute another file, 
>>>>> which is  not in /dd/cmds, the PATH won't help.  PATH only works 
>>>>> from the shell, as  in command line or script.  It *should* work 
>>>>> right from a shell("command  string") or system("string") in 
>>>>> Basic09 or C, since these invoke the  shell.  --Mike K.
>>>>>
>>>>>
>>>>>  
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>