home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Fish 1
/
GoldFishApril1994_CD1.img
/
d1xx
/
d161
/
nag
/
runback.doc
< prev
next >
Wrap
Text File
|
1988-10-02
|
4KB
|
101 lines
ReadMe for "RunBack"
RunBack is a program that allows you to start another program which is
independant of the CLI window. This is particularly useful if you want
to start a program in you Startup-Sequence and then load the WorkBench,
closing the initial CLI. Without RunBack, the original CLI window cannot
be closed until the programs Run from that CLI have terminated.
This program is being distributed as a service to owners of FastFonts,
as RunBack is particularly useful with the FunKeys hotkey program included
with FastFonts. This program, source and ReadMe are Copyright 1987,
Microsmiths Inc and may only be distributed together in their original
unmodified state. Bug reports will be appreciated.
FastFonts owners, please be sure to send in your registration cards! We
will be sending a notice of a *FREE* update for owners of FastFonts V1.0
that fixes some minor bugs and adds a few enhancements to the various
programs included with FastFonts. Notices will be sent early in April '87
to registered FastFonts owners.
Microsmiths, Inc, PO Box 561, Cambridge, MA 02140
(617) 354-1224 BIX: cheath Compuserve: 74216,2117
RunBack was inspired by the "C" program RunBackground written by *Rob Peck*
of Amiga. RunBack also allows you to specify the stack size for the
program being started. Also, RunBack is about 1/4 the size of the original
RunBackground as it is written in assembler.
The following description comes from the original runbackground.c:
***************************************************************************
--------------
runbackground.c
---------------
SUMMARY: A Workbench Disk can be used to autostart an application
through the use of the startup script and close the startup CLI.
Users have commented that it is not possible to start a process going
from the startup script and then cause the initial CLI to go away.
Here is the solution to that problem, named appropriately:
RUNBACKGROUND
which starts and runs a background task. This does indeed allow you to
create a startup script that will set up your workbench running any
programs you might wish, removing the initial CLI in the process.
Your s/startup-sequence can contain lines such as the following:
RUNBACKGROUND -3 clock
RUNBACKGROUND utilities/calculator
RUNBACKGROUND -5 utilities/notepad
where RUNBACKGROUND is the command and the second parameter is the filename
which may be preceded by a flag-variable that specifies an optional delay
time. The delay can be from 0 to 9, for the number of seconds that
the startup script should sleep while allowing the background task to
load and start. I've put that in to minimize thrashing of the disk as it
tries to load several projects at once.
LIMITATIONS:
The program that you run cannot require any input from an interactive
CLI that starts it. Additionally, you cannot specify any file
redirection in the command line since this program provides the
redirection for you already. If you need to use redirection for
your command, you can modify the source code where shown, thus
allowing the redirection to become one of the parameters passed
through to your program.
RUNBACKGROUND does pass your command line parameters to the program
you wish to start, but limits the total length of your command
string to 227 (255 minus the 28 characters for "RUN >NIL: <NIL: "
preceding your own file pathname and ">NIL: < NIL: " following it.)
**********************************************************************
The command line for RunBack is the same as RunBackground, with the
addition of a Stack parameter -Snnnn. This will allow you to adjust
the size of the stack for the program being started.
For example, the command:
1> RunBack -S2000 FunKeys
will start FunKeys with a stack size of 2000.
As with the original RunBackground, you must be careful not to try run
a non-executable file or AmigaDOS will cause a GURU. However, it is safe
to use RunBack if the command does not exist. Just be careful not to
accidentally RunBack a data file. Since you normally would use RunBack
in your Startup-Sequence, this shouldn't be a problem.
To start FunKeys in your Startup-Sequence, assuming you have copied FunKeys
into your C: directory, use:
1> RunBack -S2000 c:FunKeys [your FunKeys preferences]