Power-Programmierung/CD2.mdf/doc/os2techn/os2tnt.inf

OS/2 Help File | 1992-06-22 | 155.7 KB | 4,373 lines

ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ

First Edition (June 1992)

The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS
MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states
do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.

This publication could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time.

It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country.  Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.

Requests for technical information about IBM products should be made to your
IBM Authorized Dealer or your IBM Marketing Representative.


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


ΓòÉΓòÉΓòÉ 2.1. Trademarks and Service Marks ΓòÉΓòÉΓòÉ

Terms denoted by a single asterisk (*) in this publication are trademarks of
the IBM Corporation in the United States and/or other countries.  These terms
include:

IBM
Micro Channel
Operating System/2
OS/2
PS/2
WIN-OS/2
Workplace Shell
XGA

Terms denoted by a double asterisk (* *) in this publication are trademarks of
other companies.  Other trademarks appearing in this publication are owned by
their respective companies.

Microsoft, MS Bookshelf, MS Excel, MS Flight Simulator, MS Money, and Windows
are trademarks of Microsoft Corporation.

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.


ΓòÉΓòÉΓòÉ 3. About This Book ΓòÉΓòÉΓòÉ

This book contains useful tips and techniques that might be helpful when using
your OS/2 2.0 product.  In addition, it contains application compatibility
information.


ΓòÉΓòÉΓòÉ 3.1. Who Should Read This Book ΓòÉΓòÉΓòÉ

This book is provided as an information source for the people installing and
using OS/2 2.0. Some of the information in this book is intended for the more
advanced user or for the user already familiar with various functions provided
with OS/2 2.0.


ΓòÉΓòÉΓòÉ 3.2. How This Book Is Organized ΓòÉΓòÉΓòÉ

This book is organized as follows:

 o Introduction, provides a summary of the highlights of OS/2 2.0.

 o Service and Support Information, provides a summary of the electronic and
   voice support for the OS/2 2.0 product.

 o Installation Considerations, contains considerations before, during, and
   after installing OS/2 2.0.

 o OS/2 Workplace Shell, describes tips you might find useful when using the
   OS/2 Workplace Shell.

 o Printing Considerations, includes printing tips and information on specific
   printers.

 o Application Considerations, discusses general considerations and specific
   applications that need special attention when using the OS/2 product.

 o Performance, lists performance considerations that you should be aware of.

 o Windows Version 3.0 Programs Support discusses considerations when running
   in WIN-OS/2 sessions.

 o Video/Graphic Support, discusses SVGA support.

 o Hardware Considerations, provides information about hardware device support.


ΓòÉΓòÉΓòÉ 4. Introduction ΓòÉΓòÉΓòÉ

In  OS/2 Version 2.0,  IBM  performed the most comprehensive testing ever done
on any version of the OS/2 operating system. This included extensive DOS,
Windows, and OS/2 application compatibility validation in addition to stress,
usability, and performance testing.  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.

The information was largely collected during the final comprehensive system and
compatibility testing phases, which involved over 30,000 users of early
versions. We want to share this information with you.

     IMPORTANT NOTE

     This publication is an update to the information in the 03/92 README that
     is located in the Information folder on the desktop. It provides
     corrections to the 03/92 README as well as additional tips and techniques
     to help you run your OS/2 2.0 operating system.


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

 The OS/2 Support Line provides toll-free voice support for questions related
 to installing or using OS/2 2.0.  The voice support is available for a
 no-charge, no-obligation, 60-day trial.  To take advantage of this special
 offer, and receive additional details about the OS/2 Support Line, call
 1-800-237-5511.

 Note:  The OS/2 Support Line is not available For the Extended Services for
        OS/2 product or the Local Area Network Server Version 2.0 product. For
        these products, contact your place of purchase. only for defect
        support.

 For general IBM OS/2 product information and availability, call 1-800-3IBMOS2.


ΓòÉΓòÉΓòÉ 6. Installation Considerations ΓòÉΓòÉΓòÉ

This chapter has information about installing OS/2 2.0. For example, it
describes things you might need to consider before, during, or immediately
after installation, such as:

 o Upgrading from another operating system

 o Reformatting

 o Using non-IBM devices, such as a Logitech mouse

 o Handling problems during installation.


ΓòÉΓòÉΓòÉ 6.1. Upgrade Version of OS/2 2.0 ΓòÉΓòÉΓòÉ

The upgrade version of OS/2 2.0 (for DOS,  Windows, and OS/2 1.x) is slightly
different from the full-purchase-price version of OS/2 2.0. You must have an
operating system installed on your hard disk before you can install the upgrade
version.

If you formatted your hard disk before you attempted to install the upgrade
version (for example, because you purchased a larger hard disk), you must put
an operating system on the hard disk. For example, if your previous operating
system was DOS, start your computer with a DOS diskette, and then type the
following at the DOS command prompt:

   FORMAT C: /S
Then proceed with the installation of the upgrade version of OS/2 2.0.

If installation Diskette 1 in your upgrade package is write protected, turn the
diskette over and slide the black tab up at the bottom right side so that the
tab covers the square hole in the diskette. If the tab is missing, place a
piece of tape over the hole. Covering the hole enables information to be
written to the diskette during installation.


ΓòÉΓòÉΓòÉ 6.2. Reformatting ΓòÉΓòÉΓòÉ

Following is information about when you should and should not reformat while
you are installing OS/2 2.0.


ΓòÉΓòÉΓòÉ 6.2.1. During Installation ΓòÉΓòÉΓòÉ

It is a good idea to reformat during the installation of OS/2 2.0.

 o You must reformat if you are installing over any beta version 2.0 except for
   OS/2 2.0 Limited Availability (6.177H).
 o If you formatted during installation, and the installation failed, reformat.
 o If you did not format during installation and the installation failed, try
   to install again without formatting.  If the installation fails again, you
   might want to back up any data files you need from the drive on which you
   want to install, and then reformat.


ΓòÉΓòÉΓòÉ 6.2.2. After Successful Installation ΓòÉΓòÉΓòÉ

If you successfully install OS/2 2.0, you should NOT install it again unless
you are advised to do so by an IBM dealer or representative.  After
installation, you can add any feature you want by double-clicking on OS/2
System, System Setup, and then Selective Install.


ΓòÉΓòÉΓòÉ 6.3. Limited Availability Version ΓòÉΓòÉΓòÉ

If you previously installed the OS/2 2.0 Limited Availability version of OS/2
2.0 and installed OS/2 2.0 without reformatting, you must update the OS/2
System Editor and Clipboard Viewer PATH statements in the CONFIG.SYS file.
Change them so they read as follows:

\OS2\APPS\E.EXE

\OS2\APPS\CLIPOS2.EXE
Also, you might not be able to delete existing program associations. If this
occurs, make a copy of the program object that has the associations; then
discard the original.


ΓòÉΓòÉΓòÉ 6.4. HPFS ΓòÉΓòÉΓòÉ

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


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


ΓòÉΓòÉΓòÉ 6.4.2. HPFS Support Not Added during Installation ΓòÉΓòÉΓòÉ

Support for HPFS was not added to your system if you installed OS/2 2.0 using
either Install all features or Install preselected features, and your system:

 o Has 6MB or less of memory, and
 o Did not previously have HPFS support.

 To install HPFS support after installation of OS/2 2.0, double-click on
 Selective Install in the System Setup folder.


ΓòÉΓòÉΓòÉ 6.5. Partitioning ΓòÉΓòÉΓòÉ

It is ideal for OS/2 2.0 to be in a partition by itself, unless you are
installing Dual Boot, in which case you must have DOS on the system before you
install OS/2 2.0.

The OS/2 partition should be approximately 40-50MB if you want the default
installation and the swap drive on the same partition.  The less memory you
have, the larger the swap file you need, and, therefore, the larger the
partition should be.

If you partition the drive, you should have at least 2 partitions, one for OS/2
2.0 and one for your data.


ΓòÉΓòÉΓòÉ 6.6. CONFIG.SYS (Automatic Update) ΓòÉΓòÉΓòÉ

Some device-driver statements might not be copied to your new CONFIG.SYS file
with a REM statement if you click on Automatically update CONFIG.SYS and
AUTOEXEC.BAT during installation.  Instead, click on User edit CONFIG.SYS and
AUTOEXEC.BAT so you can copy your device-driver statements to your new
CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 6.7. Mouse Does Not Work ΓòÉΓòÉΓòÉ

Following is information about getting a mouse to work.


ΓòÉΓòÉΓòÉ 6.7.1. Mouse Driver (Changing Default) ΓòÉΓòÉΓòÉ

During installation, do not make changes in the Mouse window unless it is
displayed while Diskette 2 is in the installation drive.  If the Mouse panel is
not displayed for you, OS/2 2.0 has been able to determine the correct device
driver for your mouse.

For example, if you have a Logitech PS/2 mouse or serial mouse-series M, the
installation program will correctly select the PS/2 Style Pointing Device
driver, not the Logitech Serial Mouse driver.


