Nebula 1994 June/NEBULA_SE.ISO/Documents/FAQ/OS2-faq/user/part4

Text File | 1993-08-28 | 48.9 KB | 1,188 lines

Newsgroups: comp.os.os2.misc,comp.os.os2.apps,news.answers,comp.answers
Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!usc!howland.reston.ans.net!vixen.cso.uiuc.edu!uchinews!kimbark!sip1
From: [e-mail] (Timothy F. Sipples)
Subject: OS/2 Frequently Asked Questions List Rel. 2.1C (4 of 4)
Message-ID: <[e-mail]>
Followup-To: comp.os.os2.misc
Sender: [e-mail] (News System)
Supersedes: <[e-mail]>
Reply-To: [e-mail]
Organization: Dept. of Econ., Univ. of Chicago
Date: Sat, 28 Aug 1993 04:16:26 GMT
Approved: [e-mail]
Expires: Fri, 15 Oct 1993 23:59:59 GMT
Lines: 1171
Xref: senator-bedfellow.mit.edu comp.os.os2.misc:74983 comp.os.os2.apps:20746 news.answers:11857 comp.answers:1779

Archive-name: os2-faq/user/part4
Version: 2.1C

[Part 4 of 4]


                OS/2 LAN Server 2.0 Entry ..: _   CSD Level: ________
                OS/2 LAN Server 2.0 Advanced: _   CSD Level: ________
                OS/2 LAN Server 3.0 Entry ..: _   CSD Level: ________
                OS/2 LAN Server 3.0 Advanced: _   CSD Level: ________

LAN REQUESTER:
                LAN Server 3.0 Requester....: _   CSD Level: ________
                LAN Server 2.0 Requester....: _   CSD Level: ________
                OS/2 1.3 Requester..........: _   CSD Level: ________

  DOS LAN REQUESTER:
                  LS 3.0 Requester ...........: _   CSD Level: ________
                  LS 2.0 Requester ...........: _   CSD Level: ________
                  OS/2 1.3 Requester .........: _   CSD Level: ________
                  DOS Version: ____  DOS Vendor: _________________

Is the failing system a Domain Controller?  Y _    N _
Is the failing system an additional server? Y _    N _

DATABASE MANAGER - If this is an OS/2 DATABASE MANAGER problem, please enter
information about the DataBase Manager problem below.

SQL Error Code ....: ________
Secondary Return Code: ________
Error occurs when database is being accessed as:
Stand Alone ......: Y _  N _
Requester (Client): Y _  N _
Database Server ..: Y _  N _
Using RDS ........: Y _  N _
Using LAN ........: Y _  N _
If the error is occurring at a requester, can the problem be recreated
at the server? .....: Y _  N _
Error occurs in which application?
Query Manager.....: _
LI ..............: _  (Command Line Interface)
User Application..: _
If a trap has occurred, provide the SQLABEND results:
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________

PLEASE REVIEW ALL OF THIS PROBLEM REPORT BEFORE SENDING.  When you are
ready to send this OS/2 Problem Report, send the form via CISMAIL
to ---

Base problems   -   Base Support,     76711,610
ES/LS problems  -   ES/LS Support,    76711,611
(ES = IBM Extended Services, LS = IBM LAN Server)

(To send from the Internet use address [e-mail] or
[e-mail], as appropriate.)


  Related information:

  (4.5) Technical Support
  (4.7) Online Services


(4.11) OS/2 BBSes

 What OS/2 BBSes can I dial?

The following BBSes hold large OS/2 libraries:


  Fernwood                 [phone]

  {{ The Bin BBS           [phone] }}

  OS/2 Source BBS          [phone]

  Denver OS/2 BBS          [phone]

  Inside Technologies BBS  [phone]

  OS/2 Woodmeister         [phone]

  {{ Pyramid/2             [phone] }}

  Gateway/2                [phone]

  Bay Area OS/2            [phone]

  OS/2 San Diego           [phone]

  OS/2 Las Vegas           [phone]

  OS/2 Shareware           [phone]

  Greater Chicago Online   [phone]

  OS/2 Exchange BBS        [phone]

  Abaforum (Barcelona)     34-3-589.38.88

  IBM UK                   44-256-336655

  OS/2 UK                  44-454-633197

  IBM Denmark              45-42-88-72-22

  {{ Copenhagen UG BBS     45-48-24-45-80 }}

  OS/2 Norway              47-22-38-09-49

  IBM Norway               47-66-99-94-50

  IBM Germany              049-711-785-7777

  OS/2 Australia           61-2-241-2466

  Soft/2 Shareware         61-8-370-7339
  (Adelaide)


(The monthly Worldwide OS/2 BBS Listing, available from these BBSes, lists
others.)  The IBM PC Company BBS (modem {{ 919-517-0001 }}) has some
shareware/freeware as well, along with CSDs [See (4.6) Corrective Service
Diskettes] and the PS/2 Assistant (an invaluable resource for locating
almost any sort of information on OS/2).  For information on IBM's OS/2 BBS
phone [phone].  IBM Canada maintains several support BBSes:

      [phone]
      [phone]
      [phone]
      [phone]



  Related information:

  (3.2) Shareware and Freeware Sources
  (4.6) Corrective Service Diskettes


(4.12) IBM Telephone Directory

 IBM has so many telephone numbers.  Which do I use?

