OS/2 Professional/OS2PRO194.ISO/os2/info/faq/os2_21/tricks/tricks.inf

OS/2 Help File | 1993-11-16 | 99.8 KB | 1,120 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ

Stupid OS/2 Tricks

(Double click on a bitmap)

compiled by M. Woo
for the Champaign-Urbana OS/2 Users Group
release #1, Nov 1993

Information about this document:

o Types of "tricks" included
o How to submit tips and tricks
o Revisions
o Revision schedule
o How this document was created
o Disclaimer


ΓòÉΓòÉΓòÉ 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.

Related subject(s):

o How to submit tips and tricks


ΓòÉΓòÉΓòÉ 1.2. 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, [e-mail]
Fidonet, Sysop @ 1:233/4.0

(these addresses are subject to change after Jan 1993)


ΓòÉΓòÉΓòÉ 1.3. 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):

o Revision schedule


ΓòÉΓòÉΓòÉ 1.4. Revision schedule ΓòÉΓòÉΓòÉ

This text will be updated when the number of new tips and tricks gathered
warrants a new version.

History:

Release #1 - Nov 1993

Related subject(s):

o Revision marking


ΓòÉΓòÉΓòÉ 1.5. How this document was created ΓòÉΓòÉΓòÉ

This document was written using the OS/2 port of Elvis v1.6.  Screen captures
were done using PMCamera/2 v2.10, an IBM EWS package, then processed using
JoeView v1.21.  The resulting tagged document was compiled using the IPF
compiler from the IBM OS/2 Developer's Toolkit v2.0.


ΓòÉΓòÉΓòÉ 1.6. 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:

o Keeping applications from restarting at boot
o Shutting down without a mouse
o Rebooting from the command line
o Finding settings for original objects
o Controlling order of execution in Startup folder
o Backing up the *.ini files
o Removing device drivers for better performance
o Speeding up some IDE drives
o Disabling use of the floppy drives


ΓòÉΓòÉΓòÉ 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):

o Prevent restarting manually
o Prevent restarting automatically
o 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):

o 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.

Related subject(s):

o 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

or

SETBOOT /IBD:<drive>

where <drive> is the letter of the drive or partition to which you wish to boot

Related subject(s):

o Keeping applications from restarting at boot


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 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


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 3. Desktop ΓòÉΓòÉΓòÉ

This section covers tips and tricks which relate to the Workplace Shell.

Topics in this section:

o Saving desktop without shutting down
o Adding an "open folder" entry to the desktop's popup menu
o Changing color of shadow icon text
o Moving icon a small distance
o Changing desktop bitmaps randomly at specified interval
o Changing the standard mouse pointer
o Making an object prompt for a parameter
o Finding a "covered" icon
o Changing icon text color
o Recovering after an accidental Arrange
o Creating an onscreen "app bar"
o Creating a "trash can"
o Selecting objects without mouse
o Hiding a folder
o Creating a system file editor object


ΓòÉΓòÉΓòÉ 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):

o 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.

Other REXX scripts:

o BITMAP.CMD
o SETMOUSE.CMD
o SETFONT.CMD
o CHKDRIVE.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):

o 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.

Note that the location of the bitmap subdirectory is hard-coded into the script
in line 14.  You will need to alter the path before running BITMAP.CMD if you
are running OS/2 from a drive other than C: and/or are not running OS/2 v2.1.

Other REXX scripts:

o OPEN.CMD
o SETMOUSE.CMD
o SETFONT.CMD
o CHKDRIVE.CMD


ΓòÉΓòÉΓòÉ 3.6. Changing the standard mouse pointer ΓòÉΓòÉΓòÉ

You can replace the standard mouse pointer with one of your own creations.

(by Dann Lunsford)

 1. Use the Icon Editor to create a mouse pointer file with the extension
    *.PTR.
 2. Create the REXX script, SETMOUSE.CMD.
 3. Invoke SETMOUSE.CMD as follows:

    SETMOUSE.CMD <drive>:\<path>\<filename>.PTR

    where

       <drive> is the drive on which the *.PTR file resides

       <path> is the path on which the *.PTR file resides

       <filename> is the name of the new mouse pointer file