ΓòÉΓòÉΓòÉ 6.7.2. Logitech Mouse Not Working After Installation ΓòÉΓòÉΓòÉ

If you have a Logitech PS/2 mouse or a Logitech serial mouse, series M, and it
does not work after installation, you might have installed the Logitech Serial
Mouse driver, which is not the correct driver.  To select the correct mouse
driver, use the keyboard to select OS/2 System, System Setup, Selective
Install, Mouse in the System Configuration window, and then OK.  Those steps
install the default mouse driver, the PS/2 Style Pointing Device driver, that
is required by those mice.


ΓòÉΓòÉΓòÉ 6.7.3. Logitech Mouse Not Working after Dual-Boot Switch from DOS ΓòÉΓòÉΓòÉ

If your Logitech mouse is not working on a Dual-Boot system after you run DOS
and switch to OS/2 2.0, your mouse might be running in a mode set by a
DOS-based mouse device driver.  To correct the problem, type the following at
the DOS command prompt:

   MOUSE PC
This will reset the mouse to a mode that is recognized by OS/2 2.0.  Then type
the following:

   BOOT /OS2
OS/2 2.0 should start and your mouse should work.

You can perform this procedure automatically by creating a batch file for the
commands you would type (MOUSE PC and BOOT /OS2).  For information about
creating a batch file, refer to the online Master Help Index.


ΓòÉΓòÉΓòÉ 6.7.4. HP Mouse ΓòÉΓòÉΓòÉ

To install an HP mouse, do the following:

  1. Accept the default mouse driver during the installation of OS/2 2.0.
  2. Copy HILMOU.SYS and NOEXBIOS.SYS to the C:\OS2 directory. (Those files are
     supplied by Hewlett-Packard.)
  3. Modify your CONFIG.SYS file so it contains the following lines in the
     order shown:

             DEVICE=C:\OS2\NOEXBIOS.SYS
             DEVICE=C:\OS2\HILMOU.SYS
             DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$

 If you do not have the diskette that contains the required files, contact the
 dealer from whom you purchased the mouse. Or, you can contact Hewlett-Packard
 Company customer service.


ΓòÉΓòÉΓòÉ 6.7.5. Other Mouse Not Working after Dual-Boot Switch from DOS ΓòÉΓòÉΓòÉ

If your mouse works when you first turn on your computer, but it does not work
when you switch from DOS to OS/2, your mouse might be emulating (acting like)
another kind of mouse.  For example, your mouse might be emulating a Logitech
mouse.  Refer to the documentation that came with your mouse to see if it has a
command for changing the mode.  If so, try to reset the mouse to a mode that is
recognized by OS/2 2.0.


ΓòÉΓòÉΓòÉ 6.8. LAN Installation ΓòÉΓòÉΓòÉ

To install across a local area network (LAN), purchase IBM LAN Installation
Utility/2 (LIU/2), program package number 5799-PTC.  To order the package,
contact your IBM representative or an IBM dealer. The one-time charge is
$350.00; the license charge is $300.00.


ΓòÉΓòÉΓòÉ 6.9. Response File Installation ΓòÉΓòÉΓòÉ

Following is additional information for the "Copying the Response File to a
5.25-Inch Diskette" section of Chapter 5 in the OS/2 2.0 Installation Guide.

If you are installing OS/2 2.0 in a  non-Micro  Channel computer:

 o Delete the following additional files from your copy of Diskette 1:

    IBM2*.ADD
    *O2.SYS

 o Delete the following additional statements from the CONFIG.SYS file on your
   copy of Diskette 1:

    BASEDEV=IBM2FLPY.ADD
    BASEDEV=IBM2ADSK.ADD
    BASEDEV=IBM2SCSI.ADD

 If you are installing OS/2 2.0 in a Micro Channel computer:

 o Delete the following additional files from your copy of Diskette 1:

    IBM1*.ADD
    *01.SYS

 o Delete the following additional statements from the CONFIG.SYS file on your
   copy of Diskette 1:

    BASEDEV=IBM1FLPY.ADD
    BASEDEV=IBM1S506.ADD


ΓòÉΓòÉΓòÉ 6.10. Problems with Installation ΓòÉΓòÉΓòÉ

The following information provides solutions for problems you might encounter
during or after installation.  They are:

 o Problems at the LOGO screen
 o Problems while using specific installation diskettes (they are referenced by
   number)
 o Messages that are displayed on the screen
 o Constant beeping while changing diskettes
 o A white screen during or after installation
 o Old Version of BIOS
 o Patch needed for ZEOS notebook


ΓòÉΓòÉΓòÉ 6.10.1. LOGO Screen Problems ΓòÉΓòÉΓòÉ

Following are problems that can occur at the LOGO screen during or after
installation.


ΓòÉΓòÉΓòÉ 6.10.1.1. With OAK Video Adapter (during Installation) ΓòÉΓòÉΓòÉ

If the installation procedure stops immediately after the LOGO screen is
displayed and you have an OAK video adapter, change the video adapter to 8-bit
mode and place it into an 8-bit adapter slot.

If the problem continues, you can change the OS2LDR file with the procedure
that follows.  You must have a version of DOS on a DOS diskette or on your hard
disk. To change the OS2LDR file, do the following:

  1. Make a backup copy of installation Diskette 1. (You can use the DOS
     DISKCOPY command to make the backup.) Do not change the file on your
     original OS/2 2.0 installation Diskette 1.

  2. Start DOS from diskette or your hard disk.

     Note:  Make sure that DEBUG.COM is on your hard disk.

     If DEBUG.COM is on your hard disk, change to the appropriate directory, if
     necessary.

  3. Insert the backup copy of Diskette 1 in drive A. Type the following at the
     DOS command prompt:

             DEBUG A:\OS2LDR
     and press Enter.

  4. Type:

             4f7c
     and press Enter.  CD. will be displayed.

  5. Type:

            90
     and press the Spacebar.  10. will be displayed.

  6. Type:

             90
     and press Enter.

  7. To write changes to the file, type:

             W
     and press Enter.

  8. To end the debug procedure, type:

             Q
     and press Enter.  (If you started DOS from a diskette in drive A, remove
     the backup copy of Diskette 1 from drive A and insert your DOS diskette
     and press Enter.  You will see the DOS prompt).

  9. Restart the installation of OS/2 2.0 using your modified backup copy of
     Diskette 1.


ΓòÉΓòÉΓòÉ 6.10.1.2. With Future Domain SCSI Controller (after Installation) ΓòÉΓòÉΓòÉ

If you have a Future Domain 16xx SCSI controller, you might have installed OS/2
2.0 successfully, but then found a problem the next time you started OS/2 2.0.
If the system stopped running with the LOGO screen displayed, there might be a
conflict with the interrupt settings of your hardware devices. Check all
interrupt-request (IRQ) settings on all your hardware devices and make sure
that each one is using a unique IRQ.  Future Domain controllers are shipped
from the factory preset to use IRQ5.  IRQ5, however, is the interrupt that is
normally assigned to LPT2.  Also, it is common for IRQ5 to be used by sound or
communications adapters.  You might not see a problem immediately because of
interrupt conflicts, but eventually they can cause strange results.

Refer to Hardware Considerations for more information about setting IRQ levels.


ΓòÉΓòÉΓòÉ 6.10.2. Diskette Problems by Number ΓòÉΓòÉΓòÉ

Following are solutions for problems that occur while you are using specific
installation diskettes during installation (for example, Diskette 1).

 o Diskette 1 Problem

   If the installation procedure stops while Diskette 1 is in the diskette
   drive of a non-IBM computer, there might be a problem with the features of
   the hard disk drive controller.  If the controller has on-board disk
   caching, disable the caching.  If the controller can do asynchronous memory
   refreshes, turn off that feature.

 o Diskette 3 Problem

   If the installation program keeps prompting you to insert Diskette 3, you
   have a 1.44MB diskette drive that can work in either IBM PC/XT mode or IBM
   PC/AT mode.  You need to change the mode from XT to AT by changing the
   jumper for pin 34 on your 1.44MB diskette drive.  Refer to the information
   that came with your computer or diskette drive to find out how to make the
   change.

 o Diskette 6 (Problem after, with VGA Display)

   If the installation procedure stops after Diskette 6, the adapter for a VGA
   display might be causing the problem.  If you have a VGA display, refer to
   the Guide to Operations for your VGA adapter. If the adapter has auto-sense
   capability, find out how to turn off this feature. If the adapter has a
   resolution available other than 640x480, make sure the mode on the adapter
   is set to 640x480 mode.

 o No Diskette 16 (3.5-Inch Installation)

   If you are installing the 3.5-inch version of OS/2 2.0, and the installation
   prompts you to insert Diskette 16, your drive A is not being recognized as a
   1.44MB drive.  You must set the Basic Input/Output System (BIOS) to
   recognize drive A as 1.44MB.  Refer to the documentation that came with your
   computer to find out how to do this.


ΓòÉΓòÉΓòÉ 6.10.3. Messages on Screen ΓòÉΓòÉΓòÉ

Following are solutions you can try when you see specific information displayed
on the screen during installation.  For example, there is something you can do
if C0000005 is displayed when the installation procedure stops.