{{ Here are some of the telephone numbers at IBM that are of particular
importance to OS/2 users.  The list is by no means complete, and future
releases of the OS/2 Frequently Asked Questions List will add more.

o IBM Help Center (800-756-4IBM).  The "800 number for all 800 numbers" in
the United States.  If you're not sure which number to call, start here.
The operator will stay on the line until you're satisfied you've reached
the right party.

o IBM Information Center (800-IBM-3333).  IBM's United States "switchboard"
-- can be used to reach any IBM employee.

o IBM OS/2 Hotline (800-3-IBM-OS2).  Accepts orders for OS/2, certain OS/2
software titles, OS/2 video cassettes, t-shirts, mouse pads, computer
furniture, and other OS/2-related items.  For United States residents.

o IBM OS/2 Technical Support (800-992-4777).  The product support line for
OS/2 in the United States.  Look in the inside front cover of your OS/2
Using the Operating System manual for support information.

o IBM PC Technical Books (800-765-4IBM).  Accepts orders for most IBM
publications from anyone in the United States.

o IBM Personal Systems Software Canada (800-465-1234).  For general
inquiries and orders from Canadian residents for any OS/2-related product.

o IBM Publications Canada (416-474-7000).  Accepts orders for any IBM
publication, including the OS/2 Online Book Collection, shipped to any
Canadian address.

o IBM Publications U.S.  (800-879-2755 opt.  1).  Accepts orders for any
IBM publication shipped to any address in the United States.  }}


  Related information:

  (4.5) Technical Support


(5.0) Using OS/2

 The following questions are addressed in this section:

 (5.1)  I'm a Unix wizard.  How do I make OS/2 resemble Unix?

 (5.2)  I prefer Windows.  How do I make OS/2 2.1 resemble Windows (or
        OS/2 1.3)?

 (5.3)  Sometimes OS/2 2.1 will freeze when I run an application.  What
        do I do?

 (5.4)  How do I start a background process from the OS/2 command line?

 (5.5)  How do I add new Adobe Type Manager Typefaces?

 (5.6)  How do I tweak OS/2 2.1 for maximum performance?

 (5.7)  How do I measure OS/2 performance and memory usage?

 (5.8)  My background bitmap does not display correctly.  What's wrong?

 (5.9)  How do I boot a real version of DOS from within OS/2 2.1?

 (5.10)  Are there any clever tricks that apply to OS/2 2.1?

 (5.11)  How do I use REXX?  What does it do?

 (5.12)  What ANSI escape sequences can be used?


(5.1) Making OS/2 Resemble Unix

 I'm a Unix wizard.  How do I make OS/2 resemble Unix?

A great number of GNU and Unix utilities have been ported to OS/2 native
mode and are available from (3.2) Shareware and Freeware Sources.  A uucp
package, UUPC/Extended, is available via anonymous ftp from {{
ftp.clarkson.edu, }} directory /pub/uupc; mail [e-mail] with questions.

In addition, the Hamilton C Shell is available from Hamilton Labs (phone
508-358-5715 or mail [e-mail]).  The Thompson Toolkit, a
Bourne-like shell, and awk are published by Thompson Automation (phone
206-224-1639).  MKS (phone [phone] or mail [e-mail]) publishes a
number of standard Unix utilities for OS/2.  Hippix (Hippo Software, {{
phone [phone] }}) provides a set of low cost Unix-like command
utilities (such as grep, awk, sh, and vi) along with a POSIX programming
library.  {{ An OS/2 version of lint is available from Gimpel Software
(phone [phone]).  }} For OS/2-specific X Windows server support, IBM
provides an optional package available with its TCP/IP {{ 2.0 }} for OS/2.
The TCP/IP {{ 2.0 }} base package includes a {{ multithreaded news reader
as well.  }}

DOS and Windows based utilities and aids still work fine under OS/2 2.1.


 Related information:

 (3.2) Shareware and Freeware Sources
 (3.8) Networking Products


(5.2) Making OS/2 Resemble Windows

 I prefer Windows.  How do I make OS/2 2.1 resemble Windows (or OS/2 1.3)?

Spend some time with the Workplace Shell first.  Browse the online
Tutorial, Master Help Index, and Start Here facilties.  Consult the
Unofficial Guide to the Workplace Shell, available from (3.2) Shareware and
Freeware Sources.

If you still prefer Windows-like behavior, follow the instructions
beginning on Page 401 in the OS/2 2.1 Using the Operating System manual.

Note that you can run the Win-OS/2 Program Manager "seamlessly" on your
OS/2 desktop, and you can use it to launch DOS, Windows, and OS/2
applications.  Using the Program Manager in this way can make even hard
core Windows users more comfortable.


 Related information:

 (3.2) Shareware and Freeware Sources


(5.3) Recovering from Crashed Sessions

 Sometimes OS/2 2.1 will freeze when I run an application.  What do I do?

Before rebooting with CTRL-ALT-DEL, try CTRL-ESC.  Do not hit additional
keys, do not move the mouse.  Wait up to a minute.  Either the Window List
or an error message should pop up.  You may close the offending application
at that point; allow some time for it to close.  (Try ALT-ESC if you have
disabled CTRL-ESC in that application's DOS Settings.  If you do not get
any response, press CTRL-ESC or ALT-ESC repeatedly until the dialog
appears.)  Note that the Workplace Shell can recycle, independent of
running applications, if it crashes.

If the system is badly disabled, sometimes pressing CTRL-ALT-NUMLOCK twice
will result in a prompt to create a dump diskette.  You may do so (the
online Command Reference describes dump diskettes), or at that point you
may reboot with CTRL-ALT-DEL.

To prevent applications from automatically restarting see (5.10) Clever
Tricks.  To restore the desktop to "factory defaults," use ALT-F1 when OS/2
2.1 starts.  See Appendix C of the OS/2 2.1 Using the Operating System
manual for details.  Note that if you have installed an OS/2 Service Pak
[See (4.6) Corrective Service Diskettes] the ALT-F1 sequence will restore
your desktop to the state it was found in just before installation of the
Service Pak.


 Related information:

 (4.6)  Corrective Service Diskettes
 (5.10) Clever Tricks


(5.4) Starting Background Processes

 How do I start a background process from the OS/2 command line?

Look up the START and DETACH commands in the online Command Reference.

