home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CP/M
/
CPM_CDROM.iso
/
cpm
/
utils
/
sysutl
/
offrun34.lbr
/
OFFRUN.DQC
/
OFFRUN.DOC
Wrap
Text File
|
1986-04-27
|
4KB
|
92 lines
;;03-04-85
OFFRUN.DOC v3.4
Eric Gans
French Dep't UCLA
Los Angeles, CA 90024
This library contains the files OFFRUN.COM v3.4 (formerly
RUNOFF.COM -- I changed the name to avoid confusion with a well-
known printer program) and LUSER.COM v1.1 from EGUTIL.LBR.
*****
OFFRUN allows you to input just before turning off your computer
a series of commands to be run when it is next turned on. It
creates for this purpose (on A0:) a $$$.SUB file containing your
command line. Since it was originally written for the Kaypro-10,
it first runs a hard-disk safety program (renamed to OFF.COM)
after which, presumably, the computer is turned off. The next
time it is turned on (or reset), the command line will be run.
Once a command line has been entered it is stored in the file for
future use; the program asks you whether you want to keep the
current line or enter a new one.
I find this useful for two purposes. First, if there is a
set of startup files you want to run (loading patches to your
operating system like SMARTKEY, etc.), OFFRUN will run them
automatically. Second, if like me you use your computer for both
work and pleasure, and if the temptations of pleasure tend to get
in the way of your work, then before turning the computer off,
enter the commands you need to get to work and your conscience
will be tweaked when you next turn the switch. This has helped
me finish a few articles that might otherwise never have gotten
done.
The latest version (3.4) allows you to use OFFRUN from any
drive with different command lines. You must put OFFRUN.COM in
user 0 of the drive. This is to avoid confusion where (as on the
Kaypro-10) the operating system allows you to run a COM file in
user 0 from any user area; because OFFRUN stores its command line
in an internal buffer, the user area where the file is found must
be selected for the file to be opened and written to. The safety
program OFF.COM must be in A0.
Three formats are allowed: 1. OFFRUN cmd[;cmd1;cmd2;cmd3...]
This will run the series of commands separated by ';' (no spaces
please!) and save them on disk for future use.
2. OFFRUN =
This will display and run the command line stored in the file
without permitting changes. If the command buffer is empty you
will be asked for input. (v3.4)
3. OFFRUN entered alone allows you to inspect the current command
line (if there is none, the program will ask you to enter one).
You are then asked if you wish to run or change the set of
commands, or to abort the program.
Note: If you want to use this program but don't have/need a
safety program, you can either patch OFFRUN or, more simply,
create a dummy program thus: ddt (sid etc.) <cr> a100 <cr> jmp
100 <cr><cr> ^C save 1 off.com This one-line program will hang
your computer, thereby giving you time to turn it off. (My
previous suggestion of just entering a 'ret' forced you to turn
off the switch in the split second before the rest of the command
line began to run.)
*****
LUSER.COM (v1.1) can be used in conjunction with OFFRUN or in
.SUB files. SUBMIT and other related utilities (EX is an
exception, since it creates its command "file" in memory) create
a disk file called $$$.SUB to hold their command list during
processing. Unfortunately these files cannot be accessed once the
commands in the file leave the original user area. Since on hard
disks most application programs are located outside of user 0,
SUBMIT can't get you to them.
LUSER was written to solve this problem. It moves the
$$$.SUB file along with the commands from user area to user area.
Thus where the series: blurk;user 4;zap will not work in a SUB
file (or with OFFRUN) since when you get to user 4 the command
"zap" will be left behind, the series: blurk;luser 4;zap works
just fine; when the command to go to user 4 is issued the $$$.SUB
file is taken along and can be accessed.
To avoid BDOS R/O errors that may be encountered when A: is
a floppy drive, v1.1 resets the disk system in these cases.
Format: LUSER u where u = user number to go to