ΓòÉΓòÉΓòÉ 6.10.3.1. C0000005 Displayed on Screen ΓòÉΓòÉΓòÉ

If you see C0000005 displayed on the screen the first time you start the system
after installation, call the OS/2 Technical Support Center at 800-237-5511 and
request a corrected version of the BVHSVGA.DLL file.


ΓòÉΓòÉΓòÉ 6.10.3.2. COUNTRY.SYS File Cannot Be Found ΓòÉΓòÉΓòÉ

Following are solutions to try when OS/2 2.0 displays a message that it cannot
find the COUNTRY.SYS file

 o If you have a PS/2 P70, on PS/2 P70 contact your IBM customer engineer or
   computer dealer and request the engineering change announcement "ECA068".

 o Find out if a diskette drive or a hard disk drive controller has an
   additional device attached to it, such as a tape backup.  Disconnect the
   device, if possible.

 o Make sure the diskette drive or hard disk drive controller resides at its
   own IRQ level. Refer to the operations manual that came with your computer
   for information about the IRQ setting.

   Refer to Hardware Considerations for more information about setting IRQ
   levels.


ΓòÉΓòÉΓòÉ 6.10.3.3. SYS1200 and EC=00BF on Screen with Dual Boot ΓòÉΓòÉΓòÉ

If you see error message SYS1200 while attempting to Dual Boot to DOS and you
have error code EC=00BF (meaning that the DOS environment cannot be created),
check your CONFIG.SYS file.  Make sure your virtual DOS device drivers are
listed correctly in your CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 6.10.4. Computer Beeps Constantly ΓòÉΓòÉΓòÉ

If your computer beeps constantly while you are changing diskettes during
installation, you might have a defective diskette drive controller or cable.
Check the controller and cable for damage, and also check all their
connections.


ΓòÉΓòÉΓòÉ 6.10.5. White Screen with Disk Light On Constantly ΓòÉΓòÉΓòÉ

If you are installing OS/2 2.0 on a fast 486 ISA-bus computer, you might see a
white screen and the disk light constantly on.  If so, try switching the system
board out of turbo mode, to reduce the speed of the computer.  Refer to the
documentation that came with your computer to find out how to change the mode.


ΓòÉΓòÉΓòÉ 6.10.6. White Screen after Installation ΓòÉΓòÉΓòÉ

If the display screen is white after installation and there is no system
activity, set the video adapter to 8 bits and move the adapter to an 8-bit
slot.  If possible, disable the auto-switching capability of the video adapter.
Refer to the documentation that came with your video adapter.


ΓòÉΓòÉΓòÉ 6.10.7. White Screen with an ATI Video Adapter ΓòÉΓòÉΓòÉ

If the display screen is white after installation and you have an ATI 8514
Ultra or Graphics Ultra video adapter, you might have an old version of a video
ROM chip on the adapter. Contact ATI at 416-756-0711 to request an update.


ΓòÉΓòÉΓòÉ 6.10.8. BIOS ΓòÉΓòÉΓòÉ

Following is information about systems and system boards that do not support
OS/2 2.0 because of an old version of BIOS. Information is provided about how
to upgrade the BIOS.


ΓòÉΓòÉΓòÉ 6.10.8.1. Phoenix BIOS ΓòÉΓòÉΓòÉ

You must have level 1.02.05D, or later, BIOS from Phoenix to run OS/2 2.0.


ΓòÉΓòÉΓòÉ 6.10.8.2. AMI BIOS ΓòÉΓòÉΓòÉ

If the installation procedure stops while you are using the first few
installation diskettes, or you see SYS2025 or SYS2027 displayed on the screen,
you might have a problem because of BIOS from American Megatrends, Inc. (AMI)
AMI. To find out, do the following:

  1. Watch the screen after you turn on the computer.  Look for the name AMI.
  2. If the BIOS is from AMI, look for one of the following statements:

    o For AMI BIOS and AMI BIOS plus, you will see:

               aaaa-bbbb-mmddyy-Kc

    o For AMI Hi-Flex BIOS, you will see:

               ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c

  3. The AMI BIOS must be dated 0509991 or later.  In the previous statements,
     the BIOS date is indicated by mmddyy. Check your computer screen to see if
     the date is acceptable. If the BIOS is an older version, contact the
     dealer at your place of purchase for information about upgrading the BIOS.
     Or, contact Washburn & Co., the distributors of AMI BIOS products, at
     716-248-3627.
  4. If the BIOS has an acceptable date, you might have a problem because the
     keyboard controller is an old version.  The controller must be version KF
     or later (for example, KG). In the previous statements, the keyboard
     controller is indicated by Kc and c.  Check your computer screen to see if
     the keyboard controller is an acceptable version.  If it is not, contact
     your computer dealer or Washburn & Co..
  5. If the BIOS and keyboard controller are acceptable versions, you might
     have a problem because your hard disk drive is an old version.  Check the
     date of manufacture for each hard disk drive.

    o If you have a hard disk drive from IDE, it must be dated 040990 or later.
    o If you have a hard disk drive from another manufacturer, it must be dated
      092588 or later.

     If your hard disk drive is an old version, contact the dealer at your
     place of purchase or the manufacturer for information about upgrading the
     drive.


ΓòÉΓòÉΓòÉ 6.10.8.3. Micronics System Board ΓòÉΓòÉΓòÉ

If your computer does not work properly, you might have revision E of a
Micronics system board.  That board contains an old version of BIOS. If you
purchased the board from Gateway, contact Gateway 2000, Inc. at 800-523-2000
and request an upgrade to revision F.


ΓòÉΓòÉΓòÉ 6.10.8.4. Gateway 2000 Computer ΓòÉΓòÉΓòÉ

If you have an early version of a Gateway 2000 computer that does not work
properly, your BIOS might be an old version. The company suggests that you
replace the system board. Contact Gateway 2000, Inc. at 800-523-2000 for
information about upgrading your computer.


ΓòÉΓòÉΓòÉ 6.10.9. ZEOS Notebook ΓòÉΓòÉΓòÉ

If you have a ZEOS notebook and the installation of OS/2 2.0 fails, you can
correct the installation problem by adding a patch to your Installation
Diskette.

Note:  To do this, you must use a computer that has OS/2 2.0 running on it.
       Ask a local IBM dealer, a friend, or a co-worker if you can use their
       computer for a few minutes.  Take your OS/2 2.0 Installation Diskette
       and a blank, formatted, high-density 3.5-inch diskette with you.

 If you are unable to find a computer to use, call the OS/2 Technical Support
 Center at 800-237-5511 and request that a patched Installation Diskette be
 sent to you.

 To install the patch using a computer that has OS/2 2.0 running on it, do the
 following:

  1. Double-click on OS/2 System on the OS/2 desktop.
  2. Double-click on Command Prompts.
  3. Double click on OS/2 Window.  You will see an OS/2 command prompt.
  4. Back up your Installation Diskette to the blank 3.5-inch diskette you
     brought with you by typing the following:

             DISKCOPY A: A:
     Then press Enter and follow the prompts.
  5. Place the newly created backup Installation Diskette in drive A.
  6. Type:

             PATCH SYSINSTX.COM
     Then press Enter.
  7. When asked for the offset address, type:

             96AF
     Then press Enter.
  8. Change 44 to 45; then press Enter. The following message is displayed:

             Do you wish to continue patching sysinstx.com?

  9. Type:

             N
          Then press Enter.

 10. When asked if you want to apply patches, type:

             Y
     Then press Enter.
 11. At the OS/2 command prompt, type:

             SYSINSTX A:
     The patch is complete.
 12. Install OS/2 on your ZEOS using the patched backup Installation Diskette
     that you just created.


ΓòÉΓòÉΓòÉ 6.11. Short Cut if Your Installation Procedure Stops ΓòÉΓòÉΓòÉ

If the installation procedure stops before completion, you might be able to
complete the installation without reusing all the installation diskettes.  You
do not have to use all diskettes again if the installation stopped after you
were prompted to put the Installation Diskette in the drive the second time
(after you are in the graphical installation). For example, if you were copying
files from Diskette 9 on a 3.5-inch-diskette system, you could resume the
installation at Diskette 9 after doing the following:

  1. Identify which diskette was being "unpacked" when the installation
     procedure stopped.

  2. Subtract the number of that diskette from 15 and add one to the result if
     you have 3.5-inch installation diskettes.  (Subtract the number from 18 if
     you have 5.25-inch installation diskettes.) For example, if you were on
     Diskette 9 on a 3.5-inch system, the result would be 7.

  3. Start the computer with the Installation Diskette, and then insert
     Diskette 1 when prompted.

  4. When you are asked to press Esc to cancel, press Esc. You will see a
     command prompt.

  5. Use a text editor to edit the CONFIG.SYS file on your hard disk.

  6. In the line that starts with FIRSTDISK, change the number to the number of
     the diskette that was in the diskette drive when the installation
     procedure stopped.  In the example, this is 9.

             FIRSTDISK=9

  7. In the line that starts with NUMDISKS, change the number to the one you
     reached in step 2.  In the example, this is 7.

             NUMDISKS=7

  8. Remove the diskette and press Ctrl+Alt+Del.  You will see the graphical
     install panel.  Click on OK, then Install, and select all defaults.

  9. When you are prompted, insert the diskette named in the prompt.  In the
     example, this would be Diskette 9, the diskette that was being loaded when
     the installation procedure stopped.

 All the Selective Install choices that you selected when you first tried to
 install OS/2 2.0 are preserved.