If you wish to start a DOS session with nondefault settings, use a utility
such as STARTD.  If you wish to start an OS/2 session from a DOS session,
try OS2EXEC.  Both (and several others) are available from (3.2) Shareware
and Freeware Sources.


 Related information:

 (3.2) Shareware and Freeware Sources


(5.5) Adobe Type Manager

 How do I add new Adobe Type Manager typefaces?

OS/2 2.1 comes with built-in Adobe Type Manager (ATM) for OS/2 and
Win-OS/2.  A basic set of typefaces (Courier, Helvetica, and Times New
Roman) comes with OS/2 2.1 and is installed (if selected) for use under
both OS/2's and Win-OS/2's ATM.

{{ Each typeface you install under OS/2 and/or Win-OS/2 should come with at
least two separate files with PFB and AFM extensions.  }} To install a
typeface for use under Win-OS/2, use the ATM Control Panel.  The Win-OS/2
ATM Control Panel will then build a PFM file from {{ the AFM file if a PFM
file is not already included.  }} To install a typeface for use with
OS/2-specific applications, select OS/2 System -> System Setup -> Font
Palette -> Edit Font -> Add.

PFM files may converted to AFM files using the PFM2AFM utility, available
from (3.2) Shareware and Freeware Sources.  (However, these converted AFM
files sometimes produce unusual results.)  AFM files for Adobe commercial
typefaces are available via Internet anonymous ftp from
ftp.mv.us.adobe.com; {{ the PFB files are available for purchase from
Adobe.  }} Many public domain typefaces for OS/2's ATM are available from
(3.2) Shareware and Freeware Sources.  Atech Software's (phone
800-786-FONT) AllType and Ares Software's (phone [phone]) FontMonger
convert between TrueType and Adobe Type 1 formats {{ (as does the popular
Fontographer utility).  }}

Typeface files may be shared by OS/2 ATM and Win-OS/2 ATM.  To do so,
install the typefaces using both the Font Palette and Win-OS/2 ATM Control
Panel, specifying the {{ same }} target path each time (most conveniently
\PSFONTS).

Note that IOPL=YES should appear in CONFIG.SYS; the modules WPPWNDRV,
BVHSVGA, and PMATM are marked as requiring I/O privilege.


 Related information

 (3.2) Shareware and Freeware Sources


(5.6) Performance Tuning

 How do I tweak OS/2 2.1 for maximum performance?

For OS/2 overall, the CONFIG.SYS parameters MAXWAIT, TIMESLICE, PRIORITY,
PRIORITY_DISK_IO, PROTECTONLY, and cache settings (in the DISKCACHE line,
for FAT; or IFS line, for HPFS) can be tweaked.  The swap file should be
placed on the most used partition on the least used hard disk, and its
location is controlled by the SWAPPATH line.  See the online Command
Reference for details.

FAT partitions should be periodically defragmented.  A shareware
defragmenter for DOS called DOG (Disk OrGanizer) works well, as do many
others.  (You can boot DOS from a floppy disk to run such a utility.)

For the Workplace Shell, drag shadows of most often used items to the
desktop or to folders closer to the "surface" -- opening folders takes
time.  Drag shadows of program objects you use often (e.g.  the Win-OS/2
full screen Program Manager) to the Startup folder.  Disable animation (go
to OS/2 System -> System Setup -> System -> Window).  Use the faster
Details View when opening drive and folder objects; to set Details View as
the default, open the settings notebook for the object, select the Menu
tab, click on ~Open, then the Settings button, then select the Default
Action.

Try reducing the number of on screen colors or dropping down in screen
resolution to enhance speed.  Close (not just minimize; check the Window
List) unnecessary objects and applications.  Use the Monochrome scheme from
the Scheme Palette -- it provides marginally faster screen updates.
Consider adding more RAM.

For DOS programs, run full screen instead of windowed if speed is
important.  In DOS Settings for each application:  reduce conventional,
XMS, DPMI, and EMS memory allocations to the bare minimums required for
maximum performance; turn off VIDEO_RETRACE_EMULATION unless necessary;
adjust IDLE_SENSITIVITY; turn off DOS_BACKGROUND_EXECUTION if not needed;
change the HW_TIMER setting (particularly for games); enable
VIDEO_FASTPASTE if possible; turn on HW_ROM_TO_RAM.  Communications
programs should use hardware handshaking where possible (use OS/2's MODE
COMx command if necessary), and a buffered UART can prove helpful.  (DOS
programs running under OS/2 will not be aware of a buffered 16550AF UART.
OS/2 virtualizes the serial port and manages the buffer itself.)  For
faster printing set the DOS program's output port to LPTx.OS2 (where x is
the printer port number) -- use a "print to file" option if necessary.
Disable any DOS print spoolers; rely on OS/2's spooler instead.  Increase
CONFIG.SYS's PRINTMONBUFSIZE values.  Other, standard steps to enhance DOS
performance (e.g.  increasing BUFFERS in CONFIG.SYS) of course apply.

For Windows programs, run using a full screen desktop if speed is vital.
The Win-OS/2 Full Screen icon set up by the installation program has poor
Settings.  For better performance perform some of the same steps outlined
in the preceding paragraph, including VIDEO_RETRACE_EMULATION off.  The
same printer output advice also applies.  Consider disabling the Public
setting in the Clipboard.  If available, set VIDEO_8514A_XGA_IOTRAP to off.
If mouse control is lost when switching to/from the Win-OS/2 session, try
setting VIDEO_SWITCH_NOTIFICATION off.


 Related information:

 (1.3) DOS and Windows Compatibility
 (5.7) Measuring Performance and Memory Usage


(5.7) Measuring Performance and Memory Usage

 How do I measure OS/2 performance and memory usage?

