jkh@meepmeep.pcs.com (Jordan K. Hubbard) (07/16/90)
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 <cmd>" 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 <cmd>" 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: <glitch> Where <glitch> 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
peterk@cbmger.UUCP (Peter Kittel GERMANY) (07/18/90)
In article <JKH.90Jul16144447@meepmeep.pcs.com> jkh@meepmeep.pcs.com (Jordan K. Hubbard) writes: >I'll "RUN EXECUTE dlineart -s" in my >startup script! I have a brute force method that helps in most cases, but often needs to create at least one additional script file: NEWSHELL CON:... FROM <your_execute_file> So you must make up a script file to pass it to the FROM argument of newshell. Second effect that some people don't like (but doesn't bother me normally) is that you get an extra window by newshell. But this one will close when you end your new script file with an ENDCLI. -- Best regards, Dr. Peter Kittel // E-Mail to Commodore Frankfurt, Germany \X/ rutgers!cbmvax!cbmger!peterk
bleys@tronsbox.xei.com (Bill Cavanaugh) (07/18/90)
In article <JKH.90Jul16144447@meepmeep.pcs.com> OC jkh@meepmeep.pcs.com (Jordan K. Hubbard) writes: >I'll "RUN EXECUTE dlineart -s" in my startup script! Try this (it works with your current dos) run <nil: >nil: dlineart -s That >should< detatch the program from both stdin and stdout, and allow you to close the cli. BTW, if -s is the flag for dlineart, great, but if it's the flag you were using with execute, you don't need it. /******************************************************************** * All of the above copyright by the below. * * Bill Cavanaugh uunet!tronsbox!bleys * * "You can only be young once, but you can be immature forever." * * Larry Anderson * ********************************************************************/