ΓòÉΓòÉΓòÉ 6.12. Applications ΓòÉΓòÉΓòÉ

Following is information about running DOS or Windows applications, or Windows
Version 3.1. You can also find out what to do if any of your previous
applications did not migrate during installation.


ΓòÉΓòÉΓòÉ 6.12.1. DOS or Windows Applications (before Running) ΓòÉΓòÉΓòÉ

After installation, and before you run any DOS or Windows applications, shut
down your system and restart it.  You only have to do this once, immediately
after you finish installing OS/2 2.0.


ΓòÉΓòÉΓòÉ 6.12.2. Previous Application Not Migrated ΓòÉΓòÉΓòÉ

Occasionally, the Migrate Applications program might not find all applications.
In this case, retry the Find Programs operation.


ΓòÉΓòÉΓòÉ 6.12.3. Windows Version 3.1 ΓòÉΓòÉΓòÉ

IBM's testing of Windows Version 3.1 environment indicates that the OS/2 2.0
Installation program will not configure your   WIN-OS/2 desktop.  If the
Windows directory that is found is from a Windows Version 3.1 environment,
either change the DOS PATH to point to a Windows Version 3.0 environment, or
select the default environment.


ΓòÉΓòÉΓòÉ 6.13. CD-ROM (Selective Install) ΓòÉΓòÉΓòÉ

If you install CD-ROM using the Selective Install program, do not install any
other options at the same time.


ΓòÉΓòÉΓòÉ 6.14. UNDELETE (Enabling) ΓòÉΓòÉΓòÉ

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

  REM SET DELDIR=


ΓòÉΓòÉΓòÉ 6.15. Dual Boot Does Not Work ΓòÉΓòÉΓòÉ

If you cannot dual boot (switch from DOS to OS/2 by typing Boot /OS2), you
might have one or more active TSR (terminate and stay resident) or DOS cache
programs. If so, end the programs before you switch to DOS.


ΓòÉΓòÉΓòÉ 6.16. Boot Manager ΓòÉΓòÉΓòÉ

Following is information about using the Boot Manager.


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


ΓòÉΓòÉΓòÉ 6.16.2. Boot Manager with Dual Boot OS/2 Version 1.3 in a Partition ΓòÉΓòÉΓòÉ

If you are using Boot Manager, and one of your partitions contains OS/2 Version
1.3 with Dual Boot, copy BOOT.COM from the OS/2 2.0 \OS2 subdirectory to the
OS/2 Version 1.3 \OS2 subdirectory.


ΓòÉΓòÉΓòÉ 6.17. Non-IBM Computer with Two Drives ΓòÉΓòÉΓòÉ

If you have a non-IBM computer with two hard disk drives (for example, an IDE
and a WD 506 clone), the second drive might not work properly after you install
OS/2 2.0.  If so, reformat that drive with DOS or OS/2 2.0.


ΓòÉΓòÉΓòÉ 7. OS/2 Workplace Shell ΓòÉΓòÉΓòÉ

This chapter 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.


ΓòÉΓòÉΓòÉ 7.1. Starting Up Your System ΓòÉΓòÉΓòÉ

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

      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: c.

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

      Note:  In preparation for a situation where a faulty application suspends
             your computer, you might want to add the REM SET RESTARTOBJECTS=NO
             statement to your CONFIG.SYS file.  Then, should an application
             fail to function, you can restart your system using the OS/2
             Installation diskette, and then edit the CONFIG.SYS file and
             activate the statement by removing the word REM.  When you restart
             your computer, the faulty application (and all others) are kept
             from restarting.

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