OS/2 does not treat system resources like DOS.  Memory is treated as a
virtual resource, used intelligently.  For example, OS/2 will retain
unused, "dormant" code in memory if that memory is not otherwise required,
on the assumption that that code may be used again.  Also, all but a small
portion of OS/2 (and most applications, no matter how many are running) may
be paged to disk should a large amount of physical memory be required.
Utilities which display "free" memory, then, are only useful for rough,
relative measurements.  (Such utilities also often fail for another reason:
many only report the largest contiguous block of free physical RAM.  And a
few will never report more than 16 MB of RAM because they were designed for
OS/2 1.x.)

Similarly, utilities which purport to measure system load (e.g.  Pulse)
should not be relied upon for definitive performance measurement.
Subjective assessments are often much more reliable.  Pulse (and similar
utilities) rely on a measurement of processor time allocated to a thread
running at OS/2's lowest priority.  This method is sometimes subject to
erroneous results.

That said, more rigorous system performance optimization and monitoring
tools include {{ System Performance Monitor/2 (IBM Program No.  5871-3415),
}} BenchTech (Synetik, phone [phone]), {{ OR/SysMon (International
OS/2 User Group, phone [phone] or FAX [phone]), CPU Monitor
(Bon Ami), }} and Performance {{ 2.1 }} (Clear & Simple, phone
203-658-1204).

Note that OS/2's swap file is designed to behave with hysteresis.  It will
not shrink in size as easily as it grows, under the assumption that swap
space needed once may be needed again.  It should shrink given enough time
and continued, less intense system loads.


 Related information:

 (5.6) Performance Tuning


(5.8) Displaying Background Bitmaps

 My background bitmap does not display correctly.  What's wrong?

Color bitmap images used for the Workplace Shell screen or folder
backgrounds may not display correctly (may have distorted or missing
colors) due to incorrect matching with OS/2's default palette.  Unlike
Windows, OS/2 does not adjust the palette to accommodate background bitmaps
(to keep the rest of the desktop from experiencing color distortions).
(Palette control is now available to applications running under the 32-bit
graphics engine with an appropriate display driver, however.)

To remedy the problem you may use the numerous background images which have
been specifically prepared for the Workplace Shell [available from (3.2)
Shareware and Freeware Sources] or you may use an image editing/conversion
utility which can create a proper, {{ system }} palette-matched bitmap
file.  For example, {{ JoeView }} [available from (3.2) Shareware and
Freeware Sources] may be used to import noninterlaced GIF, Windows BMP, and
PCX files and save them as palette-matched OS/2 BMP files.

Note that background bitmap images impose some additional overhead, taking
up RAM and disk resources.  You should probably use them sparingly.  Also,
if you have set a Win-OS/2 background bitmap you may experience desktop
color distortions when running Windows programs "seamlessly."  Disable the
Win-OS/2 background bitmap to remedy the problem.


 Related information:

 (2.2) SuperVGA Support
 (3.2) Shareware and Freeware Sources


(5.9) Specific DOS Sessions

 How do I boot a real version of DOS from within OS/2 2.1?

Booting a real version of DOS under OS/2 provides certain features that the
OS/2 emulated DOS sessions cannot.  For example, a specific DOS session can
provide access to devices (like CD-ROM drives) and networks for which there
are only DOS device drivers.  A specific DOS session can also help get DOS
applications which generate spurious "divide by zero" errors running again.

You will be able to run one such session per hardware device.  So, for
example, if you have your DOS networking software loaded in one specific
DOS session, you may not start another, similar session.

Specific DOS sessions are discussed in the online Command Reference (under
VMDISK), the Master Help Index, and the printed Installation Guide
(Appendix E).  You should consult those resources first.  However, if you
are still unsure how to configure your system to run specific DOS sessions,
follow these steps:

1. Create a bootable DOS diskette.  Insert your DOS system diskette into
Drive A and reboot.  When you arrive at the "A>" prompt, type FORMAT A:  /S
and press ENTER.  (Note that you may wish to format the diskette for the
smallest capacity possible, to save hard disk space later on.  For example,
a 5.25 inch double density -- not high density -- diskette may be formatted
to just 160K by adding the /1 /N:8 parameters to the FORMAT command.)  When
prompted, insert a blank diskette into Drive A and press ENTER.  When the
FORMAT operation is complete, remove the diskette and restart OS/2.

2. Copy FSFILTER.SYS to the diskette.  Double click on OS/2 System ->
Command Prompts -> OS/2 Window.  Insert the diskette you just formatted
into Drive A. Copy the following file to your startable diskette:
\OS2\MDOS\FSFILTER.SYS.

3. Set up CONFIG.SYS.  Using a text editor (like the OS/2 System Editor)
create the file A:\CONFIG.SYS with the following lines at the top:

      DEVICE=A:\FSFILTER.SYS
      DEVICE=C:\OS2\MDOS\HIMEM.SYS
      DEVICE=C:\OS2\MDOS\EMM386.SYS
      DEVICE=C:\OS2\MDOS\ANSI.SYS

Change the "C:"  drive letter if OS/2 is installed on another drive.  Add
any other lines as required for your application (like CD-ROM or
networking), but do not include any XMS, EMS, mouse, or memory management
device drivers.  Make sure that everything is referenced with a drive
letter and path, as above.

4. Set up AUTOEXEC.BAT.  Likewise, create a file named A:\AUTOEXEC.BAT and
make sure that the first line reads:

      C:\OS2\MDOS\MOUSE

changing "C:"  if necessary.  Add any additional lines (like PATH, SET
PROMPT, and so on) as required by your application.

5. Test your DOS diskette.  Once you have configured the CONFIG.SYS and
AUTOEXEC.BAT files as you wish, double click on OS/2 System -> Command
Prompts -> DOS from Drive A:.  A DOS session should start.  Test for the
functionality you need (like access to your CD-ROM reader or network).  If
the session is not working properly, press CTRL-ESC and shut down the
session, edit CONFIG.SYS and/or AUTOEXEC.BAT as required, and repeat the
test.

