#Startup Sequences
4 messages in this thread
I have been trying to alter my startup sequence to allow a shell window to
stay open over the normal workbench. I have the co-ordinates to cover the
screen, but were ever I place the command in the sequence, it either
ignores the command or starts a second process to allow it. Is there a way
of closing the startup window, then opening new shell window ? I am using
version 1.3 of AmigaDOS.
Russell,
The only way to accomplish what you are attempting _is_ to start up a
second process with the window specs. The trick is to get the original
process to go away when it is finished. The key thing to remember is that
all programs run by the original program must either finish, or run in the
following manner:
run <nil: >nil: your_program
If you do this for all programs "run" in your original startup-sequence,
then the "endcli" command at the end of the script should allow that window
to close.
Hope this helps….
– BobR
Will that same trick allow me to exit WB (ie from the quit menu option
on the WB menu? I always get a screen flash and message "cant' close
WB; 2 programs launched from WB. I think the programs are pc/pcdisk
and condev.
I'd occasionally like to close WB to get more chip ram for some
programs. I haven't tried the run >nil <nil options because of all
the warnings not to alter the startup-sequence, but if it'll do the
trick I'm willing to try it.
I suspect that the programs launched from WB are those whose icons
are in your WBStartup drawer. The only way to avoid that situation
is to not place programs in that drawer, but to start them from the
user-startup script, using "run <nil: >nil: …". However, some
programs are really designed to only be started from WorkBench and
may not function in this manner.