page%ulowell.csnet@CSNET-RELAY.ARPA (11/20/85)
From: Bob Page <page@ulowell> I've been doing a lot of experimenting with AmigaDOS lately, especially the process handling capabilities. One 'feature' that I found was this: The Execute(cmdstring, infile_handle, outfile_handle) command actually calls C:RUN (the command) to do its work! True! If you don't have that file, or renamed it something else (like I did), the Execute will *FAIL*! It will always return 0 (False), no matter what you give it. Once I fixed that (put RUN back to what it was supposed to be called), all went well. There is another strangeness, however. I am running my commands from a custom CLI, not in the CLI window (but on the WB screen). When I type a command, like DIR, output goes to my window, like I want. But when I type something like RUN DIR, I get '[CLI 2]' in my window, and the output of the DIR command in the CLI window! My feeling is that the cause is do to some CLI process structure magic, where things not run from the CLI (like the DIR command run from RUN run from my ZLI (that's what I call my CLI)) want to talk to the CLI screen. I can get the DIR command (w/o RUN) to go to either window, but with RUN, it will only go to the CLI screen. Any ideas on what I have to tweak to stop this? Note that a NEWCLI will perform as it should (not the way ZLI does). Sorry to ramble. ZLI is coming along nicely, except for a few 'misfeatures'. Some of the documentation in the AmigaDOS (Developer's? Tech Ref?) manual is wrong about RAW: keycodes: A shifted cursor key does NOT transmit a final tilde, as stated, and SHIFT/HELP key does not transmit anything... ..Bob UUCP: ...!decvax!wang!ulowell!page ARPA: page%ulowell.csnet@csnet-relay