6. Create the diskette image.  When you are satisfied that your specific
DOS session diskette functions properly, go back to the OS/2 Window and
type VMDISK A:  C:\DOS.IMG to create a diskette image file.  (If you want
the file to be located on another drive or in another directory, change
"C:\" accordingly.)

7. Create a program object for your specific DOS session.  Drag a program
object from your Templates folder to any target folder.  When the notebook
opens, enter a single asterisk (*) in the Program Name field, then click on
the right arrow in the lower right.  Select either DOS Window or DOS Full
Screen for the session type, as desired.  Click on the DOS Settings button,
and scroll down until you find the DOS_STARTUP_DRIVE property.  Enter
C:\DOS.IMG in the field at the upper right.  (If your image file is not
located on Drive C in the root directory, make the necessary changes.)
Change any other DOS Settings if necessary.  Click on the Save button, then
click on the General tab.  Give your program object a name.  Then close up
the notebook.

You should now be able to double click on your new program object to start
your specific DOS session.  If you require access to your diskette drive
(Drive A), use the FSACCESS command.  See the online Command Reference for
details.

When formatting your bootable DOS diskette, you may wish to use additional
command line parameters to create a diskette with a reduced capacity.  The
"smaller" the diskette, the less room the diskette image file created by
VMDISK will take on your hard disk.  See your DOS manual for details, or
use the example given above.


  Related information:

  (1.3) DOS and Windows Compatibility


(5.10) Clever Tricks

 Are there any clever tricks that apply to OS/2 2.1?

o To force DIR to display your directories in alphabetical order, with the
subdirectories listed first, add the line

    SET DIRCMD=/O:GN

to CONFIG.SYS; and, if you wish the same for your DOS command line
sessions, add the same line to AUTOEXEC.BAT.  You may also wish to run
DOSKEY to enable the command history feature.  (Shutdown and reboot for
changes to CONFIG.SYS to take effect.)

o Hold down SHIFT while resizing text windows to make size changes
permanent.

o If you want to configure your printer port(s) for shared access (so that
DOS programs {{ like LapLink, }} for example, can use them directly), go to
your printer object, click on it with mouse button two, select Open ->
Settings, select the Output tab, then double click on the port you wish to
share.  Check the appropriate box.

o While running a DOS graphics program in a window, use the graphics cut
and paste feature to clip a picture and paste it into the Icon Editor.  You
can then quickly and easily create custom icons for your applications.

o To disable the automatic application restart feature, create a
STARTUP.CMD file in the root directory of your OS/2 boot drive with the
following REXX script:

    /*  */
    call RxFuncadd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
    call SysLoadFuncs
    call SysIni 'USER', 'PM_WorkPlace:Restart', 'DELETE:'
    'exit'

or add the line

    SET RESTARTOBJECTS=STARTUPFOLDERSONLY

to your CONFIG.SYS.  To manually disable automatic application restart when
booting OS/2, hold down the left CTRL, left SHIFT, and F1 keys
simultaneously from the time the mouse pointer appears until icons are
displayed on the desktop.

o Use the Alarms applet to automatically start programs at specified times.

To start the Alarms applet minimized, put /I in the Optional Parameters
section of its program object settings.

o If you wish to dispense with the Workplace Shell (and its overhead),
particularly on low memory systems, change the line SET RUNWORKPLACE...  in
CONFIG.SYS to read SET RUNWORKPLACE=C:\OS2\CMD.EXE (replacing C, if
necessary, with a different drive letter).  In fact any program with job
control (e.g.  Enhanced Editor, HyperAccess/5) can be used as the shell.
{{ [A character mode alternative to the Workplace Shell, MenuMaster, is now
available from (3.2) Shareware and Freeware Sources.] }}

o To implement a small scroll back buffer for your OS/2 command line
windows, use the command MODE CO80,102.  This procedure may be automated by
adding /K MODE CO80,102 in the Optional Parameters section of the OS/2
Window program object settings.

o If you do not want any command line parameters passed to a program object
that you start (for example, if you customize the desktop menu so that it
has an additional option which starts a command line prompt) place a lone %
in the Optional Parameters section of the program object settings.  If you
do wish to pass parameters, but you want the extraneous information that
the Workplace Shell passes to the object to be ignored, try putting && REM
% in the Optional Parameters section {{ after the parameters you wish
passed.  }}

o If you want to move an icon a small distance, "grab" it from the edge
nearest the direction you want to move the icon.

o A clever way to manipulate files that are locked when the Workplace Shell
is running (e.g.  display drivers) is to add the line CALL=CMD.EXE at the
end of CONFIG.SYS.  Then Shutdown and reboot.  The system will restart with
an OS/2 command line prompt.  Type EXIT to proceed into the Workplace
Shell.  Using CALL is also a convenient way to configure OS/2's serial
ports using the MODE command.  For example:

    CALL=C:\OS2\MODE.COM COM2:38400,N,8,1,OCTS=OFF,RTS=ON,BUFFER=ON

configures COM2 for high speed RTS handshaking and buffered I/O.  {{
[Moreover, the MODE command can be used to determine whether your system
has a buffered UART (National Semiconductor 16550A or equivalent), nearly
essential for high speed communications.  Use the command:

    MODE COMx

(where x is the communications port number) from an OS/2 command line.  If
you see anything but "BUFFER = N/A" then you have a buffered UART for that
port.] }}

You can use either {{ CDDBOC or SHIFTRUN instead of CALL }}; both utilities
are available from (3.2) Shareware and Freeware Sources.

Another way, which works well with display drivers, is to copy the new
DLL(s) to its(their) own directory (say, C:\NEW), then place that directory
name first in LIBPATH in CONFIG.SYS.  Shutdown and reboot.  OS/2 will use
that(those) DLL(s) before it attempts to use the one(s) located in
\OS2\DLL.  [This method is required when using a 16-bit OS/2 2.0 display
driver with OS/2 2.0 CSD Level 06055 or later.  See (4.6) Corrective
Service Diskettes.] To switch back to the old driver, edit CONFIG.SYS and
remove C:\NEW from LIBPATH, then Shutdown and reboot.

o To shutdown without a mouse, press CTRL-ESC, select the Desktop, then
press the spacebar (to deselect any icons, if necessary), SHIFT-F10, and
select Shutdown.

o If your video driver does not support "seamless" Windows, try running the
Win-OS/2 Program Manager in a DOS window.

o Selective Install should be used with caution when changing mouse or
display drivers.  Verify that proper changes have been made to CONFIG.SYS.

o If your settings notebooks (or PM Sticky Pads) do not display but are
listed in the Window List, click on the name of the settings notebook in
the Window List (brought up with CTRL-ESC) with mouse button two and select
Cascade.

o If your \OS2\*.INI files have grown large, use the CopyINI or WPSBackup
utilities to shrink them.  Both are available from (3.2) Shareware and
Freeware Sources.

o To restart the Workplace Shell (without saving desktop settings, perhaps
after an accidental Arrange), use a utility such as psPM [available from
(3.2) Shareware and Freeware Sources] to terminate PMSHELL.

o To get rid of a WPS object that cannot be deleted, try one of the
following:

- Insert a blank diskette in Drive A, click on the stubborn object with
mouse button two, select Move, select the Path page, enter A:\, press
ENTER, then format the diskette;

- Use the WPSTools or Black Hole, available from (3.2) Shareware and
Freeware Sources.  (The WPSTools can also recreate desktop objects that
have been lost.)

o To load a device driver into high memory in a particular DOS session
change the DOS_DEVICE setting for the session and add SIZE=0 before the
path and filename for the device driver.  For example, the following
DOS_DEVICE entry:

    SIZE=0 C:\OS2\MDOS\ANSI.SYS

loads the ANSI.SYS device driver into high memory in that particular
session.

o If you wish to create diskettes from MAKEDSKF (.DSK) image files, such as
those contained on the CD-ROM version of OS/2, and you do not wish to use
the DOS and OS/2 utility LOADDSKF, you may use a workstation.  For example,
on an IBM RS/6000 {{ or Sun workstation }} you may use the command:

    dd if=(input filename) of=/dev/rfd0 ibs=1b obs=60b conv=sync

o To reboot the machine from the command line, use:

    SETBOOT /IBD:C

Change the last letter (C) if you want to boot from another drive.

o The settings notebooks now support drag and drop operations for assigning
icons and for changing menus.

To change the icon for an object, first open the settings notebook (click
on the object with the secondary mouse button, then select Open ->
Settings).  Click on the General tab.  Then drag any other object to the
icon located on the General page of the settings notebook.  The object's
icon will change to match.  If you want to restore it to its former state,
click on the Undo button.

To assign actions to menus, open the settings notebook, then click on the
Menu tab.  Click on any of the items in the Available menus section (or
Create another).  To add an Action, drag the desired program object to the
Actions on menu section.

o To quickly maximize a window, double click on its title bar.  To restore
the window to its former size, double click on the title bar again.

o Select the Flowed setting (on the View page of the settings notebook) for
fastest display when opening folders.

o If you have UNDELETE enabled, but you want to delete an occasional file
without the overhead incurred by having UNDELETE capability, use the /F
parameter with the DEL command.  Using this parameter (in either a DOS or
OS/2 Window) will bypass the routine which moves the file(s) to the
directory specified by the DELDIR environment variable.  The file(s)
is(are) deleted faster, but you will not be able to undelete it(them).  The
/N parameter will prevent prompting ("Are you sure?").

o OS/2 2.1 now includes the ability to set a power on password.  However,
if you have forgotten your password, and you cannot unlock your desktop
when you turn your machine on, try the following.  Start OS/2 from a
diskette boot [see (4.4) Starting OS/2 from Diskette] to get a command line
prompt.  At the prompt, enter the following commands:

    C:

(assuming OS/2 is installed on Drive C; change if necessary)

    MAKEINI OS2.INI LOCK.RC


o {{ If you are using a 1024x768 display driver (such as 8514/A), but you
do not want the icons scaled up in size from 32x32 to 40x40, patch the
display driver file (e.g.  \OS2\DLL\8514_32.DLL) using DEBUG or a similar
utility.  Search for the hexadecimal byte sequence 28 00 28 00 20 00 20 00
and replace the two 28 values with 20.  Reboot for the change to take
effect, and be sure to keep a backup copy of the original file.  }}

o {{ To hide your entire desktop, single click on any icon on the desktop,
press CTRL-ESC, then press CTRL-SHIFT-ESC.  To return the desktop to
normal, press CTRL-ESC then double click on Desktop.  }}

o {{ If you would like to have a Presentation Manager application start up
minimized, first set up a program object for it by dragging a Program
template from the Templates folder.  Then, on the first page of the
notebook, enter the full path and filename of the PM program, but
deliberately misspell it.  Click on the arrow in the lower right to turn
the page, then check the Start minimized checkbox.  Click on the left arrow
to turn the page back, then correct the misspelling.  Fill in any other
information, as desired, then close up the notebook.  The program object is
now ready to start your PM application minimized.  }}

o {{ To get approximately 730K free in your DOS sessions, change
VIDEO_MODE_RESTRICTION in the session's settings to CGA (unless your
application requires more than CGA graphics capabilities).  Note that you
may have to place the line:

    DOS_RMSIZE=639

in your CONFIG.SYS file to get this much free memory.  }}


  Related information:

  (3.2) Shareware and Freeware Sources
  (4.4) Starting OS/2 from Diskette
  (4.6) Corrective Service Diskettes