ΓòÉΓòÉΓòÉ 7.2. Using the Shell ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 7.2.1. Icons, Tabs, or Bit Maps Do Not Appear ΓòÉΓòÉΓòÉ

 o Because of device-resource limitations, when too many applications are open,
   or when too many bit maps are visible on the screen, new icons, tabs, or
   other bit maps might not be drawn. To fix this situation, close unused
   folders and applications so their device resources can be used by other
   processes.

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

     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.


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

  1. Restart your computer using the OS/2 Installation Diskette; then insert
     Diskette 1.

  2. Press Esc to access an OS/2 full screen; then 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.  Type:

          ATTRIB -h -s -r "WP ROOT. SF"  (HPFS) (and press Enter)
                    or
          ATTRIB -h -s -r WP_ROOT._SF (FAT) (and press Enter)

     Type:

          DEL "WP ROOT. SF" (HPFS) (and press Enter)
                    or
          DEL WP_ROOT._SF (FAT) (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 information, but the system
 should be restored. c.

  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: c.

  1. Restart your system using the OS/2 Installation Diskette; then insert
     Diskette 1.

  2. Press Esc to access an OS/2 full screen; then 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.  Type:

          ATTRIB -h -s -r "WP ROOT. SF"  (HPFS) (and press Enter)
                    or
          ATTRIB -h -s -r WP_ROOT._SF (FAT) (and press Enter)

     Type:

          DEL "WP ROOT. SF" (HPFS) (and press Enter)
                    or
          DEL WP_ROOT._SF (FAT) (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.


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

     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:


                    MOVE OS!2_SYS \OS!2_2.0_D   (FAT)
                                 (or)
                    MOVE "OS!2 SYSTEM" \"OS!2 2.0 DESKTOP"   (HPFS)

 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.


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

  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.


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

  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.


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

  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.


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

  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.


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

  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.


ΓòÉΓòÉΓòÉ 7.2.9. 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 always minimize to the Minimized Window Viewer.


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


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


ΓòÉΓòÉΓòÉ 7.2.12. Receiving a SYS3176 Message ΓòÉΓòÉΓòÉ

If you receive the message SYS3176 whenever you attempt to open a DOS session
or DOS application, refer to the section on SVGA support in Video/Graphic
Support.  Additionally, try the following: c.

  1. In your CONFIG.SYS file, set RMSIZE to 624 instead of 640.

  2. Change the DOS setting for the object to "HW_ROM_TO_RAM to ON."


ΓòÉΓòÉΓòÉ 7.3. Using ANSI Colors and Characters in DOS Sessions ΓòÉΓòÉΓòÉ

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

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

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

  2. Shut down your computer.

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


ΓòÉΓòÉΓòÉ 7.4. Using HPFS ΓòÉΓòÉΓòÉ

 o If you formatted your installation drive with HPFS, you might not be able to
   access files in the Desktop folder from DOS or WIN-OS/2 applications.  DOS
   and WIN-OS/2 applications use the FAT file system.

 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.


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

     1. Press Ctrl+Esc to display the Window List.

     2. Press Up Arrow () 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 () 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.


ΓòÉΓòÉΓòÉ 8. Printing Considerations ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 8.1. Configuring Your Computer for Printing ΓòÉΓòÉΓòÉ

On most AT bus (ISA) parallel ports, the configuration is done by either
dual-inline package (DIP) switches or jumper settings. Most of the systems and
adapters purchased have literature that explains the interrupt request (IRQ)
level and port setting for each port.  The following are standard parallel-port
address and IRQ settings:


            Two-parallel-port hardware setup:

             AT                       EISA/MC
            _________                 ________
            3BC/IRQ7       LPT1       3BC/IRQ7
            278/IRQ5       LPT2       378/IRQ7

                         or

            378/IRQ7       LPT1       378/IRQ7
            278/IRQ5       LPT2       278/IRQ7


           Three-parallel-port hardware setup:


             AT                       EISA/MC

            _________                 ________
            3BC/IRQ7       LPT1       3BC/IRQ7
            378/IRQ7       LPT2       378/IRQ7
            278/IRQ5       LPT3       278/IRQ7

Dip switches and jumper settings reside on the system board or adapter in your
computer. To change their configuration, do the following: c.

  1. Turn off your computer.

  2. Remove the parallel-port adapter.

  3. Configure the adapter on the board or card by adjusting the DIP switches
     and/or jumpers to set the parallel port to one of the industry standard
     combinations.  Ensure that other adapters are not configured to use the
     same IRQ level (for example, the one assigned to the printer port). Sound,
     Musical Instrument Device Interface (MIDI), LAN, and serial adapters might
     be sharing these same hardware-interrupt levels and creating interference.

 For more information, refer to Setting the Interrupt Request (IRQ) Level on an
 ISA System and Interrupt Problems on an ISA System.


ΓòÉΓòÉΓòÉ 8.1.1. Hardware Adapters and IRQ Conflicts ΓòÉΓòÉΓòÉ

AT bus (ISA) computers do not allow hardware-interrupt sharing; therefore, each
adapter must be configured to a separate IRQ level to be able to work properly.
Some adapters, such as SoundBlaster, are factory configured to IRQ7, or their
accompanying instructions recommend that you configure them to IRQ7. This might
be the same hardware-interrupt level as the first parallel port. If you intend
to print, this conflict must be resolved.  You might be able to use IRQ10 with
SoundBlaster because it does not conflict with parallel ports (IRQ7,IRQ5) or
IRQ5 if LPT2 is not being used. Refer to Configuring Your Computer for Printing
and Setting the Interrupt Request (IRQ) Level on an ISA System for more
information about possible parallel-port and IRQ settings.

Refer to the reference manual for your adapters to configure the IRQ levels for
your parallel-ports (could be on the system board) and other adapters in your
system.


ΓòÉΓòÉΓòÉ 8.1.2. PS/2 Direct-Memory-Access Parallel Ports ΓòÉΓòÉΓòÉ

If you have a 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. If you
are an OS/2 Version 1.3 customer with Corrective Service Diskette 5054 (or
later) installed, and you have disabled the parallel-port arbitration level,
you need to re-enable it in order for OS/2 2.0 to take advantage of the
feature. Use the Reference Diskette shipped with the computer to view the
system configuration, and then set the parallel-port arbitration level to
SHARED7.


ΓòÉΓòÉΓòÉ 8.2. Configuring Printers ΓòÉΓòÉΓòÉ

The following section describes suggestions for using specific printers.


ΓòÉΓòÉΓòÉ 8.2.1. Cannon BubbleJet Printer ΓòÉΓòÉΓòÉ

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

 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.


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


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


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

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.


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


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


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


ΓòÉΓòÉΓòÉ 8.2.8. NEC P3200 Printer ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 8.2.9. NEC P6200 Printer ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 8.2.10. Star NX-1000 Printer ΓòÉΓòÉΓòÉ

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


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

     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.


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


ΓòÉΓòÉΓòÉ 8.4. Diagnosing Printing Problems ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 8.4.1. Slow Printing ΓòÉΓòÉΓòÉ

If you have an AT bus (ISA) computer and your parallel printer prints slowly
under OS/2, DOS, and WIN-OS/2 sessions, your parallel-port address and
hardware-interrupt levels are not configured correctly.  You need to
reconfigure your hardware.  Refer to Configuring Your Computer for Printing.


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


ΓòÉΓòÉΓòÉ 8.4.3. Printer Stops Printing ΓòÉΓòÉΓòÉ

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

  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.


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


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


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


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


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


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


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


ΓòÉΓòÉΓòÉ 8.5. Printing from a WIN-OS/2 Session ΓòÉΓòÉΓòÉ

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


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


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


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

     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 (:).


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


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


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

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

 o If a TRAPD occurs in old DOS applications, and the CS:EIP register value is
   150:00004912, then a protection fault has occurred in the OS/2 kernel. Use
   an HPFS partition as a workaround. A fix is forthcoming from IBM.

 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 or 16550 buffered communications chips.

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

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

 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 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 press Ctrl+Alt+PrtSc
   while the DOS session that first performed direct I/O to the parallel port
   has the keyboard focus.

 o Some of your Windows Multimedia Extension programs might not work correctly
   after being migrated to OS/2 2.0. 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.


ΓòÉΓòÉΓòÉ 9.2. 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.
    - If a TRAPD occurs, and the CS:EIP register value is 150:00004912, then a
      protection fault has occurred in the OS/2 kernel. Use an HPFS partition
      as a workaround. A fix is forthcoming from IBM.

 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.

 o Commander Keen (DOS)

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

       o Start a DOS session.
       o Run FFIX /date (Note that "date" must be lowercase).
       o Run WINOS2 (from the command line).
       o Install the program.
       o Exit WIN-OS/2.
       o Run FFIX /u.

    - 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 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 a small number of other processes 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:

       o Select DOS full screen or DOS window.
       o Set the VIDEO_MODE_RESTRICTION DOS setting to CGA.
       o 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:

       o Set the Path and File Name to *.
       o Set the Parameters to /K d:\path\PC3270.BAT.
       o Set the Working directory to d:\path.

 o IBM PC/3270 V2.0* (OS/2)

    - First, the program must be migrated using the OS/2 Migration utility
      program.
    - Then, in the Session Page of the OS/2 settings:

       o Select DOS full screen or DOS window.
       o Set the VIDEO_MODE_RESTRICTION DOS setting to CGA.

    - Then, in the Program Page of the DOS settings:

       o Set the Path and File Name to *.
       o Set the Parameters to /K d:\path\PC3270.COM.
       o 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:

       o Add " /C PC3270WO.BAT" to the DOS_SHELL WIN-OS/2 setting.
       o Add "D:\[path]DXMA0MOD.SYS", "D:\[path]DXMC0MOD.SYS", and
         "D:\[path]PCS802.SYS V=N" to the DOS_DEVICE WIN-OS/2 setting.
       o Set the "DOS_SHELL" setting to /C PC32700WO.BAT.
       o 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:

       o Set the Path and File Name to d:\path\PC3270.EXE.
       o Set the Working directory to d:\path.

 o Intel SatisFAXtion

    - The installation program displays the message You have inserted the wrong
      diskette when changing from disk one to disk two. After the error message
      is displayed, press Enter and the program will continue with
      installation.
    - At the end of installation of the Intel SatisFAXtion you are told 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

    - 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 Linkway Mammals (DOS)

    - Photomotion programs might exhibit some audio breakup and video
      hesitation during periods of CD ROM access.

 o Linkway Presidents (DOS)

    - Photomotion programs might exhibit some audio breakup and video
      hesitation during periods of CD ROM access.

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

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

       o Start a DOS session.
       o Run FFIX /date (Note that "date" must be lowercase).
       o Install the program (the installation program is a DOS program).
       o 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.
    - Animation programs might exhibit some audio breakup and video hesitation
      during periods of CD ROM access.

 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)

    - Photomotion programs might exhibit some audio breakup and video
      hesitation during periods of CD ROM access.

 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_DEVICE DOS 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:

       o Start a DOS session.
       o Run FFIX /find (Note that "find" must be lowercase).
       o Install the program.
       o 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 extended 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) c.

    - 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) c.

    - 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) c.

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

 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.


ΓòÉΓòÉΓòÉ 10. Performance ΓòÉΓòÉΓòÉ

Following are some performance considerations that you should be aware of.  For
more performance guidelines, see the .Information and Planning Guide document
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.)

Some systems use more than 128KB for other purposes, so less than the minimum
required memory is available.  On these systems, you might need another 512KB
to 1MB to satisfy the minimum requirements.  Check your system to see if it
offers a way to return the memory so that you can return to the minimum
requirement.

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.


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


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


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


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

 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.

 If you are running Windows applications in a single WIN-OS/2 session, the
 Windows clipboard can be changed from PUBLIC to PRIVATE for increased
 performance.  Setting it to PRIVATE means that it can be used in the single
 Windows environment only.

 When a large volume of data is being sent to the clipboard in a WIN-OS/2
 Window session, you might receive the message:

    Data not saved, possible memory or disk space error.
     This data not available in clipboard.
 followed by the message:

    Do you want to exit clipboard?

 Selecting OK to the second message will make the clipboard private to that
 WIN-OS/2 session.  Data that was previously sent to the public clipboard might
 have remained private.  You might want to use the private clipboard for
 applications seeing these messages.

 When you exit from a WIN-OS/2 session, the system leaves the clipboard and DDE
 loaded.  If you will not be returning to a WIN-OS/2 session, close both the
 clipboard and DDE. Use the PM Window List to see if they are active.

 To permanently disable public DDE and clipboard interchange between Windows
 applications and PM applications, and between Windows applications in separate
 WIN-OS/2 sessions, edit the \OS2\MDOS\WINOS2\SYSTEM.INI file.  In the "boot]
 section you will find the names of these two programs in the SAVDMApps= line,
 the MAVDMApps= line, and the WOS2VDMApps= line.  By removing the names of the
 programs from these lines, the programs will not be automatically started.
 Adding them back will cause them to be started the next time a WIN-OS/2
 session starts up.


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


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


ΓòÉΓòÉΓòÉ 10.7. Hard Disk Space ΓòÉΓòÉΓòÉ

To save hard disk space, be certain to install only the functions you need. If
you have installed the productivity aids and the games, and later only want a
subset of these, delete all \OS2\APP and \OS2\APP\DLL files and use INSTALL to
selectively install the items you want. Additionally, delete TUTORIAL.HLP in
\OS2\HELP\TUTORIAL if you no longer need the tutorial.


