home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
sysutils
/
run
/
run160.doc
< prev
Wrap
Text File
|
1993-12-23
|
9KB
|
220 lines
README FILE FOR RUN-OS/2 (v1.60)
--------------------------------
This package consists of;
1. RUN.EXE (the main RUN-OS2 executable)
2. RUN160.DOC (documentation - this file);
Please read the DISCLAIMER at the end of this file BEFORE attempting
to use either of these programs.
"RUN" is a utility that allows OS/2 users to run OS/2 programs from a DOS
session. The executable (RUN.EXE) can be run from either a DOS session
or from an OS/2 session. Certain features are not available if it is
run from an OS/2 session, and, indeed, there is nothing to be gained by
so doing, since RUN-OS/2 is only designed to overcome the restriction of
not being able to run OS/2 executables from a DOS session.
You use this program by supplying the name of the OS/2 program that you want
to run as the first parameter, and after that you can specify whatever
parameters you wish to pass to the OS/2 program. RUN-OS/2 will search the
(DOS) path for the OS/2 program, and if it is not found in the path, it
will optionally proceed to search the entire drive (if you supply
the /SCAN parameter - if the program is on the drive, RUN-OS/2 will
find it and try to run it).
Normally, you should supply the full name of the OS/2 program,
e.g., "RUN PMCAMERA.EXE". If the extension .EXE is not supplied
e.g., "RUN PMCAMERA", then the program will search for the various
permutations of valid executable file extensions, in the following order;
[1] EXE
[2] CMD
[3] COM
[4] BAT
The first one that matches will be executed.
The fact that RUN-OS/2 looks for .COM and .BAT extensions indicates that it
will also run DOS programs. However, it was written for the purpose of
running OS/2 programs only. On my system, it runs DOS programs alright, but
you might need to press ENTER before the DOS prompt returns to you. All I
can say however, is that you should only use it to run OS/2 programs. I
cannot be responsible for anything that happens if this advice is not
adhered to.
This program works fine on my system, but your mileage may vary. There is
really no way in which I can improve it further, so if it doesn't work fine
on your system, then sorry ... you will just have to delete it.
Examples of usage:
1. RUN OS2EMACS.EXE TODAY.TXT
this will run os2emacs.exe, and pass "today.txt" as a parameter to it.
2. RUN CKERMIT
this will try to locate [a] CKERMIT.EXE, or [b] CKERMIT.CMD , or
[c] CKERMIT.COM [d] CKERMIT.BAT, in that order. When any of them
is found, it will be run. If no match is found, then there will be an
error message.
3. RUN CKERMIT /SCAN
try to locate CKERMIT. If it is not found in the DOS path, search
through the whole of the CURRENT drive for it. Note that the /SCAN
option is being phased out.
Note that you need to copy RUN.EXE into a directory which is in the "path"
statement in your CONFIG.SYS and AUTOEXEC.BAT files.
COMMAND LINE PARAMETERS
-----------------------
The syntax forRUN is
RUN <progname> [prog parameters] [exec switches]
The Exec Switches are:
/D=<dir> = run PROGNAME from the directory <dir>
/P+ = PAUSE after running PROGNAME
/PM = PROGNAME is a Presentation Manager program
/FG = run PROGNAME in the FOREGROUND
/BG = run PROGNAME in the BACKGROUND
/FS = run PROGNAME in a FULL SCREEN session
/WN = run PROGNAME in a WINDOWED session
/SCAN = scan the entire drive for PROGNAME
RESTRICTIONS:
/SCAN cannot be used with any of the other switches
/FS and /WN cannot be used at the same time
/FS and /PM cannot be used at the same time
/WN and /PM cannot be used at the same time
/FG and /BG cannot be used at the same time
Note that the EXEC SWITCHES should be supplied after you have supplied
all the parameters you wish to pass to your OS/2 program.
Of what use are the command line switches?
1. To enable a user to specify the directory from which an OS/2
program should be run (this is sometimes needed because RUN-OS2
usually opens the OS/2 sessions in the root directory of the OS/2
drive).
To use this function of RUN-OS/2, you need to supply the parameter
/D=<directory name>
e.g. RUN CKERMIT.EXE /D=E:\OS2KERM
What happens here is that RUN-OS2 will then change to the
directory E:\OS2KERM, and then call CKERMIT.EXE from there.
2. To enable a user to force the OS/2 session to pause for a key press
before it closes. This is important when you want to see the output
from that session.
To use this function of RUN-OS/2, you need to supply the parameter
/P+
e.g. RUN CKERMIT.EXE /D=E:\OS2KERM /P+
Here, after exiting from CKERMIT.EXE, you will be prompted for a
key press before the OS/2 session closes.
3. To enable a user to force the OS/2 session to run in either full
screen mode or in a window (if your application is one that can
be run in a window).
For this purpose you need to supply either the parameter /FS
(for full screen mode) or /WN (for a windowed session). If neither
of these parameters is supplied, the program will probably be run
in a window, but that will depend on many things.
e.g. RUN CKERMIT.EXE /FS
Here, CKERMIT will be run in full screen mode
e.g. RUN CKERMIT.EXE /WN
Here, CKERMIT will be run in a window
4. To enable the user to force the OS/2 session to run in the
foreground or in the background.
To use this facility you need to supply the parameter /FG
(to run in the foreground) or /BG (to run in the background).
If neither of these parameters is supplied, the program will
probably be run in the foreground, but that will depend on
many things.
e.g. RUN CKERMIT.EXE /FG
Here, CKERMIT will be run in the foreground
e.g. RUN CKERMIT.EXE /BG
Here, CKERMIT will be run in the background
5. To indicate that the OS/2 program to be run is a Presentation
Manager program. For this, you need to use the /PM option. When
this is done, RUN-OS/2 disables some of the other options (e.g.,
/FS and /WN)
6. To scan the entire drive for the OS/2 program to be executed.
Sometimes, a program is not in your "path", and therefore cannot
be found by the command processor. You will then get a message
that the command is not recognised. If you are sure that the
program is on that drive, you can supply the /SCAN switch, and
RUN-OS/2 will find it, if indeed it is there.
There is a restriction with the /SCAN switch - it CANNOT be used
in conjunction with any of the other switches supported by
RUN-OS/2. If you try to use it with any other switch, it is
guaranteed NOT to work properly. Please note this point.
Note that the parameters can be supplied in any order, and any number
of them may be supplied together (as long as it makes sense to do so -
for example it does not make sense to supply /BG and /FG at the same
time).
4OS2 batch files
----------------
It _may_ be possible to run 4OS2 .BTM files through RUN-OS/2. I have not
tried this, since I do not have 4OS2. However, RUN.EXE often calls your
OS/2 session's command interpreter (your 'COMSPEC'). Thus if your
'COMSPEC' is 4OS2.EXE then it may be possible to run its .BTM files.
If anybody can confirm this one way or the other, please do let me know.
--------
LICENSE
--------
The program is released as freeware. You may do with it as you please,
provided that you do not change the program in any way, and that if it
is to be distributed, this file is distributed with it.
DISCLAIMER
----------
THE PROGRAM RUN.EXE IS SUPPLIED "AS IS", AND WITHOUT ANY WARRANTIES
WHATSOEVER. I ACCEPT NO RESPONSIBILITY FOR ANY LOSS OR DAMAGE, WHETHER
PHYSICAL, FINANCIAL, EMOTIONAL, MENTAL, MARITAL, OR OTHERWISE, THAT MAY
RESULT FROM THE USE OR THE PURPORTED USE OF RUN-OS/2.
IF THESE TERMS ARE NOT ACCEPTABLE TO YOU, THEN YOU HAVE NO LICENSE TO
THIS PROGRAM, AND YOU SHOULD DELETE IT FROM YOUR DISKS IMMEDIATELY,
AND PERMANENTLY.
{----------------------------------------------------------}
(c) December 1993
Dr. A. Olowofoyeku
Keele University,
England.
E-mail: laa12@seq1.keele.ac.uk
{---------------------------------------------------------}