OS/2 Professional Developers Kit 1992 November/Disc01/Disc01.mdf/disks/disk_8/required/README

Text File | 1992-10-01 | 133.3 KB | 4,259 lines

OS/2 2.0 README (8/92)

While most users will not require the
information in this document, it contains
unique application compatibility information
and other useful tips and techniques that might
be helpful in specific situations.  Some of the
information is intended for the more advanced
user or for the user already familiar with
various functions provided with OS/2 2.0.

If you want to search for a specific topic, click
on Edit; then Find.

The scope of this information includes:

o   Introduction
o   Service and Support Information
o   General System Considerations
o   OS/2 Workplace Shell
o   Printing Considerations
o   Application Considerations
o   Performance
o   Windows Version 3.0 Programs Support
o   Video/Graphic Support
o   Hardware Considerations

Service and Support Information

OS/2 2.0 users can access electronic support for
current technical information and exchange
messages with other OS/2 users, 24 hours a day.
If you run into problems or simply need a question
answered about OS/2 2.0, there are two ways to get
help electronically:  the new IBM BBS (Bulletin
Board System) and CompuServe.

o   For information about registering for and
    accessing the IBM OS/2 BBS, call
    1-800-547-1283.

o   For CompuServe membership information, call
    1-800-848-8199, and ask for representative
    239.

    If you already are a CompuServe member, simply
    type "GO IBMOS2" at the ! prompt to access the
    IBMOS2 forum.

To locate an OS/2 bulletin board system in your
geographical area, call 1-609-596-1267.  This
locator service allows you to enter an area code,
and the voice unit responds with phone numbers of
bulletin boards in your area.

General System Considerations

This section describes general system information:


HPFS
____

Following is information about the memory
requirement for the High Performance File System
(HPFS), and how to install it.


DECIDING TO USE

If you are trying to decide whether to use HPFS,
consider that it takes approximately 500KB of
system memory.    If your machine has 6MB or less of
memory, your system performance will be affected
adversely.


HPFS SUPPORT NOT ADDED DURING INSTALLATION

Support for HPFS was not added to your system if
your system has 6MB or less of memory.
To install HPFS support, un-REM the following
statement in your CONFIG.SYS file:

IFS=C:\OS2\HPFS.IFS /CACHE:64/CRECL:4


UNDELETE (ENABLING)
___________________

To enable the UNDELETE command, delete "REM" from
the beginning of the following statement in the
CONFIG.SYS file:

    REM SET DELDIR=


BOOT MANAGER
____________

Following is information about using the Boot
Manager.


BOOT MANAGER MENU BYPASS

The Setboot utility program supports an
immediate-restart function that will restart the
system to the specified drive without going
through the Boot Manager Menu.    The parameter is
/IBD:DRIVE, where DRIVE is the letter of a
startable partition.  For example, from the OS/2
command prompt, you can type

     SETBOOT /IBD:E

to start the logical drive E without displaying
the Boot Manager Menu.    (If the Boot Manager is
not present, then only drive C can be specified.)

RESPONSE FILE INSTALLATION
__________________________

A program used for response file installation of
OS/2 2.0 from diskettes is not included in this
preloaded system.  However, if you order the
backup diskettes from IBM, you can obtain the
program, \OS2\INSTALL\RSPINST.EXE, from
Diskette 7 by typing the following at an OS/2
command prompt:

UNPACK A:\REQUIRED /N:RSPINST.EXE


OS/2 Workplace Shell

This section describes tips you might find useful
when using the OS/2 Workplace Shell(*).  For
WIN-OS/2-specific topics, you should also refer to
"Windows Version 3.0 Programs Support."


STARTING UP YOUR SYSTEM
_______________________

o   If you are using the file allocation table
    (FAT) file system, update your CONFIG.SYS file
    with the following statement to auto-check
    drive C (or your startable partition) to
    ensure disk data is verified prior to using
    the hard disk:

      DISKCACHE=64,LW AC:C

    Note:  This function is done automatically in
       the High Performance File System
       (HPFS).

o   The Startup folder is the OS/2 Workplace Shell
    equivalent of the STARTUP.CMD file.  Objects
    placed in a startup folder are started when
    the Desktop folder is opened.  You cannot
    guarantee the order in which the objects are
    started.

    Note:  Place program objects in this folder
       instead of the executable program-file
       objects.

o   If you want to prevent programs from
    automatically starting when the computer is
    restarted (for example, programs located in
    the Startup folder or programs that were
    running at the time the computer was shut
    down), do the following:

    1.    Press Ctrl+Alt+Del to restart the
    computer.
    2.    When the mouse pointer appears, press
    Ctrl+Shift+F1.
    3.    Hold the keys for approximately 15
    seconds, or until the desktop icons
    appear.  (If the hard disk light stops
    during this time, your computer might be
    suspended.  Release the keys quickly, and
    then resume holding the keys until the
    desktop icons appear.)

o   The STARTUP.CMD file is started before the
    OS/2 Workplace Shell is started; therefore,
    you cannot start applications using this file
    if they require an initialized shell.

o   If you want a customized system startup, you
    can update your CONFIG.SYS file with the
    following statements:

    -    SET RESTARTOBJECTS =

    YES              Default.  Start
                  all objects that
                  were running at
                  time of
                  shutdown.
    NO              Do not start any
                  applications
                  that were
                  running at time
                  of shutdown.
    STARTUPFOLDERSONLY      Start objects
                  only in the
                  Startup folder.
    REBOOTONLY          Start objects
                  only if the OS/2
                  Workplace Shell
                  is starting
                  after resetting
                  with
                  Ctrl+Alt+Del or
                  turning on the
                  computer.  This
                  parameter can be
                  used with one of
                  the other
                  parameters (for
                  example, YES).

    -    SET AUTOSTART =

    FOLDERS         Folders are opened,
                including the Desktop
                folder.
    TASKLIST        The Window List is
                opened.
    PROGRAMS        Programs are opened.
    CONNECTIONS        Re-creates the network
                connections
                established when you
                last logged on.

    Note:  This option is used to start parts
           of the OS/2 Workplace Shell.
           Eliminating any of the above in the
           list restricts users from accessing
           portions of the shell (for example,
           limiting a user to only a few
           applications).


USING THE SHELL
_______________


ICONS, TABS, OR BIT MAPS DO NOT APPEAR

o   If some system icons (such as OS/2 System or
    Shredder) do not appear when you start the
    operating system, you can reset the desktop to
    its default configuration by doing the
    following:

    Warning:  This procedure removes any desktop
    customization done since installing the
    operating system.

    1.    Press Ctrl+Alt+Del to restart the
    computer.
    2.    Before the OS/2 Logo panel appears, hold
    down Alt+F1 for 20 seconds.

    The current versions of the CONFIG.SYS,
    OS2.INI, and OS2SYS.INI files are renamed and
    replaced by the default installation versions
    in the \OS2\INSTALL subdirectory.  If you have
    a STARTUP.CMD file, it also is renamed.  This
    deactivates the startup feature.

CHANGING ICON POSITIONS

If you install IBM LAN Server 2.0, the positions
of the icons on your screen might change.  To
rearrange the icons:

1. Display the pop-up menu for the Desktop folder
   by clicking mouse button 2 on an area not covered
   by any objects or windows.
2. Click on Arrange.

WINDOW BORDERS OFF SCREEN

After changing screen resolutions from a higher
resolution to a lower resolution, some applications
might open windows that are partially off the screen.
If this occurs, press Ctrl+Esc to display the
Window List.  Click mouse button 2 over the name
of the application.  From the pop-up menu, click on
Tile or Cascade.  The window will now appear on
the screen.

Note:  Refer to the help information on the
       Screen page of the System object (in
       the System Setup folder) for instructions
       on changing XGA resolution.


RESTORING THE DESKTOP

If your desktop becomes damaged (for example, if
you start a specific version of DOS and rearrange
your hard disk, damaging either INI files or
extended attributes), you must restore the initial
INI and CONFIG.SYS files to restore the desktop.
However, any modifications (such as shadows and
associations created after installation) are lost
and must be re-created.  To restore the desktop,
do the following to update your existing INI
files:

1.  Restart your computer using
    Utility Diskette 1; then insert Utility
    Diskette 2.
2.  From the OS/2 full screen;
    change to the \OS2 directory.
3.  Type

      MAKEINI OS2.INI INI.RC  (and press Enter)

      MAKEINI OS2SYS.INI INISYS.RC  (and press Enter)

4.  Delete the hidden file WP ROOT. SF in the
    startable partition.  For HPFS, type:

      ATTRIB -h -s -r "WP ROOT. SF"  (and press Enter)

    For FAT, type:

      ATTRIB -h -s -r WP_ROOT._SF  (and press Enter)

    Next, for HPFS type:

      DEL "WP ROOT. SF" (and press Enter)

    For FAT, type:

      DEL WP_ROOT._SF (and press Enter)


If the above procedure does not fix the problem,
do the following to recover the backup INI files.
You will lose all your desktop customization, but
the system should be restored.

1.  Press Ctrl+Alt+Del to restart your computer.
2.  As soon as you hear a single beep, or you
    press Enter at the Boot Manager menu or
    power-on password prompt, press and hold
    Alt+F1.  Hold these keys down until you hear
    rapid beeping.

If the preceding procedures do not fix the damaged
desktop, do the following to re-create the INI
files:

1.  Restart your system using the
    Utility Diskettes.
2.  From the OS/2 full screen;
    change to the \OS2 directory.
3.  Delete the current INI files.  Type:

      DEL OS2.INI (and press Enter)

      DEL OS2SYS.INI (and press Enter)

4.  Re-create both files using the MAKEINI
    command.  Type:

      MAKEINI OS2.INI INI.RC (and press Enter)

      MAKEINI OS2SYS.INI INISYS.RC (and press Enter)

5.  Change to the desktop directory, OS!2_2.0_D
    (FAT) or "OS!2 2.0 DESKTOP" (HPFS).
6.  Delete all subfolders (subdirectories) in this
    directory.
7.  Change to the root directory.
8.  Delete the hidden file WP ROOT. SF in the
    startable partition.  For HPFS, type:

      ATTRIB -h -s -r "WP ROOT. SF"  (and press Enter)

    For FAT, type:

      ATTRIB -h -s -r WP_ROOT._SF  (and press Enter)

    Next, for HPFS, type:

      DEL "WP ROOT. SF"  (and press Enter)

    For FAT, type:

      DEL WP_ROOT._SF (and press Enter)

9.  Press Ctrl+Alt+Del.  The desktop is
    reinstalled to its initial installation setup.
10. Shut down the system using the Shut down
    choice on the desktop pop-up menu.

Note:  Use MAKEINI instead of the Alt+F1 key
       combination if you do not want to replace
       the CONFIG.SYS file and desktop.  The
       install process places a copy of the
       original OS2.INI, OS2SYS.INI, and
       CONFIG.SYS files in the \OS2\INSTALL
       subdirectory.  These are the same INI files
       created with MAKEINI.  They will rebuild
       the desktop and set it to its initial
       installed state.

       Alt+F1 replaces OS2.INI, OS2SYS.INI, and
       the CONFIG.SYS files.


RECOVERING ICONS

o   If you lose a folder by moving it to a folder
    you are unable to access, you can recover the
    folder.  From an OS/2 Window, use the MOVE
    command to relocate the folder (for example,
    the OS/2 System folder, "OS!2_SYS."), to the
    proper location.

    Warning:  The following procedure should be
    used only if a folder is inaccessible to the
    OS/2 Workplace Shell.

    To move a folder (for example, the "OS!2_SYS"
    folder):

    1.    Change to the directory where the
    "OS!2_SYS" folder is located.
    2.    Type the following to move the folder back
    to the Desktop folder.    For FAT, type:


          MOVE OS!2_SYS \OS!2_2.0_D

    For HPFS, type:

          MOVE "OS!2 SYSTEM" \"OS!2 2.0 DESKTOP"



o   If, intermittently, the icons on your desktop
    open normally but appear black, there might
    have been a timing problem that occurred when
    a new icon was saved using the General page in
    the settings notebook.  Try correcting the
    appearance by re-creating or re-storing the
    icon.


USING EXECUTABLE FILES

It is not recommended that you move program-file
objects (.EXE, .COM, .CMD, and .BAT) from their
installed directories (for example, moving a
program-file object from the Drives folder to a
new location).    Moving program-file objects might
cause some program objects to not function
properly.  Instead, you should create a new object
that refers to the original, either a program
object or a shadow; then you can move the new
object to a location of your choice.
(Program-object settings and shadow settings
specify the location of the original program-file
object.)  To create a program object or shadow:

1.  Display the pop-up menu for the program-file
    object by moving the mouse pointer to it and
    clicking mouse button 2.
2.  Click on Create another or Create shadow.
3.  Click on a folder for the new object; then
    click on Create.

Note:  The Create another choice, when used on a
       program-file object, creates a program
       object, not a program-file object.


CREATING AN ICON FOR AN APPLICATION

If you want to create an icon for a DOS, Windows,
or OS/2 application that does not have one, but
has graphics within the application, do the
following:

1.  Run the application in a window session.
2.  When you see an icon-sized graphic that you
    would like to use as the icon to represent
    your program, size the window, making the
    image approximately the size of a desktop
    icon.
3.  Click on the title-bar icon (in the upper-left
    corner of the window); click on Mark.
4.  Mark the graphic.
5.  Click on Copy to move the graphic to the
    clipboard.
6.  Display the pop-up menu for the object by
    moving the mouse pointer to it and clicking
    mouse button 2.
7.  Click on the arrow to the right of Open.
8.  Click on Settings; then click on the General
    tab to display the default icon.
9.  Click on Create another to display the Icon
    Editor.
10. Click on File, click on New, click on Icon;
    then click on OK.
11. Click on Edit, then Paste to paste in your
    graphic.  If necessary, use the Icon Editor to
    make any changes you want in the graphic.
12. Click on File, then Save to store the program
    name.ICO file in the same drive and directory
    as the program file (.COM or .EXE file).
13. Double-click on the title-bar icon to exit the
    editor.
14. From the settings notebook, click on Find;
    then locate the saved .ICO file.  (Clicking on
    Drives is the easiest search.)
15. Click on the icon; then save the file.
16. Exit the settings notebook.  The original icon
    is replaced with the graphic from the
    application.


CHANGING THE COLOR OF ICON TITLE-TEXT

If you want to change the color of the title-text
of all the icons in a folder, do the following:

1.  Double-click on OS/2 System.
2.  Double-click on System Setup.
3.  Double-click on Color Palette.
4.  Press and hold Ctrl; then, pressing and
    holding mouse button 2, drag a color to an
    icon.  Drop the color; then release Ctrl.

Note:  You cannot change the color of individual
       icon-title text.


ADDING AN OS/2 WINDOW TO THE DESKTOP MENU

If you want another method of accessing an OS/2
Window, you can add OS/2 Window as a new menu
choice on the desktop pop-up menu.  Do the
following:

1.  Display the pop-up menu for the Desktop folder
    by clicking mouse button 2 on an area not
    covered by any objects or windows.
2.  Click on the arrow to the right of Open.
3.  Click on Settings; then click on the Menu tab.
4.  From the Actions on Menu choices, click on
    Create another.
5.  In the Menu item name field, type OS/2 Window.
6.  In the Program Name field, type C:\OS2\CMD.EXE
    (change to a different drive, if necessary).
7.  Click on OK.
8.  Double-click on the title-bar icon to close
    the notebook.
9.  Display the Desktop folder pop-up menu again.
    "OS/2 Window" is added to the available menu
    choices.  If you click on this choice, an OS/2
    Window is displayed.


CHANGING A DEFAULT FOLDER VIEW

If you want to change the default view for
displaying the objects within a folder (for
example, icon versus details view), do the
following:

1.  Display the pop-up menu for the folder by
    moving the mouse pointer to it and clicking
    mouse button 2.
