![]() |
![]() |
Articles / TULARC / PC info / Amiga / Amiga Networking / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
48 Adding to the PATH doesn't seem to work from the Shell, why? |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the Amiga Networking FAQ, by Richard Norman with numerous contributions by others.
Each shell has it's own copy of the workbench PATH structure. This allows each
shell to be customized, but does lead to confusion because adding to the PATH in
one shell does not affect the other shells. To change the PATH for the workbench
and thus all new Shells you must use the NEWPATH option of the LOADWB command. For
example, to add work:newdir to the PATH system wide you'd type:
>PATH work:newdir add
>LOADWB NEWPATH
Now work:newdir will be added to the search path system wide.
 
Continue to:
amiga, pc, hardware, sotware, networking
![]() |
|
|