OS/2 Shareware BBS: 8 Other/08-Other.zip/warpst04.zip/OWTD.INF

OS/2 Help File | 1995-12-25 | 310KB | 7,181 lines

ΓòÉΓòÉΓòÉ 1. Copyright Information ΓòÉΓòÉΓòÉ

OS/2 WARP TROUBLESHOOTING DEMYSTIFIED

First Edition (December 1995)
Revision 0: 12-21-95

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 MERCHANTIBILITY OR FITNESS FOR A
PARTICULAR PURPOSE.

This publication could include technical inaccuracies or typographical errors.
IBM may make changes to the products described in this publication at any time.
IBM is not responsible for any damages resulting from the use of this
publication or any information contained herein. Section 2 of this document is
based on OS/2 Warp Problem Solving, 2nd Edition, and portions are copyright
1994 David P. Both, IBM, and New Riders Publishing.

It is possible that this publication may contain references to, or information
about, IBM products, 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.

(c) Copyright International Business Machines Corporation 1994, 1995. All
rights reserved.


ΓòÉΓòÉΓòÉ 1.1. Notices ΓòÉΓòÉΓòÉ

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.
Subject to IBM's valid intellectual property or other legally protectable
rights, any functionally equivalent product, program, or service 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 Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood,  NY
10594, U.S.A.

Licensees of this program who wish to have information about it for the purpose
of enabling:  (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation,
Department RM1A, 1000 N.W. 51st Street, Boca Raton, FL 33431,  U.S.A.  Such
information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.


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

TRADEMARKS AND SERVICE MARKS

The following terms in this publication are trademarks or service marks of the
IBM Corporation in the United States or other countries:

Presentation Manager

AT PS/2HelpCenter

ThinkPad

IBM

OS/2

LAN Server

The following terms in this publication are trademarks of other companies as
follows:


 1-2-3                                    Lotus Development Corporation

 AutoCAD                                  AutoDesk, Inc.

 Disk Manager                             OnTrack Systems, Inc

 Gammatech Utilities                      Soft Touch Systems

 Intel, Pentium                           Intel Corporation

 Lotus                                    Lotus Development Corporation

 Microsoft, MS, MS-DOS, MSCDEX Windows,   Microsoft Corporation
 Windows NT, Windows 95

 PCMCIA                                   Personal Computer Memory Card
                                          International Association

 Stacker                                  Stac Electronics

 VESA, VL-BUS                             Video Electronics Standards Association

 WordPerfect, Novell Netware              Novell

Other company, product, and service names in this publication may be trademarks
or service marks of others.


ΓòÉΓòÉΓòÉ 2. Preface ΓòÉΓòÉΓòÉ

PREFACE

OS/2 represents a major advance in the evolution of PC operating systems. For
many users OS/2 represents the perfect balance between compatibility,
usability, stability and performance. One of IBM's key marketing points of OS/2
is "crash protection," which makes OS/2 well suited for mission critical
applications.

OS/2 is, however, a complex system, and like any complex system, things do
occasionally go wrong. OS/2 Warp Troubleshooting Demystified is designed with
three goals in mind:

o   To equip you, the end user, with enough knowledge about how OS/2 works to
    recover from as many types of OS/2 difficulties as possible. In particular,
    this guide will show you how to make effective use of the recovery features
    built into OS/2 Warp.

o   As the old saying goes,  "An ounce of prevention is worth a pound of cure."
    With this in mind OS/2 Warp Troubleshooting Demystified will provide you
    with techniques that can be used to prevent OS/2 problems before they
    occur.

o   Solutions to the most common OS/2 problems are provided in a format that is
    clear and easy to understand. Trying to anticipate every possible problem a
    user may encounter, however, is an exercise in futility, and OS/2 Warp
    Troubleshooting Demystified does not even attempt to do so. Instead, this
    work will focus on providing you with general troubleshooting techniques
    that can be applied to any OS/2 related technical problem.

This work came about because you requested such a document. More documents of
this type on other technical support issues may be published in the future,
depending on your input. Please send any comments, suggestions, corrections,
and ideas for future documents of this type to:

[e-mail]

Enjoy,

Jason R. Kersten,
PC Company Help Center


ΓòÉΓòÉΓòÉ 3. Acknowledgments ΓòÉΓòÉΓòÉ

ACKNOWLEDGMENTS

This work would not have come about were it not for the efforts of several
people. I would like to thank the following individuals for their assistance
with the preparation of this document:

Doug Pahle
PC Company HelpCenter - Manager, Operating Systems Team

Jim Wilkerson
PC Company HelpCenter

Terry Bunn
PC Company HelpCenter

Mike Sports
PC Company HelpCenter

Gary Gaydos
PC Company HelpCenter


ΓòÉΓòÉΓòÉ 4. How to use this guide ΓòÉΓòÉΓòÉ

HOW TO USE THIS GUIDE

o   Audience and prerequisites

o   A road map to this work

o   Typographical conventions


ΓòÉΓòÉΓòÉ 4.1. Audience and prerequisites ΓòÉΓòÉΓòÉ

Audience and prerequisites

This guide is not designed as a replacement for your OS/2 User's manuals. You
should be familiar with how to use the OS/2 operating system before reading
this guide (The on-line tutorial is a good place to start). In particular, you
should be familiar with the following terms and procedures:

o   Basic computer terminology, such as RAM, ROM, Hard disk, floppy disk,
    monitor, and other basic peripherals, such as mice and printers.

o   Basic OS/2 and command line tasks, such as using subdirectories, copying,
    renaming, and deleting files and formatting floppy disks. You should also
    know how to edit a text file using a text editor such the E editor provided
    with OS/2. You should be familiar with using the OS/2 WorkPlace shell to
    launch programs, create and manipulate objects, and manage files and
    directories. Finally, you should be familiar with using OS/2's on-line help
    facilities and on-line command reference.

You will need a set of bootable OS/2 diskettes for many of the procedures in
this work. If  you purchased OS/2, the installation disks can be used for this
purpose. If your system came preloaded with OS/2 and you did not receive
diskettes, use the Create Utility Diskettes program in the System Setup folder
to create a set of bootable diskettes.


ΓòÉΓòÉΓòÉ 4.2. A road map to this work ΓòÉΓòÉΓòÉ

A road map to this work

Not all sections of this document may be relevant to you. The following should
give you an idea of which sections you should read:

o   Sections 1 and 5 discuss strategies and considerations to help you prevent
    problems before they occur. Section 1 lists general preventative
    strategies. Section 5 discusses various types of hardware as well as
    compatibility issues that sometimes arise when using that hardware with
    OS/2. All readers should read Section 1. If you are considering purchasing
    hardware to be used on an OS/2 system (or you want to know how well your
    existing hardware will work under OS/2), you should also read Section 5.

o   Sections 2 and 3 discuss troubleshooting procedures. Section 2 introduces a
    troubleshooting strategy that can be used to solve any technical problem,
    and also lists various support avenues available should you be unable to
    solve a problem on your own. Section 3 discusses how to use the recovery
    features built into OS/2 Warp. Section 3 also discusses the resource
    manager architecture of OS/2 Warp, and how to use it to avoid device
    contention conflicts. All readers should read Sections 2 and 3.

o   Section 4 and 6  discuss specific problems you may encounter when running
    OS/2. Section 4 contains a description of OS/2 error messages, as well as a
    "database" of often encountered problems with OS/2. Section 6 presents a
    line by line description of the OS/2 CONFIG.SYS. If you are looking for a
    solution to a specific problem with OS/2, read Secions 4 and 6.

o   Appendices A-D provide useful reference information. Appendix A discusses
    Corrective Service updates. Appendix B contains a complete description of
    the OS/2 Warp product family, including the differences between the various
    versions. Appendix C discusses considerations to keep in mind when running
    DOS and Windows programs under OS/2. Finally, Appendix D lists various
    operating limits and capacities of OS/2.

o   Appendix E is a glossary that defines new terms introduced in the text.

o   Appendix F discusses the OS/2 Professional Certification Program from IBM.

o   Appendix G lists various IBM and non-IBM books available about OS/2.


ΓòÉΓòÉΓòÉ 4.3. Typographical conventions ΓòÉΓòÉΓòÉ

Typographical conventions

Words that appear highlighted like this or colored like this (The color used
will vary depending on how your desktop scheme is set) are hypertext links to
other related portions of this document. If you double click on them, you will
be taken instantly to that section of the document.

Words appearing in boldface like this in the text of this work are new terms
that may be unfamiliar to the reader. If you double click on the word, you will
see its glossary entry. Many new terms are defined as they are introduced,
though you may find a more complete definition in the glossary. You can also
browse the complete glossary, which is contained in Appendix E.

Note:  Text set of in this manner--preceded by the word NOTE--presents
important information or special instructions, as well as potential pitfalls.

Words that appear in ALL CAPS, such as CONFIG.SYS, are filenames. Filenames
that represent programs are presented without the .EXE or .COM extension for
simplicity (e.g. SYSLEVEL instead of SYSLEVEL.EXE).

Text that appears in a monospaced font like this indicates information you
either see on the screen or enter into the computer, such as a command or menu
option.

Text that is both monospace and green like this indicates a replaceable
argument or parameter. For example, you would replace the word file in the
command COPY file C:\OS2  with the name of the file you are trying to copy.

Monospaced text that is colored blue like this indicates things you might see
on the screen, such as lines from a settings file or output from a program.

;Text like this that is both italicized and preceded by a semicolon-;- indicates
;a text annotation. Text annotations are for your benefit and should not be
;entered into the computer. Annotation may appear both in blue regions (to
;explain what you see on the screen) or outside of them (to explain a command).

Ellipses (...) are often substituted for path information when the path may
vary from given the example. For example, you may see something like
DEVICE=...\SSMDD.SYS instead of DEVICE=C:\MMOS2\SSMDD.SYS because on your
system, SSMDD.SYS may be located somewhere other than the C:\MMOS2 directory.
Ellipses may also be used in file listings to indicate some sections have been
omitted.


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

This link goes nowhere.


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

A glossary definition would normally appear here.


ΓòÉΓòÉΓòÉ 5. Section 1. An Ounce of Prevention... ΓòÉΓòÉΓòÉ

SECTION 1. AN OUNCE OF PREVENTION...

The best approach to problem solving is problem prevention. This section will
discuss some ways you can avoid problems with OS/2. Some of these strategies
are decisions that must be made before OS/2 is installed-others can be used
after installation. Since many IBM systems come preloaded with OS/2, some of
these strategies will only apply if you are required to reinstall OS/2.


ΓòÉΓòÉΓòÉ 5.1. 1.1 Dual Boot vs. Boot Manager, and hard drive partitioning issues ΓòÉΓòÉΓòÉ

1.1 Dual Boot vs. Boot Manager, and hard drive partitioning issues

There are some DOS and Windows programs that simply will not run reliably under
OS/2. Fortunately, OS/2 provides two ways that allow you to have more than one
operating system on your hard drive.


ΓòÉΓòÉΓòÉ 5.1.1. 1.1.1 Dual boot, and why it should usually be avoided ΓòÉΓòÉΓòÉ

1.1.1 Dual Boot, and why it should usually be avoided

The first method is called dual boot, and if you purchased an IBM PC with
Select-A-System (Both OS/2 and DOS and Windows on your hard drive), then you
have dual boot. Dual boot allows both DOS/Windows 3.1 and OS/2 to coexist on
the same hard drive partition (Dual booting between OS/2 and Windows 95 is not
supported). The system always starts up with the same operating system until
you click an icon (or enter a command) to change to the other operating system.
Dual boot is the simplest way to have two operating systems on your hard drive.
If you install OS/2 on a hard drive that has DOS and Windows already installed,
dual boot functionality will be installed automatically.

Dual boot's simplicity is also its weakness. When you boot from DOS to OS/2 (or
vice versa), dual boot makes modifications to your hard drive and swaps
configuration files, reconfiguring the system to use the other operating
system. If something goes wrong during this behind-the-scenes hard disk
preparation, you may end up with a system that will not boot either operating
system! Because of its simplicity, however, dual boot may still be the best
choice if you do not intend to switch between operating systems very often.

If you have dual boot installed and are currently in a DOS/Windows environment,
you can use the following command to restart the computer with OS/2:

BOOT /OS2

Note:  If your version of DOS has the ability to bypass the startup files on
bootup, you may wish to do this before using the BOOT command while in DOS.
This will prevent an ill-behaved TSR from interfering with the dual boot
process and causing hard drive corruption.

Likewise, if you are in OS/2 and wish to reboot the computer with DOS/Windows,
either launch the dual boot icon in the command prompts folder or open an OS/2
Window and type the following command:

BOOT /DOS


ΓòÉΓòÉΓòÉ 5.1.2. 1.1.2 Boot Manager, an elegant and safer alternative ΓòÉΓòÉΓòÉ

1.1.2 Boot Manager, an elegant and safer alternative

Boot manager is the second method of allowing two operating systems to coexist
on the same hard drive. A system configured with boot manager will display a
menu at startup that will allow you to choose between operating systems.
Unlike dual boot, with boot manger, each operating system resides on its own
partition on your hard disk. The boot manager menu simply allows you to pick
which of these partitions to boot from; it does not care what operating system
is installed on that drive.

Because boot manger requires you to divide your hard disks into partitions, it
is somewhat more complex to set up than dual boot, and requires some planning
ahead. The end result, however, is a system that is both less likely to
encounter problems when switching between operating systems and easier to
recover if problems do occur. To set up boot manager, you must choose Advanced
Installation when installing OS/2 (See Chapter 18 in the OS/2 Warp User's
Guide).

Note:  If you have an IBM system that came preinstalled with Warp, you may have
a slimmer version of the User's Guide that does not have information on Boot
Manager. You may either order the full OS/2 documentation set for OS/2 or
purchase one of several third party books that discuss OS/2 installation.

To avoid problems, you should install OS/2 into its own partition, so that if
reinstallation becomes necessary, you can format and install to a clean hard
drive without affecting applications and data. Figure 1-1 below shows a
recommended Boot Manager configuration that allows for both DOS /Windows 3.1
(or Windows 95) and OS/2 Warp.

You should keep the following considerations in mind when using Boot Manager:

o   Some systems have difficulties recognizing large IDE hard drives with over
    1024 cylinders (This includes all 540Mb and larger IDE drives). This is a
    limitation of the IDE controller and the system's BIOS, not of OS/2. You
    may need an updated BIOS and/or an enhanced IDE controller if your system
    does not recognize large IDE disks. Newer BIOS's with EIDE (see Section
    5.2.2) remap the drive geometry so that operating systems see the drive as
    having less than 1024 cylinders. If your IDE hard drive has over 1024
    cylinders, any bootable partitions containing operating systems must reside
    within the first 1024 cylinders (503 Mb-see note in Section 5.2.2).

o   All operating systems other than OS/2 2.0 or later (this includes DOS and
    Windows 95) must be installed in a primary partition on the first physical
    hard drive (this will always map as drive C:). OS/2 2.0 and later may be
    installed on any partition on any physical drive. Boot manager itself must
    be installed on the first physical drive.

o   You may have up to 4 primary partitions (or 3 primary partitions and one
    extended partition) on any physical drive. Boot Manager counts as one
    primary partition. You may create as many as 16 logical drives within an
    extended partition. Note that all primary partitions on all drives are
    always mapped before any logical partitions. To avoid unexpected drive
    letter remapping, you should make all partitions on any additional hard
    drives you add to the system logical drives.

Figure 1-1: Recommended Boot Manger Configuration for 540Mb or larger hard
drives


ΓòÉΓòÉΓòÉ 5.2. 1.2 HPFS vs. FAT ΓòÉΓòÉΓòÉ

1.2 HPFS vs. FAT

OS/2 can use 2 types of file systems: HPFS and FAT. A file system determines
how files are logically stored on the hard drive. FAT, or File Allocation
Table, is the file system used by DOS, Windows 3.1, and Windows 95.  HPFS is a
new High Performance File System designed for use by OS/2. In this section we
will first discuss the limitations of FAT, then how HPFS addresses each of
them.


ΓòÉΓòÉΓòÉ 5.2.1. 1.2.1 File Allocation Table (FAT): an aging standard ΓòÉΓòÉΓòÉ

1.2.1 File Allocation Table (FAT): an aging standard

FAT was introduced with DOS 1.0 and the original IBM PC in 1981, and was
optimized for use with floppy disks.  FAT has several limitations that make it
impractical for use with large hard drives under OS/2:

o   Variable Cluster Size. Files are allocated by FAT in fixed multiples of
    sectors (512 bytes for all modern hard drives) called clusters or
    allocation units. The size of these allocation units varies according to
    the size of the hard drive. For a typical 1Gb hard drive, the allocation
    unit size is 32Kb. In other words, if you store a file that is only 100
    bytes in size (like AUTOEXEC.BAT, for example), the file will take up 32Kb
    on your hard drive, wasting nearly the entire allocation unit. This is an
    extreme example, but a 1Gb hard drive typically wastes up to 20% of its
    space in this manner. Table 1-1 shows cluster sizes for various hard drive
    capacities. FAT volumes are limited to 2Gb in size.

Table 1-1: FAT Cluster Sizes for Various Hard Drive Capacities

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDrive Size                    ΓöéSectors/Cluster     ΓöéCluster Size   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé0-5.9Mb                       Γöé8                   Γöé4Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé16-31.9Mb                     Γöé4                   Γöé2Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé32-63.9Mb                     Γöé4                   Γöé2Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé64-127.9Mb                    Γöé4                   Γöé2Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé128-255.9Mb                   Γöé8                   Γöé4Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé56-511.9Mb                    Γöé16                  Γöé8Kb            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé512-0.9Gb                     Γöé32                  Γöé16Kb           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé1-1.9Gb                       Γöé64                  Γöé32Kb           Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

o   File Fragmentation. Suppose you write a 1Mb file to the hard disk. Now
    suppose you write another 1Mb file to the hard disk. If the disk is
    formatted with FAT, the second file will be placed physically adjacent to
    the first file. Now suppose the first file grows to 2Mb in size. Since the
    second file is right next to the first one,  the remainder of the first
    file is written starting at the end of the second file. The first file is
    now noncontiguous on the hard drive. Over time, several files will become
    fragmented in this manner, degrading hard drive performance and causing
    unnecessary wear and tear on your hard disk's read/write heads. Over the
    years, many disk defragmentation utilities have been introduced to deal
    with these problems. These utilities essentially reorganize the files on
    your hard disk in a contiguous fashion. In multitasking environments,
    however, your hard disk may become fragmented relatively quickly, so these
    utilities must be used often. OS/2 does not include a defragmentation
    utility, nor can you use a DOS defragmenter under OS/2. If you are in a
    dual boot environment (see section 1.1.1), you can run the DEFRAG utility
    provided with PC-DOS 6.3 and above while in the DOS environment.

o   "8.3" File Name Restriction. All FAT formatted drives are subject to the
    now infamous 8.3 file naming limitations: 8 characters for the file name
    (Alphanumeric only-no spaces) with an extension of up to 3 characters. OS/2
    and Windows 95 both allow for long file names on FAT formatted drives
    (their respective techniques for doing so are quite different), though in
    both environments the implementations are somewhat awkward and suffer from
    limitations.

o   Inefficient File Searching. Files in a directory on a FAT volume are not
    stored in any particular order, so the operating system must look through
    every file in a directory until it finds the one it's looking for.

o   Error recovery. FAT lacks any kind of extensive fault tolerance, so it is
    relatively easy to end up with unrecoverable file system errors such as
    cross linked files (This is especially a problem in dual boot environments)
    and lost clusters.

o   Lack of native support for extended attributes. The FAT file system allows
    for four file attributes: Archive, System, Read-Only, and Hidden. OS/2 uses
    additional attributes for a file, such as the icon associated with the
    file, the long file name for the file when viewed from the workplace shell,
    and other information. To implement these extended attributes (or just
    EA's) under FAT, OS/2 makes use of some previously undocumented structures
    of the FAT filesystem. All extended attribute information for FAT volumes
    is stored in a hidden file called EA DATA. SF in the root directory of the
    drive. Since EA DATA. SF holds the extended attribute information for every
    file on the drive, the integrity of the system becomes extremely vulnerable
    if this file is damaged.

Despite its limitations,  FAT may still be the file system of choice in certain
environments, particularly those where files must be accessed from both OS/2
and DOS/Windows. Since DOS/Windows cannot recognize HPFS volumes, dual boot
partitions will by definition be FAT. For small volumes (under 80Mb), FAT may
actually be faster than HPFS. In addition, FAT has less system overhead than
HPFS, and should probably be used on systems with less than 8Mb.

Note:  Do not run any kind of DOS Disk repair utility (e.g. DOS's CHKDSK)
against a FAT volume that is used by OS/2, particularly the OS/2 boot volume.
Doing so may damage the extended attributes, leading to a corrupt OS/2
installation.


ΓòÉΓòÉΓòÉ 5.2.2. 1.2.2 High Performance File System (HPFS) ΓòÉΓòÉΓòÉ

1.2.2 High Performance File System (HPFS)

Since version 1.2, OS/2 has provided support for a new file system known as
HPFS, or High Performance File System. HPFS was optimized for use on large hard
drives, and can provide tremendous performance and space utilization
improvements over FAT on large hard drives.  The advantages of HPFS are
discussed below:

o   Better Space Utilization. Unlike FAT, files are allocated by HPFS per 512
    byte block,  regardless of the hard drive size. HPFS volumes can be larger
    than 2Gb, though if you have a large RAID drive or other large hard disk,
    you should try to keep the size of a single volume under 16Gb to avoid
    potential recovery problems.

o   Reduced File Fragmentation. HPFS avoids file fragmentation by leaving
    "growing room" in between files when they are written to disk. HPFS drives
    rarely become fragmented, but there are third party defragmenters (such as
    Gammatech HPFSOPT) available.

o   NATIVE long file name support. File names under HPFS can be up to 255
    characters long. Unlike with FAT, support for long file names under HPFS is
    an integral part of the file system.

o   Efficient File Searching. Files in a directory on an HPFS volume are stored
    in alphabetical order, so the operating system can search for files using a
    binary search. The difference this makes becomes apparent when dealing with
    large volumes.  Studies have shown the average number of disk reads when
    finding files under HPFS is reduced by over 600% compared to FAT!

o   Error recovery. The design of the HPFS file system has been enhanced to
    allow greater likelihood of recovery if an error occurs:

    -   Filesystem Dirty Flag. If a system using HPFS is shut down improperly
        (e.g. a system crash), a "dirty flag" is left set on the volume. When
        OS/2 reboots, it will detect the dirty file system and automatically
        run CHKDSK to repair any file system errors on the drive.

    -   Hotfixes. If  a bad sector is encountered while writing data to an HPFS
        drive,  the data is written to a safe location automatically by means
        of a hotfix.

    -   Better data recovery features. The structure of HPFS makes it easier to
        recover lost data. Situations under FAT that would have resulted in
        data loss (e.g. lost clusters) can often be recovered from with HPFS.

o   Native support for extended attributes. Unlike FAT, HPFS includes native
    support for extended attributes. Under HPFS the extended attributes are
    stored with the file itself. This improves speed because the operating
    system does not have to look up the information in a centrally stored file,
    and also reduces the likelihood of some unexpected event (such as a power
    failure or system crash) corrupting the extended attributes.

Remember that HPFS volumes cannot be seen from DOS, so if you are using dual
boot or boot manger to run DOS/Windows on your system, at least one the
partitions must be FAT. Also, files and directories with long filenames on HPFS
drives will be invisible to DOS and Windows applications running under OS/2.


ΓòÉΓòÉΓòÉ 5.3. 1.3 Using the OS/2 Warp archiving facility ΓòÉΓòÉΓòÉ

1.3 Using the OS/2 Warp archiving facility

OS/2 Warp has the capability of archiving the system configuration every time
the system is started. If you enable "create archive at each system restart"
from the Archive tab of the Desktop settings notebook, the system will create a
new archive each time the system is started. Other than a slight delay at
startup, the backup process is completely transparent to the user. "Archive
location" determines the directory where the archives are kept. An archive may
vary in size from around 100K to 1Mb in size depending on the complexity of the
configuration and the files chosen to back up. Because of this, you may need to
move the location of the archives to another partition. Warp will keep up to 3
archives in addition to the original installation archive. If you keep the
archiving feature enabled, the operating system will replace the oldest of the
3 archives. See Section 3.5.1 for details on restoring an archive.

Note:  If you change the location of the archives to a new drive, make sure the
new drive is using the same file system as the boot drive. FAT and HPFS use
different formats for storing extended attributes, and this could cause
problems when storing archives from one file system on a drive with the other
file system.

Figure 1-1: Desktop Settings Notebook showing Archiving Feature


ΓòÉΓòÉΓòÉ 5.3.1. 1.3.1 Including your own files in the archive ΓòÉΓòÉΓòÉ

1.3.1 Including your own files in the archive

When OS/2 Warp creates archives, it uses the file OS2.KEY in the \OS2\ARCHIVES
directory to determine which files are backed up. You can modify this file to
include your own files, such as application or network configuration files.
Simply add as many of the following lines as necessary to include your
additional files:

KEYFILE:filename

where filename is the complete path and filename of the file to be archived.
You can even archive files with system, hidden, and read only attributes (such
as the OS/2 Kernel).


ΓòÉΓòÉΓòÉ 5.3.2. 1.3.2 How archives are stored ΓòÉΓòÉΓòÉ

1.3.2 How archives are stored

There are two files in the OS2\ARCHIVE directory in addition to the directories
for the archives themselves. OS2.KEY, as mentioned earlier, is user editable
and determines which files are archived in addition to the desktop directory
tree. The following lines appear in the default OS2.KEY:

KEYFILE:OS2.INI
KEYFILE:OS2SYS.INI
KEYFILE:C:\CONFIG.SYS
KEYFILE:C:\STARTUP.CMD
KEYFILE:C:\AUTOEXEC.BAT
KEYFILE:C:\OS2INIT.CMD

The file ARCHIVES.$$$ keeps track of the number and dates of archives in the
system. In each of the individual archive directories (named 0X, 01, 02, and
03, respectively), there are a number of files and a DESKTOP directory. Each of
the keyfiles named in OS2.KEY is renamed 0, 1, 2, etc. and copied into the
appropriate archive directory. The file KEYS.$$$, also in each of the archive
directories, keeps track of these keyfiles, and maps each numbered keyfile to
its true filename. The DESKTOP directory contains the entire DESKTOP directory
tree for the archived configuration.


ΓòÉΓòÉΓòÉ 5.4. 1.4 Service Packs, CSD's, and FixPaks: "If it ain't broke, don't fix it." ΓòÉΓòÉΓòÉ

1.4 Service Paks, CSD's, and FixPaks: "If it ain't broke, don't fix it."

Occasionally IBM will release updated code for OS/2 in the form of FixPaks.
FixPaks (and other corrective service updates) generally do not add new
features or functions to the operating system, but are rather designed to fix
problems reported against OS/2 since it was released.

Unfortunately, FixPaks can potentially introduce new problems as well as fix
existing ones, so you should avoid applying them unless you have a specific
problem that has been addressed in that FixPak. Most FixPaks include a text
file (an APAR listing) listing the various problems that have been resolved in
that particular FixPak. If you suspect you are having a problem that has been
addressed, double-check this APAR listing before installing the FixPak. (See
Appendix A for a discussion of OS/2 FixPaks and service levels).

In some cases you may be required by OS/2 technical support to apply a FixPak
in order to resolve a problem. If you do install a FixPak, you should run
CHKDSK against your OS/2 boot drive (see Section 3.1) and back up any critical
files before proceeding. If you attempt to install a FixPak on a system with a
corrupt file system, the corruption can be propagated further.

Note:  Never attempt to install a fixpak over a system that does not boot up
properly or that has possible file corruption (i.e. invalid CONFIG.SYS or
corrupt desktop). Doing so will usually aggravate the problem, and may
propagate the corruption further.


ΓòÉΓòÉΓòÉ 5.5. 1.5 Make your utility (and installation) diskettes immediately ΓòÉΓòÉΓòÉ

1.5 Make your utility (and installation) diskettes immediately

There are some error recovery measures which simply cannot be performed when
OS/2 is started from the hard drive (such as when a CHKDSK is necessary, or
when the OS/2 boot files become corrupted). In these cases it helps to have a
set of OS/2 boot disks available. Although the installation disks themselves
are bootable, it may not always be practical or desirable to have a set at
every workstation. OS/2 Warp provides a Create Utility Diskettes function which
will create a set of three diskettes containing the necessary recovery
utilities. You can run Create Utility Diskettes either from its icon in the
System Setup folder or by running the BOOTDISK.EXE program in the \OS2\INSTALL
directory.

Many of the procedures in this work assume you have a set of bootable OS/2
diskettes; either the utility diskettes or the installation diskettes. If you
do not have either, make your utility diskettes before doing anything with the
system, especially before any configuration changes. If you have an IBM system
preloaded with Warp, you should also run the Diskette Factory Program on your
system and make all of the OS/2 installation diskettes (along with any other
OS/2 display and/or audio driver diskettes).

Note:  If your system will not start up, you maybe be able to use the recovery
choices menu (see Section 3.5.1) to get to the maintenance desktop. You can
then run the Make Utility Diskettes program from there. The diskettes can also
be downloaded from the IBM PC Co. BBS (see Section 2.2.3). The file names are
WARPUT01.DSK, WARPUT02.DSK, and WARPUT03.DSK. You will also need to obtain
LDF.COM to unpack the diskette images.

The utility disks include the following recovery utilities (all of which are on
diskette 3):

TEDIT.EXE          ;Text based OS/2 editor

BACKUP.EXE / RESTORE.EXE   ;Command line backup/restore (floppy disks only)

CHKDSK.COM          ;Hard disk error recovery utility

FDISK.COM          ;Manage hard disk partitions

FORMAT.COM          ;FORMAT command

SYSINSTX.COM         ;Write OS/2 boot blocks and loader

(Note: SYSINSTX does NOT copy the OS/2 kernel files)

OSDELETE.EXE         ;Completely removes OS/2 from the hard disk


ΓòÉΓòÉΓòÉ 5.6. 1.6 General problem avoidance strategies and recommendations ΓòÉΓòÉΓòÉ

1.6 General problem avoidance strategies and recommendations

o   README Files. Often a software package will require additional installation
    procedures and considerations not outlined in the installation guide. This
    information is usually contained in a README file contained on the program
    disks. You should always view the README file (especially the OS/2 README),
    if present,  to determine if there are any additional steps or
    considerations for your system.

o   Backup, Backup, and Backup again. No matter how careful you are; no matter
    how cautious and meticulous you are about following directions, your system
    WILL hang at some point. And it will generally choose to do so at a most
    inopportune time (The author speaks from experience here). You cannot
    prevent it entirely from happening, but you can make sure you are covered
    by making backups of your critical data files, as well as any applications
    you do not have installation disks for.

    If you are attempting to back up your entire system, be sure to use a
    utility that is capable of backing up all of OS/2's system files, and that
    the utility can handle extended attributes. In particular, DO NOT use DOS
    or Windows based utilities to back up an OS/2 system. If you have a tape
    backup unit, there are several utilities available which will allow you to
    back up the entire system, including the OS/2 system files.

    Many applications modify the CONFIG.SYS, AUTOEXEC.BAT, the OS/2 .INI files,
    Windows .INI files, or some combination of the above. In addition, they may
    copy files into various OS/2 or WIN-OS/2 system directories. Thus, if you
    are forced to remove and reinstall OS/2, your applications will usually
    have to be reinstalled. Note that although your data files will not be
    lost, you may lose any special settings or configuration changes you have
    made to your application since you originally installed it. Usually it is
    sufficient to reinstall the application into the directory where it was
    originally installed. This will restore any missing files and system
    configuration changes.

o   Don't take shortcuts when installing OS/2. There are two IBM-supported
    methods of installing OS/2: via the original medium (i.e. diskettes or
    CD-ROM), or over a LAN-Server network via CID
    (Configuration-Installation-Distribution) on the target machine. If you
    attempt to install OS/2 by any unsupported method and call IBM for
    technical support,  you will be required to reinstall by one of the above
    supported methods before support is given.

    There are several reasons why these methods are unsupported. To begin with,
    even machines of the same brand that may seem identical may have subtle
    hardware differences (e.g. BIOS revisions and memory configurations) that
    must be detected by OS/2 during installation. In addition, the extended
    attributes and/or boot record information may not get transferred properly.
    In particular, the following commonly attempted methods are not supported:

    -   Copying OS/2 from one computer to another via a direct cable connection
        (e.g. LapLink).

    -   Mirroring the contents of a hard drive over a network.

    -   XCOPYing OS/2 from one drive to another.

    -   Installing OS/2 on one machine, then transferring the hard drive to
        another machine.

    -   Installing "Red box" Warp (Warp for Windows) over "Blue Box" Warp (Warp
        with WIN-OS/2) and vice versa.

o   When you install Warp, you can choose between advanced and easy install.
    Easy install makes a number of choices automatically which may not be valid
    for your machine, and you will not be given a chance to go back and change
    the choices it made during installation. Because of this, you should
    probably choose advanced install to avoid problems.

o   Use Parity or ECC memory. Many newer systems (including some IBM systems)
    use non-parity memory. OS/2 is very memory intensive, and memory errors can
    cause numerous hangs and other problems that are difficult to diagnose.
    Parity memory is recommended for business systems running OS/2, and ECC
    (Error Checking and Correcting) memory is recommended for mission critical
    applications and servers. See Section 5.4 for more information.

o   Hardware diagnostics do not detect all errors. Many systems ship with
    diagnostic diskettes that perform hardware tests on the system.
    Unfortunately, these hardware tests do not catch all errors. Because OS/2
    is so demanding on the hardware, it will often detect hardware errors that
    diagnostics misses (particularly memory errors). If you are getting
    repeated trap errors while booting OS/2 and suspect you may have hardware
    problems, do not be surprised if the diagnostics diskette for your system
    does not catch the error. Often the best course of action in these
    situations is to swap hardware components until the failing component is
    isolated. Naturally, this should be done only after exhausting any
    software-related possibilities.


ΓòÉΓòÉΓòÉ 5.7. 1.7 Always shut your system down properly ΓòÉΓòÉΓòÉ

1.7 Always shut your system down properly

Always shut down OS/2 properly before turning the system power off. This allows
OS/2 to close all open files and write all cached information to the hard
drive. Failure to shut down the system properly can cause any number of
symptoms, ranging from desktop corruption to a system that will not boot at
all. There are several ways to shut down the system:

o   Click the Shutdown button on the launchpad.

o   Bring up the Desktop pop-up menu and select shutdown.

o   Open an OS/2 Window and type SHUTDOWN, then hit Enter.

If you lose control of the mouse, you can use the keyboard to shut the system
down:

1.  Close all open Windows using Alt-F4.

2.  Use Control-Esc to get to the window list, then switch to the OS/2 Desktop.

3.  Use Ctrl-\ to bring focus to the desktop.

4.  Use Shift-F10 to bring up the popup menu for the desktop. Then use the
    arrow keys to select Shutdown.

There are some cases when the system may hang or become unresponsive, making a
normal shutdown impossible. If this happens, you may be able to use
Ctrl-Alt-Delete to perform a "proper reboot." If successful, you should see a
message stating The system is restarting. please wait... This will perform a
proper shutdown, with the exception that any desktop customizations you have
made will not be saved. When the computer starts to go through POST, you can
either turn the power off at this point or allow the system to reboot


ΓòÉΓòÉΓòÉ 6. Section 2. Troubleshooting Procedures ΓòÉΓòÉΓòÉ

SECTION 2. TOUBLESHOOTING PROCEDURES

Many troubleshooting guides use a "database" approach; trying to list every
known problem and a solution, without explaining how the solution was arrived
at. This is not such a work. Although "problem-solution" documents can be
helpful (Section 4, is in fact, in this format), they are no substitute good
troubleshooting skills. No problem-solution database can list every known
problem and solution. Instead of trying to anticipate every problem you may
have with OS/2, this guide will give you general troubleshooting techniques
that can be applied to any technical problem.

Although OS/2 is rigorously tested, IBM cannot insure that you will never
encounter a problem. What we can insure is that if you do encounter a problem,
you are equipped with the tools necessary to solve it. This chapter is a good
place to start. The end of this chapter discusses other avenues of help
available to you from IBM and other sources should you be unable to solve the
problem yourself.


ΓòÉΓòÉΓòÉ 6.1. 2.1 The troubleshooting process ΓòÉΓòÉΓòÉ

2.1 The troubleshooting process

Five basic steps are involved in any problem solving endeavor: Knowledge,
Information gathering, Deduction, Action, and Testing. These steps are
universal in solving almost any kind of technical problem, whether it be fixing
a problem with OS/2 or diagnosing the clattering noises your car makes.


ΓòÉΓòÉΓòÉ 6.1.1. 2.1.1 Knowledge: Do your homework ΓòÉΓòÉΓòÉ

2.1.1 Knowledge: Do your homework

Expertise in the subject in which you are attempting to solve a problem is the
first and perhaps most critical step. You must be knowledgeable both about OS/2
and about the hardware on which OS/2 is installed. One very important rule
about computer problem solving in particular is that "a little knowledge can be
very dangerous." If you are unsure of what you are doing, you could do further
damage instead of solving your problem. This is why expertise is critical.

Knowledge about OS/2 can come from a variety of sources. The most valuable
source of knowledge is experience, which you can gain through experimentation.
Other valuable sources of knowledge include:

o   Books (especially your user's manuals) and guides such as the one you are
    reading now. A number of well written books about OS/2 are available (see
    Appendix G). If you received a "condensed" user's manual (or no manual at
    all) you can purchase the complete documentation set for OS/2 from IBM.

o   Classes and professional certification programs (see Appendix F).

o   Friends or colleagues who have experience with OS/2.

o   Internet newsgroups and other on-line discussion forums.


ΓòÉΓòÉΓòÉ 6.1.2. 2.1.2 Information gathering: "Just the facts, ma'am" ΓòÉΓòÉΓòÉ

2.1.2 Information gathering: "Just the facts, ma'am"

Most of successful problem determination is careful observation. It is
important to note all the symptoms, including those that may not seem relevant
to the problem. It is especially important to note the exact wording of any
error messages that occur, including any error numbers associated with those
messages. Finally, take note of what is working properly.

The next step is to ask yourself questions about the symptoms you observe, and
gather general information about your system configuration. Aside from the
questions that are specific to the problem at hand, some other questions
include:

o   What is the source of the error message, if there is one (i.e. hardware?
    OS/2? application software?)?

o   What is your current system configuration? In particular, you should have
    the following information:

    -   What is the speed, microprocessor type, and brand of your system?

    -   How much RAM is in your system?

    -   What type of video card do you have? What chipset does it use? What
        version of the drivers are you using?

    -   Are you using SCSI or IDE, or both? If you have a CD-ROM how is it
        connected? (e.g. SCSI, proprietary interface, IDE, etc.). What are the
        capacities of your hard drives?

    -   Did you install OS/2 from a) diskettes? b) CD-ROM?, c) via CID over a
        network, or did it d) it came preloaded?

    -   Have you applied any Service Packs or other updates?

    -   Do you have any other hardware devices in the system, such as tape
        drives or networking cards? If so, how are they configured?

    -   What other software do you have installed (e.g.
        networking/communications, application programs, etc.)?

    -   What BIOS revision level is your system currently at?