(5.11) REXX

 How do I use REXX?  What does it do?

REXX is built into every copy of OS/2 (where it is also known as Procedures
Language/2).  It is a general purpose, interpreted programming language
which was first released on IBM mainframes over a decade ago.  REXX is
extremely easy to learn and use.  It is particularly strong at string
manipulation, and it has features which are difficult to implement in
compiled languages (like the ability to read its own source code or execute
a string as a command).

OS/2 applications can use REXX as a common scripting language, which means
that users need not learn separate macro or script languages for each
application.  For example, the OS/2 versions of Lotus 1-2-3 and Borland
ObjectVision will interface with REXX.  OS/2's multimedia extensions
(MMPM/2) contain a REXX interface, so REXX programs can play, record, and
manipulate sound and video files.  And REXX can be used to create complex
batch files (with interactive prompting), since it is integrated so tightly
into OS/2's command processor.

A pair of REXX visual builders (programming tools which help create even
complex REXX applications quickly and easily using simple, drag and drop
manipulation of on screen objects), HockWare's VisPro/REXX and Watcom's VX
REXX, are now available.  [See (0.2) Recent Developments for more
information on these two programming tools.]

For more information on OS/2's REXX interpreter, see the REXX Information
online documentation located in the Information folder.  For more
information on REXX generally, consult the REXX Frequently Asked Questions
List [available from (3.2) Shareware and Freeware Sources].

