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

John Donaldson jadonaldson at charter.net
Sun Feb 20 11:46:21 EST 2005


Renamed s.t.a.r.t.u.p autoexec, still nothing.

John Donaldson


John Donaldson wrote:


> Wrote a scripted call s.t.a.r.t.u.p and in it I put

> path= /DD/CMDS /DD/PASCAL_CMDS

>

> Rebooted system. At command prompt I typed PATH=? and got nothing back.

> Anymore suggestions?? Seems the ONLY way to have this automatic is to

> do the PATH command

> at the command prompt and NOT from a script.

>

> John Donaldson

>

>

>

> Robert Gault wrote:

>

>> The primary problem seems to be that we are dealing with a hack to

>> shell rather than a change to the OS-9 system. We probably need a

>> change to one of the managers for something like path= to work with

>> all possible combinations of intermediate code modules.

>>

>> As for what Pascal created, if Ident indicates Test is ml code then I

>> don't understand what the difference is between Test and dEd regards

>> path=.

>>

>> John Donaldson wrote:

>>

>>> Robert,

>>> Here is what I have found. I booted the system. Startup ran,

>>> because it iniz /r0 and then formated it.

>>> After I got the command prompt, I did a path=? and got nothing.

>>> Path= /dd/cmds /dd/pascal_cmds IS

>>> in the startup file, just before the iniz /r0, so I know it had to

>>> be executed.

>>

>>

>>

>> It won't stick unless the last line in the startup file is

>> i=/1

>>

>>> At the command prompt I did

>>> a path= /dd/cmds /dd/pascal_cmds and when I type path=? I get

>>> /dd/cmds

>>> /dd/pascal_cmds

>>>

>>> So now the path command is working. I then move DED from /dd/cmds to

>>> /dd/pascal_cmds. I then

>>> deleted it from /dd/cmds so that it only resides in /dd/pascal_cmds.

>>> At the /DD command prompt I

>>> typed DED @/d1 and it executed corretly. I then exited DED and the

>>> at the same /DD command

>>> prompt typed test and got ERROR 216. TEST is a ML program that

>>> Pascal made and place in

>>> /dd/pascal_cmds.

>>>

>>> What we have is

>>> 1. Startup script did not set PATH for every shell.

>>> 2. If path is set, OS9 does search the path for the ML program that

>>> you typed in { DED }

>>> 3. Test which is a ML program created by Pascal is NOT executed,

>>> unless it is put into

>>> the /DD/CMDS directory.

>>>

>>> Now Pascal uses ASM to compile the program. Isn't ASM a Level I

>>> program?? Could this be the

>>> problem?? If RMA is used instead of ASM would that solve the problem??

>>>

>>> John Donaldson

>>>

>>>

>>>

>>> Robert Gault wrote:

>>>

>>>> John Donaldson wrote:

>>>>

>>>>> Robert,

>>>>> Even pure ML programs do not work on my system. Test is a ML

>>>>> program that Pascal made.

>>>>

>>>>

>>>>

>>>>

>>>>

>>>> Maybe this is critical. Have you tried this test with a program

>>>> created with an assembly package rather than Pascal? Heck, just

>>>> move one of the standard OS-9 commands to the test directory.

>>>> Clearly there is a difference between your system and mine with

>>>> respect to ml programs. We need to find what the cause of this is.

>>>>

>>>>> It sits in

>>>>> the Pascal_cmds directory. Path is set to Path= /dd/cmds

>>>>> /dd/pascal_cmds. I can execute any ML program

>>>>> that is in /dd/cmds, but when I try and excute the test ML program

>>>>> from /DD , I get ERROR 216 - Bad Path

>>>>> Name.Which means it searched /dd/cmds, but did not search

>>>>> /dd/pascal_cmds. Now if I do a chx

>>>>> /DD/pascal_cmds and execute the test ML program from /dd, it

>>>>> works. The only conculsion I can come up

>>>>> with is Path is NOT working.

>>>>>

>>>>> John Donaldson

>>>>

>>>>

>>>>

>>>>

>>>>

>>>>

>>>

>>>

>>>

>>

>

>

>






More information about the Coco mailing list