2.  Click on the arrow to the right of Open.
3.  Click on Settings; then click on the Menu tab.
4.  Click on Open in the Available menus field.
    The Menu Settings window is displayed.
5.  In the Default action field, click on the
    default you want.
6.  Click on OK.


USING THE MINIMIZED WINDOW VIEWER

o   In the Minimized Window Viewer settings
    notebook, disregard Page 1 of 3.  Each section
    of the notebook contains 1 page only.

o   Some objects, such as WIN-OS/2 programs,
    online books, and programs that start other
    programs, do not minimize to the Minimized
    Window Viewer.


USING FIND

o   In the Help information for Find, disregard
    any references to page 2.  Page 2 does not
    exist in Find operations.

o   If you change the title of an object from
    within the Find Results folder, the name of
    the original object is changed.


RECEIVING AN INCORRECT DOS VERSION MESSAGE

If you receive the message "Incorrect DOS version"
when trying to run a DOS application under OS/2
2.0, the application is using an old level of DOS
on your computer.  To fix the problem, update the
DOS setting DOS_VERSION using the Value field of
the DOS Settings window.  For example,

       PROG.EXE,5,0,255

(program, major version, minor version, count)

This setting simulates the DOS 5.0 version check
as opposed to the OS/2 2.0 version check.


USING ANSI COLORS AND CHARACTERS IN DOS SESSIONS
________________________________________________

If you want to use ANSI colors and characters in
your DOS sessions, do the following:

1.  Add this statement to your CONFIG.SYS file.

      DEVICE=\OS2\MDOS\ANSI.SYS

2.  Shut down your computer.
3.  Press Ctrl+Alt+Del to restart your computer
    and make the change active.


USING HPFS
__________


o   If you are typing a command in the HPFS, you
    must include double quotation marks around the
    name of the subdirectory or file name if it
    contains blanks.  For example, to change to
    the OS!2 2.0 Desktop directory, type:

      CD "OS!2 2.0 DESKTOP"

    As another example, to copy the file This is
    my file from the root directory to the This is
    my directory subdirectory, type:

      COPY "THIS IS MY FILE" \"THIS IS MY DIRECTORY"

Note:  In the FAT file system, HPFS file names are
       shortened.  Underscores represent blank
       spaces.


SHUTTING DOWN
_____________

o   In some low-resource situations, the final
    shutdown message might not appear after a
    shutdown is performed.  To ensure that
    shutdown is complete, wait until all disk
    activity stops before turning off or
    restarting your computer by pressing
    Ctrl+Alt+Del.

o   If you want to shut down your system without
    using a mouse, do the following:

    1.    Press Ctrl+Esc to display the Window List.
    2.    Press Up Arrow (A) to move the cursor to
    "OS/2 2.0 Desktop - Icon View"; then press
    Enter.
    3.    Press Ctrl+\ to deselect any selected
    icons.
    4.    Press Shift+F10 to display the pop-up menu
    for the desktop.
    5.    Press Down Arrow (V) to move the cursor to
    Shut down; then press Enter.

o   You should shut down your system before
    restarting or turning off your computer;
    however, there are situations where you might
    want to restart your system by pressing
    Ctrl+Alt+Del instead:

    -    If you used the Arrange choice on the
    Desktop folder pop-up menu, it rearranged
    the icons you placed in specific positions
    on the screen.    Restarting your system
    recovers your icon positions.

    -    If you opened several folders containing
    many icons, shut down will take a long
    time saving the positions of the icons.
    You might want to restart your system
    without doing a shut down as long as you
    are certain that you will not lose
    anything else of importance.

o   If you shut down your system, but do not
    receive the message "Shutdown has completed.
    It is now safe to turn of your computer...",
    you should wait for all disk activity to stop,
    and then you can press Ctrl+Alt+Del.

Printing Considerations

This section describes tips for configuring your
print hardware, as well as information to help you
diagnose printing problems.

Note:  If you experience problems printing
       with OS/2* or Windows**, contact the
       printer manufacturer or check the
       appropriate bulletin boards for
       updated printer drivers.  Because printer
       drivers are updated periodically, an
       updated printer driver might resolve
       the problem.


CONFIGURING YOUR COMPUTER FOR PRINTING
______________________________________

PS/2 DIRECT-MEMORY-ACCESS PARALLEL PORTS

On the Personal System/2(*) system that
supports direct-memory-access (DMA) parallel
ports, OS/2 2.0 can take advantage of it.  The
current systems with a DMA parallel port include
PS/2 models 56, 57, 80-A21, 80-A31, 90, and 95.
If you have one of these systems, ensure that the
parallel-port arbitration level is set to SHARED7
(enabled).  OS/2 2.0 will automatically take
advantage of this feature; no additional OS/2
setup is required.  Use the Reference
Diskette for the computer to view the
system configuration, and then set the
parallel-port arbitration level to SHARED7.


CONFIGURING PRINTERS
____________________

The following section describes suggestions for
using specific printers.


CANON BUBBLEJET PRINTER

If you want to use a Canon BubbleJet printer with
OS/2 2.0, use one of the following printer
drivers:

o   The BubbleJet BJ10E can emulate an IBM
    Proprinter x24E using the IBM42xx driver.
o   The BubbleJet BJC800 can emulate an Epson
    LQ2550 using the OS/2 Epson driver.
o   The BubbleJet LBP8 III+ can emulate an Epson
    LQ2550 or Proprinter x24E using the
    appropriate driver.


DESKJET, DESKJET+, DESKJET 500, AND DESKJET 500C
PRINTERS

If you want to use a Deskjet, DeskJet+, DeskJet
500, or DeskJet 500C printer, install the Epson
driver and then select HP DeskJet 500.

Note:  The HP DeskJet 500C will not produce color
       output using the HP DeskJet 500 device
       support in the Epson printer driver.


HP LASERJET PRINTER

If you are going to install the OS/2 HP LaserJet
printer driver over an existing driver, be sure to
delete all the old *.FNT files first.  Delete the
printer driver from the OS/2 Workplace Shell
printer object, and respond Yes when asked if the
driver files should be deleted from the hard disk.


HP PAINTJET AND PAINTJET XL PRINTERS

These printers should use the Micrografx Paintjet
printer driver (SMGXPJET.DRV) shipped with OS/2
2.0 on Printer Diskette 3 in directory
C:\OS2\INSTALL\PRTDRVS\PMDD_3.

Some applications, such as Aldus PageMaker, have
problems printing multiple bit maps using this
printer driver.  If this occurs after the driver
is installed, open the printer object settings
notebook; then select Printer-specific format on
the Queues page.

HP PAINTJET PRINTER DRIVER FOR WIN-OS/2

If you are using a HP Paintjet printer driver
for WIN-OS/2, you might receive the following
error message when printing:

 SoftRIP Failure:  insufficient memory in
 SMGXPJET.DRV

An updated printer driver that fixes
this problem will be available shortly on
IBM bulletin boards and CompuServe.


IBM 3812, 3852, 5152, 5182, 5201-1, AND 5216
PRINTERS

Printer drivers were not shipped with OS/2 2.0 for
IBM 3812, IBM 3852, IBM 5152, IBM 5182, IBM
5201-1, or IBM 5216 printers because they have
been out of service for several years.    However,
you can use the printer drivers shipped with OS/2
Version 1.3.  Download the printer drivers from
CompuServe (located in Library 17), or use the IBM
Electronic Device Driver Distribution system.
(Refer to the order card in the OS/2 2.0 package.)

Note:  The IBM 3812 printer can use the IBM 5152
       printer driver by selecting 5152
       compatibility mode in the 3812 printer.
       (For more information, refer to the
       documentation that came with your printer.)


IBM 4019 AND IBM 4029 (AUTOMATIC EMULATION
SWITCHING UTILITY)

