CompuServe Messages

Ray, I also ran into that problem when I first started playing around with ARexx for CLI scripts. It seems that a new Process is spawned to process the script, and that process doesn't inherit any of the attributes from the spawning CLI. So there is no path set up, and the default current directory is the NULL Lock, which is an implicit DF0:. I found two ways around this problem — the first was a royal pain, and the second cost money. My first solution involved building the scripts so that I either hard-coded everything (including explicit pathing of commands), or used variables that I passed as parameters when invoking the scripts. This approach worked well, but I still wasn't crazy about it. My second solution was much more satisfactory. I sprung for the $50 and purchased WShell, Bill Hawes CLI shell package. Since it was written by the person that wrote ARexx, it is designed and implemented as the perfect complement/companion to ARexx. ARexx scripts are executed automatically, no need to use the "address command … " syntax to issue an AmigaDOS command, and the complete inheriting of your current environment (path, current directory, etc.) auto-magically. I think it's well worth the cost, as it really makes ARexx a much more powerful and useful tool. BTW, I am in no way connected with Bill Hawes – just a satisfied customer. Hope this helps…Bob