Other REXX scripts:

o OPEN.CMD
o BITMAP.CMD
o SETFONT.CMD
o CHKDRIVE.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):

o 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):

o 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 you 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.


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 4. Presentation Manager ΓòÉΓòÉΓòÉ

This section covers tips and tricks which affect Presentation Manager.

Topics in this section:

o Making fonts extremely small
o Starting PM programs minimized
o Changing the default PM system font
o Moving a window in the background
o Closing several windows at once


ΓòÉΓòÉΓòÉ 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):

o 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")

Related subject(s):

o Making fonts extremely small
o OPEN.CMD
o BITMAP.CMD
o SETMOUSE.CMD
o CHKDRIVE.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.


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 5. Command Line ΓòÉΓòÉΓòÉ

This section covers tips and tricks which affect command line sessions.

Topics in this section:

o Pasting text without the final carriage return
o Clearing the Delete subdirectory
o Searching for file names
o Maximizing windows when opening
o Creating a scroll buffer
o Using OS/2 without the Workplace Shell
o Enhancing speed of text scrolling
o Adding entries to your PATH
o Permanently deleting a file when Undelete is active
o Suppressing echo from *.CMD files
o Getting more out of your command line
o Checking drive status


ΓòÉΓòÉΓòÉ 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):

o 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.

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.


ΓòÉΓòÉΓòÉ <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


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ 5.7. Enhancing speed of text scrolling ΓòÉΓòÉΓòÉ

Tricks for speeding up text display.

Related subject(s):

o Changing font size
o 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):

o 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 only runs if and only if both If.EXE and Then.EXE run)

 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:

o OPEN.CMD
o BITMAP.CMD
o SETMOUSE.CMD
o SETFONT.CMD


ΓòÉΓòÉΓòÉ 6. Win-OS/2 ΓòÉΓòÉΓòÉ

This section covers tips and tricks which affect Win-OS/2.

Topics in this section:

o Reducing Win-OS/2 initial load time
o Using Windows screen blanker for OS/2
o Running Win-OS/2 from a DOS image


ΓòÉΓòÉΓòÉ 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.


ΓòÉΓòÉΓòÉ <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 desktop background randomly */
call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
call SysLoadFuncs
parse arg changetime;
changetime=strip(changetime)
if changetime=' ' then do
        say "BITMAP.CMD--change bitmaps randomly at a specified interval"
        say ""
        say "USAGE: bitmap <time>"
        say "where <time> is the interval between bitmap changes in seconds"
        exit
        end
else
call SysFileTree "C:\OS2\BITMAP\*.*", "bitmaps.", "O"
do forever
        call SysSleep changetime
        i = random(1,bitmaps.0)
        call SysSetObjectData "<WP_DESKTOP>", "BACKGROUND="bitmaps.i";"
end
exit


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

/* 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                  */
/* invoke from a commandline with the name of your custom pointer file as  */
/* the argument.                                                           */
arg ptr_file_name
if ptr_fiie_name == '' then
   do
      say "Usage: setmouse complete_pointer_file_pathname"
      exit
   end
file = stream(ptr_file_name,'C','query exists')
if fiie == '' then
   do
      say "Specified file is not accessible."
      exit
   end
/* load REXX utility library */
call RxFuncAdd 'SysLoadFuncs','REXXUTIL','SysLoadFuncs'
call SysLoadFuncs
/* now do the deed */
val = x2c('01000000')||file||x2c('00')
res = SysIni('USER','PM_SysPointer','1',val)
if res \= '' then
   do
      say "Error while setting PM_SysPointer"
      exit
   end
say "Your new pointer will become effective at the next system boot."
exit


ΓòÉΓòÉΓòÉ <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
KeyName = "DefaultFont"
call SysIni "USER","PM_SystemFonts","DefaultFont","Font"||x2c(0)
say Result
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