{{ Here are some REXX hints and tips:  }}

o If you wish to place program output in the REXX queue (for processing by
a REXX program), try

    DIR *.TXT | RXQUEUE

as an example.  (In other words, pipe the program output to RXQUEUE.)  To
use this program output in your REXX program, try

    /* Sample */
    WHILE QUEUED() > 0
    PARSE PULL X
    SAY X
    END

o {{ To execute REXX commands interactively from the command line, use the
REXXTRY command.  For example:

    REXXTRY DO X=1 TO 10;SAY X;END
     }}



  Related information:

  (0.2) Recent Developments
  (3.2) Shareware and Freeware Sources
  (3.6) Multimedia (MMPM/2)


(5.12) ANSI Escape Sequences

 What ANSI escape sequences can be used?

ANSI escape sequences provide cursor and screen control in OS/2 character
mode sessions.  By default ANSI support is turned ON (although it may be
turned off with the command ANSI OFF).  ANSI support is also available in
DOS sessions if the device driver ANSI.SYS is loaded.  See the online
Command Reference for details.

The following ANSI escape sequences are available:

  Key
  ESC       Refers to ASCII code 27 (i.e. the Escape key)
  #         Replace with the appropriate number
  ....      Replace with additional attributes, if desired

  Escape Code Sequence          Function
  Cursor Controls
  ESC[#;#H or ESC[#;#f          Moves cursor to line #, column #
  ESC[#A                        Moves cursor up # lines
  ESC[#B                        Moves cursor down # lines
  ESC[#C                        Moves cursor forward # spaces
  ESC[#D                        Moves cursor back # spaces
  ESC[#;#R                      Reports current cursor line and column
  ESC[s                         Saves cursor position for recall later
  ESC[u                         Return to saved cursor position
  Erase Functions
  ESC[2J                        Clear screen and home cursor
  ESC[K                         Clear to end of line
  Set Graphics Rendition
  ESC[#;#;....;#m               Set display attributes where # is
                                0 for normal display
                                1 bold on
                                4 underline (mono only)
                                5 blink on
                                7 reverse video on
                                8 nondisplayed (invisible)
                                30 black foreground
                                31 red foreground
                                32 green foreground
                                33 yellow foreground
                                34 blue foreground
                                35 magenta foreground
                                36 cyan foreground
                                37 white foreground
                                40 black background
                                41 red background
                                42 green background
                                43 yellow background
                                44 blue background
                                45 magenta background
                                46 cyan background
                                47 white background
  ESC[=#;7h                     Put screen in indicated mode where # is
                                0 for 40x25 black and white
                                1 40x25 color
                                2 80x25 black and white
                                3 80x25 color
                                4 320x200 color graphics
                                5 320x200 black and white graphics
                                6 640x200 black and white graphics
                                7 to wrap at end of line
  ESC[=#;7l                     Resets mode # set with above command
  Keyboard Reassignments
  ESC[#;#;....#p                The first ASCII code defines what is to be
                                changed; the remaining codes define what it
                                is to be changed to; strings are permitted.
                                Examples:
                                ESC[65;81p - A becomes Q
                                ESC[81;65p - Q becomes A
                                ESC[0;68;"dir";13p - Assign the F10 key
                                to a DIR command.
                                The 0;68 portion is the extended ASCII
                                code for the F10 key and 13 is the ASCII
                                code for a carriage return.
                                Other function key codes: F1=59, F2=60,
                                F3=61, ... F10=68.

You can use ANSI escape sequences in the PROMPT environment variable to
create complex command line prompts.  See the online Command Reference
(under PROMPT) for details.

For example, if you have a color monitor, try editing your CONFIG.SYS file
so that

  SET PROMPT=$e[32;40m$e[1m[$P]$e[0m

to obtain a more colorful OS/2 command line prompt.  (Case is significant
in the example given.)  You can do the same for your DOS sessions if you
edit PROMPT in AUTOEXEC.BAT, assuming you have ANSI.SYS loaded.  Note that
the $i portion of your PROMPT will enable the help line at the top of the
window or screen.  It is not included in the example above.

To change the background color of your OS/2 command line sessions, modify
your CONFIG.SYS file so that this line is changed as shown:

  SET OS2_SHELL=C:\OS2\CMD.EXE /K BLUESCR.CMD

changing the drive letter, if necessary.  Then create a file named
BLUESCR.CMD which contains the following lines:

  @ECHO OFF
  PROMPT=$e[32;44;1m
  PROMPT $p$g
  CLS

Save the file to a directory that is named in the SET PATH line of your
CONFIG.SYS file.  Reboot.  Then, when you start an OS/2 command line, the
background color will be different.  You can change the numbers in the
first PROMPT line to obtain different colors.

If you are using JP Software's 32-bit 4OS2, and you would like the name of
the current working directory to appear in the title bar, try using the
following command:

  PROMPT `%@exec[window"%_cwd"]$h[$p]`


  Related information:

  (5.10) Clever Tricks


(6.0) Miscellaneous

The following questions are addressed in this section:

 (6.1)  What can I do to promote OS/2?

 (6.2)  How can I create INF files?


(6.1) Promoting OS/2

 What can I do to promote OS/2?

OS/2 is selling well, but there are steps you can take to assure that
hardware devices and software will be available for OS/2 in the future.
Customer requests do matter.

o Politely, firmly, and repeatedly request driver support from printer,
video adapter, and other hardware manufacturers.

o When you receive a mailing for DOS/Windows software with a postpaid
envelope, return the order form marked "Please send information on your
OS/2 version."

o Start a user group at your location.  Contact Gene Barlow (phone
214-402-6456) at IBM or mail [e-mail] for assistance.  Think
about how you can publicize your user group.  For instance, most local
newspapers and television stations will print/broadcast meeting
announcements for free.  Your local cable television company will be happy
to broadcast a videotape of your meeting on the public access channel.

o Correspond with members of the computer trade press.  Ask for reviews of
OS/2 software, hardware compatibility testing with OS/2, OS/2 benchmarking,
etc.  Respond politely but forcefully to press you think unfair; praise
good reporting.

o When you purchase a new system, ask the vendor to install OS/2 2.1, and
to offer credit for dropping DOS and Windows.  If the vendor refuses, you
may wish to take your business elsewhere.  {{ Compaq, Everex, }} AST,
Northgate, ALR, Unisys, Dell, Tangent, IBM, and Ariel Design all offer
systems with OS/2 2.1 preloaded.

o Make sure your company (or yourself) specifies OS/2 compatibility when
purchasing new products.

o Demonstrate OS/2 to friends, relatives, and associates.

o Ask your computer store to stock OS/2 software titles, have OS/2
demonstration machines, etc.

o Pass along useful OS/2 shareware and freeware to your local BBS.  Be sure
to register OS/2 shareware.

o Write an outstanding piece of shareware or freeware [See (4.5) Technical
Support for details on joining DAP].  IBM has been known to recognize such
work with rewards.  Also, ask authors of DOS/Windows shareware and freeware
if they would port to OS/2, or volunteer.

o Recommend products that work well under OS/2; dissuade people from
purchasing products that do not.

o Wear OS/2 pins, shirts, buttons, and other souvenirs.  Contact the {{
Lees/Keystone OS/2 Merchandise Center (phone [phone] or FAX
914-273-9187) }} or the IBM OS/2 Hotline (phone 800-3-IBM-OS2) to order
such items.

o Join Team OS/2, {{ an international organization of volunteers who are
OS/2 enthusiasts and are actively sharing their knowledge and enthusiasm
with others.  These activities include supporting OS/2 user groups, running
OS/2 BBSes and online conferences, demonstrating OS/2 at retail stores and
other public places, encouraging and helping others to install OS/2,
answering OS/2 questions, and much more.  Membership is not limited to IBM
employees.  }} For information on Team OS/2 events you should monitor the
TEAMOS2 echomail conference on your local FidoNet BBS.  If your local BBS
does not carry TEAMOS2, ask your system operator to get it.  See (4.11)
OS/2 BBSes for the names and numbers of several BBSes which carry TEAMOS2.
To join Team OS/2, send your name, address(es), and telephone number to
Vicci Conway (netmail [e-mail] or {{ FAX [phone] }}).
{{ Include information on your activities to date and a one line
description of yourself for the public Team OS/2 list.  }}


  Related information:

  (3.2)  Shareware and Freeware Sources
  (4.5)  Technical Support
  (4.11) OS/2 BBSes


(6.2) Creating INF Files

 How can I create INF files?

Creating INF files (like the OS/2 Frequently Asked Questions List) is
remarkably straightforward.  All you need is the Information Presentation
Facility Compiler (IPFC), part of the IBM Developer's Toolkit for OS/2 2.1
(available separately as IBM Part No.  61G1416 or as part of many
development environments such as Borland C++ for OS/2), and a text editor
(like the Enhanced Editor included with OS/2).

Online IPFC documentation is included with the Toolkit, but you may also
wish to order the printed Information Presentation Facility Guide and
Reference, IBM Publication No.  S10G-6262.  See (4.9) Books and Magazines
for ordering instructions.  Note that the Toolkit is part of the low cost
OS/2 {{ Developer's Connection }} CD-ROM.  See (4.5) Technical Support for
details.

If you wish to include illustrations in your INF file you can use any
graphics software which can generate OS/2 bitmaps and/or metafiles.  (For
example, you may create your illustration in PM Chart, paste the
illustration into Picture Viewer, then save the illustration as a metafile.
Both PM Chart and Picture Viewer are included with OS/2 2.1.)  A screen
capture utility [like PM Camera or Galleria, available from (3.2) Shareware
and Freeware Sources] can also prove useful.


 Related information:

 (3.2) Shareware and Freeware Sources
 (4.5) Technical Support
 (4.9) Books and Magazines


(7.0) Glossary

{{ The following terms are often used in conjunction with OS/2:

(This section will be completed in a future release of the OS/2 Frequently
Asked Questions List.)  }}


 Related information:

[End of OS/2 Frequently Asked Questions List: User's Edition]

--
Timothy F. Sipples        | READ the OS/2 Frequently Asked Questions List
[e-mail] | 2.1C, available from 192.153.46.2, anonymous
Dept. of Econ., Univ.     | ftp, in /pub/os2/all/info/faq, or from
of Chicago, 60637         | [e-mail] (send "HELP").