CompuServe Messages

Don, I had the same problem. The answer is to make sure that your shell-startup script has a Path command pointing to all of your command pathways so that the shell can find the commands that are being asked for. ie. My shell-startup script is as follows: Path >NIL: RAM: C: SYS:RexxC SYS:XtraC AMITCP: AMITCP:bin SYS:Utilities….. ………..SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools ADD ALIAS del delete ALIAS ns newshell ALIAS es endshell ALIAS List nl -gb -F "%25n %7s %27d %8p %N" -df "%8M-%2d-%2y @ %02h:%02n:%02s" ALIAS Cp Copy [] Clone PROMPT "%S> " You will notice that the Path statement directs the shell to search first in RAM: then C: etc. to find the commands that it needs. I have a RexxC directory for my ARexx commands; this is where I have WaitForPort. Mostof the other directories are a direct copy from my startup-sequence file Path statement. Hope this helps.:) Pete / / Flying the A3000 on AutoPilot 1.80 \/\/ from Durham,Ontario.