ΓòÉΓòÉΓòÉ 11. Windows Version 3.0 Programs Support ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 11.1. 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 Selective Install 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 Selective Install, double-click the icon for OS/2
   System, then System Setup, then Selective Install.

 o To decompress Windows device drivers supplied by equipment manufacturers,
   use the EXPAND.EXE utility program for WIN-OS/2 located on OS/2 2.0 Diskette
   9.

 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. Install Boot Manager, and partition your hard disk so that
   Windows 3.1 is in a partition separate from OS/2 2.0. Or, if you have DOS
   and Windows 3.1 already installed before you begin OS/2 2.0 installation,
   consider installing OS/2 2.0 Dual Boot. With Dual Boot, you can shut down
   OS/2 2.0 and start up DOS/Windows to run programs that require Windows 3.1.

 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 install the US English version of OS/2 2.0, and you want to change
   the system configuration to another country or language, run Selective
   Install 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.

 o If you start an application in a WIN-OS/2 session and receive the message
   FATAL ERROR 0X0401, a problem occurred during migration of your Windows
   programs so that device statements in the SYSTEM.INI file were not updated
   from your \WINDOWS directory. 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.


ΓòÉΓòÉΓòÉ 11.2. Using Clipboard and Dynamic Data Exchange ΓòÉΓòÉΓòÉ

 o If you use the Clipboard Viewer to cut, copy, or paste from a DOS or OS/2
   application to a Windows application, ensure that both the DOS or OS/2
   application and the Windows application are running before marking the text;
   otherwise, the copy might not be successful.

 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 WIN-OS/2 sessions, Clipboard and Dynamic
      Data Exchange (DDE) default to Public.

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

    - In WIN-OS/2 window sessions, Clipboard and DDE can only be Public.

 o To disable Clipboard and DDE in an OS/2 session, do the following:

     1. Create a WIN-OS/2 window or full-screen session, so that Clipboard and
        Data Update are started. (Clipboard and Data Update are automatically
        started when you start a WIN-OS/2 session.)
     2. On the OS/2 desktop, display the Window List.
     3. Select Clipboard and Data Update.
     4. Display a pop-up menu by clicking mouse button 2 on Clipboard or Data
        Update.
     5. Select Close.

 o To share data between WIN-OS/2 sessions only, close Data Update and
   Clipboard in the OS/2 sessions.

 o In a WIN-OS/2 window session, the Clipboard and DDE icons are not available.
   You do not have access to the clipboard features.

   However, if you want to use a private clipboard in WIN-OS/2 window sessions,
   you can remove !CLIPWOS2 from the SYSTEM.INI file (in the \OS2\MDOS\WINOS2
   directory). The statements involved are those that begin with:

      SAVDMApps=
      MAVDMApps=
      WOS2VDMapps=
   All three occurrences of !CLIPWOS2 must be removed.  It is advisable to back
   up the SYSTEM.INI file before making the changes, so that you can easily
   restore the original SYSTEM.INI if you decide to do so in the future.

     Warning: If the SYSTEM.INI file is changed incorrectly, you might not be
     able to use WIN-OS/2. If you are not familiar with Windows .INI files, you
     might want to arrange for a person who has Windows technical expertise to
     make any changes in the SYSTEM.INI file.

 o To disable Clipboard and DDE in a full-screen WIN-OS/2 session, do the
   following:

     1. Start WIN-OS/2.

     2. Click mouse button 1 on the Clipboard icon to display the window menu.

     3. Click on Close.

     4. Respond to the confirmation message.

     5. Repeat the previous steps to close the DDE Interchange Agent.

 o If you experience slow performance when using a Windows application to copy
   data to the clipboard, consider the following information on improving
   performance.

   The clipboard uses delayed rendering, which means only the format name is
   given to the clipboard.  The actual data is rendered only when the Paste
   menu choice is selected.  Many Windows applications use this scheme when
   they copy data to the clipboard.  However, to share data between WIN-OS/2
   and OS/2 sessions, the WIN-OS/2 clipboard receives all data from the
   application that copied the data to the clipboard, and then sends the data
   to other sessions.  This process is time-consuming.  You can decide whether
   or not you want to share data between WIN-OS/2 sessions.

   If you do not want to share data, open the Clipboard icon in a WIN-OS/2
   full-screen session and turn off the Public clipboard choice on the Options
   menu bar choice; however, if you want to share some of the data between
   sessions, use the File Export and Import menu bar choices.

 o If you are unable to paste data from the OS/2 clipboard to a WIN-OS/2
   session, you need to open the WIN-OS/2 session before you copy data from the
   OS/2 clipboard. The WIN-OS/2 session starts the OS/2 clipboard, which will
   send the data to the WIN-OS/2 clipboard. This problem will be fixed in a
   future release.

 o If you cannot paste an icon from the OS/2 clipboard to a WIN-OS/2 session,
   the icon file might be too large, or the application might not understand
   the device-independent bit map (DIB) format of the file. For example, icons
   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 icon in the OS/2 clipboard; however, you
   cannot paste it.  The Paste menu choice is grayed (unavailable).

 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 an application copies several sources of data to a public clipboard in
   different formats, and if one of the sources creates a rendering problem, no
   data is sent to other WIN-OS/2 sessions.  In a future release, only the
   problem data will not be sent to the public clipboard.

 o When a metafile is copied to the OS/2 clipboard, it is converted into a bit
   map, and then the image is enlarged.  Only the center of the image is in the
   clipboard window.  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 bit map 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.


ΓòÉΓòÉΓòÉ 12. Video/Graphic Support ΓòÉΓòÉΓòÉ

OS/2 2.0 fully supports EGA and VGA. Because of the highly graphical user
interface provided by the Workplace Shell, use of OS/2 2.0 in CGA mode will be
difficult and is not recommended.  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 (640x480x16 colors) are referred to as Super VGA
(SVGA). However, the implementation of SVGA varies widely and requires
different device drivers for different resolutions, as well as different
adapters and systems. The OS/2 Installation 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.


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


ΓòÉΓòÉΓòÉ 12.1.1. SVGA ON Utility Program ΓòÉΓòÉΓòÉ

If you have one of the video adapters listed on the previous page and want to
run DOS or Windows applications that make use of SVGA, you must turn on OS/2
2.0 SVGA support.  The OS/2 Installation program detects the type of video chip
in the system; it cannot detect the type of adapter or system board that the
video chip has been implemented on.  You must determine that you have a
supported configuration, and then explicitly enable SVGA.

To enable SVGA, type the following at a DOS full-screen command prompt:

 SVGA ON

Then restart the system.


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

       o 640x480/256 colors
       o 800x600/16  colors
       o 800x600/256 colors
       o 1024x768/16 colors
       o 1024x768/256 colors
       o 132x25 text
       o 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

   This file determines what video resolution the desktop uses. This is the PM
   display driver.  The equivalent file on a Windows system is the VGA.DRV (in
   the case of VGA) file.  For the first release, SVGA systems will have a VGA
   display driver installed on their system.  Already, SVGA drivers are
   available from most of the main board manufacturers.

 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.


ΓòÉΓòÉΓòÉ 12.1.3. 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 Some screen resynchronization problems might exist in DOS or WIN-OS/2
   full-screen sessions.  The problem is with how some SVGA adapters handle
   switching. IBM has created a new VSVGA.SYS file to correct this.
   Specifically, the problem occurs most frequently with Tseng chipsets.  Video
   adapters using the Tseng ET4000 chipset with batch #TC6059AF have been
   identified to have this problem. The VSVGA.SYS file dated 4/8/92 or later
   should solve this problem.

 o In the event of a TRAP000E when opening a DOS or WIN-OS/2 session on systems
   with 4MB of memory and SVGA adapters, you need to obtain the VSVGA.SYS
   driver replacement from IBM.

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

 o 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.  The more these
   manufacturers are encouraged by owners of their adapters, the faster the
   support will arrive.

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

 o Even in VGA, games in a DOS full-screen session are not optimized. Set your
   VIDEO_RETRACE_EMULATION in the DOS Settings to OFF.

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

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

 o 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

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

 o Many different SVGA boards have different interfaces and chipsets, each with
   their own characteristics.  Some boards perform better with SVGA OFF.


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


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

  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.


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


ΓòÉΓòÉΓòÉ 12.5. 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 (XGA) 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. Install OS/2 2.0 for medium resolution VGA.

     The next step requires that you 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 XGA.DRV
     device driver is used. Checking this directory reveals that this device
     driver is not loaded. (The device driver might be loaded already, if the
     system was installed in high-resolution mode and then Selective Install
     was run to return to VGA mode.)

     For XGA, the diskettes need to be searched for WINXGA and *G.FON.  The
     following shows the sequence of entries:

           DIR A:WINXGA
           DIR A:*G.FON

     No XGA drivers were on this diskette, 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 A:SYMBOLG.FON

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

    o SYMBOLG.FON
    o TMSRG.FON
    o COURG.FON
    o HELVG.FON

     Eventually the WINXGA file is found by the dir a:WINXGA search. It
     contains the WIN-OS/2 XGA.DRV and three XGA fonts.

           UNPACK A:WINXGA

     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=xga.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 XGA, these entries must be changed to:

           fixedfor.fon=xgafix.fon
           oemfonts.fon=xgaoem.fon
           fonts.fon=xgasys.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 (XGA res)=SYMBOLG.FON
           Helv 8,10,12,14,18,24 (XGA res)=HELVG.FON
           Tms Rmn 8,10,12,14,18,24 (XGA res)=TMSRG.FON
           Courier 10,12,15 (XGA res)=COURG.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).

 For 8514 displays, you must delete the following line from CONFIG.SYS:

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

 For 8514 displays, the files to find are: c.

 o WIN8514 (contains 8514.DRV, 8514SYS.FON, 8514OEM.FON, and 8514FIX.FON)

 o COURF.FON

 o TMSRF.FON

 o HELVF.FON

 o SYMBOLF.FON

  1. Windows application developers should note that their debuggers work in
     full-screen sessions only.  If you have a dual-display setup (8514+VGA),
     install 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. Installing 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.


