home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
osotcmdf.txt
< prev
next >
Wrap
Text File
|
1997-03-14
|
2KB
|
54 lines
OSOTCMDF - STARTING PROCESSES FROM AN OS/2 COMMAND FILE
01/30/96
=======================================================================
Starting Processes from an OS/2 Command File
OS/2 2.1 and OS/2 2.11
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
If you want to start a DOS or WIN-OS/2 session and not have an OS/2
window appear before the start of the session, you can create OS/2
command files to start other processes or perform other tasks.
RESOLUTION
An object can be set up to open minimized; then any program started
from the session also opens minimized. This happens regardless of any
flags that are used, because a process must have focus, be in the
foreground, and be the active window, to give focus to another session.
When a session is minimized it cannot have focus, so it cannot give
focus.
If the program to be started is a full-screen application, an OS/2 Full
Screen program object can be associated with the command file. Within
the command, then, use an At sign (@) in front of all commands to avoid
displaying what is happening. For example:
@START /FS "Bob's DOS Program" C:\OS2\MDOS\QBASIC.EXE
@EXIT
When the icon is selected, it opens in full-screen. Run the command,
and QBASIC is in front with a Window List entry stating "Bob's DOS
Program."
The same technique can be used for Windows programs.
Note: You do not have to state the program type with the START
command; the type of operating system the program requires
can be determined from the header of the EXE file.
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.