For the IBM 4019 and 4029 printers, the beta
version of the Automatic Emulation Switching (AES)
Utility is available from the Lexmark
International bulletin board service (BBS).  The
file is located in the Utilities directory and is
called 40X9SU32.EXE.  (For more information on the
bulletin board, refer to "Accessing Lexmark
International Bulletin Board Service.")

If you have any problems accessing the Lexmark
BBS, call Lexmark at 1-800-537-2540.


IBM 4072 EXECJET PRINTER

If you have an IBM 4072 Execjet printer, you might
want to obtain the new beta version of the OS/2
IBM 42xx printer driver.  The printer driver is
available on the Lexmark bulletin board. The file
is located in the Inkjet directory and is called
OS24072.EXE. (For more information on the bulletin
board, refer to "Accessing Lexmark International
Bulletin Board Service.")

Note:  This is a beta driver; therefore, any
       problems should be reported to Lexmark
       International through their bulletin board
       service.


NEC P3200 PRINTER

If you want to use a NEC P3200 printer, select
Epson driver; then select Epson LQ-850.


NEC P6200 PRINTER

If you want to use a NEC P6200 printer, select
Epson driver; then select Epson LQ-2550.


STAR NX-1000 PRINTER

If you want to use a Star NX-1000 printer, select
Epson driver; then select Epson LX-800.


NON-SUPPORTED PRINTER

o   If your printer is not supported by an OS/2
    2.0 printer driver, determine if your printer
    supports a more common printer in emulation
    mode; then install the corresponding printer
    driver.

o   If your printer has a supported WIN-OS/2
    printer driver, but no OS/2 printer driver, do
    the following:

    1.    Set up the WIN-OS/2 printer driver using
    the WIN-OS/2 Control Panel.
    2.    Set up the OS/2 print object using the
    IBMNULL printer driver.

    You should be able to print from a WIN-OS/2
    session.  Contact your printer manufacturer to
    obtain an OS/2 2.0 printer driver or to
    determine what other printers your printer
    emulates.

OS/2 1.3 PRINTER DRIVERS

If you are using any of the following OS/2 1.3
printer drivers, you should obtain new versions
from the IBM OS/2 BBS or CompuServ:

     IBM3852.DRV
     IBM4201.DRV
     IBM4202.DRV
     IBM4207.DRV
     IBM4208.DRV
     IBM5152.DRV
     IBM5182.DRV
     IBM52011.DRV
     IBM52012.DRV
     IBM5202.DRV
     IBM5216.DRV
     IBMNULL.DRV

In addition, IBM will update OS/2 and Windows
drivers on the bulletin board to provide the
best possible printing support
for our customers on an ongoing basis.


ACCESSING LEXMARK INTERNATIONAL BULLETIN BOARD
______________________________________________
SERVICE
_______

The phone number for the Lexmark bulletin board
service is 1-800-453-9223.  To access the BBS,
select (N,8,1) for port settings, and use the
XMODEM or ZMODEM protocols.  Baud rates 1200 to
38400 are supported.

If you have any problems accessing the Lexmark
BBS, call Lexmark at 1-800-537-2540.


DIAGNOSING PRINTING PROBLEMS
____________________________

This section describes the actions you can take to
resolve some common printing problems.


UNABLE TO PRINT

If you encounter printing problems with parallel
ports (for example, nothing prints), ensure that
you have installed the appropriate printer driver
for your model printer.  If the printer driver is
correct, check the following:

o   Check that your parallel ports are configured
    properly.  Refer to "Configuring Your Computer
    for Printing" for configuration settings.

o   Verify that your printer cable meets
    parallel-port specifications. Some cables do
    not meet these specifications and can cause
    printing problems. (Cables that are longer
    than six feet in length are suspect.  The
    six-foot cable-length problem is more evident
    on high-speed microprocessor systems.)  Some
    cable manufacturers reduce the costs of their
    cables by not wiring all interface signals.
    This might not have been a problem under DOS,
    because DOS does not make use of all the
    signals within the parallel-port interface.
    However, some interface signals used to
    transmit data under OS/2 2.0 are not used when
    printing under DOS.

    You might need to purchase a new cable.  You
    might want to use an "IBM approved" cable, one
    which has been verified as properly wired.

o   If you still cannot print, and you are
    convinced it is not a printer-driver problem,
    interrupt problem, or cable problem, there
    might be a problem with your I/O adapter.
    Some older parallel-port adapters fail to
    generate hardware interrupts; therefore, they
    will not work with versions of the OS/2
    operating system.  These adapters usually work
    correctly under DOS, as DOS does not use
    hardware interrupts to print.  The OS/2 2.0
    operating system waits for the printer to send
    an interrupt when the printer is ready for
    more data.    If your adapter does not generate
    interrupts, it must be replaced if you want to
    print under OS/2 2.0.  If your printer-buffer
    light illuminates, or prints one character and
    then displays an error message (or otherwise
    behaves erratically), you might have an
    interrupt problem.


PRINTER STOPS PRINTING

If your DOS application sending PostScript output
stops printing, do the following:

1.  Cancel the print job that caused the printer
    to stop printing.
2.  Open the printer-object settings notebook to
    the Queue page.
3.  Turn off the Print while spooling check box.
4.  Resend the print job.


ATTEMPT TO PRINT TO AN OFF-LINE PRINTER

If you send a print job to an off-line printer,
and then retry the operation while the printer is
online by responding to the Retry message, your
job might be damaged.    To fix the problem, cancel
the initial job, and resubmit it after resetting
the printer.


PRINTER WORKED UNDER DOS, BUT NOT UNDER OS/2 2.0

If your printer worked under DOS, but does not
work under OS/2 2.0, there is probably a problem
with your hardware-interrupt level or printer
cable.    (Refer to "Unable to Print.")


PRINT JOB SPOOLED BUT DOES NOT PRINT

The spooler will not print a job until the
application closes the print-data stream.  Some
DOS applications do not immediately close the
print-data stream.  If you see your print job as
an icon with an arrow pointing to the document in
the Job Icon View window, the job will not print.
The arrow must point from the document to the
print device.  This will not occur until the
application closes the data stream.

If the job does not print after 15 seconds, you
might need to change a DOS setting.  By default,
the PRINT_TIMEOUT DOS setting is turned ON and set
to 15 seconds.    If, after 15 seconds, your job
does not print, adjust the setting.  (Refer to
"Printing Starts Only When DOS Application Stops"
regarding the LPTDD.SYS file.)


PRINTING STARTS ONLY WHEN DOS APPLICATION STOPS

If your DOS print job does not begin printing
until the application is stopped, the application
has not closed the data stream.  Use the
DOS_DEVICE DOS setting to load the
C:\OS2\MDOS\LPTDD.SYS device driver.  Then, the
PRINT_TIMEOUT DOS setting can be used to close the
print job without having to exit your application.


PRINT JOB SPLIT INTO SEVERAL SPOOL FILES

If your DOS application print job is split into
several spool files, you might need to disable the
spooler to correct the problem.  Some applications
open and close the printer data stream for every
character, line, or page.  Disabling the spooler
(using the Spooler object in the System Setup
folder) is one way to correct this problem.
Another alternative is to upgrade the application
by contacting the manufacturer.  If the problem
occurs with complex printouts, you might increase
the DOS setting PRINT_TIMEOUT value.


CAN PRINT FROM DOS APPLICATION, BUT CANNOT PRINT
ELSEWHERE

If you are printing from a DOS application, but
are unable to print elsewhere until you stop the
DOS application, your DOS application is accessing
the parallel-port hardware directly.  OS/2 2.0
prevents two or more applications from
simultaneously accessing the same parallel-port
hardware.  The second application must wait for
the first application to stop, even if the second
application is the OS/2 print object.


PRINTER WORKED UNDER WINDOWS, BUT NOT UNDER OS/2
2.0

o   If your printer worked under a Windows
    operation, but does not work after installing
    OS/2 2.0, delete the printer driver and
    reinstall it under WIN-OS/2 using the WIN-OS/2
    Control Panel.

o   If printing from a WIN-OS/2 session is slow,
    but acceptable everywhere in the system, you
    might need to set the priority level higher
    using the Options menu in the WIN-OS/2 Print
    Manager.


PRINTING FROM A WIN-OS/2 SESSION
________________________________

The following section describes considerations for
customizing your system to print from a WIN-OS/2
session.


LPTX AND LPTX.OS2 PORT CONSIDERATIONS

If your printer is connected to LPTx or LPTx.OS2,
be sure that the OS/2 spooler is active and the
WIN-OS/2 printer does not use the Print Manager.
(Disable using the Printer icon in the WIN-OS/2
Control Panel.)  When the OS/2 spooler is active,
WIN-OS/2 applications print directly to the OS/2
spooler.  Therefore, multiple print jobs can be
spooled from one WIN-OS/2 session or multiple
WIN-OS/2 sessions.  This does not apply to serial
printers, because there is no spooling for COM
devices to the OS/2 spooler (only to WIN-OS/2
Print Manager).  If you are using LPTx but are
unable to print from any other session, you must
use LPTx.OS2 for WIN-OS/2 printing.  If you are
printing to a redirected port, you must use
LPTx.OS2.


OBTAINING AN LPT3.OS2 DESTINATION

To enable support for LPT3.OS2, you need to
configure an LPT3.OS2 destination that you can
select from the ports listbox in the WIN-OS/2
Control Panel.    You must shutdown your WIN-OS/2
session and edit the C:\OS2\MDOS\WINOS2\WIN.INI
file.  You need to add a "LPT3.OS2=" line
following the "LPT2.OS2=" line in the ports
section of the file.  After saving the file, you
can start the WIN-OS/2 session and Control Panel
and then select the LPT3.OS2 destination.


INSTALLING THE IBM 4029 LASER PRINTER

o   If you are installing the IBM4029 Windows
    PostScript printer driver for use in WIN-OS/2
    sessions, do the following to avoid an invalid
    entry in the WIN.INI file.

    1.    Double-click on Control Panel in the
    WIN-OS/2 session.
    2.    Double-click on Printers.
    3.    Click on Add Printer.
    4.    Click on Unlisted Printer from the list of
    printers.
    5.    Insert Printer Driver Diskette 4 in drive
    A.
    6.    In the Files and Directories window, click
    on A.
    7.    Click on PSCRIPT.DRV from the files list.
    (The PostScript driver is installed.)
    8.    Click on Configure.
    9.    Click on the appropriate port.
    10. Click on Setup.
    11. Click on IBM4029 (17 font, 600 Dpi) from
    the list of printers.
    12. Click on OK several times to remove the
    open windows.
    13. Exit the Control Panel.
    14. Save any changes; then exit the WIN-OS/2
    session.

o   If you have problems printing with a 4029
    printer in a WIN-OS2 session, change the
    WIN.INI file in the OS2\MDOS\WINOS2 directory.
    Several lines in the file refer to the 4029
    printer (for example, "IBM 4029 v52.3 (17
    Fonts, 600 Dpi").  Change the comma (,) to a
    colon (:).


NETWORK PRINTING
________________

o   To improve the performance of viewing the
    contents of a network printer object, use a
    long refresh interval or set the interval to 0
    (no refresh).

o   If you move the network object from the
    desktop to another folder, the network
    printer-object template will not appear the
    next time you start the system. To make it
    reappear, move the network object back to the
    desktop and restart the system.

o   If you are unable to print from a DOS session
    to an LPT port that is redirected to a network
    printer, you might need to use the LPTDD.SYS
    device driver.  (Refer to "Printing Starts
    Only When DOS Application Stops" for more
    information.)

Application Considerations

Most DOS, Windows, and OS/2 programs run under
OS/2 2.0 without any modification.  A few need
specific attention, such as changes to DOS
settings, for optimum performance.


GENERAL CONSIDERATIONS
______________________

Some categories of programs do not work correctly
with OS/2 2.0 because of their design, or because
they use undocumented interfaces, or because they
perform restricted activities.    The following list
identifies these categories of programs:

o   DOS extenders that require exclusive access to
    the 80386 control registers, such as the
    Virtual Control Program Interface (VCPI), are
    not supported because they would violate the
    integrity of the system.  The DOS Protect-Mode
    Interface (DPMI 0.9), the Expanded Memory
    Specification (EMS), and the Extended Memory
    Specification (XMS) are supported.

o   Programs that directly address the physical
    disk sectors to perform disk-write operations
    are not supported.    These operations would
    violate the integrity of the system.  This
    category includes most DOS UNDELETE programs.

o   Some Windows programs make use of the Windows
    accessory programs, like the Calculator.  If
    you already had Windows Version 3.0 installed
    and you did not format your hard disk when you
    installed OS/2 2.0, the accessory programs are
    on your hard disk and are supported by OS/2
    2.0.  However, the accessory programs are not
    part of the WIN-OS/2 environment included with
    OS/2 2.0.

o   Programs (and hardware) that require the
    Windows Enhanced mode are not supported.  This
    mode uses an unsupported memory-management
    method.  Programs that run in the Windows
    Standard mode and Real mode are supported.

o   Programs that manipulate the 80386 control
    registers, such as 386 DOS debuggers, are not
    supported; this would violate system
    integrity.

o   Fax boards and programs that use more that
    1000 interrupts per second (9600 baud or
    greater) are not supported.  The following fax
    boards and programs contain timing
    sensitivities that might prevent reliable
    operation:

    -    ATI ETC
    -    Cardinal FAX
    -    Practical Peripherals
    -    Smartfax
    -    Twincomm 24/96

o   If you run a bulletin board or a DOS
    communications application that keeps timing
    out, change the DOS settings as indicated
    below.  If the first settings change does not
    fix the problem, change the next settings, and
    so forth.

    1.    HW_TIMER to ON
    2.    IDLE_SECONDS to 60, and IDLE_SENSITIVITY
    to 100
    3.    COM_HOLD to ON
    4.    HW_ROM_TO_RAM to ON
    5.    If you lose data using DOS communications
    software, set the PRIORITY_DISK_IO setting to
    NO in your CONFIG.SYS file, and the
    IDLE_SENSITIVITY setting to 100% in the DOS
    settings for the object.

    If the DOS settings changes do not fix the
    problem, set PRIORITY_DISK_IO to NO in the
    CONFIG.SYS file.


Our testing has identified the following programs
that perform one or more of the activities
described above:

o   Ansel for Windows
o   Bound Checker (DOS)
o   Central Point Backup for Windows
o   Close-Up (Windows)
o   Desert Storm CD-ROM (Windows)
o   Distinct Back-Up (Windows)
o   DoDot 3.0 (Windows)
o   Fax Concentrator (DOS)
o   Magic-CV (DOS)
o   Mathematica 2.0 (Windows)
o   MusicPrinter Plus 4.0 (DOS)
o   OmniPage Professional 1.0 (Windows)
o   Oracle (DOS)
    (There is an OS/2 version of this program.)
o   Perceive for Windows
o   Phar-Lap DOS extenders prior to Version 4.0
o   Realizer 1.0 (Windows)
o   Sherlock Holmes CD-ROM (DOS)
o   Smartfax (DOS)
o   Soft-ICE (DOS)
o   Splash 1.01 (DOS)
o   Turbo Debugger (DOS)

In addition to the restricted activities described
previously, some general conditions you should be
aware of are in the following list:

o   For more reliable DOS communications
    performance on slower systems, the combined
    baud rate should not exceed 9600 bps for one
    or more concurrent DOS applications.

o   You can improve the performance of DOS
    communications programs by using the 16450
    UART or 16550AFN UART communications chips.

o   Some DOS and Windows programs run correctly
    only in full-screen sessions.  Any Windows
    program that does not use the Windows API to
    change the video mode should be run in a
    WIN-OS/2 full-screen session.

o   Some Windows programs experience
    painting problems when running in a window
    on the OS/2 2.0 Desktop.  These problems
    may be the fault of the application code.
    If possible, modify Windows application
    code to handle the receipt of back to
    back WM_PAINT messages.  Never ignore
    second, or subsequent, WM_PAINT messages.
    Also, avoid displaying message boxes
    within application "paint" logic
    (logic related to the receipt of a WM_PAINT
    message).

o   Some DOS and Windows programs must be
    installed or run in a "Specific-DOS" session;
    that is, in a session that was started by
    booting from an actual version of DOS.
    For more information, refer to "DOS, starting
    specific version" in the Master Index.

o   Some programs run in OS/2 DOS or WIN-OS/2
    sessions, but require that you install the
    program under DOS.

o   Windows programs cannot start DOS sessions or
    DOS programs.

o   DOS programs that use low-level file system
    calls cannot access HPFS disks.

o   If you are running communications programs,
    you should set the CONFIG.SYS statement
    PRIORITY_DISK_IO to NO; then restart your
    system.

o   Code-page-switching support is not available
    for graphics mode in DOS sessions.

o   Some DOS and Windows programs use security
    keys as protection against copyright
    infringement.  The security key is a 25-pin
    connector that is connected to the parallel
    port of the computer on which the program is
    executing.    The program checks to see if the
    connector is attached and, if the connector is
    not present, the program is assumed to be an
    illegal copy.  When more than one DOS session
    is running one of these programs, a SYS1799
    error can result.  This occurs because the
    programs that use these security keys do not
    de-allocate the parallel port if a second
    session is started for a program that also
    requires the security key.    This error is the
    result of a direct I/O parallel port
    contention mechanism that protects the user
    from possible data corruption.  To disable
    this mechanism:

    1.    Display the pop-up menu for the printer
    object by moving the mouse pointer to it and
    clicking mouse button 2.
    2.    Click on Open; then Settings.
    3.    Click on the Output tab.
    4.    Double-click on the LPT port that has
    the contention problem.
    5.    Click on the Shared access checkbox to share
    the port between DOS sessions doing direct I/O
    to the parallel port.
    6.    Click on OK.

o   Some Windows Multimedia Extension programs
    might not work correctly after being migrated
    to OS/2 2.0.  If this occurs, reinstall them
    under WIN-OS/2.

o   If the SYS0005 error "ACCESS DENIED" occurs
    when starting DOS programs, follow this
    procedure:

    1.    Shut down the system.
    2.    Insert the Installation Diskette into
    drive A.
    3.    Restart the system.
    4.    When prompted, remove the Installation
    Diskette, insert Diskette 1, and press
    Enter.
    5.    At the "Welcome to OS/2" screen, press
    Esc.
    6.    Remove Diskette 1, and insert Diskette 2.
    7.    At the command prompt, type "CHKDSK C:
    /F:3 " and press Enter.
    8.    If you receive the error "cross-linked
    extended attribute", repeat the previous
    command until CHKDSK reports no errors.
    9.    After repeated attempts, if CHKDSK
    continues to report errors, note the names
    of the files related to the errors.  Copy
    these files to a blank diskette and delete
    the files from the hard disk.  Then, run
    CHKDSK again.
    10. When CHKDSK reports no errors, copy the
    files back to their original location, and
    restart your system.

    Note:  This problem usually occurs when an EADATA
       file is deleted from DOS.  If you have DOS,
       copy files to another directory or name; delete
       the originals, and then copy back to the original
       location.

SPECIFIC APPLICATIONS
_____________________

The following list provides information about the
compatibility of specific programs with OS/2 2.0.
This information is version specific; later
versions of the same program might operate
correctly.  Some program manufacturers already
have resolved incompatibility issues and have
fixes available; these are noted.

o   Action! Sampler 1.0 (Windows)

    -    The DPMI_MEMORY_LIMIT WIN-OS/2 setting
    must be set to 5 or greater.

o   Adobe Type Manager (Windows)

    -    When using an IBM 4029 printer in PPDS
    mode with Adobe Type Manager, some Windows
    programs may not function correctly.  If
    this occurs, do not use the printer
    resident fonts.  To disable printer
    resident fonts, bring up the control panel
    of the Windows Adobe Type Manager and
    ensure that the selection "Use Pre-built
    or Resident Fonts" is disabled.

o   After Dark (Windows)

    -    To run in a WIN-OS/2 window session,
    change the object's settings to hide or
    minimize the icon to the desktop.
    -    This program places a TSR (terminate and
    stay-resident) reference in the
    AUTOEXEC.BAT file when it is installed.
    To run in a WIN-OS/2 window session,
    remove this reference from AUTOEXEC.BAT.

o   Aldus PageMaker 4.0 (Windows)

    -    The spelling checker cannot locate the
    dictionary.
    -    Deselect the public setting to use the
    clipboard.
    -    If you experience incorrect output when
    spooling Standard format files to the
    printer, set the printing to RAW mode.    To
    do this, take the following actions:
    1.  Go to the Printer icon on the desktop.
    2.  Select Open, then Settings, then Queue
        Options.
    3.  Ensure that Printer Specific Format is
        checked.

o   Aldus Persuasion 2.0 (Windows)

    -    Use the parallel ports to print.
    -    Deselect the public setting to use the
    clipboard.

o   Arts & Letters Graphics Editor 3.1 (Windows)

    -    The DECIPHS utility program requires that
    a DOS session be started from the Windows
    environment; this is not supported.
    -    To run in a WIN-OS/2 window, change the
    object's settings to minimize to the
    desktop.
    -    The directory created by Arts & Letters is
    named A&L.  The "&" character is a
    reserved character of the command shell,
    CMD.EXE; it is used for conjugated command
    lines.    To change to the A&L directory
    with the CD command you must use one of
    two methods of quoting the directory name.
    The first method is to prefix the "&" in
    A&L with a ^ (caret, shift 6):
    CD A^&L
    The second method is to surround the
    entire directory name with quotation marks
    ("):
    CD "A&L"
    -    If you are running Arts & Letters and you
    get a system error (a GDI trap), you must
    restart the operating system before
    running the program again.  This is
    because the program left a portion of
    itself running when it ended and will not
    start a new copy of itself while that
    portion is running.  This also means that
    when you restart the computer, Arts &
    Letters will start again automatically.
    It is recommended that you close the copy
    that is launched on system startup and
    start the program from its icon when you
    intend to run it in a window.

o   AutoCAD Version 10 (DOS)

    -    Close the program from the desktop.

o   AutoCAD (OS/2)

    -    Some of the background colors are set to
    an unusually pale color that does not show
    up well on XGA displays.

o   AutoManager 4.0 (DOS)

    -    The version of the program that uses
    extended memory uses an unsupported DOS
    memory extender.  Use the real-mode
    version.
    -    The program expects COMMAND.COM to be in
    the root directory of drive C:\.  Copy
    COMMAND.COM from the C:\OS2\MDOS directory
    to C:\.

o   Borland C++ 2.0 and 3.0 (DOS)

    -    Set the DPMI_DOS_API DOS setting to
    ENABLED.

o   Borland Turbo C++ 2.0 (DOS)

    -    The version of the program that uses
    extended memory uses an unsupported DOS
    memory extender.  Use the standard version
    of the program.

o   Borland Turbo Debugger 2.01 (DOS)

    -    The version of the program that uses
    extended memory uses an unsupported DOS
    memory extender.  Use the standard version
    of the program.
    -    TD386, the 386 version of Turbo Debugger,
    manipulates the 80386 control registers;
    this is not supported.

o   Borland Turbo Debugger for Windows (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.
    -    The screen is temporarily corrupted when
    this program is called from Turbo C++.
    The screen is restored on the first
    repaint.  (A repaint can be forced by
    clicking the mouse on several different
    windows.)

o   Borland Turbo Pascal 6.0 (DOS)

    -    The version of the program that uses
    extended memory uses an unsupported DOS
    memory extender.  Use the standard version
    of the program.

o   Central Point Backup for DOS 7.1 (DOS)

    -    Displays meaningless characters when
    running in a DOS window session.  Run this
    program only in a DOS full-screen session.

o   Central Point PC Tools Deluxe 7.1 (Windows)

    -    Many of the utility programs require
    starting a DOS session from the Windows
    environment; this is not supported.  Start
    these programs from a separate DOS
    session.
    -    The backup feature of this program
    performs in a manner similar to Central
    Point Backup for Windows, which is in the
    list of programs that perform restricted
    activities.  If you experience difficulty
    backing up on a diskette, back up on an
    alternate device, such as a network drive
    or a tape drive.

   Note:  You might need to install this program
      under a specific-DOS session.

o   Commander Keen (DOS) (other Apogee games)

    -    Set the VIDEO_RETRACE_EMULATION DOS
    setting to OFF.

o   COMMUTE (Windows)

    -    When this program is installed under
    WIN-OS/2, the statement
    keyboard.drv=commkbd.drv is added to the
    SYSTEM.INI file.  Change this statement to
    keyboard.drv=keyboard.drv.

o   Control Room 1.0 (DOS)

    -    You must run this program in a DOS
    full-screen session for the screen
    blanking feature to work correctly.

o   CorelDRAW 2.0 (OS/2)

    -    If you do a large amount of printing while
    in this program, it is possible that you
    might run out of system resources.  To
    avoid this, you should periodically save
    your work and exit CorelDRAW, then restart
    the program and continue your work.

o   CorelDRAW 2.0 (Windows)

    -    Install the program in a DOS session.
    -    Run the program in a WIN-OS/2 full-screen
    session.

o   CorelDRAW 2.1 (Windows)

    -     To install this program:
    --  Start a DOS session.
    --  Run FFIX /date (Note that "date" must
        be lowercase).
    --  Type "A:" and press Enter.
    --  Exit WIN-OS/2.
    --  Run FFIX /u.
    --  Type "install" and press Enter.
    -    Run the program in a WIN-OS/2 full-screen
    session.

o   Crosstalk (Windows)

    -    Run "MODE COMx BUFFER=OFF" from the
    command line, where x is the
    communications port you are using, before
    you run the program.

o   dBase IV 1.1 (DOS)

    -    If you receive a "too many files open"
    error message, set the DOS_FILES DOS
    setting to 30.    Set the DOS_VERSION DOS
    setting to DBASE.EXE,5,0,255.  With
    Hyperdisk, set DOS_VERSION to
    DBASE1.EXE,5,0,255.
    -    When using Hyperdisk, you might have to
    adjust the EMS and XMS memory limits.
    -    With the multi-user version, the program
    must be run in a Specific-DOS session.

o   Designer (OS/2)

    -    The MIRRORS.DLL that comes with this
    program must be installed in the program
    directory, as opposed to the C:\OS2\DLL
    directory, and the program must be started
    from this directory.  This is because OS/2
    2.0 comes with its own dynamic link
    library named MIRRORS.DLL.

o   Drafix CAD Version 1.11 (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   Drafix CAD Version 3.0 (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   DynaComm Asynchronous OS/2 (OS/2)

    -    The DLL's included with this product must
    not be in the same directory as the
    executable file.  Put them in a separate
    directory and add that directory to the
    end of the LIBPATH.

o   Enhanced Editor (OS/2)

    -    The OS/2 Enhanced Editor supports up to 99
    fonts.    If additional fonts are installed,
    unpredictable results might occur.
    -    In the online help for the enhanced
    editor, it states that you should contact
    your IBM representative for detailed
    information on how to program the editor.
    Instead, obtain this information from the
    IBM bulletin boards.

o   F-117A Stealth Fighter 2.0 (DOS)

    -    Set the VIDEO_RETRACE_EMULATION DOS
    setting to OFF.
    -    If the program appears to stop at a blank
    screen soon after you start it, press ESC
    and the program will continue.    Once you
    are past the opening screens, the program
    runs correctly.

o   F19 (DOS)

    -    Set the HW_ROM_TO_RAM DOS setting to ON
    and the VIDEO_RETRACE_EMULATION DOS
    setting to OFF.

o   Fastback for Windows (Windows and OS/2)

    -    Use only Version 1.01, a no-charge upgrade
    from Fifth Generation Systems.    To order,
    call 1-800-873-4384.
    -    In the Options pull-down menu in the
    program, make sure that the Media setting
    is set to system default.  (The other
    Media settings write to DMA device
    drivers, which have incompatibility
    problems.)

o   Fastback Plus 2.1 and 3.04 (DOS)

    -    If you experience difficulty backing up on
    a diskette, back up on an alternate
    device, such as a network drive or a tape
    drive.

o   FastLynx 1.1 (DOS)

    -    To use the serial port with this program,
    remove the DEVICE=C:\OS2\MDOS\VCOM.SYS
    statement from CONFIG.SYS.  The parallel
    port works correctly.
    -    Due to its high speed, the program
    sometimes fails to function.  If this
    occurs, simply end the program; system
    integrity is not compromised.  To minimize
    the possibility of this error condition,
    set the following DOS settings:
    HW_TIMER = ON
    IDLE_SENSITIVITY = 100
    IDLE_SECONDS = 10

o   Form Publisher (Windows)

    -    Ensure that the program's printer driver
    is installed before running the program.

o   FormBase 1.2 (Windows)

    -    The SHARE statement is automatically added
    to AUTOEXEC.BAT during program
    installation.  Use an editor to remove the
    SHARE command from AUTOEXEC.BAT.
    -    When running this program and Lotus 1-2-3
    in the same Windows session, this program
    must be started first.

o   FotoMan (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   Framework III 1.1 (DOS)

    -    The program expects COMMAND.COM to be in
    the root directory of C:\.  Copy
    COMMAND.COM from the C:\OS2\MDOS directory
    to C:\.
    -    Disable the program's print spooler; using
    it might cause an error.

o   Guide (Windows)

    -    When running Guide in a WIN-OS/2 window
    session, you might encounter problems
    with the display of pop-up items.  When
    a pop-up is selected, the box is drawn,
    the text placed within it, but then redrawn
    in the upper-left portion of the window.
    The text is not erased when the selection
    button is released.  To avoid this problem,
    run the application in a full-screen session.

o   Harvard Draw (Windows)

    -    When installing this program under
    WIN-OS/2, you will receive an error dialog
    box.  Select OK in the dialog box and
    installation will complete successfully.

o   Harvard Graphics (Windows)

    -    When installing this program under
    WIN-OS/2, you will receive an error dialog
    box.  Select OK in the dialog box and the
    installation will complete successfully.
    -    When running in a window, the Color
    Selection windows are missing the Color
    Selection grid.  Run the program in a
    WIN-OS/2 full-screen session.

o   hDC FileApps 1.0 (Windows)

    -    The program uses the Windows Notepad for a
    README text file during installation.
    Indicate that you do not wish to read the
    file and installation will continue.

o   HP New Wave 3.0 (Windows)

    -    Install the program under DOS.    If you
    experience problems with program or
    session termination, set UseOS2shield=0 in
    SYSTEM.INI (in the \OS2\MDOS\WINOS2
    directory on your start-up drive).  If
    that does not help, run the program in a
    full-screen WIN-OS/2 session.

o   IBM 3363 Optical Disk Drive

    -    The software for this product must be run
    in a Specific-DOS session that is started
    from drive A.
    -    You should run only one DOS session
    when using this product.

o   IBM PC LAN Support Program (DOS)

    -    If you close the DOS session that is
    running this program, you must first reset
    the token-ring adapter before you restart
    this session.  To fix this problem,
    download RSTTOK.ZIP from the IBM BBS or
    from IBMFILES in CompuServe.

o   IBM PC/3270 V2.0* (DOS)

    -    First, the program must be migrated using
    the OS/2 Migration utility program.
    -    Then, in the Session Page of the DOS
    settings:
    --  Select DOS full screen or DOS window.
    --  Set the VIDEO_MODE_RESTRICTION DOS
        setting to CGA.
    --  Add "D:\[path]DXMA0MOD.SYS" and
        "D:\[path]DXMC0MOD.SYS" to the
        DOS_DEVICE DOS setting.
    -    Then, in the Program Page of the DOS
    settings:
    --  Set the Path and File Name to *.
    --  Set the Parameters to /K
        d:\path\PC3270.BAT.
    --  Set the Working directory to d:\path.

o   IBM PC/3270 V2.0* (Windows)

    -    First, the program must be migrated using
    the OS/2 Migration utility program.
    -    Then, in the Session Page of the WIN-OS/2
    settings:
    --  Add " /C PC3270WO.BAT" to the
        DOS_SHELL WIN-OS/2 setting.
    --  Add "D:\[path]DXMA0MOD.SYS",
        "D:\[path]DXMC0MOD.SYS", and
        "D:\[path]PCS802.SYS V=N" to the
        DOS_DEVICE WIN-OS/2 setting.
    --  Set the "DOS_SHELL" setting to /C
        PC32700WO.BAT.
    --  Set the "WIN-OS/2 window Separate
        session" or "WIN-OS/2 full screen"
        setting to ON (click on the check box
        until a check mark appears).
    -    Then, in the Program Page of the WIN-OS/2
    settings:
    --  Set the Path and File Name to
        d:\path\PC3270.EXE.
    --  Set the Working directory to d:\path.

o   Icon Author (Windows)

    -  Existing animations and graphics that are
       shipped with the program should be run on a
       VGA system or in a low-resolution XGA full-
       screen WIN-OS/2 session.  In XGA high
       resolution, the graphics are scaled to
       only a portion of the screen and text is
       drawn in normal size.

o   Intel SatisFAXtion    (DOS)

    -    The program must be run in a specific-DOS session.
    -    At the end of installation of the Intel
    SatisFAXtion, you are instructed to remove the
    diskette and press any key to reboot your
    machine.  Instead, shut down the operating
    system and restart your computer.
    -    If SatisFAXtion software is loaded into
    each DOS session, it might cause the fax
    to stop if another DOS session is started.
    Set up one DOS session to be used for
    faxing, and load the device driver and
    executable files only into that DOS
    session.  To do this, take the following
    steps:
    1.  Edit AUTOEXEC.BAT.
    2.  Cut the last two lines referring to
        the Intel SatisFAXtion board to the
        clipboard and save the file (using DOS
        Command File for the file type).
    3.  Open a New file.
    4.  Paste the last two lines into the new
        file.
    5.  Save the new file as FAX.BAT, using
        DOS Command File as the file type.
    6.  Edit CONFIG.SYS and cut the last two
        lines relating to the Intel
        SatisFAXtion board to the clipboard
        (cut only the last line if you do not
        have a scanner installed).
    7.  Save the file using Plain Text as the
        file type.
    8.  In the Command Prompts folder, select
        a DOS Full Screen icon, press the Ctrl
        key and mouse button 2 at the same
        time, move the mouse pointer to an
        empty area in the folder, and release
        the mouse button and the Ctrl key.
        This creates a copy of DOS Full
        Screen.
    9.  Put the mouse pointer over your new
        icon and press mouse button 2.
    10. Click on the arrow next to Open, and
        select Settings.
    11. Go to the Session page and select the
        DOS settings push button.
    12. Go to DOS_DEVICE and press mouse
        button 1.  Then, move the mouse to the
        dialog area and press mouse button 1
        (there should be a blinking cursor
        now).
    13. Paste the text that you cut from the
        CONFIG.SYS file and select Save.
    14. Go to the General page and replace the
        contents of the Title box with FAX (or
        whatever other title you choose).
    15. If you want to edit the new session's
        icon, go to the General page and
        select the Edit push button.
    16. If you want to have this session start
        each time your system starts, move the
        icon to the Start Up folder.
    17. Whenever you start this session, type
        FAX to run the FAX.BAT file before
        using the SatisFAXtion board.  Use the
        fax board in only one session at a
        time.
    -    If you install using this procedure and
    you receive error messages, install the
    program under DOS.

o   King's Quest (DOS)

    -    Remove the DOS=HIGH statement, if one
    exists, from CONFIG.SYS or from the
    DOS_DEVICE DOS setting.

o   LAN Support Program Device Drivers (DOS)

    -    If you opened a DOS session with the DOS
    LAN Support Program (LSP) device drivers,
    and subsequently closed the session, you
    must ensure that the token-ring adapter is
    reset before using the LAN from another
    DOS session.  To ensure that the
    token-ring adapter is reset, use
    RESETOKN.EXE or RESETOKN.SYS.  These files
    can be retrieved from CompuServe by
    issuing GO IBMOS2 and downloading
    RESTKN.ZIP from SECTION 17, IBMFILES, or
    they can be retrieved from the IBM
    National Support Center Bulletin Board
    System by downloading RESTKN.ZIP.
    -    The IBM token-ring adapter should be used
    by only one session at a time.

o   LANtastic 4.0 (DOS)

    -    You might experience problems with this
    version of LANtastic.  Use Version 4.1
    instead.  For more information, contact
    the ARTISOFT BBS at 602-293-0065.

o   LANtastic 4.1 (DOS)

    -    Run this program in a Specific-DOS
    session.  Set DOS_STARTUP_DRIVE DOS
    setting to the location of a DOS kernel to
    boot from.
    -    If you are using Artisoft AE-2 or AE-3
    adapters, set your adapters to 8-bit mode,
    as described in the adapter documentation.

o   LapLink Pro (DOS)

    -    Run "MODE COMx IDSR=OFF ODSR=OFF ORTS=OFF"
    from the command line, where x is the
    communications port you are using, before
    you run the program.

o   LapLink III 3.0 (DOS)

    -    It is preferable that you use the parallel
    port.  To use the serial port with this
    program, comment out the VCOM.SYS
    statement from CONFIG.SYS (by putting "REM
    " at the beginning of the line) and
    restart the computer.  To use the serial
    port for other purposes, uncomment the
    lines in CONFIG.SYS and restart the
    computer.

o   Lotus 1-2-3 for Windows 1.0 and Lotus 1-2-3
    Release 3.1 (DOS)

    -    Set the DPMI_MEMORY_LIMIT DOS setting to a
    minimum of 3MB.
    -    After migrating the program to the
    Workplace Shell, copy the file 123W.INI to
    the \OS2\MDOS\WINOS2 directory (from the
    directory previously containing Windows
    3.0).
    -    If you plan to use this program, follow
    these steps:
    1.  Create a batch file called LOTUS.BAT
        which contains:

           @ECHO OFF
           CLS
           PROMPT $p$g
           PATH=X:\LOTUS
           SET 123MEMSIZE=2048
           ...    (any other lines)
           123.EXE   (last line in file)

    2.  Open the Templates folder from the
        desktop.  Select the Program Icon by
        single-clicking on it with the left
        mouse button.  Drag a program template
        to the desktop using the right mouse
        button.
    3.  Single-click on the program template
        on the desktop with the right mouse
        button to reveal the Object menu.
        Select Open Settings.  A notebook
        display will be opened.
    4.  In the Program and Filename field,
        enter:

        x:\path\lotus.bat

    5.  Select the Session Tab and click on
        the DOS FULL SCREEN radio button.
        Select the DOS SETTINGS push button.
    6.  Select or add the following DOS
        Settings:

        DOS_UMB  ON
        DOS_HIGH  ON
        DOS_VERSION  INSTALL.EXE,3,40,255
                    123.EXE,3,40,255
                    LOTUS.EXE,3,40,255
                    123DOS.EXE,3,40,255
                    ZAP.EXE,3,40,255
                    INS.EXE,3,40,255
        DPMI_MEMORY_LIMIT  4 OR HIGHER

    7.  Click on the General Tab, and add:

        Title -> Lotus 123 (or whatever you choose)

        Close the notebook by selecting Close
        or double-clicking on the system menu.
    8.  Start the DOS session by
        double-clicking on the DOS full-screen
        icon.
    9.  From the A: prompt, type INSTALL to
        install the product.
    10. Start the LOTUS Specific-DOS session
        by double-clicking on the LOTUS
        program object.

o   Lotus Freelance Graphics for OS/2 (OS/2)

    -    If you experience installation problems,
    contact the Lotus Development Corporation.
    Lotus will provide a fix.

    You can also download FLGOS2.ZIP from the
    IBM BBS or from IBMFILES in CompuServe, or
    download INSTAL.ZIP from the LOTUS section
    of CompuServe.
    -    If you experience problems with the color,
    change the palette from the Freelance
    menus.    Instructions on how to do this can
    be found in the Lotus Freelance Graphics
    for OS/2 User's Guide.  A set of new
    default palettes for Freelance Graphics is
    available.  These can be retrieved from
    CompuServe by issuing GO IBMOS2 and
    downloading PALETT.ZIP from SECTION 17,
    IBMFILES, or they can be retrieved from
    the IBM National Support Center Bulletin
    Board System by downloading PALETT.ZIP.

o   Lotus Freelance Graphics for Windows (Windows)

    -    The pointer to printer objects points to
    Screen Show instead of to the printer.

o   Lotus Magellan 2.0 (DOS)

    -    The UNDELETE function in the program uses
    physical sector addressing, which is not
    supported.  Use the OS/2 UNDELETE command.

o   Lotus Notes (OS/2)

    -    To use Notes 2.x, you must delete the file
    QWC.EXE from the Notes program directory.
    This file is used only for support in the
    field, and, therefore, its removal will
    not affect program execution.

o   MAGICorp (Windows)

    -    Running this program with other programs
    in the same WIN-OS/2 session might cause a
    system halt.  Run this program by itself
    in a WIN-OS/2 full-screen session.

o   Mathcad 3.0 (Windows)

    -    To install this program:
    --  Start a DOS session.
    --  Run FFIX /date (Note that "date" must
        be lowercase).
    --  Install the program (the installation
        program is a DOS program).
    --  Run FFIX /u.

o   Mathcad 3.1 (Windows)

    -    Set the DPMI_MEMORY_LIMIT DOS setting to
    64 or greater.
    -    Set the XMS_MEMORY_LIMIT DOS setting to 0.
    -    Set the EMS_MEMORY_LIMIT DOS setting to 0.

o   MicroProse Civilization (DOS)

    -    Set the VIDEO_RETRACE_EMUL setting to OFF
    and the HW_TIMER setting to ON.

o   More Windows (Windows)

    -    If you use the Full-Page Paper White mode
    or Full-Screen Color mode, the screen
    might be disrupted.  Avoid using these
    modes.

o   MS Bookshelf** - CD-ROM Reference Library
    (DOS/Multimedia)

    -    The program requires version 6.14 of the
    mouse device driver, MOUSE.COM, which
    comes with the product.
    -    Use the INT_DURING_IO setting to avoid
    video and audio problems.
    -    The program will not install if the
    PATH statement in the AUTOEXEC.BAT
    file exceeds 254 characters.  If this
    problem exists, do the following:

    1. Make a backup copy of AUTOEXEC.BAT.
    2. Edit the AUTOEXEC.BAT and add the
       directory to install the program.
       For example, if you want to install
       the program in your D drive, add
       D:\VIEWER to the PATH statement.
    3. Save the file; then start a
       WIN-OS/2 session to install
       the program.

o   MS Chart 3.0** (DOS)

    -    Install the program's mouse driver, and
    set MOUSE_EXCLUSIVE_ACCESS to ON.

o   MS Codeview** (DOS/OS/2)

    -    When using the protect-mode version, CVP
    2.2 (for OS/2), trace through the source
    code, rather than through the assembler
    language.
    -    In order for the program to work
    correctly, delete the PWBHLP.PXT help
    file.

o   MS Codeview for Windows Version 3.0**
    (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   MS Excel for DOS 2.1** (DOS)

    -    Set the XMS_MEMORY_LIMIT DOS setting to 0.

o   MS Excel for OS/2 3.0** (OS/2)

    -    The Help index and the Keyboard Help
    windows operate incorrectly.  Avoid using
    these functions.

o   MS Excel for Windows 3.0** (Windows)

    -    Deselect the public setting to use the
    clipboard.
    -    When using dynamic data exchange (DDE),
    run it in the same WIN-OS/2 session as the
    Windows program it is communicating with.

o   MS Money 1.0** (Windows)

    -    Calls the Windows Calculator accessory
    program.  Use the OS/2 Calculator
    mini-application program in the
    Productivity folder.

o   MS MSCDEX (DOS)

    -    Run the program in a specific-DOS session.

o   MS Project for Windows 1.0** (Windows)

    -    Must be installed in a DOS session.

o   MS QuickC** (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   MS Windows 3.0** (DOS)

    -    It is preferable that you run Windows
    programs under WIN-OS/2, which supports
    both Standard and Real mode Windows
    programs.  If, however, you choose to run
    this program, run it in Real mode only.

o   MS Word (OS/2)

    -    You might have problems selecting items
    from the application menu, and the
    application appears to freeze.    Call the
    Microsoft support number for their fix.

o   Mirrors III

    -    Run "MODE COMx BUFFER=OFF" from the
    command line, where x is the
    communications port you are using, before
    you run the program.

o   National Geographics Mammals (DOS)

    -    Run the program with the DOS Setting
    INT_DURING_IO set to On.

o   National Geographic Presidents (DOS)

    -  Run the program with the DOS Setting
       INT_DURING_IO set to On.

o   Norton Backup 1.2 (DOS)

    -    You might experience diminished
    performance when backing up to diskette.

o   Norton Desktop (Windows)

    -    This program assumes that, if it is not
    the first program loaded, another desktop
    is running.  Include the UseOS2shield=0
    statement in SYSTEM.INI (in the
    \OS2\MDOS\WINOS2 directory on your
    start-up drive).
    -    If you experience difficulty formatting a
    diskette, use the OS/2 FORMAT command.    If
    you experience difficulty backing up on a
    diskette, back up on an alternate device,
    such as a network drive or a tape drive.
    -    Run the program in a WIN-OS/2 full-screen
    session.

o   Norton Utilities 5.0 (DOS)

    -    The UNDELETE functions require physical
    sector addressing, which is not supported.
    Use the OS/2 UNDELETE command.
    -    The utility programs that manipulate the
    hard disk (for example, UNDELETE,
    UNFORMAT, DISKTOOL, CALIBRATE, the Disk
    Doctor, and the Disk Editor) can cause a
    system halt.  Some of these programs can
    be used on floppy diskettes.

o   PaintShow Plus 2.21 (DOS)

    -    Load the version of MOUSE.COM that comes
    with the program before starting the
    program.

o   Paradox 3.5 (DOS)

    -    The version of the program that uses
    extended memory uses an unsupported DOS
    memory extender.  Use the standard version
    of the program.

o   Peachtree Complete III 5.0 (DOS)

    -    Set the DOS_FILES DOS setting to 60.
    -    The program's Lookup function does not
    list all the companies that have been
    entered into the program's list of
    companies; it displays meaningless
    characters.

o   Perform Pro 1.0 (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   PFS: First Choice (DOS)

    -    When the program is run in a DOS window,
    the mouse pointer does not reflect tool
    selection.
    -    Set the baud rate to 2400 or lower when
    using the communication feature.

o   PFS: WindowWorks 1.75 (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   Photostyler (Windows)

    -    Run the program in a WIN-OS/2 full-screen
    session.

o   PM Terminal Program

    -    Make sure that the asynchronous
    communications driver, SASYNCDB.SYS, is
    not commented out on a REM statement in
    the CONFIG.SYS file.

o   Publishers PowerPak 2.1 (Windows)

    -    Create the directory
    C:\OS2\MDOS\WINOS2\POWERPAK
    before running the installation batch
    file.

o   Quattro Pro 3.0 (DOS)

    -    Install printers from within the program,
    rather than during program installation.

o   Quicken (DOS)

    -    Remove the DOS=HIGH statement, if one
    exists, from CONFIG.SYS or from the
    DOS_HIGH setting.

o   Quicken for Windows (Windows)

    -    The program calls the Windows Calculator
    accessory program.  Use the Calculator
    mini-application program in the
    Productivity folder.

o   Risk (DOS)

    -    Do not use the program's shutdown
    function.

o   SantaFe Media Manager (DOS)

    -    To install this program:
    --  Start a DOS session.
    --  Run FFIX /find (Note that "find" must
        be lowercase).
    --  Install the program.
    --  Run FFIX /u.

o   SideKick (OS/2)

    -    A printer must be installed and present on
    the desktop to use the Notepad.

o   Signmaster 5.11 (DOS)

    -    The plot/preview feature causes an illegal
    instruction to be issued.

o   Soft Term (OS/2)

    -    In the Send File and Receive File windows,
    the first time the drive is changed,the
    Directory window updates incompletely.
    After the first time, the Directory window
    works normally.

o   SoundBlaster (DOS)

    -    The SBTEST utility program reports an
    incorrect DMA level during installation.
    Disregard the error message and continue
    with installation.  The program will be
    installed correctly.
    -    The PARROT program does not run in a DOS
    session.

o   Space Quest IV (DOS)

    -    Set DOS_BACKGROUND_EXECUTION to OFF so
    that the program is suspended when it is
    placed in the background.
    -    Set up the program so that it does not use
    extra memory.
    -    For best performance, run this program in
    a DOS full-screen session.
    -    For computers with a SoundBlaster card,
    change to the drive and directory which
    contains Space Quest IV and enter

      SQ4FIX

    on the command line.

o   SQLWindows 3.0 (Windows)

    -    The program accesses drive A at
    intermittent intervals.  Keeping a scratch
    diskette or an empty diskette in drive A
    will save you from having to respond to
    "The A: device is not ready" error
    windows.

o   Stacker 2.0 (DOS)

    -    This program does not run under OS/2 2.0.
    Stac Electronics has announced an OS/2 2.0
    compatible version of Stacker that will be
    released later in 1992.  Contact Stac
    Electronics for more information.

o   The Way You Work (DOS/Windows)

    -    Install this program under DOS.  Once
    installed, the program can be run in a DOS
    or WIN-OS/2 session.

o   Windows Multimedia Extensions (Windows)

    -    If you are running this program and
    another program that uses the audio
    adapter at the same time, unpredictable
    results might occur.
    -    The OS/2 Multimedia Presentation Manager
    avoids this problem.

o   Winfax Pro (Windows)

    -    Run this program only in a WIN-OS/2
    full-screen session.
    -    If you are using Dynamic Data Exchange
    (DDE), avoid switching away from the
    WIN-OS/2 full-screen session in which you
    are running; switching from the WIN-OS/2
    session to another session might break the
    DDE link.

o   Wing Commander II (DOS)

    -    Set HW_TIMER to ON.
    -    If you are running on a slower computer,
    turn the sound option off.

o   WordPerfect for Windows (Windows)

    -    Change to the directory that contains
    WPWINFIL.EXE and run:
    FIXWP WPWINFIL.EXE.
    (To enable WordPerfect for Windows to run
    under DOS and Windows 3.0 again, run
    UNFIXWP in a similar manner.)

    -    Button bar icons do not always appear
    correctly.  Button bar text and processing
    is correct.

o   WordPerfect Office 3.0 (DOS)

    -    Install the keyboard-enhancement utility
    program manually, after program
    installation, by adding it to CONFIG.SYS.

o   Xtree Pro Gold 2.0 (DOS)

    -    The Zip Manager feature cannot find the
    zip file it is to act upon.  Avoid using
    this feature.

Performance

Following are some performance considerations that
you should be aware of.  For more performance
guidelines, see the Information and Planning
Guide document (G326-0160) that can be obtained
through your point of purchase or retrieved
through CompuServe.

The minimum memory requirement for OS/2 2.0 is
4MB.  (This includes up to 128KB that is used on
some systems for ROM to RAM remapping.)

Users concerned with response times when using
some system functions, such as loading programs,
starting sessions, and switching between sessions,
can improve performance by increasing system
memory.  If you are running on a constrained
system (small hard disk, 16-MHz or less processor,
4MB of memory), an additional 2MB of memory will
improve performance.  In the entry memory system
(4MB), the recommended file system is the FAT file
system.


SWAPPER FILE
____________

The system automatically pre-allocates the
SWAPPER.DAT file based on the size of installed
memory.  This is done to optimize performance and
reduce disk fragmentation.  To tune the size of
the swapper file, see the information about
SWAPPATH in the Command Reference.

In OS/2 2.0, the SWAPPER.DAT file is designed to
shrink in size when the data segments are no
longer needed, but does not shrink as expected.
This problem has been fixed by IBM APAR PJ03686,
available from CompuServe or the IBM BBS.

Ignore any CHKDSK errors that might be reported on
the SWAPPER.DAT file.  These error indications are
normal.


FILE SYSTEMS
____________

Many performance changes have been incorporated
into OS/2 2.0 File Systems.  Both file systems
read ahead (for sequential I/O), lazy write to
disk, and accept threshold parameters.

A disk cache size is preselected by the system
based on installed memory, disk size, and file
systems installed. The default for the entry
memory system (4MB) is a cache size of 128KB.  To
tune the size of the disk cache, see the
information about DISKCACHE in the Command
Reference.


DOS APPLICATIONS
________________

You can improve the performance of some DOS
applications by adjusting the DOS settings.  If
the application does not require extended or
expanded memory, these values can be set to zero.
This will provide maximum performance.

Some DOS applications use polling techniques to
poll the system for work. An example is an
application that appears to be idle at an input
prompt, but is in fact polling the keyboard
looking for keystrokes.  Use the IDLE SENSITIVITY
choice to detect this occurrence and put the
application to sleep when it is polling.


WINDOWS APPLICATIONS
____________________

Windows applications are generally started in one
WIN-OS/2 session, unless specifically set to run
in their own WIN-OS/2 session.    If you use several
applications simultaneously, you might want to
increase the DPMI memory limit before starting the
first application.  The first application started
determines the DPMI memory available for all
subsequent Windows applications that are used.

In low-memory configurations, you can run multiple
Windows applications in one WIN-OS/2 session. This
reduces both memory and swapper-file requirements.

With a WIN-OS/2 window session, a new session is
created every time you double-click on an active
object.  To restore the currently active object:

o   Double-click on the minimized application
    object, or
o   Display the OS/2 Window List and double-click
    on the application name.

If you choose to migrate your Windows applications
(at installation time or later using MIGRATE),
most Windows applications will execute in one
WIN-OS/2 session.  If you set up a Windows
application and do not use MIGRATE, each program
executes in its own WIN-OS/2 session.


APPLICATION USAGE
_________________

If you have an application that you always use,
you can set up the application in the Startup
folder to load when the system is started.

To avoid reloading frequently used applications,
minimize the application after use and simply
maximize it to use it again. You can find the
application in the Window List or the Minimized
Window Viewer.

If you use several different applications, the
icons (objects) can be placed on the desktop or in
a folder.  The folder can be set to open when the
system is restarted.


MEMORY
______

Close opened applications when you are not going
to use them again.

Close folders that you do not need.  Also, move
commonly used functions out of folders and onto
your desktop, and close the folders that contained
the icons.


HARD DISK SPACE
_______________

To save hard disk space, you can use the
Selective Uninstall utility in the Configuration
Tools folder within the Welcome folder
to remove functions you do not need.
If you have the Productivity aids and the Games, and
later only want a subset of these, use Selective
Uninstall to selectively remove the items you
do not want.

Windows Version 3.0 Programs Support

This section contains tips and techniques for
running Windows applications in WIN-OS/2 sessions
(window and full-screen).


OPTIMIZING WIN-OS/2
___________________

The following are tips for using your computer
more efficiently in WIN-OS/2 sessions:

o   Current information for WIN-OS/2 window
    sessions in high-resolution video modes is
    available from CompuServe, the IBM National
    Support Center Bulletin Board System, the OS/2
    Bulletin Board System, and IBMLINK.

o   If you are running Windows programs in
    WIN-OS/2 window sessions, you cannot have any
    statement in the AUTOEXEC.BAT file that
    prompts the user for input (for example,
    "Press any key to continue").

o   Do not use the SETUP.EXE file shipped with
    Windows 3.0.  Instead, use the SETUP.EXE file
    shipped with WIN-OS/2 to ensure your
    environment is properly configured for OS/2
    2.0.  Use the Configure program in
    OS/2 2.0 to change video device drivers for
    VGA, 8514, XGA, EGA, and CGA, and for mouse
    device drivers.  To start the Configure program,
    double-click the icon for Welcome, then
    Configuration Tools, then Configure.

o   To decompress Windows device drivers supplied
    by equipment manufacturers, use the EXPAND.EXE
    utility program for WIN-OS/2 located in
    C:\OS2\INSTALL\DRIVERS.

o   Windows Version 3.1 is not compatible with
    OS/2 2.0, so you cannot run it in a WIN-OS/2
    session.  You can, however, run Windows 3.1 in
    a separate partition.  Partition your hard
    disk so that Windows 3.1 is in a partition
    separate from OS/2 2.0.

o   If a Windows application does not work
    correctly in a WIN-OS/2 session, it is likely
    that the application files were not all
    migrated properly.    To fix the problem, you
    can reinstall the application using a WIN-OS/2
    full-screen session.  (Select Run on the File
    menu of the Program Manager and use the
    command line there.)  Or, if you know the
    specific files that are needed, you can copy
    them from the \WINDOWS directory to the
    \OS2\MDOS\WINOS2 directory.

o   If you are running a WIN-OS/2 full-screen
    session and you have an 8514 display, use DOS
    Settings to set VIDEO_8514A_XGA_IOTRAP to Off
    and VIDEO_SWITCH_NOTIFICATION to On.

o   If the VIDEO_SWITCH_NOTIFICATION setting is
    On, wait until you see your WIN-OS/2 desktop
    in a full-screen session before switching back
    to the OS/2 desktop.  If the session does not
    start successfully, close it, and then restart
    it.

o   The value for VIDEO_SWITCH_NOTIFICATION should
    not be changed for an active WIN-OS/2 session.

o   You cannot use the WIN-OS/2 Control Panel to
    change mouse buttons in WIN-OS/2 window
    sessions.  Change mouse button settings from
    the OS/2 desktop to affect the WIN-OS/2 mouse
    buttons in the WIN-OS/2 window environment.
    The WIN-OS/2 Control Panel can still be used
    for changing mouse buttons in WIN-OS/2
    full-screen sessions.

o   If you have the US English version of OS/2
    2.0, and you want to change the system
    configuration to another country or language,
    run Configure to make the changes
    effective for OS/2.  To make the changes
    effective for WIN-OS/2, start WIN-OS/2 in a
    full-screen session, open the Control Panel,
    and use the International choice to make your
    changes.  The drivers are located in
    C:\OS2\INSTALL\DRIVERS.  Type the directory
    name in the entry field when prompted for
    the .DLL file.

o   If you start an application in a WIN-OS/2
    session and receive the message "FATAL ERROR
    0X0401", ensure that all device statements
    are correct in \OS2\MDOS\WINOS2\SYSTEM.INI.

o   If you are running a WIN-OS/2 full-screen
    session with an XGA video device driver and
    your WIN-OS/2 icons are not clear, use the
    Control Panel to choose another color scheme
    for the WIN-OS/2 desktop.

o   To improve performance, it is preferable to
    have only one server or client in a WIN-OS/2
    session.

o   If you have an XGA or 8514 display, keep the
    DDE server as an icon instead of opening it.
    Also, set the DOS setting
    VIDEO_SWITCH_NOTIFICATION to On.


USING CLIPBOARD AND DYNAMIC DATA EXCHANGE
_________________________________________

o   The availability of Clipboard and Dynamic Data
    Exchange (DDE) functions can vary, depending
    upon the types of sessions you are running.

    -    In standard-mode (full-screen and window)
    sessions, Clipboard and Dynamic Data
    Exchange (DDE) default to Public.

    -    In real-mode full-screen WIN-OS/2
    sessions, the default is Private.

o   To share data in a single WIN-OS/2 session:

    1. Select OS/2 System.
    2. Select System Setup.
    3. Select WIN-OS/2 Setup.
    4. Select Data Exchange.
    5. Select the Private radio button.
    6. Close the WIN-OS/2 Setup Settings notebook.

o   If you cannot paste a bitmap from the OS/2
    clipboard to a WIN-OS/2 session, the bitmap
    might be too large, or the application might
    not understand the device-independent bitmap
    (DIB) format of the file.  For example, bitmaps
    created using the Icon Editor are not
    understood by some Windows applications, such
    as Microsoft Paintbrush.  If your WIN-OS/2
    session is started first, you can view the
    bitmap in the OS/2 clipboard; however, you
    cannot paste it.  The Paste menu choice is
    grayed (unavailable).

o   When performing DDE with a WIN-OS/2 server and
    an OS/2 2.0 client, linked data is not received
    when the OS/2 2.0 application requests 256 color
    XGA bitmaps.  Correct this by following these
    steps:

    1.    Select OS/2 System.
    2.    Select System Setup.
    3.    Select System icon.
    4.    Change the screen resolution
    to 1024 x 768 x 16.
    5.    Shut down your system.

o   If you are running several applications
    concurrently (each doing Copy and Paste), you
    might receive from the clipboard pasted data
    that was supposed to go into another
    application.  Suppose you copy data to the
    clipboard using Application 1, but do not
    paste it into its destination right away.
    While Application 1 is doing other work, you
    copy data from Application 2 to the clipboard,
    and you do not paste that data either.  Later,
    you attempt to paste the Application 1 data
    from the clipboard.  However, the only data
    that is pasted is from Application 2, not
    Application 1.  This happens because the
    clipboard can hold data from only one cut or
    copy at a time.  In this example, the copied
    data from Application 2 replaced the data from
    Application 1.

    To avoid having this problem, always paste the
    cut or copied data into its destination
    application before you cut or copy data from
    another application to the clipboard.

o   Vertical scrolling in the OS/2 clipboard does
    not work.  It will be fixed in a future
    release.  In the meantime, you can use Page
    Down and Page Up.

o   When a metafile is copied to the OS/2
    clipboard, it is converted into a bitmap, and
    then the image is enlarged.  Only the center
    of the image is in the clipboard viewer.  This
    will be fixed in future release.

o   Metafiles in WIN-OS/2 and OS/2 are not
    compatible.  If you copy a WIN-OS/2 metafile
    without bitmap information to a public
    clipboard, it is converted to a
    device-independent bit map (DIB) so that it
    can be exchanged with an OS/2 session.

o   If you want to use dynamic data exchange (DDE)
    using the Paste Link choice on the File menu
    of an application, consider the following
    information.

    The clipboard should be set to Public.  The
    client and server must "negotiate" the data
    format to initiate the DDE link.  If this
    negotiation fails, some applications do not
    display any error message and no further
    action is taken.  If this happens, try another
    menu choice (for example, Link), if available.

Video/Graphic Support

OS/2 2.0 fully supports EGA, VGA and XGA.  OS/2 2.0
also supports 256 color palette management,
WIN-OS/2 and Windows applications running
within a window on the OS/2 XGA desktop.
Because of the highly graphical user interface
provided by the Workplace Shell, using OS/2 2.0
in CGA mode will be difficult and is not recommended.
However, applications designed for CGA mode are
supported and can be run even when OS/2 2.0 is
running in EGA, VGA, or SVGA mode.  Resolutions
above VGA (640 x 480 x 16 colors) are referred
to as XGA or Super VGA (SVGA).    However, the
implementation of SVGA varies widely and requires
different device drivers for different resolutions,
as well as for different adapters and systems.
The OS/2 Configure program will correctly configure
OS/2 2.0 and WIN-OS/2 drivers for 8514 and XGA.
All SVGA adapters are supported in VGA mode with
the VGA driver provided with OS/2 2.0.

DISPLAY TYPE OVERRIDE
---------------------

In order to correctly operate your display,
OS/2 2.0 attempts to determine the type and
characteristics of the device using a display
identification number.    Some displays have the same
identification number but different characteristics.
If OS/2 does not operate your display at the correct
refresh rate or display mode, run the Display Type
Override Utility provided on the "IBM PS/2 XGA
Device Drivers - DOS, Windows and AutoCAD Support"
diskette that came with your system (Diskette
Number 53G0183).  To run this utility, perform the
following steps:

    1. Open a DOS Window or DOS full-screen session.
    2. Type the SET command:

     SET DMQSPATH = C:\XGA$DMQS

    3. Set the default drive to the diskette drive
       containing the PS/2 XGA Device Drivers diskette.
    4. Change to the DIFINST directory on the diskette

     cd \DIFINST

    5. Execute the Display Information File Install
       (DIFINST) program.  At the command prompt type:

     DIFINST

    The DIFINST main menu appears.
    6. Select Change XGA Display Configuration Profile.
    7. Use the online help and documentation provided
       with DIFINST to complete the configuration
       definition for your display.  Access online help
       by pressing the PF1 key.

SVGA
____

The base video system and virtual display device
driver in OS/2 2.0 have been enabled for some of
the most popular SVGA chips and boards.  This
support is required to switch between PM and DOS
or WIN-OS/2 applications.  Because of the many
implementations and video modes, a limited number
of video boards have been tested.

The following Super VGA boards have been tested
and found to work with OS/2 2.0 for DOS
applications that make use of SVGA modes:

o   Orchid ProDesigner IIs by Orchid Technology
    (ISA and MCA versions)
o   Trident TVGA by Trident Microsystems, Inc.
    (8900b and c levels)
o   STB PowerGraph VGA by STB Systems, Inc.
o   Video Seven VRAM II, by Video Seven
o   Boca Super VGA by Boca Research Inc.
o   VGA Wonder XL Series by ATI Technologies, Inc.
o   Paradise VGA Professional by Western Digital
    Imaging

VGA support is designed to be generic for the
Trident, Tseng, ATI, Headland, and Western Digital
chipsets.  It is likely that there are many more
adapters which are supported that have not been
tested.

The 8514 Ultra by ATI must be installed as an 8514
and as a primary display; it will default to
high-resolution mode.  You should update the
following statement in your CONFIG.SYS file:

  DEVICE=\OS2\MDOS\VVGA.SYS

to

  DEVICE=\OS2\MDOS\VSVGA.SYS

Contact the manufacturer of your computer or SVGA
video adapter to obtain device drivers and
installation instructions if you want to run
Windows or OS/2 applications in SVGA modes.
Information about SVGA support will be available
on CompuServe, the National Support Center
Bulletin Board System, the OS/2 Bulletin Board
System, as well as many video-board and system
manufacturers' bulletin boards.

We recommend you do NOT run the video-adapter test
utility programs in OS/2 2.0 unless the
manufacturer has explicitly verified that they run
in OS/2 2.0.

Some video adapters require that the computer's
DOS BIOS initialize the video adapter correctly.
If you have one of these adapters, screen text
might appear distorted in an OS/2 full-screen
command prompt.  To remedy this, start a DOS
full-screen session, type exit, and then switch
back to the OS/2 full-screen session; the text
should appear normal.

To automate this process, you can create a DOS
batch file to run when you start your computer.
Add the following statement to STARTUP.CMD:

   START /FS /DOS DOSFS.BAT

Create the file, DOSFS.BAT, and place the
following statement in it:

   EXIT


OS/2 SVGA VIDEO FILES

o   \OS2\SVGADATA.PMI

    This file indicates that SVGA support has been
    enabled with SVGA ON.  The file contains data
    on the following:

    -    The video chipset of your SVGA adapter.
    -    The SVGA modes, from the supported list,
    your adapter is capable of setting.  The
    list of supported modes is:
    --  640x480/256 colors
    --  800x600/16    colors
    --  800x600/256 colors
    --  1024x768/16 colors
    --  1024x768/256 colors
    --  132x25 text
    --  132x43 or 44 text
    -    The values in the video registers when the
    adapter is in each mode.  This data is
    used by the OS/2 operating system to save
    and restore the registers to their proper
    state when switching between sessions with
    different SVGA modes set.  This data file
    must be generated by typing SVGA ON at a
    DOS full-screen command prompt, because
    SVGA ON sets all the possible modes using
    the BIOS of the video adapter and then
    reads out the values of the registers into
    the .PMI file.    If SVGA ON is run from a
    DOS window, the video virtualization of
    the operating system takes over, and the
    BIOS does not set the SVGA modes properly.

    Even though two systems have the same video
    adapter, the same SVGADATA.PMI file does not
    work in both.  The SVGADATA.PMI file has to be
    specific to each adapter/display setup.

o   \OS2\SVGA.EXE

    This is the utility program that generates the
    .PMI file and places it in the \OS2
    subdirectory.  The syntax is:

      SVGA ON|OFF|STATUS

    where ON creates the \OS2\SVGADATA.PMI file
    and enables SVGA support, OFF deletes the .PMI
    file, and STATUS returns the chipset type that
    your adapter appears to be to the operating
    system.

o   \OS2\DLL\DISPLAY.DLL

  - In previous release of the OS/2 operating
    system, this file was the PM display driver.
    Some 16-bit printer drivers made calls
    directly to this file.  Because the graphic
    subsystem is now 32-bit, those printer drivers
    that make calls directly to this file will
    fail.  Consequently, this file is now the PM
    Printer Raster Engine (PMPRE) and contains
    those functions necessary to provide printer
    support.  Because there are existing printer
    drivers that make calls to the file, PMPRE
    is installed as DISPLAY.DLL.  If you want to
    use a display driver named DISPLAY.DLL,
    use the normal install procedure, and then
    the operating system will detect that the
    .DLL is a display driver and not the
    Printer Raster Engine.

  - The 32-bit graphic subsystem has adopted
    the convention of storing the name of the
    PM display driver in the SYSTEM.INI file.
    The display driver selected at installation
    is recorded as the current and default
    driver.

    The display driver information is saved
    under the application name "PM_DISPLAYDRIVERS."
    The string value associated with the keys
    "CURRENTDRIVER" and "DEFAULTDRIVER" are
    the names of the specific display drivers.
    Additionally, the file name of each display
    driver is associated with the driver name as
    a string value and key pair.

    For the 32-bit XGA driver, the following
    information would be stored in the SYSTEM.INI
    file:

    App Name          Keyname       String value  Description

    PM_DISPLAYDRIVERS DEFAULTDRIVER IBMXGA32 default driver
                         name
    PM_DISPLAYDRIVERS CURRENTDRIVER IBMXGA32 current driver
                         name
    PM_DISPLAYDRIVERS IBMXGA32        IBMXGA32 name of the DLL for
                         the 32-bit XGA display
                         driver (.DLL is
                         assumed if not specified.)

   To install a display driver named "XYZGA", whose
   file name was "XYZDISP.DLL", the information would
   be set up as follows:

   App Name         Keyname      String value    Description

   PM_DISPLAYDRIVERS DEFAULTDRIVER XYZGA      default driver
                          name
   PM_DISPLAYDRIVERS CURRENTDRIVER XYZGA      current driver
                          name
   PM_DISPLAYDRIVERS XYZGA       XYZDISP    name of the DLL for
                          the XYZGA display
                          driver (.DLL assumed.

   The current IBM display drivers for the 32-bit graphics
   systems are:

   Driver Name       File Name      Description

   IBMXGA32       IBMXGA32      32-bit XGA driver
   IBMVGA32       IBMVGA32      32-bit VGA driver
   IBMVG132       IBMVG132      16-bit 132 column VGA driver

o   \OS2\DLL\BVHSVGA.DLL

    This file is the Base Video Handler for the
    OS/2 operating system.  Any OS/2 application
    that sets a video mode calls this DLL.  In
    most cases, however, the only application that
    sets any video modes is the PM display driver
    and the MODE.EXE utility program (for setting
    132-column modes).    The first time this DLL
    would be called is after the OS/2 bit-map logo
    appears (PM starts up then).  This DLL is
    specified in the CONFIG.SYS file as the
    following:

      SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA)

    BVHVGA is used to set, save, and restore VGA
    modes; BVHSVGA is used for SVGA modes.

o   \OS2\MDOS\VSVGA.SYS

    This is the virtual video device handler for
    DOS sessions.  All calls to change the video
    mode from a DOS session are handled through
    this driver.  The job of this driver is to
    allow the user to set an SVGA mode, and when
    the user switches away, to save the current
    state of the video adapter (its registers and
    its video RAM).  Then, when the user returns
    to the DOS session, it restores the video
    adapter to its previous state.  When there is
    no .PMI file (SVGA is OFF), this driver acts
    like a VGA driver, except for adapter-specific
    code in it to make sure the VGA modes work
    right on the SVGA adapter.    Therefore, even if
    you do not want SVGA, you will probably want
    VSVGA.

o   \OS2\MDOS\WINOS2\SYSTEM\VGA.DRV
    \OS2\MDOS\WINOS2\SYSTEM\SWINVGA.DRV

    These are the WIN-OS/2 full-screen and
    WIN-OS/2 window session drivers, respectively.
    They determine what resolution WIN-OS/2 uses.


ADDITIONAL SVGA SUPPORT INFORMATION

o   Over time, more display adapters and PC
    systems that offer SVGA will be tested.  Refer
    to the bulletin boards mentioned previously,
    or to the manufacturers, for the latest
    support information.

o   To make use of SVGA modes, you also must
    install Windows and Presentation Manager video
    display drivers.

o   If you experience display errors on an
    SVGA-enabled system, try disabling SVGA
    support by typing SVGA OFF at a command line.
    This will delete the SVGADATA.PMI file.  Then
    restart your system.

o   In some SVGA displays, if you switch to the PM
    desktop while the screen is still drawing, you
    might experience display errors on the PM
    desktop.  Switch back to the SVGA screen,
    allowing the drawing to complete, and then
    switch back to the PM desktop.

o   In the event of a SYS3176 message when
    starting a DOS or WIN-OS/2 command prompt, try
    setting the HW_ROM_TO_RAM setting in the
    session to ON or changing the DOS_RMSIZE
    parameter in the session to 624 from the
    default 640.  If this does not work, the
    VSVGA.SYS fix from IBM might resolve the
    problem.

o   A virtual desktop is a PM display driver that
    uses all of the adapter's video memory to
    store a desktop that is bigger than what is
    actually displayed.  You could have 1024x1024
    of desktop space, with only 640x480 being
    displayed on the screen.  You move to other
    portions of the desktop by dragging the mouse
    to the edge of the screen, which scrolls the
    desktop.  Because of the way OS/2 2.0 is
    designed, this is an extremely quick operation
    and will be very smooth even on the slowest
    video adapters.  The PM driver must be coded
    to support virtual desktops, and Trident is
    currently the only chipset to support it.

o   Trident supports OS/2 2.0 and has SVGA
    Presentation drivers available for their SVGA
    boards.  Trident's support number is
    415-691-9211.  They also have support bulletin
    boards where these drivers are available.  For
    the West Coast, the number is 415-691-1016 and
    for the East Coast, the number is
    203-483-0348.

o   Orchid is working on OS/2 drivers for their
    video adapters.  For more information, you can
    reach Orchid's bulletin board service at:

    -    510-683-0327 for 2400 baud, parameters
    n,8,1
    -    510-683-0555 for 9600 baud, parameters
    n,8,1
    -    ATI now has SVGA drivers for OS/2 2.0.
    Information is available using the ATI
    bulletin board service:

        416-756-4591 (2400 baud, N, 8, 1)


    The file names are ATIOS213.ZIP and
    WIN31ACC.ZIP.
    -    A WIN-OS/2 window session has the ability
    to run Windows Version 3.0 programs on the
    desktop.  The way it is achieved is by
    making a place in the desktop that the
    WIN-OS/2 window session driver writes to.
    Special code must be put into both the
    window session driver and the display
    driver to support this.  Trident has
    produced 800x600/16 WIN-OS/2 window
    session drivers, and has been the only one
    to produce SVGA support for WIN-OS/2
    window sessions so far.
    -    Questions about OS/2 support for adapters
    based on the S3 or TI chipsets have been
    asked.    Adapters which are co-processed
    are the fastest, but also take the longest
    to develop software for.  No manufacturers
    have announced dates yet for support of
    any of these adapters.    You might want to
    contact the manufacturer for further
    information.
    -    In the event of some corruption when
    returning to a WIN-OS/2 full-screen
    session, set your
    VIDEO_SWITCH_NOTIFICATION in the DOS
    Settings to ON.
    -    Even in VGA, games in a DOS full-screen
    session are not optimized.  Set your
    VIDEO_RETRACE_EMULATION in the DOS
    Settings to OFF.
    -    Some DOS applications in a window have
    color corruption.  This is a limitation of
    the VGA desktop.  The color palette of the
    DOS session has to be translated to PM,
    and the 640x480/16 desktop does not offer
    enough colors to do a good translation.
    The best solution is to use a 256 color PM
    driver or run the application in a DOS
    full-screen session.
    -    The graphics of some applications are
    corrupted when displayed in a window.
    These applications are probably using a
    non-standard VGA mode that the adapter can
    support, but that OS/2 2.0 does not.
    -    When you have SVGA ON, you can:
    --  Use 132 column modes in an OS/2
        full-screen session
    --  Take a window with an SVGA image in it
        and paste to the clipboard
    -    To enable the Windows 3.0 SVGA drivers in
    WIN-OS2, update the SYSTEM.INI file to
    point to a new Windows display driver, or
    just copy over the VGA.DRV in the
    \OS2\MDOS\WINOS2\SYSTEM directory.  Keep
    in mind, however, that a Windows session
    in SVGA mode will only work if you have
    set SVGA ON.
    -    Many different SVGA boards have different
    interfaces and chipsets, each with their
    own characteristics.  Some boards perform
    better with SVGA OFF.


DUAL DISPLAYS
_____________

In multiple XGA configurations, when you switch
from DOS to the desktop, your system will not save
and restore the hardware registers.

If your machine has an 8514 Ultra adapter and an
OS/2 2.0 supported SVGA adapter, you will need to
change the DEVICE= statement in your CONFIG.SYS
file from VVGA.SYS to VSVGA.SYS.


LAPTOP LCD OR MONOCHROME PLASMA DISPLAYS
________________________________________

To change the color schemes for OS/2 system
windows and create a more readable display image,
change the Scheme Palette as follows:

1.  Use your Reference Diskette or hardware Setup
    program to set your hardware to VGA color, if
    possible.
2.  Open the System folder.
3.  Select System Setup.
4.  Select Scheme Palette.
5.  Select the monochrome scheme in the right-hand
    column.

This procedure will optimize the color scheme for
gray-scale usage, and also provide a good set of
colors for a VGA desktop presentation.


GRAPHICS
________

Several fonts have been enhanced in OS/2 2.0.
Some existing applications use inappropriate font
metrics to scale their text.  In some cases, the
text becomes clipped because it no longer fits the
available space.


WIN-OS/2 WINDOW AND FULL-SCREEN SESSIONS
________________________________________

When running a WIN-OS/2 full-screen session with
an 8514 adapter in high resolution (8514.DRV)
mode, do not switch to a different session while
an application is updating the screen or
displaying the hourglass.

The following is a procedure for enabling WIN-OS/2
full-screen sessions to run in high-resolution
8514 mode while the Workplace Shell Desktop and
WIN-OS/2 window sessions run in medium-resolution
(VGA) mode.  The procedure assumes you are not
familiar with the SYSTEM.INI and WIN.INI files.

Follow the instructions very carefully.
Otherwise, you could cause your WIN-OS/2 sessions,
both window and full-screen, to become inoperable.

1.  Make backup copies of your SYSTEM.INI and
    WIN.INI files.  DO NOT SKIP THIS STEP.  It is
    assumed that you have a diskette or tape
    backup copy of your system; instructions follow
    for a backup in the directory only.

2.  Back up the SYSTEM.INI and WIN.INI files.

    Open an OS/2 Window from the Command Prompts
    folder in the OS/2 System folder.  At the
    [C:\] prompt, type the following and press
    Enter:

       CD\OS2\MDOS\WINOS2
       COPY WIN.INI WIN.BAK
       COPY SYSTEM.INI SYSTEM.BAK

    Before making changes to the files, be sure
    the desired high-resolution Windows device
    drivers and fonts are loaded in the system.

3.  Check the \OS2\MDOS\WINOS2\SYSTEM directory
    for the desired high-resolution display device
    driver.  In this example, the 8514.DRV device
    driver is used.  Checking this directory
    reveals that this device driver is not loaded.

    The directory C:\OS2\INSTALL\DRIVERS
    needs to be searched for WIN8514 and *F.FON.
    The following shows the sequence of entries:

       DIR C:\OS2\INSTALL\DRIVERS\WIN8514
       DIR C:\OS2\INSTALL\DRIVERS\*F.FON

    No 8514 drivers were in this directory, but one
    of the font files was.  Although the font file
    is not in a bundle of files, it is still in
    packed format and must be unpacked.

    The files are packed with their standard
    target directory coded into the packed file.
    To copy the file to the system disk in the
    proper directory, just run the Unpack utility
    program.

       UNPACK C:\OS2\INSTALL\DRIVERS\SYMBOLF.FON

    This procedure continues until all of the
    scalable fonts are unpacked.  These fonts are:

    o    SYMBOLF.FON
    o    TMSRF.FON
    o    COURF.FON
    o    HELVF.FON

    The WIN8514 file contains the WIN-OS/2
    8514.DRV and three 8514 fonts.

       UNPACK C:\OS2\INSTALL\DRIVERS\WIN8514

    With all of the required driver and font files
    on the system disks, the next step is to
    modify the SYSTEM.INI file.

4.  Edit the SYSTEM.INI file and find the
    following line:

       display.drv=vga.drv

5.  This line specifies the device driver WIN-OS/2
    is to use in full-screen sessions.    Change
    this line to point to the high-resolution
    device driver that was unloaded in the steps
    above. In this example, the device driver is
    XGA.DRV.  The modified line should look like
    the following:

       display.drv=8514.drv

    Both SYSTEM.INI and WIN.INI have font entries
    that must be changed.  In SYSTEM.INI, these
    entries are:

       fixedfor.fon=vgafix.fon
       oemfonts.fon=vgaoem.fon
       fonts.fon=vgasys.fon

    For 8514, these entries must be changed to:

       fixedfor.fon=8514fix.fon
       oemfonts.fon=8514oem.fon
       fonts.fon=8514sys.fon

    In WIN.INI, the entries:

       Symbol 8,10,12,14,18,24 (VGA res)=SYMBOLE.FON
       Helv 8,10,12,14,18,24 (VGA res)=HELVE.FON
       Tms Rmn 8,10,12,14,18,24 (VGA res)=TMSRE.FON
       Courier 10,12,15 (VGA res)=COURE.FON

    Must be changed to:

       Symbol 8,10,12,14,18,24 (8514 res)=SYMBOLF.FON
       Helv 8,10,12,14,18,24 (8514 res)=HELVF.FON
       Tms Rmn 8,10,12,14,18,24 (8514 res)=TMSRF.FON
       Courier 10,12,15 (8514 res)=COURF.FON

When these changes have been made and the INI
files saved, the system is ready for running
Windows applications in WIN-OS/2 window sessions
(VGA mode) and WIN-OS/2 full-screen sessions
(high-resolution mode).

You must delete the following line from the
CONFIG.SYS file:

  DEVICE=C:\OS2\MDOS\V8514A.SYS

On an XGA system, you can change your screen
resolution using the Screen page of the System
object, which is in the System Setup folder.

Notes:

1.  Windows application developers should note
    that their debuggers work in full-screen
    sessions only.  If you have a dual-display
    setup (8514+VGA), configure OS/2 2.0 for the
    8514 as primary display with no secondary
    display.  This will allow your Turbo Debugger
    for Windows (TDW) or CodeView for Windows
    (CVW) to run in a full-screen session on the
    VGA display while the WIN-OS/2 session runs
    full screen on the 8514.  For CVW, make sure
    to use the /8 option.  Quick C runs on the
    same display as WIN-OS/2.  If you use Quick C,
    you don't need a special video configuration.

2.  Configuring OS/2 2.0 in this way will allow PM
    to run on the 8514, and your full-screen
    debugger to run on the VGA.  It also will
    provide a "stereo" effect for all full-screen
    sessions; both the 8514 and VGA displays will
    show the same picture, unless a full-screen
    application takes advantage of video-specific
    features.

Hardware Considerations

The following sections provide information about
hardware device support in OS/2 2.0.

SCSI DEVICES
____________

o   ProCom+ SCSI disk adapters (Micro Channel) are
    not supported by OS/2 2.0.    You should contact
    the manufacturer for any details on OS/2
    support.

o   Some SCSI adapters have jumper pins which can
    be set to either synchronous or asynchronous
    mode. There have been noted problems such as
    no icons appearing or slow hard disk
    performance.  This can be attributed to the
    SCSI adapter and hard disk not being set to
    the same synchronous or asynchronous settings.
    Either way, they must match.  Be sure these
    are set properly.

o   The early versions of the IBM 16-bit SCSI
    adapters may experience problems and report,
    erroneously, that the device is not
    functioning.  This can be corrected by
    replacing the SCSI adapter with an adapter
    with updated microcode.

ADAPTEC AND FUTURE DOMAIN SCSI DEVICE DRIVERS

Device support for the following Adaptec and
Future Domain SCSI adapters is shipped with OS/2
2.0.  When any of the following adapters is
installed in a workstation, its presence is
normally detected automatically, and the
appropriate device support is subsequently
installed.

For reference, the names of the device drivers
that support each adapter are provided in the
following table:

+------------------------+-----------------------+
| SCSI Adapter or     | Device Driver     |
| Interface         |             |
+------------------------+-----------------------+
| Adaptec A/C 6260     | AHA152X.ADD         |
+------------------------+-----------------------+
| Adaptec AHA 1510     | AHA152X.ADD         |
+------------------------+-----------------------+
| Adaptec AHA 1520/1522  | AHA152X.ADD         |
+------------------------+-----------------------+
| Adaptec AHA 1540/1542  | AHA154X.ADD         |
+------------------------+-----------------------+
| Adaptec AHA 1640     | AHA164X.ADD         |
+------------------------+-----------------------+
| Adaptec AHA         |             |
| 1740/1742/1744     |             |
+------------------------+-----------------------+
| (Standard mode     | AHA154X.ADD         |
| operation)         |             |
+------------------------+-----------------------+
| (Enhanced mode     | AHA174X.ADD         |
| operation)         |             |
+------------------------+-----------------------+
| Future Domain      | FD8XX.ADD         |
| TMC-850/860/875/885     |             |
+------------------------+-----------------------+
| Future Domain      | FD16-700.ADD      |
| TMC-1660/1670/1680     |             |
+------------------------+-----------------------+
| Future Domain      | FD16-700.ADD      |
| MCS-600/700         |             |
+------------------------+-----------------------+
| Future Domain      | FD850IBM.ADD      |
| TMC-850IBM         |             |
+------------------------+-----------------------+

The TMC-850/860/875/885 and TMC-850IBM adapters
will not be detected when the adapter's BIOS is
disabled.  You can manually install this support
in your system by following the steps below.

Note:  xxxxxxxx.ADD should be replaced with the
       file name of the device-driver file you
       want to install.

The C:\OS2\INSTALL\DRIVERS directory contains
the ADD files.

1.  Type:  COPY OS2\INSTALL\DRIVERS\xxxxxxxx.ADD \OS2

2.  Add the following line to the CONFIG.SYS file:

       BASEDEV=xxxxxxxx.ADD

3.  Restart the system.


Adaptec 1542B SCSI Card

For this card to run properly, set the default
data rate to 5.


OS2SCSI.DMD DEVICE DRIVER

Older versions of the OS/2 operating system used
the device driver SCSI.SYS.  This has been
replaced by OS2SCSI.DMD.  OS2SCSI.DMD is provided
in the \OS2 directory of the startup partition.
Old CONFIG.SYS entries of the form
"DEVICE=SCSI.SYS" should be replaced by the entry
"BASEDEV=OS2SCSI.DMD."  Normally, this is done
automatically but inspect your CONFIG.SYS file if
you suspect SCSI problems.

The OS2SCSI.DMD device driver is required for a
number of SCSI CD-ROM devices, SCSI Read/Write
Optical devices, and SCSI Tape devices.


SCSI CD-ROM SUPPORT

The SCSI CD-ROM support built into OS/2 2.0 has
some manufacturer-specific dependencies at this
time.  Support has been verified for IBM and
Toshiba SCSI CD-ROM drives.  If your CD-ROM is
either SCSI with no other devices attached or is
non-SCSI, you might get it to work by using an
external DOS session (VMBOOT by using the DOS
Program setting, DOS_STARTUP_DRIVE ).  Information
about the support and verification of additional
manufacturers' drives will be made available at a
later date.


SCSI REMOVABLE MEDIA SUPPORT

Full-function support is not yet available for
SCSI hard disk drives that support removable
media.    Examples of this class of device include
the Bernoulli drives manufactured by IOMEGA, and
the removable-media drives manufactured by SyQuest
Technology.

Although OS/2 2.0 recognizes these drives, it will
treat media as large diskettes.  You will be able
to format for the FAT file system only.  You will
not be able to partition or start up from the
media, and partitioned media will not be
recognized.

If the IBMINT13.I13 driver is used to control
these units, the drive will be treated as a hard
disk.  In this case, the cartridge must be in the
drive at startup time, and you will need to use
the Shutdown procedure to remove the cartridge
from the drive.

Bernoulli 44MB and 89MB drives work if connected
to Adaptec, Future Domain, IBM, or any adapter
other than the Bernoulli adapter.  The drive will
work as a large diskette but cannot be used as a
startup drive.    Customers should call IOMEGA for
status on an update for their adapter.

If Seagate SCSI controller model ST-01 or ST-02 is
present, it must be the only disk controller
present.  Conflicts exist between this controller
and MFM and RLL disk controllers.

If you experience some problems with a Western
Digital WD7000 SCSI adapter, contact Future Domain
for assistance.


SCSI USAGE NOTES

Following are a number of notes about usage, and
about potential compatibility problems with the
microcode levels on various adapters and devices.

Adapter:       All Adaptec adapters

Note:

           (1) Might produce contention problems with the
           diskette drive controller on fast computers.
           (2) Do not support drives of 1GB or larger.
           (3) Must have SCSI hard disks configured as
           SCSI target ID 0 or 1 to be able to
           start up from that hard disk.

Adapter:       IBM SCSI

Note:           If you experience intermittent data
           errors with older IBM SCSI
           adapters, you might need to upgrade
           them.  If you have IBM SCSI FRU P/N
           15F6561, obtain ECA032.    If you
           have IBM SCSI with cache FRU P/N
           64F0124, obtain ECA027.    These
           adapters are standard in 8565
           models 061 and 121 and 8580 models
           121, 131, A21, and A31.

Adapter:       Adaptec AHA-154x

Drive:           IBM 0661 - 320MB SCSI

Note:           Adapter BIOS will not recognize the
           drive as Target 0 or 1 (Drives 80,
           81).  For OS/2 2.0, the drive can
           be used but not as a startup drive.

Adapter:       Adaptec AHA-174x

Drive:           IBM WDS-3180 - 80MB SCSI, IBM
           WDS-3160 -160MB SCSI

Note:           Adapter will not recognize these
           drives when configured in standard
           mode (AHA-154x emulation).
           Instead, the AHA-174x adapter
           should be configured in enhanced
           mode.  This mode is supported by
           the OS/2 2.0 drivers, and the
           problem does not occur when the
           adapter is operating in enhanced
           mode.

Adapter:       Future Domain TMC-850/860/875/885
           w/BIOS revision level 7.0.  Future
           Domain TMC-1660/1670/1680 w/BIOS
           revision level 2.0.

Note:           When the Future Domain adapter is
           controlling the startup diskette,
           it will produce the message, "Disk
           read error has occurred" when you
           attempt to start the Installation
           Diskette.  Contact Future Domain
           for a free BIOS upgrade.

Adapter:       Seagate ST-01, ST-02

Note:           Causes contention with MFM and RLL
           drives.    The ST-01 or ST-02 should
           be the only drive controller
           installed.  This problem is being
           investigated.

Adapter:       Western Digital WD7000

Note:           Newer adapters seem to be supported
           while older ones are not.  Western
           Digital is now owned by Future
           Domain.    Contact Future Domain for
           assistance.


AMI AND CEI SCSI ADAPTERS

AMI "Fast Disk" and AMI "Fast Disk II" SCSI
adapters are incorrectly recognized as Adaptec
adapters.  The CEI Cumulus C5640B SCSI Micro
Channel adapter has the same problem.  If you have
one of these adapters in your system, do the
following:

o   Delete from the CONFIG.SYS file any
    line with "BASEDEV=AHA1xxx.ADD" (where x can
    be any character).
o   Ensure the line, "BASEDEV=IBMINT13.I13,"
    appears in the CONFIG.SYS file.


ALWAYS TECHNOLOGY SCSI

If you are experiencing OS/2 problems
(such as a TRAP 000D) and your system has an
Always Technology IN-2000 SCSI adapter, the
BIOS on the adapter might be the
problem.  If the BIOS revision level is 3.06A or
3.20 (as shown during the system self-test), you
should get the BIOS on the adapter upgraded.  The
current BIOS level is VCN:1-02 and works with OS/2
2.0.  If you require this upgrade, you might also
need an upgrade to a companion 8-pin serial PROM
chip which must have a revision level of 2.5-2.7.
Always Technology support can be reached at
818-597-9595.



ADDITIONAL DEVICE SUPPORT INFORMATION
_____________________________________

The following contains useful information about
OS/2 2.0 support for the specified devices.


HP SCANJET

On a PS/2 computer, you must use the
Reference Diskette to set the adapter to ROM
addresses C8000-CBFFF and I/O address to 268-26F.
In both cases, you also need to set the DOS
Setting for the DOS session for EMS_FRAME_LOCATION
to AUTO.


TAPE DRIVES (ADAPTER OR SCSI)

The only tape drives that have been tested at this
point are IBM tape drives.  If no other device is
connected to the SCSI bus on its adapter or the
tape adapter, then you might be able to get your
drive to work in an external DOS (VMBOOT) session.

If the tape drive worked under OS/2 version 1.x
and the device is written to ASPI, IBM is
currently working on support for your device.  IBM
does not provide third-party device drivers for
peripherals.  Refer to your peripheral
manufacturer for OS/2-specific support.


TAPE DRIVES (DISKETTE BASED)

IBM or IRWIN tape drives are supported.
Applications are PMTAPE or PS2TAPE.  Easy Tape
from Maynard Backup Systems is scheduled for
future release.  Contact Maynard for information.


TAPE DRIVES (COLORADO JUMBO)

For Colorado Jumbo tape drives connected to a
floppy controller, you must setup a DOS Startup
session from a diskette image and run the tape
backup program from it.  To do this, you need to
refer to the topic "Starting DOS from an image
file" in the Master Help Index.

The Colorado Jumbo Tape program allows you to
specify some hardware and software settings to be
used when backing up files.  The Concurrent
Disk/Tape operation option must be set to No.  To
change the option, start the program and select
the Utilities menu (F3); then select Software
Setups (F6).  Change the option to N.

The Colorado company is developing an OS/2-specific
version of their software.  For more information,
please contact Colorado.

TAPE DRIVES (MOUNTAIN TAPE BACKUP)

The Mountain company is developing OS/2-specific
version of their software.  For more information,
please contact Mountain at 800-458-0300.


LOGITECH 3-BUTTON MOUSE

The Logitech 3-button bus mouse is supported as a
2-button mouse.  It is treated as a Microsoft
2-button bus mouse.

A Logitech serial mouse with 3 buttons behaves as
expected in DOS sessions.  In a Presentation
Manager session, however, there might be different
and more limited functions assigned to the
buttons.  There are no standards for the functions
of 3-button mice.


AOX SYSTEMS

If your computer has an Aox add-in processor card
and you encounter problems starting up your OS/2
system, you can call Aox support and ask for
the latest "flash-prom" code upgrade.

PERSTORE

PerStore disk controllers are not supported.


PARALLEL-PORT-ATTACHED DEVICE

o   If you have a parallel device (for example, a
    tablet system, LAN adapter, or SCSI device)
    that does not work in a DOS session, it might
    be because interrupt IRQ7 is not reflected in
    the session.  Your device might attempt to use
    the parallel-port feature and is prevented
    from doing so.  OS/2 developers are working on
    a solution for this limitation.

o   Some security devices (known as dongles)
    attached to a parallel port do not work
    properly with OS/2 2.0.  The DOS application
    that uses the device can start from one DOS
    session only.  An error message appears when
    you try to start additional copies of the
    application.  You can press Ctrl+Alt+Print
    Screen to release access to the parallel-port
    software prior to starting the second copy of
    the DOS application.

    Note:  Please refer to the General System
       Considerations section for a
       description of how to configure
       your printer object to enable more
       than one DOS session access to the
       parallel port with a security
       device attached to it.

o   Make sure you are using cables that are
    properly shielded and wired.  (For more
    information, refer to "Unable to Print")


PROBLEMS WITH FAX ADAPTERS

When certain fax adapters are operating as
ordinary modems, they might operate correctly yet
fail to work correctly as a fax device in a DOS
session.  The probable cause of the trouble is the
VCOM.SYS device driver.  VCOM.SYS might be
introducing timing distortions into those hardware
commands that are used to control the fax device
but are not a part of normal asynchronous
communications.

Because there are no standards established for fax
controls, it might be that the only solution is to
acquire an OS/2-based fax device driver and
application software.  Your fax adapter
manufacturer might have information on sources and
availability of OS/2 based software.

Without purchasing new software, you can try
removing the VCOM.SYS statement from your
CONFIG.SYS file.  This might allow your fax
adapter to work properly but might have other
undesirable side effects.  One of the functions of
VCOM.SYS is to provide a performance assist.
Without VCOM.SYS, you might have to use a reduced
baud rate.  Also, some applications, such as
Prodigy, will not run without it.  Therefore,
while removing VCOM.SYS is OK in some instances,
it might not be the right action for you.


PS/2 EXTERNAL 5.25-INCH 1.2MB DISKETTE DRIVE

If you cannot get the external 5.25-inch 1.2MB
diskette drive to work, install
the device driver that comes with the drive into
the \OS2 directory in the startup partition.  The
device driver is called EXT5DD.SYS.  Change your
CONFIG.SYS file statement to read \OS2\EXT5DD.SYS
instead of \OS2\EXTDSKDD.SYS.


NOTICES
________

References in this publication to IBM products,
programs, or services do not imply that IBM
intends to make these available in all countries
in which IBM operates.    Any reference to an IBM
product, program or service is not intended to
state or imply that only IBM's product, program,
or service may be used.  Any functionally
equivalent product, program, or service that does
not infringe any of IBM's intellectual property
rights or other legally protectible rights may be
used instead of the IBM product, program, or
service.  Evaluation and verification of operation
in conjunction with other products, programs, or
services, except those expressly designated by
IBM, are the user's responsibility.

IBM may have patents or pending patent
applications covering subject matter in this
document.  The furnishing of this document does
not give you any license to these patents.  You
can send license inquiries, in writing, to the IBM
Director of Commercial Relations, IBM Corporation,
Purchase, NY 10577.


TRADEMARKS AND SERVICE MARKS
____________________________

The following terms, denoted by an asterisk (*),
used in this publication, are trademarks or
service marks of the IBM Corporation in the United
States or other countries:

AT              IBM
IBMLINK           Micro Channel
PCAT              PC/XT
Personal System/2     PS/2
Proprinter          ExecJet
Presentation Manager  Operating System/2
OS/2              Workplace Shell
WIN-OS/2          XGA
XT

The following terms, denoted by a double asterisk
(**), used in this publication, are trademarks of
other companies as follows:

Trademark          Owner

Boca Research          Boca Research, Inc.
Adobe              Adobe Systems Inc.
Adobe Type Manager    Adobe Systems Inc.
Aox              Aox Corporation
AutoCAD           AutoDesk, Inc.
Borland C++          Borland International, Inc.
Canon              Canon Kabushiki Kaisha
Central Point Backup  Central Point Software, Inc.
Corel              Corel Systems
CorelDRAW          Corel Systems
CompuServe          CompuServe Inc.
CodeView          Microsoft Corporation
Control Room          Ashton-Tate Corporation
Crosstalk          Digital Communications
              Associates, Inc.
dBase              Ashton-Tate Corporation
Distinct          Distinct Corporation
DynaComm          Future Soft Engineering, Inc.
Epson              Seiko Epson Kabushiki Kaisha
Everex              Everex Systems
Fastback Plus          Fifth Generation Systems, Inc.
FastLynx          Rupp Corporation
Framework III          Aston-Tate Corporation
Hewlett-Packard       Hewlett-Packard Company
HP              Hewlett-Packard Company
Intel              Intel Corporation
LapLink           Traveling Software, Inc.
LaserJet          Hewlett-Packard Company
Logitech          Logitech, Inc.
Lotus              Lotus Development Corporation
Lotus Magellan          Lotus Development Corporation
MAGICorp          MAGICorp Ltd.
Mathcad           MathSoft, Inc.
Micrografx          Micrografx Inc.
Microsoft          Microsoft Corporation
Microsoft Excel       Microsoft Corporation
MS              Microsoft Corporation
MS Bookshelf          Microsoft Corporation
MS Excel          Microsoft Corporation
MS Flight Simulator   Microsoft Corporation
MS Money          Microsoft Corporation
Microsoft Windows     Microsoft Corporation
More Windows          Aristosoft, Inc.
National Geographic   National Geographic Society
NEC              NEC Corporation
Norton Backup          Peter Norton Computing, Inc.
Norton Utilities      Peter Norton Computing, Inc.
Orchid              Orchid Technology Inc.
Omnipage Professional Caere Corporation
PaintJet          Hewlett-Packard Company
Paradox           Borland International, Inc.
Peachtree          Peachtree Software, Inc.
Peachtree Complete    Peachtree Software, Inc.
Persuasion          Aldus Corporation
PFS              Software Publishing Corporation
PFS First Choice      Software Publishing Corporation
Phar Lap          Phar Lap Software, Inc.
PostScript          Adobe Systems Inc.
Powergraph          STB Systems Inc.
Publishers PowerPak   Atech Software
Prodigy           Prodigy Services Company
Quicken for Windows   Intuit Company
Realizer          Within Technologies, Inc.
SideKick          Borland International, Inc.
SmartFax          American Data Technology, Inc.
TI              Texas Instruments Inc.
Tseng              Tseng Laboratories Inc.
Turbo C++          Borland International, Inc.
Turbo Pascal          Borland International, Inc.
Windows           Microsoft Corporation
Winfax Pro          Delrina Technology Systems, Inc.
Wing Commander          Origins Systems, Inc.
WordPerfect          WordPerfect Corporation
8514/ULTRA          ATI Technologies, Inc.

IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR
IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES
OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT.  BY FURNISHING THIS
DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED
PATENTS OR COPYRIGHTS.

Copyright IBM Corporation, 1992, all rights
reserved.