o   Does this problem resemble another you may have seen before? If so, what
    are the commonalties?

o   What was running just before the error occurred?

o   What did you expect to happen if the error had not occurred?

o   Has anything about the system hardware or software changed recently (i.e.
    have you installed anything or changed any settings)?

The important thing to remember here is to gather as much information about the
circumstances and the environment in which the error occurs as you possibly
can. Never make any unwarranted assumptions, and do not jump to conclusions. If
you support OS/2 systems for your company, for example, do not assume that OS/2
was installed correctly, or that your users have not changed anything.


ΓòÉΓòÉΓòÉ 6.1.3. 2.1.3 Deduction: Putting the puzzle pieces together ΓòÉΓòÉΓòÉ

2.1.3 Deduction: Putting the puzzle pieces together

Deduction is the trickiest part of the troubleshooting process. You must try to
figure out the cause of the problem based on your observations in the
information gathering stage above. This is not necessarily a scientific
process, and often involves a great deal of intuition and "gut instinct."
Deduction is where your expertise comes in to play. If you troubleshoot often
enough, you will eventually get to the point where you often have a pretty good
idea of what the solution is, even if you have never encountered the problem
previously.  Be careful not to become over-confident and neglect the
information gathering step.

Your deduction skills will increase with experience. In some cases deduction is
a fairly easy process, and the problem will be readily apparent. In other cases
it is perhaps the most difficult part of the entire process. Remember that the
problem causes the symptom, and not vice-versa.  In many cases, the real
problem may appear to have little relationship to the symptoms you observe, as
you will see in Section 4.


ΓòÉΓòÉΓòÉ 6.1.4. 2.1.4 Action: Rectify the problem ΓòÉΓòÉΓòÉ

2.1.4 Action: Rectify the problem

Once you have determined the nature of the problem, the next step is to perform
the appropriate repair action. This is usually relatively straightforward.
After you know the cause of the problem it is usually easy to determine the
correct repair action to take.

Sometimes repair procedures may be somewhat tedious, and involve several steps
that may seem repetitive. Do not try to take shortcuts by skipping steps or you
may end up with a worse problem than the one you started with.


ΓòÉΓòÉΓòÉ 6.1.5. 2.1.5 Testing: Make sure it works. Then make sure again ΓòÉΓòÉΓòÉ

2.1.5 Testing: Make sure it works. Then make sure again

After making the repair action, you should rigorously test your fix. If the
repair does not work, you should begin the procedure over again, starting with
the Information gathering portion of the process. It is possible the symptoms
have changed. If so, you will need to be aware of this to make more informed
deductions the next time through the process. Even if the problem still exists,
the altered symptom will help you determine a better course of corrective
action.

Do not assume a problem has been fixed without rigorous testing. Sometimes the
systems may appear to go away for a while, but then come back. Also try to make
sure the fix did not break anything else that was working previously.


ΓòÉΓòÉΓòÉ 6.1.6. 2.1.6 Putting it all together ΓòÉΓòÉΓòÉ

2.1.6 Putting it all together

The following example will show you how the process works. Suppose, for
example,  you enter the EPM command to start the enhanced editor at the OS/2
command prompt and receive the following response:

[C:\]epm myfile.txt
SYS1041: The name specified is not recognized as an
internal or external command, operable program or batch file.

It is simple to observe this error message, but the problem is still not
apparent. You need to get more information. In this case, you know how to use
OS/2's on-line help facility, so you type help 1041 at the command line to get
a better description of the error. The results are shown  below:

[D:\]help 1041

SYS1041: The name specified is not recognized as an
internal or external command, operable program or batch file.

EXPLANATION: The name specified should be one of the following:
o  The name of a batch file whose file extension is .CMD.
o  The name of an executable program whose file extension
  is .EXE or .COM.
o  The name of an OS/2 external command.
o  The name of an OS/2 internal command.

For the first 3 cases (if a path for the command was not specified at
the command prompt), the file must reside in the current directory or
in one of the directories specified by the PATH environment variable.

ACTION: Retry the command using a correct name or path.

(You could also have entered help SYS1041, but OS/2 assumes you are talking
about a SYS message unless specify otherwise).

Not only does the OS/2 help facility provide more information about the
problem, it also provides one or more possible corrective actions for you to
take.

You use the System Editor object on your desktop to check the PATH statement in
the CONFIG.SYS and discover that the C:\OS2\APPS directory where EPM.EXE
resides is not in the path. Clearly the corrective action here is to add
C:\OS2\APPS to the path. After you make the correction and shut down and
reboot, you open an OS/2 command line window and retry your original command to
see if it works. If so, you have solved the problem. This was a simple problem,
but some knowledge of OS/2 (how to get help for the error message) and
intuition (You realize that you could use an editor by opening the System
Editor object on the desktop) was required to solve the problem.

Another important lesson that can be learned from this example is that there is
sometimes more than one solution to a problem. For example, you could just as
easily have used the E command from the command line to launch the OS/2 System
Editor and check the CONFIG.SYS.


ΓòÉΓòÉΓòÉ 6.2. 2.2 Other sources of help ΓòÉΓòÉΓòÉ

2.2 Other sources of help

No matter how well trained you are, there will always be certain types problems
that you will be unable to resolve on your own. You can obtain OS/2 support
from a number of places. The IBM PC Company provides OS/2 support for the
systems on which it preloads or bundles OS/2. The IBM PC Company also provides
support for OS/2 to all IBM Authorized Dealers regardless of the system
involved, as long as it is a system on which OS/2 is supported (see Section
5.5).

Many electronic information services provide discussion areas for OS/2 users.
Among these are America On-Line, Prodigy, Delphi, and CompuServe. In many cases
these are users helping users. Many IBM'ers also provide unofficial assistance
on these services. IBM currently provides official electronic support for OS/2
on three electronic services.


ΓòÉΓòÉΓòÉ 6.2.1. 2.2.1 CompuServe ΓòÉΓòÉΓòÉ

2.2.1 CompuServe

IBM has a strong official presence on CompuServe. The OS2USER forum is very
active with users helping users. The OS2SUP forum is where IBM maintains its
official OS/2 support presence on Compuserve. IBM also maintains CompuServe
forums for developers and vendors of OS/2 programs. The latest patches and
Service Packs are usually available for download from CompuServe. IBM also
maintains libraries of Employee Written Software (EWS) and other freeware and
shareware OS/2 files on Compuserv, and the IBM PC Company provides hardware
support on the THINKPAD and IBMSYS forums.


ΓòÉΓòÉΓòÉ 6.2.2. 2.2.2 The IBM PSP OS/2 BBS ΓòÉΓòÉΓòÉ

2.2.2 The IBM PSP OS/2 BBS

This BBS is operated by the Personal Software Products (PSP) Division of IBM.
Fee access to this BBS provides you with forums you can use to report bugs and
problems to OS/2 developers. Chat areas allow you to chat with or obtain help
from other users of OS/2. The OS/2 BBS provides patches and Service Packs (or
the newer FixPaks) when they become available for downloading, as well as other
OS/2 programs and Employee Written Software. Call 800-992-4447 for more
information.


ΓòÉΓòÉΓòÉ 6.2.3. 2.2.3 The IBM PC Company BBS ΓòÉΓòÉΓòÉ

2.2.3 The IBM PC Company BBS

The IBM PC Company BBS provides a number of chat areas where you can obtain
help and advice. Many IBM'ers and OS/2 power users are "regulars" there and are
available to answer questions and provide guidance. This BBS is also an
official source for Service Packs and OS/2 device drivers. Many shareware and
freeware programs are available from this BBS as well. The IBM PC Company
provides this BBS at no charge. You can contact the IBM PCC BBS at
919-517-0001. Set your modem to 8-N-1 at 2400 to 14,400 baud.


ΓòÉΓòÉΓòÉ 6.2.4. 2.2.4 Getting telephone support from IBM PSP ΓòÉΓòÉΓòÉ

2.2.4 Getting telephone support from IBM PSP

IBM  PSP provides support to any end user for sixty days free of charge. Your
sixty days of free support begin with your first call. If you are an
organization with multiple copies of OS/2, your sixty days begin with the first
call from anyone in your organization. After your sixty days of free support
have expired, you can obtain support from PSP on a fee basis. Service can be
purchased on a yearly basis or on a per incident basis and charges are based on
the size of your organization. You can contact PSP at 800-992-4777. Have the
registration number of your copy of OS/2 in front of you before you call. The
number is located in the Customer Service and Support pamphlet that came in the
box with OS/2 Warp.

Note:  PSP supports end users who purchase OS/2 "off the shelf" and install it
on their systems. If your system came from IBM preloaded with OS/2, you should
call the PC Company help center (see below) for support.


ΓòÉΓòÉΓòÉ 6.2.5. 2.2.5 Getting telephone support from the IBM PC Company ΓòÉΓòÉΓòÉ

2.2.5 Getting telephone support from the IBM PC Company

If you have an IBM PC Company system that has been preloaded or bundled with
OS/2, you should call the IBM PC Company for support. Operating system support
is free for the first 60 days after the first call during the warranty. Support
is available for a fee basis for systems that are out of warranty, or for which
the 60 day startup period has expired. Users can reach the IBM PC Company Help
Center (PSHC) at 1-800-772-2227. You should be in front of your machine, and
have its serial number and machine type available when calling. IBM authorized
dealers can also call the IBM PC Company for unlimited support of OS/2, even on
non-IBM systems (This is subject to certain restrictions, discussed in Section
5.5) Authorized dealers have been provided a telephone number and access code
entitling them to support from the IBM PC Company.


ΓòÉΓòÉΓòÉ 6.2.6. 2.2.6 Non IBM support avenues ΓòÉΓòÉΓòÉ

2.2.6 Non IBM support avenues

You have many other possible resources available to you for solving problems
besides IBM. A number of books are available at your local book store that are
designed for a wide variety of audiences (see Appendix G). If you are new to
OS/2, and feel intimidated by the complexity of the operating system, there are
a variety of beginner books available.

Some of the best places to obtain unofficial help for OS/2 are bulletin boards
and other electronic information services. Many electronic information services
provide discussion areas for OS/2 users. Among these are America On-Line,
Delphi, and Compuserve. The internet news groups (in particular, the
COMP.OS.OS2.* newsgroups) are perhaps some the best places to look. These
groups are subscribed to by OS/2 users around the world, and are an excellent
source of "tricks" for solving OS/2 problems.

You may also be able to find help at a local OS/2 User's Group in your area.
There are OS/2 user groups in many cities and towns across the U.S. Many P.C.
user's groups may also have an OS/2 SIG (Special interest Group). The members
of these groups are often OS/2 advocates, and are a good source of help. You
can post a message on a local BBS or internet newsgroup to find the location of
an OS/2 user's group near you.

Finally, the best source of information may be friends of yours that use OS/2.
Some of them may have experienced the same problems as you, and may be able to
help you find the answer quicker than other sources.


ΓòÉΓòÉΓòÉ 7. Section 3. OS/2 Problem Determination and Recovery Features ΓòÉΓòÉΓòÉ

SECTION 3. OS/2 PROBLEM DETERMINATION AND RECOVERY FEATURES

OS/2 provides many error recovery features with the operating system itself.
Some of these tools are relatively straightforward, while others are not and
must be used with caution. Information for most of these features is provided
in the OS/2 printed and on-line documentation.


ΓòÉΓòÉΓòÉ 7.1. 3.1 Using CHKDSK to repair your file system ΓòÉΓòÉΓòÉ

3.1 Using CHKDSK to repair your file system

CHKDSK is perhaps one of the most useful problem recovery tools in OS/2. CHKDSK
is used to find and correct file system problems (lost data, file corruption,
etc.).  The syntax of CHKDSK is as follows:

CHKDSK X: [/f[:1|:2|:3]]

X: is the drive letter to be checked. CHKDSK with no parameters will display
statistical information for the current drive. If errors are found, an
appropriate message will displayed, but the errors will not be corrected.

There are 4 levels of error detection and recovery for HPFS volumes:


 /F:0    ;Specifies that CHKDSK is to analyze the file system, display
         information about its  state, but not perform any repairs. This is the
         same as omitting the /F parameter altogether.

 /F:1    ;Specifies that CHKDSK is to resolve inconsistent file system
         structures.

 /F:2    ;Specifies that CHKDSK is to resolve inconsistent file system
         structures and also scan disk space that is in use but not referred to
         by the file system. If recognizable file or directory structures are
         found, CHKDSK recovers them.  /F:2 is used for HPFS volumes if only /F
         by itself is entered.

 /F:3    ;Includes all level 2 recovery and also specifies CHKDSK is to scan
         the entire disk partition for recognizable file system structures
         regardless of whether or not the disk space is marked as in use.

Note:  If you did not use the /L parameter when formatting the drive (see
Section 3.2), /F:3 may attempt to recover files that existed before the drive
was formatted. Since Warp does not use the /L parameter if you format during
installation, you should probably refrain from using /F:3 on your Warp boot
partition unless absolutely necessary.

The /F by itself is the only valid /F parameter for FAT volumes.  There are
additional parameters available for CHKDSK; see the OS/2 on-line command
reference for more information. In the following example,  CHKDSK is being used
to do the most rigorous testing possible on an HPFS drive:

CHKDSK C: /F:3

Note:  CHKDSK resolves logical file system problems only. It will not repair or
mark sectors on the hard disk that are physically bad (bad sectors usually
cause "sector not found" or "CRC error" messages). If your hard drive has bad
sectors, you should either format the hard drive by booting OS/2 from floppies
and using the long format command (see Section 3.2),  or purchase a third party
OS/2 utility program that can find and mark bad sectors. Do NOT low level
format the drive, as this may blindly reformat bad sectors as good. The sectors
may appear to work for awhile, but will eventually fail again.

If OS/2 crashes or is improperly stopped for any reason, you should boot OS/2
from floppy diskettes (either the utility diskettes or the installation
diskettes, see Section 1.5) and run CHKDSK against the OS/2 boot partition as a
first step for problem recovery.  Keep in mind the following Considerations
when running CHKDSK:

o   Be sure to run CHKDSK from the A: drive, and do not change to the OS/2 boot
    drive for any reason until you have finished with CHKDSK. If you access the
    OS/2 boot drive, OS/2 will lock the drive and prevent CHKDSK from
    correcting any errors it finds.

o   If CHKDSK finds lost data on the hard drive, it will ask if you wish to
    convert this data to files. If you choose to do this, CHKDSK will save the
    lost data it finds in the root directory of the drive. The files will be
    named FILE0001.CHK, and so forth. Unless the lost data originally belonged
    to a file in ASCII text format, it is unlikely you will be able to salvage
    the contents of these files. Because of this, you should probably not
    bother converting the lost data to files (Most often the data belongs to
    temporary files which were left open when the system went down).

o   Some errors may take more than one pass to correct. If CHKDSK finds errors
    on the hard drive, run it repeatedly until it runs twice with no errors.

o   CHKDSK cannot fix cross linked files (this should only be a  problem on FAT
    drives). It will, however, report which files are cross linked. Cross
    linked files occur when two files claim the same segment of data on the
    hard drive. You can try copying the cross linked files to another drive,
    erasing the originals, and then copying the files back to their original
    locations. This is not guaranteed to work, however, and in some cases it
    may be necessary to reformat the hard drive to recover.


ΓòÉΓòÉΓòÉ 7.2. 3.2 The FORMAT command ΓòÉΓòÉΓòÉ

3.2 The FORMAT command

There a rare circumstances where it may be necessary to reformat the hard disk
and reinstall OS/2. The circumstances include but are not limited to the
following:

o   The EA DATA. SF (extended attributes) file on a FAT volume has been damaged
    (perhaps by a DOS Disk utility) or was erased accidentally.

o   Numerous cross linked files on a FAT volume.

o   Bad sectors have been found on the hard drive.

o   You are installing or upgrading OS/2 over a beta version, or another
    unsupported version.

o   The filesystem has become irreparably damaged in some way that CHKDSK is
    unable to recover from (Perhaps due to a virus).

o   The system appears to be unstable, file corruption has been found by
    CHKDSK, and all other software and hardware recovery measures have been
    exhausted.

OS/2 is a very complex operating system, and over time, small problems may crop
up in the system that are completely unnoticeable to the user. The problems are
usually in OS/2's desktop and extended attributes, and may be caused user
error, defective installation software, power failures, and a host of other
"everyday" occurrences. This is especially likely to happen in an office or
classroom environment where the system is continually being used and modified
by several different people. Over time, these problems accumulate, and may lead
to occasional lockups, strange error messages and other problems that are very
hard to diagnose. (Note that this is a problem of all computer systems and
operating systems in general, and is no way peculiar to OS/2). There are
various third party utilities that will find inconsistencies in OS/2's
configuration files, but these utilities must be used with extreme caution.
Because of this, it may be wise to configure your system to suit your needs,
than immediately back up the entire OS/2 boot partition. Once a year, reformat
your disk and restore the backed up configuration. This will "freshen" your
system, and clean up any glitches that have worked their way into your system
since you last backed up. In some cases you may even notice a performance
increase. (OS/2's Desktop files have a tendency not to delete information once
it is no longer needed, and tend to become bloated with age).

If you must format your hard drive partition, you can normally do so as part of
the part of the installation. There are cases, however, when you may wish to do
so manually. OS/2 by default will format hard disks using the "fast format"
method. This method merely creates a clean directory record and does not check
for bad sectors on the hard drive. In addition, if you format an HPFS disk
using fast format, and later run CHKDSK with the /F:3 parameter against the
drive, you may end up " recovering" files that existed before the hard drive
was formatted. If you suspect your hard drive may contain bad sectors, or you
want to wipe all traces of the old files from your hard drive, you must use the
"long" formatting procedure. The "long" format performs media testing and will
mark bad sectors.

The syntax of the FORMAT command is as follows:

FORMAT X: [/L|/Q] [/FS:HPFS|FAT]

X: is the drive to be formatted. Use to /L force a "long" format, or /Q to
force a "fast" format. Hard disks are fast formatted by default, and floppy
disks are long formatted by default. The /FS: parameter allows you to specify
the file system type. Use FAT to create a FAT volume, and HPFS for HPFS
volumes. If this parameter is omitted, the drive will by default be formatted
with FAT. Note also that floppy disks are always formatted with FAT.  The
following example shows the correct use of the format command to format the D:
drive using HPFS and "long" formatting:

FORMAT D: /L /FS:HPFS


ΓòÉΓòÉΓòÉ 7.3. 3.3 Using SYSINSTX to recreate the boot record ΓòÉΓòÉΓòÉ

3.3 Using SYSINSTX to recreate the boot record

If OS/2 freezes up or displays error messages (usually OS/2 !! SYS01475 and
OS/2 !! SYS02027) before it reaches the colorful logo screen, the problem is
usually either in the initial boot files or in the OS/2 kernel itself. You can
use the SYSINSTX command to rewrite the OS/2 boot record and loader file should
they become corrupted. SYSINSTX is located on the first OS/2 Installation
Diskette,  and on the third utility diskette. To restore the OS/2 boot record
and loader, boot OS/2 from floppy disks (either from the installation disks or
from the utility diskettes).  From a command prompt, insert the diskette
containing SYSINSTX.COM and type the following command:

SYSINSTX X:

X: is the OS/2 boot partition. Note that SYSINSTX does not write the OS/2
Kernel files. If SYSINSTX still does not allow you to boot past the logo, you
may have to format your hard drive and reinstall OS/2.

Note:  You should also check the start-up sequence setting in your system's
BIOS and insure that it is set to "conventional" (A:, then C:). Some systems
have a "smart" setting which can interfere with the boot process. You should
also disable boot sector virus protection, especially if you are using dual
boot.


ΓòÉΓòÉΓòÉ 7.4. 3.4 Using OS/2's on-line help facility ΓòÉΓòÉΓòÉ

3.4 Using OS/2's on-line help facility

OS/2's on-line help facility is indispensable when resolving problems. Suppose
you receive the message shown in figure 3-1 when a program crashes.

Figure 3-1: A typical message indicating a program has crashed.

If you click help in the dialogue box that appears, a detailed explanation of
the error is presented, along with the cause of the error and possible
corrective action.

You can also go to an OS/2 command line and type "help 3175." If you do, the
following information is displayed:

Figure 3-2: Help Message for SYS3175

[D:\]help 3175

SYS3175: A program in this session encountered a problem and
cannot continue.

EXPLANATION: An access violation exception occurred and was generated
when an attempt was made either to load or store data in an inaccessible
location or to execute an inaccessible instruction.  This exception
corresponds to both the Intel 80386 processor general protection fault
(#13), caused by an invalid access attempt, and the page fault (#14),
caused by an attempt to access an uncommitted page or a page with
incorrect attributes for the desired operation.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.

This text is identical to the description you would get if you pushed the help
button in the message dialogue itself. In many cases, the error message you
receive may not display in a graphical window with a help button, but you can
always type help xxxx (where xxxx is the error number) to get help for a
particular error. Although the information presented in the description above
may not seem particularly useful, it does tell you the problem is being caused
by software, and that your application vendor may be a good place to start for
problem resolution.


ΓòÉΓòÉΓòÉ 7.4.1. 3.4.1 Additional on-line information ΓòÉΓòÉΓòÉ

3.4.1 Additional on-line information

In addition to the on-line help for error messages, the entire OS/2 Command
Reference is available as an on-line book. If you are looking for help
performing a specific task, you may wish to try looking in the Master Help
Index. All of OS/2's on-line books and help facilities are available in the
Information folder on your OS/2 Desktop.


ΓòÉΓòÉΓòÉ 7.5. 3.5 The Recovery Choices menu ΓòÉΓòÉΓòÉ

3.5 The Recovery Choices menu

The recovery choices menu is a new feature of Warp, and is extremely helpful in
recovering from situations that previously would have required having a set of
bootable OS/2 floppy diskettes on hand. The recovery choices menu is activated
by briefly holding down and releasing Alt-F1 during startup, when you see the "
OS/2" message. The following menu will appear:

Figure 3-3: Recovery Choices Menu

                             RECOVERY CHOICES
   Select the system configuration file to be used, or enter the option
   corresponding to the archive desired.

   ESC - Continue the boot process using \CONFIG.SYS without changes
   C   - Go to command line, (no files replaced, use original CONFIG.SYS)
   V   - Reset primary video display to VGA and reboot
   M   - Restart the system from the Maintenance Desktop (Selective Install)

   Choosing an archive from the list below replaces your current CONFIG.SYS,
   Desktop directory, and INI files with older versions.  These older versions
   might be different from your current files.  Your current files are saved in
   \OS2\ARCHIVES\CURRENT.

   1) Archive created 10-25-94  9:18:14AM
   2) Archive created 10-24-94  1:38:02PM
   3) Archive created 10-21-94  10:09:36AM
   X) Original archive from INSTALL created 10-18-94  6:40:02PM


ΓòÉΓòÉΓòÉ 7.5.1. 3.5.1 Decisions, decisions ΓòÉΓòÉΓòÉ

3.5.1 Decisions, decisions

The following choices are presented in the recovery choices menu:

o   [ESC] If the escape key is pressed, the system will continue to boot
    normally. No changes will be made to the system configuration.

o   [C] If the C key is pressed, OS/2 will bypass loading the desktop and boot
    straight to a command line. This is especially useful in situations where
    it is necessary to modify the CONFIG.SYS as OS/2 Warp now includes TEDIT, a
    text-based editor. Note that if you use C you cannot run more than one text
    based application, or start a DOS session. Do not use the OS/2 System
    Editor (E.EXE) from here. Doing so will start Presentation Manager, and
    probably cause a system crash. To exit the command line, issue the EXIT
    command and the system will restart normally.

    You will still not be able to run CHKDSK on the boot drive while booting to
    the command line because the drive is in use. You must still boot with
    floppy disks to run CHKDSK on the boot drive.

o   [V] If you choose V from the recovery choices menu, the system will
    preserve your current configuration, with the exception that it reinstalls
    VGA as the primary display device. This is extremely useful for recovering
    from  incorrect or corrupt display driver installations. Selecting V
    actually runs the SETVGA utility that was present in earlier versions of
    OS/2. It is usually a good idea to use V to return your system to VGA
    before installing new or updated video drivers.

    Note:  You should no longer run DSPINSTL directly to install display
    drivers that ship with OS/2. DSPINSTL will not copy all the files needed.
    Attempting to run DSPINSTL directly will generate an error message on
    versions of Warp that do not include WIN-OS/2. Use Selective Install (see
    Section 3.11) to install video drivers that are provided with Warp

    Note:  SETVGA may not work if certain Super VGA display drivers are used.
    This is primarily a problem when trying to use 2.x drivers under Warp.
    Warp's video subsystem has changed somewhat, and it is best to use
    Warp-specific drivers whenever possible.

o   [M] Selecting M from the recovery choices menu will activate the
    maintenance desktop. The maintenance desktop is a essentially a "lite"
    version of the desktop, with only a system and information folder. From
    here you can essentially repeat in its entirety the graphical portion of
    OS/2's installation (disk 7 onwards) if necessary. Selecting M calls
    SETVGA, so the maintenance desktop always comes up using VGA drivers.

    DO NOT use the maintenance desktop to selectively reinstall components of
    OS/2. If you clear any of the check boxes on second panel of Selective
    Install, the objects for these features will be removed when you return to
    your normal desktop. Only use the Maintenance desktop if you intend to
    completely reinstall OS/2 from disk 7 onwards.

o   [X] OS/2 always keeps an archive of the original desktop created during
    installation. If you choose X from the archives menu, your original desktop
    and CONFIG.SYS are restored. This is similar to the old "Alt-F1" technique
    under OS/2 2.x. The difference is that the original Alt-F1 simply restored
    the original CONFIG.SYS, OS2.INI, and OS2SYS.INI files. Using X restores,
    in addition to these files, a copy of your original OS/2 DESKTOP directory
    tree, AUTOEXEC.BAT, STARTUP.CMD, and OS2INIT.CMD (OS/2 version 1.0 used
    OS2INIT.CMD instead of STARTUP.CMD).

o   [1]-[3] If you have archiving enabled, you will be able to select any of 3
    most recent archives. Restoring an archive will replace your CONFIG.SYS,
    OS2.INI, OS2SYS.INI, AUTOEXEC.BAT, STARTUP.CMD, OS2INIT.CMD, the OS/2
    DESKTOP directory, and any other key files you specified. Your display
    driver configuration will also be restored. See Section 1.3 for details on
    creating an archive.


ΓòÉΓòÉΓòÉ 7.5.2. 3.5.2 Modifying the recovery choices menu ΓòÉΓòÉΓòÉ

3.5.2 Modifying the recovery choices menu

The recovery choices menu is essentially a collection of text screens, command
files, and CONFIG.SYS files. Although you cannot disable the menu, you can
modify how it behaves. The necessary files are in the \OS2\BOOT directory.
ALTF1.CMD controls the behavior of the menu itself. ALTF1TOP.SCR is a text file
that contains the top half of the recovery choices menu (everything above the
archive selections). ALTF1MID.SCR is usually empty by default, and overlaps
with ALTF1BOT.SCR, which contains the archive selections. ALTF1BOT.SCR is
modified by the system every time a new archive is created. All of the .SCR
files are ASCII text and are modifiable by the user once the read only
attribute is removed. Note that editing these files only changes the appearance
of the menu. If you wish to change how the menu behaves (i.e. key assignments),
you must modify the ALTF1.CMD file.


ΓòÉΓòÉΓòÉ 7.5.3. 3.5.3 A MultiConfig feature for OS/2 ΓòÉΓòÉΓòÉ

3.5.3 A MultiConfig feature for OS/2

In same cases (e.g. a ThinkPad in a docking station) it may be desirable to
have several CONFIG.SYS files, and switch between them at boot time. One would
load the LAN drivers, another would not, etc. You can use the recovery choices
menu to implement this. If you place a CONFIG.? (where ? can be any character
valid for use in a file name) file in the OS2\BOOT directory, OS/2 will use
this file as the active CONFIG.SYS when the ? key is pressed in the recovery
choices menu. In fact, OS/2 will also check for the presence of ALTF?.CMD, and
if it is found, OS/2 will execute it. ALTF?.CMD can be any valid batch file. It
cannot, however be a REXX program, as REXX support has not yet been loaded when
the recovery choices menu is processed.

Note:  Do NOT use the following characters for your own configuration files:
C,M,V,X,1,2, or 3. These characters already have defined actions in the
recovery choices menu. Also, if you install an application that modifies the
CONFIG.SYS, you will have to manually make the appropriate modifications to all
of your CONFIG files.

If you wish for your different configurations to appear in the recovery choices
menu, you must edit one of the .SCR files and manually add the choices. If you
need a more extensive version of MultiConfig, such as the ability to switch
among desktops, display drivers, etc., you may wish to use the archiving
feature of OS/2 instead of custom configuration files. See Section 1.3 for
details.


ΓòÉΓòÉΓòÉ 7.6. 3.6 TEDIT: lean, mean, and to the point ΓòÉΓòÉΓòÉ

3.6 TEDIT: lean, mean, and to the point

There are times when OS/2 may not boot up to the desktop because of a problem
with the CONFIG.SYS file. If this happens, you can use the recovery choices
menu (Section 3.5.1) to boot OS/2 to a command prompt. You can then use the
OS/2 text mode editor TEDIT to edit your CONFIG.SYS.

TEDIT does not use Presentation Manager at all, and there is no mouse support.
TEDIT's interface is rather unintuitive (see Figure 3-4), but it gets the job
done. If you are familiar with the E editor provided with PC-DOS 6.x, you will
find TEDIT's interface to be very similar.

Note:  TEDIT starts up in command mode. To put TEDIT in edit mode (so that you
can alter the CONFIG.SYS), you must hit the escape key.

Figure 3-4: TEDIT in action

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé=====Top of File=====                                                             Γöé
ΓöéIFS=D:\OS2\HPFS.IFS /CACHE:512 /CRECL:4 /AUTOCHECK:DEFC                           Γöé
ΓöéREM ifs=D:\IBM386FS\HPFS386.IFS /A:* /AUTOCHECK:F                                 Γöé
ΓöéREM run=D:\IBM386FS\CACHE386.EXE                                                  Γöé
ΓöéPROTSHELL=D:\OS2\PMSHELL.EXE                                                      Γöé
ΓöéSET USER_INI=D:\OS2\OS2.INI                                                       Γöé
ΓöéSET SYSTEM_INI=D:\OS2\OS2SYS.INI                                                  Γöé
ΓöéSET OS2_SHELL=D:\OS2\CMD.EXE                                                      Γöé
ΓöéSET AUTOSTART=CONNECTIONS,PROGRAMS,TASKLIST,FOLDERS,LAUNCHPAD                     Γöé
ΓöéSET RESTARTOBJECTS=STARTUPFOLDERSONLY                                             Γöé
ΓöéSET RUNWORKPLACE=D:\OS2\PMSHELL.EXE                                               Γöé
ΓöéSET COMSPEC=D:\OS2\CMD.EXE                                                        Γöé
ΓöéLIBPATH=D:\watchcat;d:\SM2\DLL;.,D:\IBM386FS;D:\MUGLIB\DLL;D:\MPTN\DLL;D:\ibmcom  Γöé
ΓöéSET PATH=d:\SM2;D:\IBM386FS;D:\MPTN\BIN;D:\ibmcom;D:\IBMLAN\NETPROG;D:\MUGLIB;E:  Γöé
ΓöéSET DPATH=d:\SM2;D:\ibmcom;D:\IBMLAN\NETPROG;D:\sqllib;D:\IBMLAN;D:\MUGLIB;E:\Wo  Γöé
ΓöéSET LIB=D:\SQLLIB;                                                                Γöé
ΓöéSET INCLUDE=D:\SQLLIB;                                                            Γöé
ΓöéDEVICE=D:\IBMCOM\PROTOCOL\LANPDD.OS2                                              Γöé
ΓöéDEVICE=D:\IBMCOM\PROTOCOL\LANVDD.OS2                                              Γöé
ΓöéDEVICE=D:\ibmcom\LANMSGDD.OS2 /I:D:\ibmcom                                        Γöé
ΓöéDEVICE=D:\ibmcom\PROTMAN.OS2 /I:D:\ibmcom                                         Γöé
ΓöéRUN=D:\ibmcom\LANMSGEX.EXE                                                        Γöé
Γöéconfig.sys                                                      1 1      Rep      Γöé
ΓöéF1=Help F2=Save F3=Quit F4=File F5=Cmd          F7=Name F8=Edit F9=Undo F10=Next  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.7. 3.7 Using MAKEINI to rebuild your OS/2 Desktop ΓòÉΓòÉΓòÉ

