home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
warpst04.zip
/
tricks.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-09-24
|
400KB
|
4,395 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
Stupid OS/2 Tricks
compiled by M. Woo, Champaign-Urbana OS/2 Users Group, release #6, Sept 1995
(Double click on a bitmap to start)
Information about this document:
Γûá Types of "tricks" included
Γûá How to use the included REXX scripts
Γûá How to submit tips and tricks
Γûá Revisions
Γûá Revision schedule
Γûá How this document was created
Γûá Disclaimer
Copyright 1993-95 M. Woo.
All Rights Reserved. This work, or parts thereof, may not be reproduced or
redistributed in any form without permission, with the exception that "Stupid
OS/2 Tricks" can be freely distributed in electronic form for non-commercial
use, as long as it remains unaltered.
ΓòÉΓòÉΓòÉ 1.1. Types of "tricks" included ΓòÉΓòÉΓòÉ
This file contains various tips and tricks for OS/2 which have been gathered
over time from various sources. Creation of this text was inspired by the
"Clever Tricks" section of Tim Sipples' excellent Frequently Asked Questions
list, a must read for all OS/2 owners.
The type of tips and tricks included in this text are those which cover
features of OS/2 that people often ask about, short REXX scripts which do
interesting things, as well as other items which hopefully don't overlap
information already contained in Tim Sipples' FAQ (well, not by TOO much,
anyway).
The tricks contained in this text do not make references to any specific
product names, other than those components included in OS/2 itself. However,
it may occasionally have been necessary to mention generic classes of utilities
which are not included as part of OS/2.
A Japanese language version of Stupid OS/2 Tricks should now be available.
Contact A. Kikuchi at kiku@ymtl01.yamato.ibm.co.jp for details.
Related subject(s):
Γûá How to submit tips and tricks
ΓòÉΓòÉΓòÉ 1.2. How to use the included REXX scripts ΓòÉΓòÉΓòÉ
as per a suggestion from Dawn Perchik
In order to use the included REXX scripts, you must have REXX installed on your
OS/2 system. If you did not install REXX during your OS/2 installation, it can
be installed using the Selective Install object in your System Setup folder.
Each REXX script is linked to the first instance of its name via a hypertext
link. If you double-click with mouse button 1 on the hypertext link, a window
will pop up containing the REXX script.
To write the REXX script to disk, make sure the window containing the REXX
script is the active window. Pull the Services menu down from the menu bar,
then choose Copy to File. This will create a file called TEXT.TMP on your
disk.
Open TEXT.TMP into a text editor (such as the System Editor) for editing. In
order for OS/2 to recognize the script as a REXX script, rather than a regular
OS/2 batch file, the symbols "/*" (without quotes) must reside on the topmost
line, in the positions to the farthest left. In order to accomplish this, you
will have to delete the blank lines at the top of the file, and delete any
spaces that occur before the first "/*" symbols.
When you are finished editing TEXT.TMP, save it as a filename which ends with
the extension .CMD (such as SETPTR.CMD), so that OS/2 can recognize the file as
a REXX script.
Voila! You should now have a working REXX script that can be run simply by
typing its name at an OS/2 command line.
ΓòÉΓòÉΓòÉ 1.3. How to submit tips and tricks ΓòÉΓòÉΓòÉ
If you know of any neat OS/2 tips or tricks that you're dying to share, please
send them along. They would be greatly appreciated!
If your tip or trick is used, your name will be listed along with it for all to
see!
Neat OS/2 tricks can be sent to:
Internet, m-woo@uiuc.edu
Fidonet, Sysop @ 1:233/4.0
Please also send any corrections to either of the addresses above.
ΓòÉΓòÉΓòÉ 1.4. Revisions ΓòÉΓòÉΓòÉ
INF revision marks
Revisions/additions to this INF file will be displayed in the following text
color (this is a revision).
Related subject(s):
Γûá Revision schedule
ΓòÉΓòÉΓòÉ 1.5. Revision schedule ΓòÉΓòÉΓòÉ
This text will be updated when the number of new tips and tricks gathered
warrants a new version.
Revision History:
Γûá Release #1 - Nov 1993; initial release
Γûá Release #2 - Dec 1993
Γûá Release #3 - Jan 1994
Γûá Release #4 - Apr 1994
Γûá Release #5 - Nov 1994
Γûá Release #6 - Sept 1995
Related subject(s):
Γûá Revision marking
ΓòÉΓòÉΓòÉ 1.5.1. Release #2 ΓòÉΓòÉΓòÉ
Release #2 - Dec 1993
Changed:
Using Elvis v1.8c beta instead of v1.6
Corrected info in "Getting more out of your command line"
Corrected typos in SETMOUSE.CMD (this is important!!!)
Added note to "Adding an 'open folder' entry to the desktop's popup menu"
Improved BITMAP.CMD
Added:
Getting Epson ActionLaser 1500 to work
Using keyboard shortcuts in PM
Navigating in notebooks without a mouse
Shutting down from a REXX script automatically
Curing "jumpy mouse"
Retrieving a "changed" icon
Pasting between Windows applications
Associating data files with programs
Getting memory back from unused caches
Changing the default view of a folder
Dealing with OS/2 !! SYS messages on boot
Using multiple arguments at the OS/2 command line
Using EPM as a customized command shell
Setting the startup directory for command line objects
Restoring last desktop backup
Creating new printer objects
Viewing *.inf files more conveniently
Formatting a diskette with the detach command
Creating your own templates
Using less memory for DOS images
Replacing your Shredder if deleted
ΓòÉΓòÉΓòÉ 1.5.2. Release #3 ΓòÉΓòÉΓòÉ
Release #3 - Jan 1994
Changed:
Added comment to "Prevent restarting automatically"
Added note to "Speeding up some IDE drives"
Corrected code and added comment to SETFONT.CMD.
Replaced SETMOUSE.CMD with an improved version, SETPTR.CMD
Added:
Starting seamless Windows from the command line
Resizing a command line window permanently
Making the system "sleep"
Substituting REPLACE for the COPY command
Deleting "undeletable" objects
Speeding up opening folders
Managing your icons
Enlarging the mouse cursor
Manipulating objects through the Window List
Booting OS/2 in full-screen mode
Completing shutdown
"Touching" a file's date and time
Adjusting your swap file
Adding command sessions to the desktop's popup menu
Using SVGA.EXE under real DOS
Selecting listbox entries without a mouse
Making "no-shows" re-appear
Opening multiple command line sessions from the desktop menu
Creating a command line calculator
Loading a DOS device driver into high memory
Starting a DOS session with maximum free memory
Fixing "locked" INI files
Using START to avoid the dreaded "clock"
Coloring OS/2 command line sessions
ΓòÉΓòÉΓòÉ 1.5.3. Release #4 ΓòÉΓòÉΓòÉ
Release #4 - Apr 1994
Changed:
Added code to BIGDOS.CMD to make DOS session open in foreground.
Removed ICONRES.CMD because it was copyrighted.
Added 2.11 note to "Maximizing windows when opening"
Added 2.11 note to "Retrieving a 'changed' icon"
Added note to "Rebooting from the command line"
Added 2.11 note to "Backing up the *.ini files"
Added info to "Curing 'jumpy mouse'"
Added:
Opening the parent folder
Playing audio CDs via REXX
Copying fullscreen text to the Clipboard
Displaying custom DOS settings at the command line
Using Windows File Manager on your OS/2 desktop
Fixing seamless Windows on some 2.11 CSD systems
Jumping between windowed sessions
Playing media files from the command line
Editing object names on the desktop
How to use the included REXX scripts
Determining if you have a buffered UART in your computer
Moving a template object without creating a copy
Changing the long name (icon text) of a file or folder without changing
the real name
Starting an OS/2 command line from a folder's directory
Adding INF files to the desktop popup menu
ΓòÉΓòÉΓòÉ 1.5.4. Release #5 ΓòÉΓòÉΓòÉ
Release #5 - Nov 1994
Changed:
Unfortunately, it became necessary to expand on the copyright statement
Added a separate section for OS/2 Warp-specific tips
Added warning to "Changing the standard mouse pointer"
New version of BITMAP.CMD
Added note to indicate that author's address is now more or less permanent
Now using the IPF compiler from the IBM OS/2 Developer's Toolkit v2.1
Added:
Opening windowed command line in the background
Recreating a "lost" template
Viewing the Nowhere subdirectory
Using PMREXX as a scrolling command window
Backing up INI files in the background
Tearing off Launchpad drawer
Opening the Settings notebook
Changing printing from polling to interrupt-driven
Closing the parent folder when opening an object
Recovering a deleted Launchpad
Keeping the system running, even through traps
Obtaining information about your hardware
Editing animated folder icons
Bringing the Launchpad to the top
Setting the swap file
Setting video modes
Speeding up opening folders II
Closing parent folders automatically
Setting default folder appearance
Creating OS/2 Warp boot diskettes
Caching your cdrom drive
Resetting Boot Manager to have no default partition
Switching temporarily to a different directory
Associating icon with executable
Booting DOS from a C: partition within OS/2
Resetting the boot record
Canceling print jobs from the command line
Adding more LPT ports in Win-OS/2
Customizing the Launchpad
ΓòÉΓòÉΓòÉ 1.5.5. Release #6 ΓòÉΓòÉΓòÉ
Release #6 - Sept 1995
Changed:
Corrected manipulating objects through the Window List
Added additional material to "Adding a trash can"
Added:
Displaying the Recovery Screen
Displaying Device Drivers on Boot
Dual Booting Without Confirmation
Adding Temporary LIBPATH Entries
Showing the Buildlevel of EXE and DLL Files
Using the Pickup Functions
Bringing the Launchpad to the Top Using the Keyboard
Opening Parent Folder While Closing Child Folder
Putting Template Buttons on the Launchpad
Preventing Save of Desktop Settings Between Shutdowns
Viewing HLP Files Without Opening the Application
Command Line Options for the WebExplorer
Pulling Down Menus in WebExplorer Presentation Mode
Using Different INI Files with the WebExplorer
Adding Fastkeys to the WebExplorer Quick List
Setting the Size of the WebExplorer
Shortening Pulldown Menus
Removing the Drive B Icon from the Drives Object
Creating a Program Object from Executables
Resetting Drive Open Behavior
Scrolling in the Background
ΓòÉΓòÉΓòÉ 1.6. How this document was created ΓòÉΓòÉΓòÉ
This document was written using the OS/2 port of Elvis v1.8c beta. Screen
captures were done using PMCamera/2 v2.10, an IBM EWS package. The resulting
tagged document was compiled using the IPF compiler from the IBM OS/2
Developer's Toolkit v2.1.
ΓòÉΓòÉΓòÉ 1.7. Disclaimer ΓòÉΓòÉΓòÉ
I don't claim to be an expert on OS/2, so I can't guarantee that all the tips
and tricks presented in this document will work with all configurations of
OS/2. Thus, the following disclaimer:
The reader/user assumes all responsibility, liability and risk for any damages,
incidental or consequential, resulting from the use of the information provided
in this document. No warranty is expressed or implied, and this document is
only guaranteed to use space on your disk.
ΓòÉΓòÉΓòÉ 2. System ΓòÉΓòÉΓòÉ
This section covers tips and tricks which affect the system in general.
Topics in this section:
Γûá Keeping applications from restarting at boot
Γûá Shutting down without a mouse
Γûá Rebooting from the command line
Γûá Finding settings for original objects
Γûá Controlling order of execution in Startup folder
Γûá Backing up the *.ini files
Γûá Removing device drivers for better performance
Γûá Speeding up some IDE drives
Γûá Disabling use of the floppy drives
Γûá Getting Epson ActionLaser 1500 to work
Γûá Getting memory back from unused caches
Γûá Dealing with OS/2 !! SYS messages on boot
Γûá Restoring last desktop backup
Γûá Viewing *.inf files more conveniently
Γûá Using less memory for DOS images
Γûá Booting OS/2 in full-screen mode
Γûá Completing shutdown
Γûá Adjusting your swap file
Γûá Using SVGA.EXE under real DOS
Γûá Loading a DOS device driver into high memory
Γûá Fixing "locked" INI files
Γûá Playing audio CDs via REXX
Γûá Playing media files from the command line
Γûá Determining if you have a buffered UART in your computer
Γûá Pooling multiple printers
Γûá Viewing the Nowhere subdirectory
Γûá Backing up INI files in the background
Γûá Caching your cdrom drive
Γûá Resetting Boot Manager to have no default partition
Γûá Booting DOS from a C: partition within OS/2
Γûá Resetting the boot record
ΓòÉΓòÉΓòÉ 2.1. Keeping applications from restarting at boot ΓòÉΓòÉΓòÉ
When OS/2 is started, it automatically opens applications which were open
during the last OS/2 session. To keep applications from restarting on boot,
you can use either the manual or automatic method.
Related subject(s):
Γûá Prevent restarting manually
Γûá Prevent restarting automatically
Γûá Rebooting from the command line
ΓòÉΓòÉΓòÉ 2.1.1. Prevent restarting manually ΓòÉΓòÉΓòÉ
To prevent applications from restarting during boot, hold down the Ctrl, left
Shift, and F1 keys at the same time, beginning when the mouse pointer appears
until the icons begin appearing on the desktop. If you find that disk activity
stops, you may have to release the keys and then quickly hold them down again.
Related subject(s):
Γûá Prevent restarting automatically
ΓòÉΓòÉΓòÉ 2.1.2. Prevent restarting automatically ΓòÉΓòÉΓòÉ
Placing the line
SET RESTARTOBJECTS=STARTUPFOLDERSONLY,REBOOTONLY
into your CONFIG.SYS file will prevent any applications which had been open in
the last session from opening, but will allow programs in the Startup folder to
open.
(this line may be order-dependent on some systems)
Related subject(s):
Γûá Prevent restarting manually
ΓòÉΓòÉΓòÉ 2.2. Shutting down without a mouse ΓòÉΓòÉΓòÉ
To shut OS/2 down without a mouse, press Ctrl-Esc to bring up the Window List,
choose the Desktop, press the Spacebar to deselect any icons, press Shift-F10
to pop up the Desktop's menu, choose Shutdown.
ΓòÉΓòÉΓòÉ 2.3. Rebooting from the command line ΓòÉΓòÉΓòÉ
To reboot OS/2 down from the command line, type
SETBOOT /B
Note: the above only works with Boot Manager installed.
or
SETBOOT /IBD:<drive>
where <drive> is the letter of the drive or partition to which you wish to boot
Related subject(s):
Γûá Keeping applications from restarting at boot
Γûá SHUTDOWN.CMD
ΓòÉΓòÉΓòÉ 2.4. Finding settings for original objects ΓòÉΓòÉΓòÉ
The settings for all of the objects which were created upon installation of
your OS/2 system are contained in the INI.RC file, located in the \OS2
subdirectory. Those handy with REXX and the external REXXutils can use the
information contained in the INI.RC file to rebuild the original OS/2 objects.
Related subject(s):
Γûá Replacing your Shredder if deleted
ΓòÉΓòÉΓòÉ 2.5. Controlling order of execution in Startup folder ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Startup execution window 1 ΓòÉΓòÉΓòÉ
You can control the order in which objects in your Startup folder execute.
1. Open the Startup folder in either Flowed or Non-flowed view.
2. Drag objects or their shadows into the Startup Folder in the order you
want them to execute.
ΓòÉΓòÉΓòÉ <hidden> Startup folder ΓòÉΓòÉΓòÉ
Startup folder in Flowed view with item being dragged into it.
ΓòÉΓòÉΓòÉ 2.6. Backing up the *.ini files ΓòÉΓòÉΓòÉ
Much of your system's customization is stored in two files, OS2.INI and
OS2SYS.INI. To back up these important files, add the following line to the
beginning of your CONFIG.SYS:
CALL=<drive1>:\OS2\XCOPY.EXE <drive2>:\OS2\OS*.INI <drive3>:\<path>
where
<drive1> is the letter of the drive in which XCOPY.EXE is found
<drive2> is the letter of the drive in which the *.ini files are found
<drive3> is the letter of the drive in which you would like to locate the
backups of the *.ini files
<path> is the path in which you would like to locate the backups of the *.ini
files
Note: The 2.11 CSD adds the System attribute to OS2.INI and OS2SYS.INI. In
order for this tip to work, you should use XCOPY's /T switch at the end of the
CALL command above.
Related subject(s):
Γûá Restoring last desktop backup
Γûá Backing up INI files in the background
ΓòÉΓòÉΓòÉ 2.7. Removing device drivers for better performance ΓòÉΓòÉΓòÉ
contributed by Jack Tan
If you aren't using the DOS subsystem, you can improve performance by removing
DOS-specific device drivers from loading in your CONFIG.SYS (they generally
begin with the letter V). The same applies to Win-OS/2, HPFS, CD-ROM drivers
as well.
Related subject(s):
Γûá Getting memory back from unused caches
ΓòÉΓòÉΓòÉ 2.8. Speeding up some IDE drives ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Try adding switches to the BASEDEV=IBM1S506.ADD line:
BASEDEV=IBM1S506.ADD /A:0 /U:0 /SMS
and use /V to see if the /SMS works (/V = verbose). This is supposed to speed
up IDE drives that support this feature; otherwise, it will be ignored.
(note: the switches above affect the first drive on the first adapter in the
system -- for more information on the switches, search for "basedev" in your
online OS/2 Command Reference)
ΓòÉΓòÉΓòÉ 2.9. Disabling use of the floppy drives ΓòÉΓòÉΓòÉ
by Darius Vaskelis
To prevent users from using the floppy drives under OS/2, such as in a
workstation situation:
Remove the following line from your CONFIG.SYS:
BASEDEV=IBMxFLPY.ADD
Where x is 1 for ISA and EISA, or 2 for Microchannel.
ΓòÉΓòÉΓòÉ 2.10. Getting Epson ActionLaser 1500 to work ΓòÉΓòÉΓòÉ
To get an Epson ActionLaser to work with OS/2 2.1:
1. First, follow the standard steps for non-working printers under OS/2:
a) Make sure you have a compliant cable. A parallel cable should have
all 25 pins wired, unfortunately, a lot of cables currently
manufactured only have 18 pins wired.
b) Check your interrupts. ISA and EISA bus machines cannot share
interrupts under OS/2. Often, a sound card will be set to the same
interrupt as LPT1 (IRQ7), and must be changed.
c) Get a compatible I/O card. Some parallel port cards don't seem to
work correctly under OS/2.
2. Finally, for the Epson ActionLaser, change the "Busy Delay" to +5
(covered in p.4-15 of the Epson's manual).
ΓòÉΓòÉΓòÉ 2.11. Getting memory back from unused caches ΓòÉΓòÉΓòÉ
from the OS/2 2.1 Technical Reference
You can increase available resources by disabling unused caches. If you are
running an HPFS-only system, remove (or REM) the DISKCACHE line in your
CONFIG.SYS file. Similarly, if you are running a FAT-only system, remove (or
REM) the IFS=<drive>:\OS2\HPFS.IFS line in your CONFIG.SYS.
Related subject(s):
Γûá Removing device drivers for better performance
ΓòÉΓòÉΓòÉ 2.12. Dealing with OS/2 !! SYS messages on boot ΓòÉΓòÉΓòÉ
contributed by Jack Tan
The error message:
OS/2 !! SYS01475
OS/2 !! SYS02027
means that the system files can't be found. Try removing any diskettes from
the disk drives. If this message appears when trying to boot from a hard disk,
use SYSINSTX to restore the OS/2 system files.
ΓòÉΓòÉΓòÉ 2.13. Restoring last desktop backup ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To make the Alt-F1 trick restore your last desktop backup instead of the (ugly)
default, replace the CONFIG.SYS, OS2.INI, and OS2SYS.INI in \OS2\INSTALL with
the files from your last backup. Make sure to save the original files in
\OS2\INSTALL before replacing them.
Related subject(s):
Γûá Backing up the *.ini files
ΓòÉΓòÉΓòÉ 2.14. Viewing *.inf files more conveniently ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Here are two tips to make viewing OS/2 *.inf files more convenient:
1. Put several INF files together using a plus sign. On the command line (or
'Parameters' field of the settings notebook), enter something such as:
e.g., <drive>:\BOOKS\FILE1.INF+<drive>:\BOOKS\FILE2.INF+
<drive>:\BOOKS\FILE3.INF.
The pathnames aren't necessary if the file is in a directory specified by the
HELP environmental variable.
2. You can assign the book names to an environmental variable:
e.g., SET FILE=<drive>:\BOOKS\FILE1.INF+<drive>:\BOOKS\FILE2.INF+
<drive>:\BOOKS\FILE3.INF
and execute VIEW.EXE using the variable name (e.g., VIEW FILE).
ΓòÉΓòÉΓòÉ 2.15. Using less memory for DOS images ΓòÉΓòÉΓòÉ
When you load a DOS image file (Virtual Machine Boot, or VMB), the entire
diskette image is loaded into memory. Since the files on the DOS image
diskette don't take up much room themselves, much of the memory used for the
diskette is wasted. Therefore, in order to regain memory when loading the
specific DOS session, try using double-density diskettes to make your DOS
images, instead of high-density diskettes.
Related subject(s):
Γûá Booting DOS from a C: partition within OS/2
ΓòÉΓòÉΓòÉ 2.16. Booting OS/2 in full-screen mode ΓòÉΓòÉΓòÉ
You can boot OS/2 in full-screen mode, and still retain Presentation Manager
support for multiple sessions:
1. Change:
SET RUNWORKPLACE=<drive>:\OS2\PMSHELL.EXE
in your CONFIG.SYS file to:
SET RUNWORKPLACE=<drive>:\OS2\CMD.EXE /FS
where <drive> is the drive on which OS/2 resides.
2. Create the file STARTUP.CMD in your OS/2 boot drive's root directory.
STARTUP.CMD should contain the following lines:
@ECHO OFF
START /FS
EXIT
Related subject(s):
Γûá Using OS/2 without the Workplace Shell
ΓòÉΓòÉΓòÉ 2.17. Completing shutdown ΓòÉΓòÉΓòÉ
If shutdown seems to "hang" at the first shutdown message box, this trick
sometimes works:
1. Press the Ctrl-Esc keys.
2. Wait for about a minute.
3. In many cases, a dialog box will pop up telling you that the Workplace
Shell isn't responding to system requests, and will give you the
choice of clicking on Enter to end the application, or Cancel.
4. Click on the Enter box. The shutdown usually proceeds normally.
ΓòÉΓòÉΓòÉ 2.18. Adjusting your swap file ΓòÉΓòÉΓòÉ
If you have disk space to spare, you can adjust the default startup size of
your swap file (SWAPPER.DAT) to improve system performance.
The default startup size of SWAPPER.DAT is set in your CONFIG.SYS file with the
line:
SWAPPATH=<drive>:<path> <minfree> <swapsize>
where <swapsize> is the default startup size of SWAPPER.DAT.
To adjust the startup size for better performance:
1. Monitor the size of the SWAPPER.DAT over the course of a normal day's
work. A third-party utility for monitoring swap file size makes this
task a bit easier.
2. Note the maximum size that SWAPPER.DAT reaches during normal usage.
3. Change the <swapsize> parameter of SWAPPATH to reflect at least the
maximum swap file size you noted (<swapsize> is measured in
kilobytes).
CAUTION:
You MUST have enough free drive space to use this tip. If the size of the
<swapsize> parameter violates the amount needed for the <minfree>
parameter, your system will not boot.
Related subject(s):
Γûá Setting the swap file
ΓòÉΓòÉΓòÉ 2.19. Using SVGA.EXE under real DOS ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Running SVGA.EXE in a VDM usually results in a file called SVGADATA.PMI, which
contains information which lets OS/2 access SVGA graphics modes.
Sometimes, SVGA.EXE has trouble "seeing" the video chip, and extended graphics
modes won't work correctly. If so, try running SVGA.EXE under real DOS or a
VMB. This will create a file named SVGADATA.DOS. Rename SVGADATA.DOS to
SVGADATA.PMI and copy it into your \OS2 subdirectory.
ΓòÉΓòÉΓòÉ 2.20. Loading a DOS device driver into high memory ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Load into high memory ΓòÉΓòÉΓòÉ
contributed by Xavier Caballe
In order to load a DOS device driver into high memory in a particular DOS
Session:
1. Open the settings notebook for the DOS object.
2. Choose the Session tab.
3. Click on the DOS Settings button.
4. Highlight the DOS_DEVICE setting
5. Add 'SIZE=0' (without quotes) before the path and filename for the
device driver to load in high memory. For example:
SIZE=0 C:\OS2\MDOS\ANSI.SYS
In this example, the ANSI.SYS will be loaded in the high memory area
(if available).
ΓòÉΓòÉΓòÉ <hidden> Loading device drivers high ΓòÉΓòÉΓòÉ
DOS Settings for loading a device driver high.
ΓòÉΓòÉΓòÉ 2.21. Fixing "locked" INI files ΓòÉΓòÉΓòÉ
contributed by Jack Tan
If your INI files (OS2.INI and OS2SYS.INI) stop saving system changes, they may
have been marked read-only. To reset the read-only attribute:
1. Change to your \OS2 subdirectory.
2. Type
attrib -r os2*.ini
at an OS/2 command prompt.
3. You may have to shutdown and reboot.
Note: if using OS/2 2.0, you may have to boot OS/2 from your installation
floppies in order to reset the attributes.
ΓòÉΓòÉΓòÉ 2.22. Playing audio CDs via REXX ΓòÉΓòÉΓòÉ
contributed by Xavier Caballe
The combination of REXX with MMPM/2 can be quite powerful, as demonstrated by
CDPLAY.CMD, a "poor man's CD player."
Note: requires MMPM/2
Related subject(s):
Γûá Playing media files from the command line
ΓòÉΓòÉΓòÉ 2.23. Playing media files from the command line ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Note: MMPM/2 is required.
To play a media file, use PLAY.CMD (included in MMPM/2, and requires REXX)
or MPPM.EXE.
To play a media file immediately (i.e., no need to hit the "Play" button
in the Media Player window) and close the session afterwards, use MPPM.EXE
/SC <filename> where <filename> is a WAV or AVI file.
To play a media file immediately, close the session afterwards, and not
see the Media Player window, use START /MIN MPPM.EXE /SC <filename> where
<filename> is a WAV or AVI file.
Related subject(s):
Γûá Playing audio CDs via REXX
ΓòÉΓòÉΓòÉ 2.24. Determining if you have a buffered UART in your computer ΓòÉΓòÉΓòÉ
A buffered UART (such as the 16550AF chip) is often necessary for error-free
serial communications in a multitasking environment.
To determine if your computer has a buffered UART:
1. Open an OS/2 command line session.
2. Type
MODE COMx
where x is the number of the serial port you wish to check.
3. A list of current settings for the serial port should appear. If the
line
BUFFER=N/A
appears, you do not have a buffered UART. If the BUFFER line contains
anything other than N/A, you have a buffered UART.
ΓòÉΓòÉΓòÉ 2.25. Pooling multiple printers ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Pooling printers ΓòÉΓòÉΓòÉ
Choosing multiple ports for the printer object.
ΓòÉΓòÉΓòÉ <hidden> Pooling printers. ΓòÉΓòÉΓòÉ
If you have more than one printer that use the same printer driver, and each is
attached to different parallel or serial ports, you can configure your printer
object so that waiting print jobs will be sent to any free port.
"Pooling" multiple printers:
1. Open the Settings notebook for the printer object.
2. Click on the Printer Driver tab.
3. Highlight the desired printer driver.
4. Click on the Output tab.
5. Hold the Ctrl key while selecting all the desired ports with mouse
button 1.
6. Close the Settings notebook.
ΓòÉΓòÉΓòÉ 2.26. Viewing the Nowhere subdirectory ΓòÉΓòÉΓòÉ
Note: this trick does not appear to work in OS/2 Warp.
Ever wonder what the subdirectory called Nowhere on your OS/2 boot drive is?
The Nowhere subdirectory is a place where transient objects are stored.
Since each directory represents a folder, you can view the Nowhere directory,
and watch objects appear and disappear in it:
1. Bring up the desktop's popup menu by clicking once on the desktop with
mouse button 2.
2. Choose Find.
3. In the entry box next to "Folder:" type
<drive>:\
where <drive> is the letter of the drive on which OS/2 is installed.
4. Click on the Find button. All of the objects in the root directory of
your OS/2 drive should appear in a folder.
5. Open the folder named "Nowhere." (Note: you may have to open it in
Icon view via its popup menu, depending on how your system defaults
are set.)
6. You should see some objects in your open Nowhere folder.
CAUTION:
Do not manipulate any of the objects in the Nowhere folder! Simply
observe!
7. Try opening and closing folders on your desktop; you should see
objects appear and disappear from the Nowhere folder.
8. When you are done watching the Nowhere folder, close it, then feel
free to delete the Find Results folder, since the object in it are
only shadows, not the actual objects.
ΓòÉΓòÉΓòÉ 2.27. Backing up INI files in the background ΓòÉΓòÉΓòÉ
contributed by Jorge Omar
If you would like to backup your OS2.INI and OS2SYS.INI files in the background
during the boot process:
1. Create an OS/2 batch file named BACKINI.CMD:
ATTRIB -S <drive>:\OS2\OS2*.INI
COPY <drive>:\OS2\*.BK1 <drive>:\OS2\*.BK2
COPY <drive>:\OS2\OS2*.INI <drive>:\OS2\*.BK1
ATTRIB +S <drive>:\OS2\OS2*.INI
where <drive> is the drive on which OS/2 resides.
Note: the ATTRIB command is only needed for systems running OS/2 2.11
and higher.
2. Open the Templates folder.
3. Drag off a program template and place it into the Startup folder. A
Settings notebook should open.
4. In the Path and File name box, fill in the necessary information for
BACKINI.CMD.
5. Click on the Session tab.
6. Place a checkmark next to Start Minimized.
7. Close the Settings notebook.
A variation of the above BACKINI.CMD uses XCOPY switches rather than using
ATTRIB to reset the System attribute:
BACKINI.CMD:
XCOPY <drive>:\OS2\*.BK1 <drive>:\OS2\*.BK2 /T /R /O
XCOPY <drive>:\OS2\OS2*.INI <drive>:\OS2\*.BK1
Note: the files OS2.BK1, OS2.BK2, OS2SYS.BK1, OS2SYS.BK2 must exist in
<drive>:\OS2\ before this will run!
Related subject(s):
Γûá Backing up the *.ini files
ΓòÉΓòÉΓòÉ 2.28. Caching your cdrom drive ΓòÉΓòÉΓòÉ
You can adjust the read cache for your cdrom drive. In your CONFIG.SYS, you
can add a switch to the end of the cdrom IFS line:
IFS=<drive>:\OS2\CDFS.IFS /C:<number>
where <drive> is the drive on which CDFS.IFS is located
<number> is the number of 64K segments used for the cache. The default is 2,
or 128K (2 x 64K = 128K).
ΓòÉΓòÉΓòÉ 2.29. Resetting Boot Manager to have no default partition ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Boot Manager can boot to the partition from which the system was last started,
but once you select a default partition from which to boot in Boot Manager, you
lose the ability. To reset Boot Manager so that it has no default value, issue
the following command at an OS/2 prompt:
SETBOOT /0:
ΓòÉΓòÉΓòÉ 2.30. Booting DOS from a C: partition within OS/2 ΓòÉΓòÉΓòÉ
You can create a Virtual Machine Boot to boot real DOS from the C: partition,
rather than the typical floppy boot if you are running a Boot Manager system
with real DOS on the primary (C:) partition. Point the Virtual Machine Boot at
the C: partition by setting DOS_STARTUP_DRIVE to C:. OS/2 must be installed on
a logical drive.
Related subject(s):
Γûá Using less memory for DOS images
ΓòÉΓòÉΓòÉ 2.31. Resetting the boot record ΓòÉΓòÉΓòÉ
contributed by Jack Tan
If your boot record should become damaged, you can reset your boot record by
typing the following at an OS/2 prompt:
FDISK /NEWMBR
ΓòÉΓòÉΓòÉ 3. Desktop ΓòÉΓòÉΓòÉ
This section covers tips and tricks which relate to the Workplace Shell.
Topics in this section:
Γûá Saving desktop without shutting down
Γûá Adding an "open folder" entry to the desktop's popup menu
Γûá Changing color of shadow icon text
Γûá Moving icon a small distance
Γûá Changing desktop bitmaps randomly at specified interval
Γûá Changing the standard mouse pointer
Γûá Making an object prompt for a parameter
Γûá Finding a "covered" icon
Γûá Changing icon text color
Γûá Recovering after an accidental Arrange
Γûá Creating an onscreen "app bar"
Γûá Creating a "trash can"
Γûá Selecting objects without mouse
Γûá Hiding a folder
Γûá Creating a system file editor object
Γûá Retrieving a "changed" icon
Γûá Associating data files with programs
Γûá Creating new printer objects
Γûá Creating your own templates
Γûá Replacing your Shredder if deleted
Γûá Deleting "undeletable" objects
Γûá Managing your icons
Γûá Editing object names on the desktop
Γûá Moving a template object without creating a copy
Γûá Changing the long name (icon text) of a file or folder without changing
the real name
Γûá Adding INF files to the desktop popup menu
Γûá Recreating a "lost" template.
Γûá Associating icon with executable
Γûá Shortening Pulldown Menus
Γûá Removing the Drive B Icon from the Drives Object
Γûá Creating a Program Object from Executables
ΓòÉΓòÉΓòÉ 3.1. Saving desktop without shutting down ΓòÉΓòÉΓòÉ
To save the settings of your desktop without shutting down OS/2:
by Jack Tan
1. Open the Settings folder for the Desktop.
2. Choose the Window tab.
3. Under Object Open Behavior, choose Create New Object.
4. Close the Settings folder.
5. Click on the arrow next to Open in the Desktop's popup menu; choose
Icon View.
6. A folder of your Desktop should appear. You can arrange this folder
any way you wish.
7. Close the folder of your Desktop to save its settings. The icon
positions will be saved.
8. Change the Object Open Behavior to Display Existing Window.
9. To activate the newly-saved Desktop, use a kill utility to kill the
second PMSHELL process. The Workplace Shell will restart with your
newly-saved icon settings.
Related subject(s):
Γûá Recovering after an accidental Arrange
ΓòÉΓòÉΓòÉ 3.2. Adding an "open folder" entry to the desktop's popup menu ΓòÉΓòÉΓòÉ
To add an entry to the desktop's popup menu which allows you to open a specific
folder:
1. Create a REXX script, OPEN.CMD to open the folder.
2. Open the Templates folder.
3. Use the right mouse button to drag a copy of the Program template to
the desired final location. Its Settings notebook should open.
4. Fill in the path and file name (OPEN.CMD) on the Programs page.
Complete the General page as desired.
5. Close the Settings notebook.
6. Open the Settings notebook for the Desktop.
7. Choose the Menu tab.
8. If using OS/2 v2.1, drag the icon of your newly-created OPEN.CMD
object onto the box underneath "Actions on menu: Primary pop-up menu."
If using OS/2 v2.0, click on the Create Another button and fill in the
proper information.
9. The menu choice for your OPEN.CMD object should now be available on
the desktop's popup menu.
Note: If you repeat the "call SysSetObjectData" line a second time, the
folder will open in the foreground.
Related subject(s):
Γûá Adding command sessions to the desktop's popup menu
Γûá Opening multiple command line sessions from the desktop menu
Γûá Adding INF files to the desktop popup menu
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 3.3. Changing color of shadow icon text ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Shadow icon text window 1 ΓòÉΓòÉΓòÉ
To change the color of the shadow icon text:
1. Open the Scheme Palette.
2. Choose Shadow Text.
3. Choose the desired color from the color wheel.
4. Close the Scheme Palette.
5. Drag (or Alt-drag) the desired scheme to the desired folder with the
right mouse button.
Related subject(s):
Γûá Changing icon text color
ΓòÉΓòÉΓòÉ <hidden> Scheme Palette ΓòÉΓòÉΓòÉ
Scheme Palette with Shadow Text highlighted.
ΓòÉΓòÉΓòÉ 3.4. Moving icon a small distance ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Moving icon window 1 ΓòÉΓòÉΓòÉ
from Tim Sipples' FAQ
To move an icon a small distance, "grab" the outer edge of the icon with the
mouse and drag it to the new position.
ΓòÉΓòÉΓòÉ <hidden> Moving icon ΓòÉΓòÉΓòÉ
Moving an icon a small distance.
ΓòÉΓòÉΓòÉ 3.5. Changing desktop bitmaps randomly at specified interval ΓòÉΓòÉΓòÉ
The Desktop bitmaps can be changed via a REXX script, BITMAP.CMD. Note that
this script does not support tiling of bitmaps.
You must set the environmental variable BOOTDRIVE to use the new version of
BITMAP.CMD, e.g.,
SET BOOTDRIVE=<drive:>
where <drive> is the drive from which you boot OS/2
Changes to bitmap.cmd (thanks to Jack Tan) added so that bitmap subdirectory is
no longer hard-coded into the script.
Other REXX scripts:
Γûá OPEN.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 3.6. Changing the standard mouse pointer ΓòÉΓòÉΓòÉ
contributed by Jack Tan; original by Dann Lunsford
You can replace the various mouse pointers with your own customized creations,
and can remove the customized pointers.
1. Use the Icon Editor to create a mouse pointer file with the extension
*.PTR.
2. Create the REXX script, SETPTR.CMD.
3. Type SETPTR.CMD /? for help.
CAUTION:
Do not move the *.ptr file after assigning the mouse pointer! You will
not be able to boot your machine if the *.ptr file is missing or invalid.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 3.7. Making an object prompt for a parameter ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Object prompt window 1 ΓòÉΓòÉΓòÉ
To make an object prompt for a parameter when invoked
1. Open the Settings notebook for the object.
2. In the Parameters field of the Program page, enter a left square
bracket, a space, then a right square bracket,
i.e., [ ]
3. If you want text to appear along with parameter prompting, insert the
desired text between the square brackets.
ΓòÉΓòÉΓòÉ <hidden> Settings notebook ΓòÉΓòÉΓòÉ
Parameters box of Settings notebook.
ΓòÉΓòÉΓòÉ 3.8. Finding a "covered" icon ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Covered icons window 1 ΓòÉΓòÉΓòÉ
The disadvantage of having many windows open on the desktop is that icons on
the desktop can often get covered. To find an icon more easily:
1. Click the right mouse button on a clear space on the desktop.
2. Click on the arrow next to Open on the popup menu.
3. Choose Tree or Details View (Icon View can only be selected if the
Desktop's object open behavior has been set to Create New Window);
this will open up a new view of your desktop from which you can find
the icon you want.
ΓòÉΓòÉΓòÉ <hidden> Desktop Popup Menu ΓòÉΓòÉΓòÉ
Desktop's popup menu with Tree View highlighted.
ΓòÉΓòÉΓòÉ 3.9. Changing icon text color ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Color Palette ΓòÉΓòÉΓòÉ
The color of the icon text on your desktop can be changed as follows:
1. Open the Color Palette.
2. Hold the Ctrl key.
3. Use the right mouse button to drag the desired color to the desktop.
Related subject(s):
Γûá Changing color of shadow icon text
ΓòÉΓòÉΓòÉ <hidden> Color Palette ΓòÉΓòÉΓòÉ
Color Palette with color being dragged with mouse.
ΓòÉΓòÉΓòÉ 3.10. Recovering after an accidental Arrange ΓòÉΓòÉΓòÉ
To regain your desktop's icon positions after an accidental Arrange, use a
third-party utility which can kill processes to kill the second instance of
PMSHELL. The Workplace Shell will restart with your old icon positions.
Related subject(s):
Γûá Saving desktop without shutting down
ΓòÉΓòÉΓòÉ 3.11. Creating an onscreen "app bar" ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> App bar window 1 ΓòÉΓòÉΓòÉ
You can create something that acts a little like an "app bar":
1. Create a new folder.
2. Size the folder so that it has the shape and size that you like, then
position it where you like.
3. Set the folder's view to either Flowed or Non-flowed.
4. Drag shadows of your most-used applications to the folder.
5. Drag a shadow of your "app bar" folder to your Startup folder.
6. You now have a folder of your most-used apps that will open at boot.
You can further customize the "app bar" with a utility that will cause
the folder to "float" on top of other windows so that it will be more
accessible.
ΓòÉΓòÉΓòÉ <hidden> App Bar ΓòÉΓòÉΓòÉ
Example of an App Bar.
ΓòÉΓòÉΓòÉ 3.12. Creating a "trash can" ΓòÉΓòÉΓòÉ
You can create a trash can-like icon on your desktop:
1. Open the Templates folder and make a copy of the Folder template.
2. You should now have a template called Folder:1; rename it to Trash, or
whatever you like.
3. Attach your favorite trash can icon to your Trash template.
4. To create a trash can, use your right mouse button to drag a Trash
folder from your Trash template onto your desktop.
5. Drag objects to the Trash as you see fit.
6. When you want to empty the Trash can, simply delete the folder, then
replace it with a new Trash can by pulling one off of your Trash
template.
7. The advantage of using the Trash can over the shredder is that you can
open your Trash can and observe the contents, and remove what you
don't want deleted.
contributed by Chris Corzine
Another trash can tip:
1. Create a subdirectory called <drive>:\DESKTOP\TRASH (where <drive> is
the drive on which OS/2 resides).
2. Create a batch file called EMPTRASH.CMD. It should contain the line
DEL <drive>:\DESKTOP\TRASH /N
3. Add EMPTRASH.CMD to the menu of your trash folder and call the menu
choice "Empty Trash."
4. Your trash folder should now have an Empty Trash choice on its menu.
ΓòÉΓòÉΓòÉ 3.13. Selecting objects without mouse ΓòÉΓòÉΓòÉ
You can select objects in folders or the Deskop without a mouse. Simply type
the first letter of the object, and the object will be highlighted. Hit Enter
to open the object. If more than one object begins with the same letter,
subsequent typing of the same letter will jump between each object that begins
with that letter.
Related subject(s):
Γûá Selecting listbox entries without a mouse
ΓòÉΓòÉΓòÉ 3.14. Hiding a folder ΓòÉΓòÉΓòÉ
You can hide folder icons on the desktop so that others can't see them:
1. Open the Settings notebook of the folder which you wish to hide.
2. Click on the File tab, then click on the right arrow in the lower
right corner to turn to the second page of the File tab.
3. Place a check mark next to Hidden under the Flags section. The folder
should now be hidden.
To view the folder's icon once again:
1. Open the Settings notebook for the Desktop.
2. Click on the Include tab.
3. Click on the right arrow in the lower right corner to turn to the
second page of the Include tab.
4. Click on Change. A new dialog box will appear.
5. In the dialog box, choose the following settings:
a) Property to be considered = Flags
b) Comparison type = Not equal
c) Comparison value = H
6. Click on Change.
7. Close Settings notebook. The icon should now be visible.
ΓòÉΓòÉΓòÉ 3.15. Creating a system file editor object ΓòÉΓòÉΓòÉ
You can create an object which, when opened, will open your system setup files
for editing, through the aid of a Work Area folder:
1. Open the Settings notebook for the System Editor.
2. Click on the Association tab.
3. If Plain Text does not appear in the Current Types box, use the Add
button to add it from the Available Types box. Close the Settings
notebook.
4. Create a new folder.
5. Open the Settings notebook for the new folder.
6. Click on the File tab.
7. Place a check in the box next to Work Area. Close the Settings
notebook.
8. Open the Drives object, then open the drive(s) with the CONFIG.SYS,
WIN.INI, and SYSTEM.INI files.
9. Open the Settings notebook for the CONFIG.SYS file.
10. Click on Association.
11. If Plain Text does not appear in the Current Types box, use the Add
button to add it from the Available Types box. Close the Settings
notebook. Repeat for the Settings notebook for the WIN.INI and
SYSTEM.INI files.
12. Drag shadows of the CONFIG.SYS, WIN.INI, and SYSTEM.INI files into the
new folder.
13. Open the new folder if not already open.
14. Use the right mouse button on the CONFIG.SYS shadow object to popup
the menu. Click on the arrow next to Open, choose System Editor.
Your CONFIG.SYS should be loaded into the System Editor. Repeat for
WIN.INI and SYSTEM.INI.
15. Leaving the three System Editor windows open, close the new folder.
16. You should now have a folder object that will open up your system
files automatically when the folder is opened.
ΓòÉΓòÉΓòÉ 3.16. Retrieving a "changed" icon ΓòÉΓòÉΓòÉ
In OS/2 2.1, making changes to an object's settings often causes the object's
icon to revert to its default icon. To retrieve your customized icon, this
usually works:
1. Open the object's Settings notebook.
2. Choose the General tab.
3. Click on the Undo button.
Note: this behavior is fixed in the 2.11 CSD.
Related subject(s):
Γûá Managing your icons
ΓòÉΓòÉΓòÉ 3.17. Associating data files with programs ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Associate files ΓòÉΓòÉΓòÉ
Want to be able to double click on a data file object and have it open in its
appropriate application? Try setting up associations in your applications:
1. Open the Settings notebook for the application.
2. Choose the Association tab.
3. Under Available Types, see if you can find the file type appropriate
for your application. If so, highlight the file type, and press the
Add button to the right of the box.
4. If the file type you need doesn't exist under Available Types, and the
data files you wish to have associated have a common file extension or
name, enter the common part of the filename (with appropriate
wildcards) in the New Name box. Click on the Add button to the right
of the box.
5. If neither of the above two situations applies, open up the Settings
notebook for each data file you wish to associate, and set up the
association there.
Note that this does not work for all programs.
ΓòÉΓòÉΓòÉ <hidden> Associations ΓòÉΓòÉΓòÉ
Settings notebook displaying Describe association.
ΓòÉΓòÉΓòÉ 3.18. Creating new printer objects ΓòÉΓòÉΓòÉ
To create a new printer object:
1. Open the Templates folder.
2. Drag a new printer object out from the Printer template with the right
mouse button.
3. Customize the settings for your printer.
ΓòÉΓòÉΓòÉ 3.19. Creating your own templates ΓòÉΓòÉΓòÉ
You can create your own templates for customized uses. For example, you can
create a template of a word processor file with boilerplate text for business
letters. The next time you want to write a new business letter, just drag a
copy off of your customized template, and the file, complete with your
pre-defined settings, will be ready to edit.
To create a customized template:
1. Customize your data file (such as a wordprocessor file) to the way you
want it. Save the file.
2. Open the Drives object and find the file you just created.
3. Make a copy of the file object; you can either use Copy from the
object's pop-up menu, or hold down the Ctrl key while dragging off a
copy with your right mouse button.
4. Open the Settings notebook for the copy you just made.
5. Choose the General tab.
6. Place a check mark next to Template. Close the notebook.
7. When you want to use the new template, just use your right mouse
button and drag a copy off of the template.
Related topic(s):
Γûá Moving a template object without creating a copy
ΓòÉΓòÉΓòÉ 3.20. Replacing your Shredder if deleted ΓòÉΓòÉΓòÉ
Did you somehow manage to shred your Shredder? If so, SHREDDER.CMD can replace
it.
CAUTION:
This REXX script does not check to see if you already have a Shredder present,
and will replace one if it exists.
Related subject(s):
Γûá Finding settings for original objects
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 3.21. Deleting "undeletable" objects ΓòÉΓòÉΓòÉ
If you find you have an undeletable object, this trick sometimes (but not
always) works.
1. Insert a floppy disk in a floppy drive.
2. Open the Drives object.
3. Drag the undeletable object to the floppy drive object. Make sure
that you are moving the object (you can ensure this by holding the
Shift key while dragging).
4. Format the floppy disk.
ΓòÉΓòÉΓòÉ 3.22. Managing your icons ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Change icon ΓòÉΓòÉΓòÉ
contributed by George Orvis
To manage your icons more easily:
1. Place your icons (*.ICO) into a subdirectory (or several
subdirectories, if you have a large number of icons).
2. Create an object of that directory:
a) Open the Drive object of the drive in which the icon subdirectory
is located.
b) Drag a shadow of the icon subdirectory into the desired location.
3. Set view of the folder to Icon View.
4. You now have a handy folder full of icons. If you double click on an
icon, it starts the icon editor.
5. To change an object's icon (OS/2 2.1):
a) Open the Settings notebook of the object.
b) Choose the General tab.
c) Drag an icon out of your icon folder with the right mouse button,
and drop it onto the icon on the General page of the Settings
notebook.
Related subject(s):
Γûá Retrieving a "changed" icon
ΓòÉΓòÉΓòÉ <hidden> Icon directory ΓòÉΓòÉΓòÉ
Directory of icon files
ΓòÉΓòÉΓòÉ <hidden> Creating object ΓòÉΓòÉΓòÉ
Creating an icon directory object.
ΓòÉΓòÉΓòÉ <hidden> Setting Icon view ΓòÉΓòÉΓòÉ
Setting icon directory folder to Icon view by default.
ΓòÉΓòÉΓòÉ <hidden> Icon folder ΓòÉΓòÉΓòÉ
Folder full of icons.
ΓòÉΓòÉΓòÉ <hidden> Changing an icon ΓòÉΓòÉΓòÉ
Changing an object's icon by dragging and dropping (OS/2 2.1).
ΓòÉΓòÉΓòÉ 3.23. Editing object names on the desktop ΓòÉΓòÉΓòÉ
contributed by Lt. Rob Targosz
You can change the icon text as follows:
1. Select the icon.
2. Press Shift-F9 on your keyboard, or hold the Alt key and click on the
icon text with mouse button 1.
3. Type in the new icon text
4. Click on the screen with your mouse away from the icon.
contributed by Jack Tan
When editing the name of an object on the desktop, use the main keyboard
"Enter" key to add a newline to the name. Use the keypad "Enter" key to
signal the end of editing.
Note: this may not be supported on all keyboards.
ΓòÉΓòÉΓòÉ 3.24. Moving a template object without creating a copy ΓòÉΓòÉΓòÉ
contributed by Nathan Hamblen
To move a template object without dragging off a copy of the template, hold
down the Shift key while dragging the template with mouse button 2.
Related topic(s):
Γûá Creating your own templates
ΓòÉΓòÉΓòÉ 3.25. Changing the long name of a file or folder without changing the real name ΓòÉΓòÉΓòÉ
contributed by Bill Parrill
The long name, or icon text, of a file or folder can be changed without
changing its real name with PUTLONG.CMD.
where myfil.ext can either be a filename or the full path to a subdirectory
which represents a folder.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá SHREDDER.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
ΓòÉΓòÉΓòÉ 3.26. Adding INF files to the desktop popup menu ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> INF file to popup menu ΓòÉΓòÉΓòÉ
Settings notebook for INF object.
ΓòÉΓòÉΓòÉ <hidden> INF file to popup menu ΓòÉΓòÉΓòÉ
INF files are those that are viewed with OS/2's VIEW.EXE. If an INF file is
added to a popup menu via the regular procedure, attempts to open the INF file
will result in a "Topic not found" error message. To add an INF file to the
desktop's popup menu:
1. Create a viewable INF object:
a) Open the Templates folder. Drag a Program template off with mouse
button 2. A Settings notebook will open.
b) On the Program page, under Path and file name, type:
<drive>:\OS2\VIEW.EXE
where <drive> is the drive on which OS/2 resides.
c) In the Parameters box, enter the path and name of the INF file,
then append a percent sign (%) to the end of the file name.
d) Close the Settings notebook for the INF object.
2. Add the INF file to the desktop's popup menu:
a) Open the Settings notebook for the desktop.
b) Click on the Menu tab.
c) With mouse button 2, drag the INF object onto the box under Actions
on Menu.
d) Close the Settings notebook for the desktop.
3. You should now have a menu choice for the INF file.
Related subject(s):
Γûá Adding an "open folder" entry to the desktop's popup menu
Γûá Adding command sessions to the desktop's popup menu
ΓòÉΓòÉΓòÉ 3.27. Recreating a "lost" template ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To recreate a lost template:
1. Find an object on your system which is of the same type as the one
that was lost.
2. Pop up the menu of the object by clicking on the object once with
mouse button 2.
3. Select Create Another from the menu.
4. Open the Settings notebook for the new object.
5. Click on the General tab.
6. Place a check mark next to Template.
7. Close the Settings notebook for the object.
8. You should now have a template object.
ΓòÉΓòÉΓòÉ 3.28. Associating icon with executable ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To associate an icon with an executable:
1. Copy the icon file to the same directory as the executable.
2. Rename the icon file to the same base name as the executable, except
with the extension *.ICO.
ΓòÉΓòÉΓòÉ 3.29. Shortening Pulldown Menus ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To shorten the popup/pulldown menus, add:
SET MENUSTYLE=SHORT
to your CONFIG.SYS. Several menu choices will be removed, including Help,
Create another, Create Shadow, Copy, Move, Delete, and Find.
ΓòÉΓòÉΓòÉ 3.30. Removing the Drive B Icon from the Drives Object ΓòÉΓòÉΓòÉ
contributed by Timur Tabi
If you have only one floppy drive, but the Drives object still insists on
having a Drive B object, you can remove it as follows:
1. Open the Settings notebook for the Drives object.
2. Choose the Include page.
3. Delete the existing criterion.
4. Add new criteria with the following values:
Γûá Attribute = Object Title
Γûá Comparison = is equal to
Γûá Comparison Value = drive b
Γûá Use of criteria = E - exclude
5. Close the Settings notebook.
ΓòÉΓòÉΓòÉ 3.31. Creating a Program Object from Executables ΓòÉΓòÉΓòÉ
contributed by Timur Tabi
Easily create program objects from executable files with PROGRAM.CMD.
1. Create a program object called "Make Object."
2. In the Path and filename box, enter the path and name of PROGRAM.CMD.
3. In the Parameters box, put:
%* [What is the name of this object?]
4. Choose the Session page.
5. Check the Start Minimized box.
6. Choose the Associations page.
7. Add associations for files matching the *.EXE, *.CMD, *.BAT and *.COM
file extensions.
8. Close the Settings notebook.
9. Each *.EXE, *.CMD, *.BAT and *.COM file should now have a "Make
Object" choice on the Open menu. Additionally, the program icon can
be dragged and dropped onto the Make Object icon. A program object
for the desired program will be created on your desktop.
ΓòÉΓòÉΓòÉ 4. Presentation Manager ΓòÉΓòÉΓòÉ
This section covers tips and tricks which affect Presentation Manager.
Topics in this section:
Γûá Making fonts extremely small
Γûá Starting PM programs minimized
Γûá Changing the default PM system font
Γûá Moving a window in the background
Γûá Closing several windows at once
Γûá Using keyboard shortcuts in PM
Γûá Navigating in notebooks without a mouse
Γûá Changing the default view of a folder
Γûá Speeding up opening folders
Γûá Manipulating objects through the Window List
Γûá Selecting listbox entries without a mouse
Γûá Making "no-shows" re-appear
Γûá Opening the parent folder
Γûá Jumping between windowed sessions
Γûá Starting an OS/2 command line from a folder's directory
Γûá Opening windowed command line in the background
Γûá Speeding up opening folders II
Γûá Resetting Drive Open Behavior
Γûá Scrolling in the Background
ΓòÉΓòÉΓòÉ 4.1. Making fonts extremely small ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Small fonts split window 1 ΓòÉΓòÉΓòÉ
You can make most Presentation Manager fonts as small as you like:
1. Open the Font Palette.
2. Double click on one of the fonts. A new dialog box will open.
3. Under "Size," highlight the font size shown in the box.
4. Type in a new font size that is non-zero (decimal values work); you
should notice a corresponding change in the size of the font in the
Sample box.
Note that this trick does not work for System Proportional, System
Monospaced, or System VIO fonts.
Related subject(s):
Γûá Changing the default PM system font
ΓòÉΓòÉΓòÉ <hidden> Font Palette ΓòÉΓòÉΓòÉ
Font Palette dialog box with point size highlighted.
ΓòÉΓòÉΓòÉ 4.2. Starting PM programs minimized ΓòÉΓòÉΓòÉ
from Tim Sipples' FAQ
In order to start Presentation Manager programs minimized
1. Open the Settings notebook for the object.
2. On the Program page, change the name of the program so that it is
misspelled.
3. Go to the Session page and click on Start Minimized.
4. Go back to the Program page, and correct the spelling of the program
name.
5. Close the Settings notebook.
ΓòÉΓòÉΓòÉ 4.3. Changing the default PM system font ΓòÉΓòÉΓòÉ
You can change the default system font with a REXX script, SETFONT.CMD.
However, the font used in the Settings notebooks will not be affected.
Note: system fonts are designated by font size and font name, separated only by
a period. (e.g., 8pt Helv would be designated by "8.Helv")
Note: only the "default" fonts will work, e.g., Helv (not Helvetica), Tms Rmn
(not Times Roman), System Proportional, and System Monospaced.
Related subject(s):
Γûá Making fonts extremely small
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 4.4. Moving a window in the background ΓòÉΓòÉΓòÉ
You can move a window in the background without bringing it to the front by
holding the Ctrl key and dragging the window by its title bar with your mouse.
Related subject(s):
Γûá Opening windowed command line in the background
ΓòÉΓòÉΓòÉ 4.5. Closing several windows at once ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Closing windows split window 1 ΓòÉΓòÉΓòÉ
You can close all or several of your open windows using the following method:
1. Bring up the Window List with Ctrl-Esc or clicking both mouse buttons
at once.
2. Highlight the windows you want to close with your mouse.
3. Press the Delete key on your keyboard, or click your right mouse
button on one of the highlighted entries and choose Close from the
popup menu.
ΓòÉΓòÉΓòÉ <hidden> Closing windows split window 2 ΓòÉΓòÉΓòÉ
Window List with highlighted items and popup menu.
ΓòÉΓòÉΓòÉ 4.6. Using keyboard shortcuts in PM ΓòÉΓòÉΓòÉ
There are plenty of keyboard shortcuts in Presentation Manager. Here are just
a few of the lesser-known ones:
1. Alt-Backspace = undo last action (note that this doesn't always work).
2. Ctrl-Del = erase to end of field (useful when you have to retype text
in a field - press Home to get to the beginning of a field, then
Ctrl-Del to erase the text in the field - no more endless
backspacing).
3. Alt-F4 = close window.
4. Alt-F5 = restore window.
5. Alt-F6 = move between related windows, such as between an application
and its Help Window.
6. Alt-F7 = move window with cursor keys.
7. Alt-F8 = resize window with cursor keys.
8. Alt-F9 = minimize/hide window.
9. Alt-F10 = maximize window.
10. F5 = refresh window.
Related subject(s):
Γûá Navigating in notebooks without a mouse
ΓòÉΓòÉΓòÉ 4.7. Navigating in notebooks without a mouse ΓòÉΓòÉΓòÉ
To navigate around the notebooks (such as an object's Settings notebook)
without a mouse (note that sometimes these keys don't always act consistently):
1. Down/Up Arrows = moves between notebook tabs when a tab is highlighted
2. Tab = moves dotted box highlight between selections
3. Spacebar = moves to next page if its notebook tab is highlighted
4. Alt-Down Arrow = move from notebook tab to page
5. Alt-Up Arrow = move from page to notebook tab
6. Alt-PageDown = move to next page
7. Alt-PageUp = move to previous page
8. Ctrl-Tab = move to next field on a page
9. Shift-Tab = move to previous field on a page
Related subject(s):
Γûá Using keyboard shortcuts in PM
ΓòÉΓòÉΓòÉ 4.8. Changing the default view of a folder ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Default folder view ΓòÉΓòÉΓòÉ
1. Open the Settings notebook for the folder you wish to change.
2. Choose the Menu tab.
3. Highlight ~Open in the box marked Available Menus.
4. Click on the Settings button to the right of the box. A new dialog
box will open.
5. Under Default Action, click on the down arrow next to the box.
Several choices will be revealed. Choose the one you wish.
6. Click on OK, and close the Settings notebook.
Related subject(s):
Γûá Resetting Drive Open Behavior
ΓòÉΓòÉΓòÉ <hidden> Changing default view ΓòÉΓòÉΓòÉ
Dialog box with Default Action choice.
ΓòÉΓòÉΓòÉ 4.9. Speeding up opening folders ΓòÉΓòÉΓòÉ
contributed by David Haar
Folders open faster when set to Flowed view:
1. Open the Settings notebook for the folder.
2. On page 1 of the View section, click on Flowed.
You may also wish to have the folders sorted automatically:
1. Open the Settings notebook for the folder.
2. Choose the Sort tab.
3. In the pull down box under Default Sort Attribute, choose which type
of sorting you like.
4. Place a check next to Maintain Sort Order.
5. Close the Settings notebook.
Related subject(s):
Γûá Speeding up opening folders II
ΓòÉΓòÉΓòÉ 4.10. Enlarging the mouse cursor ΓòÉΓòÉΓòÉ
You can make the mouse cursor larger on systems with standard VGA with
LARGE.CMD.
The system must be rebooted for the change to take effect.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 4.11. Manipulating objects through the Window List ΓòÉΓòÉΓòÉ
correction by Martin Lafaix
You can affect objects that are listed in the Window List:
Γûá Holding the Shift key and double-clicking on an object's name in the
Window List will minimize the application.
Γûá Holding the Ctrl key and double-clicking on an object's name in the
Window List will maximize the application.
Γûá Holding the Alt key and single-clicking on an object's name in the
Window List will allow you to change the name of the object.
ΓòÉΓòÉΓòÉ 4.12. Selecting listbox entries without a mouse ΓòÉΓòÉΓòÉ
An easy way to select an entry in a Presentation Manager listbox is to type the
first letter of the name of the entry. Subsequent presses of the same letter
will cycle through all listbox entries which start with that letter.
Related subject(s):
Γûá Selecting objects without mouse
ΓòÉΓòÉΓòÉ 4.13. Making "no-shows" re-appear ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> No shows ΓòÉΓòÉΓòÉ
Sometimes you will swear that you've opened an application, but for some
reason, you don't see it onscreen (the Sticky Pad and Settings notebooks are
especially notorious). Try this, and see if it does the trick:
1. Use Ctrl-Esc or click both mouse buttons simultaneously on the desktop
to open the Window List.
2. Click the right mouse button on the name of the offending application.
This will pop up the object's menu.
3. Choose either Tile or Cascade from the menu. The application should
appear.
ΓòÉΓòÉΓòÉ <hidden> "No shows" ΓòÉΓòÉΓòÉ
Window List with Tile choice selected for Settings notebook.
ΓòÉΓòÉΓòÉ 4.14. Opening the parent folder ΓòÉΓòÉΓòÉ
contributed by Brian Mathewson
You can open the parent of a folder from the folder's pulldown menu with an
object created from a REXX script and added to the folder's menu:
1. Create the REXX script OPENPAR.CMD.
2. Create an object from OPENPAR.CMD:
a) Open the Templates folder.
b) Drag out a Program template with the right mouse button. A
settings notebook will open.
c) Enter the location and name of OPENPAR.CMD in the Path and Name
field on the Program page.
d) Choose the Session tab.
e) Place a check next to Start Minimized.
f) Choose the General tab.
g) In the Title field, name the object whatever you wish.
h) Close the settings notebook for the new object.
3. Add the new object to the desired folder's pulldown menu:
a) Open the settings notebook for the desired folder.
b) Choose the Menu tab.
c) If using OS/2 2.1, drag the open parent folder object onto the
lower box labeled "Actions on Menu." If using OS/2 2.0, you must
use the lower Create Another button to create the new menu entry.
d) Close the settings notebook for the folder.
4. To use the new menu choice, choose it from the folder's pulldown menu.
The parent folder should open.
Note: You can change the command 'OPEN=DEFAULT' to 'OPEN=DETAILS' or
'OPEN=ICON' or 'OPEN=TREE' in OPENPAR.CMD.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 4.15. Jumping between windowed sessions ΓòÉΓòÉΓòÉ
contributed by Lt. Rob Targosz
Use Alt-Tab to jump between windowed sessions.
ΓòÉΓòÉΓòÉ 4.16. Starting an OS/2 command line from a folder's directory ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Folder's directory command line ΓòÉΓòÉΓòÉ
Settings notebook for folder's directory command line object.
ΓòÉΓòÉΓòÉ <hidden> Folder's directory command line ΓòÉΓòÉΓòÉ
contributed by Brian Mathewson
You can open a command line at a specific folder's directory from the folder's
pulldown menu:
1. Open the Templates folder.
2. Using mouse button 2, drag off a Program template. The Settings
notebook should open.
3. On the Program page, place an asterisk (*) in the Path and File Name
box.
4. In the Parameters box, place the following:
/k "cd %*"
5. Click on the Session tab.
6. Click on the box next to "OS/2 Window."
7. Click on the General tab, name the object to anything you like, then
close the Settings notebook.
8. Add the newly-created object to the menu of any folder.
9. When you click on the new menu item on the folder's pulldown menu, an
OS/2 command prompt window will open in that folder's directory.
ΓòÉΓòÉΓòÉ 4.17. Opening windowed command line in the background ΓòÉΓòÉΓòÉ
To open OS/2 and DOS windowed sessions in the background:
1. Make sure the windowed command line object to be opened is not
highlighted. To do this, you can either click once on the desktop with
mouse button 1, or hold the Ctrl key and click on the object with
mouse button 1. The object will either have dotted lines around it,
or nothing at all.
2. Hold the Ctrl key while double clicking on the object with mouse
button 1.
3. The windowed command line should open in the background.
Related subject(s):
Γûá Moving a window in the background
ΓòÉΓòÉΓòÉ 4.18. Speeding up opening folders II ΓòÉΓòÉΓòÉ
Folders appear to open faster if folder animation is disabled.
1. Open the System object. It should be located in the System Setup
folder.
2. Click on the Window tab.
3. Under "Animation," click on the choice "Disabled."
4. Close the System object. All folders on your system should now open
without animation.
Related subject(s):
Γûá Speeding up opening folders
ΓòÉΓòÉΓòÉ 4.19. Resetting Drive Open Behavior ΓòÉΓòÉΓòÉ
contributed by Craig Stark
After setting a default open behavior for a Drives object folder, it can be
reset to its default of no behavior as follows (note: this does not apply to
OS/2 Warp):
1. Open the Settings notebook for the desired Drive folder object.
2. Choose the Menu tab.
3. Highlight Open in the top listbox.
4. Select Create Another.
5. Create a temporary menu entry.
6. Click on the top Settings button.
7. Under Conditional Cascade choose the temporary menu choice as the
Default Action.
8. Under Actions on Menu, highlight the temporary menu entry, then click
on the lower Delete button.
9. The default open behavior should now be reset.
Related subject(s):
Γûá Changing the default view of a folder
ΓòÉΓòÉΓòÉ 4.20. Scrolling in the Background ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To scroll windows in the background, hold the Ctrl key while using the mouse to
drag the scrollbar of a window that is in the background.
ΓòÉΓòÉΓòÉ 5. Command Line ΓòÉΓòÉΓòÉ
This section covers tips and tricks which affect command line sessions.
Topics in this section:
Γûá Pasting text without the final carriage return
Γûá Clearing the Delete subdirectory
Γûá Searching for file names
Γûá Maximizing windows when opening
Γûá Creating a scroll buffer
Γûá Using OS/2 without the Workplace Shell
Γûá Enhancing speed of text scrolling
Γûá Adding entries to your PATH
Γûá Permanently deleting a file when Undelete is active
Γûá Suppressing echo from *.CMD files
Γûá Getting more out of your command line
Γûá Checking drive status
Γûá Shutting down from a REXX script automatically
Γûá Using multiple arguments at the OS/2 command line
Γûá Using EPM as a customized command shell
Γûá Setting the startup directory for command line objects
Γûá Formatting a diskette with the detach command
Γûá Resizing a command line window permanently
Γûá Making the system "sleep"
Γûá Substituting REPLACE for the COPY command
Γûá "Touching" a file's date and time
Γûá Adding command sessions to the desktop's popup menu
Γûá Opening multiple command line sessions from the desktop menu
Γûá Creating a command line calculator
Γûá Starting a DOS session with maximum free memory
Γûá Using START to avoid the dreaded "clock"
Γûá Coloring OS/2 command line sessions
Γûá Copying fullscreen text to the Clipboard
Γûá Displaying custom DOS settings at the command line
Γûá Using PMREXX as a scrolling command window
Γûá Switching temporarily to a different directory
Γûá Canceling print jobs from the command line
ΓòÉΓòÉΓòÉ 5.1. Pasting text without the final carriage return ΓòÉΓòÉΓòÉ
To paste text after a copy/mark operation without a final carriage return, hold
down the Shift key while choosing Paste from the pull-down menu.
ΓòÉΓòÉΓòÉ 5.2. Clearing the Delete subdirectory ΓòÉΓòÉΓòÉ
In order to remove the files from the Delete subdirectory of a drive to regain
some drive space, type the following at a command line:
UNDELETE <drive>:\* /f /s /a
where <drive> is the letter of the drive which contains the Delete subdirectory
you wish to clear.
Related subject(s):
Γûá Permanently deleting a file when Undelete is active
ΓòÉΓòÉΓòÉ 5.3. Searching for file names ΓòÉΓòÉΓòÉ
To search for a particular file name on a drive, type
DIR <drive>:\<file spec> /S
where
<drive> is the letter of the drive you wish to search
<file spec> is the specification of the file you are searching; standard wild
cards can be used.
ΓòÉΓòÉΓòÉ 5.4. Maximizing windows when opening ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Maximizing windows split window 1 ΓòÉΓòÉΓòÉ
To make all command line windows open maximized, hold the Shift key while
clicking on the maximize button.
Note: the above procedure causes anomalous behavior (the window opens in the
upper left hand corner, then repositions itself in the middle of the screen)
under the 2.11 CSD. To fix this problem, hold the Shift key while clicking on
the restore button in the uppermost right hand corner of the command line
window.
In some cases, you additionally may have to hold the Shift key while using the
mouse to resize the window to its fullest size by dragging the bottom right
corner.
Related subject(s):
Γûá Resizing a command line window permanently
ΓòÉΓòÉΓòÉ <hidden> Maximizing windows ΓòÉΓòÉΓòÉ
Command window with mouse pointer on Maximize button.
ΓòÉΓòÉΓòÉ 5.5. Creating a scroll buffer ΓòÉΓòÉΓòÉ
from Tim Sipples' FAQ
To create a small scroll-back buffer for your command line sessions, type
MODE 80,102
Related subject(s):
Γûá Resizing a command line window permanently
Γûá Setting video modes in a command line window
ΓòÉΓòÉΓòÉ 5.6. Using OS/2 without the Workplace Shell ΓòÉΓòÉΓòÉ
To use OS/2 without loading the Workplace Shell, replace the following line in
your CONFIG.SYS
SET RUNWORKPLACE=<drive>:\OS2\PMSHELL.EXE
with
SET RUNWORKPLACE=<drive>:\OS2\CMD.EXE
where <drive> is the letter of the drive on which OS/2 is located.
Note that you can always invoke the Workplace Shell by typing PMSHELL at an
OS/2 command line. It can consequently be removed by closing it from the
Window List.
Related subject(s):
Γûá Booting OS/2 in full-screen mode
ΓòÉΓòÉΓòÉ 5.7. Enhancing speed of text scrolling ΓòÉΓòÉΓòÉ
Tricks for speeding up text display.
Related subject(s):
Γûá Changing font size
Γûá Changing Video_ROM_Emulation
ΓòÉΓòÉΓòÉ 5.7.1. Changing font size ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Changing font size window 1 ΓòÉΓòÉΓòÉ
Fonts which are 8 pixels wide generally display faster than those which are not
8 pixels wide. Choose Font Size from the pull-down menu, then choose a "x 8"
type of font size.
ΓòÉΓòÉΓòÉ <hidden> Font Size dialog ΓòÉΓòÉΓòÉ
Font Size dialog box with 14x8 font size highlighted.
ΓòÉΓòÉΓòÉ 5.7.2. Changing Video_ROM_Emulation ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> VideoROM window 1 ΓòÉΓòÉΓòÉ
Text scrolling speed can also be enhanced using the Video_ROM_Emulation
setting.
1. Select DOS Settings from either the pull-down menu of a DOS session,
or from the Session page of the Settings notebook of a DOS session.
2. Highlight Video_ROM_Emulation.
3. Try the setting both on and off to find out if one setting results in
better performance than the other.
ΓòÉΓòÉΓòÉ <hidden> DOS Settings ΓòÉΓòÉΓòÉ
DOS Settings dialog with Video_ROM_Emulation highlighted.
ΓòÉΓòÉΓòÉ 5.8. Adding entries to your PATH ΓòÉΓòÉΓòÉ
You can add entries to your PATH "on the fly" by using:
PATH %PATH%;<drive>:\<path>
where
<drive> is the drive on which the subdirectory you want to add is located
<path> is the path you want to add
(This also works for DPATH)
ΓòÉΓòÉΓòÉ 5.9. Permanently deleting a file when Undelete is active ΓòÉΓòÉΓòÉ
If you have Undelete activated (via SET DELDIR in your CONFIG.SYS), but want to
delete a file or files so they can't be undeleted, use:
DEL <file(s)> /F
where <file(s)> is the file specification of the file(s) you want to delete
Related subject(s):
Γûá Clearing the Delete subdirectory
ΓòÉΓòÉΓòÉ 5.10. Suppressing echo from *.CMD files ΓòÉΓòÉΓòÉ
If you are using batch files (*.CMD) which do not have ECHO OFF statements, you
can also suppress the echo by using the /Q switch:
Example: BATCH.CMD /Q
ΓòÉΓòÉΓòÉ 5.11. Getting more out of your command line ΓòÉΓòÉΓòÉ
Supplement your command line usage by stacking commands with &&, &, ||, and ():
contributed by Jack Tan
1. && executes the second program only if the former succeeds,
e.g., RunMe.EXE && RunMeIfFormerSucceeds.EXE
2. || executes the second program if the former doesn't succeed,
e.g., RunMe.EXE || RunMeIfTheFormerDidntSucceed.EXE
3. Combining && and || results in an if..then..else situation,
e.g., If.EXE && Then.EXE || Else.EXE
(Else.EXE doesn't run if and only if both If.EXE and Then.EXE run
successfully)
4. & runs both the first and second programs,
e.g., RunMe.EXE & AndMeToo.EXE
5. () executes the instructions within the parentheses, overriding the
normal order of command precedence,
e.g., DETACH (FORMAT a: /once /v:"hi" && XCOPY c:\x A: /S) & UNZIP
myfile.zip
(the commands in parentheses are operated on by DETACH, then UNZIP
executes)
ΓòÉΓòÉΓòÉ 5.12. Checking drive status ΓòÉΓòÉΓòÉ
inspired by a code snippet by Dick Goran
You can check the status of a drive (e.g., if a floppy is inserted into a
floppy drive or not) with a REXX script, CHKDRIVE.CMD.
The routines in CHKDRIVE.CMD can be incorporated into longer REXX scripts
whenever the status of a drive needs to be ascertained.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 5.13. Shutting down from a REXX script automatically ΓòÉΓòÉΓòÉ
by David Matocha
You can shutdown your system with a countdown using SHUTDOWN.CMD combined with
a scheduling utility and a automatic power-down of the system.
Related subject(s):
Γûá Rebooting from the command line
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 5.14. Using multiple arguments at the OS/2 command line ΓòÉΓòÉΓòÉ
Unlike DOS, OS/2's command line allows you to use multiple arguments at the
command line for the DEL and DIR commands.
e.g.,
DEL <file1> <file2> <file3>
DIR <file1> <file2> <file3>
where <file1>, <file2>, and <file3> are different filenames (with any
appropriate wildcards).
ΓòÉΓòÉΓòÉ 5.15. Using EPM as a customized command shell ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> EPM shell ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Use the Enhanced Editor (EPM) command SHELL to produce a command line with the
following attributes:
Γûá Uses any font recognized by EPM.
Γûá Window sizeable to nearly any size.
Γûá Dynamically resizeable window.
Γûá Can alter text/background colors.
Γûá Scroll buffer spans the entire session.
Unfortunately, programs which take control of the screen (like
screen-based editors) won't run.
Related subject(s):
Γûá Using PMREXX as a scrolling command window
ΓòÉΓòÉΓòÉ <hidden> EPM command shell ΓòÉΓòÉΓòÉ
EPM command shell, using the Helvetica font.
ΓòÉΓòÉΓòÉ 5.16. Setting the startup directory for command line objects ΓòÉΓòÉΓòÉ
contributed by Jack Tan
The 'Working Directory' entry in the settings notebook also applies to command
lines, such as 'OS/2 Window' and 'DOS Full Screen.' In these cases, the
working directory becomes the starting directory.
ΓòÉΓòÉΓòÉ 5.17. Formatting a diskette with the detach command ΓòÉΓòÉΓòÉ
You can format a diskette in the background from the command line or in a batch
file without user intervention with the line:
DETACH FORMAT <drive>: /ONCE /V:<label>
where <drive> is the drive of the diskette you wish to format, and <label> is
the name you wish to use for the volume label.
ΓòÉΓòÉΓòÉ 5.18. Resizing a command line window permanently ΓòÉΓòÉΓòÉ
contributed by Guy Gerard Lemieux
You can save the size of any window permanently by holding the Shift key while
resizing.
Related subject(s):
Γûá Maximizing windows when opening
Γûá Creating a scroll buffer
Γûá Setting video modes in a command line window
ΓòÉΓòÉΓòÉ 5.19. Making the system "sleep" ΓòÉΓòÉΓòÉ
The REXX script SLEEP.CMD will create a pause for a specified length of time.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 5.20. Substituting REPLACE for the COPY command ΓòÉΓòÉΓòÉ
The REPLACE command will only copy files of the same name from the source to
the target:
REPLACE <source> <target>
where <source> is the drive, path, and file specification of the files you want
copied; and, <target> is the drive and path to which you want the files copied.
However, when REPLACE is used with certain command line switches, it becomes
even more useful.
Have you ever wished you could only copy files which don't already exist on the
target drive? Try:
REPLACE <source> <target> /A
Have you wanted to copy only files which have been updated? Try:
REPLACE <source> <target> /U
ΓòÉΓòÉΓòÉ 5.21. "Touching" a file's date and time ΓòÉΓòÉΓòÉ
You can "touch," i.e., change to current date and time, a file or set of files
using a form of the COPY command:
COPY <filespec> /b + ,,
where <filespec> is any valid filename or OS/2 file specification
ΓòÉΓòÉΓòÉ 5.22. Adding command sessions to the desktop's popup menu ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Adding command sessions ΓòÉΓòÉΓòÉ
When adding OS/2 or DOS command line sessions to the desktop's popup menu,
prevent the object from passing the desktop's path by putting a percent sign
(%) in the Parameters field on the Program page of the command line object's
Settings notebook.
Related subject(s):
Γûá Adding an "open folder" entry to the desktop's popup menu
Γûá Opening multiple command line sessions from the desktop menu
Γûá Adding INF files to the desktop popup menu
ΓòÉΓòÉΓòÉ <hidden> Adding command sessions ΓòÉΓòÉΓòÉ
Placing a percent sign in the Parameters field.
ΓòÉΓòÉΓòÉ 5.23. Opening multiple command line sessions from the desktop menu ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Create new window setting ΓòÉΓòÉΓòÉ
Desktop Settings notebook with Create New Window highlighted.
ΓòÉΓòÉΓòÉ <hidden> Create new window setting ΓòÉΓòÉΓòÉ
In order to be able to open multiple command line sessions from a command line
object that you added to the desktop's popup menu, you must alter the desktop's
settings, not those of the command line object:
1. Open the Settings notebook for the desktop.
2. Choose the Window tab.
3. Under Object Open Behavior, select Create New Window.
4. Close the Settings notebook.
Note: changing the Object Open Behavior for the desktop may have
unexpected results when opening other objects from the desktop.
Related subject(s):
Γûá Adding an "open folder" entry to the desktop's popup menu
Γûá Adding command sessions to the desktop's popup menu
ΓòÉΓòÉΓòÉ 5.24. Creating a command line calculator ΓòÉΓòÉΓòÉ
contributed by L. Kuru
EVAL.CMD is a REXX script for a simple, yet powerful command line calculator.
Several arithmetic functions are available:
Γûá The basic arithmetic functions:
1. + = Addition
2. - = Subtraction
3. * = Multiplication
4. / = Division
5. ** = Exponential (must be an integer)
Γûá Parentheses, e.g., EVAL (2+3)**2
Γûá Floating point numbers, e.g., EVAL 12.345567e14*1e-50
Γûá Environment variables,
e.g., set pi=3.1415926
set radius=3
EVAL %pi%*%radius%**2
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá BIGDOS.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 5.25. Starting a DOS session with maximum free memory ΓòÉΓòÉΓòÉ
contributed by Xavier Caballe
You can start a DOS session with the maximum free memory using BIGDOS.CMD.
Note: if using OS/2 2.1, you may have to change RMSIZE=640 to RMSIZE=639 in
your CONFIG.SYS file in order to get this to work.
Other REXX scripts:
Γûá OPEN.CMD
Γûá BITMAP.CMD
Γûá SETPTR.CMD
Γûá SETFONT.CMD
Γûá CHKDRIVE.CMD
Γûá SHUTDOWN.CMD
Γûá SHREDDER.CMD
Γûá SLEEP.CMD
Γûá LARGE.CMD
Γûá EVAL.CMD
Γûá PUTLONG.CMD
ΓòÉΓòÉΓòÉ 5.26. Using START to avoid the dreaded "clock" ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Use the START command in a fullscreen session to avoid the dreaded clock
pointer and continue working at the command line when loading certain
queue-hogging applications.
e.g, at a fullscreen OS/2 prompt:
START /b 123G.EXE
ΓòÉΓòÉΓòÉ 5.27. Coloring OS/2 command line sessions ΓòÉΓòÉΓòÉ
contributed by Peder Madsen
Tired of the dreaded black-and-white OS/2 command prompt? Create more colorful
prompts with the PROMPT command. Try
set prompt=$E[37;44m[$P]
which gives you white text on blue background.
Instead of 37 you can use any number between 30 and 37 to control the
foreground color, and instead of 44 you can use any number between 40 and 47 to
control the background color.
You can also use the PROMPT command in your CONFIG.SYS file to start each OS/2
command session with your favorite colors.
Note: ANSI must be turned on (this is the default).
ΓòÉΓòÉΓòÉ 5.28. Copying fullscreen text to the Clipboard ΓòÉΓòÉΓòÉ
contributed by Hugo Jimenez-Vazquez
To copy fullscreen text to the OS/2 Clipboard:
1. Open the menu for the default printer and change the status of the
jobs to "Hold."
2. Go to the OS/2 fullscreen session you wish to copy, and press the
PrintScreen button on your keyboard.
3. Go back to the OS/2 desktop and open either the Icon or Details view
of the default printer.
4. Double click on the icon of the PrintScreen job. This will place the
job into the OS/2 System Editor (E.EXE).
5. Copy the desired text from the OS/2 System Editor to the OS/2
Clipboard.
6. Delete the job from the list of the default printer.
7. Change the status of the default printer back to "Release."
ΓòÉΓòÉΓòÉ 5.29. Displaying custom DOS settings at the command line ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> DOS Settings ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To list custom DOS settings (i.e., the settings which have been changed from
the default) at the command line:
1. Open the Settings notebook for the DOS program object.
2. Put an asterisk (*) as the first character in the "Path and File Name"
box on the Program page. If the filename is already an asterisk,
place some text immediately after the asterisk.
3. The icon will change to that of an OS/2 window after the change.
4. Open the session by clicking on its icon. This should bring up an
OS/2 command line window.
5. Type "SET" (without quotes) at the command line.
6. This should list the customized DOS settings, as well as some
environmental variables.
7. When done, remove the asterisk or extra text from the Settings
notebook.
8. If the DOS session was fullscreen initially, it may be changed to a
windowed session. If so, click on the Session tab, and choose "DOS
full screen."
ΓòÉΓòÉΓòÉ <hidden> DOS Settings ΓòÉΓòÉΓòÉ
Use asterisk as first character in "Path and File Name" box.
ΓòÉΓòÉΓòÉ <hidden> DOS Settings II ΓòÉΓòÉΓòÉ
List of custom DOS settings (with cute cat pointer!).
ΓòÉΓòÉΓòÉ 5.30. Using PMREXX as a scrolling command window ΓòÉΓòÉΓòÉ
contributed by Michael Prager
Many of us have wished for a scrolling command window, as supplied in many
graphical versions of Unix. This is how to get one. At an OS/2 command line,
type:
PMREXX REXXTRY.CMD
This gives a scrolling Rexx window that executes Rexx commands interactively.
Since Rexx passes through all OS/2 commands, it can be used for executing OS/2
commands. Just don't forget that many OS/2 commands will need to be enclosed
in quotation marks.
Γûá Using EPM as a customized command shell
ΓòÉΓòÉΓòÉ 5.31. Switching temporarily to a different directory ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To switch temporarily to a different directory when at an OS/2 command line,
type CMD.EXE at the command line. Switch to the directory you want, and when
you are finished in that directory, simply type EXIT at the prompt. You will be
back in your original directory.
ΓòÉΓòÉΓòÉ 5.32. Canceling print jobs from the command line ΓòÉΓòÉΓòÉ
contributed by Jack Tan
You can use command line switches to cancel print jobs from the OS/2 command
line:
PRINT /C
will cancel the current print job on the default printing device.
PRINT /T
will cancel the current print job and the rest of the print queue on the
default printing device.
If you want to cancel a job on a device other than the default, add the switch
/D:device>
where <device> is the name of the print device (e.g., LPT2).
ΓòÉΓòÉΓòÉ 6. Win-OS/2 ΓòÉΓòÉΓòÉ
This section covers tips and tricks which affect Win-OS/2.
Topics in this section:
Γûá Reducing Win-OS/2 initial load time
Γûá Using Windows screen blanker for OS/2
Γûá Running Win-OS/2 from a DOS image
Γûá Curing "jumpy mouse"
Γûá Pasting between Windows applications
Γûá Starting seamless Windows from the command line
Γûá Using Windows File Manager on your OS/2 desktop
Γûá Fixing seamless Windows on some 2.11 CSD systems
Γûá Adding more LPT ports in Win-OS/2
ΓòÉΓòÉΓòÉ 6.1. Reducing Win-OS/2 initial load time ΓòÉΓòÉΓòÉ
If you are running Windows programs in a common session, the load time for the
first Windows program you execute will be much longer than subsequent load
times because OS/2 needs to load both a VDM and the Win-OS/2 code. If you want
to speed up loading Windows programs, load a small Windows program, such as the
Clock, via your Startup folder. Your boot time will increase, but when you
finally sit down to work, your Windows programs will load more quickly.
ΓòÉΓòÉΓòÉ 6.2. Using Windows screen blanker for OS/2 ΓòÉΓòÉΓòÉ
You can use a Windows screen blanker when running seamless Windows to blank the
OS/2 desktop. However, since Win-OS/2 can sometimes miss keystrokes intended
for Presentation Manager, be sure to set the delay of the screen blanker as
long as possible.
ΓòÉΓòÉΓòÉ 6.3. Running Win-OS/2 from a DOS image ΓòÉΓòÉΓòÉ
You can run Win-OS/2 from a DOS image, also known as a Virtual Machine Boot
(VMB) or specific DOS session:
1. Put a bootable DOS system disk in the A: drive. Make sure that you
have a simple, DOS-compatible editor on this disk that you can use to
edit the CONFIG.SYS and AUTOEXEC.BAT files.
2. Open an OS/2 command line session.
3. Create a subdirectory to store the boot images.
4. At the OS/2 command line, type VMDISK A: <imagename> where <imagename>
is a name you give to the boot image
5. When the system files have been transferred from A: to your boot image
subdirectory, close the OS/2 command line and remove the diskette from
A:.
6. Open the Templates folder and use the right mouse button to drag a
template from the Program template icon. The Settings notebook for
the new program object should open.
7. On the Program page, put an asterisk in the Path and Filename box.
8. Click on the Session tab.
9. Select either the DOS Window or DOS Full Screen button.
10. Click on the DOS settings button.
11. Highlight the DOS_STARTUP_DRIVE option.
12. In the Value box, enter the drive, path and name of your boot image.
13. Highlight DOS_FILES.
14. In the Value box, set DOS_FILES to 40.
15. Highlight DPMI_MEMORY_LIMIT.
16. In the Value box, set DPMI_MEMORY_LIMIT to 4 or higher.
17. Click on Save.
18. Close the Settings notebook.
19. Open the newly-created DOS image.
20. While in the DOS image, create/edit the CONFIG.SYS file.
21. The CONFIG.SYS should contain, among other entries, these lines:
a) DEVICE=<drive>:\OS2\MDOS\FSFILTER.SYS -- this line should be near
the top of CONFIG.SYS, and <drive> is the drive on which your OS/2
DOS support files are located.
b) DEVICE=<drive>:\OS2\MDOS\HIMEM.SYS
c) DEVICE=<drive>:\OS2\MDOS\EMM386.SYS
22. Save the CONFIG.SYS and create/edit an AUTOEXEC.BAT file as you wish.
23. Close the session by double clicking on the title bar icon.
24. Reopen the DOS image, and type WIN to start Win-OS/2.
ΓòÉΓòÉΓòÉ 6.4. Curing "jumpy mouse" ΓòÉΓòÉΓòÉ
additions by Hugo Jimenez-Vazquez and Tony Colliver
The mouse can often be "jumpy" in fullscreen Win-OS/2 sessions. Try changing
the following, checking after the first change to see if jumpiness has been
cured. If not, try the second change.
1. Open the Settings notebook for the object.
2. Choose the Session tab.
3. Click on DOS Settings.
4. Highlight IDLE_SECONDS.
5. Set IDLE_SECONDS to a value from 1 to 3 (you will have to play with
this setting).
6. Highlight IDLE_SENSITIVITY.
7. Set IDLE_SENSITIVITY to a value from 10 to 100 (you will have to play
with this setting, too).
ΓòÉΓòÉΓòÉ 6.5. Pasting between Windows applications ΓòÉΓòÉΓòÉ
Sometimes data gets lost when you're pasting between Windows applications under
Win-OS/2. If this happens to you, try:
1. Open the Win-OS/2 object's Settings notebook.
2. Choose the Session tab.
3. Click on DOS Settings.
4. Highlight VIDEO_FASTPASTE.
5. Set VIDEO_FASTPASTE to ON.
ΓòÉΓòÉΓòÉ 6.6. Starting seamless Windows from the command line ΓòÉΓòÉΓòÉ
contributed by Jack Tan
To start a seamless Windows session from the OS/2 command line:
START /WIN <program>
where <program> is the name of the Windows program you wish to run.
ΓòÉΓòÉΓòÉ 6.7. Using Windows File Manager on your OS/2 desktop ΓòÉΓòÉΓòÉ
contributed by Walter Dnes
If you are familiar with the Windows File Manager, and wish to use it as your
main shell on the OS/2 desktop (you must have seamless Windows capability to do
this):
1. Open the Templates folder.
2. Use mouse button 2 to drag out a Program template to the location you
wish it to be. The Settings notebook for the object should open.
3. On the Program page, in the "Path and File Name" box, type
<drive>:\OS2\MDOS\WINOS2\WINFILE.EXE
where <drive> is the drive on which Win-OS/2 is located.
4. Click on the Session page.
5. Select WIN-OS/2 Window.
6. Click on WIN-OS/2 Settings, and make any appropriate changes for a
Windows program (e.g., 64 meg DPMI).
7. Close the Settings notebook.
You should be able to run Windows, DOS, and OS/2 programs from the File
Manager by simply double clicking on the name of the file.
In order to run OS/2 *.CMD and REXX files, edit the "Programs=" line in
the [windows] section of WIN.INI to read:
Programs=com exe bat pif cmd
Associations in the [extensions] section of WIN.INI can also be added to
invoke OS/2 programs. For example, you can associate *.INF files with
VIEW.EXE as follows:
INF=<drive>:\OS2\VIEW.EXE ^.INF
where <drive> is the drive on which OS/2 resides.
ΓòÉΓòÉΓòÉ 6.8. Fixing seamless Windows on some 2.11 CSD systems ΓòÉΓòÉΓòÉ
Some systems running the 2.11 CSD have trouble running seamless Windows in that
double-clicking on a seamless Windows application will cause the icon to be
shaded, but nothing runs. In some cases, this is the result of improper
updating of Win-OS/2.
Check the file named SERVICE.LOG. It should be located in the subdirectory
<drive>:\OS2\INSTALL. Read through the listings to find out if either your
Win-OS/2 subdirectories or Win-OS/2 video drivers have been updated or not.
If not, you may have to run the SERVICE program located on the Service Pak disk
1, and instruct the program to update your Win-OS/2 subdirectories (it will
inform you that no updating is needed). If you are using high resolution video
drivers, you may instead only have to install the new video drivers.
CAUTION:
Make alterations to your system at your own risk!
ΓòÉΓòÉΓòÉ 6.9. Adding more LPT ports in Win-OS/2 ΓòÉΓòÉΓòÉ
contributed by Gary Pool
Windows has a limit of LPT ports 1 through 3. If you are on a LAN or are in a
situation where you have more than 3 LPT ports, you can add LPT ports by
editing your WIN.INI file. Find the "ports" section of the WIN.INI file.
There you will see LPT1.OS2, LPT2.OS2, and LPT3.OS2. Just manually add
LPT4.OS2 through LPT9.OS2 and you will be able to access those printers from
Win-OS/2.
ΓòÉΓòÉΓòÉ 7. Warp ΓòÉΓòÉΓòÉ
This section covers tips and tricks for OS/2 Warp.
ΓòÉΓòÉΓòÉ 7.1. System ΓòÉΓòÉΓòÉ
This section covers System tips for OS/2 Warp.
Topics in this section:
Γûá Changing printing from polling to interrupt-driven
Γûá Recovering a deleted Launchpad
Γûá Keeping the system running, even through traps
Γûá Setting the swap file
Γûá Creating OS/2 Warp boot diskettes
Γûá Displaying the Recovery Screen
Γûá Displaying Device Drivers on Boot
Γûá Dual Booting Without Confirmation
Γûá Adding Temporary LIBPATH Entries
Γûá Showing the Buildlevel of EXE and DLL Files
Γûá Loading Multiple Configuration Files at Boot
ΓòÉΓòÉΓòÉ 7.2. Changing printing from polling to interrupt driven ΓòÉΓòÉΓòÉ
Warp
The default mode of printing under OS/2 Warp is now via polling, rather than
interrupt-driven, as was the case in previous OS/2 versions. Polling can cause
problems with printing on some systems, and can use more system resources.
To change from the polling mode of printing to interrupt-driven printing, edit
the following line in your CONFIG.SYS file:
BASEDEV=PRINT01.SYS
to
BASEDEV=PRINT01.SYS /IRQ
Note that using the interrupt-driven mode of printing requires the use of IRQ
7.
ΓòÉΓòÉΓòÉ 7.3. Recovering a deleted Launchpad ΓòÉΓòÉΓòÉ
Warp
You can recover a deleted Launchpad by adding the word LAUNCHPAD to your SET
AUTOSTART line in your CONFIG.SYS file.
Conversely, to prevent the Launchpad from opening at boot, remove the word
LAUNCHPAD from your SET AUTOSTART line.
Related subject(s):
Γûá Removing the Launchpad permanently
ΓòÉΓòÉΓòÉ 7.4. Keeping the system running, even through traps ΓòÉΓòÉΓòÉ
Warp
To keep an unattended system, such as a BBS, running despite a TRAP condition,
add the following lines to your CONFIG.SYS file:
REIPL=ON
Setting REIPL to ON will automatically reboot your system when a TRAP occurs.
SUPPRESSPOPUPS=<drive>
SUPPRESSPOPUPS will prevent TRAP information from popping up and will log the
popup information to a log file. <drive> is the drive to which the log file
POPUPLOG.OS2 is written.
DUMPPROCESS=<drive>
DUMPPROCESS causes a process dump file PDUMP.* to be written. <drive> is the
drive letter to which PDUMP.* will be written.
ΓòÉΓòÉΓòÉ 7.5. Setting the swap file ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
The swap file in OS/2 Warp will tend to grow larger than in previous versions
of OS/2 because certain DLLs are treated differently. Therefore, to prevent
excess swapping, you may wish to increase the default size of your swap file
from the value which you used in previous versions of OS/2.
Related subject(s):
Γûá Adjusting your swap file
ΓòÉΓòÉΓòÉ 7.6. Creating OS/2 Warp boot diskettes ΓòÉΓòÉΓòÉ
Warp
OS/2 Warp has its own facility to create boot diskettes. Simply open the
System Setup folder and open the Create Utility Diskettes object.
Create Utility Diskettes object.
ΓòÉΓòÉΓòÉ 7.7. Displaying the Recovery Screen ΓòÉΓòÉΓòÉ
Warp
OS/2 Warp provides a recovery screen during reboot which gives you the
following choices:
Γûá Use customized configuration files.
Γûá Boot to a command line.
Γûá Restore previously archived configurations.
Γûá Reset your primary display to VGA mode.
Γûá Boot to the Maintenance Desktop.
To reach the recovery screen:
1. Boot OS/2 Warp.
2. During boot, a small, white box will appear in the upper left hand
corner of the screen.
3. While the white box in onscreen, press the Alt and F1 keys
simultaneously.
4. The Recovery Choices screen will appear.
Related subject(s):
Γûá Loading Multiple Configuration Files at Boot
ΓòÉΓòÉΓòÉ 7.8. Displaying Device Drivers on Boot ΓòÉΓòÉΓòÉ
Warp
contributed by Markku Leinio
To display device driver names on boot:
1. Boot OS/2 Warp.
2. During boot, a small, white box will appear in the upper left hand
corner of your screen.
3. While the white box is onscreen, press the Alt and F2 keys
simultaneously.
4. Device driver messages will appear on the screen as the drivers are
loaded.
ΓòÉΓòÉΓòÉ 7.9. Dual Booting Without Confirmation ΓòÉΓòÉΓòÉ
Warp
contributed by Jack Tan
To dual boot between DOS and OS/2 configurations using the command line without
a confirmation message, use the /QUIET command line switch. For example:
BOOT /DOS /QUIET
or,
BOOT /OS2 /QUIET
ΓòÉΓòÉΓòÉ 7.10. Adding Temporary LIBPATH Entries ΓòÉΓòÉΓòÉ
Warp
contributed by Ian Hargreaves
It is possible to add temporary LIBPATH entries to an OS/2 session using the
SET BEGINLIBPATH and SET ENDLIBPATH statements.
To add subdirectories to the beginning of the LIBPATH:
SET BEGINLIBPATH=<drive>:\<subdir1>;<drive>:\<subdir2>;
where
<drive> is the drive for the temporary LIBPATH addition(s) <subdir1> and
<subdir2> are the subdirectories to add to the LIBPATH
ΓòÉΓòÉΓòÉ 7.11. Showing the Buildlevel of EXE and DLL Files ΓòÉΓòÉΓòÉ
Warp
contributed by Jack Tan
To display the buildlevel of IBM files, type:
BLDLEVEL <filename>
where
<filename> is an IBM *.EXE or *.DLL file
ΓòÉΓòÉΓòÉ 7.12. Loading Multiple Configuration Files at Boot ΓòÉΓòÉΓòÉ
Warp
Sometimes you might need to boot your OS/2 Warp machine under different
versions of CONFIG.SYS. The OS/2 Warp Recovery Screen provides a way to do
this.
To use multiple CONFIG.SYS files:
1. Make a backup copy of your CONFIG.SYS file and save it in a safe
place.
2. Copy the CONFIG.SYS file to the BOOT subdirectory as follows:
COPY <boot drive>:\CONFIG.SYS <boot drive>:\OS2\BOOT\CONFIG.?
where
<boot drive> is your OS/2 Warp boot drive
? is replaced by any single letter of the alphabet, except X, x, C, c,
M, m, or V, v.
3. Make any custom modifications you desire to your \OS2\BOOT\CONFIG.?
file.
4. Create a batch file called ALTF1?.CMD in <boot drive>:\OS2\BOOT where
the ? is the same alphabetical character you used for CONFIG.?. The
contents of the batch file should read:
COPY <boot drive>:\OS2\BOOT\CONFIG.? <boot drive>:\CONFIG.SYS
where
? corresponds to the alphabetical character you used for CONFIG.?.
5. Change to the <boot drive>:\OS2\BOOT subdirectory.
6. Remove the read-only attribute from the file ALTF1BOT.SCR as follows:
ATTRIB ALTF1BOT.SCR -R
7. Edit and add lines to the end of ALTF1BOT.SCR describing your new
configuration choices. You should include the alphabetical character
of each choice, the name of the configuration file, and perhaps some
descriptive text. For example:
A CONFIG.A Configuration A
B CONFIG.B Configuration B
8. Save ALTF1BOT.SCR.
9. Replace the read-only attribute as follows:
ATTRIB ALTF1BOT.SCR +R
10. Your configuration choices should now show up on the Recovery Screen.
Related subject(s):
Γûá Displaying the Recovery Screen
ΓòÉΓòÉΓòÉ 7.13. Workplace Shell ΓòÉΓòÉΓòÉ
This section covers Workplace Shell tips for OS/2 Warp.
Topics in this section:
Γûá Tearing off Launchpad drawer
Γûá Opening the Settings notebook
Γûá Closing the parent folder when opening an object
Γûá Removing the Launchpad permanently
Γûá Editing animated folder icons
Γûá Bringing the Launchpad to the top
Γûá Closing parent folders automatically
Γûá Setting default folder appearance
Γûá Customizing the Launchpad
Γûá Creating Multiple Launchpads
Γûá Using the Pickup Functions
Γûá Bringing the Launchpad to the Top Using the Keyboard
Γûá Opening Parent Folder While Closing Child Folder
Γûá Putting Template Buttons on the Launchpad
ΓòÉΓòÉΓòÉ 7.14. Tearing off Launchpad drawer ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Tearoff drawer ΓòÉΓòÉΓòÉ
Launchpad with drawer "torn off."
ΓòÉΓòÉΓòÉ <hidden> Tearoff drawer ΓòÉΓòÉΓòÉ
Warp
You can "tear" off a drawer from the Launchpad and place it where you wish.
Note that the drawer will disappear if the Launchpad is minimized or closed.
1. Open the desired drawer.
2. Drag the drawer to the desired location using either mouse button 1 or
mouse button 2.
3. To retrieve the drawer, just close the drawer as usual.
ΓòÉΓòÉΓòÉ 7.15. Opening the Settings Notebook ΓòÉΓòÉΓòÉ
Warp
A quick method of opening the Settings notebook for an object:
1. Highlight the desired object.
2. Hold the Alt key.
3. Double click on the object with mouse button 1.
Related subject(s):
Γûá Closing the parent folder when opening an object.
Γûá Opening a windowed command line in the background
ΓòÉΓòÉΓòÉ 7.16. Closing the parent folder when opening an object. ΓòÉΓòÉΓòÉ
Warp
You can automatically close the parent folder when opening an object:
1. Highlight the desired object.
2. Hold the Shift key.
3. Double click on the desired object with mouse button 1.
Related subject(s):
Γûá Opening the Settings notebook
Γûá Opening a windowed command line in the background
Γûá Closing parent folders automatically
ΓòÉΓòÉΓòÉ 7.17. Removing the Launchpad permanently ΓòÉΓòÉΓòÉ
Warp
To remove the Launchpad permanently from your system, drag the Launchpad object
to your Shredder. Then, remove the word LAUNCHPAD from the SET AUTOSTART line
in your CONFIG.SYS file.
Related subject(s):
Γûá Recovering a deleted Launchpad
ΓòÉΓòÉΓòÉ 7.18. Editing animated folder icons ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Animation icon ΓòÉΓòÉΓòÉ
Warp
To edit the animated folder icon:
1. Open the Settings notebook for the desired folder.
2. Click on the General tab.
3. Click on the right arrow in the lower right corner of the page.
4. Edit and save icon as usual, or change icon as usual.
ΓòÉΓòÉΓòÉ <hidden> Animation icon page ΓòÉΓòÉΓòÉ
Animation icon page of Settings notebook.
ΓòÉΓòÉΓòÉ 7.19. Bringing the Launchpad to the top ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
You might know that double-clicking with mouse button 1 on the OS/2 desktop
will open the Launchpad, but double-clicking on the desktop is also useful for
raising the Launchpad to the top if it is covered by other windows.
Related subject(s):
Γûá Bringing the Launchpad to the Top Using the Keyboard
ΓòÉΓòÉΓòÉ 7.20. Closing parent folders automatically ΓòÉΓòÉΓòÉ
Warp
You can set all or some parent folders to close automatically when opening a
subfolder or all objects.
To set parent folders to close automatically system-wide:
1. Open the System object. It should be located in the System Setup
folder.
2. Click on the Window tab.
3. Click once on the right arrow in the lower right hand corner of the
page.
4. Under "Folder Automatic Close," choose either "Subfolders only" or
"All Objects."
Individual folders' automatic closure settings can be changed in the same
manner through their individual Settings notebooks.
Related subject(s):
Γûá Closing the parent folder when opening an object
ΓòÉΓòÉΓòÉ 7.21. Setting default folder appearance ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Default appearance page ΓòÉΓòÉΓòÉ
Page for setting default folder appearance.
ΓòÉΓòÉΓòÉ <hidden> Default appearance page ΓòÉΓòÉΓòÉ
Warp
You can determine whether the folders on your system will default to icon,
tree, or details view:
1. Open the System object. It should be located in the System Setup
folder.
2. Click on the Window tab.
3. Click twice on the right arrow in the lower right hand corner of the
page. You should be on page 3 of the Window tab.
4. Select Icon, Tree, or Details.
5. Close the System object.
ΓòÉΓòÉΓòÉ 7.22. Customizing the Launchpad ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Launchpad options ΓòÉΓòÉΓòÉ
Warp
The Launchpad can be customized to your taste.:
1. Click on an open area (no buttons) of the Launchpad with mouse button
2 to bring up its popup menu.
2. Choose Settings to open the Settings notebook.
3. Pages 1 and 2 of the Options tab contain several different options
which change the appearance of the Launchpad. Choose the options you
desire.
4. Close the Settings notebook.
ΓòÉΓòÉΓòÉ <hidden> Launchpad options ΓòÉΓòÉΓòÉ
Second page of Launchpad options.
ΓòÉΓòÉΓòÉ 7.23. Creating Multiple Launchpads ΓòÉΓòÉΓòÉ
contributed by Simon C. Pol
Warp
You can create multiple Launchpads for better organization of your desktop. To
create additional Launchpads:
1. Click on the background of the Launchpad (i.e., not on the buttons)
with mouse button 2 to bring up the popup menu.
2. Choose Copy from the popup menu.
3. Copy the new Launchpad to the Desktop.
4. Rename the new Launchpad to a name other than "LaunchPad"
5. You now have an additional Launchpad that is ready for customization.
Related subject(s):
Γûá Customizing the Launchpad
ΓòÉΓòÉΓòÉ 7.24. Using the Pickup Functions ΓòÉΓòÉΓòÉ
contributed by Martin Lafaix
Warp
For those who might have trouble dragging objects with a mouse, OS/2 Warp
offers the "Pickup" option, which will "pickup" and "hold" an object until it
is dropped without having to hold the mouse button down while moving the mouse.
To Pickup an object, hold the Alt key and click on the desired object with
mouse button 2.
After you've picked up the object, you can do one of three things with it:
1. Copy the object - hold the Ctrl key and click with mouse button 2 on
the location to which you want to copy the object
2. Move the object - hold the Shift key and click with mouse button 2 on
the location to which you want to move the object
3. Create a shadow of the object - hold both the Ctrl and Shift keys and
click with mouse button 2 on the location on which you wish to create
the shadow
ΓòÉΓòÉΓòÉ 7.25. Bringing the Launchpad to the Top Using the Keyboard ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
To raise the Launchpad to the top in any folder, including the Workplace Shell
itself:
1. Deselect all objects in the folder by pressing the Ctrl and backslash
(\) keys.
2. Press the Enter key.
Related subject(s):
Γûá Bringing the Launchpad to the top
ΓòÉΓòÉΓòÉ 7.26. Opening Parent Folder While Closing Child Folder ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Opening Parent Folder ΓòÉΓòÉΓòÉ
contributed by Martin S. Hanoian and Martin Lafaix
Warp
To close a child folder while opening its parent folder, hold the Shift key
while choosing the "Open parent" option in the folder's menu.
ΓòÉΓòÉΓòÉ <hidden> Open parent option on menu ΓòÉΓòÉΓòÉ
Choosing the Open parent option on the folder menu
ΓòÉΓòÉΓòÉ 7.27. Putting Template Buttons on the Launchpad ΓòÉΓòÉΓòÉ
contributed by Robert I. Petersen
Warp
If you use a template frequently, it can be useful to have a template button on
the Launchpad. Unfortunately, when you try to drag a template to the
Launchpad, it becomes an object. The solution is to use the "Pickup" option to
place the template onto the Launchpad.
Related subject(s):
Γûá Using the Pickup Functions
ΓòÉΓòÉΓòÉ 7.28. Preventing Save of Desktop Settings Between Shutdowns ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> Don't save desktop ΓòÉΓòÉΓòÉ
Save Desktop Settings page.
ΓòÉΓòÉΓòÉ <hidden> Don't save desktop ΓòÉΓòÉΓòÉ
Warp
To prevent desktop settings from being saved at shutdown in OS/2 Warp:
1. Open the Settings notebook for the desktop.
2. Choose the Desktop tab.
3. Uncheck the "Save Desktop Settings" box.
ΓòÉΓòÉΓòÉ 7.29. Command Line ΓòÉΓòÉΓòÉ
This section covers Command Line tips for OS/2 Warp.
Topics in this section:
Γûá Obtaining information about your hardware
Γûá Setting video modes
Γûá Viewing HLP Files Without Opening the Application
ΓòÉΓòÉΓòÉ 7.30. Obtaining information about your hardware ΓòÉΓòÉΓòÉ
Warp
To obtain extensive information about your hardware, use the RMVIEW command at
an OS/2 command prompt.
RMVIEW /?
will provide a list of the different command line switches which can be used
with RMVIEW.
ΓòÉΓòÉΓòÉ 7.31. Setting video modes in a command line window ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
In previous versions of OS/2, you could not specify non-standard column and row
sizes in windowed command lines. In OS/2 Warp, non-standard sizes can be
specified. Just use the OS/2 MODE command:
MODE <columns>,<rows>
where <columns> is the number of columns and <rows> is the number of rows
Related subject(s):
Γûá Creating a scroll buffer
Γûá Resizing a command line window permanently
ΓòÉΓòÉΓòÉ 7.32. Viewing HLP Files Without Opening the Application ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
To view a help file (*.HLP) without having to open the application, use the
following command at a command prompt (you must have the Internet support
installed):
VIEWHELP <filename>
where
<filename> is an OS/2 help file that ends with the *.HLP extension.
Note: Typing VIEWHELP without parameters will give you a list of the available
options for the command.
ΓòÉΓòÉΓòÉ 7.33. BonusPak ΓòÉΓòÉΓòÉ
This section covers BonusPak tips for OS/2 Warp.
Topics in this section:
Γûá Command Line Options for the WebExplorer
Γûá Pulling Down Menus in WebExplorer Presentation Mode
Γûá Using Different INI Files with the WebExplorer
Γûá Adding Fastkeys to the WebExplorer Quick List
Γûá Setting the Size of the WebExplorer
ΓòÉΓòÉΓòÉ 7.34. Command Line Options for the WebExplorer ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
To increase the number of threads used by the WebExplorer (up to a maximum of
8), add the following into the Parameters box of the WebExplorer's Settings
notebook:
-t <threads>
where
<threads> is the number of threads desired
To prevent the WebExplorer from asking for confirmation when it is closed, add:
-q
to the Parameters box of the WebExplorer's Settings notebook.
ΓòÉΓòÉΓòÉ 7.35. Pulling Down Menus in WebExplorer Presentation Mode ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
To access the pull-down menus when using the WebExplorer's Presentation Mode,
tap the Alt key and use the arrow keys to pull down and move between menus.
ΓòÉΓòÉΓòÉ 7.36. Using Different INI Files with the WebExplorer ΓòÉΓòÉΓòÉ
contributed by Doug Heintzman
Warp
To avoid bulding up long and unmanageable quick lists in the WebExplorer,
create multiple WebExplorer icons and have them call different INI files by
adding the following to the Parameters box of the WebExplorer's Settings
notebook:
-i <drive>:\tcpip\etc\<filename>.ini
where
<drive> is the drive
<filename> is the name of the INI file you wish to use
The first time you open the new WebExplorer object(s), you will receive a
message that the INI file doesn't exist and and new one will be created.
ΓòÉΓòÉΓòÉ 7.37. Adding Fastkeys to the WebExplorer Quick List ΓòÉΓòÉΓòÉ
contributed by Jack Tan
Warp
To add Fastkey access to the items on your WebExplorer QuickList:
1. Click on the QuickList button to open the QuickList Document List box.
2. Highlight the entry to which you would like to add the Fastkey.
3. Click on the Edit button.
4. Place a tilde (~) in front of the letter that you would like to use as
the Fastkey.
5. Close the QuickList Document List box.
6. The Fastkey will show up as underlined when you use the QuickList
pulldown menu.
ΓòÉΓòÉΓòÉ 7.38. Setting the Size of the WebExplorer ΓòÉΓòÉΓòÉ
contributed by Christopher Hayashida
Warp
You can customize the size of the WebExplorer on your screen:
1. Edit the file \TCPIP\ETC\EXPLORE.INI.
2. To set the leftmost edge, add
xleft=<pixels>
where
<pixels> is the number of pixels from the left side of the screen.
3. To set the bottom edge, add
xbottom=<pixels>
where
<pixels> is the number of pixels from the bottom of the screen.
4. To set the width, add
width=<pixels>
where
<pixels> is the number of pixels wide.
5. To set the height, add
height=<pixels>
where
<pixels> is the number of pixels high.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* A "poor-man's" CD player for OS/2 using REXX */
/* Xavier Caballe - December 1993 */
/* Initialize MCIAPI */
call RxFuncAdd 'mciRxInit', 'MCIAPI', 'mciRxInit';
call mciRxInit;
/* Initialize variables */
A = 0;
P = 0;
/* Open a CD for subsequent manipulation */
Ordre = 'open cdaudio01 alias cederom wait';
call Executa;
say '';
/* Get the number of tracks on the disk */
Ordre = 'status cederom number of tracks wait';
call Executa;
say 'Songs on the CD disk:' RetStr;
Cancons = RetStr;
/* Get the beginning of each track */
do until A = Cancons
A = A + 1;
Ordre = 'status cederom position track 'A' wait';
call Executa;
say 'The track number 'A' begins at:' RetStr;
P.A = RetStr;
end;
/* Get the last track */
Ordre = 'status cederom length wait';
call Executa;
say 'Last track on the CD disk:' RetStr;
UltimaPista = RetStr;
/* Data input */
Repetir:
say '';
say 'Which song do you wish? ';
pull Numero;
NumeroPlus1 = Numero + 1;
CanconsPlus1 = Cancons + 1;
P.CanconsPlus1 = UltimaPista;
if Numero < 1 | Numero > Cancons then do;
say 'Wrong answer.';
Signal Repetir;
end;
/* Play the selected song */
Ordre = 'play cederom from 'P.Numero' to 'P.NumeroPlus1' wait';
call Executa;
/* That's all, folks! */
Ordre = 'close cederom';
call Executa;
call mciRxExit;
exit;
/* Send a MCI command string to MMPM/2 */
Executa:
rc = mciRxSendString(Ordre, 'RetStr', '0', '0');
if (rc <> 0) then do
say "Error No = " Ordre;
say 'Code No. = ' rc;
GetErr = mciRxGetErrorString(rc, 'ErrStVar');
say 'Message =' ErrStVar;
end;
return
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* OPEN.CMD - opens a folder */
call RxFuncAdd "SysSetObjectData", "RexxUtil", "SysSetObjectData"
folderpath="<drive>:\<path>"
call SysSetObjectData folderpath, "OPEN=DEFAULT";
exit
/* where <drive> is the letter of the drive on which the subdirectory
corresponding to the folder is located
<path> is the path to the subdirectory corresponding to the folder */
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* BITMAP.CMD: change the desktop bitmap at regular intervals
Syntax: BITMAP.CMD <interval in seconds> [/?]
Copyright 1994 Jack Tan
*/
/* Check the interval value */
arg interval
if interval=="" | WORDPOS("/?", interval)<>0 then do
SAY
SAY " BITMAP.CMD: randomly change the desktop bitmap at",
"periodic intervals"
SAY " Syntax: BITMAP.CMD <interval in seconds> [/?]"
SAY " <interval> is the interval between bitmap changes,",
"in seconds"
exit 1
end /* Do */
else if DATATYPE(interval, "Whole Number")<>1 then
call badNumber interval
else if interval<=0 then
call badNumber interval
/* Prepare for the changes */
signal on halt name exitProgram
BootDrive = VALUE("BOOTDRIVE", , "OS2ENVIRONMENT")
BitmapSpec = BootDrive || "\OS2\BITMAP\*.BMP"
call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
call SysLoadFuncs
SAY "BITMAP.CMD: Hit Ctrl+Break to exit"
/* Execute the change */
do forever
call SysFileTree BitmapSpec, "bitmaps", "FO"
if bitmaps.0>0 then do
i = RANDOM(1, bitmaps.0)
call SysSetObjectData "<WP_DESKTOP>", "BACKGROUND="bitmaps.i";"
end /* Do */
call SysSleep interval
end /* Do */
exitProgram:
SAY " Successfully exited"
exit 0
badNumber: procedure
SAY "Bad interval value '"ARG(1)"'"
exit 2
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* SetPtr.CMD -- set/remove a custom mouse pointer.
Copyright 11 January 1994 by Jack Tan
This is based on Dann Lunsford's SETMOUSE.CMD
SETMOUSE.CMD by Dann Lunsford
Short procedure to set mouse pointer to contents of specified .PTR file
This file is in the public domain, but I'd appreciate it greatly if you
would leave this notice in... Author: Dann Lunsford
Vortex BBS (1:203/726)
13-Aug-1993
Be careful about adding/removing lines to this script -- it uses the
SOURCELINE function, which is source-dependent.
Syntax: SetPtr.CMD <filename> [pointer index] [/X] [/L] [/?]
<filename> is the name of the file containing the pointer.
If <filename> does not exist, <filename>.PTR is searched.
[pointer index] is an optional parameter. It defaults to 1.
Index Pointer Default OS/2 icon
------------------------------------------------------------------
1 normal OS/2 pointer arrow
2 text insertion I-beam
3 wait cursor clock
4 size pointer (no icon)
5 move pointer four-way arrow
6 resize (NW to SE) diagonal double arrow (\)
7 resize (NE to SW) diagonal double arrow (/)
8 resize (horizontal) horizontal double arrow (-)
9 resize (vertical) vertical double arrow (|)
/X (optional) indicates that the custom pointer should be removed.
/L (optional) lists currently installed pointers.
/? (optional) displays this help.
*/
/* Get arguments */
PARSE ARG arguments
bigArgs = TRANSLATE(arguments)
/* Show help */
if arguments=='' | WORDPOS("/?", arguments)<>0 then do
do i=12 to 33
SAY SOURCELINE(i)
end /* do */
EXIT(1)
end /* Do */
/* Setup the REXX function */
call RxFuncAdd 'SysIni', 'RexxUtil', 'SysIni'
Inifile = 'User'
App = 'PM_SysPointer'
/* Show current pointers */
if WORDPOS('/L', bigArgs)<>0 then do
result = SysIni(Inifile, App, 'All:', 'list')
if list.0<1 then
SAY "No custom pointers have been set."
else do
SAY "Current custom pointers:"
do i=1 to 9
result = SysIni(Inifile, App, i)
if result<>"ERROR:" then
SAY " ("i")" LEFT(pointerDesc(i), 20),
SUBSTR(result, 5, LENGTH(result)-5)
end /* Do */
end /* Do */
EXIT(0)
end /* Do */
/* Look for a '/X' */
xPos = WORDPOS('/X', bigArgs)
if xPos<>0 then do
removePtr = 1
arguments = DELWORD(arguments, xPos, 1)
end /* Do */
else
removePtr = 0
/* Look for a pointer index */
pointerIndex = 1
if WORDS(arguments)>1 | removePtr then do
/* Last argument should be the pointer index, since any '/X'
has already been removed. If the last argument does not fit
the requirements for a pointer index, assume that it is part
of the filename.
*/
guessIndex = WORD(arguments, WORDS(arguments))
if LENGTH(guessIndex)==1 & VERIFY(guessIndex, '123456789')==0 then do
arguments = DELWORD(arguments, WORDS(arguments))
pointerIndex = guessIndex
end /* Do */
end /* Do */
/* Set the filename */
if removePtr<>1 then do
arguments = STRIP(arguments)
if SUBSTR(arguments, 1, 1)=='"' then
arguments = DELSTR(arguments, 1, 1)
if SUBSTR(arguments, LENGTH(arguments))=='"' then
arguments = DELSTR(arguments, LENGTH(arguments))
filename = STREAM(arguments, 'Command', 'Query Exists')
if filename=='' then do
/* Try again use .PTR extension */
filename = STREAM(arguments".PTR", 'Command', 'Query Exists')
if filename=='' then do
SAY "Cannot find file: '"arguments"'"
EXIT(3)
end /* Do */
end /* Do */
end /* Do */
/* Execute the change */
if removePtr then
result = SysIni(Inifile, App, pointerIndex, 'DELETE:')
else do
Keyvalue = x2c('01000000')||filename||x2c('00')
result = SysIni(Inifile, App, pointerIndex, Keyvalue)
end /* Do */
/* If the change failed... */
if result<>"" then do
returnCode = 3
if removePtr then
SAY "Unable to delete the pointer"
else
SAY "Unable to set the pointer"
end /* Do */
/* ... else print 'successful' message */
else do
returnCode = 0
if removePtr then
SAY "Pointer successfully removed"
else
SAY "The new pointer will become effective at the next system boot."
end /* Do */
/* Give some more information */
if removePtr<>1 then
SAY " File = "filename
SAY " Pointer = "pointerDesc(pointerIndex) "("pointerIndex")"
EXIT(returnCode)
pointerDesc: procedure
return STRIP(SUBSTR(SOURCELINE(20+ARG(1)), 15, 30))
/* End of REXX script */
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* shredder.cmd - REXX script to recreate the Shredder */
call RxFuncAdd "SysCreateObject", "RexxUtil", "SysCreateObject"
class="WPShredder"
title="Shredder"
location="<WP_DESKTOP>"
settings="OBJECTID=<WP_SHRED>;"
settings=settings||"ICONPOS=90 8;"
call SysCreateObject class, title, location, settings, "REPLACE"
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* This procedure will change the long name of */
/* a file without changing the actual file name. */
/* Usage: */
/* PUTLONG myfil.ext "Long File Name" */
/* Written by Bill Parrill */
/* bparrill@vnet.ibm.com */
call RxFuncAdd 'SysPutEA', 'RexxUtil', 'SysPutEA'
parse arg FileName '"'LongName'"'
if FileName = '' then DO
say 'Please specify a file name!'
exit 1
end /* Do */
if LongName = '' then DO
say 'Please specify a long name!'
exit 2
end /* Do */
say 'File Name: 'FileName
say 'Long Name: 'LongName
RetCode = SysPutEA(FileName, '.LONGNAME',,
'FDFF'x||D2C(LENGTH(LongName))||'00'x||LongName)
say 'Return Code: 'RetCode
EXIT
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* program.cmd */
Call RxFuncAdd 'SysLoadFuncs','RexxUtil','SysLoadFuncs'
Call SysLoadFuncs
Parse Arg FileName Title
slash=lastpos("\",FileName);
if slash=3 then slash=4
Startup=left(filename,slash-1)
rc=SysCreateObject("WPProgram",,
Title,,
"<WP_DESKTOP>",,
"EXENAME="FileName";STARTUPDIR="Startup)
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* setfont.cmd */
/* Usage: SETFONT <font size/type> */
/* where <font size/type> is the */
/* point size and font desired in the */
/* format size.type (e.g., 8.Helv) */
call RxFuncAdd "SysIni", "RexxUtil", "SysIni"
parse arg Font
IniFile = "USER"
AppName = "PM_SystemFonts"
KeyName = "DefaultFont"
call SysIni IniFile, AppName, KeyName, Font||x2c(0)
say Result
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* large.cmd - increase cursor size */
/* If you want to return to the standard */
/* mouse cursor, change '1' to '2' in */
/* the "val" variable. */
call RxFuncAdd "SysIni", "RexxUtil", "SysIni"
inifile='USER'
app='PM_IBMVGA'
key='CURSOR_SIZE'
val='1'
call SysIni inifile, app, key, val
say Result
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* OpenPar.cmd 4 January 1993
* REXX script to open parent folder from a folder's menu in OS/2 2.x
* Written by Brian B. Mathewson bbm@r2d2.eeap.cwru.edu
*/
Arg drivedir
parent=filespec(drive,drivedir)filespec(path,drivedir)
parent=left(parent,length(parent)-1)
Call RxFuncAdd 'SysSetObjectData', 'RexxUtil', 'SysSetObjectData'
Call SysSetObjectData parent, 'OPEN=DEFAULT' /* opens parent folder */
Call SysSetObjectData parent, 'OPEN=DEFAULT' /* brings it to foreground */
Exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* CHKDRIVE.CMD - check drive status */
'@echo off'
parse arg drive_letter;
drive_letter=delstr(drive_letter,2);
if drive_letter=' ' then do
say "CHKDRIVE.CMD - check status of drive"
say "USAGE: CHKDRIVE.CMD <drive>"
say "where <drive> is the letter of drive you wish to check"
exit
end
else
signal ON NOTREADY name NOT_READY
call STREAM drive_letter || ':*', 'D'
say "Drive Ready"
exit
NOT_READY:
say "Drive Not Ready"
return
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* REXX script to shutdown the PC in 5 minutes
Author: David Matocha david.matocha@yob.sccsi.com
If you make any improvements, please send me a copy.
Version 930316.6 */
say ' '
say 'Please close all running applications.'
say ' '
say 'WARNING: The Computer will shutdown in 5 minutes!'
beep(500, 1000);
CALL SysSleep 14;
beep(475, 1000);
CALL SysSleep 14;
beep(450, 1000);
CALL SysSleep 14;
beep(425, 1000);
CALL SysSleep 14;
say ' '
say 'WARNING: The Computer will shutdown in 4 minutes!'
beep(400, 1000);
CALL SysSleep 14;
beep(375, 1000);
CALL SysSleep 14;
beep(350, 1000);
CALL SysSleep 14;
beep(325, 1000);
CALL SysSleep 14;
say ' '
say 'WARNING: The Computer will shutdown in 3 minutes!'
beep(300, 1000);
CALL SysSleep 14;
beep(275, 1000);
CALL SysSleep 14;
beep(250, 1000);
CALL SysSleep 14;
beep(225, 1000);
CALL SysSleep 14;
say ' '
say 'WARNING: The Computer will shutdown in 2 minutes!'
beep(200, 1000);
CALL SysSleep 14;
beep(175, 1000);
CALL SysSleep 14;
beep(150, 1000);
CALL SysSleep 14;
beep(125, 1000);
CALL SysSleep 14;
say ' '
say 'WARNING: The Computer will shutdown in 1 minute!'
beep(100, 1000);
CALL SysSleep 14;
beep(500, 1000);
CALL SysSleep 14;
beep(1000, 1000);
CALL SysSleep 14;
beep(1500, 1000);
CALL SysSleep 14;
'setboot /T:NO'
'setboot /B'
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* sleep.cmd - make system sleep for specified # of seconds */
/* syntax: sleep <time>, where <time> is time in seconds */
call RxFuncAdd "SysSleep", "RexxUtil", "SysSleep"
parse arg sleeptime;
sleeptime=strip(sleeptime)
if sleeptime= '' then do
say "SLEEP.CMD - make system sleep for specified # of seconds"
say "Usage: sleep <time>"
say " where <time> is time in seconds"
exit
end
else
call SysSleep sleeptime
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* eval by L Kuru 25.11.1993 */
arg params;
interpret say params;
exit
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
/* Start a DOS session with the maximum free memory */
/* Xavier Caballe - December 1993 */
/* code added to make DOS session open in foreground */
/* M.Woo - 6 Jan 94 */
CALL RxFuncAdd SysLoadFuncs, RexxUtil,SysLoadFuncs;
CALL SysLoadFuncs;
ClassName='WPProgram'; /* Object type */
Title='Big DOS'; /* Window title */
Program='EXENAME=*;'; /* Program to run */
Location='<WP_NOWHERE>'; /* Object location */
Type='PROGTYPE=VDM;'; /* DOS full screen session */
StartUp='STARTUPDIR=C:\;' /* Working directory */
Objectid='OBJECTID=<BIGDOS>;' /* Object ID */
/* Session Settings */
/* The Video_Mode_Restriction value *MUST BE* fifteen characters long */
Settings='SET VIDEO_MODE_RESTRICTION=CGA ;'
Settings=Settings||'SET DOS_UMB=1;'
Settings=Settings||'SET DOS_HIGH=1;'
Open='OPEN=DEFAULT;' /* Open default view */
call SysCreateObject classname, title, location,,
program||type||startup||objectid||settings||open, 'REPLACE'
call SysSetObjectData '<BIGDOS>', open
Return