ΓòÉΓòÉΓòÉ 13. Hardware Considerations ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 13.1. Personal Computer Manufacturer (PCM) Systems ΓòÉΓòÉΓòÉ

OS/2 2.0 is supported on personal computers with an 80386 SX (or compatible) or
later microprocessor, with at least 4MB of memory and a 60MB hard disk with
15MB to 30MB of free space.

IBM is currently testing personal computer manufacturer (PCM) systems for
compatibility with OS/2 2.0. The compatibility test verifies 18 key functions
of OS/2 2.0. Test results are based on selected model configurations provided
by the manufacturers.  While testing is continuing, current compatibility
information about tested systems is available through your dealer or Marketing
Representative, as well as through the following online services.

 o Prodigy, Jump Computer Club, in Windows and OS/2 topic. (To join Prodigy,
   call 1-800-Prodigy.)

 o CompuServe, G IBMOS2, in Library 17, PCMTAB.TXT. (To join CompuServe, call
   the appropriate phone numbers for your area, or Membership Service at
   1-800-848-8199, and ask for representative 239.)

 o IBM National Support Center Bulletin Board System (NSC BBS).  This service
   is available 24 hours a day, on a toll-call basis, with no access charge, to
   anyone in the world who has a modem, asynchronous-communication software,
   and a switched telephone line.  (The modem should be set for 8 data bits, 1
   stop bit, no parity, and the standard transmission speed from 1200 to 9600
   baud.)

   To access the NSC BBS, call [phone].

 o IBM Link.  Eligible customers can obtain installation and usage assistance
   through IBM Link Question Support.  To obtain information about eligibility,
   contact your local Branch Office or Marketing Representative.

 Note:  The compatibility test information is provided for information purposes
        only.  IBM MAKES NO WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE
        OPERATION OF THE PERSONAL COMPUTERS LISTED THROUGH THE ABOVE SOURCES


ΓòÉΓòÉΓòÉ 13.2. SCSI devices ΓòÉΓòÉΓòÉ

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

 o Adaptec SCSI adapters do not currently support drives larger than 1GB.


ΓòÉΓòÉΓòÉ 13.2.1. 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 INTERFACE              Γöé DEVICE DRIVER                         Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 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 operation)              Γöé AHA154X.ADD                           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé (Enhanced mode operation)              Γöé AHA174X.ADD                           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Future Domain TMC-850/860/875/885      Γöé FD8XX.ADD                             Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Future Domain TMC-1660/1670/1680       Γöé FD16-700.ADD                          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Future Domain MCS-600/700              Γöé FD16-700.ADD                          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Future Domain TMC-850IBM               Γöé FD850IBM.ADD                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
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.

  1. Locate Installation Diskette 8, which contains the file, DASDDRVS.

  2. Insert the diskette in drive A.

  3. Change the current directory to the root directory of the startup drive.

  4. Type:  UNPACK A:DASDDRVS \OS2 /N:xxxxxxxx.ADD

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

           BASEDEV=xxxxxxxx.ADD

  6. Restart the system.


ΓòÉΓòÉΓòÉ 13.2.2. OS2SCSI.SYS Device Driver ΓòÉΓòÉΓòÉ

Older versions of the OS/2 operating system used the device driver SCSI.SYS.
This has been replaced by OS2SCSI.SYS. OS2SCSI.SYS 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.SYS."
Normally, this is done automatically but inspect your CONFIG.SYS file if you
suspect SCSI problems.

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


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


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


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

 System:        IBM Models 35 and 40

 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.


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

 o At the final restart after the installation is completed, 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.
   This line should have been placed there by system installation.


ΓòÉΓòÉΓòÉ 13.2.7. Always Technology SCSI ΓòÉΓòÉΓòÉ