3.7 Using MAKEINI to rebuild your OS/2 Desktop

OS/2 stores most of the configuration information for the desktop in two files:
OS2.INI and OS2SYS.INI. OS2.INI is often referred to as the "user" .INI because
most of the information it contains is user configurable (e.g. Any desktop
objects you create are stored in this file, as are color and font changes).
Various OS/2 applications may also store some of their configuration
information in these files. The OS2SYS.INI file contains parallel and COM port
configuration information, information about window positions and sizes, scheme
palettes, fonts, and other system information, and is often referred to as the
"system" .INI file. Together these files, along with the DESKTOP subdirectory
tree (which contains directories that represent the folders on your desktop)
and extended attributes, comprise the OS/2 desktop.

If your desktop becomes corrupt, and you do not have a set of archives to
recover, you can manually recreate your desktop files by using MAKEINI. There
are two ways to do this. The first method simply reinitializes the default OS/2
Desktop objects and settings in your desktop files, and leaves any other
objects or customizations you have made intact. This is often referred to as a
"nondestructive MAKEINI." You should try this procedure first. If a
nondestructive MAKEINI fails to correct the problem, a more drastic method
known as a "destructive MAKEINI" may be required. The destructive MAKEINI
procedure creates only a default OS/2 Desktop; any additional objects or
customizations you have made are lost.

Note:  Any time you use MAKEINI (nondestructive or destructive), your video may
be reset back to VGA resolution. Your SVGA drivers are still present, but the
resolution settings have been deleted from the .INI files. To get your
resolution and monitor settings back, you must use the Selective Install object
in the System Setup folder to reinstall your video drivers. Some display
drivers may also cause the desktop to fail to come up after a MAKEINI. If this
happens, boot to the recovery choices menu (see Section 3.5.1) and select "V"
to restore VGA manually. Then use Selective Install to reinstall your video
drivers. If you have a disk containing updated video drivers, follow the
procedures in the README file on this disk instead of using Selective Install.

Note:  On Warp "Red Box" systems (see Appendix B. This includes IBM systems
preloaded w/ Warp), performing any MAKEINI operation will cause the "X" choice
in the recovery choices menu (see Section 3.5.1) to be updated with the new
desktop created by MAKEINI. Thus, if you perform a nondestructive MAKEINI
procedure and it fails to repair the desktop, your "X" archive will now be
corrupted as well. You may also lose any other archives you have created.


ΓòÉΓòÉΓòÉ 7.7.1. 3.7.1 Performing a nondestructive MAKEINI ΓòÉΓòÉΓòÉ

3.7.1 Performing a nondestructive MAKEINI

To perform a nondestructive MAKEINI, perform the following steps:

Boot OS/2 from floppy diskettes and run CHKDSK to correct any file system
errors (See Section 3.1).

Change to the \OS2 directory. Then take the system, hidden, and read only
attributes off of the WP ROOT .SF file with  the following command:

ATTRIB -s -h -r c:\wp?root.?sf

(If OS/2 is not on drive C:, replace C: with the OS/2 partition). OS/2 uses
this file to store windows size and position information for the WorkPlace
shell. If this file becomes corrupted, it can cause strange behavior while
using the WorkPlace shell. Next, erase the file by typing the following
command:

ERASE c:\wp?root.?sf

Then execute the following commands (You should still be in the \OS2
directory):

COPY OS2*.INI OS2*.BAK
MAKEINI OS2.INI INI.RC
MAKEINI OS2SYS.INI INISYS.RC

If the process was successful, you should see the message "MAKEINI.EXE -
Successful completion." At this point you should remove the floppy disk and
reboot. The procedure should reset you to VGA, and leave your desktop intact.


ΓòÉΓòÉΓòÉ 7.7.2. 3.7.2 Destructive MAKEINI: a last resort ΓòÉΓòÉΓòÉ

3.7.2 Destructive MAKEINI: a last resort

The procedure for a destructive MAKEINI is almost identical to the
nondestructive variety. Because you will lose any added objects and desktop
customizations, you should try a nondestructive MAKEINI first. If you must
perform a destructive MAKEINI, use the following steps:

Boot OS/2 from floppy diskettes and run CHKDSK to correct any file system
errors (See Section 3.1).

Change to the \OS2 directory. Then take the system, hidden, and read only
attributes off of the WP ROOT. SF file with  the following command:

ATTRIB -s -h -r c:\wp?root.?sf

(If OS/2 is not on drive C:, replace C: with the OS/2 partition). OS/2 uses
this file to store windows size and position information for the WorkPlace
shell. If this file becomes corrupted, it can cause strange behavior while
using the WorkPlace shell. Next, erase the file by typing the following
command:

ERASE c:\wp?root.?sf

(Again, if OS/2 is not on drive C:, replace C: with the OS/2 partition). Then
run the following five commands to recreate the OS/2 Desktop (You should still
be in the \OS2 directory):

COPY OS2*.INI OS2*.BAK
ERASE OS2.INI
ERASE OS2SYS.INI
MAKEINI OS2.INI INI.RC
MAKEINI OS2SYS.INI INISYS.RC

If the MAKEINI process was successful, you should see the message "MAKEINI:
successful completion." At this point you should remove the floppy disk and
reboot. The procedure should reset you to VGA. You will have a default OS/2
Desktop at this point, and may have to reinstall any additional features or
software that was present on your system before the MAKEINI.

Note:  Each time you perform a destructive MAKEINI, an additional DESKTOP
directory tree containing only the default OS/2 folders is created. Any
previous DESKTOP directories are left intact but ignored. Do not delete any of
these additional desktop directories, as desktop corruption may occur if this
is done.


ΓòÉΓòÉΓòÉ 7.8. 3.8 Using Alt-F2 to find problematic drivers ΓòÉΓòÉΓòÉ

3.8 Using Alt-F2 to find problematic drivers

If you are experiencing system hangs on startup or other device driver related
difficulties, you can use ALT-F2 to determine which driver is causing the
problem. When you start OS/2 Warp, you will briefly see, before the logo
appears, an "## OS/2" message in the upper left hand corner of the screen.
Briefly hold down and release the [Alt] and [F2] keys at this time, and Warp
will display the name of each device driver as it is loaded. You can use this
feature to determine which device driver is causing the problem. Often this
will be the second to last device driver displayed on the screen.


ΓòÉΓòÉΓòÉ 7.9. 3.9 Using PSTAT to view running processes ΓòÉΓòÉΓòÉ

3.9 Using PSTAT to view running processes

OS/2 is a multithreaded operating system, which means that one program (known
as a process) can execute several tasks (or threads) at once. A perfect example
of this is the WorkPlace shell itself. You can format a floppy disk while at
the same time copying files between two partitions an your hard drive. In this
case, one thread is handling the disk format, while the other is copying the
file (actually, there are even more threads going, such as the one that is
interpreting your mouse clicks, etc.).

The PSTAT command can be used to view details about currently running processes
and threads. When attempting to solve a problem, it is helpful to know what is
running at the time. PSTAT will show a variety of details about processes
running on your system. See the OS/2 on-line command reference for details on
how to use PSTAT. The following output was obtained using PSTAT /C, and shows
several networking software processes (the .EXE files), and the various threads
associated with each process (the numbers below each process).

Figure 3-5: Sample PSTAT output

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéProcess and Thread Information                                                  Γöé
Γöé          Parent                                                                Γöé
ΓöéProcess   Process   Session   Process   Thread                                  Γöé
Γöé  ID        ID        ID       Name       ID    Priority   Block ID   State     Γöé
Γöé 005D      0000       1A      D:\IBMLAN\SERVICES\MSRV.EXE                       Γöé
Γöé                                          01      0200     040054B2   Block     Γöé
Γöé                                          02      0200     FFFE6A88   Block     Γöé
Γöé 005B      0000       1A      D:\IBMLAN\SERVICES\WKSTAHLP.EXE                   Γöé
Γöé                                          01      031E     0C90B366   Block     Γöé
Γöé                                          02      0200     0C8005FE   Block     Γöé
Γöé                                          03      031E     0C802108   Block     Γöé
Γöé                                          04      031E     0C80061C   Block     Γöé
Γöé 005A      0000       1A      D:\IBMLAN\SERVICES\WKSTA.EXE                      Γöé
Γöé                                          01      0300     FFFE6AC1   Block     Γöé
Γöé                                          02      021F     FFFD003C   Block     Γöé
Γöé                                          03      0200     FFFE69CA   Ready     Γöé
Γöé                                          04      021F     FFFD0045   Block     Γöé
Γöé 002A      0000       17      D:\CMLIB\CMKFMSMI.EXE                             Γöé
Γöé                                          01      0300     FFFE18EE   Block     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.10. 3.10 The Resource Manager ΓòÉΓòÉΓòÉ

3.10 The Resource Manager

One the primary architectural enhancements of OS/2 Warp is the resource
manager. System resources include such items as IRQ's, DMA channels, and I/O
port addresses. The resource manager is a kernel-level device driver
(RESOURCE.SYS) whose primary purpose is to resolve resource contentions among
device drivers. A device driver must first request access to system resource.
The resource manager then determines whether that resource is already in use,
and relocates the driver as necessary. If the driver is not resource manager
aware, or is hardcoded to use a specific set of resources, and these resources
have already been assigned, the driver will fail to load, and may or may not
generate an error message. The resource manager is used extensively during
installation, when autoscanning is used to set up port addresses, IRQ levels,
and other system configuration parameters. Even after installation, the
resource manager may continue to autoscan, dynamically locating drivers as
necessary. To decrease boot time, you may be able to use switches on the end of
device driver statements to explicitly assign resources to them, thus avoiding
the autoscan. Note that if you choose to do this, it is your responsibility to
avoid resource conflicts.

Note:  In order for resource manager to dynamically allocate a driver's system
resources, the driver must be written to be resource manager (RM) aware.
Microchannel drivers, display drivers, and most third party device drivers,
including all 2.x drivers, are not RM aware. Resource manager will have no
effect on such drivers, though it can detect when they load. You can use
RESERVE.SYS to keep resource manager from touching the resources needed by
these drivers.


ΓòÉΓòÉΓòÉ 7.10.1. 3.10.1 Using RMVIEW to find resource conflicts ΓòÉΓòÉΓòÉ

3.10.1 Using RMVIEW to find resource conflicts

If you have problems loading a specific device driver, you can use RMVIEW to
determine the cause of the conflict. RMVIEW is a command line utility, and its
syntax is as follows:

RMVIEW [switch]


      /P       ;Display Physical view (default) shows all resources claimed
               by physical components

      /P1      ;Physical view with planar chipset

      /D       ;Display Device Driver view shows all registered drivers and
               resources claimed by them

      /D1      ;Driver view with planar chipset

      /L       ;Display Logical view of system resources

         /R    ;Display in raw data format. Use with P, L, and D switches

      /IRQ     ;Display claimed Interrupt levels (IRQ)

      /IO      ;Display claimed IO ports above 100 Hex

      /IOA     ;Display all claimed IO ports

      /DMA     ;Display claimed DMA channels

      /MEM     ;Display claimed Memory regions

         /SO   ;Sort IO, IOA, IRQ, DMA, MEM by owner

      /HW      ;Display Hardware Tree shows a hardware diagram of the
               system

      /?       ;Help

 You can use the /P and /D to verify that device drivers are using the correct
resources for the device they are supporting. The following is an example
section of output using the /P switch (in this case, the ThinkPad 755 audio
chip). This shows the resources claimed by the chipset itself:

Adapter: Thinkpad/CS4231 Audio
Device Type: MMEDIA-AUDIO  Bus/Width: ISA 16 BIT
I/O = 0X4E30  Len =  16  Flg = EXCLUSIVE   Addr Lines = 16
IRQ Level = 10  PCI Pin = NONE  Flg = MULTIPLEXED
DMA Channel =  0  Flg =  EXCLUSIVE
DMA Channel =  1  Flg =  EXCLUSIVE
  Device: AUDIO_1 Busaudio AUDIO Device   FIXED  AUDIO

You can also use the /D switch, which gives you information about the device
driver.

Driver: CS4231.SYS  -  CS4231 Sound Driver
Vendor: Crystal Semiconductor  Version: 1.1  Date (MDY): 9/26/1994
Flag:   STATIC     Type-Subtype: AUDIO
  Adapter: Thinkpad/CS4231 Audio
  Device Type: MMEDIA-AUDIO  Bus/Width: ISA 16 BIT
  I/O = 0X4E30  Len =  16  Flg = EXCLUSIVE   Addr Lines = 16
  IRQ Level = 10  PCI Pin = NONE  Flg = MULTIPLEXED
  DMA Channel =  0  Flg =  EXCLUSIVE
  DMA Channel =  1  Flg =  EXCLUSIVE
  Device: AUDIO_1 Busaudio AUDIO Device   FIXED  AUDIO

The information presented by the /P and /D switches shows the resources that
OS/2 has allocated to the device. If the actual settings on the adapter differ
from what is presented here, you must change the parameters for the driver.


ΓòÉΓòÉΓòÉ 7.10.2. 3.10.2 Using RESERVE.SYS to reserve system resources ΓòÉΓòÉΓòÉ

3.10.2 Using RESERVE.SYS to reserve system resources

Many drivers are not RM aware. As a result, if resource manager allocates
resources for an RM aware driver and a non - RM aware driver later loads and
tries to use those same resources, a conflict will result, causing the non - RM
aware driver not to load.  You can use the RESERVE.SYS device driver to
allocate resources for non - RM aware device drivers. Once allocated by
RESERVE.SYS, the resources will NOT be used by RM aware drivers, leaving them
free for non - RM aware drivers. The following is the syntax for RESERVE.SYS:

BASEDEV=RESERVE.SYS ArgumentList

/IO:a,n  or /P:a,n      ;Reserve I/O ports. a=base address in HEX. b=number of ports in DECIMAL
   ex. /P:200,4 /DW:10  ;Reserve I/O port 200h, length 4, decode width 10
/MEM:a,l                ;Reserve memory. a=base address in HEX. l=number of bytes in DECIMAL
   ex. /MEM:CC00,16384  ;Reserve memory starting at CC00h, length 16Kb
/DMA:c                  ;Reserve DMA channel. c = channel in DECIMAL
   ex. /DMA:2 /EXC      ;Reserve DMA channel 2 for EXClusive access
/IRQ:n                  ;Reserve IRQ. n = IRQ level in DECIMAL
   ex. /IRQ:9 /SHA      ;Reserve IRQ 9 for SHAred access
/EXC                    ;Sets the EXClusive attribute for the specified resource
/MUL                    ;Sets the MULtiplexed attribute for the specified resource
/SHA                    ;Sets the SHAred attribute for the specified resource
/GY                     ;Sets the Grant Yield attribute for the specified resource
/DW:w                   ;Sets the decode width. valid only for I/O ports. w = 10 or 16

Resource attributes are mutually exclusive , so only one attribute may be
specified per resource. If no attributes are specified or decode width is set,
RESERVE.SYS defaults to EXCLUSIVE and decode width of 16. In the previous
example, we used RMVIEW to show the resources used by ThinkPad CS4231 audio
chip and it's driver. In reality, the CS4231 driver is RM aware, but suppose it
wasn't. We could use RESERVE.SYS  to specify  the resources used by this chip:

BASEDEV=RESERVE.SYS  /IRQ:10  /DMA:10 /MUL /P:4E30,16

This would prevent RM aware drivers from using these resources. Note that while
RESERVE.SYS will  prevent RM aware drivers from using these resources; it will
not prevent other non - RM aware drivers from using them. It is still your
responsibility to resolve resource conflicts between non - RM aware drivers.


ΓòÉΓòÉΓòÉ 7.11. 3.11 Using Selective Install to re-install system components ΓòÉΓòÉΓòÉ

3.11 Using Selective Install to re-install system components

Certain types of problems in OS/2 may require that various components of OS/2
(e.g. WIN-OS/2 support, multimedia, video, etc.) be reinstalled. This can be
accomplished by using the Selective Install object located in the System Setup
folder. You will need to have your original installation media available. To
re-install or add a device driver, launch Selective Install and click the
button that corresponds to the type of device support you wish to add or change
(See figure 3-6). Choose the correct device driver (this will usually be
automatically highlighted) from the list that appears.

If you are just re-installing a system component such as multimedia support or
WIN-OS/2 support, then bypass the initial screen shown in figure 3-6 by
clicking OK. You will be presented with a list of components. Choose only the
one you are trying to reinstall. If you need to modify the way the component is
installed (e.g. tell OS/2 where your Windows directory is located for WIN-OS/2
support), click the More... button.

Figure 3-6: Selective Install screen for adding a device driver


ΓòÉΓòÉΓòÉ 7.12. 3.12 "Surgically" Removing OS/2 Warp using OSDELETE ΓòÉΓòÉΓòÉ

3.12 "Surgically" Removing OS/2 Warp using OSDELETE

If it should become necessary for some reason to remove OS2 entirely from the
hard drive, you can use the OSDELETE program provided on Utility Diskette 3.
This program will remove all traces of OS2 (including the OS2 , SPOOL, DELETE,
NOWHERE, DESKTOP, MAINTENA, PSFONTS, IBMVESA, and MMOS2 directories, as well as
the hidden files in the root directory) except the EA DATA. SF file on FAT
drives.

There are rare circumstances where, due to file corruption, it may be necessary
to completely remove all traces of OS/2 from the system and reinstall. It is
usually best to simply reformat the drive during installation to accomplish
this, but there may be times where this is undesirable or impractical.  The
following procedure may be used instead, and will for most purposes suffice as
a "format" when it is necessary to format the drive and reinstall OS/2.

To remove OS/2 completely from the hard drive,  perform the following steps:

1.  Boot OS/2 from the utility diskettes and run the OSDELETE program on
    diskette 3.

2.  Manually remove anything OSDELETE missed (e.g. additional DESKTOP and
    NOWHERE directories, etc.)

3.  For FAT volumes, change to the \OS2 directory and type A:ATTRIB -s -h -r
    C:\EA?DATA.?SF and hit enter to remove the system, hidden, and read-only
    attributes from the extended attributes file.

4.  Type ERASE C:\EA?DATA.?SF and hit enter to remove the unneeded EA's from
    FAT drives.

5.  Change back to A:, then run CHKDSK C: /F on the hard drive to remove any
    pointers to extended attributes.


ΓòÉΓòÉΓòÉ 8. Section 4. OS/2 Warp Problems, Symptoms and Fixes ΓòÉΓòÉΓòÉ

SECTION 4. OS/2 WARP PROBLEMS, SYMPTOMS AND FIXES

Section Four describes various types of OS/2 error messages and problem
symptoms you may encounter, as well as possible solutions for these problems.
Although the information presented here is in "Symptom-Problem-Fix" format,
this does not eliminate the need for the good troubleshooting skills described
in Section 2. OS/2 is an evolving operating system, and its problems evolve
with it. As old problems are fixed new ones are introduced. This is true of any
operating system (or of any complex man-made invention, for that matter). There
are many potential problems that may not appear in this section, and there may
be additional solutions other than the ones listed for the problems that do
appear in this section. Use this section as a starting point, not as an
authoritative reference.


ΓòÉΓòÉΓòÉ 8.1. 4.1 SYS Errors ΓòÉΓòÉΓòÉ

4.1 SYS Errors

"SYS" error messages are generated by the operating system itself. You can
obtain help for these errors by typing HELP SYSxxxx (where xxxx is the error
number) at an OS/2 command prompt (See Section 3.4). In many cases when a SYS
error occurs, a dialog box appears (See Figure 3-1) that contains the error
message and one or more of the five options listed below. The first three
options are similar to the "A)bort, R)etry, F)ail?" choices you get under DOS.
The last two are unique to OS/2. Note that which options are presented depends
on the nature of the error. It is unlikely, for example, that you will see the
"display register information" choice if a needed file cannot be found on a
disk (SYS0002). If you select help from the dialog box of a SYS error, you will
receive the same help message you would get by typing HELP SYSxxxx at a command
line. Note that when the error dialog appears, the program has been suspended
by OS/2, and does not yet "know" an error occurred.

o   Return error code to the program. This option is equivalent to the "F)ail"
    option under DOS. It simply tells OS/2 to return the error code to the
    program that encountered it. The program then decides what, if anything, to
    do about it. In some cases, poorly written programs do nothing and ignore
    the error, which will usually cause problems very shortly thereafter. In
    other cases, the program will simply display its own (often nearly
    identical) version of the same error message and then terminate.

o   End program/command/operation. This option corresponds to the "A)bort"
    option under DOS, and simply terminates the program. This is usually the
    best option in most circumstances.

o   Retry command or operation. You may see this option when an attempt to
    access a disk fails. If the disk is a floppy disk, you can sometimes remove
    it, reinsert it, then select this option. You may also receive this option
    if the wrong diskette or CD is in the drive, or a needed file cannot be
    found.

o   Ignore the error and continue. This option should usually be avoided.
    Choosing this option tells OS/2 to allow the application program to
    continue without telling the application that the error has occurred. A
    poorly written application may crash if this occurs. One example of where
    ignoring the error might be useful is if a program attempts to generate
    sounds, but multimedia support is not properly installed. You may be able
    to ignore the error and continue to use the program without sound support.

o   Display register information. This option usually appears if a program
    encounters an error and is forced to terminate for some reason. Choosing
    this option will display a screen displaying the contents of the processor
    registers, and other information about the program that terminated. IBM
    technicians may use this information to determine why the program is
    crashing. If you anticipate calling technical support, you  may wish to
    copy this information.

Whenever you see a SYSxxxx type error message, it is being handled by OS/2's
internal exception handler, HARDERR.EXE. HARDERR.EXE intercepts the error and
presents the error message before the program knows an error has occurred. Some
OS/2 applications may have their own exception handler, and are capable of
dealing with certain types of errors without the intervention of the operating
system. If you see an OS/2 SYSxxxx error message generated by the operating
system, this is a pretty good indication that the program does not have its own
built in error handler.


ΓòÉΓòÉΓòÉ 8.2. 4.2 Trap Errors ΓòÉΓòÉΓòÉ

4.2 Trap Errors

Traps are generated by the microprocessor and are used to inform the operating
system that an error has occurred. When a trap occurs, the software flow of
control is transferred to a special segment of code that is designed to handle
the trap. Not all traps are "errors" in the strictest sense of the word. For
example, if a program asks for a page of memory that has been swapped to the
hard drive, a trap results and the software flow of control is transferred to a
portion of code that reads the memory page back into RAM from the hard drive.
This is in fact what OS/2 was designed to do; so from the user's perspective,
no error occurred. Other traps are errors, but are handled gracefully by OS/2.
The SYS3175 and 3176 messages you sometimes see in errant applications are, in
fact, the result of microprocessor traps.

When most people think of traps, however, visions of black screens filled with
register information come to mind. These traps are errors that OS/2 does not
know how to handle. The operating system terminates itself and displays the
register information before any damage is done. Although there are 17 possible
trap messages, only four of them occur often enough to be described here.


ΓòÉΓòÉΓòÉ 8.2.1. 4.2.1 Common Trap Errors ΓòÉΓòÉΓòÉ

4.2.1 Common Trap Errors

Trap 0002

