Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!unido!pcsbst!jkh From: jkh@meepmeep.pcs.com (Jordan K. Hubbard) Newsgroups: comp.sys.amiga Subject: Strange behaviour with run EXECUTE Message-ID: Date: 16 Jul 90 13:44:47 GMT Sender: news@pcsbst.pcs.com Organization: PCS Computer Systems, GmbH Lines: 33 I've got myself a version of Workbench 1.3 that's had ARP installed along with a few other goodies (I ran some disk block optimizer on it as well, which has speeded up my boot time a bit). I just added Matt's DMouse program (nice; I don't know how I ever used the mouse before! :-) to the startup sequence and would like to start the companion "dlineart" program from s/startup-sequence as well. I ran into the following problems: Since dlineart doesn't background itself the way DMouse does, I first tried to "run" it. This worked fine, though then the startup CLI wouldn't go away. Various things tried with no success. Then I read a "help!" letter in one of the Amiga magazines describing a very similar problem where the suggestion was to use "runback " to prevent the program from being somehow "bound" to the original CLI (causing it to wait). Fine, but it seems that I don't *have* a program called runback Hmmmm. Read german documentation with dictionary on knee and find that the new(?) form "RUN EXECUTE " is the way to do it. Fine! Great! I'll "RUN EXECUTE dlineart -s" in my startup script! No. Now I simply get the message (when the aformentioned command is run): [CLI 2] Unknown command: Where is an unlauted "O". Obviously something is hosed and dlineart is also not started. Any clues? Bug introduced by ARP (1.2) perhaps? Jordan -- PCS Computer Systeme GmbH, Munich, West Germany UUCP: pyramid!pcsbst!jkh jkh@meepmeep.pcs.com EUNET: unido!pcsbst!jkh ARPA: jkh@violet.berkeley.edu or hubbard@decwrl.dec.com