If you are experiencing OS/2 problems either at installation time or after,
(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.


ΓòÉΓòÉΓòÉ 13.3. Additional Device Support Information ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 13.3.1. HP Scanjet ΓòÉΓòÉΓòÉ

If you get an error saying that you cannot access your HP scanner, and you are
using an ISA (AT-style) bus machine, your adapter switches need to be set to
1010.

If you are using 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.


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


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


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


ΓòÉΓòÉΓòÉ 13.3.5. IBM PS/2 Model 30-286 Upgrades ΓòÉΓòÉΓòÉ

IBM PS/2 Model 30-286 upgrades to a 386 microprocessor are not supported.


ΓòÉΓòÉΓòÉ 13.3.6. 50 MHz Systems ΓòÉΓòÉΓòÉ

There have been some intermittent problems using 50 MHz systems with AT-style
bus computers with a mouse.  The mouse can get out of synchronization. Input
will function through the keyboard and the mouse, but to avoid possible
problems, shutdown the system and restart to resynchronize the mouse.


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


ΓòÉΓòÉΓòÉ 13.3.8. Aox Systems ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 13.3.9. Orchid Video Adapters ΓòÉΓòÉΓòÉ

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

 o 510-683-0327 for 2400 baud, parameters n,8,1
 o 510-683-0555 for 9600 baud, parameters n,8,1


ΓòÉΓòÉΓòÉ 13.3.10. ISA (Non-Micro Channel or Non-EISA) Bus Systems ΓòÉΓòÉΓòÉ

Some customers with AT-bus (ISA) systems might have disk controllers that are
not recognized or supported by OS/2 2.0.  OEM drivers for their disk controller
might not yet be available.  Symptoms include:

 o Very slow installation
 o Very noisy hard disk during installation
 o FDISK errors
 o Disk not recognized
 IBM has a new IBM1S506.ADD disk driver available that will fix many of these
 problems.  It can be obtained from any of the sources described in Chapter 2
 "Service and Support Information". In the event you cannot get this new file,
 or if the new file does not solve your particular problem, you might do the
 following:

  1. Use DOS to edit the CONFIG.SYS file on Diskette 1 in the 2.0 package.
     Change the line

          BASEDEV=IBM1S506.ADD
     to

          REM BASEDEV=IBM1S506.ADD

  2. Insert the Installation Diskette and proceed with the installation through
     the first five diskettes.
  3. After Diskettes 1 through 5 are processed, you are asked to reinsert the
     Installation Diskette.  DO THIS. After copying some files from the
     Installation Diskette, you are asked to remove it and press Enter to
     restart. DO NOT DO THIS.  LEAVE THE INSTALLATION DISKETTE IN THE DRIVE.
  4. Press Enter with the Installation Diskette in the drive. This will start
     up the Installation Diskette. You will be asked to insert Diskette 1. DO
     THIS. Watch the screens carefully. You will see a screen that tells you
     (on the lower left) to press Esc to exit. When you see this, press Esc.
  5. You are now at a command line. Enter the following commands:

          RENAME C:\OS2\IBM1S506.ADD   IBM1S506.XXX
          COPY   C:\OS2\IBMINT13.I13   C:\OS2\IBM1S506.ADD

     Note:  If C is not the drive you are installing to, adjust the commands
            accordingly.


  6. Remove the diskette from the drive. Press Ctrl+Alt+Del to restart the
     system, and the installation program will continue from where it left off.


ΓòÉΓòÉΓòÉ 13.3.11. Interrupt Problems on an ISA System ΓòÉΓòÉΓòÉ

On an ISA system, having a shared interrupt-request line can cause problems.
ISA systems have what are called "edge triggered" interrupts whereas Micro
Channel and EISA systems use "level sensitive" interrupts. "Edge triggered"
interrupts can only be sensed for a very short period of time.  If a second
interrupt arrives from another adapter while the first interrupt is still being
processed, the second interrupt will be lost. In your computer system, this
situation can lead to various difficulties such as printers that do not seem to
print smoothly or reliably, or communications sessions where some characters
are getting lost.

However, with single-tasking systems such as DOS, the two adapters that are
sharing the interrupt might never cause any real problems because they might
never be in use at the same time. OS/2 2.0, however, presents a different set
of problems.  If you have multiple serial communications adapters, there is a
greater probability that you might try to use two or more of them at the same
time.  If some of them have previously been set up using shared interrupts,
problems can occur that probably didn't happen in DOS.

OS/2 2.0 can detect that an interrupt line is shared and will not allow
simultaneous use.  Assume that COM1 and COM3 are sharing Interrupt Request line
4 (IRQ4). If you try to use both COM ports at the same time, the OS/2 operating
system will not allow the second one to start. A well-written OS/2
communications program will recognize that the port cannot be opened and an
error message will be displayed. A DOS application, however, is unprepared to
respond to this unfamiliar situation.  It will probably suspend, waiting for
the port that will not open.

Another potential source of trouble is having multiple hardware adapters that
are sharing the same I/O address.  The various hardware adapters in your
computer must have their own addresses.  Consider what might happen, for
example, if the commands that were meant for your printer were instead routed
to your disk drive.

The solution for all of these problems is to ensure that all your hardware
adapters have their own unique I/O addresses and IRQ assignments.


ΓòÉΓòÉΓòÉ 13.3.12. COM3 or COM4 Support on an ISA system ΓòÉΓòÉΓòÉ

The original ISA machine (the IBM PC-AT) allowed for the definition of up to
four serial communication ports.  However, there has never been any hardware
architectural standard that defined the I/O port addresses or Interrupt Request
(IRQ) lines associated with communication ports 3 or 4.

Over the years, a convention has developed that places the port addresses for
COM3 and COM4 at 03E8 and 02E8 respectively.  This is a generally accepted
convention, but not a standard.  Check the documentation and the settings of
the adapters in your system to verify your hardware environment.

After you have checked and set the I/O and IRQ values on your COM ports or
internal modems, you must add this information to the communications
device-driver (COM.SYS) statement in the CONFIG.SYS file.

You might also need to tell your communications application software where the
COM ports are.  ProComm software, for example, has a configuration screen that
enables you to specify these settings.  If the application, operating system,
and hardware are not in agreement, then the application will not run.

OS/2 COM ports do not need to be defined in sequence.  It is acceptable to have
a COM4 without having a COM3.  DOS, however, might have difficulty if there is
a gap in the port definition.  To avoid confusion for DOS, you can define COM
ports that do not have any physical adapters attached in the COM.SYS statement.
These substitute definitions will serve as placeholders.  COM1 and COM2 are
assumed to have standard values and do not need to be explicitly set up unless
you want to set some non-standard values to accommodate your particular
configuration.

To enable COM3 or COM4 on an ISA system, place the following in the CONFIG.SYS
file:

DEVICE=X:\OS2\COM.SYS (n,a,i) (n,a,i)
where

 X = the drive where OS/2 is installed
 n = the COM port that you are attempting to access
 a = communications port I/O address (03E8, 02E8, for example)
 i = IRQ level, which is usually a jumper setting on the I/O adapter
For example, to specify that COM3 is at address 03E8 on IRQ5 and that COM4 is
at address 02E8 on IRQ10, use the following statement (assuming that OS/2 is
installed on drive C):

      DEVICE=C:\OS2\COM.SYS (3,03E8,5) (4,02E8,10)
The I/O address and IRQ level should be noted in the documentation that came
with your adapter.  Either or both might be fixed values or can be set to a
range of values via jumpers or switches.  In some cases you might find that the
values are fixed or that the range of settings available to you is insufficient
to avoid the sharing conflict.  In that case, you must purchase a different,
more versatile adapter or accept that you cannot use both adapters at the same
time.


ΓòÉΓòÉΓòÉ 13.3.13. Setting the Interrupt Request (IRQ) Level on an ISA System ΓòÉΓòÉΓòÉ

The following information will help you determine what IRQ settings you can use
for COM3 or COM4 port adapters to avoid shared interrupts.

On an ISA machine there are a total of 15 IRQ levels available.  Many of these
are already being used.  Most are already in use because they are the the
standard settings for the more common devices.  These standard settings are as
follows:

 IRQ Level      Device Associated

 0              System Timer

 1              Keyboard

 2              Secondary Interrupt Controller  (see note)

 3              COM2 (Serial Communications Port 2)

 4              COM1 (Serial Communications Port 1)

 5              LPT2 (Parallel Port 2)

 6              Diskette

 7              LPT1 (Parallel Port 1)

 8              Realtime Clock

 9              open

 10             open

 11             open

 12             open

 13             Math Coprocessor

 14             Hard Disk

 15             open

 Note:  On the IBM-AT (ISA bus), the IRQ9 pin is identical with the IRQ2 pin on
        the original IBM-PC.  If you have an older, 8-bit adapter whose
        documentation states that it uses IRQ2, be aware that this will
        actually be interpreted as IRQ9 when plugged into the 16-bit ISA bus.

 The IRQ levels shown as "open" have no established, standardized use. When
 setting the IRQ values on your COM3 or COM4 ports, you are likely to find
 these levels available to use without conflict with some other adapter.
 Furthermore, if you don't have two parallel ports installed, IRQ5 might be
 usable for some other purpose, such as COM3 or COM4. Be cautious about doing
 this because it might cause a problem later if you decide to install a second
 parallel port.  In addition, some other non-standard device might already be
 using IRQ5.

 When trying to manage the IRQ levels of your various hardware adapters to
 avoid conflicts, you may find that your 8-bit adapters cause problems. Except
 for IRQ9, only 16-bit adapters are configurable to use IRQ levels higher than
 7.  A glance at the IRQ table will also show that the low-numbered IRQ lines
 already have some standard function assigned. It might be that your only
 alternative for avoiding some IRQ conflicts is to purchase a more versatile
 16-bit adapter.

 If you have non-standard 8-bit adapters, be especially careful of interrupt
 conflicts.  For example, the SoundBlaster adapter is configured at the factory
 to use IRQ7. IRQ7, however, is the standard assignment for LPT1, the first
 printer port. This conflict might not be apparent with DOS because DOS
 printing typically does not use the interrupt line.  OS/2 2.0, however,
 requires it, and the hidden conflict can become the source of printing
 problems.  It is also fairly common to discover that the interrupt feature on
 your parallel port adapter does not work.  In DOS, this might not have any
 effect.  In OS/2 2.0, however, your printer might be very erratic or not work
 at all.


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

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


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

If you have an ISA bus system, you might consider making changes to the fax
adapter so that only part of your system detects it. Then, place all operation
into a single DOS session.  This is possible on an ISA system if you can set up
your fax adapter as COM3 or COM4.  Since there are no standards for COM3 or
COM4 on an ISA system, OS/2 2.0 will not recognize the adapter unless it is
defined for the system in the CONFIG.SYS file (See the section "COM3 or COM4
Support on an ISA System" found earlier in this chapter).

To set up this configuration, set the hardware switches on the fax adapter to
indicate either COM3 or COM4.  Use a setting that is available and that does
not conflict with other adapters.  Leave VCOM.SYS in your CONFIG.SYS definition
but do not define the fax adapter settings to the COM.SYS device driver.  When
OS/2 2.0 starts up, it will not recognize the fax adapter, but the normal
communications ports will still get the benefit of having VCOM.SYS available.

Next, set up a DOS session so that it loads the DOS application software that
you use for faxing and also the DOS device driver used to control the fax
adapter if it came with a special driver.  Check your documentation to be sure.
This single DOS session should now be able to operate your fax adapter
normally.

In some cases, this still might not work.  If the DOS application treats the
adapter as a COM port instead of directly accessing the hardware, then DOS will
not recognize the adapter either.  The only problem with this configuration is
that this single DOS session controls the adapter. Other DOS or OS/2 sessions
will not be able to access it at all.

IBM is working on a fix to alleviate this problem, but the best solution will
be to use OS/2-specific device drivers and applications, especially where
performance is critical.


ΓòÉΓòÉΓòÉ 13.3.16. 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 on a PS/2
computer, 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.


ΓòÉΓòÉΓòÉ 13.3.17. IBM PS/2 Model 90 or 95 ΓòÉΓòÉΓòÉ

If you are experiencing problems with your Model 90 or 95, ensure your system
is at the latest engineering change (EC) level. Your IBM service representative
can assist you.

If your Model 90 or 95 is a 33 MHz system and you are having intermittent
difficulty identifying memory parity errors such as TRAP 0002, forcing you to
restart your system, then ECA053 might apply.  If your processor card has part
number 84F9356, contact your IBM representative to assist you with a
replacement.

If your Model 90 is experiencing intermittent memory errors, ECA084 might apply
if the part number of your memory riser card is N33F4905 or 84F9356.  Again,
your IBM representative can assist you with a replacement.

For both Model 90 and 95 computers, you must ensure that you have matched pairs
of single in-line memory modules. This means that each pair of single in-line
memory modules, as described in your technical reference manual, must be
matched in memory size and speed. Mixing these modules can cause some computers
to report memory errors.


ΓòÉΓòÉΓòÉ 13.4. Formatting Diskettes ΓòÉΓòÉΓòÉ

If you have a non-Micro Channel system with a 5.25-inch drive, and its 3.5-inch
drives all support media sense, your 5.25-inch drive will format diskettes at
720MB.  Previously formatted 1.2MB diskettes will read and write correctly.  A
fix for this problem can be obtained from the electronic bulletin board
described in Chapter 2 "Service and Support Information".


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

Trademark of the IBM Corporation.


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

Trademark of the Microsoft Corporation


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

Trademark of the IBM Corporation


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

Trademark of the IBM Corporation


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

Trademark of the IBM Corporation.


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

Trademark of the IBM