1.  This trap is almost always caused by hardware, and usually by memory.
    Hardware diagnostics may not catch the error. If you have installed
    additional memory, try removing it. Remove and reinsert SIMM's and make
    sure they are seated properly. Make sure your memory is of the same speed
    (e.g. do not mix 70ns with 80ns SIMM's), type (e.g. do not mix 1X9 SIMM's
    with 1X3's), and brand. Try replacing or swapping memory SIMM's until the
    problem disappears.

2.  You may also have defective external cache memory. Try disabling and/or
    removing any external cache memory.

3.  If your system board allows you to disable its high performance features
    (e.g. "Turbo" mode, High Performance I/O mode, memory interleaving, shadow
    RAM, etc.), you should do so, especially if the trap is occurring during
    the installation of OS/2.

4.  You may need to update your system's BIOS.

5.  You may have a non-memory related hardware conflict. Make sure there are no
    interrupt, DMA, I/O port address, or upper memory conflicts between any
    hardware devices in your system. The easiest way to isolate these problems
    is to remove any additional hardware devices (e.g. LAN adapters, Audio
    adapters, Tape Backup units that attach to the floppy drive cable, etc.),
    then add them back one by one until the error reappears. Table 4-1 below
    shows the standard interrupt assignments for a typical PC.

Table 4 - 1: Standard Interrupt Assignments

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéInterrupt (IRQ)ΓöéUse                           ΓöéNotes                          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé0              ΓöéSystem Timer                  Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé1              ΓöéKeyboard                      Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2              ΓöéSecondary Interrupt ControllerΓöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3              ΓöéCOM2                          Γöémay be alterable through BIOS  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé4              ΓöéCOM1                          Γöémay be alterable through BIOS  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé5              ΓöéLPT2                          Γöéfree if no second parallel portΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé6              ΓöéFloppy Drive                  Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé7              ΓöéLPT1                          Γöémay be alterable through BIOS  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé8              ΓöéReal Time Clock               Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé9              ΓöéFree                          Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé10             ΓöéFree                          Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé11             ΓöéFree                          Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé12             ΓöéAux Port (mouse)              Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé13             ΓöéMath Coprocessor              Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé14             ΓöéHard Disk                     Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé15             ΓöéFree                          Γöé                               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

Trap 0003

1.  This trap is almost always caused by IDE problems. If your system is an IBM
    ThinkPad 75x series, make sure you are using the latest BIOS level, then
    reinitialize the system.

2.  If you are using "Red Box" Warp (see Appendix B), you should download and
    apply the file ATAPI.ZIP from the IBM PC Co. BBS (see Section 2.2.3). The
    file is a .ZIP file containing a new set of IDE drivers.

3.  If you have an IDE CD-ROM drive, make sure its master/slave settings are
    correct, and that it is on the correct IDE controller. If so, try
    rearranging IDE devices in your system until the  problem disappears.

4.  Some systems ship with a secondary IDE ribbon cable that is coiled up
    unused next to the power supply. Keep any IDE ribbon cables as far away
    from the power supply of the system as possible.

5.  Some systems ship with the IDE ribbon cable containing the hard drive and
    CD-ROM drive plugged into the wrong IDE controller socket. If this happens,
    the system may appear to work correctly for a while, but will eventually
    generate trap 0003 messages on startup. Try moving the IDE ribbon cable to
    the other IDE controller socket, if your system has one.

Trap 000D

1.  Trap 000D's can either be caused by hardware or software problems. Try the
    steps below to isolate software problems. If you discover the problem to be
    due to an errant application, you should report the error to the
    application's vendor.  If the following steps do not isolate the problem,
    follow the steps outlined for Trap 0002 errors to eliminate hardware
    problems.

2.  Restart OS/2 with floppy diskettes and run CHKDSK against the boot drive
    (see Section 3.1).

3.  If the trap occurs while running a DOS/Windows program, make sure the
    settings for the program are correct (see Appendix C). If the program is
    running over a network, install (do not just copy) and run it locally.

4.  If the trap occurs while running an OS/2 application, try reinstalling the
    application (install it locally if it was previously running over a
    network).

5.  If the machine is on a network, try copying the original CONFIG.SYS in the
    \OS2\INSTALL directory back to the root directory and booting with it (back
    up the old one first, of course).

6.  Make sure the latest video drivers are correctly installed.

7.  Try a non-destructive MAKEINI of the desktop (see Section 3.7.1).

8.  Try a destructive MAKEINI of the desktop (see Section 3.7.2). Then
    reinstall applications as necessary.

Trap 000E

1.  If the error occurs while running DOS/Windows applications, try adding the
    line VME=NO to the CONFIG.SYS.

2.  Trap 000E's are usually caused by some type of software problem. Follow the
    same steps as for trap 000D's above.


ΓòÉΓòÉΓòÉ 8.3. 4.3 Warp Troubleshooting FastPath ΓòÉΓòÉΓòÉ

4.3 Warp Troubleshooting FastPath

The following lists some common problems you may experience in OS/2 Warp,
arranged by the circumstances under which they occur. Following each problem is
a list of possible causes and corrective actions. The most likely causes are
listed first, but you may wish to try the simpler fixes before moving on to
more drastic measures. This list is by no means comprehensive, but it should
serve as a good starting point. Remember the strategies outlined in Section 2
when tackling the problems listed here. You may find solutions to some of these
problems that are not listed here.

Note:  Anytime the system is not shut down properly, there is a good chance
that extended attributes have been corrupted. In any of the following
circumstances, if the system is forcefully restarted using a reset button, or
is powered down while OS/2 is running, you should boot OS/2 from diskettes and
run CHKDSK D: /F (where D: is the OS/2 boot drive) to clean up any extended
attribute errors. If the corruption is allowed to remain, it could cause errors
later on which are extremely difficult to diagnose.


ΓòÉΓòÉΓòÉ 8.3.1. 4.3.1 Problems that occur during installation, or at system startup ΓòÉΓòÉΓòÉ

4.3.1 Problems that occur during installation, or at system startup

OS/2 !! SYS01475 and OS/2 !! SYS02027 errors on startup

1.  A non-bootable floppy diskette has been left in the drive. Remove the
    floppy diskette and restart the system.

2.  The OS/2 boot record has been damaged. Boot OS/2 from floppy diskette,
    either from utility or installation diskettes. Get to a command prompt,
    then insert the first OS/2 boot diskette. Use SYSINSTX to restore the boot
    record (See Section 3.3).

OS/2 !! SYS00276 and OS/2 !! SYS02027 errors occur on startup

1.  The extended attributes have been corrupted to the point the system cannot
    boot properly. This is usually the result of an improper shut down (See
    Section 1.7). Reboot OS/2 using floppy disks and run CHKDSK against the
    OS/2 boot partition (See Section 3.1).

2.  If CHKDSK does not repair the error, you may need to reformat the hard
    drive and reinstall the operating system.

OS/2 hangs or displays an error message before the logo appears at startup.

This is usually caused by an problem with one of the following OS/2 boot files.
Always run CHKDSK after booting from floppy disks (see Section 3.1) before
performing any of the following measures.

1.  EA DATA. SF (FAT volumes only). If this file has been damaged, the system
    may not boot, and will display OS/2 !! SYS00276 and OS/2 !! SYS02027
    errors. Reboot OS/2 using floppy disks and run CHKDSK against the OS/2 boot
    partition (See Section 3.1). If CHKDSK does not repair the error, you may
    need to reformat the hard drive and reinstall the operating system.

2.  OS2BOOT. This file is the OS/2 boot record. If it is missing or damaged,
    the system will display OS/2 !! SYS01475 and OS/2 !! SYS02027 errors. Try
    using SYSINSTX to restore the boot record (see Section 3.3). If SYSINSTX is
    unsuccessful, you must format your hard drive and reinstall the operating
    system.

3.  OS2KRNL, OS2LDR, OS2LDR.MSG. These files comprise the OS/2 kernel and
    loader. If they are missing or damaged, you may try copying them from the
    Installation Diskette or the first Utility Diskette. OS2KRNL is called
    OS2KRNLI on the floppy, and must be renamed to OS2KRNL when it is copied to
    the hard drive.  If OS/2 still fails to boot after you have recopied these
    files, you will need to reformat and reinstall OS/2.

    Note:  The above files should be marked hidden, system, and read only. You
    will need to take these attributes off before replacing them. To do so,
    change to the \OS2 directory and type the following command:

        ATTRIB -S -H -R C:\OS2*.

    When you have finished replacing the files, restore the attributes by
    typing:

        ATTRIB +S +H +R C:\OS2*.

4.  The problem may also be caused by a hardware problem or conflict. If you
    are using a SCSI hard drive, make sure your SCSI card has its boot ROM
    enabled, and that the ROM is at the latest level. Remove any additional
    adapter cards from the system. Ensure that your system's BIOS is configured properly.

OS/2 freezes at the logo, or immediately after the logo.

1.  A device driver (usually NOT video) conflict has occurred, or an incorrect
    driver has been installed. This is most often caused either by hard disk
    controller drivers of some sort (e.g. SCSI, IDE, CD-ROM's, etc.) or LAN
    drivers. Use Alt-F2 (See Section 3.8) to force a boot which displays the
    names of device drivers as they load. The second to last driver displayed
    before the machine freezes is often the culprit. Use Alt-F1 to get to
    recovery choices, and use "C" to get to a command prompt. Use TEDIT to
    remove the conflicting line. You may also be able to use RMVIEW (see
    Section 3.10.1) to determine the conflict, and correct the line either by
    using RESERVE.SYS or explicitly specifying the correct resources for the
    driver by adding parameters to line in CONFIG.SYS that loads the driver.

OS/2 fails at boot with "File not found: COUNTRY.SYS."

1.  This is one of the most maligned and misleading errors in OS/2. It rarely
    has anything whatsoever to do with the COUNTRY.SYS file. CONFIG.SYS may be
    missing from the root directory, damaged, or contain null characters. Copy
    the backup CONFIG.SYS from  \OS2\INSTALL to the root directory.

2.  A conflict may exist between OS/2 and either the hard drive controller or
    floppy drive controller. Comment all BASEDEV lines from the CONFIG.SYS
    except IBMxFLPY.ADD (IBM2FLPY for MCA machines, IBM1FLPY for all others)
    and IBMINT13.I13. These drivers are "lowest common denominator" drivers and
    should work with just about anything with the exception of a few SCSI
    controllers drives  (which should come with their own drivers). Then add
    drivers back one at a time and reboot until you find the offending driver.

3.  The hard drive or floppy drive controller may have an additional device
    (e.g. tape drive, IDE CD-ROM drive) connected which is causing the
    conflict. Remove any such devices. If the problem goes away, try adding the
    device back to see if the error reappears. If it does, contact the
    manufacturer of the device.

4.  An IRQ (or other) conflict may exist between the floppy drive, hard drive
    controller, and other devices in the system (sound boards, network cards,
    etc.). Remove any non-essential adapters from the system to see if this is
    the case, then reconfigure the hardware to eliminate the conflicts.

5.  The computer may be using an incompatible BIOS. Check the BIOS date and
    insure it is in the correct date range for the version of OS/2 being used
    (This information will normally be found in the OS/2 User's Guide). If the
    machine uses a FLASH BIOS insure the latest FLASH level has been applied.

6.  The hard drive may have been compressed with an unsupported compression
    program (e.g. DoubleSpace or SuperStor). Uncompress the drive before
    installing OS/2, or convert the compressed volume to a format supported by
    an appropriate third party OS/2 compression utility.

"SYS0318: Message File OSO0001.MSG Not Found", or "SYS0319: The system cannot
read message file OSO0001.MSG" During Boot.

1.  These messages usually appear if the CONFIG.SYS is damaged in some way. If
    you use the Enhanced Editor in the Productivity folder to edit the
    CONFIG.SYS, it may truncate lines longer than 255 characters. If the PATH=
    or DPATH= statements are truncated, one of these messages may result.
    Either use the System Editor to repair the CONFIG.SYS, or restore a backup
    from an archive. (You can find an unmodified CONFIG.SYS in the \OS2\INSTALL
    directory).

"The System cannot find a Dynamic Link Library" or similar  errors on startup.

1.  The extended attributes for the file may be corrupt. Boot OS/2 with floppy
    diskettes and run CHKDSK against the OS/2 partition (see Section 3.1).

2.  The file itself may be corrupt. Boot OS/2 from floppy diskettes. Insert
    OS/2 installation Diskette 1. Copy all *.DLL files from the diskette to the
    \OS2\DLL directory on the hard drive. Then restart the system. If this does
    not work you may need to reinstall the operating system.

"SYS1201: The device driver XXXX.SYS specified in the XXXX= statement on line
XX of the CONFIG.SYS file was not installed. Line XX is ignored." while
starting OS/2.

1.  There is an error in the line in the CONFIG.SYS that loads the driver in
    question. The line may point to a nonexistent or a corrupt driver, or the
    driver may be improperly configured or in the wrong order in the
    CONFIG.SYS. Read the documentation for the driver to insure that it is
    installed and configured properly.

2.  The hardware device associated with the driver is not being recognized for
    some reason. The BIOS of the system may need to be updated or reconfigured.
    If this error occurs on a ThinkPad, you should reinitialize the system.
    There may also be a hardware conflict in the system, or the device may be
    improperly installed or defective. Make sure you are using the latest
    version of the driver, and that it was written for the version of OS/2 you
    are using.

"SYS1200: The system cannot create the DOS environment." error while starting
OS/2.

1.  A virtual device driver (VDD) may be missing or invalid. VDD's allow DOS
    sessions access to various hardware devices, and if a critical VDD is
    missing, OS/2 may not be able to open a DOS session. Use Selective Install
    to reinstall DOS Support.

2.  This error sometimes occurs after restoring an archive from the Recovery
    Choices Menu. Use Selective Install to reinstall DOS Support.

OS/2 boots to a blank screen and blinking cursor after the logo appears and
disappears.

1.  OS/2 Warp stores display driver resolution information in its .INI files
    (similar to S3 drivers under 2.x). If the .INI files are corrupted,
    replaced, or remade using MAKEINI, the system may boot to a black screen if
    certain SVGA drivers are used. Reboot the system and use Alt-F1 to get to
    the recovery choices menu. Then choose "V" to return to VGA. Use Selective
    Install to reinstall SVGA support.

2.  An incorrect display driver has been installed. Use Alt-F1 to get to the
    recovery choices menu. Select "V" to return to VGA drivers. Then use
    Selective Install to reinstall the correct video drivers.

The system runs CHKDSK automatically every time the system restarts.

1.  OS/2 maintains a dirty flag on the hard drive to determine when the system
    is shutdown. If OS/2 is improperly shut down for any reason (e.g. a system
    crash or power failure), the dirty flag remains set, and OS/2 will run
    CHKDSK on bootup. If you are using dual boot (See Section 1.1.1),  and have
    just returned to OS/2 from a DOS/Windows environment, then this is normal
    behavior.

2.  If you are not using dual boot, then the system is probably not shutting
    down properly. Shut down all programs before attempting to shut down OS/2.

OS/2 boots to a blank desktop, a clock cursor, and the launchpad.

1.  There may be a problem with a WIN-OS/2 audio driver. Reboot, then hold down
    Ctrl-Shift-F1 when the clock appears. If the desktop comes up, disable
    WIN-OS/2 fastload. Check for audio adapter conflicts.

2.  The desktop may be corrupted. Boot OS/2 from floppy diskettes and run
    CHKDSK against the OS/2 boot drive. (see Section 3.1). If you have made a
    recent archive of your system, you may wish to restore it (see Section
    3.5.1). If you do not have a working archive, you can either restore the
    original OS/2 configuration (see Section 3.5.1) or use a nondestructive
    makeini to attempt to rebuild your existing desktop (see Section 3.7.1).

OS/2 boots to a blank desktop and a launchpad. A SYS3175 or SYS3176 appears.
When you dismiss the message, the launchpad disappears, then reappears, and the
SYS317X reappears. This cycle repeats endlessly.

1.  The workplace shell is repeatedly crashing, and then restarting itself,
    usually because of a problem with the desktop. Begin with step 2 above.

2.  A workplace shell extension has been installed and is interfering with the
    desktop. These extensions are not actual programs, but are usually a set of
    .DLL files that add functionality to the OS/2 desktop. Contact the vendor
    of the extension for instructions on how to remove it. You may have to
    resort to destructive MAKEINI (see Section 3.7.2) to resolve the problem.

A program caused the system to hang. Now, every time the system starts up, the
same program automatically runs and immediately hangs the system, creating an
inescapable loop.

1.  As a short term solution, hold down [Ctrl]-[Shift]-[F1] as soon as you see
    the clock when the system reboots. This will prevent any applications that
    were open when the system was last shut down from launching automatically
    when OS/2 restarts.

2.  As a long term solution, add the line SET RESTARTOBJECTS=STARTUPFOLDERSONLY
    to the CONFIG.SYS. This will make the Ctrl-Shift-F1 behavior permanent.

The launchpad does not appear when the system is started.

1.  The launchpad may have been deleted or disabled by accident. Add the
    LAUNCHPAD parameter to the AUTOSTART line in CONFIG.SYS. This will restore
    a DEFAULT launchpad (regardless of why it disappeared). You can leave the
    parameter in place once the launchpad reappears. If you did not delete the
    launchpad (it "disappeared" on its own), then change the autostart line,
    boot OS/2 from floppy diskettes,  and run CHKDSK (see Section 3.1) to make
    sure desktop corruption has not occurred.

2.  If you accidentally delete the LaunchPad, you can double-click on any open
    area of the desktop to recreate it. Any customizations you have made to the
    launchpad will be lost.


ΓòÉΓòÉΓòÉ 8.3.2. 4.3.2 Problems related to video ΓòÉΓòÉΓòÉ

4.3.2 Problems related to video

Screen corruption in various Windows programs running on the OS/2 Desktop.

1.  Make sure that you are using the latest video drivers for your system, and
    that they are correctly installed.

2.  Some Windows applications may only run correctly in a full screen
    environment. Try running your application in a Full Screen session.

3.  Try dragging the application's window to the lower right corner of the
    screen such that most of the application's window is off the bottom of the
    screen and cannot be seen. Then double click the application's title bar to
    maximize it. This will often cure the "transparent windows" that sometimes
    occur in Microsoft Office applications.

Desktop colors appear "plaid" or distorted while running some WIN-OS/2
applications.

1.  This behavior normal, and is caused by palette switching. You should only
    see this when in 256 color mode. When you quit the application, the Desktop
    colors should revert to normal. If not, try opening and closing some
    folders on the OS/2 Desktop.

2.  If the screen still does not restore itself, try enabling the "palette
    aware" option on the screen tab of the System settings notebook in the
    System Setup folder. Then shut down and reboot. This option will not be
    available with all display adapters.

3.  Make sure you are using the latest video drivers for your system, and that
    they are properly installed.

SVGA support is installed, but the OS/2 will not allow the use of high refresh
rates supported by your card, even though the you ran the utility program to do
so during installation.

1.  OS/2 uses the SVGADATA.PMI file to determine the proper resolutions and
    refresh rates for various adapter cards. This file is generated by the
    SVGA.EXE program, which queries the adapter for supported resolutions and
    refresh rates. OS/2 versions 2.1 and above allow you to run a DOS utility
    program during installation (such as VMODE or REFRESH) to set up the card
    for optimal settings before SVGA queries it. Apparently a problem with OS/2
    Warp's video subsystem can in some cases cause these refresh rate utility
    programs to fail; so when SVGA runs, it generates a .PMI file based on the
    card's default settings, which may or may not be optimal. You can correct
    this situation by running SVGA OFF from an DOS fullscreen prompt. This will
    erase the current .PMI file. Then run SVGA ON MONITOR. Type CUSTOM at the
    menu that appears, and you will be asked to manually enter the refresh
    rates supported by your adapter. Shut down and reboot, and you should be
    able to select the new refresh rates from the screen tab in the system
    settings notebook. This may not work with all adapters.

    Note:  If you remove SVGA support by turning SVGA OFF, do not shut down the
    system before recreating the .PMI file (by running SVGA ON), or OS/2 may
    boot to a black screen. If this happens, boot your system with DOS, then
    run SVGA ON DOS. Then rename the file SVGADATA.DOS to SVGADATA.PMI and put
    it in your \OS2 directory. (If your drive is formatted with HPFS, you will
    not be able to see it from DOS. In this case, you should boot to a command
    prompt using ALT-F1, copy the SVGA.EXE from the \OS2 directory to your DOS
    boot floppy before rebooting the system). Note that you may not be given
    the option to change the refresh rate with all display adapters.


ΓòÉΓòÉΓòÉ 8.3.3. 4.3.3 Hard drive/SCSI device recognition problems ΓòÉΓòÉΓòÉ

4.3.3 Hard drive/SCSI device recognition problems

When using FDISK, OS/2 only sees around 500Mb of an IDE hard drive, or sees all
of it, but will not format a partition greater than 500Mb.

1.  The original IDE specification has a limit of 1024 cylinders per drive.
    This is a limit caused both by the system BIOS and the IDE controller
    itself. On virtually all modern hard drives, 1024 cylinders translates to
    roughly 503Mb per IDE drive. OS/2 can see all of the drive even with a
    standard IDE controller, but the OS/2 boot partition must reside within
    1024 cylinders. The remainder of the drive must be formatted as HPFS, and
    can be used as a data drive.

2.  If you are using Warp /w WIN-OS/2 or Warp Connect, you can use a product
    called OnTrack Disk Manager (Disk Manager is bundled with many hard drive
    kits) that will allow you to use the entire drive as one partition. Disk
    Manager works by remapping the drive geometry so that the drive appears to
    have less than 1024 cylinders.

3.  The enhanced IDE (EIDE) specification breaks the 1024 cylinder limit by
    "deceiving" the BIOS into thinking the drive has less than 1024 cylinders.
    To avoid the limitations described in step 1 above, you need both an
    enhanced IDE controller and a new system BIOS that supports EIDE. If you
    have both of these, and your large hard drive is still not being recognized
    properly, then the EIDE features may have been disabled in your machine.
    Run the configuration utility for your machine and re-enable these features
    (They may be called different things on different machines, such as "High
    Performance I/O" or "Logical Block Addressing").

SCSI devices are not recognized by OS/2.

1.  For all SCSI devices, make sure that ID's and device termination are set up
    properly. The SCSI controller itself is set to 7, and in IBM systems, the
    first SCSI hard drive is usually set to 6. Typically the last device on the
    SCSI chain must be terminated. The length of the entire SCSI chain should
    not exceed 3 meters (this includes any cables attached to devices inside
    the case).

2.  Before using any SCSI devices in your system, you must have the correct
    drivers installed for your SCSI adapter. Make sure that you are using the
    latest drivers for the SCSI adapter in your system, and that they are
    properly installed.

3.  Some very old SCSI controllers have size limits for hard drives. If you are
    using a hard drive over 1Gb in size and are having problems, check the
    documentation for your SCSI controller.

4.  Not all SCSI devices have native support in OS/2. Scanners and Tape drives,
    for example, are supported through the applications that use them. Other
    devices, such as SCSI CD-ROM drives, require their own drivers in addition
    to the SCSI adapter drivers.

5.  In order to boot from a SCSI hard drive, your SCSI adapter must have its
    boot ROM enabled. Some older SCSI cards may need to have this ROM updated
    to work correctly with OS/2. Also make sure there are no adapters in your
    system using upper memory address ranges ( e.g. networking cards) that
    conflict with the address range for your SCSI adapter.

6.  If you have both an IDE and a SCSI drive, the IDE drives will always be
    mapped first.  To avoid drive mapping problems, make sure the IDE driver
    (BASEDEV=IBM1S506.ADD) comes before any SCSI drivers in your CONFIG.SYS.

7.  Different SCSI controllers have different ways of performing sector
    translation for hard drives. If your system is having problems recognizing
    a SCSI drive, you should low-level format the SCSI hard drive using the
    controller that the drive will be used with. This is also true if you are
    experiencing slow performance with the drive.

8.  If your SCSI card does not have an OS/2 driver available, you may be able
    to use the generic interrupt 13 driver (Add the line BASEDEV=IBMINT13.I13
    in your CONFIG.SYS) to use your SCSI hard drive. Note this driver will
    recognize hard drives only and may not work with all SCSI adapters.

9.  If you do have the correct SCSI drivers installed, remove the line in the
    CONFIG.SYS that loads IBMINT13.I13 if it is present. This driver may
    conflict with your SCSI adapter driver.

OS/2 is unable operate your hard disk"  or similar errors on startup.

1.  This error usually occurs if there is a problem recognizing your hard drive
    controller. If you are using a SCSI controller, follow the steps listed for
    SCSI devices not being recognized on the previous page.

2.  If you are using an IDE controller, make sure the hardware is properly
    configured. Also make sure the line BASEDEV=IBM1S506.ADD appears in the CONFIG.SYS.

3.  If none of the above steps work or are applicable, you may be able to use
    the generic interrupt 13 driver (Add the line BASEDEV=IBMINT13.I13 in your
    CONFIG.SYS) to use your hard drive. Note this driver may not work with all
    hard drive controllers.

4.  If you do have the correct drivers installed for your hard drive
    controller, remove the line in the CONFIG.SYS that loads IBMINT13.I13 if it
    is present. This driver may conflict with your hard drive controller
    driver.

5.  If your system has dual boot installed, an error may have occurred while
    swapping your startup files during the dual boot process. Boot the system
    with floppy diskettes and see if the CONFIG.SYS is a DOS CONFIG.SYS (check
    for the line DEVICE=C:\DOS\HIMEM.SYS near the top of the file). If so,
    check for the presence of CONFIG.OS2 and AUTOEXEC.OS2 in the OS2\SYSTEM
    directory. If these files are present, copy them to the root directory as
    CONFIG.SYS and AUTOEXEC.BAT, respectively (back up your existing ones
    first). If these files are not present, you may try booting to the recovery
    choices menu (see Section 3.5) and restoring an archive, or you may be able
    to use the backup CONFIG.SYS located in the \OS2\INSTALL directory. If none
    of these methods are successful, you will need to reinstall the operating
    system.


ΓòÉΓòÉΓòÉ 8.3.4. 4.3.4 Multimedia ΓòÉΓòÉΓòÉ

4.3.4 Multimedia

Your IDE CD-ROM is not recognized by OS/2.

1.  If the machine is a ThinkPad 755CDx series insure that the drivers are
    installed properly, then reinitialize your system (see the documentation
    for the ThinkPad for directions). If the problem persists, make sure you
    are using the latest FLASH BIOS level. There may also be an IRQ conflict
    between the PCMCIA socket controller and the CD-ROM drive.  You can add the
    /C0 parameter to BASEDEV=IBM2SS01.SYS line in the CONFIG.SYS to change the
    IRQ used by the PCMCIA socket controller (usually IRQ's 9 and 11 are
    available). If the system is in a docking station, you may also need to
    change the interrupt used by the socket controller in the docking station.
    The following example illustrates this. The line below specifies that
    socket controller 0 (The one in the ThinkPad) uses IRQ 9 and that socket
    controller 1 (In the dock) uses IRQ 11 (changes are in boldface).

        BASEDEV=IBM2SS01.SYS /C0=9 /C1=11


    You can check for free IRQ levels by using the ThinkPad Setup Utility or by
    using RMVIEW /IRQ (see Section 3.10.1).

2.  If you have an IBM system preloaded with OS/2, you may also wish to
    download ATAPI.ZIP from the IBM BBS (see Section 2.2.3 for BBS
    information). ATAPI.ZIP contains updated IDE CD-ROM drivers that fix a
    number of difficulties present in the version that shipped with Warp. The
    following lines should be present in the CONFIG.SYS for IDE CD-ROM support:

        BASEDEV=IBM1S506.ADD
        DEVICE=C:\OS2\BOOT\OS2CDROM.DMD
        BASEDEV=IBMIDECD.FLT
        IFS=C:\OS2\BOOT\CDFS.IFS /Q

The CD-ROM drive letter maps as drive F: (or some other drive letter),
conflicting with a network drive assignment.

1.  You must reconfigure the network so that network drives are mapped to a
    drive other than the one used by the CD-ROM. CD-ROM drives are mapped
    immedaitely after the last hard drive partition at start up. The drive
    letter for the CD-ROM cannot be changed.

"SYS1174: The xxx device is already in use by another application" when
launching a WIN-OS/2 session.

1.  Many audio adapters may be used by only one application at a time. This
    error usually occurs when using sound drivers in WIN-OS/2. If you launch a
    WIN-OS/2 session while OS/2 is using the audio card, or while another
    WIN-OS/2 session is already open, you may receive this message. If your
    WIN-OS/2 application does not require sound, change the
    AUDIO_ADAPTER_SHARING setting for the session to Off. Run all of your
    applications that do require sound in the same Windows session (i.e., make
    sure that these programs are all set to either Standard or all set to run
    in Enhanced mode, and that the separate session option on the session page
    of the system settings notebooks of the applications is not selected), and
    make sure that AUDIO_ADAPTER_SHARING for that session is set to Required.

The correct  drivers have been installed for multimedia, but there is still no
sound in OS/2.

1.  The audio driver is set up incorrectly. Use RMVIEW to see what resources
    the driver is attempting to use, then check to see what resources the
    adapter is actually using. You may need to specify or correct parameters on
    the line(s) which load the audio support. Or remove the drivers and use
    selective install to reinstall multimedia support with the correct
    settings.

2.  You may have a resource conflict. Check the I/O port address,  IRQ, and DMA
    channel settings on your audio adapter and make sure there are no conflicts
    with any other adapters in the system.


ΓòÉΓòÉΓòÉ 8.3.5. 4.3.5 Problems running applications ΓòÉΓòÉΓòÉ

4.3.5 Problems running applications

A SYS0004 occurs when starting or running an application.

1.  This message can be caused by an application trying to open one or more
    files when the system has run out of resources such as memory.
    Theoretically, you can open an infinite number of files open in OS/2
    because the file handles and buffers are allocated dynamically as they are
    needed. If your system is out of memory, however, additional space cannot
    be allocated, hence this message. Even though OS/2 uses virtual memory,
    there are certain code segments and data areas that cannot be paged to
    disk. Try shutting down some open applications. If the problem goes away,
    you may need to purchase additional RAM.

2.  One of your open applications may also have a memory leak. Memory leaks
    occur when applications allocate memory, but then never release it when
    they are finished with it. Memory leaks can also cause excessive growth of
    the SWAPPER.DAT file. If you suspect a memory leak in your application, you
    should report it to the application vendor to have the problem fixed.

SYS0023 and/or  SYS0041 Errors (CRC Errors) occur when reading or writing data
on a disk.

1.  Both of these errors indicate that a CRC error (Cyclic Redundancy Check)
    has occurred. A CRC error usually indicates that a sector on the disk is
    going bad. If this happens, you should either high-level format the drive
    or use a third party utility that can find and mark bad sectors on the
    disk's recording surface. Usually the data contained on these bad sectors
    is lost. If the error occurs on a floppy disk, you can sometimes retry the
    operation several times and eventually get it to complete successfully. If
    you are able to do this, you should immediately back up the floppy disks
    before the sector(s) become unrecoverable. If the error occurs repeatedly
    on a hard disk, you may need to replace the hard disk.

2.  A CRC error can also be caused by damage to the data recorded on the disk
    without actual damage to the surface of the disk itself. This usually
    happens when a floppy disk is exposed to extreme temperatures or strong
    magnetic fields. More often than not, the affected data cannot be
    recovered, although there are various utilities on the market that claim
    the ability to "revive" floppy disks. In general, you should avoid exposing
    your floppy disks to extreme temperatures or magnetic fields.

SYS3175 or SYS3176 errors while running OS/2 applications.

1.  Either of these two error messages occur when a program tries to make an
    illegal memory access. These errors are more or less equivalent to the
    General Protection Fault messages that occur in Windows 3.1. OS/2, however,
    terminates the program before any damage is done. The application may not
    be installed correctly. Make sure the application is installed and
    configured properly. You may wish to try re-installing the application

2.  If the application is trying to access a particular data file when the
    error occurs, the data file may be damaged.

3.  Your desktop may be corrupt, and the application may be trying to access
    its entries in the OS2.INI. Try using the MAKEINI procedure (see Section
    3.7) to rebuild the desktop. A destructive MAKEINI may be necessary.

4.  The application may be poorly written. Applications will often crash if
    they encounter some type of error they are not programmed to deal with,
    such as the causes mentioned above. Contact the vendor of the application
    to see if a more recent (and hopefully more stable) version is available.

SYS3175 or SYS3176 errors while running DOS or Windows applications.

1.  These errors are usually an indication that the settings for the program
    are incorrect. If you are uncertain about what the correct settings should
    be, try using the Add Programs object in the System Setup folder to
    re-migrate the application. You can also find files with "optimal settings"
    recommendations for a variety of programs on a number of BBS's and internet
    sites. These files are usually posted by "power users" who have
    experimented with settings. See Appendix C for more information on DOS
    settings.

2.  If this is a WIN-OS/2 application, try running it in a separate session.
    Also make sure the WIN_RUN_MODE setting is set to 386 Enhanced
    Compatibility Mode.

3.  If you are getting this error while running WIN-OS/2 sessions on a ThinkPad
    75x series, set DOS_HIGH  to OFF.

4.  Try placing the line VME=NO in the CONFIG.SYS. This will disable the
    Virtual mode extensions of 80486 and above microprocessors which can
    sometimes cause instability of DOS and WIN-OS/2 sessions.

When launching a WIN-OS/2 windowed session, the icon hashes and the session
begins to startup, but quits before it comes up. Launching a full-screen
session produces a brief black screen, then returns to the desktop.

1.  Try going to a DOS full screen, and then running WINOS2.COM. If Windows
    starts, then the settings for your Windows session are incorrect. See step
    3 below. If Windows does not start, it will at least give  you an error
    message which you can use to track down the problem. "Fatal exit 0401"
    codes are usually an indication of something wrong with your SYSTEM.INI.

2.  This may be caused by a problem in the SYSTEM.INI or WIN.INI files, usually
    a video driver. These Windows files are analogous to the OS2SYS.INI and
    OS2.INI files in OS/2 (See Section 3.7), except that may be edited by any
    text editor. Verify that you have the proper video drivers installed for
    WIN-OS/2. If not, then use the recovery choices menu to reset the video to
    VGA. Then use Selective Install to reinstall the correct video drivers.

3.  Verify that the DOS and WIN-OS/2 settings are correct for the program you
    are running. If you are uncertain about what the correct settings should
    be, try using the Add Programs object in the System Setup folder to
    re-migrate the application. You can also find files with "optimal settings"
    recommendations for a variety of programs on a number of BBS's and internet
    sites. These files are usually posted by power users who have experimented
    with settings.

4.  The AUTOEXEC.BAT file may be missing, damaged, or contain a statement that
    is causing the WIN-OS/2 session to fail. Check the AUTOEXEC.BAT file for
    errors. Make sure the PATH statement includes your WINDOWS  (for Warp Red
    Box, usually C:\WINDOWS) or WINOS2 (for Warp with WIN-OS/2, usually
    C:\OS2\MDOS\WINOS2) directory.

5.  Your WIN-OS/2 subsystem may be corrupted, or they may be another (non-video
    related) problem with your SYSTEM.INI. If steps 1-3 above fail to correct
    the problem, you may wish to use the Selective Install in the System Setup
    folder to reinstall DOS and WIN-OS/2 support. If this still fails to
    correct the problem, and you are using any "Blue Box" version of Warp (see
    Appendix B), you can try shredding the WINOS2 folder from the drives
    object, and then selectively reinstalling WIN-OS/2 support. If this allows
    you to now start WIN-OS/2, you will probably have to reinstall your Windows
    applications.

Win32s errors when starting WIN-OS/2 applications.

1.  Win32s is an API that allows developers to write 32-bit Windows programs
    that run under Windows 3.1. OS/2 Warp currently only supports Win32s
    version 1.15. Windows applications that require a later version will not
    run under OS/2.

2.  Make sure that Win32s 1.15 has been properly installed and configured. The
    Win32s run-time file may or may not be provided with the application, and
    must be installed for Win32s applications to work. Win32s can be obtained
    from Microsoft.

Errors about *.386 files not being installed when starting WIN-OS/2
applications.

1.  Some Windows applications require *.386 files (also known as VxD's, or
    Windows virtual device drivers) that load in the Windows SYSTEM.INI file.
    OS/2 does not support VxD's (They could compromise system integrity), so
    any applications that require them will not run under OS/2.

"Another program is already using the processor in 386 protected mode" or
similar errors while starting DOS applications.

1.  The DOS program probably uses VCPI (Virtual Control Program Interface)
    memory. VCPI applications could compromise system integrity, and are thus
    not supported under OS/2. Contact the vendor of the application for an
    update.


ΓòÉΓòÉΓòÉ 8.3.6. 4.3.6 Swapper/Hard drive space problems ΓòÉΓòÉΓòÉ

4.3.6 Swapper/Hard drive space problems

The SWAPPER.DAT file in Warp is larger than in previous versions of OS/2

1.  SWAPPER.DAT is the file Warp uses when it swaps memory to the hard disk.
    Warp changed the way memory is paged to the hard disk from previous
    versions of OS/2. The net result of these changes is usually a larger swap
    file when running under Warp than under OS/2 2.x. Under Warp, the swap file
    may grow as you launch programs, but may not shrink dramatically after you
    shut them down. This is normal, and is done to improve system performance.

2.  If the swapper file keeps growing until it fills up your available hard
    drive space (even after shutting down applications), you may have a memory
    leak in one of your applications or a problem with OS/2. If the problem
    occurs when running a specific application, report the problem to the
    vendor of that application. If the problem does not appear to be linked
    with a specific application, try removing all nonessential software
    components from the system (e.g. networking drivers) to isolate the cause
    of the memory leak.

A black screen with the following message appears while running applications:
"The partition containing the SWAPPER.DAT file is full. You may lose data.  Do
not ignore this message!"

1.  This message occurs when the swapper file becomes so large that it has
    almost consumed all available disk space. Ironically, the best course of
    action when you receive this message is to choose ignore the error and
    continue. If you choose end command/program/operation, the system will kill
    the workplace shell (which can in turn lead to a system crash). When the
    desktop reappears, immediately close down at least one of your
    applications. Note that when this error appears, you still have some disk
    space left. If the message reappears and you continue ignoring it without
    shutting anything down, the disk will fill completely up, causing a system
    crash.

2.  If the problem occurs again, you may need either to relocate your swapper
    file to another partition with more free space or delete some unneeded
    files from the OS/2 partition (If you don't know what you are deleting,
    leave it alone. Under no circumstances remove any portion of the OS/2
    system files).

    Note:  If your system was preloaded with OS/2, run the Diskette Factory
    program to make all of the OS/2 and other installation diskettes for your
    system. Then use Diskette Factory to delete the diskette images from your
    hard drive. This should free up a substantial amount of disk space.

    The SWAPPATH line in the CONFIG.SYS determines the swapper file parameters
    and can be used to relocate the swap file:

        SWAPPATH=Path Minfree Initsize


    Path determines the location of the swapper file. Relocate this as
    necessary to a drive with sufficient free space. Minfree determines how
    little free space (in Kb) must be left on the hard drive before the warning
    message appears. Initsize determines how large the SWAPPER.DAT file is when
    initially created. If you typically have a large swap file while running
    OS/2, you may wish to set Initsize to match the size of your normal
    SWAPPER.DAT as closely as possible. The following example illustrates the
    correct use of the SWAPPATH statement for setting up a swap file on D: with
    2Mb of "buffer space" and an initial size of 16Mb:

        SWAPPATH=D:\ 2048 16384


ΓòÉΓòÉΓòÉ 8.3.7. 4.3.7 Printing Problems ΓòÉΓòÉΓòÉ

4.3.7 Printing Problems

Printer off line or out of paper" when trying to print from OS/2. Printing from
DOS works as expected.

1.  Make sure you are using the latest printer drivers for your printer and
    that they are properly installed.

2.  If you are using interrupt based printing (BASEDEV=PRINT0x.SYS line will
    have a /IRQ after it in your CONFIG.SYS), try a different cable. The
    printer cable must have all 25 pins active for interrupt based printing to
    work. Some low end DOS cables only use 6 pins. The printer should be
    attached locally (for troubleshooting purposes), and the printer cable
    should not exceed 6 feet in length. Make sure that IRQ7 is not being used
    by another device in the system.

3.  If you are using polling (this is the default), try using interrupt based
    printing. Some printers require interrupt based printing to work properly
    in OS/2. Add a /IRQ to the PRINT0x.SYS line in your CONFIG.SYS so that it
    reads

        BASEDEV=PRINT0x.SYS /IRQ

    This will enable interrupt based printing. Again, make sure you are using a
    printer cable with all 25 pins active, and that IRQ7 is not being used by
    another device in the system.

4.  If you are using a ThinkPad 701 system,  the ESS Audio System uses IRQ 7,
    which conflicts with the parallel port. Use the ThinkPad Setup Utility to
    change ESS Audio from IRQ 7 to IRQ 10 in the system's BIOS. Then find the
    DEVICE=C:\MMOS2\ES688DD.SYS  line in the CONFIG.SYS and change it so that
    it reads as follows (Changes are in bold):

        DEVICE=C:\MMOS2\ES688DD.SYS /B220 /D1 /I10

5.  If you have any other devices such as software copy-protection "dongles",
    parallel port tape backup units, parallel port CD-ROM drives, printer
    switch boxes, or other devices attached to the parallel cable in addition
    to your printer, try removing them. Such devices may interfere with
    printing and are not supported under OS/2.

Problems printing from OS/2 applications.

1.  Follow the steps listed for "Printer off-line or out of paper" above.

2.  Try removing, then reinstalling your printer drivers.

3.  Remove your existing printer drivers. Perform a non-destructive MAKEINI of
    your desktop (see Section 3.7.1). Then reinstall your printer drivers.

4.  Remove your existing printer drivers. Perform a destructive MAKEINI of your
    desktop (see Section 3.7.2). Then reinstall your printer drivers.

Problems printing from WIN-OS/2 applications.

1.  Check to see if OS/2 applications are printing properly (The Enhanced
    Editor and IBM Works are good applications to test this with). If not,
    follow the steps for "Problems printing from OS/2 applications" above,
    including Step 1.

2.  Make sure you have the proper WIN-OS/2 printer drivers for your printer
    properly installed.

3.  If you are using Windows 3.x drivers provided with your printer, make sure
    the output port is set to LPT1.OS2 in the WIN-OS/2 Printers Control Panel,
    and that the default printer driver on the OS/2 desktop is set to IBM Null.

4.  Try enabling or disabling the WIN-OS/2 Print Manager in the WIN-OS/2
    Printers Control Panel.


ΓòÉΓòÉΓòÉ 8.3.8. 4.3.8 Other problems ΓòÉΓòÉΓòÉ

4.3.8 Other problems

A SYS0551 warning occurs while running CHKDSK against an HPFS drive.

1.  The message will appear as follows:

    SYS0551: Warning! CHKDSK cannot find the root directory of the specified
    disk but will still attempt to reconstruct the file system.

    You will only see this warning if you are running CHKDSK against an HPFS
    drive. The warning occurs if the root directory of the hard drive has
    become completely unreadable. The structure of HPFS allows CHKDSK to
    reconstruct the root directory of your drive based on double links between
    file system structures. When CHKDSK completes, check to make sure that all
    of your files have been recovered. If you notice that something is missing,
    you may be able to use the /F:3 parameter of CHKDSK (see Section 3.1) to
    recover the missing files. This level of error recovery is impossible for
    FAT drives, and it is for this reason you should always use HPFS if
    possible.

The message "SYS2065: The system is stopped" appears - either during startup or
after a Trap message has been displayed.

1.  This message is almost always preceded by another message (e.g. a message
    stating that "OS/2 is unable to operate your hard disk,"  "Trap XXXX," or
    "an internal processing error has occurred"), and means that an error of
    such serious nature has occured that OS/2 is unable to proceed further.
    Usually the system is completely locked up and a power off is required. You
    will probably have to determine the cause of the first error message to fix
    this one.

PCMCIA cards are not recognized.

1.  PCMCIA architecture is discussed in Section 5.1. The PCMCIA drivers may not
    be installed correctly, or you may have an obsolete version of the drivers
    installed. Remove any references to PCMCIA drivers in your CONFIG.SYS and
    erase any all copies of the PCMCIA drivers from the hard drive (The
    filenames are those listed in the CONFIG.SYS below. You may find duplicate
    copies of these files in several directories, including \OS2 and
    \OS2\BOOT). Use Selective Install to reinstall the OS/2 PCMCIA drivers for
    your system. When PCMCIA support is correctly installed, the following
    lines should appear in the CONFIG.SYS.

        BASEDEV=PCMCIA.SYS                ;Card Services
        BASEDEV=IBM2SS01.SYS              ;Socket Services (This line may vary)
        DEVICE=C:\OS2\BOOT\$ICPMOS2.SYS   ;Suspend/Resume driver for PCMCIA
        ;(The following lines are generic  client enablers provided with OS/2)
        DEVICE=C:\OS2\AUTODRV2.SYS C:\OS2\AUTODRV2.INI   ;modem card
        BASEDEV=PCM2ATA.SYS               ;ATA hard drive card
        DEVICE=C:\OS2\BOOT\ICMEMMTD.SYS   ;(or ICMEMCDD.SYS) FLASH memory card

2.  If you are using a ThinkPad in a Dock II, you may have an interrupt
    conflict. Try adding the parameter /C0=irq to the socket services line in
    the CONFIG.SYS (see above), where irq is a free IRQ level. You can use
    RMVIEW /IRQ (See Section 3.10.1) or the ThinkPad Setup Utility (on some
    ThinkPads) to determine which IRQ's are available. Usually IRQ 9 is
    available.

3.  Your system may not be supported by the socket services drivers provided
    with OS/2. If this is the case, you will have to obtain an OS/2 socket
    services driver for your system from the system's manufacturer.

4.  Your card may not be supported by the client enablers provided with OS/2.
    If this is the case, you will have to obtain an OS/2 client enabler for the
    card from the card's manufacturer.

The "Lock System at Startup" feature is enabled, but you have forgotten your
password. When the system starts up, the desktop immediatedly locks up.

1.  Restart the system to the recovery choices menu, (see Section 3.5) or boot
    OS/2 from floppy diskettes. Get to a command line. Change to the \OS2
    directory and run the following command:

        MAKEINI OS2.INI LOCK.RC


    When the command has completed, restart the system. The password will be
    removed and the lockup feature disabled. You can enter a new password and
    re-enable the lockup feature from the Lockup tab of the Desktop settings notebook.


ΓòÉΓòÉΓòÉ 9. Section 5. Hardware Compatibility ΓòÉΓòÉΓòÉ

SECTION 5: HARDWARE COMPATIBILITY

Sometimes it is not easy to differentiate between problems with OS/2 and
hardware problems. This section discusses hardware compatibility issues with
OS/2, as well as briefly describing elements of the PC architecture that may be
relevant when doing troubleshooting. Note that specific troubleshooting
procedures for many of the hardware devices mentioned here are discussed in
Section 4 of this work.


ΓòÉΓòÉΓòÉ 9.1. 5.1 BUS Types ΓòÉΓòÉΓòÉ

5.1 BUS Types

When troubleshooting OS/2 it is important to understand the bus architecture of
the system in question.  A bus architecture is a hardware specification that
determines how adapter cards communicate with the computer system. PC systems
may use any combination of the bus types listed below, though some combinations
are more common than others. Most modern PC's use ISA bus in conjunction with
one of the local bus architectures.

o   ISA (Industry Standard Architecture).  ISA, also known as AT-Bus, was the
    original bus architecture used by the IBM PC AT. ISA remains the most
    popular bus for PC's. ISA cards are typically configured using jumpers or
    dip switches on the card itself.

o   EISA (Extended Industry Standard Architecture).  EISA is an improved, high
    speed version of ISA developed by Compaq and others. EISA connectors can
    accept both ISA and EISA cards, though only EISA cards will reap the
    performance benefits of the EISA bus. EISA cards are usually configured by
    software that comes with the card. Some EISA cards support a feature called
    bus mastering that allows the EISA card to control the EISA bus. Such cards
    may not work properly in bus mastering mode under OS/2.

o   Microchannel (MCA).  Microchannel is a proprietary high speed bus
    architecture developed by IBM for the PS/2 line of personal computers.
    Microchannel is not backward-compatible with ISA cards. Microchannel cards
    are configured by running the Set Configuration utility on the reference
    disk for the microchannel PC. On some microchannel systems, you may be
    asked to insert the system's reference diskette during the installation of
    OS/2. On others you may have to patch your OS/2 installation diskette
    manually before OS/2 will install correctly. This procedure is called an
    ABIOS patch, and typically involves copying files from your system's
    reference diskette to the installation diskette. See the OS/2 README file
    for more information.

o   Local bus.  Local bus is a term used to describe several new high speed bus
    architectures that attempt to avoid speed bottlenecks by linking directly
    into the microprocessor bus. There are currently two prevalent local bus
    standards: VL-Bus and PCI.

    -   VL-Bus (VESA Local Bus).  VL-Bus a local bus architecture developed by
        the Video Electronics Standards Association that is used primarily in
        80486 based systems. VL-Bus is actually an extension of the ISA bus,
        and VL-Bus cards are typically configured through dip switch or jumper
        settings just as ISA cards are. The VL-Bus architecture is losing
        popularity to PCI, but there are many VL-Bus systems still in use.

    -   PCI (Peripheral Component Interconnect).  PCI is a local bus
        architecture developed by Intel that is used extensively on Pentium
        systems. PCI has several advantages over VL-Bus, and is gradually
        becoming the dominant local bus architecture. PCI cards are generally
        auto-configuring. Settings are usually changed either by software that
        comes with the card or by running the system's configuration utility.

o   Plug-and-Play.  Plug-and-Play is an extension to ISA developed by Intel,
    Microsoft and others. Plug-and-Play attempts to simplify the configuration
    of PC's by using better resource management and allowing for automatic
    configuration of adapters. Plug-and-Play cards are supposed to be
    auto-configuring, but settings can usually be changed by running the
    software that comes with the card or by running the system's configuration
    utility. Conflicts may result if plug-and-play and non plug-and-play
    devices are used in the same system. As of this writing, OS/2 has no built
    in support for the plug-and-play BIOS. OS/2 can still be used with
    plug-and-play systems and devices, but any adapters must be configured
    through the system's BIOS or through software that comes with the card.

o   PCMCIA (Personal Computer Memory Card International Association). PCMCIA is
    a hardware specification for the credit-card sized peripherals (called PC
    Cards or just PCMCIA cards) used in many notebook computers. PCMCIA cards
    are configured by running software that comes with the card. Of all the bus
    types listed here, PCMCIA usually causes the most headaches, primarily
    because of a lack of standardization. PCMCIA support under OS/2 requires
    that special drivers be loaded. You can use Selective Install to install
    the drivers. PCMCIA support under OS/2 is three-layered: socket services,
    card services, and the client enabler (or superclient driver) for the card
    itself.

    -   Socket Services. The socket services driver provides a low level
        interface between card services and the PCMCIA socket controller. It
        must be loaded before card services or any client enablers or
        SuperClient drivers. Socket services is system specific. If you attempt
        to use Selective Install to install PCMCIA support for your machine,
        but it does appear in the list of machines supported by Warp, then you
        will need to obtain the OS/2 socket services driver from your system's
        manufacturer.

    -   Card Services. The card services driver allocates resources such as
        memory, interrupts, and I/O addresses to the PCMCIA card and its
        drivers. Card services must be loaded after socket services, but before
        any client enablers or SuperClient Drivers. Card Services is operating
        system specific, and is automatically installed when you install PCMCIA
        support under OS/2.

    -   Client Enablers. Client enablers are card-specific drivers that
        configure the card and allow it to be recognized by applications.
        Client enablers communicate to the card via card and socket services.
        Each card will typically have its own client enabler that is provided
        by the manufacturer of the card.

    -   SuperClient Drivers.  A SuperClient driver is essentially a generic
        client enabler which may support many different types of cards (modems,
        network adapters, etc.). OS/2 Warp comes with SuperClient drivers for
        modems, flash memory cards, and ATA hard disk cards. If your card is
        not supported by these drivers, then you should obtain the OS/2 client
        enabler from your card's manufacturer.

        PCMCIA troubleshooting procedures are discussed in Section 4.3.8.


ΓòÉΓòÉΓòÉ 9.2. 5.2 The IDE vs. SCSI debate ΓòÉΓòÉΓòÉ

5.2 The IDE vs. SCSI debate

There are currently two competing storage interfaces for PC's: SCSI and IDE.
Each has its advantages and disadvantages for OS/2 users.


ΓòÉΓòÉΓòÉ 9.2.1. 5.2.1 SCSI: The power user's choice ΓòÉΓòÉΓòÉ

5.2.1 SCSI: The power user's choice

SCSI (Small Computer System Interface) is a storage interface originally
designed for mini-computers. Over the years many improvements have been made to
the original SCSI specification, such as Fast/Wide SCSI and more recently, SCSI
3. Up to 7 devices can be daisy chained to a single SCSI controller. Each
device must have a unique ID. The last device in the chain must typically have
a device known as a terminator attached to it. The terminator is used to
prevent line noise from interfering with communication between the controller
and devices on the chain. SCSI supports a wide range of I/O devices, including
CD-ROM drives, tape drives, optical drives, scanners, and even printers. The
result is an extremely flexible, high performance interface. SCSI is also well
suited for large disk volumes, and is often used in file servers and other I/O
intensive systems.

Despite its superior flexibility and performance, SCSI has two main
difficulties that prevent it from being adopted as the standard interface for
PC's: a high price and a lack of standardization. A hard drive with a SCSI
interface may cost up to 30% more than the same drive mechanism with an IDE
interface. Since most systems do not ship standard with SCSI controllers, the
price of the adapter card and any associated cables must also be included in
the cost. Some SCSI devices come with a terminator that cannot be removed
(meaning the device must go on the end of the chain), and others may have a
"hard wired" ID that cannot be changed (meaning that no other device that uses
that ID can be attached to the same SCSI chain). Each device, in addition to
the SCSI adapter itself, must have its own driver. Although OS/2 ships with
drivers for most of the popular SCSI cards and SCSI CD-ROM's, newer SCSI
devices may not have OS/2 drivers available.  It is always a good idea to check
with the vendor of the SCSI device to verify that it is supported under OS/2
before making a purchase.

Troubleshooting problems related to SCSI drives is discussed in Section 4.3.3.


ΓòÉΓòÉΓòÉ 9.2.2. 5.2.2 IDE: Fast, cheap, and reliable ΓòÉΓòÉΓòÉ

5.2.2 IDE: Fast, cheap, and reliable

IDE (Integrated Drive Electronics) is the most popular interface for connecting
hard drives to PC's. There are two versions of the IDE specification in use
today. The original IDE specification was designed strictly for hard drives,
and allows for up to two hard drives to be attached to the system. One of the
drives is configured as a master, the other as a slave. Drives may have up to
1024 cylinders (503 Mb in capacity).

Note:  Most drive manufacturers use the equation 1Mb = 1,000,000 bytes in order
to artificially inflate the capacity of their drives for advertising purposes.
OS/2 correctly uses "1Mb" to refer to 1,048,576 bytes. Because of this, a 527Mb
hard drive according to the manufacturer's specifications will show up as being
503Mb in OS/2. This work always uses the equation 1Mb = 1,048,576 bytes when
referring to hard drive capacities.

In 1994 a new specification called Enhanced IDE (EIDE) was introduced to
address the limitations of the original specification. EIDE introduced the
following improvements to the original IDE specification:

o   A new EIDE system BIOS removes the 1024 cylinder limitation. IDE hard
    drives can now be up to 8Gb in size.

    Note:  Simply plugging an EIDE controller into a system without an EIDE
    BIOS will not resolve the sector limitation problem. Many large hard drives
    come with a utility called OnTrack Systems Disk Manager. Disk Manager
    essentially deceives the BIOS into thinking the drive has less than 1024
    cylinders. Disk Manager is incompatible with some earlier versions of "Red
    Box" Warp. If the part number for your Warp package is 83G8100 or 83G8102,
    or if your system came preloaded with Warp, then you will need to obtain
    and apply FixPak 9 (see Appendix A) to use Disk Manager. If your Warp
    package is part number 52H3800 or you are using Warp w/ WIN-OS/2 or any
    version of Warp Connect, then no update is necessary.

o   Up to two IDE controllers (a primary and secondary controller) can now
    reside in the system, allowing for up to four IDE devices.

o   IDE devices are no longer restricted to hard drives. Other IDE devices,
    such as CD-ROM drives, can now be attached to the IDE controller.

o   New performance enhancements such as PIO (programmed I/O) modes allow for
    greater data throughput. Newer enhanced IDE hard drives can typically
    outperform all but the highest end SCSI drives.

OS/2 has robust built in support for both IDE specifications. IDE hard drives
and CD-ROM drives will be automatically detected by OS/2 during installation.
The sector limitation problems of original IDE are discussed in more detail in
Sections 1 and 4 of this work.

Note:  Some Pentium motherboards use an onboard I/O controller known as the
RZ1000. If you suspect you have this controller on your motherboard, you should
obtain EIDE80.ZIP from the IBM PC Co. BBS (see Section 2.2.3). This file
contains a new OS/2 IDE driver (IBM1S506.ADD) that addresses potential problems
with this controller.

IDE is fast, inexpensive, and relatively reliable, which makes it the most
popular choice in most PC's. It is not nearly as flexible as SCSI, however, and
many of the new IDE devices such as IDE CD-ROM drives suffer from the same
configuration headaches that plague their SCSI counterparts. Nevertheless,
because of its low cost, IDE is still the best option for most users.


ΓòÉΓòÉΓòÉ 9.2.3. 5.2.3 Recommendations ΓòÉΓòÉΓòÉ

5.2.3 Recommendations

If you will be running a simple configuration (e.g. a single hard drive and
CD-ROM), and are more concerned with cost and ease of setup over performance,
IDE is probably the best choice. If you are looking for performance and
flexibility, and are willing to tolerate some initial setup hassles, choose
SCSI.

It is also possible to use both SCSI and IDE in the same system. If you are
using both IDE and SCSI hard drives, however, there are two special
considerations:

1.  IDE drives will be mapped before any SCSI drives.

2.  You must make sure the SCSI driver in the OS/2 CONFIG.SYS (the name of this
    driver will depend on which SCSI adapter you have) loads after the IDE
    driver (IBM1S506.ADD). Otherwise drives may be mapped in an inconsistent
    manner.


ΓòÉΓòÉΓòÉ 9.3. 5.3 BIOS Considerations ΓòÉΓòÉΓòÉ

5.3 BIOS Considerations

All IBM and compatible PC's have a special type of ROM called BIOS, or Basic
Input/Output System. The BIOS is a set of programs built into ROM that give the
computer enough built in intelligence to boot up. For example, when you first
turn on your computer, it may seem to sit idle for a few seconds, access all of
your disk drives, and then count up memory before it starts up. It is actually
running a program contained in BIOS called the POST. POST, or
Power-On-Self-Test, tests the various hardware components of your computer each
time the system is powered up. Adapter cards may also include their own BIOS.
Some OS/2 hardware compatibility problems are occasionally caused by the
system's BIOS. If your BIOS does not work correctly with OS/2 you may need to
update or replace it. In older systems, the BIOS is typically contained in a
ROM chip that is socketed on the motherboard. Replacing the BIOS involves
physically replacing this chip on the motherboard.

Newer systems use a newer type of BIOS called FLASH BIOS. Instead of being
stored on a ROM chip, the BIOS code is stored in a special type of non-volatile
RAM called FLASH memory. Replacing the BIOS involves booting from a special
diskette and updating the contents of FLASH memory with the new BIOS (This is
sometimes called "flashing" the system).


ΓòÉΓòÉΓòÉ 9.4. 5.4 Memory Considerations ΓòÉΓòÉΓòÉ

5.4 Memory Considerations

There are three main types of RAM memory currently used in modern PC's. Some
are better suited for use with OS/2. Most modern PC's use SIMM's (Single
In-line Memory Modules). OS/2 is extremely sensitive to defective or marginal
memory, and will often detect errors that hardware diagnostic programs will
miss. When adding memory to your PC, keep the following in mind:

o   All SIMM's must be of the same speed, type, and brand. Memory speed is
    measured in nanoseconds, or "ns." You cannot, for example, mix 70ns SIMM's
    with 80ns SIMM's, even if the system board supposedly supports this
    configuration. SIMM's may also be available in different types. 1Mb SIMM's,
    for example, may be available in either a 1X3 or 1X9 configuration. The 1X3
    configuration has 3 chips mounted on the SIMM, whereas the 1X9 has 9 chips.
    You should not mix these two types in the same system. Finally, to avoid
    problems caused by subtle timing differences between different brands, you
    should try to use SIMM's of the same brand.

o   Some SIMM's have connectors that are made of a tin-lead alloy. Others have
    gold connectors. Either will work with OS/2 as long as the memory socket on
    the motherboard is the same type as the SIMM itself. If tin-lead SIMM's are
    plugged into a socket with gold connectors (or vice versa), the metals will
    react, causing corrosion and eventual system board failure.

o   Using substandard memory on an OS/2 system will eventually cause a system
    crash (probably a trap 0002). Hardware diagnostics may not detect the
    problem.

Different types of memory are available with various levels of error detection.
The three most popular varieties are Parity, ECC, and Non-Parity memory. Only
the first two are recommended for use with OS/2.

o   Parity Memory. Parity memory is the standard type of memory used for most
    PC's. Parity memory includes an extra bit known as a parity bit for every
    byte of memory. The parity bit is set such that the total number of "on"
    bits in every byte is either even (even parity), or odd (odd parity). If an
    error occurs in memory and one of the bits changes unexpectedly, the
    hardware detects a parity error and halts the system before the corrupted
    data can be written to the hard drive. Because OS/2 is so memory intensive,
    parity or ECC memory (see below) should always be used with a system that
    runs OS/2.

o   ECC Memory. ECC, or Error Checking and Correcting memory, is an expensive
    type of memory that used primarily in mission critical systems. ECC memory
    not only detects errors in memory, but can even correct them if the error
    is not too severe. ECC Memory is recommended for mission critical systems
    and file servers.

o   Non-Parity Memory. Non-parity memory is becoming increasingly popular in
    low end systems. Non-parity memory has no error checking, so if an error
    occurs in memory, data corruption will inevitably result. For this reason,
    non-parity memory is not recommended for use in any business oriented
    system. Before purchasing a PC, check to make sure that it supports at
    least parity memory.

Some newer systems are beginning to use a newer high speed type of memory known
as EDO (Extended Data Out) memory. EDO memory is available both in parity and
non-parity SIMM's. When running OS/2, use the parity type.


ΓòÉΓòÉΓòÉ 9.5. 5.5 Using the PCM Table to determine hardware compatibility with OS/2 ΓòÉΓòÉΓòÉ

5.5 Using the PCM Table to determine hardware compatibility with OS/2

If you own equipment, or are considering purchasing new equipment, and want to
insure that OS/2 will work with it, then you should obtain the PCM (Personal
Computer Manufacturer) Table. The PCM table lists systems and hardware devices
that have been tested and verified to work with OS/2. Also included is
information on where the driver for the device is available from, and any
limitations when using the device under OS/2. This table is updated frequently
as new hardware is announced, so make sure you are using the latest version.
The PCM table lists information on the following components:

o   IBM and Non-IBM Systems and NoteBooks

o   Motherboard /Processor Upgrades

o   Display Adapters

o   Disk and SCSI Adapters

o   CD-ROM drives

o   Miscellaneous Storage Devices

o   Keyboards

o   Digitizers

o   Mice and Trackballs

o   Joysticks

o   Scanners

o   Multimedia Adapters

o   Wireless

o   PCMCIA

o   Printers and Plotters

o   LAN Adapters

o   Tape Drives

Note that the IBM PC Co. and PSP only supports OS/2 with systems and components
that appear on this list. Support for other systems (e.g. home-built "clone"
systems) is provided on a best effort basis.

The PCM table is available from a variety of sources, including the IBM PC Co.
BBS (see Section 2.2.3). The file name is usually PCMTABLE.ZIP. You can also
find an HTML version of this list on the World Wide Web at:

http://www.austin.ibm.com/pspinfo/os2hw.html


ΓòÉΓòÉΓòÉ 10. Section 6. The CONFIG.SYS Chapter ΓòÉΓòÉΓòÉ

SECTION 6: THE CONFIG.SYS CHAPTER

If you encounter a problem with OS/2 during startup, the problem is often with
the CONFIG.SYS. This section dissects a sample OS/2 CONFIG.SYS line by line.
Note that some of the statements in your CONFIG.SYS may be different than what
is shown here. You will probably have statements in your CONFIG.SYS which do
not appear here, and you may see some statements here which do not appear in
your CONFIG.SYS.


ΓòÉΓòÉΓòÉ 10.1. 6.1 The CONFIG.SYS: A line by line explanation ΓòÉΓòÉΓòÉ

6.1 The CONFIG.SYS: A line by line explanation

IFS=C:\OS2\HPFS.IFS /CACHE:512 /CRECL:4 /AUTOCHECK:CD

The IFS line is used to install HPFS or other file system support, such as
CDIFS for CD-ROM's. The parameters below are for HPFS.IFS and may not be
applicable to other IFS's.

o   /CACHE: sets the cache size. Some caution is necessary when tuning the
    cache. More is not always better, especially on a memory constrained
    system. The best advice is to experiment, but not to stray too far from the
    defaults. The maximum cache for HPFS is 2048Kb.

o   /CRECL: sets the cacheable record size (in multiples of 2K).

o   /AUTOCHECK: is used to enable AUTOCHECK for the specified drives. AUTOCHECK
    causes OS/2 to automatically run CHKDSK during startup on the specified
    drive is OS/2 was shut down improperly.

RUN=C:\OS2\CACHE.EXE /LAZY:ON /MAXAGE:5000 /DISKIDLE:6000 /BUFFERIDLE:2000

CACHE.EXE is used in conjunction with the HPFS statement to tune performance.
If omitted, the default values will be used.

o   /LAZY: enables or disables lazy write. Lazy write enables OS/2 to defer
    writing data in the cache to the disk until the disk is idle. This can
    increase the performance of applications that make frequent disk writes.

o   /MAXAGE: specifies the amount of time (in milliseconds) that data remain in
    the cache before it is written to the hard drive.

o   /DISKIDLE: specifies the amount of time (in milliseconds) that a disk must
    remain idle before the contents of the cache are written to the hard drive.

o   /BUFFERIDLE: specifies the amount of time (in milliseconds) that a cache
    buffer can remain idle before its contents are written to the hard drive.

PROTSHELL=C:\OS2\PMSHELL.EXE

PROTSHELL determines the user interface for OS/2. The default choice,
PMSHELL.EXE, initializes Presentation Manager and starts the execution of
STARTUP.CMD. If you replaced PMSHELL with CMD.EXE, the system would start up to
a command line. (This is essentially what using "C" from the Recovery Choices
menu does).

SET USER_INI=C:\OS2\OS2.INI

USER_INI is an environment variable used to set the name of the "user" .INI
file (Discussed in Section 3.7). This will normally be OS2.INI.

SET SYSTEM_INI=C:\OS2\OS2SYS.INI

SYSTEM_INI is an environment variable used to set the name of the "system" .INI
file (Discussed in Section 3.7). This will normally be OS2SYS.INI.

SET OS2_SHELL=C:\OS2\CMD.EXE

OS2_SHELL is an environment variable used to specify the OS/2 command
interpreter. This will normally be CMD.EXE, though there are third-party
replacements available.

SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD

AUTOSTART is an environment variable used to determine what items start
automatically when the system is restarted

o   PROGRAMS automatically starts programs that were running at shutdown.

o   TASKLIST enables the use of the Window list to switch between running
    applications.

o   FOLDERS starts up the Desktop folder.

    Note:  Do not remove FOLDERS, or your Desktop will not appear.

o   CONNECTIONS tries to restart network connections that were active at shut
    down. You should probably remove this to avoid problems.

o   LAUNCHPAD enables the LaunchPad on the OS/2 Desktop.

SET RESTARTOBJECTS=STARTUPFOLDERSONLY

RESTARTOBJECTS is an environment variable which can be used to determine which
objects are automatically started when the system restarts. RESTARTOBJECTS is a
more precise way of controlling this behavior than using PROGRAMS in SET
AUTOSTART. RESTARTOBJECTS overrides PROGRAMS in the SET AUTOSTART statement.

o   STARTUPFOLDERSONLY starts up only objects that are in the Startup folder in
    the OS/2 System folder.

o   REBOOTONLY Restarts objects that were running at system shut down only if
    the system is restarted by [Ctrl]+[Alt]+[Del].

o   YES or NO corresponds to the presence of PROGRAMS in the SET AUTOSTART
    statement.

SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE

RUNWORKPLACE is an environment variable used to specify the program used as the
primary interface to the WorkPlace Shell. Normally, this will be the same as
PROTSHELL. If invoked using SET RUNWORKPLACE, PMSHELL.EXE will start the OS/2
Desktop. You could set RUNWORKPLACE to use another Presentation Manager program
(such as FM/2) as the primary interface. If you do this, you will be limited to
performing only system functions (such as starting other programs, file
management functions, etc.) that are provided by that application.

SET COMSPEC=C:\OS2\CMD.EXE

COMSPEC is an environment variable used by some older applications to determine
the name and location of the OS/2 command line processor. If you changed your
OS2_SHELL statement to use an alternate command processor, you should update
COMSPEC accordingly.

LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;d:\...

The LIBPATH statement sets search path for .DLL files. By default, OS/2 does
NOT search the current directory, but the ".;" entry can be used to force a
search of the current directory.

Note that LIBPATH is not an environment variable, and therefore cannot be
changed while the system is running by issuing a SET command. You can, however,
use the BEGINLIBPATH and ENDLIBPATH environment variables to append new entries
to the beginning and end of the existing LIBPATH defined in the CONFIG.SYS. The
existing LIBPATH itself cannot be modified. LIBPATH can be optimized by placing
the most often used directories first.

SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\...

The PATH environment variable specifies the search path OS/2 uses to find
executable files. PATH is identical to its DOS counterpart in the AUTOEXEC.BAT,
and can be similarly optimized by placing the most often used directories first
in the path.

SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\...

The DPATH environment variable specifies the search path for applications' data
files. The application must be written to use DPATH for this to work.

SET PROMPT=$e[1;31mProtect Mode$e[33m$_$d$_$t$_$e[32m$i[$p]

The PROMPT environment variable determines the appearance of the command
prompt. See the OS/2 Command Reference for more information. The example above
produces the following prompt:

PROTECT MODE
Fri 11-24-1995
12:41:09.07
[D:\]

SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;
SET GLOSSARY=C:\OS2\HELP\GLOSS;

These two environment variables set the search locations for the Help and
Glossary files, respectively.

Note that all HELP files located in HELP search path are merged into the Master
Help Index in the Information Folder.

SET IPF_KEYS=SBCS+OPSYS

The IPF_KEYS environment variable is used as a sort of "password" to limit
access to information in HLP or on-line books (.INF files). Code placed in the
.INF file limits access to those who have the right "key" specified on the
IPF_KEYS statement. Multiple keys can be placed on this line, and are separated
by the plus "+" symbol.

PRIORITY_DISK_IO=YES

PRIORITY_DISK_IO allows the foreground application to receive disk I/O
priority. This may improve the performance of the foreground application at the
expense of decreasing performance for background applications.

FILES=20

FILES= is applicable to DOS sessions only, and specifies the maximum number of
files which a DOS session can have open. This statement sets the global default
value for all DOS sessions. The setting can be customized for each individual
DOS session by changing the DOS_FILES setting for the session (see Appendix C).

BASEDEV=IBMKBD.SYS

This statement provides extended keyboard device support, and works in
conjunction with KBDBASE.SYS.

DEVICE=C:\OS2\BOOT\TESTCFG.SYS

TESTCFG.SYS is used to detect system hardware configuration during
installation, and must be present in order for Selective Install to run.

DEVICE=C:\OS2\BOOT\DOS.SYS

DOS.SYS allows DOS programs to be launched from the desktop.

DEVICE=C:\OS2\BOOT\PMDD.SYS

PMDD.SYS is a device driver used by Presentation Manager.

DEVICE=D:\OS2\BOOT\APM.SYS

APM.SYS enables Advanced Power Management support for the OS/2 environment. The
system must have APM features for this to work.

DEVICE=D:\OS2\MDOS\VAPM.SYS

VAPM.SYS is the virtual APM driver for the DOS environment.

BUFFERS=90

BUFFERS specifies the number of disk buffers (a sort of mini disk cache) used
by OS/2. Each buffer requires 512 Bytes of RAM, and can hold 1 disk sector of
information. You can optimize this for performance, but again, do not stray too
far from the defaults. The maximum value is 255.

IOPL=YES

Allows I/O Privilege Level (Ring 2) access to be granted to all programs which
require it. You could also specify a list of executable programs instead of
YES. In this case, only the programs on the list get IOPL privilege.

Note:  The FaxWorks installation program that comes with the Bonus Pack changes
the IOPL line to read IOPL=FXPRINT.EXE. This gives FXPRINT.EXE exclusive access
to IOPL, which can cause other applications that need IOPL to fail. If you have
installed FaxWorks on your system, find the IOPL line and change it to read
IOPL=YES.

DISKCACHE=D,LW,AC:C

DISKCACHE specifies the cache parameters for FAT volumes. DISKCACHE is not
needed if all drive volumes are HPFS.

o   D defines the amount of memory in Kb allocated to the FAT file system
    cache. D is a default value determined by the amount of installed RAM at
    installation. You can replace D with a number representing the new size of
    the cache if you wish to change it. Some caution is necessary when tuning
    the cache. More is not always better, especially on a memory constrained
    system. As with HPFS, the best advice is to experiment, but not to stray
    too far from the defaults.

o   LW enables lazy write caching for FAT volumes. This can increase the
    performance of applications that make frequent disk writes.

o   AC: specifies which drives are to be checked using CHKDSK in the event of
    an improper shut down.

MAXWAIT=3

Specifies the maximum time (in seconds) a process must wait without obtaining
CPU time before OS/2 will temporarily boost its priority. This value can range
for 1 to 255. The lower the value, the greater the system overhead. Lowering
this value will increase the performance of background processes at the expense
of decreasing performance for the application running in the foreground.

MEMMAN=SWAP,PROTECT,COMMIT,NOMOVE

MEMMAN specifies various memory management tuning parameters.

o   SWAP or NOSWAP enables/disables disk swapping.

    Note:  Some systems will be unstable if NOSWAP is chosen, even if the
    system appears to have enough memory not to need a swap file. For this
    reason, you should probably leave swapping enabled even if you think you
    will not need it. You can use the SWAPPATH statement to tune the initial
    size of the SWAPPER.DAT file itself.

o   PROTECT allows certain DLL API's to allocate protected memory.

o   COMMIT (optional) forces allocation of all memory required by each
    application to the swapper file. If the hard drive runs out of swap space,
    the application will display an "out of memory" message.

o   MOVE or NOMOVE (optional) is provided for compatibility with certain OS/2
    1.x applications which check for its presence. This parameter is ignored by
    OS/2 Warp.

SWAPPATH=C:\OS2\SYSTEM 2048 20480

SWAPPATH defines the location to be used for the SWAPPER.DAT file. The swap
file should usually be placed in the root directory of the least used physical
hard drive for best performance. The SWAPPER.DAT grows and shrinks as necessary
depending on the system's memory requirements at any given time.

o   The first number (2048) determines the amount of "headroom" (in Kb) on the
    drive (2Mb in this case). If the SWAPPER.DAT grows such that less than this
    amount of space is left free on the drive, a warning message will be
    displayed.

o   The second number (20480) determines the initial size (in Kb) of
    SWAPPER.DAT (20Mb in this case). Preallocating disk space for SWAPPER.DAT
    reduces time required for swapping, and avoids fragmentation of the swap
    file. If you typically have a large swap file while running OS/2, you may
    wish to set this number to match the size of your normal SWAPPER.DAT as
    closely as possible.

The swap file is always recreated during startup.

BREAK=OFF

Specifies when the system will check for a Ctrl-Break signal.

o   OFF checks for Ctrl-Break only when standard I/O is performed and provides
    better system performance.

o   ON checks for Ctrl-Break continuously and provides quicker response to the
    Ctrl-Break request at the expense of slower overall system performance.

THREADS=256

Specifies the maximum number of threads that can run simultaneously under OS/2.
256 is the default. You may wish to decrease this to 128 in memory constrained
(8MB or less) environments. The maximum is 4095.

Note:  Each thread requires 4Kb of overhead which is allocated at system
startup. This memory cannot be swapped to the hard drive. Because of this, you
should probably try to reduce THREADS as much as possible. Even "overloaded"
systems will typically never need any more than 512 threads.

PRINTMONBUFSIZE=134,134,134

PRINTMONBUFSIZE determines the buffer size for parallel printer ports. 134
bytes is the minimum and default. The maximum is 2048 bytes.

COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS

Specifies country code and identifies the file containing country information.
Most errors on startup that reference this line have little to do with
COUNTRY.SYS. See Section 4.3.1 for more information on "COUNTRY.SYS" errors at
startup.

SET KEYS=ON

KEYS enables or disables command line history for OS/2 command line sessions.
Setting KEYS=ON is the equivalent of loading DOSKEY in the AUTOEXEC.BAT under
DOS.

SET BOOKSHELF=C:\OS2\BOOK;D:\DOSMEM\;

The BOOKSHELF environment variable sets the locations that OS/2 searches for
on-line books. Each specified path is a "Library" for searches in on-line
documentation.

SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;...C:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=C:\OS2\ETC\DSOM

These environment variables specify directories used by the SOM (System Object
Model) libraries. SOM is used extensively by the WorkPlace Shell.

REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;

The DELDIR environment variable specifies the location of the "holding area"
for deleted files so they can be undeleted. A directory for deleted files is
created on each desired logical drive. The number after the path specifies the
maximum total size of files stored in this directory. Older files are
permanently deleted to make room for new deletions.

DELDIR (and hence UNDELETE) is not enabled by default. You  must un-REM this
line and reboot to activate undelete support. Note that undelete only works
with files deleted from the command line (not from the shredder).

BASEDEV=PRINT01.SYS    ;Parallel port driver
BASEDEV=IBM1FLPY.ADD   ;Floppy drive driver for Microchannel systems
BASEDEV=IBM1S506.ADD   ;IDE device driver
BASEDEV=IBMIDECD.FLT   ;Filter for IDE CD-ROM drives
BASEDEV=OS2DASD.DMD    ;Generic Device Manager for hard drives
BASEDEV=XDFLOPPY.FLT   ;XDF format filter for reading OS/2 installation diskettes

BASEDEV statements load base system device drivers. BASEDEV's are different
from DEVICE statements, as they load before the IFS statement is processed, and
thus cannot contain path information. The root directory is searched first,
then the \OS2 and OS2\BOOT\ directories are searched. The following extensions
may appear on BASEDEV's, and are loaded in the following order regardless of
their order in the CONFIG.SYS: SYS, BID, VSD, TSD, ADD, I13, FLT, and DMD.

BASEDEV=IBMINT13.I13

You may be able to use IBMINT13.I13 if no driver is available for your hard
drive controller. IBMINT13 only supports hard drives when used with SCSI
controllers; CD-ROM's will not be usable. IBMINT13 is a "no frills" driver, so
performance will typically be slow. Note that IBMINT13 will override any other
hard drive controller driver in the CONFIG.SYS. If you have a driver for your
adapter and IBMINT13 is present, remove it. Otherwise a conflict may occur,
resulting in a system crash.

DEVICE=C:\OS2\COM.SYS (3,3E8, 5)

COM.SYS provides generic COM device support. COM1 and COM2 are supported
directly. COM3 and COM4 require parameters to enable the port. In the example
above, the 3 determines the COM port number (in this case COM3). The 3E8
specifies the I/O port address of the COM port, and the 5 specifies the IRQ
level. COM.SYS works in conjunction with the PCMCIA modem client enabler
AUTODRV2.SYS if PCMCIA support is installed.

SET EPMPATH=D:\UTILITY\EPM;D:\UTILITY\EBOOKIE2;

The EPMPATH environment variable sets the data and file path for the Enhanced
Editor (EPM). Do not use EPM editor to edit the CONFIG.SYS, as it truncates
lines longer than 255 characters.

PROTECTONLY=NO

Setting PROTECTONLY to NO allows DOS and WIN-OS/2 sessions to run under OS/2.

SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /P

SHELL specifies the DOS command processor for DOS sessions.

o   The second parameter is the path from which the command processor is
    reloaded. This should usually match the path of the command processor
    itself.

o   /P indicates that the command processor should remain resident in memory
    when an application is run.

FCBS=16,8

FCBS specifies File Control Blocks. This statement is provided for
compatibility with very early versions of DOS.

RMSIZE=640

RMSIZE specifies maximum amount of conventional memory available for DOS
sessions. This statement sets the global defaults for all DOS sessions, and can
be manually overridden on an individual basis by changing the DOS_RMSIZE
setting for each DOS session. 640Kb is both the maximum and default.

DOS=LOW,NOUMB

The DOS statement specifies whether or not DOS can use the High Memory Area
(HMA) and Upper Memory Blocks (UMB). This statement works the same as its real
DOS counterpart.

o   HIGH or LOW determines whether DOS will load its kernel into the HMA.

o   UMB or NOUMB determines whether DOS can control UMB's.

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

VEMM.SYS is the virtual expanded memory (EMS) driver, for DOS sessions. This
driver is analagous to the EMM386 driver in real DOS.

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

VMOUSE.SYS is the virtual mouse driver for DOS sessions. VMOUSE.SYS is the
equivalent of MOUSE.COM in real DOS.

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

VDPX.SYS is the virtual DOS protect mode extender, and provides address
translation between the virtual 86 (used by DOS sessions) and Protected modes
(used by OS/2) of the microprocessor. VDPX.SYS is used by DPMI applications.

DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB

VXMS.SYS provides extended memory (XMS) support for DOS sessions. It is
analagous to the HIMEM.SYS driver in real DOS.

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

VDPMI.SYS allows DOS sessions to use DPMI (DOS Protect Mode Interface) memory.

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

VCOM.SYS is the virtual COM port driver for DOS.

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

VVGA.SYS allows DOS applications to use VGA video modes.

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

VSVGA.SYS allows DOS applications to use Super VGA video modes on supported
adapters.

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

VXGA.SYS allows DOS applications to use XGA video modes on supported adapters.

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

VWIN.SYS is the seamless WIN-OS/2 driver. VWIN.SYS works closely with the video
device driver to coordinate drawing WIN-OS/2 seamless windows on the OS/2
desktop.

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

VW32S provides Win32s API compatibility up to version 1.15. Note that you will
still need to install the Win32s runtime library itself for win32s applications
to work. This is sometimes, but not always, included with the application.

BASEDEV=PCMCIA.SYS                ;Card Services
BASEDEV=IBM2SS01.SYS              ;Socket Services (This line may vary)
DEVICE=C:\OS2\BOOT\$ICPMOS2.SYS   ;Suspend/Resume driver for PCMCIA
;(The following lines are generic  client enablers provided with OS/2)
DEVICE=C:\OS2\BOOT\AUTODRV2.SYS C:\OS2\AUTODRV2.INI  ; modem card
BASEDEV=PCM2ATA.SYS               ;ATA hard drive card
DEVICE=C:\THINKPAD\ICMEMMTD.SYS   ;(or ICMEMCDD.SYS) FLASH memory card

The lines above are for PCMCIA device support in OS/2. PCMCIA support is
discussed in Section 5.1.

DEVICE=C:\OS2\XGARING0.SYS

XGARING0 is the Ring 0 device driver for XGA.

DEVINFO=SCR,XGA,C:\OS2\VIOTBL.DCP

This line specifies code page for full screen and VIO fonts for XGA systems.

SET VIDEO_DEVICES=VIO_XGA
SET VIO_XGA=DEVICE(BVHVGA,BVHXGA)

This line sets display environment variables for XGA systems.

DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP

This line specifies code page for full screen and VIO fonts for VGA systems.

SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA)

This line sets display environment variables for VGA systems.

DEVINFO=SCR,SVGA,C:\OS2\VIOTBL.DCP

This line specifies code page for full screen and VIO fonts for SVGA systems.

SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)

This line sets display environment variables for SVGA systems.

DEVICE=C:\OS2\POINTDD.SYS

POINTDD.SYS is a driver that provides pointer drawing support.

DEVICE=C:\OS2\BOOT\MOUSE.SYS SERIAL=COM1

MOUSE.SYS is a mouse specific driver for PS/2 and Microsoft compatible mice.
Some mice may require additional hardware specific drivers.

o   TYPE parameter is required for certain brands of mice.

o   SERIAL parameter is required for serial mice.

CODEPAGE=437,850

CODEPAGE specifies the primary and alternate code pages for OS/2.

DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP

DEVINFO specifies the keyboard codepage and provides keyboard translation.

IFS=C:\OS2\BOOT\CDFS.IFS /Q /C:4

CDIFS is the installable file system for CD-ROM drives. This statement should
always be present for CD-ROM support.

DEVICE=C:\OS2\BOOT\OS2CDROM.DMD /Q

OS2CDROM.DMD is the generic CD-ROM device manager. This statement should always
be present for CD-ROM support.

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

VCDROM.SYS is the virtual CD-ROM driver for DOS sessions

SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=C:\MMOS2\SSMDD.SYS
DEVICE=C:\MMOS2\R0STUB.SYS

The above lines are for MMPM/2 (Multimedia Presentation Manager/2) base
support.

VME=NO

This line disables the Virtual Mode Extensions of 80486 and above processors.
These extensions are used in conjunction with virtual 86 mode when running DOS
and WIN-OS/2 sessions, and have been known to cause stability problems.
Disabling the extensions does not effect the performance or functionality of
the operating system, but may increase the stability of DOS and WIN-OS/2
applications.


ΓòÉΓòÉΓòÉ 10.2. 6.2 Where are my backups? ΓòÉΓòÉΓòÉ

6.2 Where are my backups?

Sometimes it is difficult to tell where the problem lies in the CONFIG.SYS. If
the CONFIG.SYS is missing or irreparable, you may be able to find a backup copy
in any of the following locations. Copy one of them to the root directory
(after backing up your existing copy) and then restart the system. At the very
least, this should allow you to determine whether or not the problem is indeed
in the CONFIG.SYS.

o   The root directory of your OS/2 boot partition. Many applications make
    backup copies of the CONFIG.SYS during installation and label them
    CONFIG.001, CONFIG.BAK, or something similar.

o   The \OS2\ARCHIVES\* directories. The filename will usually be "2." Try
    copying back a CONFIG.SYS from the most archive you have that works.

o   The \OS2\INSTALL directory. This is the original CONFIG.SYS created during
    installation. If you suspect your problem is in the CONFIG.SYS but do not
    know for certain, then try using this one.


ΓòÉΓòÉΓòÉ 11. Appendix A. Corrective Service Updates ΓòÉΓòÉΓòÉ

APPENDIX A. CORRECTIVE SERVICE UPDATES

OS/2 is constantly being updated by IBM development to fix reported problems,
add support for new hardware devices, and improve performance. These updates
are usually distributed in the form of FixPaks. FixPaks are usually designed to
address specific reported problems (APARS), and are often made available on an
individual basis to customers who report the problems addressed in the FixPak
to technical support. Some FixPaks, however, are made widely available.

There are reasons restricting the availability of FixPaks. They are not tested
as rigorously as new releases of OS/2, and because of this may fix some
problems and introduce others. Often after several FixPaks are introduced and
tested extensively, they are rolled into a cumulative service pack and made
available to the public. Service packs may also include additional drivers for
new hardware devices that have been introduced since the operating system was
initially released. Service Packs and FixPaks are often collectively referred
to as CSD's (Corrective Service Diskettes).  CSD's usually do not add new
features to the operating system, though they may include performance
enhancements.

When doing OS/2 problem determination, it is very important to know which
version of OS/2 you are using and whether a FixPak or service pack has been
applied. If you are unsure of this, there are two ways to find out. If you are
unsure of what version of OS/2 you are using (Warp vs. Warp Connect, etc.), you
can use the SYSLEVEL command to find out. To run SYSLEVEL, open an OS/2 Window
or full screen command prompt session and type the following command:

SYSLEVEL

This will present several screens of information about various OS/2 components.
The information you are interested in is the OS/2 Base Operating System current
CSD level. This number is highlighted in the following example.

Figure A-1: SYSLEVEL Output

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéD:\OS2\INSTALL\SYSLEVEL.GRE                                             Γöé
Γöé                           IBM OS/2 32-bit Graphics Engine              Γöé
ΓöéVersion 3.00     Component ID 562274700                                 Γöé
ΓöéType 0C                                                                 Γöé
ΓöéCurrent CSD level: XR03003                                              Γöé
ΓöéPrior   CSD level: XR03003                                              Γöé
ΓöéD:\OS2\INSTALL\SYSLEVEL.OS2                                             Γöé
Γöé                           IBM OS/2 Base Operating System               Γöé
ΓöéVersion 3.00     Component ID 562274700                                 Γöé
ΓöéType 0C                                                                 Γöé
ΓöéCurrent CSD level: XR03003                                              Γöé
ΓöéPrior   CSD level: XR03003                                              Γöé
Γöé------------------------------------------------------------------------Γöé
ΓöéPress Enter (<--) to display next page.                                 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

Table A-1 shows the CSD levels for all releases of OS/2 and service packs since
2.0. If you have applied a service pack (not a FixPak), the CSD level will be
changed. FixPaks generally do not change the CSD level, so they are  more
difficult to detect. One method of detecting FixPaks is to check the internal
revision level.  To do this, use the ver / r command at an OS/2 command prompt.
The following example illustrates this:

[D:\]ver /r
The Operating System/2 Version is 3.00
Revision 8.236

Compare the revision level obtained from ver /r with that listed in Table A-1
for your version of OS/2. If the number is different than  that presented in
Table A-1, then a FixPak or service pack has been applied. In the example
above, the revision level is 8.236, indicating a FixPak has been applied (in
this case FixPak 12).

Table A-1: OS/2 Service Levels

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéOS/2 Version                            ΓöéInternal Revision LevelΓöéCSD Level Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.00                                    Γöé6.307                  ΓöéXR02000   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.00.1 (Preloaded on IBM Systems)       Γöé6.427                  ΓöéXR02005   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.00.x with ServicePak XR06055 applied  Γöé6.466                  ΓöéXR06055   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.00.x with ServicePak XR06100 applied  Γöé6.543                  ΓöéXR06100   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.1                                     Γöé6.514                  ΓöéXR02010   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.1 for Windows                         Γöé6.514                  ΓöéXR02011   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.11 or 2.1 with ServicePak XR06200     Γöé6.617                  ΓöéXR06200   Γöé
Γöéapplied                                 Γöé                       Γöé          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé2.1 for Windows with ServicePak XR06300 Γöé6.624                  ΓöéXR06300   Γöé
Γöéapplied                                 Γöé                       Γöé          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3.00 Warp (Red Box)                     Γöé8.162                  ΓöéXR03000   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3.00 Warp (Blue Box)                    Γöé8.200                  ΓöéXR03001   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3.00 Warp Connect (Red Box)             Γöé8.200                  ΓöéXR03002   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3.00 Warp Connect (Blue Box)            Γöé8.200                  ΓöéXR03003   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé3.00 Warp (Red Box) Aptiva preload*     Γöé8.200                  ΓöéXR03005   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

As discussed in section 1.4, you should avoid applying FixPaks or service packs
unless absolutely necessary. In many cases, if you selectively reinstall a
component, you must reapply the FixPak or service pack.

You can obtain public FixPaks either from PSP at 1-800-992-4777 or from the IBM
PC Co. BBS at [phone]. If you have internet access, the PC Co. BBS files
are available via anonymous ftp at ftp.pcco.ibm.com.

Note:  Sometimes restricted access CSD's are illegally posted to various
internet sites. If you download and apply these FixPaks, IBM technical support
may refuse to assist you until the OS/2 is reinstalled without the FixPak. To
avoid this problem, always obtain FixPaks from official IBM sources, such as
those listed above.


ΓòÉΓòÉΓòÉ 11.1. A.1 General CSD installation tips ΓòÉΓòÉΓòÉ

A.1 General CSD installation tips

The following tips should help you avoid problems should you need to install a
CSD.

o   Read all instructions carefully. There will typically be one or more README
    files located on diskette 1 of the CSD's.

o   Never attempt to apply a FixPak or service pack over an OS/2 configuration
    that does not boot properly, or one that has a corrupt desktop. Doing so
    will usually result in a non-functioning system from which the only
    recovery is to reformat the hard drive and reinstall both the operating
    system and the CSD.

o   Most CSD's require a set of 2 Corrective Service Facility Boot diskettes
    ("kicker" diskettes) that contain the installation programs for the CSD.
    These disks are the same for most CSD's, but may not be supplied with the
    CSD's themselves. You should be able to obtain the kicker diskettes from
    the same source as the CSD itself.

o   When installing a CSD, you typically run a:\service.exe from an OS/2
    command prompt. A list will appear at some point listing the various
    installed products on your hard drive that can be updated by the CSD. If
    you have another copy of OS/2 installed in a different partition, the CSD
    will find it and update it if you select it from this list. You will also
    be required to furnish a path for archiving your existing files before they
    are updated. You cannot override this feature. Check the README.1ST file on
    the first CSD diskette (NOT on the kicker diskettes) for space requirements
    for the archived files.

o   Often the CSD installation program (known as Corrective Service Facility,
    or CSF) will find files that it is unable to update because the files are
    currently in use by the operating system. You will be given a choice
    between rebooting from the kicker diskettes to install or letting CSF defer
    updating the files until the machine is shut down and rebooted. If you
    choose to let CSF defer service until a reboot, it will copy the files to a
    temporary location. When the system is restarted, the files are copied to
    the correct location, and the system reboots itself again before the
    desktop appears. Sometimes you will encounter hangs while CSF copies the
    files from diskette in the first step. If this happens, re-apply the CSD
    from scratch, and choose to reboot from the kicker diskettes when prompted.


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

Some Aptiva systems come with a version of OS/2 which uses special hardware
features of the Aptiva to allow OS/2 to temporarily reboot to DOS when running
DOS or Windows Games (This is called the "Trap Door" feature). SYSLEVEL will
show this version of OS/2 as CSD level XR03005, type WP. This version of OS/2
is not supported on non-Aptiva Systems.


ΓòÉΓòÉΓòÉ 12. Appendix B. The OS/2 Warp Product Family ΓòÉΓòÉΓòÉ

APPENDIX B. THE OS/2 WARP PRODUCT FAMILY

Although Warp is the current version of OS/2, many people are still using
previous versions. If you are using an older version of OS/2, this may
determine which version of Warp you should purchase as an upgrade, should you
decide to do so.


ΓòÉΓòÉΓòÉ 12.1. B.1 OS/2 2.x Product Family ΓòÉΓòÉΓòÉ

B.1 OS/2 2.x Product Family

Note:  OS/2 2.1x has been officially withdrawn from marketing as of September
30, 1995. Technical support for OS/2 2.1 and 2.11 will end in February of 1996.
If you are still using OS/2 2.1, you should consider upgrading to the
appropriate Warp product.


ΓòÉΓòÉΓòÉ 12.1.1. B.1.1 OS/2 2.0 ΓòÉΓòÉΓòÉ

B.1.1 OS/2 2.0

OS/2 2.0 was the first 32-bit version of the operating system, and introduced
many of the features present in Warp (WorkPlace shell, WIN-OS/2, etc.).
WIN-OS/2 code is based on Windows 3.0. OS/2 2.0 has been discontinued for some
time and is no longer supported by IBM. If you upgrade your OS/2 2.0 system to
Warp, you should format the installation drive during installation to avoid
problems.


ΓòÉΓòÉΓòÉ 12.1.2. B.1.2 OS/2 2.1 and 2.11 ΓòÉΓòÉΓòÉ

B.1.2 OS/2 2.1 and 2.11

Many people are still using OS/2 2.11. OS/2 2.11 is a manufacturing refresh of
OS/2 2.1 that incorporates Service Pack XR06200 (See Appendix A) into the base
operating system. If you are still using OS/2 2.1, you should obtain and
install the Service Pack before contacting IBM for technical support. OS/2 2.1
and 2.11 can be upgraded using either Blue Box Warp or Blue Box Warp Connect.


ΓòÉΓòÉΓòÉ 12.1.3. B.1.3 OS/2 2.1 for Windows ΓòÉΓòÉΓòÉ

B.1.3 OS/2 2.1 for Windows

OS/2 2.1 for Windows is identical to OS/2 2.1 in every way except that WIN-OS/2
code is not provided. Instead, OS/2 2.1 "absorbs" your existing copy of Windows
3.1 so that when you launch a Windows application under OS/2, it launches
Windows 3.1 to run the application. OS/2 2.1 for Windows only supports Windows
3.1. Windows 3.11 and Windows for Workroups are not supported, though Windows
3.11 can be "downgraded" to Windows 3.1 to allow OS/2 for Windows to work. OS/2
2.1 for Windows can be upgraded using either Red Box Warp or Red Box Warp
Connect.


ΓòÉΓòÉΓòÉ 12.2. B.2 OS/2 Warp 3.0 Product Family ΓòÉΓòÉΓòÉ

B.2 OS/2 Warp 3.0 Product Family

OS/2 Warp 3.0 is the current version of OS/2 as of the writing of this work.
There are several different variations of Warp available. The base operating
system features are the the same between all versions. The differences are
explained below.


ΓòÉΓòÉΓòÉ 12.2.1. B.2.1 OS/2 Warp 3.0 ("Red Box Warp") ΓòÉΓòÉΓòÉ

B.2.1 OS/2 Warp 3.0 ("Red Box Warp")

OS/2 Warp v3.0 (Red Box). OS/2 Warp is the follow on product to OS/2 2.1 for
Windows. Like OS/2 for Windows, "Red Box" Warp requires Windows to be installed
on the hard drive. Warp adds several enhancements to OS/2, including increased
speed, an improved user interface, better recovery features, and support for
more hardware devices. Red Box Warp can be used to upgrade OS/2 2.1 for
Windows, but not ordinary OS/2 2.1, 2.11, or over any other version of Warp.
Red Box Warp is recommended for upgrading systems that already have DOS and
Windows 3.x installed. Warp Red Box can use any of the following versions of
Windows 3.x:

o   Windows 3.1

o   Windows 3.11

o   Windows for Workgroups 3.1

o   Windows for Workgroups 3.11

Note:  If you install Warp Red Box over Windows for Workgroups, you will not be
able to use the networking features of Windows for Workgroups. If you are
upgrading to OS/2 and want to be able to attach to your Windows for Workgroups
peer network, you may want to consider Warp Connect (See Section B.2.3).

Note:  All IBM PC Co. Warp preloads at the time of this writing use Red Box
Warp dual booting with DOS and Windows.


ΓòÉΓòÉΓòÉ 12.2.2. B.2.2 Warp with WIN-OS/2 3.0 ("Blue Box Warp") ΓòÉΓòÉΓòÉ

B.2.2 Warp with WIN-OS/2 3.0 ("Blue Box Warp")

OS/2 Warp with WIN-OS/2 is the follow on product to OS/2 2.1 and 2.11.  Blue
Box Warp is identical to Red BOX Warp in every way except that WIN-OS/2 is
provided with the product. It may be used to upgrade over OS/2 2.1 or 2.11, but
not over OS/2 2.1 for Windows or any other version of Warp. Blue Box Warp is
recommended for systems where OS/2 is the only operating system to be used, or
on systems that do not have Windows 3.x already installed.


ΓòÉΓòÉΓòÉ 12.2.3. B.2.3 OS/2 Warp Connect 3.0 ("Red Box Warp Connect") ΓòÉΓòÉΓòÉ

B.2.3 OS/2 Warp Connect 3.0 ("Red Box Warp Connect")

Red Box Warp Connect is identical to Red Box Warp except that it comes bundled
with networking software. The following additional components are provided:

o   IBM Peer for OS/2 1.0. Peer for OS/2 allows for peer-to-peer networking
    between OS/2 worksations on a LAN. Peer for OS/2 also allows OS/2
    workstations to connect to existing Windows for Workgroups peer networks.

o   OS/2 Lan Requester 4.0. Lan requester allows OS/2 workstations to connect
    to IBM LAN Server networks.

o   LAN Distance Remote 1.1. LAN Distance Remote allows you to connect an OS/2
    workstation to a remote LAN by using a modem connection. Additional
    software is required in the server to make this possible.

o   TCP/IP 3.0 Base Package. Warp Connect provides the most recent version of
    TCP/IP for OS/2. The full suite of TCP/IP utilities is provided, including
    both command line and PM versions PING, TELNET, TN3270, FTP, and FINGER.
    Also included are PM versions of a USENET news reader (News Reader/2), a
    World Wide Web browser (Web Explorer), a gopher client, and a multimedia
    enabled e-mail package (Ultimail Lite).

o   Novell Client 2.11 for OS/2. The Novell client allows OS/2 workstations to
    connect to Novell Netware networks.

o   NetWork SignON Coordinator/2. NSC/2 automates the logon process by allowing
    a single workstation to connect to  several networks and resources (each
    with their own login ID's and passwords) with a single user ID and
    password.

o   Lotus Notes Express. Lotus Notes Express is a "lite" version of Lotus's
    popular Notes workgroup software.

Red Box Warp Connect is recommended for upgrading existing DOS/Windows
worksations on a network to OS/2. Red Box Warp Connect can be installed over
OS/2 2.1 for Windows or over ordinary Red Box Warp, but not over OS/2 2.1,
2.11, or any "Blue Box" version of Warp.


ΓòÉΓòÉΓòÉ 12.2.4. B.2.4 Warp Connect with WIN-OS/2 3.0 ("Blue Box Warp Connect") ΓòÉΓòÉΓòÉ

B.2.4 Warp Connect with WIN-OS/2 3.0 ("Blue Box Warp Connect")

Warp Connect with WIN-OS/2 is identical to the Red Box version except that
WIN-OS/2 support is provided. Blue Box Warp Connect can be used to upgrade over
OS/2 2.1 or 2.11, but not over OS/2 2.1 for Windows or any "Red Box" version of
Warp.


ΓòÉΓòÉΓòÉ 12.2.5. B.2.5 The BonusPak ΓòÉΓòÉΓòÉ

B.2.5 The BonusPak

All versions of OS/2 ship with the BonusPak, a collection of 32 bit native OS/2
productivity applications and utilities. All of the applications were designed
to take advantage of OS/2's advanced features and are highly integrated with
the workplace shell. The BonusPak includes the following applications:

o   Compuserve Information Manager (CIM) for OS/2. CIM for OS/2 gives you a
    graphical front end for the Compuserve Information Service.

o   IBM Works and Personal Information Manager (PIM). IBM Works is an
    integrated software package that includes word processing, spreadsheet,
    database, charting, and report writer functions. The PIM includes calendar,
    monthly planner, appointment book, phone book, contact list, to do list,
    and notepad.

o   FaxWorks for OS/2. FaxWorks for OS/2 allows you to send and receive faxes
    from your computer using a fax /modem. Faxes can even be sent from DOS and
    Windows applications using the included fax printer driver.

o   HyperAcess Lite. HyperAccess Lite is a terminal emulation program that
    allows you to dial in to other computer systems and BBS's.

o   IBM Internet connection for OS/2. The Internet Connection provides a set of
    tools that allows you to connect to and explore the internet. Included are
    PM versions of TELNET, TN3270, FTP, and FINGER. Also included are PM
    versions of a USENET news reader (News Reader/2), a World Wide Web browser
    (Web Explorer), a gopher client, and a multimedia enabled e-mail package
    (Ultimail Lite).

    Note:  If you are using Warp Connect, you should not install the Internet
    Connection Kit from the BonusPak. You should install the TCP/IP product
    from the Warp Connect installation CD instead. All of the functionality of
    the Internet Connection Kit is included in the TCP/IP package.

o   IBM Multimedia Viewer. The IBM Multimedia Viewer provides a convenient way
    to organize and view various types of multimedia files (images, audio,
    video, etc.).

o   Video IN for OS/2. Video IN for OS/2 allows you to record digital video
    segments (with the appropriate hardware).

o   IBM Person to Person (P2P) for OS/2. P2P for OS/2 allows you to work with
    others over a LAN. You can hold on-line conferences via a "chat" function,
    and share drawings via a "chalkboard" function. The computers can be linked
    together either via modem, LAN connection, or ISDN.

o   System Information Tool. The System Information Tool reports various
    hardware and software information about your computer.

    Note:  On some IBM systems preloaded with OS/2, running the System
    Information Tool may cause the system to hang.


ΓòÉΓòÉΓòÉ 12.3. B.3 Upgrading a system to OS/2 Warp ΓòÉΓòÉΓòÉ

B.3 Upgrading a system to OS/2 Warp

If you are encountering problems trying to install OS/2 Warp, you may be trying
to upgrade over another operating system or a previous version of OS/2 that is
not supported by the OS/2 Warp package you have. The following table lists what
upgrade options are available.

Table B-1: Upgrading made easy

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéIf you now have.Γöéyou can install...Γöébut  you must first...  ΓöéYour file systemΓöé
Γöé..              Γöé                  Γöé                        Γöécan be...       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéA clean hard    ΓöéAny Base version  Γöéformat the hard drive   ΓöéFAT or HPFS     Γöé
Γöédrive           Γöéof Warp           Γöéduring installation.    Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDOS and/or      ΓöéAny version of    Γöé(no action required)    ΓöéFAT             Γöé
ΓöéWindows 3.x     ΓöéWarp              Γöé                        Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéWindows 95      ΓöéAny version of    Γöéformat the hard drive   ΓöéFAT (also HPFS  Γöé
Γöé                ΓöéWarp              Γöéduring installation     Γöéif Windows 95 isΓöé
Γöé                Γöé                  ΓöéOR                      Γöéremoved)        Γöé
Γöé                Γöé                  Γöéget "Just Add OS/2 Warp"Γöé                Γöé
Γöé                Γöé                  Γöépackage from IBM.       Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOS/2 1.x or     ΓöéAny Base version  Γöéformat the hard drive   ΓöéFAT or HPFS     Γöé
ΓöéOS/2 2.0        Γöéof Warp.          Γöébefore installation.    Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOS/2 2.1 or     ΓöéWarp "Blue Box" orΓöé(no action required)    ΓöéFAT or HPFS     Γöé
ΓöéOS/2 2.11       ΓöéWarp Connect "BlueΓöé                        Γöé                Γöé
Γöé                ΓöéBox"              Γöé                        Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOS/2 2.1 for    ΓöéWarp "Red Box" or Γöé(no action required)    ΓöéFAT             Γöé
ΓöéWindows         ΓöéWarp Connect "Red Γöé                        Γöé                Γöé
Γöé                ΓöéBox"              Γöé                        Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéWarp "Red Box"  ΓöéWarp Connect "Red Γöé(no action required)    ΓöéFAT             Γöé
Γöé                ΓöéBox"              Γöé                        Γöé                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéWarp "Blue Box" ΓöéWarp Connect "BlueΓöé(no action required)    ΓöéFAT or HPFS     Γöé
Γöé                ΓöéBox"              Γöé                        Γöé                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


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

The "Just Add OS/2 Warp" package contains patches that allow you to dual boot
between Windows 95 and OS/2. The package can be obtained from the IBM PC Co.
BBS (see Section 2.2.3).


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

Base operating system packages can be installed on a clean hard drive. Upgrade
packages incorporate a "sniffer" module that checks the hard drive for the
presence of the operating system(s) for which the upgrade was intended. If the
operating system is not found, the upgrade will not install.  Packages will be
marked as either base or upgrade. Packages that are not marked one way or
another are base packages.


ΓòÉΓòÉΓòÉ 13. Appendix C. Running DOS and Windows Programs Under OS/2 ΓòÉΓòÉΓòÉ

APPENDIX C. RUNNING DOS AND WINDOWS PROGRAMS UNDER OS/2.

OS/2 versions 2.0 and above have the capability of running DOS and Windows
programs simultaneously in one or more VDM's (Virtual DOS Machines) by using
the virtual 86 feature of 386 and above microprocessors. Each VDM is a separate
emulated DOS session, independent of and isolated from any other VDM's that are
running at the time. Should a program in a VDM crash, any other VDM's will
remain unaffected. The emulated DOS present in OS/2 is similar in features and
functionality to PC DOS 5.02. Note that since Windows is simply an operating
environment that runs under DOS, WIN-OS/2 sessions are VDM's as well.


ΓòÉΓòÉΓòÉ 13.1. C.1 OS/2 VDM settings ΓòÉΓòÉΓòÉ

C.1 OS/2 VDM settings

VDM's under OS/2 are highly customizable. Each DOS or WIN-OS/2 program can have
its own settings that are optimized for that particular session. If you are
having difficulties running a particular DOS or Windows application under OS/2,
you should probably start by trying to tweak the settings for that program so
that the OS/2 DOS and/or Windows environment is optimized for it.


ΓòÉΓòÉΓòÉ 13.1.1. C.1.1 Full Screen vs. Windowed sessions ΓòÉΓòÉΓòÉ

C.1.1 Full Screen vs. Windowed sessions

DOS Programs can be run under OS/2 in either Windowed or Full Screen sessions.
Each method has its advantages and disadvantages. Full screen mode more closely
mimics the environment the program was originally designed to run in, providing
maximum stability. Windowed mode (also called seamless mode) creates a seamless
level of integration between OS/2, Windows, and other DOS applications on the
OS/2 desktop, allowing you to cut and paste freely between these applications.

Some DOS applications that use enhanced graphics modes, however,  may appear
"jerky" or have corrupted video when run in a window, and others will not run
at all in a window. In general, if you are having problems running a DOS
application, try running it in a full screen session.

Windows applications can also be run in either windowed or full screen mode.
WIN-OS/2 windowed sessions can either run in a single, common VDM or in
separate VDM's (see Section C.1.3). WIN-OS/2 full screen sessions always run in
separate VDM's. Note that the same considerations that apply to DOS sessions
above also apply to WIN-OS/2 sessions. Most Windows applications will perform
better in full screen mode.


ΓòÉΓòÉΓòÉ 13.1.2. C.1.2 WIN-OS/2 FastLoad and its caveats ΓòÉΓòÉΓòÉ

C.1.2 WIN-OS/2 FastLoad and its caveats

WIN-OS/2 FastLoad is a feature of OS/2 that allows you to drastically reduce
the amount needed to launch a Windows program under OS/2. Normally, when you
launch a Windows program, you are also launching an entire DOS/Windows session
as well. FastLoad works by automatically starting an invisible WIN-OS/2 session
when you boot OS/2. When you launch a Windows application, the WIN-OS/2 session
is already running, and the program simply loads in that session. The settings
for the FastLoad session can be changed through the Session tab of the settings
notebook for the WIN-OS/2 setup object in the System Setup folder. Keep the
following pitfalls in mind when using FastLoad:

o   If you have audio support installed in WIN-OS/2, device conflicts and
    system hangs may occur at startup on some systems if FastLoad is enabled.

o   FastLoad requires additional system overhead in order to maintain the
    WIN-OS/2 session when you are not running Windows programs. In addition,
    your bootup time will be increased due to the time it takes to launch the
    hidden WIN-OS/2 session at startup.

o   FastLoad does not apply to full screen WIN-OS/2 sessions, or seamless
    sessions  for which you have enabled Separate Session (see Section C.1.3).

o   FastLoad only applies to sessions that run in the same mode as the FastLoad
    session. If your FastLoad session is set up to run in 386 Enhanced
    Compatibility Mode and you launch a session set up for Standard mode, a new
    Standard mode session will be created that will run all subsequently
    launched standard mode applications not marked as Separate Session. The
    reverse applies if your FastLoad session is set up to use Standard mode.


ΓòÉΓòÉΓòÉ 13.1.3. C.1.3 Running Windows programs in separate seamless sessions ΓòÉΓòÉΓòÉ

C.1.3 Running Windows programs in separate seamless sessions

By default, all Windows programs launched in seamless mode run in the same
WIN-OS/2 session, provided that their WIN_RUN_MODE settings are all the same.
This reduces the amount of time required to launch the applications, and also
minimizes the total amount of memory they use. Unfortunately, if one of the
applications crashes, all other applications running in that session are at
risk.

You can elect to run a particular Windows application in its own session by
enabling the Separate Session setting on the Session page of the program's
settings notebook. If you want all WIN-OS/2 seamless sessions to run in their
own VDM's, enable Separate Session from the Session tab of the WIN-OS/2 Setup
System settings notebook. Using separate WIN-OS/2 sessions isolates programs
from one another and increases stability, but is very costly in terms of
performance and system resources. If you have an Windows application that is
ill behaved, however,  you should probably run it in a separate session.

Figure C-1: WIN-OS/2 Setup Session Page

This page sets the global defaults for all WIN-OS/2 sessions. Each application
will have a similar version of this page from which the settings for the
session can be customized.


ΓòÉΓòÉΓòÉ 13.1.4. C.1.4 Using Add Programs to migrate programs to the desktop ΓòÉΓòÉΓòÉ

C.1.4 Using Add Programs to migrate programs to the desktop

If you are having trouble running a DOS or Windows application, and do not know
what the correct settings are for the application, you may be able to use the
Add Programs object in the System Setup folder to migrate your application to
the OS/2 Desktop. Add Programs searches your hard drive for executable files,
and compares the results with its own internal database of applications. If it
finds an application it recognizes, it will create an icon for the program on
the OS/2 desktop with the proper settings for the application. Note that Add
Programs will only do this for programs that it finds in its database, and that
some applications will still require additional tweaking.

OS/2 Warp also has an auto-migrate function. If you add a new program reference
object to the desktop from the Templates folder and specify a path and filename
for the executable, OS/2 will quickly check to see if the executable is in
another smaller database of popular applications. If so, OS/2 will
automatically load the correct settings for the application and even title the
icon for you. Again, you still may need to tweak the settings for best
performance.

Figure C-2: Add Programs Utility


ΓòÉΓòÉΓòÉ 13.1.5. C.1.5 VDM Settings for DOS and Windows applications ΓòÉΓòÉΓòÉ

C.1.5 VDM Settings for DOS and Windows applications

As mentioned earlier, each DOS or WIN-OS/2 session can have its own settings
which are independent of any other objects. To change the settings for a
particular application, open its settings notebook and click the Session tab.
Then click the DOS settings... (Or WIN-OS/2 Settings...) button on the Session
page. Table C-1 (see next page) lists a description of each of the settings.
Note that the defaults listed here may vary depending on the version of OS/2
and whether or not the program was added to the to the OS/2 desktop using the
Add Programs icon. In many cases, the best choices for these settings can be
determined only through experimentation.

Note that the descriptions presented here are designed to give you only the
information you need to know to get your application working. More complete
information on each of these settings can be obtained by using OS/2's on-line
help facility.

Table C-1: OS/2 VDM Settings

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéSetting                   ΓöéDefault Value            ΓöéAcceptable Values        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéWIN_RUN_MODE              Γöé3.1 Enhanced             Γöé3.1 Standard,            Γöé
Γöé                          ΓöéCompatibility            Γöé3.1 Enhanced             Γöé
Γöé                          Γöé                         ΓöéCompatibility            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: WIN-OS/2 only. Use this setting to determine whether the Windows Γöé
Γöéapplication runs in enhanced or standard mode. For most modern applications,  Γöé
Γöéthis should be left at enhanced compatibility mode.  Note that WIN-OS/2 never Γöé
Γöéactually operates in enhanced mode, but rather emulates enhanced mode.  Note  Γöé
Γöéthat applications that require VxD's or Win32s versions greater than 1.15 willΓöé
Γöénot run under OS/2.                                                           Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéWIN_DDE                   ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting enables dynamic sharing of data (DDE) among other OSΓöé
Γöé/2 and Windows programs. When this setting is On, dynamic data exchange (DDE) Γöé
Γöéis public.  Windows programs that support DDE automatically update identical  Γöé
Γöédata in other Windows and OS/2 programs, if you select public DDE on the Data Γöé
ΓöéExchange page  from the WIN-OS/2 Setup object, in the System  Setup folder.   Γöé
ΓöéOtherwise, you can share information  only with other Windows programs. When  Γöé
Γöéthis setting  is set to Off, DDE is private and Windows programs cannot share Γöé
ΓöéDDE information with other Windows and OS/2 programs.                         Γöé
Γöé                                                                              Γöé
ΓöéNote: If you are running multiple Windows programs in a single WIN-OS/2       Γöé
Γöésession and the program supports the DDE feature, it is possible to share DDE Γöé
Γöéinformation between these programs even when this setting is Off (private).   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéWIN_CLIPBOARD             ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting enables sharing of clipboard information among OS/2,Γöé
ΓöéDOS (window), and Windows programs. When this setting is On, the clipboard is Γöé
Γöépublic. Windows  programs can share data with other DOS, Windows,  and OS/2   Γöé
Γöéprograms, if you select public clipboard on  the Data Exchange page from the  Γöé
ΓöéWIN-OS/2 Setup object, in the System Setup folder.  Otherwise, you can share  Γöé
Γöéinformation only with other Windows programs in that session.  When this      Γöé
Γöésetting is set to  Off, the clipboard is private and Windows programs cannot  Γöé
Γöéshare clipboard information with other DOS,  Windows, and OS/2 programs.      Γöé
Γöé                                                                              Γöé
ΓöéNote: If you are running multiple Windows programs in a single WIN-OS/2       Γöé
Γöésession it is possible to share clipboard information between these programs  Γöé
Γöéeven when this setting is Off (private).                                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéWIN_ATM                   ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Enables Adobe Type Manager support in WIN-OS/2 sessions. Set to  Γöé
Γöéoff if you have applications that conflict with ATM.                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéAUDIO_ADAPTER_SHARING     ΓöéREQUIRED                 ΓöéNone, Optional, Required Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Most audio adapters can be in use by only one program (or WIN-OS/Γöé
Γöé2 session) at a time. If another WIN-OS/2 or DOS session is launched when the Γöé
Γöéaudio adapter is already in use, an error message will result. Use this       Γöé
Γöésetting to determine which DOS and WIN-OS/2 sessions get access to the audio  Γöé
Γöéadapter. REQUIRED is the default, and means the session must have access to   Γöé
Γöéthe audio adapter to function properly. the NONE setting means the session    Γöé
Γöédoes not need the device at all. If this setting is set to OPTIONAL, the      Γöé
Γöésession will try to use the adapter if it is not already in use, and ignore itΓöé
Γöéotherwise. To avoid device contention problems, try to make sure that only oneΓöé
Γöésession marked as REQUIRED is running at any given time. If you have several  Γöé
ΓöéWIN-OS/2 applications that require audio, run them all in a common REQUIRED   Γöé
Γöésession.                                                                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCOM_DIRECT_ACCESS         ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: If you have a communications application that is timing sensitiveΓöé
Γöé, or that requires direct access to the COM port, then turn this setting ON.  Γöé
ΓöéOtherwise, leave it off for better performance.                               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCOM_HOLD                  ΓöéOn                       ΓöéOff                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Some applications use one program to open the COM port, then     Γöé
Γöéaccess it with another. Setting COM_HOLD to ON allows these applications to   Γöé
Γöéwork under OS/2. COM_HOLD keeps the port open until the session ends.         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCOM_RECEIVE_BUFFER_FLUSH  ΓöéNONE                     ΓöéALL, RECEIVE DATA IRQ    Γöé
Γöé                          Γöé                         ΓöéENABLE, SWITCH TO        Γöé
Γöé                          Γöé                         ΓöéFOREGROUND, NONE         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting controls the content of the COM port received data  Γöé
Γöébuffers when the received data IRQ is enabled by a DOS program or when a DOS  Γöé
Γöésession is switched from the background to the foreground. Some DOS programs  Γöé
Γöérequire that communications data be discarded when the program is switched to Γöé
Γöéthe foreground; other DOS programs require that the  data be kept.  You can   Γöé
Γöéuse COM_RECEIVE_BUFFER_FLUSH to override the program setting and discard or   Γöé
Γöékeep the communication data  for all programs in this DOS session.            Γöé
Γöé                                                                              Γöé
ΓöéIf you select RECEIVE DATA INTERRUPT ENABLE, OS/2 will discard data in the    Γöé
Γöéreceived data buffer when the DOS program enables the received data interrupt.Γöé
Γöé                                                                              Γöé
ΓöéIf you select SWITCH TO FOREGROUND, OS/2 will discard data in the received    Γöé
Γöédata buffer when the DOS program is switched to the foreground.               Γöé
Γöé                                                                              Γöé
ΓöéIf you select ALL, communications data will be discarded when a DOS program   Γöé
Γöéenables the received  data interrupt or the program is switched to the        Γöé
Γöéforeground.                                                                   Γöé
Γöé                                                                              Γöé
ΓöéIf you select NONE, OS/2 will keep data in the received data buffer.          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCOM_SELECT                ΓöéALL                      ΓöéALL, COM1-COM4, NONE     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Some DOS applications grab all available COM ports (even when    Γöé
Γöéthey have no intention of using all of them), preventing any other            Γöé
Γöéapplications from using them. You can use this setting to limit the DOS       Γöé
Γöésession's access to the specified port.                                       Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_AUTOEXEC              ΓöéAUTOEXEC.BAT             ΓöéAny valid .BAT file      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Each DOS session under OS/2 can have its own customized AUTOEXEC.Γöé
ΓöéBAT. Use this setting to specify the batch file that runs automatically when  Γöé
Γöéthe system is started.                                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_BACKGROUND_EXECUTION  ΓöéOn                       ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting determines whether DOS applications remain running  Γöé
Γöéor suspend when in the background.  Some DOS applications poll the keyboard   Γöé
Γöécontinuously, wasting processor time. If the DOS program is usually idle when Γöé
Γöéin the background, turn this setting OFF to increase system performance.      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_BREAK                 ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting determines when the system checks to see if [Ctrl]-[Γöé
ΓöéBreak] is pressed. If set to on, responsiveness to [Ctrl]-[Break] is increasedΓöé
Γöéat the expense of system performance. This setting is analogous to the BREAK= Γöé
Γöéstatement in the DOS CONFIG.SYS.                                              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_DEVICE                Γöé-                        ΓöéAny valid DOS device     Γöé
Γöé                          Γöé                         Γöédriver                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting allows you to specify which DOS device drivers load Γöé
Γöéin the DOS session. Note that not all DOS device drivers will work under OS/2.Γöé
ΓöéThis setting is analogous to the DEVICE= statements in the DOS CONFIG.SYS.    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_FCBS                  Γöé16                       Γöé0-255                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: DOS_FCBS corresponds to the FCBS statement in the DOS CONFIG.SYS,Γöé
Γöéand is present primarily for compatibility with very old DOS programs that useΓöé
ΓöéFCB's (File Control Blocks).                                                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_FCBS_KEEP             Γöé8                        Γöé0-255                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: DOS automatically closes FCB's to keep the amount of open FCB's  Γöé
Γöéat or lower than the maximum (set in DOS_FCBS). Use this setting to force DOS Γöé
Γöéto keep the specified amount of FCB's open. This value must be less than or   Γöé
Γöéequal to the amount specified in DOS_FCBS above.                              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_FILES                 Γöé20                       Γöé20-255                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting corresponds to the FILES= statement in the DOS      Γöé
ΓöéCONFIG.SYS, and is used to specify the maximum number of files that the DOS   Γöé
Γöéprogram can have open at once.                                                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_HIGH                  ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines whether or not the DOS kernel is loaded high. This is Γöé
Γöéanalogous to the DOS=HIGH statement in CONFIG.SYS.                            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_LASTDRIVE             ΓöéZ                        ΓöéD-Z                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This statement is analogous to the LASTRDRIVE= statement in the  Γöé
ΓöéDOS CONFIG.SYS, and is used to determine the highest drive letter available toΓöé
Γöéthe DOS session.                                                              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_RMSIZE                Γöé640Kb                    Γöé128-640Kb                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Used to restrict the amount of conventional memory available to  Γöé
Γöéthe DOS session. This should usually not be changed.                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_STARTUP_DRIVE         Γöé-                        ΓöéAny valid drive letter orΓöé
Γöé                          Γöé                         Γöéimage file               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: If you are booting to a specific version of DOS, use this settingΓöé
Γöéto specify the drive containing the DOS kernel and startup files. If you have Γöé
Γöécreated a diskette image file containing a specific version of DOS (see       Γöé
ΓöéSection C.2), you can specify the filename of the image file here.            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_UMB                   ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines whether or not DOS has control of the Upper Memory    Γöé
ΓöéArea. This is analogous to the DOS=UMB statement in CONFIG.SYS.               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDOS_VERSION               Γöé-                        ΓöéProgram-name,0-255,0-255,Γöé
Γöé                          Γöé                         Γöé0-255                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: DOS_VERSION corresponds to the SETVER command in DOS, and is usedΓöé
Γöéto "lie" to a DOS about the DOS version so that the program will run. PROGRAM Γöé
Γöéspecifies the name of the program. The first number specifies the major DOS   Γöé
Γöéversion (e.g. "6" in  6.3). The second number specifies the minor DOS version Γöé
Γöé(e.g. "3" in 6.3). The final number specifies the number of times OS/2 will   Γöé
Γöéreport the phony DOS version. If you want OS/2 to always report the phony DOS Γöé
Γöéversion every time a program asks, use 255 for this number.                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDPMI_DOS_API              ΓöéAUTO                     ΓöéAUTO, ENABLED, DISABLED  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines whether DOS API translation is enabled for this       Γöé
Γöésession. If you are using a DPMI application in this session, you should      Γöé
Γöéprobably set this value to ENABLED.                                           Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDPMI_MEMORY_LIMIT         Γöé4Mb                      Γöé0-512Mb                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines the amount of DPMI Memory available to this session.  Γöé
ΓöéLike all extended-expanded memory that is available to DOS sessions, DPMI     Γöé
ΓöéMemory is sparsely allocated under OS/2, which means OS/2 will only allocate  Γöé
Γöéthe amount of memory requested by the application. Nevertheless, there is a   Γöé
Γöécertain amount of overhead associated with making this memory available, so   Γöé
Γöéyou should set this value to closely reflect the requirements of your         Γöé
Γöéapplication.                                                                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDPMI_NETWORK_BUFF_SIZE    Γöé8Kb                      Γöé1-64Kb                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines the size of the network translation buffer for this   Γöé
Γöésession. If you are having difficulty running DPMI applications (e.g. Windows Γöé
Γöéapplications) over a network, try increasing this value.                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéEMS_FRAME_LOCATION        ΓöéAUTO                     ΓöéAUTO, NONE, C000h-DC00h, Γöé
Γöé                          Γöé                         Γöé8000h-9000h              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Determines the location of the EMS page frame. AUTO will         Γöé
Γöéautomatically place the page frame. Choosing NONE will disable it. If you     Γöé
Γöéchoose a range within C000-DC00, the page frame will be placed in upper memoryΓöé
Γöé. If you choose a range within 8000-9000, the frame will be placed in         Γöé
Γöéconventional memory. It may be necessary to move the frame to avoid adapter   Γöé
ΓöéROM-RAM conflicts.                                                            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéEMS_HIGH_OS_MAP_REGION    Γöé32Kb                     Γöé0-96Kb                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Determines the amount of memory a DOS program can add to the    Γöé
Γöé64KB EMS page frame. Some applications may use additional upper memory in     Γöé
Γöéaddition to the page frame.  Use  MEM_EXCLUDE_REGIONS and MEM_INCLUDE_REGIONS Γöé
Γöé(mentioned later) to avoid a conflict with memory used by an adapter card.    Γöé
ΓöéThis will cause the EMS_HIGH_OS_MAP_REGION to be placed in an area that       Γöé
Γöéaccommodates both your program and the adapter card.                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéEMS_LOW_OS_MAP_REGION     Γöé384Kb                    Γöé0-576Kb                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Some DOS programs access EMS memory by remapping it into        Γöé
Γöéconventional memory. EMS_LOW_OS_MAP_REGION determines the amount of memory    Γöé
Γöéavailable to the VDM for this purpose.                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéEMS_LOW_OS_MAP_REGION     Γöé384Kb                    Γöé0-576Kb                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Some DOS programs access EMS memory by remapping it into        Γöé
Γöéconventional memory. EMS_LOW_OS_MAP_REGION determines the amount of memory    Γöé
Γöéavailable to the VDM for this purpose.                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéEMS_MEMORY_LIMIT          Γöé2048Kb                   Γöé0-32768Kb                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Determines the amount of EMS memory available to this session.  Γöé
ΓöéAgain, it is best to adjust this value to match the requirements of the       Γöé
Γöéapplication. Set this value to 0 if your application does not use EMS memory. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéHW_NOSOUND                ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Turn this setting ON to disable program generated sounds.        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéHW_ROM_TO_RAM             ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting enables BIOS ROM shadowing for DOS sessions. ROM    Γöé
ΓöéShadowing copies the BIOS to RAM, and can potentially increase system         Γöé
Γöéperformance, but may not be compatible with some DOS applications.            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéHW_TIMER                  ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting gives DOS applications direct access to the hardwareΓöé
Γöétimer. You should usually set this setting to ON for games, multimedia, and   Γöé
Γöéother timing sensitive applications.                                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéIDLE_SECONDS              Γöé0                        Γöé0-60                     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Many DOS applications continuously poll the keyboard for input   Γöé
Γöéwhen not in use, degrading performance. OS/2 can detect this behavior and     Γöé
Γöéreduce the program's processor time. IDLE_SECONDS determines how long the     Γöé
Γöéprogram must remain idle before OS/2 checks to see if the program is polling  Γöé
Γöéthe keyboard. See also IDLE_SENSITIVITY below.                                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéIDLE_SENSITIVITY          Γöé75                       Γöé1-75                     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting determines what percentage of its time a DOS programΓöé
Γöémust spend idly polling the keyboard before OS/2 reduces that program's       Γöé
Γöéprocessor time.  Setting this value to 100 will disable idle detection        Γöé
Γöéaltogether. See also IDLE_SECONDS above.                                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéINT_DURING_IO             ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting determines whether or not DOS applications are      Γöé
Γöéallowed to process interrupts during file read and write operations.  Turn    Γöé
Γöéthis setting ON for multimedia applications.                                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéKBD_ALTHOME_BYPASS        ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: The [Alt]-[Home] keystroke sequence is usually used to toggle a  Γöé
ΓöéDOS session between windowed and full screen modes. If you have a DOS         Γöé
Γöéapplication that uses  [Alt]-[Home] for its own purposes, you can turn this   Γöé
Γöésetting ON to force OS/2 to ignore the [Alt]-[Home] sequence and  allow it to Γöé
Γöébe passed directly to the DOS session.                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéKBD_BUFFER_EXTEND         ΓöéOn                       ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: If set to ON, this setting increases the size of the keyboard    Γöé
Γöébuffer for the session from 16 to 128 characters.                             Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéKBD_CRTL_BYPASS           ΓöéNone                     ΓöéNone, CTRL_ESC, ALT_ESC  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: The [Ctrl]-[Esc] and [Alt]-[Esc] keystroke sequences are used to Γöé
Γöéactivate the task list and to switch between sessions in OS/2. If you have a  Γöé
ΓöéDOS application that uses either [Ctrl]-[Esc] or [Alt]-[Esc] for its own      Γöé
Γöépurposes, you can use this setting to force OS/2 to bypass either the [Ctrl]-[Γöé
ΓöéEsc] or [Alt]-[Esc] sequence and  allow it to be passed directly to the DOS   Γöé
Γöésession. Choose the sequence you want to be bypassed from the list.           Γöé
Γöé                                                                              Γöé
ΓöéNote: You cannot bypass BOTH [Ctrl]-[Esc] and [Alt]-[Esc]. Doing so would     Γöé
Γöéleave you with no way to switch out of a DOS full screen session.             Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéKBD_RATE_LOCK             ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Some DOS programs may change the keyboard repeat rate. Turning   Γöé
Γöéthis setting ON prevents this.                                                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéMEM_EXCLUDE_REGIONS       Γöé None                    ΓöéAny address range(s) in  Γöé
Γöé                          Γöé                         Γöéthe Upper Memory Area    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  This setting can be used to prohibit access to Upper Memory     Γöé
Γöéregions. If you specify a single address, a 4Kb block is assumed. Separate theΓöé
Γöéranges by commas, as in the following example: C0000, D8000-DBFFF. This is theΓöé
Γöésame as excluding the following regions with EMM386 in a native DOS           Γöé
Γöéenvironment: x=C000-C0FF x=D800-DBFF. Note that OS/2 uses all five hex digits Γöé
Γöéof an address.                                                                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéMEM_INCLUDE_REGIONS       Γöé None                    ΓöéAny address range(s) in  Γöé
Γöé                          Γöé                         Γöéthe Upper Memory Area    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  This setting can be used to allow access to Upper Memory regionsΓöé
Γöé. If you specify a single address, a 4Kb block is assumed. Use the same syntaxΓöé
Γöéas with MEM_EXCLUDE_REGIONS. This setting is analogous to Including regions   Γöé
Γöéwith EMM386 in a native DOS environment.                                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéMOUSE_EXCLUSIVE_ACCESS    ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: You may sometimes see two mouse pointers when using some DOS     Γöé
Γöéapplications (e.g. WordPerfect) in a window. Turning this setting ON gives theΓöé
ΓöéDOS session exclusive control of the mouse when you click inside the session'sΓöé
Γöéwindow. To regain use of the mouse on the OS/2 Desktop, use [Ctrl]-[Esc] or [ Γöé
ΓöéAlt]-[Esc] to switch to another session.                                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéPRINT_SEPARATE_OUTPUT     ΓöéOn                       ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting allows the print spooler to separate output from    Γöé
Γöédifferent DOS programs running in the same session. If you want the output    Γöé
Γöéfrom all DOS applications running in the same session treated as a single     Γöé
Γöéstream of data, turn this setting OFF.                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéPRINT_TIMEOUT             Γöé15                       Γöé0-3600                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: OS/2 has no way of knowing when a DOS print job has completed.   Γöé
ΓöéThis setting determines (in seconds) how long the program sits idle before OS/Γöé
Γöé2 assumes the print job is ready and sends the data to the spooler to be      Γöé
Γöéprinted.  If your DOS program sends data to the printer in bursts separated byΓöé
Γöélong periods of inactivity (e.g. graphics programs that render images in      Γöé
Γöémemory before sending them to the printer), increase the value of this settingΓöé
Γöé.                                                                             Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéSESSION_PRIORITY          Γöé1                        Γöé1-32                     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Use this setting to adjust the priority level of the DOS session.Γöé
ΓöéPriority 1 is the lowest and the default.                                     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_8514A_XGA_IOTRAP    ΓöéOn                       ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Turn this setting OFF to give DOS applications direct access to  Γöé
Γöéthe video hardware for 8514a and XGA adapters. This may increase performance  Γöé
Γöéof the DOS session, but may also cause screen refresh problems. The default isΓöé
ΓöéON, which generally allows for greater stability at the expense of performanceΓöé
Γöé. If you turn this setting OFF, you should set VIDEO_SWITCH_NOTIFICATION to ONΓöé
Γöé(see entry below).                                                            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_FASTPASTE           ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Turning this setting ON increases the speed of text based cut-andΓöé
Γöé-paste operations from the clipboard between DOS applications. Note that not  Γöé
Γöéall applications are compatible with VIDEO_FASTPASTE.                         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_MODE_RESTRICTION    ΓöéNone                     ΓöéNone, CGA, Mono          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: You can use this setting to restrict the video mode of a DOS     Γöé
Γöésession to either CGA or Monochrome mode. Doing this can allow up to 720Kb of Γöé
Γöéconventional memory for the program, if the program is able to use            Γöé
Γöéconventional memory above 640Kb. Note that some applications may become       Γöé
Γöéunstable if this setting is used.                                             Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_ONDEMAND_MEMORY     ΓöéOn                       ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: If you are having problems running a program that uses Super VGA Γöé
Γöé(SVGA) modes in a DOS full screen session, try turning this setting OFF. This Γöé
Γöémay increase the stability of the application at the expense of increased     Γöé
Γöésystem overhead.                                                              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_RETRACE_EMULATION   ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Some applications written for CGA displays continuously refresh  Γöé
Γöéthe screen, wasting processor time. This setting determines the behavior of   Γöé
Γöéthese applications under OS/2. Turning this setting OFF will prevent          Γöé
Γöécontinuous refresh and usually increase performance, but may cause            Γöé
Γöécompatibility problems with some applications. Turning this setting ON will   Γöé
Γöéusually increase compatibility at the expense of performance.                 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_ROM_EMULATION       ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Turn this setting ON for better text mode performance. Turn it   Γöé
ΓöéOFF if your application requires special text-mode enhancements provided by   Γöé
Γöéyour display adapter.                                                         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_SWITCH_NOTIFICATION ΓöéOff                      ΓöéOn, Off                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: Turn this setting ON when you are not using VIDEO_8514A_XGA_     Γöé
ΓöéIOTRAP,  when you are using VIDEO_ONDEMAND_MEMORY, for WIN-OS/2 sessions, and Γöé
Γöéwhen you are using DOS programs that require SVGA. If your application is     Γöé
Γöéusing a standard video mode (e.g. CGA, Mono, EGA, or VGA), you should probablyΓöé
Γöéturn this setting OFF. Some experimentation may be necessary.                 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVIDEO_WINDOW_REFRESH      Γöé1                        Γöé1-600                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription: This setting adjusts the rate (in tenths of seconds) that a DOS  Γöé
Γöéprogram is allowed to refresh its screen. If the program appears "jerky" and  Γöé
Γöéunresponsive when drawing menus or refreshing the screen, try decreasing this Γöé
Γöévalue.                                                                        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéXMS_HANDLES               Γöé32                       Γöé0-128                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Determine the number of handles available to identify EMB's (   Γöé
ΓöéExtended Memory Blocks). You should probably not adjust this value unless yourΓöé
Γöéapplication requires a large number of handles.                               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéXMS_MEMORY_LIMIT          Γöé2048Kb                   Γöé0-16384Kb                Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Determines the amount of XMS memory available to this session.  Γöé
ΓöéIf your application does not use XMS memory, set this value to 64 (If you set Γöé
Γöéit to 0, the session will not have access to the HMA)                         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéXMS_MINIMUM_HMA           Γöé0Kb                      Γöé0-63Kb                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription:  Determines the minimum amount of HMA memory a program can use inΓöé
Γöéthis session. Since only one program can use the HMA at a time, it may be     Γöé
Γöédesirable to use this setting to prevent programs from using a small portion  Γöé
Γöéthe HMA, thus wasting the remainder of the High Memory Area.                  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 13.1.6. C.1.6 Saving settings to a file ΓòÉΓòÉΓòÉ

C.1.6 Saving settings to a file

Through experimentation you may find a set of optimal settings that you would
like to use with several of your applications. Or you may wish to use the same
settings for the same application on several different systems. Figure C-3
below shows a typical settings page for a DOS or WIN-OS/2 application (A DOS
application would not show the "WIN_" settings). If you choose Print from this
screen, one of the options will allow you to save the settings in an encoded
file. From the settings page for any session, you can then use the Load button
to reload the settings for the session from the encoded file.

Figure C-3: A typical settings page for a WIN-OS/2 program


ΓòÉΓòÉΓòÉ 13.2. C.2 Booting a specific version of DOS ΓòÉΓòÉΓòÉ

C.2 Booting a specific version of DOS

Some programs will simply not run correctly with OS/2's emulated DOS. If you
have a program of this sort, you can  use the DOS from Drive A: object in the
Command Prompts folder to boot a real version of DOS from diskette under OS/2
and run your program. DOS sessions of this type are called specific DOS
sessions. Keep in mind the following pointers when using specific DOS sessions:

o   Any version of DOS from 3.3 through PC-DOS 7.0 is supported. this includes
    Microsoft MS-DOS,  IBM PC-DOS and other variants of DOS such as Novell DOS
    and DR-DOS.

o   The various disk compression utilities provided by more recent versions of
    DOS (DoubleSpace, DriveSpace, SuperStor, and Stacker) are not supported.

o   The various disk utilities provided by more recent versions of DOS
    (UNDELETE, CPBACKUP, DEFRAG, SCANDISK, CHKDSK, etc.) are not supported.

o   Many of the drivers provided with DOS (e.g. HIMEM.SYS, EMM386.SYS,
    MOUSE.COM, and SMARTDRV.EXE) have substitutes provided by OS/2. If you need
    the functionality provided by these drivers, you must use the OS/2
    substitutes. The versions provided with your version of DOS will not work
    under OS/2. See the OS/2 Master Help Index for more information.


ΓòÉΓòÉΓòÉ 13.2.1. C.2.1 Booting DOS from an image file ΓòÉΓòÉΓòÉ

C.2.1 Booting DOS from an image file

Booting DOS from a floppy disk is not very convenient, especially if you must
do it often to run a particular program. Fortunately, OS/2 provides an easier
way. Using OS/2's VMDISK utility, you can create an image of your DOS boot
diskette on the hard drive, and then start DOS from this image. Perform the
following steps to create an image of DOS which can be booted from your hard
drive.

1.  Create a bootable DOS diskette from a system running DOS. Use the following
    command:

        FORMAT A: /S

    Note:  You must be running "pure" DOS when you make this diskette.  You
    cannot simply run the FORMAT A: /S from an DOS session under OS/2.

2.  Copy all needed DOS files as well as any drivers needed by your application
    to the bootable diskette.

3.  Create the startup files on the diskette. Start by creating a CONFIG.SYS
    file using a DOS text editor or the OS/2 system editor. Use the following
    sample CONFIG.SYS as a guide, adding any additional device drivers needed
    by your application:

        DEVICE=FSFILTER.SYS
        DEVICE=C:\OS2\MDOS\HIMEM.SYS
        DEVICE=C:\OS2\MDOS\EMM386.SYS
        FILES=20
        BUFFERS=30
        SHELL=C:\OS2\MDOS\COMMAND.COM /P /E:1024

    Note:  The FSFILTER.SYS device drive is only needed if you need to access
    HPFS drives from within the specific DOS session. If you are referencing
    device drivers in the CONFIG.SYS that load from an HPFS drive (as in the
    above example), the FSFILTER statement must come before any such reference.

    Create an AUTOEXEC.BAT file on the diskette using a DOS text editor or the
    OS/2 system editor. Use the following sample AUTOEXEC.BAT as a guide,
    adding any additional device drivers or TSR's needed by your application.
    If you are creating this image to run a particular application, you may
    wish to add a statement to your AUTOEXEC.BAT that will automatically run
    the application.

        @ECHO OFF
        PROMPT $P$G
        SET COMSPEC=C:\OS2\MDOS\COMMAND.COM
        PATH=A:\;C:\OS2\MDOS
        C:\OS2\MDOS\MOUSE

4.  If you need to access HPFS drives from your specific DOS session, copy the
    FSFILTER.SYS from the OS2\MDOS subdirectory to the bootable diskette.

5.  Create another DOS Window (or Full Screen) object by making a copy of the
    original. Name the new icon appropriately.

6.  When you have the boot diskette prepared, create an image file from it by
    typing the following command at an OS/2 or DOS command prompt:

        VMDISK A: C:\DOS5.IMG    ;or any other appropriate file name

7.  Open the settings notebook for the new icon you have created.  Change the
    DOS_STARTUP_DRIVE setting to point to the image file you created in step 6
    above. For the example given above, the setting would read as follows:

        C:\DOS5.IMG

At this point you will have an object which will allow you to launch a specific
version of DOS from your hard drive and run your application. Note that when
you are running programs in the specific DOS session, drive A: will be the
image file from which you started the session. The session will be able to read
from and write to the image file just as though it were a floppy disk. If you
need access to the real drive A: while in the specific DOS session, you can use
the FSACCESS command to remap drive A: to the floppy drive. The syntax of the
command is as follows:

FSACCESS A:

Note that doing this will make the image file unavailable. If your DOS program
tries to access files from the disk image, it will probably fail. In addition,
some DOS programs flush the command interpreter out of memory, and then reload
it when the application shuts down. If you have used FSACCESS and have loaded
the command interpreter from the image file, you may receive an error message
about a missing command interpreter (or some similarly worded error message)
when the program quits.

One way to avoid these problems is to load all device drivers, TSR's, and even
the command interpreter  itself from the hard drive. This way you no longer
need the image file once you have booted from it (The DOS kernel files always
remain resident in memory). This is how the example startup files in the steps
above are set up.


ΓòÉΓòÉΓòÉ 14. Appendix D. Limits and Capacities ΓòÉΓòÉΓòÉ

APPENDIX D. LIMITS AND CAPACITIES

File System Limits:

Limits common to both FAT and HPFS File Systems

Max file size..................................................2Gb
Max useable partitions (on all hard drives) per system.........24
Max primary partitions per physical drive......................4
Max extended partitions per physical drive.....................1
Max partitions (logical+primary) per physical drive............16

FAT File System

Largest FAT volume.............................................2Gb
Max cache size.................................................None (4)
Max FAT entries................................................65536
Max storage space..............................................48Gb
Cluster size...................................................2-32Kb (1)

High Performance file system

Max file enties per volume.....................................None (4)
Max bootable partition size....................................4Gb
Max partition size.............................................64Gb (2)
Max cache size.................................................2048Kb (3)
Max storage space..............................................1.5Tb
Cluster size...................................................512 bytes

Multitasking Limits

OS/2 Limits

Max threads....................................................4095 (4)
Max amount of addressable memory...............................4Gb
Max amount of virtual memory...................................512Mb (4)
Max sessions (OS/2 and VDM's)..................................255 (4)
Max Full Screen sessions.......................................16 (5)
Max data rate for OS/2 telecommunications......................57,600bps

VDM Limits

Max VDM sessions...............................................240 (4)
Max XMS Memory per VDM.........................................16Mb
Max EMS Memory per VDM.........................................32Mb
Max DPMI Memory per VDM........................................512Mb
Max data rate for DOS/Windows telecommunications...............9,600bps


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

The cluster size for FAT volumes varies depending on the size of the hard
drive. See Table 1-1 in Section 1.2.1 for more information.


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

The current version of CHKDSK may encounter problems checking drives over 16Gb
in size. for this reason, you should keep HPFS drives under 16Gb.


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

The HPFS386 File System driver that ships with OS/2 LAN Server Advanced
supports larger cache sizes.


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

These limits are theoretical. You will typically run out of other resources
(e.g. hard disk space, RAM, patience) long before these limits are reached.


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

Note that PMSHELL.EXE and HARDERR.EXE are already taking 2 sessions, so you
will in reality be limited to 14 full screen OS/2 sessions.


ΓòÉΓòÉΓòÉ 15. Appendix E. Glossary ΓòÉΓòÉΓòÉ

APPENDIX E: GLOSSARY

ABIOS (Advanced Basic Input/Output System).  A set of sofware extensions to the
BIOS ROM of a PC. ABIOS code is typically loaded from a special partition on
the hard drive at startup. See also BIOS.

ABIOS Patch.  A procedure needed to install OS/2 on some microchannel systems.
The patch typically involves copying all the ABIOS.SYS and all *.BIO files from
the system's reference diskette to a copy of the OS/2 installation diskette.

argument, or parameter.  A value specified on the end of a command line or
statement used to pass input to the command or statement being executed.
Arguments that can vary in value are often represented by a generic
placeholder, such as dddd-dddd for address ranges.

AUTOEXEC.BAT.  A batch file started by a DOS or WIN-OS/2 session that executes
automatically every time the session is started. AUTOEXEC.BAT consists of a
series of DOS commands just as they would be entered at the command line.

BIOS (Basic Input/Output System).  A set of programs built into the ROM of a PC
that act as a low level interface between the computer and various peripherals.

binary search.  An extremely efficient search algorithm which reduces the
amount of data to be searched by 50% through each iteration. Binary searches
are performed in log[2] n time, where n represents the total number of items to
be searched. Binary searches require that the list be sorted before the search
is performed.

bit.  Short for binary digit. A binary digit may either be 0 or 1, and usually
corresponds to a low or high signal, receptively,  in a computer circuit.

boot ROM.  On a SCSI adapter, the chip containing the code necessary to allow
the system to boot from a SCSI hard drive.

boot manager.  One of two methods provided with OS/2 for allowing multiple
operating systems to reside on the same system. Each operating resides in its
own partition. The user chooses which partition to boot from a menu displayed
at startup. See also Dual Boot.

bus.  The circuitry used to connect various components inside the PC.

bus architecture.  A hardware specification that determines how adapter cards
communicate with the computer system.

bus mastering.  A feature supported by some bus architectures that allows an
adapter card in the system to take control of the bus.

bytes.  An eight digit binary number. The smallest addressable unit of memory
in a computer. In most computers, a character is represented by one byte.

card services.  The software component of the PCMCIA architecture that
allocates and manages system resources used by PCMCIA cards.

CID (Configuration-Installation-Distribution).  A feature of OS/2 LAN Server
that allows OS/2 and other software products to be installed over a LAN.

client.  In a client/server scheme, the client is an entity that requests
resources from another entity (the server) that controls those resources. In a
client/server networking environment, the client systems are often called
workstations. See also server.

client enabler.  The card-specific software component of the PCMCIA
architecture that allows the PCMCIA card to be recognized by applications.

cluster, or allocation unit.  The smallest amount of disk space that may be
allocated by a file system at any given time. The size of the cluster will
depend on the size of the hard drive and the file system used, but will always
be some multiple of 512 bytes.

CONFIG.SYS.  A file used by OS/2 at system startup to configure various
operating system parameters and to load device drivers.

conventional memory.  The first 640Kb of memory address space in a PC.
Conventional memory is the only memory available to pure DOS programs.

cooperative, or voluntary multitasking.  A multitasking scheme in which running
applications voluntarily allow the operating system to manage processor time.

CRC (Cyclic Redundancy Check) error.  An error that usually occurs when part of
a disk's magnetic recording surface has weakened to the point that its data has
become unreadable. A CRC error indicates that the data on that portion of the
disk is unreadable.

cross linked files.  Two or more files on a disk that claim the same segment of
data on the disk as their own.

destructive MAKEINI.  A procedure for rebuilding the OS/2 desktop that
recreates the default desktop from scratch. All user customizations and
additions to the OS/2 desktop are lost.

device driver.  Software code that allows the operating system to access and
operate various peripherals, such as multimedia, networking, and video
adapters. In OS/2, device drivers are typically specified and configured in the
CONFIG.SYS.

DMA channel.  A hardware signal used by devices to perform DMA (Direct Memory
Access). DMA allows adapter cards to access system memory directly without
having to go through the microprocessor.

DOS Extender.  A program that allows specially written DOS applications to use
extended memory.

DPMI (DOS Protected Mode Interface) memory.  A specification for accessing
extended memory from DOS applications. DPMI is the preferred method of
accessing extended memory from DOS programs.

dual boot.  One of two methods of allowing DOS and OS/2 to reside on the same
system. Dual boot allows OS/2 and DOS to reside on the same hard drive
partition. The user is able to reboot the machine into either operating system
by clicking an icon or entering a command. See also Boot Manager.

EA DATA. SF.  A file that contains the extended attributes for all files on the
drive. Each file on the hard drive has a pointer in its directory entry that
points to an offset in this file. EA DATA. SF is only present on FAT volumes.
Damage to this file can result in operating system failure.

ECC (Error Checking and Correcting) memory.  An expensive type of memory that
uses redundant memory to both detect and correct memory errors.

EDO (Extended Data Out) memory.  A new type of high performance memory that
allows both read and write operations to occur simultaneously on the same chip.

EIDE (Enhanced Integrated Drive Electronics).  An enhanced version of the IDE
specification that allows larger, faster hard drives as well as other types of
devices, such as CD-ROM's, to be attached to the PC via the IDE interface. See
also IDE.

EISA (Extended Industry Standard Architecture).  An improved high speed bus
developed by Compaq and others, based on ISA.

EMS memory.  See entry for LIM Memory.

exception handler.  The component of the operating system that handles errors
(exceptions) that are generated by the microprocessor. The exception handler
determines the type of the error, and takes appropriate action (such as
displaying an error message).

extended attributes.  A set of data structures associated with a file that
stores information concerning the file, such as the file's icon, long file name
(for FAT drives), comments, and information concerning desktop objects that are
associated with the file.

extended memory.  The memory address space above 1Mb that is directly
accessible by 286 and above microprocessors operating in protected mode.

external (or level 2) cache.  A special type of fast RAM used to cache
read/write operations between the microprocessor and RAM. Most modern
microprocessors are much faster than RAM, and require external cache for best
performance.

fault tolerance.  A set of features designed to allow enhance a product's
ability to recover in the event of an error.

 FAT (File Allocation Table).  One of two file systems supported by OS/2. FAT
was originally designed for (and is still used by) DOS, and is internally
supported by OS/2 without special drivers. See also HPFS.

file fragmentation.  The condition that occurs when a file is stored in
non-contiguous locations on the hard drive. Severe file fragmentation can
adversely affect performance.

file system.  A set of data structures that determine how files are physically
stored and accessed on a disk.

FixPak.  A set of diskettes that is used to apply corrective service (bug
fixes) to an existing installation of OS/2. FixPaks may not be publicly
available, and are often specific to a particular set of symptoms.

FLASH BIOS.  A special type of BIOS that is stored in nonvolatile RAM instead
of ROM. FLASH BIOS is popular in many modern systems because it can be easily
upgraded by the user without replacing hardware.

High Memory Area, or HMA.  The first 64Kb of address space above 1Mb. The HMA
is directly accessible by 286 and above microprocessors operating in real mode.

hotfix.  A fault tolerance feature of HPFS that allows data to be written to
temporary areas on the hard drive (the hotfixes) if bad sectors on encountered.
At a later time (when CHKDSK is run), the data is written to a permanent
location and the bad sectors are marked as such by the file system.

hot plugging.  The practice of removing and reinserting PCMCIA cards (or other
hardware devices) while the system is powered up.

HPFS (High Performance File System).  One of two file systems supported by
OS/2. HPFS was designed specifically for OS/2, and is optimized for use with
large hard disks. HPFS support requires a special driver. See also FAT.

IDE (Integrated Drive Electronics).  A popular specification for attaching hard
drives to a PC. As its name implies, IDE incorporates most of the hard drive
controller hardware onto the drive itself. See also EIDE.

internet.  A vast global public network consisting of government, corporate,
and educational institutions. In recent years the internet has experienced
phenomenal growth, with many service providers providing access directly to end
users.

interrupt (IRQ).  An electrical signal generated by a hardware component to
request the immediate attention of the operating system. The operating system
processes the interrupt by passing control to a piece of code which handles the
event signaled by the hardware.

I/O port.  A range of memory addresses that is used  by the operating system to
communicate with a hardware device, such as a COM port or network adapter.

ISA (Industry Standard Architecture), or AT Bus.  The original bus architecture
used by the IBM PC AT.  ISA remains the most popular bus for PC's.

LAN Server.  A popular client/server networking environment for PC's,
manufactured by IBM. The server software itself runs under OS/2.

lazy write caching.  A caching scheme that holds data to be written to the disk
in cache memory until the disk is idle. When the disk has remained idle for a
specified period of time, the contents of the cache are written (flushed) to
the disk.

local area network (LAN).  A network composed of several interconnected PC's.
LAN's allow users on several different computers to share data and
applications.

LIM (Lotus-Intel-Microsoft) memory, EMS memory,  Expanded memory.  An early
scheme designed to allow DOS programs running on 8088 and 8086 systems access
to memory outside the processor's addressing capabilities.

local bus.  A term used to describe several new high speed bus architectures
that attempt to avoid speed bottlenecks by linking directly into the
microprocessor bus.

lost allocation unit (or lost cluster).  A segment of data on the hard disk
that is marked as in use by the operating system, but does not belong to any
particular file.

maintenance desktop.  An option in the recovery choices menu that allows you to
repeat the second half of the OS/2 installation procedure.

master/slave.  Only one device may have control of an IDE chain. This device is
the master, and is usually the first physical device on the chain. The other
IDE device is called the slave. IDE devices typically have jumpers that allow
them to be configured either as master or slave. Some devices also have a
"neutral" setting that is used if the device is the only one on the chain.

memory leak.  A phenomenon that occurs when an application allocates memory,
but never de-allocates the memory when the application exits or no longer needs
the memory. Memory leakage is typically due to a programming error, and can
cause excessive growth of the swap file.

memory manager.  In PC-DOS, a program that manages access to the memory
resources of a PC.

microchannel (MCA).  A proprietary high speed bus architecture developed by IBM
for the PS/2 line of personal computers.

microprocessor.  The chip in a PC responsible for interpreting and executing
instructions. The microprocessor may be thought of as the "brain" of the
computer.

migrate.  The term used to describe the process of configuring programs to run
from the OS/2 desktop.

multitasking.  A feature of OS/2 and other advanced operating systems that
allows several programs to execute simultaneously. Compare with multithreading.

multithreading.  A feature of OS/2 and other advanced operating systems that
allows a single application to perform several tasks simultaneously. Compare
with multitasking.

Netware.  A popular client/server networking evironment for PC's, manufactured
by Novell.

network interface card (NIC).  An adapter card that allows a PC to hook into a
local area network.

non-destructive MAKEINI.  The procedure for rebuilding the OS/2 desktop that
resets the default system objects to default values, leaving any user additions
and customizations intact.

non-parity memory.  A type of memory used in many low end systems that does not
include any error detection capabilities.

OS2.INI.  One of two files that comprise the OS/2 Desktop. OS2.INI contains
user interface customizations, abstract object definitions, and configuration
parameters for OS/2 applications.

OS2SYS.INI.  One of two files that comprise the OS/2 Desktop. OS2SYS.INI
contains hardware configuration information, window positions, and other system
information.

page frame.  A fixed number of contiguous memory pages. In DOS memory
management, a 64Kb page frame is used as a "window" into which EMS memory is
remapped, making it accessible to older DOS programs.

page.  An arbitrary unit of memory consisting of a fixed number of bytes. When
pertaining to OS/2 and the 386 microprocessor architecture, pages are 4Kb in
size.

parity checking.  A scheme used to detect errors in memory. A 9th bit (the
parity bit) is added to every byte, and is set in such a way that the total
number of on bits for every byte is either even (even parity) or odd (odd
parity). If the system encounters a byte that displays even parity on an odd
parity memory system (or if odd parity is detected on an even parity system),
then a parity error occurs.

parity memory.  A type of system RAM that includes a parity bit to detect
memory errors.

PCI (Peripheral Component Interconnect).  A local bus architecture developed by
Intel that is used extensively on pentium systems.

PCMCIA (Personal Computer Memory Card International Association).  (1) A
hardware specification for the credit-card sized peripherals (called PC Cards
or just PCMCIA cards) used in many notebook computers.  (2) The consortium of
hardware manufacturers that developed the aforementioned specification.

peer-to-peer networking.  A networking scheme that allows machines on a network
to share one another's resources, such as printers and hard drives. Unlike a
client/server environment, there need not be a dedicated file server on a
peer-to-peer network. All systems on the LAN are "equals" (hence the term
"peer"). See also client and server.

plug-and-play.  An extension to the ISA specification developed by Intel,
Microsoft and others. Plug-and- Play attempts to simplify configuration of PC's
by using better resource management and automatic configuration of adapters.

point enablers.  An older type of client enabler for PCMCIA cards that does not
use Card or Sockets Services, but rather interfaces directly with the card.
Point enablers are very hardware specific, and have generally given way to
client enablers. See also client enablers.

POST (Power On Self Test).  A set of diagnostic programs built into the ROM of
a PC that perform a hardware test every time the system is powered up.

preemptive multitasking.  A multitasking scheme in which the operating system
has absolute control over processor time.

Presentation Manager (PM).  The graphical user interface used by OS/2.

privilege level, or ring.  In the 80386 microprocessor architecture, the level
of authority at which a program executes. There are four privilege levels
(0-3), and programs running in lower (higher numbered) privilege levels do not
have access to resources controlled by programs running at higher privilege
levels. IOPL in OS/2 is equiavalent to ring 2.

process.  When pertaining to OS/2, a process is a running program.

protected mode.  A mode available in 80286 and above microprocessors that
allows the processor to directly address memory over 1Mb. Protected mode also
allows access to the ring protection, memory isolation, and virtual 86 features
of 386 and above microprocessors, and is the mode used by OS/2.

PSHC (Personal Systems Help Center).  The support center responsible for
supporting IBM PC dealers and customers who purchase IBM PC systems.

PSP (Personal Software Products).  The division of IBM responsible for
developing, marketing, and supporting OS/2.

QCONFIG.  A system information tool provided with IBM PC-DOS 6 and above.
QCONFIG produces a several page report listing the various hardware and
operating system components of the system.

RAID (Redundant Array of Inexpensive Disks).  A  scheme used to create an
extremely large logical drive by transparently linking together many smaller
hard drives. There are numerous specifications and implementations of RAID,
each with varying degrees of performance and fault tolerance features. RAID is
used primarily by file servers.

RAM (Random Access Memory).  A type of memory in a PC that can both be read
from and written to. The contents of RAM are volatile and disappear in the
absence of electrical current. The term "memory" in this work refers to RAM
unless otherwise noted. Contrast with ROM.

real mode.  The default mode of operation for 80x86 microprocessors, and the
only mode of operation for 8086 and 8088 processors. Processors operating in
real mode can only address 1Mb of memory.

reference disk.  A bootable diskette that is used to configure a microchannel
PC. This diskette may also contain ABIOS files. The contents of the reference
disk may also be present on a special invisible hard drive partition (IML
partition) on the PC. See also ABIOS.

resource manager.   The software component in OS/2 WARP responsible for
allocating hardware resources to OS/2 device drivers.

ROM.   A type of memory in a PC that can only be read from, not written to. The
contents of ROM are permanent and remain even in the absence of electrical
current. Contrast with RAM.

SCSI (Small Computer Systems Interface).  A versatile interface for connecting
various types of I/O devices, such as hard drives, scanners, CD-ROM's and tape
drives, to a PC.

server.  In a client/server scheme, the server is an entity that controls and
allocates resources among several requesting entities known as clients. In most
client/server networking environments, a single high end system is dedicated as
a file server. See also client.

service pack.  A set of diskettes used to update an existing installation of
OS/2 to newer code. Service packs typically incorporate problem fixes and may
include new drivers, but will typically not add new functionality.

SIMM (Single In-line Memory Modules).  A type of memory module used as main
system RAM by most modern PC's.

socket services.  The software component of the PCMCIA architecture that acts
as an interface between card services and the PCMCIA socket controller. See
also card services.

specific DOS session.  A VDM in which a real copy of DOS is booted, either from
diskette or an image file on the hard drive. See also virtual DOS machine
(VDM).

superclient driver.  A generic client enabler that can drive a variety of
PCMCIA cards, usually various types of modems and networking cards. See also
client enablers.

SVGA (Super VGA).  A loosely defined term used to describe video adapters that
provide high resolution graphics modes above standard VGA (640 X 480 X 16
colors). Virtually all modern video adapters fall into this category.

SWAPPER.DAT.  The file used by the OS/2 virtual memory subsystem to hold the
contents of memory that have been swapped to the hard drive. See also virtual
memory.

system resources.  A collective term used to describe a number of hardware
items (such as IRQ's, DMA channels, etc.) and software data structures. The key
thing to remember about resources is that they are finite in quantity and are
often competed for by applications and hardware devices.

TCP/IP.  A set of networking protocols and associated utilities, used primarily
by the Internet.

terminator.  A device placed on the end of a SCSI chain, used to prevent
electrical signals from reverberating through the chain and interfering with
the operation of the devices on the chain.

thread.  The smallest dispatchable unit in OS/2. A process in OS/2 may have
several threads (multithreadedness) of execution. DOS and Windows applications
typically have only one (singlethreadedness).

TSR (Terminate-and-Stay-Resident).  A special type of DOS program that loads
into memory and remains inactive until invoked; usually by pressing some key
combination. Unlike ordinary applications, several TSR's can coexist in memory
in a DOS session at once.

Upper Memory Area, UMA.  The 384Kb of memory address space between 640Kb and
1Mb. This area was reserved for system use by the original PC, but many areas
are unused.

upper memory blocks (UMB's).  Unused regions in the upper memory area.

VCPI.  An obsolete method for accessing extended memory. VCPI has fallen out of
use because of its inherent incompatibility with multitasking operating
systems, including OS/2.

VGA (Video Graphics Array).  A standard type of graphics adapter developed by
IBM, capable of up to 640 X 480 X 16 colors. VGA is supported by most modern
video adapters, and is used to provide a "lowest common denominator" level of
compatibility between video adapters of different brands.

virtual 86 mode.  A mode of 80386 and above microprocessors that allows several
DOS applications to execute simultaneously, each in its own address space. Each
application believes it is running on an 8086 system and has the processor all
to itself.

virtual DOS machine, (VDM).  An environment created under OS/2 and other
advanced operating systems that emulates a DOS environment. Programs running
under VDM's run exactly as they would in pure DOS. VDM's are made possible by
the virtual 86 mode of 80386 and above microprocessors. See also virtual 86
mode.

virtual device driver (VDD).  A form of device driver provided with OS/2.
Virtualized device drivers allow several DOS applications running
simultaneously under OS/2 to access the same peripherals. VDD's consume
negligible amounts of memory in VDM's, and simply route access requests through
the native OS/2 device driver.

virtual memory.  A technique for using hard disk space as memory. Unused
portions of memory are written to the hard disk and kept there until they are
needed again. This is referred to as swapping or paging. Extensive use of
virtual memory can slow system performance.

VL-Bus (VESA Local Bus).  A local bus architecture developed by the Video
Electronics Standards Association.

workgroup sofware.  Software designed to allow users to collaborate on a group
project by sharing information over a LAN.

XMS (eXtended Memory Specification).  A programming specification for accessing
extended memory from DOS programs.


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

ABIOS (Advanced Basic Input/Output System).  A set of sofware extensions to the
BIOS ROM of a PC. ABIOS code is typically loaded from a special partition on
the hard drive at startup. See also BIOS.


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

ABIOS Patch.  A procedure needed to install OS/2 on some microchannel systems.
The patch typically involves copying all the ABIOS.SYS and all *.BIO files from
the system's reference diskette to a copy of the OS/2 installation diskette.


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

argument, or parameter.  A value specified on the end of a command line or
statement used to pass input to the command or statement being executed.
Arguments that can vary in value are often represented by a generic
placeholder, such as dddd-dddd for address ranges.


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

AUTOEXEC.BAT.  A batch file started by a DOS or WIN-OS/2 session that executes
automatically every time the session is started. AUTOEXEC.BAT consists of a
series of DOS commands just as they would be entered at the command line.


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

BIOS (Basic Input/Output System).  A set of programs built into the ROM of a PC
that act as a low level interface between the computer and various peripherals.


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

binary search.  An extremely efficient search algorithm which reduces the
amount of data to be searched by 50% through each iteration. Binary searches
are performed in log[2] n time, where n represents the total number of items to
be searched. Binary searches require that the list be sorted before the search
is performed.


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

bit.  Short for binary digit. A binary digit may either be 0 or 1, and usually
corresponds to a low or high signal, receptively,  in a computer circuit.


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

boot ROM.  On a SCSI adapter, the chip containing the code necessary to allow
the system to boot from a SCSI hard drive.


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

boot manager.  One of two methods provided with OS/2 for allowing multiple
operating systems to reside on the same system. Each operating resides in its
own partition. The user chooses which partition to boot from a menu displayed
at startup. See also Dual Boot.


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

bus.  The circuitry used to connect various components inside the PC.


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

bus architecture.  A hardware specification that determines how adapter cards
communicate with the computer system.


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

bus mastering.  A feature supported by some bus architectures that allows an
adapter card in the system to take control of the bus.


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

bytes.  An eight digit binary number. The smallest addressable unit of memory
in a computer. In most computers, a character is represented by one byte.


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

card services.  The software component of the PCMCIA architecture that
allocates and manages system resources used by PCMCIA cards.


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

CID (Configuration-Installation-Distribution).  A feature of OS/2 LAN Server
that allows OS/2 and other software products to be installed over a LAN.


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

client.  In a client/server scheme, the client is an entity that requests
resources from another entity (the server) that controls those resources. In a
client/server networking environment, the client systems are often called
workstations. See also server.


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

client enabler.  The card-specific software component of the PCMCIA
architecture that allows the PCMCIA card to be recognized by applications.


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

cluster, or allocation unit.  The smallest amount of disk space that may be
allocated by a file system at any given time. The size of the cluster will
depend on the size of the hard drive and the file system used, but will always
be some multiple of 512 bytes.


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

CONFIG.SYS.  A file used by OS/2 at system startup to configure various
operating system parameters and to load device drivers.


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

conventional memory.  The first 640Kb of memory address space in a PC.
Conventional memory is the only memory available to pure DOS programs.


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

cooperative, or voluntary multitasking.  A multitasking scheme in which running
applications voluntarily allow the operating system to manage processor time.


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

CRC (Cyclic Redundancy Check) error.  An error that usually occurs when part of
a disk's magnetic recording surface has weakened to the point that its data has
become unreadable. A CRC error indicates that the data on that portion of the
disk is unreadable.


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

cross linked files.  Two or more files on a disk that claim the same segment of
data on the disk as their own.


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

destructive MAKEINI.  A procedure for rebuilding the OS/2 desktop that
recreates the default desktop from scratch. All user customizations and
additions to the OS/2 desktop are lost.


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

device driver.  Software code that allows the operating system to access and
operate various peripherals, such as multimedia, networking, and video
adapters. In OS/2, device drivers are typically specified and configured in the
CONFIG.SYS.


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

DMA channel.  A hardware signal used by devices to perform DMA (Direct Memory
Access). DMA allows adapter cards to access system memory directly without
having to go through the microprocessor.


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

DOS Extender.  A program that allows specially written DOS applications to use
extended memory.


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

DPMI (DOS Protected Mode Interface) memory.  A specification for accessing
extended memory from DOS applications. DPMI is the preferred method of
accessing extended memory from DOS programs.


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

dual boot.  One of two methods of allowing DOS and OS/2 to reside on the same
system. Dual boot allows OS/2 and DOS to reside on the same hard drive
partition. The user is able to reboot the machine into either operating system
by clicking an icon or entering a command. See also Boot Manager.


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

EA DATA. SF.  A file that contains the extended attributes for all files on the
drive. Each file on the hard drive has a pointer in its directory entry that
points to an offset in this file. EA DATA. SF is only present on FAT volumes.
Damage to this file can result in operating system failure.


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

ECC (Error Checking and Correcting) memory.  An expensive type of memory that
uses redundant memory to both detect and correct memory errors.


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

EDO (Extended Data Out) memory.  A new type of high performance memory that
allows both read and write operations to occur simultaneously on the same chip.


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

EIDE (Enhanced Integrated Drive Electronics).  An enhanced version of the IDE
specification that allows larger, faster hard drives as well as other types of
devices, such as CD-ROM's, to be attached to the PC via the IDE interface. See
also IDE.


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

EISA (Extended Industry Standard Architecture).  An improved high speed bus
developed by Compaq and others, based on ISA.  See also ISA.


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

EMS memory.  See entry for LIM Memory.


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

exception handler.  The component of the operating system that handles errors
(exceptions) that are generated by the microprocessor. The exception handler
determines the type of the error, and takes appropriate action (such as
displaying an error message).


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

extended attributes.  A set of data structures associated with a file that
stores information concerning the file, such as the file's icon, long file name
(for FAT drives), comments, and information concerning desktop objects that are
associated with the file.


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

extended memory.  The memory address space above 1Mb that is directly
accessible by 286 and above microprocessors operating in protected mode.


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

external (or level 2) cache.  A special type of fast RAM used to cache
read/write operations between the microprocessor and RAM. Most modern
microprocessors are much faster than RAM, and require external cache for best
performance.


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

FAT (File Allocation Table).  One of two file systems supported by OS/2. FAT
was originally designed for (and is still used by) DOS, and is internally
supported by OS/2 without special drivers. See also HPFS.


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

fault tolerance.  A set of features designed to allow enhance a product's
ability to recover in the event of an error.


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

file fragmentation.  The condition that occurs when a file is stored in
non-contiguous locations on the hard drive. Severe file fragmentation can
adversely affect performance.


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

file system.  A set of data structures that determine how files are physically
stored and accessed on a disk.


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

FixPak.  A set of diskettes that is used to apply corrective service (bug
fixes) to an existing installation of OS/2. FixPaks may not be publicly
available, and are often specific to a particular set of symptoms.


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

FLASH BIOS.  A special type of BIOS that is stored in nonvolatile RAM instead
of ROM. FLASH BIOS is popular in many modern systems because it can be easily
upgraded by the user without replacing hardware.  See also BIOS.


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

High Memory Area, or HMA.  The first 64Kb of address space above 1Mb. The HMA
is directly accessible by 286 and above microprocessors operating in real mode.


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

hotfix.  A fault tolerance feature of HPFS that allows data to be written to
temporary areas on the hard drive (the hotfixes) if bad sectors on encountered.
At a later time (when CHKDSK is run), the data is written to a permanent
location and the bad sectors are marked as such by the file system.


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

hot plugging.  The practice of removing and reinserting PCMCIA cards (or other
hardware devices) while the system is powered up.


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

HPFS (High Performance File System).  One of two file systems supported by
OS/2. HPFS was designed specifically for OS/2, and is optimized for use with
large hard disks. HPFS support requires a special driver. See also FAT.


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

IDE (Integrated Drive Electronics).  A popular specification for attaching hard
drives to a PC. As its name implies, IDE incorporates most of the hard drive
controller hardware onto the drive itself. See also EIDE.


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

internet.  A vast global public network consisting of government, corporate,
and educational institutions. In recent years the internet has experienced
phenomenal growth, with many service providers providing access directly to end
users.


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

interrupt (IRQ).  An electrical signal generated by a hardware component to
request the immediate attention of the operating system. The operating system
processes the interrupt by passing control to a piece of code which handles the
event signaled by the hardware.


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

I/O port.  A range of memory addresses that is used  by the operating system to
communicate with a hardware device, such as a COM port or network adapter.


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

ISA (Industry Standard Architecture), or AT Bus.  The original bus architecture
used by the IBM PC AT.  ISA remains the most popular bus for PC's.


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

LAN Server.  A popular client/server networking environment for PC's,
manufactured by IBM. The server software itself runs under OS/2.


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

lazy write caching.  A caching scheme that holds data to be written to the disk
in cache memory until the disk is idle. When the disk has remained idle for a
specified period of time, the contents of the cache are written (flushed) to
the disk.


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

local area network (LAN).  A network composed of several interconnected PC's.
LAN's allow users on several different computers to share data and
applications.


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

LIM (Lotus-Intel-Microsoft) memory, EMS memory,  Expanded memory.  An early
scheme designed to allow DOS programs running on 8088 and 8086 systems access
to memory outside the processor's addressing capabilities.


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

local bus.  A term used to describe several new high speed bus architectures
that attempt to avoid speed bottlenecks by linking directly into the
microprocessor bus.


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

lost allocation unit (or lost cluster).  A segment of data on the hard disk
that is marked as in use by the operating system, but does not belong to any
particular file.


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

maintenance desktop.  An option in the recovery choices menu that allows you to
repeat the second half of the OS/2 installation procedure.


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

master/slave.  Only one device may have control of an IDE chain. This device is
the master, and is usually the first physical device on the chain. The other
IDE device is called the slave. IDE devices typically have jumpers that allow
them to be configured either as master or slave. Some devices also have a
"neutral" setting that is used if the device is the only one on the chain.


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

memory leak.  A phenomenon that occurs when an application allocates memory,
but never de-allocates the memory when the application exits or no longer needs
the memory. Memory leakage is typically due to a programming error, and can
cause excessive growth of the swap file.


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

memory manager.  In PC-DOS, a program that manages access to the memory
resources of a PC.


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

microchannel (MCA).  A proprietary high speed bus architecture developed by IBM
for the PS/2 line of personal computers.


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

microprocessor.  The chip in a PC responsible for interpreting and executing
instructions. The microprocessor may be thought of as the "brain" of the
computer.


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

migrate.  The term used to describe the process of configuring programs to run
from the OS/2 desktop.


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

multitasking.  A feature of OS/2 and other advanced operating systems that
allows several programs to execute simultaneously. Compare with multithreading.


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

multithreading.  A feature of OS/2 and other advanced operating systems that
allows a single application to perform several tasks simultaneously. Compare
with multitasking.


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

Netware.  A popular client/server networking evironment for PC's, manufactured
by Novell.


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

network interface card (NIC).  An adapter card that allows a PC to hook into a
local area network.


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

non-destructive MAKEINI.  The procedure for rebuilding the OS/2 desktop that
resets the default system objects to default values, leaving any user additions
and customizations intact.


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

non-parity memory.  A type of memory used in many low end systems that does not
include any error detection capabilities.


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

OS2.INI.  One of two files that comprise the OS/2 Desktop. OS2.INI contains
user interface customizations, abstract object definitions, and configuration
parameters for OS/2 applications.


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

OS2SYS.INI.  One of two files that comprise the OS/2 Desktop. OS2SYS.INI
contains hardware configuration information, window positions, and other system
information.


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

page frame.  A fixed number of contiguous memory pages. In DOS memory
management, a 64Kb page frame is used as a "window" into which EMS memory is
remapped, making it accessible to older DOS programs.


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

page.  An arbitrary unit of memory consisting of a fixed number of bytes. When
pertaining to OS/2 and the 386 microprocessor architecture, pages are 4Kb in
size.


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

parity checking.  A scheme used to detect errors in memory. A 9th bit (the
parity bit) is added to every byte, and is set in such a way that the total
number of on bits for every byte is either even (even parity) or odd (odd
parity). If the system encounters a byte that displays even parity on an odd
parity memory system (or if odd parity is detected on an even parity system),
then a parity error occurs.


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

parity memory.  A type of system RAM that includes a parity bit to detect
memory errors.


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

PCI (Peripheral Component Interconnect).  A local bus architecture developed by
Intel that is used extensively on pentium systems.


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

PCMCIA (Personal Computer Memory Card International Association).  (1) A
hardware specification for the credit-card sized peripherals (called PC Cards
or just PCMCIA cards) used in many notebook computers.  (2) The consortium of
hardware manufacturers that developed the aforementioned specification.


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

peer-to-peer networking.  A networking scheme that allows machines on a network
to share one another's resources, such as printers and hard drives. Unlike a
client/server environment, there need not be a dedicated file server on a
peer-to-peer network. All systems on the LAN are "equals" (hence the term
"peer"). See also client, and server.


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

plug-and-play.  An extension to the ISA specification developed by Intel,
Microsoft and others. Plug-and- Play attempts to simplify configuration of PC's
by using better resource management and automatic configuration of adapters.
OS/2 currently has no built in support for the Plug-and-Play BIOS.


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

point enablers.  An older type of client enabler for PCMCIA cards that does not
use Card or Sockets Services, but rather interfaces directly with the card.
Point enablers are very hardware specific, and have generally given way to
client enablers. See also client enablers.


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

POST (Power On Self Test).  A set of diagnostic programs built into the ROM of
a PC that perform a hardware test every time the system is powered up.


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

preemptive multitasking.  A multitasking scheme in which the operating system
has absolute control over processor time.


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

Presentation Manager (PM).  The graphical user interface used by OS/2.


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

privilege level, or ring.  In the 80386 microprocessor architecture, the level
of authority at which a program executes. There are four privilege levels
(0-3), and programs running in lower (higher numbered) privilege levels do not
have access to resources controlled by programs running at higher privilege
levels. IOPL in OS/2 is equiavalent to ring 2.


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

process.  When pertaining to OS/2, a process is a running program.


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

protected mode.  A mode available in 80286 and above microprocessors that
allows the processor to directly address memory over 1Mb. Protected mode also
allows access to the ring protection, memory isolation, and virtual 86 features
of 386 and above microprocessors, and is the mode used by OS/2.


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

PSHC (Personal Systems Help Center).  The support center responsible for
supporting IBM PC dealers and customers who purchase IBM PC systems.


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

PSP (Personal Software Products).  The division of IBM responsible for
developing, marketing, and supporting OS/2.


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

QCONFIG.  A system information tool provided with IBM PC-DOS 6 and above.
QCONFIG produces a several page report listing the various hardware and
operating system components of the system.


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

RAID (Redundant Array of Inexpensive Disks).  A  scheme used to create an
extremely large logical drive by transparently linking together many smaller
hard drives. There are numerous specifications and implementations of RAID,
each with varying degrees of performance and fault tolerance features. RAID is
used primarily by file servers.


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

RAM (Random Access Memory).  A type of memory in a PC that can both be read
from and written to. The contents of RAM are volatile and disappear in the
absence of electrical current. The term "memory" in this work refers to RAM
unless otherwise noted. Contrast with ROM.


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

real mode.  The default mode of operation for 80x86 microprocessors, and the
only mode of operation for 8086 and 8088 processors. Processors operating in
real mode can only address 1Mb of memory.


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

reference disk.  A bootable diskette that is used to configure a microchannel
PC. This diskette may also contain ABIOS files. The contents of the reference
disk may also be present on a special invisible hard drive partition (IML
partition) on the PC. See also ABIOS.


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

resource manager.   The software component in OS/2 WARP responsible for
allocating hardware resources to OS/2 device drivers.


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

ROM.   A type of memory in a PC that can only be read from, not written to. The
contents of ROM are permanent and remain even in the absence of electrical
current. Contrast with RAM.


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

SCSI (Small Computer Systems Interface).  A versatile interface for connecting
various types of I/O devices, such as hard drives, scanners, CD-ROM's and tape
drives, to a PC.


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

server.  In a client/server scheme, the server is an entity that controls and
allocates resources among several requesting entities known as clients. In most
client/server networking environments, a single high end system is dedicated as
a file server. See also client.


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

service pack.  A set of diskettes used to update an existing installation of
OS/2 to newer code. Service packs typically incorporate problem fixes and may
include new drivers, but will typically not add new functionality.


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

SIMM (Single In-line Memory Modules).  A type of memory module used as main
system RAM by most modern PC's.


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

socket services.  The software component of the PCMCIA architecture that acts
as an interface between card services and the PCMCIA socket controller. See
also card services.


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

specific DOS session.  A VDM in which a real copy of DOS is booted, either from
diskette or an image file on the hard drive. See also virtual DOS machines
(VDM).


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

superclient driver.  A generic client enabler that can drive a variety of
PCMCIA cards, usually various types of modems and networking cards. See also
client enablers.


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

SVGA (Super VGA).  A loosely defined term used to describe video adapters that
provide high resolution graphics modes above standard VGA (640 X 480 X 16
colors). Virtually all modern video adapters fall into this category.


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

SWAPPER.DAT.  The file used by the OS/2 virtual memory subsystem to hold the
contents of memory that have been swapped to the hard drive. See also virtual
memory.


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

system resources.  A collective term used to describe a number of hardware
items (such as IRQ's, DMA channels, etc.) and software data structures. The key
thing to remember about resources is that they are finite in quantity and are
often competed for by applications and hardware devices.


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

TCP/IP.  A set of networking protocols and associated utilities, used primarily
by the Internet.


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

terminator.  A device placed on the end of a SCSI chain, used to prevent
electrical signals from reverberating through the chain and interfering with
the operation of the devices on the chain.


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

thread.  The smallest dispatchable unit in OS/2. A process in OS/2 may have
several threads (multithreadedness) of execution. DOS and Windows applications
typically have only one (singlethreadedness).


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

TSR (Terminate-and-Stay-Resident).  A special type of DOS program that loads
into memory and remains inactive until invoked; usually by pressing some key
combination. Unlike ordinary applications, several TSR's can coexist in memory
in a DOS session at once.


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

Upper Memory Area, UMA.  The 384Kb of memory address space between 640Kb and
1Mb. This area was reserved for system use by the original PC, but many areas
are unused.


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

upper memory blocks (UMB's).  Unused regions in the upper memory area.


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

VCPI.  An obsolete method for accessing extended memory. VCPI has fallen out of
use because of its inherent incompatibility with multitasking operating
systems, including OS/2.


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

VGA (Video Graphics Array).  A standard type of graphics adapter developed by
IBM, capable of up to 640 X 480 X 16 colors. VGA is supported by most modern
video adapters, and is used to provide a "lowest common denominator" level of
compatibility between video adapters of different brands.


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

virtual 86 mode.  A mode of 80386 and above microprocessors that allows several
DOS applications to execute simultaneously, each in its own address space. Each
application believes it is running on an 8086 system and has the processor all
to itself.


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

virtual DOS machine, (VDM).  An environment created under OS/2 and other
advanced operating systems that emulates a DOS environment. Programs running
under VDM's run exactly as they would in pure DOS. VDM's are made possible by
the virtual 86 mode of 80386 and above microprocessors. See also virtual 86
mode.


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

virtual device driver (VDD).  A form of device driver provided with OS/2.
Virtualized device drivers allow several DOS applications running
simultaneously under OS/2 to access the same peripherals. VDD's consume
negligible amounts of memory in VDM's, and simply route access requests through
the native OS/2 device driver.


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

virtual memory.  A technique for using hard disk space as memory. Unused
portions of memory are written to the hard disk and kept there until they are
needed again. This is referred to as swapping or paging. Extensive use of
virtual memory can slow system performance.


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

VL-Bus (VESA Local Bus).  A local bus architecture developed by the Video
Electronics Standards Association.


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

workgroup sofware.  Software designed to allow users to collaborate on a group
project by sharing information over a LAN.


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

XMS (eXtended Memory Specification).  A programming specification for accessing
extended memory from DOS programs


ΓòÉΓòÉΓòÉ 16. Appendix F. The OS/2 Professional Certification Program ΓòÉΓòÉΓòÉ

APPENDIX F. THE OS/2 PROFESSIONAL CERTIFICATION PROGRAM

If your job involves installing, supporting, or maintaining OS/2, you should
consider the professional certification program from IBM. Professional
Certification provides numerous benefits, including recognition as an industry
professional.

IBM has a number of professional certification programs available for OS/2 and
LAN Server related products, including Certified OS/2 Engineer, Certified LAN
Server Engineer, Certified LAN Server Administrator, Certified OS/2 Instructor,
and Certified LAN Server Instructor. To become certified on one of the above
areas, you must take and pass a series of exams. There are many benefits to
becoming OS/2 certified, including:

o   Industry recognition as an OS/2 professional. When you have successfully
    passed the certification exams, your name will be added to the Professional
    Certification Program Directory. This directory is made available to
    companies who are seeking qualified OS/2 professionals.

o   Priority Technical Support. If you support OS/2 for others, obtaining
    prompt technical support is critical. As a Certified OS/2 Engineer, you
    will receive a higher priority of support when you call in to the OS/2
    support center.

o   Free on-line technical publications. As a certified OS/2 engineer, you will
    receive free copies of the Technical Connection and OS/2 on-line book
    collection on CD. The Technical Connection CD contains a wealth of
    technical support information, including problem-resolution databases,
    CSD's, device drivers, "white papers," and product announcements. The
    On-Line Book Collection CD contains manuals and redbooks for several OS/2
    and LAN related products.

o   Free subscriptions to IBM technical publications. As a Certified OS/2
    Engineer, you will receive free subscriptions two IBM technical
    publications: Personal Systems Technical Solutions and the Personal
    Software Technical Newsletter.

Course materials, test objectives, and other resources are available to help
you prepare for the exams. For more information on the certification program,
including test scheduling and student kits, call Drake Testing services at
1-800-959-EXAM.

You can also write to the following address to receive information on the
professional certification program:

Professional Certification Program from IBM
IBM Corporation
11400 Burnet Road, Internal ZIP 3013
Austin, Texas  78758


ΓòÉΓòÉΓòÉ 17. Appendix G. For Further Reading ΓòÉΓòÉΓòÉ

APPENDIX G. FOR FURTHER READING

The following IBM publications were instrumental in the preparation of this
document. You may wish to consult these documents if you need more detailed
information on a particular topic than was presented in this work. Requests for
technical information about IBM products should be made to your IBM Authorized
Dealer or your IBM Marketing Representative.

83G8712     IBM OS/2 Warp User's Guide to OS/2

GG24-4426-00  OS/2 Warp Version 3 and BonusPak "Exploring a New Generation"

GG24-4212-00  OS/2 2.11, OS/2 for Windows, New OS/2 Device Drivers, and Updates
to OS/2 2.1

GG24-3948-00  OS/2 2.1 Technical Update

GG24-4346-00  OS/2 2.11 Power Techniques

The following non-IBM books are recommended to readers who are interested in
more in depth OS/2 information than what is presented in the User's Guide.
These books are recommended for the "intermediate" to "advanced" user. Note
these books are listed here because they are familiar to the author. Their
presence in this section in no way represents an official endorsement from IBM.

Deitel, H.M. and Kogan, M.S. The Design of OS/2. New York: Addison-Wesley,
1992.

Mark Minasi, et al. Inside OS/2 Warp version 3. Indianopolis, Indiana: New
Riders Publishing, 1994.

Moskowitz and Kerr, et al. OS/2 Warp Unleashed. Indianopolis, Indiana: Sams
Publishing, 1994.