Black Box 4/BlackBox.cdr/os2/ps2a_tec.arj/PS2A_TEC.INF

OS/2 Help File | 1992-05-11 | 426.5 KB | 11,475 lines

ΓòÉΓòÉΓòÉ 1. About PS/2 Assistant ΓöÇ Tutorial ΓòÉΓòÉΓòÉ

                               IBM PS/2 ASSISTANT (TM)
                          Developed by Mark T. Chapman
                         IBM NDD National Support Center
                  2300 Windy Ridge Parkway, Marietta, GA. 30067
                 PROFS ID: DAYVM2(MCHAPMAN) ΓöÇ Tie Line: 269-6432
                     Prodigy ID: JPJS05A ΓöÇ BBS: 404-835-6600
                    Copyright (C) IBM Corporation, 1989-1992

OVERVIEW
There are many sources of information available from IBM, including
announcement letters, service manuals, programming and technical reference
manuals, how-to "cookbooks," electronic bulletin boards (both public and
IBM-use only), and others.  The IBM PS/2 Assistant is an attempt to bring much
disparate and often difficult to find information together into one easy-to-use
"electronic book."

The IBM PS/2 Assistant is an online help tool composed of PS/2 and OS/2-related
marketing, service, technical and general information.  The books include the:

 1. IBM PS/2 Marketing Assistant (filename PS2A_MKT.INF), including:

   o IBM hardware and software pricing and part number information.
   o Promotional and upgrade information.
   o IBM publication ordering information.
   o Marketing Qs & As, and more.

 2. IBM PS/2 Service Assistant (PS2A_SVC.INF), including:

   o Hardware and OS/2 error code information.
   o DOS and OS/2 CSD information.
   o Hardware and software service tips and Qs & As, and more.

 3. IBM PS/2 Technical Assistant (PS2A_TEC.INF), including:

   o Tutorials on Micro Channel Advantages, and Expanded vs. Extended Memory,
   o Hardware and software Technical tips and Qs & As, and more.

 4. IBM PS/2 Technical Specifications Assistant (PS2A_TSP.INF), including:

   o Lengthy technical specifications documents for every PS/1 and PS/2 system
     and display, past and present.

 5. IBM PS/2 General Information Assistant (PS2A_GEN.INF), including:

   o IBM and non-IBM telephone numbers.
   o List of OS/2-related BBSes.
   o Acronym and abbreviation list.
   o List of OS/2-related books available in bookstores, and more.

The reason for having a number of different books instead of just one large one
is two-fold.  First, there is so much information provided that it might be
awkward to use, and would take longer to search through than smaller books.
And second, by dividing up all of this information into related subject matter,
those who don't need certain categories of information (such as service tips,
for example), can delete entire books to save disk space.  Besides, these files
may be logically linked together and viewed or searched as one large book, at
your preference.  (This procedure is explained in the accompanying PS2ASST.TXT
file.)  For convenience, the files will be collectively called the "PS/2
Assistant" throughout the rest of this document.

Not only is the information more "centrally located" this way than distributed
across all the individual documents, but due to its electronic nature, the
specific information you seek can be found more quickly and easily.  The source
information is compiled into binary files that take roughly half as much disk
space as ASCII files would.  And since the compiler also creates a "data
dictionary" of all words and numbers anywhere in the files, all occurrences can
be found and displayed on-screen in only a few seconds via the search facility
provided.  In addition, hypertext links (hyperlinks) allow you to jump from
section to section within a book without ever having to return to the Table of
Contents.  Hyperlinks are also used to display popup footnote windows at the
point of the footnote reference, rather than making you have to scroll down to
the bottom of a page, or the end of a chapter, to find the footnoted
information.

The PS/2 Assistant is created by compiling a scripted ASCII text file, using
the Information Presentation Facility (IPF) Tag Language and Compiler.  They
are included in the OS/2 V1.2 and 1.3 Programming Tools and Information
toolkits (P/Ns 6024929 or 85F1671).  The PS/2 Assistant requires OS/2 1.2 (or
later) to operate, because it uses the OS/2 VIEW.EXE command to access the
files.  This is the same command used to display the online OS/2 Command
Reference.  Since both files were created with the same compiler, and are
displayed by the same command, they look and act very much alike.  So if you
know how to use one, you also know how to use the other.

Note:  The PS/2 Assistant was tested, and does work, across an OS/2 LAN Server
V1.2 or 1.3 network, relieving the need for disk space on the requester, not to
mention not having to keep all those requesters updated with the latest
versions of the PS/2 Assistant books.  (For instructions on Setting Up an OS/2
LAN Server to Share Online Books, see the document by the same name in the
Networking Tips section of the PS/2 Technical Assistant.)

HOW TO USE THE PS/2 ASSISTANT
Before you begin to use this tool, it is helpful to understand how to:

o Expand the Contents to see all available topics
o Obtain additional information for a highlighted word or phrase
o Use action bar choices.

How to use the Table of Contents
When the Contents window first appears, some topics have a plus (+) sign beside
them.  The plus sign indicates that additional topics are available.

To expand the Contents if you are using a mouse, click on the plus sign.  If
you are using the keyboard, use the Up or Down Arrow key to highlight the
topic, and press the plus (+) key. For example, PS/2 Part Number / Pricing /
Availability List has a plus sign beside it.  To see the complete list of Part
Numbers, etc, click on the plus sign or highlight that topic and press the plus
(+) key.

To view a topic, double-click on the topic (or press the Up or Down Arrow key
to highlight the topic, and then press the Enter key).

Note:  To exit from any panel (window), including this one, simply press the
ESC key, or double-click on the icon to the left of the panel title bar (NOT
the one to the left of the PS/2 Assistant title bar, or you will close the PS/2
Assistant).  This will return you to the point from which you entered the panel
(either the Table Of Contents or another panel).  This may be done a number of
times in succession to step back through layers of panels, or until the TOC is
reached.

How to obtain additional information
After you select a topic, the information for that topic appears in a window.
Words, phrases, or numbers highlighted like this or this indicate that
additional information is available, either in the form of a footnote, or
sometimes an entire section.  Hyperlinks are used in some areas to help you
jump from one section of a document directly to another, without having to
return to a menu. (If you don't find this color to be easily identifiable as a
hyperlink, you may change the color, as described below.)  Use the mouse, or
Tab and Enter keys, to move between all the hyperlinks within a document.  For
example:

Certain words in the following section are highlighted in this way.  If you are
using a mouse, double-click on the highlighted words.  If you are using a
keyboard, press the Tab key to move from one highlighted word to the next, (or
Shift-Tab to backup) and then press the Enter key.  Additional information will
appear in a pop-up window.

Note:  The windows that pop up when you double-click on a hypertext link are
sizable.  Simply drag the sides or corners of the windows to the desired size
and shape, just as you would any other PM window.

Note:  Headings are assigned the color red throughout the PS/2 Assistant. The
Change Bars (|), which indicate additions or revisions since the last release
of the PS/2 Assistant, are also highlighted in red to make them easier to find.
(All other colors are as set by your OS/2 Control Panel selections.  If a
color, or combination of colors, is not to your liking, you may change them to
something more pleasing. The operative choices are:  Help Text, Help
Background, and Help Highlight.)

Tip:  An easy way to find ALL changes since the last version is to Search for
the Change Bar character (|).  This can be typed by holding the Shift key while
typing the backslash key.

How to use the Action Bar options
A number of choices are available for managing information presented in the
PS/2 Assistant.  If you want to see more information about these choices, click
on the name of the choice (or press the Tab key to move to the choice and press
Enter).

Help
      Provides online help panels for using the Help facility.

Bookmark
      Allows you to set a placeholder so you can retrieve information of
      interest to you. (This choice is available from the Services pull-down.)

Search
      Allows you to find occurrences of a word or phrase in the current topic,
      selected topics, or all topics. (This choice is available from the
      Services pull-down.)

Print
      Allows you to print one or more topics. (This choice is available from
      the Services pull-down.)

Copy
      Allows you to copy a topic you are viewing to a file you can edit. (This
      choice is available from the Services pull-down.)

Options
      Allows you to change the way your Contents is displayed.

To see the PS/2 Assistant Disclaimer and Trademark Information, select:

                            Disclaimers & Trademarks


ΓòÉΓòÉΓòÉ 1.1. Disclaimer & Trademark Info ΓòÉΓòÉΓòÉ

To return to the About PS/2 Assistant section, select:

                              About PS/2 Assistant

* * * * * * * DISCLAIMER OF LIABILITY * * * * * * *

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.  THE EVALUATION AND USE OF THIS INFORMATION IS A CUSTOMER
RESPONSIBILITY.  IN NO EVENT WILL IBM BE LIABLE FOR ANY DAMAGES, INCLUDING ANY
LOST PROFITS, LOST SAVINGS, OR ANY OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING FROM THE USE OR INABILITY TO USE ANY OF THE INFORMATION PROVIDED HEREIN
EVEN IF IBM HAS BEEN ADVISED OF DAMAGES IN ADVANCE.  SOME STATES DO NOT ALLOW
THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL
DAMAGES, SO THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.

It is possible that this material contains references to, or information about,
IBM products, programs, or services that are not announced or available in
every country in which IBM operates.  Such references or information must not
be construed to mean that IBM intends to announce or make available such
products, programs, or services in any country in which they are not currently
announced or available.  The information herein is intended for use only in the
United States, notwithstanding there may be many similarities between products
marketed worldwide.

Any reference to an IBM product in this document is not intended to state or
imply that only IBM's product may be used.  Any functionally equivalent product
may be used instead, provided that use is in accordance with the manufacturer's
guidelines for that product.

Prices and specifications are subject to change at any time without notice.
Prices are provided for information purposes only, and shall not limit in any
way the remarketers' ability to set their own prices for IBM products.

The contents of this online book are copyrighted by International Machines
Corporation.

                     * * * * * * * TRADEMARKS * * * * * * *

The following trademarks apply to all online information:

o 1-2-3, Agenda, Freelance, Magellan, Notes, and Lotus are registered
  trademarks of Lotus Development Corporation.
o 1-2-3/G and Symphony are trademarks of Lotus Development Corporation.
o 386 MAX, 386 MAX Professional, and Qualitas are trademarks of Qualitas,
  Incorporated.
o 3+ Open and 3Com are trademarks of 3Com Corporation.
o 80286, 80386, 80486, and i486 are trademarks of Intel Corporation.
o Adobe Type Manager and ATM are registered trademarks of Adobe Systems,
  Incorporated.
o ActionMedia and DVI are registered trademarks of Intel Corporation.
o AIX is a Registered trademark of International Business Machines Corporation.
o AIXwindows is a trademark of International Business Machines Corporation.
o Aldus and Pagemaker are registered trademarks of Aldus Corporation.
o Apple is a registered trademark of Apple Computer, Incorporated.
o AppleTalk is a trademark of Apple Computer, Incorporated.
o Application System/400 and AS/400 are registered trademarks of International
  Business Machines Corporation.
o Ashton-Tate is a registered trademark of Ashton-Tate.
o AT&T is a registered trademark of American Telephone and Telegraph.
o Audio Visual Connection is a trademark of International Business Machines
  Corporation.
o Audio-Technica is a registered trademark of Audio-Technica, U.S.,
  Incorporated.
o AutoCAD and AutoSketch are registered trademarks of Autodesk, Incorporated.
o BASIC/2, C/2, COBOL/2, FORTRAN/2, Macro Assembler/2, and Pascal/2 are
  trademarks of International Business Machines Corporation.
o BookManager is a trademark of International Business Machines Corporation.
o CATIA is a trademark of Dassault Systemes
o Chargecard is a trademark of All Computers, Incorporated.
o COBOL/2, COBOL/2 Workbench, and Micro Focus are trademarks of Micro Focus.
o Compaq is a registered trademark of Compaq Computer Corporation.
o Current is a trademark of International Business Machines Corporation.
o D40CHK is a trademark of Dialogic Corporation.
o dBASE II is a trademark of Ashton-Tate.
o dBASE III, dBASE III Plus, and dBASE IV are registered trademarks of
  Ashton-Tate.
o DEC VT220/VT100/VT52 are trademarks of Digital Equipment Corporation.
o DeScribe is a trademark of DeScribe, Incorporated.
o Diablo is a trademark of Xerox Corporation.
o Diconix is a trademark of Eastman Kodak Corporation.
o DIF is a registered trademark of Lotus Development Corporation.
o Digital Research is a registered trademark of Digital Research, Incorporated.
o DiscoverEducation is a trademark of International Business Machines
  Corporation.
o DisplayWrite is a registered trademark of International Business Machines
  Corporation.
o DOS Merge is a trademark of International Business Machines Corporation.
o DOS Server/AADU is a trademark of International Business Machines
  Corporation.
o DXF is a registered trademark of AutoDesk Incorporated.
o EASEL is a registered trademark of Easel Corporation.
o Epson is a registered trademark of Seiko Epson Corporation.
o Etherand is a trademark of International Business Machines Corporation.
o Ethernet is a registered trademark of Xerox Corporation.
o Excelsior is a registered trademark of Excelsior Software, Incorporated.
o Express Publisher is a trademark of Power Up Software Corporation.
o GDDM is a trademark of International Business Machines Corporation.
o GEM and GEM/3 are trademarks of Digital Research, Incorporated.
o Harvard is a trademark of Software Publishing Corporation.
o Hayes is a registered trademark of Hayes Microcomputer Products,
  Incorporated.
o HP is a trademark of Hewlett-Packard Corporation.
o HPGL and Hewlett-Packard are registered trademarks of Hewlett-Packard
  Corporation.
o IBM is a registered trademark of International Business Machines Corporation.
o ImagEdit is a trademark of International Business Machines Corporation.
o Independence Series is a trademark of International Business Machines
  Corporation.
o InfoWindow is a trademark of International Business Machines Corporation.
o Intel is a trademark of Intel Corporation.
o LANSchool is a trademark of Lan Fan Technologies, Incorporated.
o LapStation is a trademark of Axonix Corporation.
o LaserJet and LaserJet Plus are registered trademarks of Hewlett-Packard
  Corporation.
o Lattice is a trademark of Lattice, Incorporated.
o Lexmark is a trademark of Lexmark International, Incorporated.
o LinkWay is a trademark of International Business Machines Corporation.
o M-Motion Video Adapter/A is a trademark of International Business Machines
  Corporation.
o Micro Channel is a trademark of International Business Machines Corporation.
o Microsoft is a registered trademark of Microsoft, Incorporated.
o Motif is a trademark of the Open Systems Foundation.
o MS-DOS is a registered trademark of Microsoft Corporation.
o MultiView is a trademark of JSB Computer Systems Limited.
o Network File System and NFS are trademarks of Sun Microsystems, Incorporated.
o NextStep is a trademark of NeXT, Incorporated.
o Netware, Advanced Netware, Novell, and SFT are trademarks of Novell,
  Incorporated.
o NFS is a registered trademark of Sun Microsystems, Incorporated.
o NTI is a registered trademark of Northern Telecom International.
o OfficeVision is a trademark of International Business Machines Corporation.
o Operating System/2 and OS/2 are registered trademarks of International
  Business Machines Corporation.
o Operating System/400 and OS/400 are trademarks of International Business
  Machines Corporation.
o ORACLE is a registered trademark of Oracle Corporation.
o PageMaker is a registered trademark of Aldus Corporation.
o PageScanner is a trademark of International Business Machines Corporation.
o Paradox is a registered trademark of Borland International, Incorporated.
o PC Mouse is a trademark of Mouse Systems Corporation.
o PC-MOS is a trademark of The Software Link.
o PCjr is a trademark of International Business Machines Corporation.
o PCradio is a trademark of International Business Machines Corporation.
o Personal Computer AT and AT are registered trademarks of International
  Business Machines Corporation.
o Personal Computer XT and PC XT are trademarks of International Business
  Machines Corporation.
o Personal Computer XT Model 286 is a trademark of International Business
  Machines Corporation.
o Personal Decision Series is a trademark of International Business Machines
  Corporation.
o Personal System/1 and PS/1 are trademarks of International Business Machines
  Corporation.
o Personal System/2 and PS/2 are registered trademarks of International
  Business Machines Corporation.
o Platinum is a registered trademark of Advanced Business Microsystems,
  Incorporated.
o PostScript, Encapsulated PostScript, and EPS are registered trademarks of
  Adobe Systems.
o PRODIGY is a registered service mark and trademark of Prodigy Services
  Company.
o PROFS is a registered trademark of International Business Machines
  Corporation.
o Proprinter is a trademark of International Business Machines Corporation.
o PS/2 Assistant, PS/2 General Info Assistant, PS/2 Marketing Assistant, PS/2
  Service Assistant, and PS/2 Technical Assistant are trademarks of
  International Business Machines Corporation.
o Query Management Facility is a trademark of International Business Machines
  Corporation.
o Quickwriter is a registered trademark of International Business Machines
  Corporation.
o Quietwriter is a registered trademark of International Business Machines
  Corporation.
o R:BASE and Microrim are registered trademarks of Microrim, Incorporated.
o RISC System/6000 and RS/6000 are trademarks of International Business
  Machines Corporation.
o RPG II Application Platform is a trademark of International Business Machines
  Corporation.
o Scanmaster is a trademark of Howtek, Incorporated.
o SCO is a trademark of Santa Cruz Operations, Incorporated.
o Screen Reader is a trademark of International Business Machines Corporation.
o SpeechViewer is a trademark of International Business Machines Corporation.
o Storyboard is a trademark of International Business Machines Corporation.
o SYLK is a trademark of Microsoft Corporation.
o Symphony is a registered trademark of Lotus Development Corporation.
o System Application Architecture and SAA are trademarks of International
  Business Machines Corporation.
o System V is a trademark of AT&T.
o System/370 is a trademark of International Business Machines Corporation.
o Times Roman, Helvetica, Palatino, and Optima are trademarks of Linotype AG
  and/or its subsidiaries.
o UNIX is a registered trademark of UNIX System Laboratories, Incorporated.
o Vines is a registered trademark of Banyan Systems, Incorporated.
o Windows and Microsoft are registered trademarks of Microsoft Corporation.
o WordPerfect is a registered trademark of WordPerfect Corporation.
o WordStar is a registered trademark of WordStar International Corporation.
o Workplace Shell is a trademark of IBM Corporation.
o XENIX is a registered trademark of Microsoft Corporation.
o Xircom is a trademark of Xircom, Incorporated.


ΓòÉΓòÉΓòÉ 2.  ΓöÇ PS/2 Technical Assistant - What's New? ΓöÇ  ΓòÉΓòÉΓòÉ

To see what has changed in the PS/2 Technical Assistant since the last edition,
just perform a search, using the "change bar" character (|). This is the
"shift-backslash" character (above the Enter key on 101-key keyboards).  All
changes in the PS/2 Technical Assistant are reflected by a change bar in the
right margin of tabular information.  Textual info (paragraphs, Qs & As, etc.)
have change bars to the left of the text to indicate new text, and at the end
of the text to reflect modified text.  All change bars are colored red to make
them easier to spot.

Reminder:  If you are not familiar with how to search for information in the
PS/2 Assistant, double-click here.

Note:  For a complete history of changes to all PS/2 Assistant books, refer to
the History of Changes menu item in the PS/2 General Info Assistant.


ΓòÉΓòÉΓòÉ 3.  ΓöÇ TECHNICAL INFORMATION ΓöÇ  ΓòÉΓòÉΓòÉ

The following sections contain information of a technical nature. To jump
directly to the other sections of this document, use the mouse, or Tab and
Enter keys, to select the section to which you wish to jump, below:

Main Menu Sections
Micro Channel Tutorial                                      Technical Tips
Explanation of Expanded vs Extended Memory                  Technical Qs & As


ΓòÉΓòÉΓòÉ 4. Micro Channel Tutorial ΓòÉΓòÉΓòÉ

By Mark Chapman

Many factors contribute to the superiority of the Micro Channel Architecture
over the AT architecture (or bus) system.  The primary reason there has not
been a perceived advantage to the Micro Channel so far, is that it was designed
for a multitasking environment, and most end-users have utilized it in a
single-tasking manner.  The true worth of the Micro Channel is especially
evident when multiple tasks are running (and optionally, multiple processors).
This is where the AT bus bogs down.  A number of the more significant
advantages (in no particular order) are discussed in the following sections.

Disclaimers:  1) Although this document refers specifically to the IBM Personal
Computer AT, the information applies equally to most so-called "100%
AT-Compatible" systems.  Details may differ from machine to machine, however,
so be sure to contact the system vendors for specifics regarding their
hardware.  2) This document was not written for engineers, but for those
looking for a layman's understanding of the benefits provided by the Micro
Channel Architecture.  Hence many concepts were simplified (and perhaps
oversimplified to the point where they are not precisely accurate from an
engineer's standpoint, but still serve as an effective overview for
non-engineers).  For detailed Micro Channel specifications, to the point of
timing diagrams and adapter design, refer to the IBM Personal System/2 Hardware
Interface Technical Reference manual.  Ordering instructions may be found at
the end of this document.

Note:  This article borrows heavily from a document called "Micro Channel
Architecture: Balance in the Multi-Tasking Environment", by Chet Heath, IBM
Senior Engineer and chief architect of the Micro Channel.  (Any IBM Rep or SE
can download the document from a VM file called "MCROCHNL PACKAGE" on the
PCTOOLS Disk, which is only accessible to IBM employees.  If you, or your IBM
Rep or SE, is unfamiliar with this procedure, have them contact the NDD
National Support Center for assistance.)

To jump directly to the first section of this document, use the mouse, or Tab
and Enter keys, to select this section, below:

Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Technical Information header.


ΓòÉΓòÉΓòÉ 4.1. Adapter Design ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

All adapters developed for the PC (which are often used on the AT) were
designed for 8-bit (1 byte at a time) data transfer, because that was all the
PC could handle.  When the AT came along, some adapters (mainly memory) were
developed to take advantage of the 16-bit (2 bytes per transfer) I/O path the
AT afforded, but most were still designed with 8-bit data transfer (for the
"lowest common denominator", the PC) to broaden their potential market. The
same is true of most adapters used in 32-bit 386 "AT compatibles".  Except for
memory cards, most AT adapters are designed for 8-bit (or at most 16-bit) I/O,
thus wasting much of the potential throughput.  In fact, most 386 systems ONLY
allow proprietary (sold by the system unit vendor only) 32-bit memory boards to
be used in the 32-bit slots.

32-bit Micro Channel systems (such as the PS/2 Models 70, P70, and 80), on the
other hand, not only support the use of 32-bit non-proprietary memory boards
(in the 32-bit slots), but also any other kind of 32-bit card desired.  Also,
since backward-compatibility with 8-bit adapter slots is not an issue, there is
no reason (except perhaps cost) to design adapters with 8-bit I/O paths.
Because of this, most Micro Channel adapters use 16-bit I/O (the lowest
common-denominator for PS/2s), for better performance.  32-bit (4 bytes) I/O is
most commonly provided for memory boards, but can be used for high-speed
communications or other devices requiring the best possible performance. Where
throughput is not critical, 8-bit I/O devices may also be used, if desired, in
16- or 32-bit Micro Channel adapter slots.  32-bit slots are NOT restricted to
only 32-bit cards, unlike proprietary "AT-compatible" 32-bit memory slots.

Once again, in a multitasking environment the ability to move data at a faster
rate translates into better overall system performance.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.2. DMA Burst Mode ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

In the AT design, data flow consists of many stops and starts.  First the
processor signals that it is going to send one byte of data, then it sends the
data, and finally indicates that it is ready to send another byte.  This occurs
for each and every byte.  These constant start/stops greatly impede the flow of
data.  The processor becomes a point of congestion as it is the only element in
the system capable of moving continuous blocks of data.  This is compounded in
a multitasking environment, where multiple programs are each trying to transmit
large blocks of data concurrently.  By comparison, the Micro Channel allows a
device to move large blocks of data in bursts.  Data bursts can be transferred
to and from the I/O device at up to 18.7 MegaBYTES per second (for a 32-bit I/O
device), by going through the DMA controller instead of the system
microprocessor (which is free to do other tasks).

When IBM released the original IBM Personal Computer, it included support for
three 8-bit non-bursting DMA channels.  The IBM PC/AT increased the number of
non-bursting DMA channels to seven (three 16-bit, and four 8-bit).  Of these,
only the original three 8-bit DMA channels are typically used by AT adapters,
(so that the adapters could also be used in the PC).  With only three 8-bit DMA
channels available, no more than three adapters may use DMA (non-bursting)
transfers; and only one at a time.

The Micro Channel, by comparison, allows up to fifteen DMA devices to be
installed, up to eight of which can be transferring at the same time, at burst
mode transfer rates, through eight 32-bit DMA channels.  This becomes
especially important in a multitasking environment, where system resources are
at a premium.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.3. Bus Masters ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

A key feature that enhances the concurrent processing of OS/2 is the support of
bus masters.  A bus master is a microprocessor which operates independently of
the system microprocessor, and may contain its own memory, hard disk drive
and/or slave co-processors on a card, and run its own operating system.  Bus
Masters allow the more efficient distribution of work throughout the system,
thus freeing the system microprocessor to perform more system management tasks,
while providing greater system capability. The Micro Channel can support up to
15 bus masters that can take control of the I/O bus to move blocks of data.
These bus masters do NOT have to be from the Intel family of microprocessors.
They may be any kind of microprocessor, from any vendor.

Bus masters add another dimension to the multitasking environment, called
multiprocessing.  Multiprocessing occurs when bus masters (usually intelligent
I/O adapters) communicate directly with system memory or with other I/O
devices.  Bus masters permit the system to transfer more data in less time than
is possible without bus masters, because multiple bus masters may be
transferring data concurrently.

Bus masters allow the creation of "intelligent subsystems", which use
microprocessors dedicated to a specific task in order to provide better
performance.  For example, a board containing a 12MHz 286 chip and 2MB of
memory for disk caching might be added to a PS/2 to do nothing but disk drive
data transfer.  Or a high-speed Intel or Texas Instruments graphics chip and
1MB of memory for video processing might be used for CAD/CAM.  Or a Motorola
68030 chip and 6MB of RAM might be added for desktop publishing. Or the IBM
PS/2 Wizard adapter, with a 33MHz Intel i860 numeric processor, for heavy-duty
number-crunching.

Similarly, LAN or communications subsystems can be designed (such as the IBM
ARTIC Portmaster adapter, for high-speed serial communications). In fact, all
of the above, and more, can be in the same system unit (assuming enough open
adapter slots) at the same time, and all will be running independently of the
system processor, and each other.  AND each bus master could "talk" directly
with one another, totally bypassing the system bus which may be running at a
much slower rate than the bus masters.  For example, the bus in a 20MHz Model
70-121 runs at 10MHz; however a 33MHz i860 bus master and a 25MHz 68030 bus
master could communicate directly at 25MHz (the lowest common denominator),
without tying up "traffic" on the system bus, or having to slow down to the bus
speed.

The only conflicts that might occur would be when two bus masters try to use
the same common resource (such as a diskette drive or other device not on the
bus master card).  In this event, the Central Arbiter will determine which bus
master gets control (based on priority level); the others will wait their turn.

If a multiprocessing operating system is used, each application could execute
on a different microprocessor, if desired.  Additionally, one integrated
application would be able to use several different microprocessors for multiple
tasks.  Thus it might use one 386 for sorting a file, while another 386 (with
its own 387) is used for recalculating a spreadsheet, and a graphics chip is
being used for graphing the result of the recalc, and a communications bus
master is downloading the next file to process.  Then a 68020 might be used for
output to a laser printer.

The AT architecture does not easily lend itself to bus mastering, because it
was developed for the single-tasking environment.  Thus there is no
standardized protocol defined for bus master arbitration in the AT bus, as
there is in the Micro Channel Architecture.  This means there is potential for
conflicts between multiple bus masters in an AT bus system.

Even if intelligent subsystems were to be used with the AT architecture, the
system processor is still the only element capable of moving blocks of data to
and from multiple disk drives, or I/O devices, because the AT DMA controller
does not support burst mode.  This results in an unavoidable bottleneck.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.4. Programmable Option Select (POS) ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

Because the AT was designed for a single-tasking environment, it cannot
allocate and share system resources easily.  Conflicts can be caused by two or
more adapters attempting to use the same DMA Channel, I/O Address, Memory
Address, Interrupt Level, ROM location, or memory-mapped I/O address.
Therefore many combinations of adapters are impossible to use concurrently in
the AT bus, such as Bisynchronous (Bisync) and Synchronous Data Link Control
(SDLC) adapters, and some network adapters when used in conjunction with Async,
Bisync, SDLC, or fixed disk controllers.  This is only a sample of the possible
conflicts. The more adapters you put in a system, the more possible
combinations of resources required, and the greater the likelihood of two or
more adapters conflicting.

System resource sharing is even more complex in a multitasking environment,
because two applications may require the use of the same type of system
resources at the same time.  To re-design todays adapters with enough DIP
switches and/or jumpers to accommodate all possible combinations of memory,
I/O, etc, described above, would require up to 15 switches in a system with 8
adapters or less: 4 for interrupt assignments, 4 for DMA channel selection, 3
for I/O address selection, and 4 more for adapter ROM addresses.  On top of
that, memory boards would require still more switches to specify starting
addresses and lengths for each block of memory.

This is why IBM developed Programmable Option Select (POS).  POS identifies the
type of adapter in each slot, and automatically configures it, based on
information stored in an Adapter Description File (ADF) supplied with every
adapter.  This unique function eliminates the need for the many DIP switches
often found on AT adapters.  It also saves the time spent looking up the DIP
switch settings, and then actually changing them.  The POS method is not only
faster than the manual means, but also more accurate: the ADF supplied by the
adapter vendor changes the settings; not the user.

Running multiple async communications programs concurrently requires the use of
multiple interrupts.  An AT is limited to only two asynch (serial) ports
concurrently, because only two interrupts (INT 4 for COM1, and INT 3 for
COM2...COMx) are allocated for async communication use; and the AT cannot share
interrupts.  The Micro Channel, on the other hand, CAN share interrupts (due to
the Micro Channel Architecture's use of Level-Sensitive Interrupts, rather than
the Edge-Triggered Interrupts used by the PC bus).

This means that as many as EIGHT serial devices can use those two interrupts in
the current implementation of the Micro Channel (although the current versions
of OS/2 and DOS only support 3 or 4 serial ports, respectively, in a Micro
Channel system).  In addition, the Micro Channel Architecture has the potential
for handling as many as 512 serial devices in the future.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters                                       Programmable Option Select
                                                  (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.5. Fixed Disk Performance ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

Advances in technology allow many of today's high-capacity fixed disk drives to
transfer data far faster than the AT bus can accept.  The slower I/O data
transfer capability of the AT I/O bus requires data from the drive to be
buffered in the adapter and transferred slowly across the channel, generally
requiring an interleave of 2-to-1 or 3-to-1, versus 1-to-1 for all Micro
Channel systems.  (The interleave factor identifies how many revolutions of the
disk must occur before every sector has been written to once.)  Even if 1-to-1
interleave is achieved, data transfer is still limited by the smaller I/O bus
bandwidth of the AT.

By comparison, the Micro Channel's burst capability allows data from the disk
to be transferred to memory, unbuffered, and at full speed.  Data does not have
to be temporarily stored in the adapter, or saved for later transfer.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.6. Reliability ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

Micro Channel PS/2s make extensive use of Large Scale Integration (LSI) and
Surface Mount Technology (SMT).  LSI improves reliability by putting more
components and their connections within one chip.  These interconnections are
far more reliable than solder connections, eliminating intermittent errors
caused by poor electrical connections.  Using fewer components also means that
there are fewer components to fail.

The Micro Channel also simplifies adapter design by reducing the number of
signal lines connecting hardware.  To support the same number of DMA devices as
the Micro Channel, a PC would require 16 additional signal lines.  This means
31 contacts on every connector, module, or adapter, versus only 6 for a Micro
Channel machine.  The miniaturized Micro Channel connectors also conserve
system board space (the 32-bit connectors are approximately the same length as
the 16-bit AT connectors).  Smaller circuitry means smaller system boards and
adapters (or more circuitry on the same sized board), which results in smaller
system units.

Surface Mount Technology bonds all circuits directly to the surface of the
board, eliminating the need to drill holes through the board.  This simplifies
robotic insertion of the components.  The procedure of solder-bonding modules
to the circuit board avoids bent pins and thermal shocks to the joints (which
lead to unreliable, intermittent contacts).

Because of the heavy use of LSI and SMT, Micro Channel adapters require far
less power than conventional AT adapters (which use the less expensive
pin-in-hole technology).  Lower power draw means that smaller, and less
expensive, power supplies may be used.  This (plus the use of less power-hungry
3.5" fixed disk drives) is the reason the 25MHz Model 70 has "only" a 132-watt
power supply, compared to AT-compatible systems containing 200+ watt power
supplies.  Lower power also means less heat generated inside the computer (and
excess heat is the major cause of chip failure), as well as out. The Model 70
puts out approximately 750 BTUs, versus 1,000-1,500 BTUs for systems with
larger power supplies.  This helps to reduce the expense of additional air
conditioning at sites with a large number of systems installed.

Also, although the Micro Channel adapters contain only 60% of the surface area
of AT adapters, the use of SMT allows both sides of the card to be used, making
it equivalent to 120% of the surface area of an AT card using pin-in-hole
mounting.  Because of this, as well as the smaller components themselves, SMT
permits the placement of 8 times as many modules per adapter as the older
"pin-in-hole" technology.

Overall, field experience has shown that, on average, the PS/2 product line is
five times as reliable as the IBM PC family that preceded it.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.7. Electromagnetic Compatibility (EMC) ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

Electronic equipment is susceptible to radio frequency emissions from other
electronic equipment, which can cause intermittent errors.  The problem is
potentially so severe that the U.S. Government has set up emissions and
susceptibility limits.  An FCC Class A certification means that a device passes
the minimum level required to operate in an office environment.  The test for
Class B certification, which certifies the device as safe to use in the home,
is 10 TIMES as strict as Class A.  ALL PS/2 systems are FCC Class B certified.

Tests show that the adapter connector in the AT bus is the principal source of
these emissions, and is the most susceptible to outside interference as well.
To make matters worse EMC problems increase exponentially with the increase in
speed of the system microprocessor: doubling the speed of the processor from
8MHz to 16MHz QUADRUPLES the emissions.  Doubling the speed of the processor
from 16MHz to 33MHz QUADRUPLES the emissions yet again.  To combat this, the
adapter connectors in the Micro Channel were designed with many more grounding
pins (and the pins smaller and closer together), in order to substantially
reduce emissions and susceptibility.  This design contains emissions at the
source, without having to resort to the cost and weight of bulk shielding (such
as heavy steel covers surrounding the system unit) typically found in AT
systems. This is the main reason why the Model 70s are among the few 25 MHz
386/486 systems to pass FCC Class B certification, and yet they weigh only 21
pounds (the same as the 10MHz Model 50); less than half the weight of most 386
machines. Already, some AT-sized systems weigh over 70 lbs.

This disparity in weight will only increase as microprocessor speeds go from
20MHz to 25MHz to 33MHz to 50MHz.  The EMC problem is more than 16 times worse
at 33MHz than at 8MHz, requiring even more shielding on non-Micro Channel
systems.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)
                                                  Additional Micro Channel Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 4.8. Additional Micro Channel Information ΓöÇ Micro Channel ΓòÉΓòÉΓòÉ

This section describes newly emumerated capabilities of the Micro Channel.
These capabilities (described in more detail in a new update to the PS/2
Hardware Interface Technical Reference manual) will be implemented in future
systems.  In addition, they may optionally be added to current systems through
the use of adapters that implement these abilities.

Higher Performance Data Transfers
The first new capability announced is the ability of Micro Channel systems to
transfer data at up to 160 Megabytes per second (MBps).  The basic data
transfer rate of current systems is up to 20 MBps.  In a basic data transfer
cycle, addresses and data alternate every 100ns (for a total of 200ns).  A new
feature, called Streaming Data Mode, sends the address in the first 100ns,
followed by only data in each successive 100ns period.  This allows a data
transfer rate of up to 40 MBps.

By using multiplexing techniques, on a 32-bit data bus, 64-bit data transfers
are possible. (64-bit data transfers between an adapter and the system
processor requires a 32-bit adapter.) Combining this with the Streaming Data
procedure yields data transfer rates of up to 80 MBps. In the future, with
faster microprocessors yielding shorter cycle times, data transfer rates of up
to 160 MBps will be possible.

Fault Detection and Isolation Features
In addition to memory parity checking (implemented in current systems), Data
Parity Checking and Address Parity Checking, as well as Synchronous Channel
Checking have been defined for future implementation.

Data Parity provides verification of data transferred across the Micro Channel
bus, as Address Parity provides for verification of address information.  In
addition, Synchronous Channel Check allows error information to be signaled in
synch with the information being transferred.  These capabilities enable
adapters and system boards to be designed with much higher error detection
capabilities, and will allow better software recovery in the future.

Enhanced Programmability Features
Current Micro Channel implementation requires adapters to be designed with
unique adapter addresses built in, to avoid conflicts between adapters.  This
requirement is eliminated for future systems.  The architecture now allows the
assignment of I/O addresses by the setup program during installation.

The Subsystem Control Block Architecture defines a consistent software protocol
by which bus masters may communicate and exchange information.  The SCB
architecture allows for transfer of command, data, and status information
between different bus masters, and between one bus master and the system
processor.  This will make it easier to develop intelligent subsystems.

Relationship to Current and Future Systems
All of the Micro Channel capabilities described above (except for assignment of
I/O addresses) may be implemented in current systems via adapters.  Future
systems can implement all of these capabilities on the system board, as well as
on adapters.  In addition, these functions may be used between adapters,
between the system processor and adapters, as well as between system memory and
adapters.  Because of this, the operating system doesn't have to worry about
matching the capabilities of the various components.  Data transfers will occur
at the level of the HIGHEST common denominator (ie. using those capabilities
enabled at both ends).

Thus, even in a current system, which does not contain these new functions, two
"advanced" adapters would be able to initiate 64-bit data transfers between
themselves (although transfers between one of these adapters and the system
processor would still be 32-bit), for example.

Manual Ordering Information
To order the update to the PS/2 Hardware Interface Technical Reference manual,
which describes these additional capabilities in more detail, call the IBM PC
Technical Book Hotline (at 800-IBM-PCTB), and order Part Number 15F2160.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Other Sections
Adapter Design                                    DMA Burst Mode
Bus Masters
                                                  Programmable Option Select (POS)
Fixed Disk Performance                            Reliability
Electromagnetic Compatibility (EMC)               Additional Micro Channel
                                                  Information

Return to the Micro Channel Advantages vs. the AT Bus header.


ΓòÉΓòÉΓòÉ 5. Explanation of Expanded vs. Extended Memory ΓòÉΓòÉΓòÉ

The following attempts to explain, in layman's terms, the differences between
Expanded and Extended memory, and the advantages and disadvantages of each
type.

When discussing the difference between Expanded and Extended memory, it is
important to know why both types of memory came about.

When IBM announced the IBM PC in 1981 it revolutionized the industry.  Until
then, most personal computers had a maximum memory capacity of 64K, due to the
microprocessor chips used.  A few systems offered 128K through a technique
called bank switching.  This involved swapping the contents of one 64K bank of
chips out of working memory for a moment, and swapping the other bank in.  In
this manner, the computer could actually access twice as much memory as it was
capable of using at any one time.  Although relatively slow and inefficient, it
was workable and a way of getting around the architectural limit of 64K of
addressable memory.

With the advent of the IBM PC the user had access to 10 TIMES as much as memory
before.  This was the result of using the Intel 8088 chip, which could access
1024K (1MB) of memory addresses.  Of this 1024K, 384K was reserved for hardware
addresses, leaving 640K available for memory addresses.  This 640K area was
referred to as Real memory. Although in historical perspective 640K has turned
out to be a tremendous limitation to many users, it was a huge amount of memory
back in 1981.  Remember, in those days, it was common for commercial programs
to be able to run in only 48K or less of available memory (whatever was left by
the operating system of the initial 64K).

As the PC (and later the PC/XT) became more popular, programs began to expand
in scope and size.  By the time the PC/AT debuted, in 1984, a few programs
(notably Lotus 1-2-3) were beginning to approach the 640K "barrier".  One of
the innovations brought to the PC world by the 80286 chip used in the AT was
the Extended mode, which allowed access to 16MB of memory all at once.  This
offered tremendous potential for those users running up against the 640K DOS
limitation.  In addition, by using this Extended memory in Protected mode,
multiple programs could be run in this memory, each protected from one another
by (in effect) temporary memory partitions.

However there were two problems with using Extended Memory:  1) The
architecture of the 286 allowed for transition from Real mode to Protected
mode, but not vice versa.  This meant that once an application used Extended
memory, it was stuck there until the system was re-booted; and 2) When the AT
first shipped no one knew that it (and the 80286 chip in general) would be as
wildly successful as it was.  So looking at the problem, in 1984, of how to
access more than 640K, software developers tended to think, "Yes, the 286 chip
allows us to do that, but less than 1% of all users have 286 systems.  So if we
develop software to use Extended memory we lock ourselves out of 99% of the
market, and we still don't solve the memory limitation problem for most users."

This concern simmered for a while longer, until finally Lotus Development
Corporation (the maker of Lotus 1-2-3, the program most apt to run into the
640K limit at that time), Intel Corporation (the maker of the 808x and 80x86
chips), and Microsoft Corporation (the maker of the DOS operating system) got
together to propose a specification for another sort of memory: Expanded.  This
specification, which came to be known as LIM EMS (Lotus-Intel-Microsoft
Expanded Memory Specification--also referred to as LIM Spec or EMS memory)
V1.0, described how to manufacture a memory board conforming to a specific set
of rules, as well as the operating system device drivers that would let DOS
applications recognize and use that memory.  Amazingly enough, the LIM EMS spec
was for bank-switched memory, similar in concept to that used before the PC
existed!

The way it works is relatively simple.  Some of the 384K of memory that is
reserved for hardware addresses is generally unused.  EMS memory uses 64K of
that memory area as a "door" to the Expanded memory board.  Portions of the
Expanded memory are swapped into that 64K space (well, actually just the memory
addresses are swapped, not the data, but the concept is the same) long enough
to be used by DOS, then swapped out to be replaced by another section of
Expanded memory.  Early versions of the EMS spec required the 64K of memory to
be in a contiguous (that is, connected) block.  This was often difficult to
find in a system with many adapters, some of which use small sections of memory
in the same area between 640K and 1MB.  Beginning with LIM EMS V4.0 memory can
be allocated among four 16K pages, which need not be contiguous.

Whereas Extended memory is addressed ABOVE 1MB, Expanded memory is essentially
located "beside" Real memory.  The details are more complicated than that, but
this should be sufficient for a basic conceptual understanding.  A simple
diagram (not to scale), below, contrasts the two methods:

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ         ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ     ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
ΓöéEXT. MEMORYΓöé         ΓöéREAL MEMORYΓöé     ΓöéEXP. MEMORYΓöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ         ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ     ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉΓöÇ 4GB ΓöÇ
^  Extended ^(80386/486 Limit)
^   Memory  ^                    ΓöÇ 32MB ΓöÇΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γö£ΓöÇ ΓöÇ ΓöÇ ΓöÇ ΓöÇ ΓöÇΓöñΓöÇ16MB ΓöÇ           EMS Limit)Γöé         Γöé
^  Extended ^(80286 Limit)               Γöé   Up    Γöé
^   Memory  ^                           /Γöé         Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñΓöÇ 1MB ΓöÇΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ  / ^         ^
Γöé  Reserved Γöé       Γöé ROM Addresses Γöé /  ^         ^
Γöé  for ROM  Γöé       Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ/   Γöé   to    Γöé
Γöé Addresses Γöé       Γöé Unused Space  Γöé    ^         ^
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñΓöÇ640K ΓöÇΓö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ\   ^         ^
^    DOS    ^       ^     DOS       ^ \  Γöé         Γöé
^   Memory  ^       ^    Memory     ^  \ Γöé  32MB   Γöé
^    Area   ^       ^     Area      ^   \Γöé         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿΓöÇ  0K ΓöÇΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

You might think of Expanded memory as a juggler with a number of balls in the
air at the same time, only one of which is in his hand at any time.  All the
balls are available to the juggler, and all eventually get handled in turn.  By
comparison, to take this analogy further, Extended memory would be like a box
with the balls in it: all available at the same time, rather than one at a
time.

The original EMS specification was limited to only 2MB, but later versions
increased the capacity. The current version, 4.0, supports up to 32MB of RAM.
It is still bank-switched memory, which makes it inherently less efficient, and
thus slower, than directly-accessible memory (such as Real Memory and Extended
memory).  The big advantage of Expanded memory, of course, is that it will run
on almost any PC or PS/2, from an 8088 to an 80386.  Extended memory requires
an 80286 or above.  Although the 286 architectural limitation is 16MB, the 386
can address up to 4 Gigabytes(thousand Megabytes) of physical memory, so the
potential memory capacity is far larger for Extended memory than for Expanded
memory.

For these (mostly marketing) reasons Expanded memory became the dominant method
of increasing memory beyond 640K, and remains so today.  However this is
rapidly changing.  With the existence of OS/2, a single-user, multi-tasking
operating system; and Unix (including Xenix and AIX), a multi-user,
multi-tasking operating system; and even 386 protected mode DOS extenders; we
now have operating systems capable of utilizing the protected mode of the
286/386/486 chips, and all of the Extended memory they provide.  Because these
operating systems can (through software resets) jump back and forth between
Real and Protected mode on the 286, the "one-way access" limitation mentioned
earlier no longer exists (the 386 and 486 chips have never had the same
limitation as the 286).  And because these operating systems use the memory
scheme architected into the microprocessors, they have no need for EMS memory.

Another reason why the days of Expanded memory may be numbered lies in the very
way it works.  To access Expanded memory, 64K of the area between 384K and 1MB
must be left unused by hardware addresses, and thus available for use as a
"door".  Until recently, this was not a problem.  Of this 384K, 128K is
reserved for video memory (in systems with EGA or VGA controllers), and another
128K for ROM BIOS.  This leaves only 128K left for everything else.  Among this
"everything else" are ESDI, Token Ring, 3270 Emulation, and 8514/A Adapters;
three of which can leave you with less than 64K available for EMS memory.  This
means that either you can't use Expanded memory, or you have to remove one or
more adapters from the system; something most users would be reluctant to do.
Extended memory has no such conflicts, situated as it is above the 1MB
boundary.

As far as the memory boards themselves are concerned, there is not much to
worry about.  Although the older 286 memory boards were designed for either EMS
memory or Extended memory (but not both), most newer boards (such as the PS/2
0-8MB Expanded Memory Adapter/A, and 2-8MB 80286 Memory Expansion Option/A)
contain logic chips which allow the board to be used interchangeably as either
type of memory. This protects the customer's hardware investment in the event
they convert from DOS-and-Expanded-memory to OS/2-and-Extended-memory (or
AIX-and-Extended-memory).  Boards designed for use in 386 systems can be used
interchangeably as Expanded or Extended memory as well.  The 80386 and 80486
chips are "intelligent" enough to access a memory board either way, depending
on the operating system and device drivers used.

To jump directly to the Technical Information header, double-click with the
mouse, or press the Enter key.


ΓòÉΓòÉΓòÉ 6. Technical Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on various PS/2-related hardware and software products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tip Sections
AIX PS/2 Tips                                     Networking Tips
IBM Printer Tips                                  PS/2 Hardware Tips
OS/2 1.x Tips                                     PS/2 Assistant Tips
OS/2 2.x Tips                                     Application Software Tips

To jump directly to the Technical Information header, double-click with the
mouse, or use the Tab and Enter keys.


ΓòÉΓòÉΓòÉ 6.1. AIX PS/2 Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on AIX PS/2 and related products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips
What is IBM AIX?                                  AIX Communications
Installing DOS and AIX On The Same System
Error in AIX 1.2 Command Reference DISPLAY Command

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.1.1. What is IBM AIX? ΓöÇ Tip ΓòÉΓòÉΓòÉ

By David Nation
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

To many people in the microcomputer world, UNIX:

 1. is an archaic operating system
 2. is only used on minicomputers
 3. has a very unfriendly user interface
 4. is not something they want to learn a lot about

Most people cringe when you mention UNIX to them.  When asked a question about
how much he knew about UNIX, one person said, "I don't even want to know how to
spell it." With the rise of the personal workstation as a development platform,
UNIX has become a state of the art operating system and runs on every platform
from a PS/2 to a System 370.  The introduction of graphical user interfaces
such as AIXwindows and MOTIF provides easy to use "point and shoot" menus
similar to those found in OS/2 and Microsoft Windows. With many microcomputer
users outgrowing the DOS environment, UNIX is rapidly becoming something that
programmers and support specialists will want to l earn a lot about.  The
remainder of this article will be an introduction to AIX, IBM's version of
UNIX, and to demonstrate how an existing knowledge of DOS can make learning
UNIX easier.

AIX

AIX is IBM's version of UNIX.  UNIX was originally developed by AT&T Bell Labs
and a number of different versions have appeared. AIX is a combination of
AT&T's System V and Berkeley Software Distribution's versions of UNIX, with
some IBM extensions and modifications.  It requires a minimum of a 80386
processor to run, but can be used as an operating system on platforms as
diverse as the PS/2 Model 70 and 80, the RISC System 6000, and System 370
mainframe computers.  It is a multitasking operating system similar to OS/2 in
that it allows multiple programs to run at the same time on the same processor,
but it is also multiuser, allowing up to 256 (depending on the platform) users
on ASCII terminals to run programs on the same processor at the same time.

Unlike some other versions of UNIX, AIX splits the components of the operating
system into separate packages, allowing the user to buy only the pieces that
they need. Some of these components include the Base Operating System,
Operating System Extensions that add additional UNIX commands, Programming
Tools and Interfaces, DOS Merge (lets multiple DOS applications run at the same
time on an AIX machine), and DOS Server/AADU (lets the AIX machine become a
file server for DOS machines).

Transition Easier than Expected

For someone used to a single user operating system such as DOS, AIX can be
intimidating, but DOS and AIX share many characteristics that make the
transition between systems easier than it first appears. The file system tree
structure used by DOS was modeled after the CP/M operating system file system,
which was created to behave like UNIX's file system.  With this common tree
structure, both file systems are organized around the concept of a root
directory with a branching subdirectory scheme. The commands for directory
operations are almost the same.  CD to change directories.  MKDIR to make
directories.  RMDIR to remove directories.  Note that the MD and RD
abbreviations used by DOS don't work under AIX.  The major differences between
the file systems are that file names under AIX can be up to 14 characters,
while DOS is limited to 11 characters, AIX file names are case sensitive (i.e.
text.dat and TEXT.DAT are two different files), while DOS file names are not
(i.e.  TEXT.DAT and text.dat refer to the same file), and the slashes in the
directory tree under dos are "\" (i.e.  C:\DOS), while AIX slashes are "/"
(i.e.  /usr).  Since both DOS and AIX take a command line approach to the basic
operating system functions, they have commands that perform similar tasks. DIR
gives DOS users a list of files in the current directory; ls does the same
thing for AIX. COPY copies files under DOS; cp is the AIX file copy command.
RENAME renames a DOS file; mv changes an AIX filename and provides additional
functionality by allowing you to move a file to another directory. DEL and
ERASE delete DOS files; rm removes AIX files.  Another area of similarity is
the use of redirection and pipes. DOS borrowed the commands and symbols for
redirection (< is redirect from and > is redirect to) and pipe (|) from UNIX.
Samples of using these commands to print a sorted directory listing under AIX
and DOS would be:

AIX:
$ ls | sort > /dev/lp0

DOS:
C:\> dir | sort >lpt1:

Disk Writes Cause Problem

Although some commands are shared by AIX and DOS, there are a few areas that
are different enough to cause problems for an AIX novice. The chief cause of
problems for DOS users converting to an AIX system is in the way AIX handles
disk writes. AIX uses an area of the disk for file information much in the same
way DOS uses a FAT table with one major difference: DOS writes data directly to
the disk whenever a write request is made; AIX writes to buffers in memory and
"syncs" the data to disk periodically. If a machine is turned off while data is
still in the buffers, file system corruption may occur. Using the buffer and
"sync" method increases the efficiency of the file system by speeding up data
access and writes, but users converting from DOS have to get used to running
the "shutdown" command before turning off the system in order to avoid any file
system problems. The shutdown command broadcasts a message to all users on the
system letting them know when the system is coming down, and after a specified
time (usually 1 to 5 minutes) kills any remaining processes, syncs the disks
one last time, and stops the machine.

Must "Mount" Diskettes

Another related area is mounting floppy disks. When a disk is placed in a DOS
machine, all that is necessary to read the disk is to reference A: and read
data. Under AIX, the diskette drive is called /dev/fd0 and it must be attached
to the AIX file system with the mount command (i.e. mount /dev/fd0 /diskette0).
The drive is then referenced as subdirectory diskette0. Before the disk may
removed, it must be unmounted (i.e. unmount /diskette0). Unmounting the disk
forces a sync of the data waiting to be written to diskette and avoids file
system corruption. If a diskette is removed before being unmounted, file system
damage can occur.

DOS C Code Portable to AIX

Programmers writing code for DOS in C will find that their code is very
portable to AIX. The two areas which require the most changes are routines that
make BIOS calls and video routines. BIOS calls can usually be replaced with
system calls written in C, but using direct access video routines under DOS
will require re-writing the code to use a standard AIX library called CURSES.
CURSES provides a screen handling system with windowing, cursor control, color
control, etc. CURSES is also available for DOS from a number of sources, making
it possible to use the same screen manager on both systems. A number of other
options for screen management exist in AIX including the Graphics Subroutine
Library, and the High Function Terminal library.  As more and more users
realize the power and flexibility of AIX, being prepared to understand and
support AIX will become increasingly important. For support personnel with a
DOS background, the transition to AIX is easier than it might first appear.
Remember that DOS owes many of it's characteristics to UNIX traditions.

To return to the AIX PS/2 Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.1.2. AIX Communications ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Richard L. Mayson
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1990)

In this issue, we will briefly describe the types of communications available
to the AIX/UNIX user with a more in-depth emphasis on modem communications.
One of UNIX's many strengths lies in its communications.  AIX has a vast array
of internal and external communication facilities.

TCP/IP
IBM's AIX offers the UNIX user complete networking facilities.  For the
traditional Local Area Network (LAN) or Wide Area Network (WAN), the software
of choice is TCP/IP (Transmission Control Protocol/Internet Protocol).  Because
TCP/IP can reside on a range of systems from PCs to Mainframes and operating
systems from DOS and OS/2 through VM-based 3090 mainframes, it is the worldwide
defacto standard protocol for networking.  On the hardware side, AIX offers a
hardware choice of Token Ring and/or Et hernet for LANs and X.25 packet
switching for WANs.  This type of networking is normally found in installations
where many systems need to share data.  These systems may be other UNIX
systems, OS/2 or DOS PCs, or mainframes.

3270 & Async
For users that need direct mainframe access, AIX offers complete 3270 support
via the Workstation Host Interface Program (WHIP). Use of the WHIP LPP enables
users to have interactive sessions as well as complete upload/download
facilities from the AIX workstation to the mainframe.

The most common form of external communication found on any UNIX is via a
1200/2400 baud modem.  AIX supports internal and external modems ranging in
speed from 300 baud to 19200 baud.  The software utilities that support modems
are the Basic Network Utilities (BNU), these are commonly referred to as the
UUCP subsystem.  Let's look at the sequence of events needed to "attach" the
modem to the software.

Setup
First, some assumptions....  Let's assume a 2400 baud, Hayes command set,
external modem.  We will physically attach the modem to the native serial port
on a PS/2.  We also assume that the Basic Networking Utilities part of the AIX
Operating System Extensions has been applied to the system.  The
system/nodename of our system is 'marlowe'.  (Administrator's Note:  The
default system/nodename for AIX PS/2 is 'aixps2'.  It is strongly recommended
that you choose another unique name for your systems at installation.  If you
have already installed the system with the default name, see the 'chparm'
command to change the system/nodename.  As you will see, communications between
systems requires unique system/nodenames.) Next, the control files.... Change
directory to '/usr/adm/uucp' to find the UUCP control files.  The file names
are fairly descriptive of their function. We need to tell the software where
the modem is and its characteristics.  This is accomplished in the 'Devices'
file.  As distributed, the Devices file contains numerous sample entries.  For
this example, uncomment the line that is similar to 'ACU tty0 - 2400 hayes'.
This tells the software that an Automatic Calling Unit or ACU is attached to
port tty0 at 2400 baud and uses the Hayes command set.

Finally, we need to tell the software how to dial a Hayes compatible modem.
This is accomplished in the 'Dialers' file.  No setup is required to use most
common command sets or modems. Now that we have completed the modem-to-system
connection, we need to tell the system who we can call.  The 'Systems' file
keeps the names, phone numbers, and login information for the systems with
which we wish to communicate.  For example, the entry: unixgt Any ACU 2400
5551212 "" \d in:-BREAK-in: nuucp word: password translates to:

unixgt                 - Call system named unixgt
Any                    - Call anytime of day
ACU 2400               - Use a device that has an ACU and operates at 2400 baud
5551212                - Dial this number

The following is referred to as a 'chat script'

"" \d                  - expect nothing and send a 'delay'
in:-BREAK-in: nuucp    - expect 'in:' (login:) if you don't receive it, send a
                       break signal to the system and look for 'in:' again,
                       upon receipt, send 'nuucp' as the login.
word: password         - expect the password prompt, 'word:', upon receipt,
                       send the 'password' for that login.

File Transfer
The sequence of events for sending a file to another system is:

 1. The user issues the uucp file transfer command.
 2. A work file is created and placed in queue for transfer.
 3. Uucico is invoked, scans the spool directory and finds the work file.
 4. Uucico reads the 'Systems' file to obtain information on allowable time of
    day to call, connection and speed information and the phone number.
 5. Uucico then reads the 'Devices' file to match the connection and speed
    information to a physical port.
 6. Uucico consults the 'Dialers' file for the proper commands then places the
    call.
 7. Uucico logs into the remote system using instructions from the 'Systems'
    file.
 8. Remote system's uucico verifies the permissions from the 'Permissions' file
    and the transfer begins. Your system is now ready to communicate to the
    outside world.  There are other files in the /usr/adm/uucp directory that
    will need to be modified to meet your unique needs and security
    requirements.  With the proper configuration in place, you will be able to
    not only exchange mail and or files with other locations, but can build a
    complete software distribution system to your clients.  Suggested books on
    the setup, administration and use of UUCP:

From O'Reilly and Associates (better known as Nutshell Handbooks),
800-338-6887; in CA, 800-533-6887:

Managing UUCP and Usenet
Using UUCP and Usenet

To return to the AIX PS/2 Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.1.3. Installing DOS and AIX On The Same System ΓöÇ Tip ΓòÉΓòÉΓòÉ

First install AIX on your fixed disk.  Using the Boot and Install diskettes,
create and size your AIX minidisks, then install the AIX Base Operating System.
When sizing your minidisks it is important to remember to leave enough room for
your DOS partition. After the AIX installation is complete, shut down your
system using the *shutdown -f* command.

When you receive the message "System Halted, hit ENTER to Reboot." insert your
DOS startup diskette and press the Enter key.  From the DOS prompt (A:) use
FDISK to create your primary DOS partition on the C: drive.

Next, FORMAT the partition, and then use the SELECT command to install DOS in
the partition.  When the system is rebooted, it will automatically default to
booting from AIX.  In order to override this, press any key when the AIX boot
screen appears.  From the menu select the "Boot DOS" option and the system will
boot from the DOS partition.

Alternatively, you may want to mark the DOS partition (using FDISK) as the
active partition.  This will make the system boot from DOS as the default.  To
boot from AIX again, you would have to change FDISK to make the AIX partition
the active one.

To return to the AIX PS/2 Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.1.4. Error in AIX 1.2 Command Reference DISPLAY Command ΓöÇ Tip ΓòÉΓòÉΓòÉ

The AIX PS/2 Version 1.2 Operating System Commands Reference lists a -d and -c
flag for the 'display' command.  This is an error in the publication.

These flags are NOT supported.  The user DOES NOT have the capability of
changing the physical display used by the standard out terminal or changing the
default display for subsequent opens to the specified display.

Dual display functionality is not supported on AIX PS/2 1.2.

To return to the AIX PS/2 Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.2. Application Software Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on IBM application software products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips
Performing PrintScreens From DisplayWrite 5

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.2.1. Performing PrintScreens From DisplayWrite 5 ΓöÇ Tip ΓòÉΓòÉΓòÉ

DisplayWrite 5 installs automatically in APA mode (All Points Addressable).
There are two ways to enable DW5 to do print screens, depending if the user
wants to change to character mode or remain in APA mode. The two methods are
described below:

 1. In order to change to character mode, locate the following line in the
    DW5.BAT file:

           C:\DW5\DW5PG C:\DW5\PROFILE.PRF,C:\DW5,C:\DW5,,A

    Change the last character in the line from A (All Points Addressable) to C
    (Character). Print screen should now print correctly.

 2. In order to perform the print screen function within DW5 while in APA mode,
    the user must type at the DOS C: prompt GRAPHICS /R and hit the enter key.
    Then start DW5. The GRAPHICS /R DOS command tells the computer to print
    black and white as it is seen on the screen. To get back to the default
    mode, exit DW5 and just type GRAPHICS at the C: prompt.

    The GRAPHICS /R command can also be initiated by placing it inside the
    DW5.BAT file. This will allow the user to access the print screen function
    every time they use DW5 in APA mode.

See the DOS manual for additional information on the GRAPHICS command.

To return to the Application Software Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3. Networking Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on networking and related hardware and software products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips
Configuring IBM LAN Support Program V1.2                Guest UserID Problem
NET8002 Error After Installing a CSD
                                                        Access Denied Message Logging
Users Unable to Get Access to Shared Resources
                                                        Auto Continue Function On The LaserJet
                                                        Slow-starting Domain Controller With Many Servers       Backup of the NET.ACC File
Common Network Errors And Solutions
                                                        Access Control Profile Problems
Setting Up an OS/2 LAN Server to Share Online Books
IBM PC/3270 and NetWare From IBM Interoperability
Setting Up NetWare To Communicate Through An 8209 Bridge
Setting Up Public DOS Apps on an OS/2 LAN Server 1.x

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.1. Configuring IBM LAN Support Program V1.2 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Julian Over
IBM Personal Systems Group, UK Technical Support
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1990)

Configuring for IBM, 3Com or Western Digital 802.3/Ethernet Adapters
Configuring for Ethernet is not as straightforward as for Token-Ring; please
read this article carefully.  In most respects, it applies to the use of LAN
Support Program 1.2 for either DOS LAN Requester or PC LAN Program 1.3.
Personal Communications/3270, AS/400 PC Support and the 8209 LAN Bridge are
also mentioned.

If you find any errors, omissions or additions, please contact the IBM NDD NSC
and pass the information on to the Network group. We will make sure the author
receives your information.  The term 'Ethernet', as used in this document,
implies both Ethernet V2 and 802.3 unless otherwise stated.  Ethernet is no
longer a trademark of Xerox Corporation and can therefore legitimately be used
generically.

Adapters Supported
The LAN Support Program provides support for Ethernet/DIX V2 and IEEE 802.3
protocols under DOS with the following adapters:

o IBM PS/2 Adapter/A for Ethernet Networks
o 3Com Etherlink/MC 3C523 Micro Channel adapter
o 3Com Etherlink II 3C503 PC-bus adapter
o Western Digital Ethercard PLUS/A (WDLAN-EP/A-F001)
o Western Digital Ethercard PLUS (WDLAN-ERP-F001)

Note:  LSP 1.2 does not support the Ungermann Bass adapters which are supported
by OS/2 EE; this is because UB have not yet generally released a DOS NDIS
driver for their adapters.

Requirements

To install LSP 1.2 for Ethernet, you will need:

 1. Lan Support Program v1.2
 2. A printed copy of DXMINFO.001 (or .DOC) from the LSP diskette
 3. A printed copy of PROTOCOL.INI from the LSP diskette
 4. MACETH.DOS - NDIS driver for the IBM adapter
 5. MACETH2.DOS - NDIS driver for a second IBM adapter
 6. ELNKMC.DOS - NDIS driver for the 3Com 3C523 Micro Channel adapter
 7. ELNKII.DOS - NDIS driver for the 3Com 3C503 PC-bus adapter
 8. MACWD.DO- NDIS driver for either Western Digital adapter

Note:  ELNKMC.DOS is not supplied with the adapter (contrary to what the LSP
1.2 PLET says).  Later in the year, it will be; in the meantime, it can
probably be obtained from 3Com.  The driver is supplied with the IBM adapter,
with the 3Com PC-bus adapter and with the Western Digital adapters.

Physical Attachment
All the adapters allow two types of connection to the LAN - via a BNC connector
to a thin-wire LAN or via a D-shell connector and AUI (Attachment Unit
Interface) cable to a thick-wire LAN.  The adapters provide an on-board
transceiver for the BNC connection but require an external transceiver for the
D-shell connection. You have to select which type of connection to use; the
methods are described below.  The default in all cases is BNC (on-board
transceiver).

Configuring a PS/2 System

 1. Install the adapter and use the Reference Diskette to run Automatic
    Configuration or Set Configuration as usual.  The ADF for the card is
    supplied with it.
 2. For DOS LAN Requester and PC LAN Program, the adapter you want to use must
    be the primary.  Therefore, if you have both Ethernet and Token-Ring
    adapters and want to use the Ethernet for DLR or PCLP, you must make the
    Token-Ring card 'alternate'; the Ethernet card will then be primary by
    default.
 3. IBM Adapter

    a. Adapter I/O Range Definition. This specifies the start of the IO range
       used by the adapter; the default is 0x200.  The IOBase = parameter in
       PROTOCOL.INI must have the same value as this definition and must be
       active (not remarked out); if it is not, you will get, when PROTMAN
       executes in config.sys, one of these two messages:

      Error: No IBM Ethernet Adapter specified in PROTOCOL.INI
      Error: Conflicting parameters specified in PROTOCOL.INI for IBM adapter

    b. The Interrupt Level and RAM Address Range definitions override those in
       PROTOCOL.INI.
    c. Physical Connection.  This must be set by jumpers on the adapter (even
       though this is a Micro Channel adapter).

 4. 3Com Adapters

    a. Interrupt Level.  The config panels will show that the 3Com card uses
       Channel 3; this is IRQ (interrupt level) 3.
    b. Physical Connection.  This is set by means of the Reference Diskette.

 5. Western Digital Adapters

    a. Adapter I/O Space Definition.  This specifies the start of the IO range
       used by the adapter; the default is 0x280.  This definition and those
       for RAM Address and Interrupt Level override the definitions in
       PROTOCOL.INI.
    b. Physical Connection.  This must be set by jumpers on the adapter (even
       though this is a Micro Channel adapter).

Installing LAN Support Program
In this example, we shall assume that you want to use an IBM adapter and to
install LSP 1.2 in a directory called LSP12 on the C: drive.

 1. Make the directory (md lsp12) and make it current (cd lsp12), then make A:
    the current drive.  (During installation, you can select the drive on which
    to install LSP  - but you cannot specify a subdirectory).
 2. Run DXMAID from the A drive; this will do several things:

    a. Create a config.sys or alter the existing one (and make a backup copy of
       it).
    b. Create a LANMAN directory and copy 3 files into it
    c. Add a NETBIND command to autoexec.bat and copy NETBIND.EXE to the root
       of drive C: (but see the note in section 9).
    d. Copy into the LSP12 directory the files necessary for the configuration
       that you specify via the panels.

 3. You must copy the NDIS driver into the LSP12 directory.  The config.sys
    will include a line:

   device=\lsp12\XX.dos

   You must change XX to the name of the NDIS driver for your adapter; these
   names are given in the PROTOCOL.INI file, which you should print as noted in
   the Requirements section of this document.

Note:  If you have two 3Com adapters in the same machine, create the NDIS
driver for the second adapter by copying ELNKxx.DOS to ELNKxx2.DOS and adding
the appropriate line to CONFIG.SYS immediately after the first NDIS driver
line.

Modify CONFIG.SYS. The relevant lines of a typical config.sys will look like
this:

   device=\LANMAN\PROTMAN.EXE (/I:(d:)\LANMAN)   See note 3.
   device=\LSP12\MACETH.DOS
   (device=\LSP12\MACETH2.DOS)
   device=\LSP12\DXMA0MOD.SYS
   device=\LSP12\DXME0MOD.SYS 400000100101
   device=\LSP12\DXMT0MOD.SYS S=12 C=12 ST=12 O=N   See notes 1 & 2.

Note 1: The O=N parameter is essential; if it is omitted or is O=Y, the LSP
will try to open the adapter but will fail and you will get the message:  DXMT0
32E - Initialisation or open error on adapter n. The reason for this is that
the NETBIND command (see section 9) must have been issued before the adapter is
opened.  The DOS Lan Requester or PC LAN Program will open the adapter when
they are started.

Note 2: The DLR installation process puts O=Y.  Depending on how you are
installing the DLR, you may get the chance to change this parameter during the
installation process; if not, you must change it manually.

Note 3: If you install LSP 1.2 on a drive other than the boot drive, the LANMAN
directory will be created on that drive, not on the boot drive.  In this case,
you must add the /I:path parameter shown in the example above, so that PROTMAN
knows where to find PROTOCOL.INI; by default, it looks for it in the LANMAN
directory on the boot drive.  If you do not do this, you will get the messages:

PRO0003 PROTOCOL.INI open failure MAC0001

Initialization failure PRO0023 Cannot find Protocol Manager

 4. DXMAID will create a LANMAN directory, into which it will put 3 files:

   o PROTMAN.EXE  - the protocol manager
   o PROTOCOL.INI - the protocol manager's parameter file
   o PRO.MSG - a message file (this is created from the PROMSG.nnn file for
     your language).

 5. PROTOCOL.INI is a text file which provides parameters for PROTMAN.EXE.  It
    is a good idea to print this because you may need to alter it and because
    reading it helps in understanding how the Ethernet systems work.  You must
    set the BINDINGS= statement in this file to match the type(s) of adapter
    you have; the default is for the 3Com MC adapter.  Note that you can define
    an Ethernet adapter as alternate (secondary) by putting a comma before the
    entry in the Bindings field:

        BINDINGS = ,WDMAC

 6. Add the IBM adapter definitions to  PROTOCOL.INI. The simplest way to do
    this is to copy the Western Digital section, twice, onto the foot of
    PROTOCOL.INI and then modify it as follows:

    a. Change the heading to 'IBM PS/2 Adapter/A for Ethernet Networks'
    b. Change the BINDINGS module name from WDMAC to IBMAC (primary) and IBMAC2
       (alternate).
    c. Change the DriverName to MACETH$ (pri), MACETH2$ (alt)
    d. Change the RamAddress defaults to 0xC800
    e. Remove the remark about the IOBase parameter (invalid)
    f. Change the IOBase defaults to 0x200
    g. Remove the ; (semicolon) before the IOBase parameter. If you do not, the
       driver will not load - see section 3 of Configuring a PS/2 machine.  The
       IBM primary adapter section should look like Figure 1 on Page 18.
    h. USING TWO LAN ADAPTERS

       1. Token-Ring or PC Network with Ethernet
       2. If you use a PC Network adapter with either a Token-Ring or an
          Ethernet adapter, the PCN adapter must be primary.  To configure the
          Ethernet adapter as alternate, put a comma before the module name in
          the BINDINGS = definition of PROTOCOL.INI, for example: ,IBMAC.
       3. Bear in mind that the DLR and PCLP can use only the primary adapter
          if two of any kind are installed.  PC/3270 can use either or both.

    i. Two Ethernet Adapters

 7. You can use two IBM or 3Com adapters in the same machine but only one
    Western Digital (there is no secondary NDIS driver and a renamed copy of
    the driver is not valid).  You can also use two Ethernet adapters of
    different makes.
 8. You need a command in CONFIG.SYS for the NDIS driver for each adapter.
    These commands must be consecutive, primary first.
 9. A driver for the second IBM adapter is provided (MACETH2.DOS).  For the
    3Com adapter, you must create a driver by copying the primary driver and
    adding 2 to the name, eg. ELNKMC2.DOS.
10. The PROTOCOL.INI file gives examples of how to specify the BINDINGS =
    command when you are using two adapters.  The sequence of the values in the
    BINDINGS = command determines the assignment (pri/alt).
11. NETBIND Command. DXMAID will put the command "NETBIND" as the first command
    in AUTOEXEC.BAT (but will not create autoexec.bat if this does not already
    exist) and will copy NETBIND.EXE to the root directory of the boot drive.
    NETBIND will be in the LSP directory anyway; you can change its path if you
    like and delete the copy from the root.

    Note:  If you install LSP 12 on a drive other than the boot drive, the
    NETBIND command will not be put into autoexec.bat, nor will it be copied to
    the root of the boot drive.
12. Personal Communications/3270. If you want to run PC/3270 at the same time
    as the DLR or PCLP, you must add ES=1 EST=n (where n = the number of
    gateways the machine must use) to the DXMT0MOD line.  If you have only
    these two parameters here, they will cause LSP to open the adapter, so you
    must add O=N.

        Note 1:  The maximum PIU size allowed for PC/3270 on Ethernet is 1490; if it is
        set higher, you will get MACH682 in the OIA.
        Note 2:  Only the network station configuration is supported with Ethernet; the
        gateway is not supported (though testing is going on).

13. AS/400 PC Support. The default frame size in PCS is 1994; if you use this,
    you will get internal router errors (5123).  You must change the TRMF
    frame-size entry to 1496 or less.
14. Extended/Expanded Memory. The use of high memory is supported with Ethernet
    for the DOS LAN Requester and most other applications that can use high
    memory.  Be aware, however, that Personal Communications/3270 is not
    supported in this environment.  HIMEM.SYS, which allows applications to use
    the first 64kb of memory above 1Mb (as exTENded memory) is supplied with
    the DLR.  This version, 2.04, has been superseded by v2.6, which is
    supplied with OS/2 EE CSD WR04064.  Also supplied with the CSD is EMM386,
    which is an exPANded memory manager (LIM EMS v4) and works with HIMEM. The
    DLR is supposed to be able to use either extended or expanded memory (/HIM
    or /EMS) but we have found that /EMS sometimes hangs the machine and that
    it is better to use /HIM.  The memory saving is the same.

    Note:  The version of EMM386 supplied on the CSD is faulty and a
    replacement is now available; the file sizes are 60964 and 61040
    respectively. The versions of HIMEM and EMM386 supplied with Microsoft
    Windows 3 can also be used.
15. 8209 LAN Bridge. The DLR, PCLP and PC/3270 work well across an 8209 to a
    server.  You must ensure that the 8209 is configured to support the correct
    protocol -Mode Priority 1 = Ethernet, 2 = 802.3) and that Netbios support
    is enabled - (Forward LLC traffic, mode 1 = Y).

    Note:  Ethernet systems generally allow a maximum frame size of 1514 bytes.
    It is necessary to limit the transmit buffer size of Token-Ring devices to
    less than 1500 bytes if they are to communicate with Ethernet devices
    through an 8209; if you do not, applications may fail to load and files to
    copy etc.

    The default transmit buffer size on an OS/2 system is 1944 bytes when
    configured for Token-Ring; we suggest that you reduce it to 1496, which is
    the default used by OS/2 when configured for Ethernet.  15. PROTOCOL to be
    used - 802.3 or Ethernet. The default protocol for all the supported
    adapters is 802.3; this is also the default for LSP 1.2.  If you want to
    change to Ethernet on a DOS machine, you must add a parameter, thus:

        device=\lsp12\DXME0MOD.SYS 400000000001,,1

    The final parameter, 1, indicates that Ethernet/DIX is to be used. Note the
    extra comma, which indicates the omission of the work area parameter
    (adapter buffer space), ie. that the default will be used. If you want to
    increase the work area, add a figure from 8 - 64 between the two commas
    (see DXMINFO section 10-5).

    Note 1:  All the Ethernet devices that must communicate with each other
    must be using the same protocol - either Ethernet/DIX or 802.3.  The
    defaults are as follows:

   o LAN Support Program: 802.3
   o OS/2 EE Comms Manager: Ethernet/DIX
   o 8209 LAN Bridge: Ethernet/DIX

    You will probably have to change something.  In the case of the DLR, if one
    of the systems is set for the wrong protocol, the DLR will start but, when
    you try to log on, you will get the message:

        NET248 Cannot contact the domain controller

        This message is not documented.

    Note 2:  In OS/2 EE CM, you can select the protocol in the IEEE 802.2
    profile of LAN Feature Profiles.

16. SUMMARY of things to be careful about:

    a. Obtaining and configuring the NDIS driver. See 3.
    b. Adding O=N to DXMT0MOD.SYS. See 4, note 1.
    c. The parameter for PROTMAN.EXE. See 4, note 3.
    d. The BINDINGS= statement in PROTOCOL.INI. See 6, 8.
    e. The IOBase definition for the IBM adapter. See 7.
    f. The NETBIND program and command. See 10.
    g. PC/3270's PIU size. See 11.
    h. AS/400 PCS frame size. See 12.
    i. The OS/2 CM transmit buffer size. See 13.
    j. Configuring the correct protocol. See 14, 15.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.2. Setting Up an OS/2 LAN Server to Share Online Books ΓöÇ Tip ΓòÉΓòÉΓòÉ

Here is how to have the OS/2 Command Reference, LAN Command Reference, PS/2
Assistant, and other OS/2 online books accessed by OS/2 requesters from the
OS/2 LAN Server:

 1. Create an alias for the VIEW.EXE file (which is the program that actually
    displays the online books) in the C:\OS2 subdirectory.  Give it a Universal
    Access Profile (UAP) of R.  In the example below the alias is VIEWEXE.
 2. Create an alias for the subdirectory containing the books (e.g.,
    C:\OS2\BOOK). Also assign it a UAP of R.
 3. Create a public OS/2 application for the PS/2 Marketing Assistant (or
    whatever book you want to display), and call it PS2A_MKT.  The important
    parts of this definition are listed below:

             Program Location:  Remote
             Alias:             VIEWEXE
             Remaining Path:    \
             Command Line:      VIEW F:\PS2A_MKT

    Note:  VIEW F:\PS2A_MKT will start the PS/2 Assistant.  (The F: is
    explained below.)
 4. Select the following headings from the OS/2 Administrator's Main Panel.

<Definitions>
 <Users> Select a user
  <Logon Details>
   <File Assignments>

For PS2A_MKT you must assign a specific drive letter (the example used F: but
any drive letter would do, as long as all the OS/2 requesters have access to
that drive.)  You must then make that drive assignment correspond with the
Command Line you have defined in the PS2A_MKT application (e.g., VIEW
F:\PS2A_MKT).  Then assign * to VIEWEXE.

By completing the above actions OS/2 requesters should be able to access the
online books. To do the same for other online books, simply repeat the steps,
but use the appropriate names, paths, and drivers for those books.  The best
place to look for this information is in the Program Properties set up to run
these reference books from one of the Group menus.

Note:  Be sure to make all the INF files read-only, otherwise all concurrent
users after the first will receive "access denied" error messages and be unable
to access these files.

To return to the Networking Tips header, double-click here.

Or, to return to the PS/2 Assistant Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.3. NET8002 Error After Installing a CSD ΓöÇ Tip ΓòÉΓòÉΓòÉ

When the OS/2 communications manager is installed default configuration files,
ACSCFG.CFG and ACSCFGUS.CFG, are furnished. The installation instructions
suggest making a copy of these files with different names.  The reason for this
is that when a CSD is installed new copies of these files will be copied over
the current ones.  If the customer was using the default files it will be
replaced with new ones and all information that was put in the old files will
be lost.  This is seen most often as a server or requester failing to start
with a NET8002 error message.  This will also result in no host connection if
the user was using the communication manager to contact the host.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.4. Users Unable to Get Access to Shared Resources ΓöÇ Tip ΓòÉΓòÉΓòÉ

When a user seems unable to get access to a resource that should be available
there is an easy way to see if it is an access control problem.  Have the
network administrator go to the User Profile Management Services (UPM) and
change the UserID from type 'user' to 'admin'. Have the user then see if they
have access to the resource when logged on as an admin that they don't have
access to as a user. If they do get access, then the user didn't have
sufficient access for to the resource.  The access profile system will never
prevent an admin ID from accessing a resource.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.5. Guest UserID Problem ΓöÇ Tip ΓòÉΓòÉΓòÉ

There are some unique characteristics about the Guest ID and Guest Group that
are not obvious to most network administrators. Both RIPL and disk boot DLR
machines need the Guest ID to get DLR files from the \IBMLAN\DOSLAN\NET
directory to start the network.  The DLR machine that is trying to start will
display a message that the server is not available or that it cannot copy
XSRW.BAT.  This can happen if an apply has been done above the NET directory
with insufficient access rights.  Access to needed files are being denied.  To
correct this problem just have the administrator give the Guest ID "R" access
to the IBMLAN\DOSLAN\NET directory.

Another known cause of this problem is if the Guest ID has been deleted or
given a password.  This can be resolved by adding the Guest ID back or remove
the password requirement for the Guest ID.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.6. Auto Continue Function on the LaserJet ΓöÇ Tip ΓòÉΓòÉΓòÉ

There is a function on HP Laserjet Series II and III printers called "Auto
Continue."  The manual for the HPLJ II talks about it but says nothing about
running on a network.  The HPLJ III book says that if the printer is on a
network Auto Continue should be turned on.  The default for both II and III is
off.  Turning on Auto Continue has cleared some Network printing problems for
both printers.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.7. Common Network Errors and Solutions ΓöÇ Tip ΓòÉΓòÉΓòÉ

Error Codes                        Solution
NET3055                            Check the cable connecting the PC to the
                                   ring.
NET3062                            If this error is on an additional server, go
                                   through the resync procedure listed at the
                                   end of the READ.ME file on diskette 12 of EE
                                   1.2 CSD 4098.
NET3055, NET3056, NET3195          Make sure that the Sessions and Commands
                                   parameters in the NETBIOS section of the
                                   communication manager CFG file are larger
                                   than the Sessions and Commands parameters
                                   set on the NET1 line of the IBMLAN.INI file.
NET9853                            Make sure the MachineID listed in the
                                   IBMLAN.INI at the requester is not the same
                                   as the UserID.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.8. Backup of the NET.ACC File ΓöÇ Tip ΓòÉΓòÉΓòÉ

The following is an easy way to keep a good backup copy of your NET.ACC file,
using the three lines below as an example for the STARTUP.CMD file.  This will
make at least one good copy of the NET.ACC file available.  You can use
whatever file names you want for the backup files.

XCOPY C:\IBMLAN\ACCOUNTS\NETBACK2.ACC  C:\IBMLAN\ACCOUNTS\NETBACK3.ACC
XCOPY C:\IBMLAN\ACCOUNTS\NETBACK1.ACC  C:\IBMLAN\ACCOUNTS\NETBACK2.ACC
XCOPY C:\IBMLAN\ACCOUNTS\NET.ACC  C:\IBMLAN\ACCOUNTS\NETBACK1.ACC

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.9. Slow-Starting Domain Controller with Many Additional Servers ΓöÇ Tip ΓòÉΓòÉΓòÉ

If the IBMLAN.INI file of the domain controller contains the parameter: Update
= Yes  it means that when the server is starting, the NET.ACC for every
additional server must be updated.  If there are many additional servers on the
network it could take a long time before all the NET.ACC files have been
updated. This will increase the network activity and therefore the server will
run somewhat slower until the files have been updated on all additional
servers.

The update parameter can be changed from Yes to No on the domain controller.
This will not require NET.ACC to be updated on each server before the domain
controller can complete startup.  The NET.ACC file on the servers will be
updated as changes are made to it but all servers are not updated when the
domain controller is being started.

The additional servers still need to have Update = Yes.  This will get a new
NET.ACC for the additional server at the startup of the additional server.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.10. Access Control Profile Problems ΓöÇ Tip ΓòÉΓòÉΓòÉ

The Network Administrator's Guide page 6-8 describes how the Access Control
Profile system checks for a users access to a resource.  It does a good job of
explaining the subject but this further information may clear up some
questions.

Note 1, at the bottom of page 6-8, explains that for a files resource the root
is C: and not C:\.
C: = Root of the C: drive.
C:\ = Root Directory of the C: drive.

The Access Control system sees C: as the Root and C:\ as just the first
directory on the drive.  This is an important distinction.

If a user tries to access a resource that has no Access Control Profile the
Access Control Profile system will end up looking for a profile for the Root,
C: not C:\.  If a profile can be found for the Root then access to the resource
will be based on the users access to the Root, C: not C:\.  If no profile for
the root is found access to the resource is denied.

Anyone who has ever tried to create a profile for an alias has found that the
field for the Server path to the Directory requires a "\" as the first
character.  With this requirement how can one ever make a profile for C: alone?

This can only be done by creating an Access Control Profile for a Non-Alias.
To do this, using the full screen interface from the Main Panel, choose
Definitions then Access Control.  At the Manage Access Control - Alias menu
press the F10 key and select Servers. Press Enter to select Display Profiles by
Server.  Select the server you want the profile on and the Manage Access
Control - Non-Alias should be displayed.  From this menu one should be able to
select New and Create and a profile for C:, the root, can be created.

This is also true for other drives letters besides C:.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.11. Access Denied Message Logging ΓöÇ Tip ΓòÉΓòÉΓòÉ

Access denied messages can get logged to the statistics log or the audit log
for several reasons that are not obvious.  If an E-mail application is
accessing shared files but doesn't have the A (attributes) access permission,
access denied messages can get written to the statistics log.  Giving the
shared resource the A access will stop the logging of access denied messages
and not give the users any more actual access than they now have.  Other
applications may cause similar results.  If users are given any access to a
resource, make sure they also have the A access to alleviate problems such as
these.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.12. IBM PC/3270 and NetWare From IBM Interoperability ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Bennett Gaston and Thomas Strength
(From The IBM Advisor, the technical newsletter for IBM dealers; 3Q 1990)

In the past few months several questions have arisen concerning the use of
Personal Communications/3270 (PC/3270) with NetWare.  The following paragraphs
discuss two methods (which have been thoroughly tested) of running both
products concurrently on workstations using Expanded memory.

1) A directly attached PC/3270 session and NetWare will operate simultaneously.
To accomplish this, load PC/3270 into expanded memory, "Hot Key" to DOS, and
start NetWare IPX.COM.  This allows the workstation to run applications under
PC/3270 and NetWare concurrently.  If PC/3270 is not loaded into expanded
memory, some NetWare applications will not work due to memory requirements.

An alternate way of achieving the same function (as above) is to start PC/3270
from a user defined menu under NetWare.  Make sure that the PC/3270 directory
on the workstation is mapped to a NetWare search drive in the workstation's
user login script.  This allows the file server to search for and execute the
PC/3270 batch file.  (Note: To execute from the menu, all users must recognize
the same PC/3270 batch file.  When creating the menu, do not change directories
when calling the batch file.  This will lock-up the workstation.)

2) PC/3270 is the only IBM emulator supported working with NetWare and
Token-Ring.  (Ethernet testing was not completed in time for this article.)
The methods for implementing PC/3270 over a Token-Ring Gateway concurrently
with NetWare are as follows: PC/3270 requires the IBM LAN Support program to
provide a NetBIOS interface.

1) Configure the NetWare workstation for IBM LAN Support rather than
Token-Ring.
2) Add parameters to the NetBIOS LAN Support driver as follows:

DEVICE=d:\path\DXMT0MOD.SYS ES=2 EST=2 O=Y

(It is necessary for LAN Support to open the adapter (O=Y) so that when IPX.COM
is loaded, it will not take all of the available resources on the adapter.)

After rebooting the system, start IPX.COM and NETx.COM (where x denotes the
version of DOS being used) and then PC/3270 or vice versa.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.13. Setting Up NetWare To Communicate Through An 8209 Bridge ΓöÇ Tip ΓòÉΓòÉΓòÉ

Run source routing, which comes with V3.11 and V2.2.  On the workstation, load
ROUTE.COM after IPX and before NETx.  On the V3.11 server load ROUTE.NLM.  On a
V2.2 server load ROUTE.VP0 by copying the ROUTE.VP0 into the system directory.
Note: If the IBM 8209 is connecting a Token-Ring to an Ethernet network, you
must have the Enhanced Ethernet Module.  Any Enhanced Ethernet module ordered
before June 21, 1991 will require an Engineering Change (EC).  All Enhanced
Ethernet modules ordered after. June 21 will already have the EC installed.
The 8209 customer can call 800-IBM-SERV to have an IBM CE order ECA001 EC
C25206. The EC will work with the following NetWare products:
 - NetWare 286 V2.15 Revision C from Novell
 - NetWare V2.2 Revision A from Novell or IBM
 - NetWare V3.11 from Novell or IBM

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.3.14. Setting Up Public DOS Apps on an OS/2 LAN Server 1.x ΓöÇ Tip ΓòÉΓòÉΓòÉ

Let us assume we have an application on the server called, "PROGRAM.EXE."  It
is in the C:\APPS directory on the server, and several users must access it
from DOS machines.

 1. Create the USERS in the User Profile Management.
 2. In LAN REQUESTER, create an ALIAS for C:\APPS called APPS.
 3. Create an ACCESS PROFILE for APPS.  Choose the appropriate universal access
    or specific access profiles for the User List.
 4. APPLY this ACCESS PROFILE.
 5. Create a PUBLIC DOS APPLICATION called APPNAME
 6. Fill in the description field.  The description is important because it is
    what will be displayed on the DOS LAN Requesters' Program Starter.
 7. Put "Program" as the COMMAND LINE. (The quotes are not included)
 8. Choose APPS as the FILESET.  The remaining path should be \.  The assigned
    drive should be *. (This assigns APPS to the next available drive on the
    DOS LAN Requester.)  Leave everything else as default.
 9. Choose ACTIONS and Working Directory for APPNAME. APPS should be the
    Working Directory. The assigned drive should be *. (This assigns APPS to
    the next available drive on the DOS LAN Requester.)  Leave everything else
    as default.
10. Choose Application Selector and add this program to all of the appropriate
    users.
11. Restart the server and log on.

To return to the Networking Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.4. IBM Printer Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on IBM printers and related products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips
IBM 4019 Laser Printer Setup
IBM 4216 Personal Pageprinter II Setup

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.4.1. IBM 4019 Laser Printer Setup ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman and Jeff Dean
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

IBM 4019 Setup for Serial
The following directions explain how to set up the IBM 4019 LaserPrinter, and
4019 LaserPrinter E, for serial use:

 1. Turn off the computer and the 4019 LaserPrinter.
 2. Make sure the serial cable is attached to both the computer and the
    LaserPrinter.
 3. To get the printer into configuration mode, press the FONT and ORIENTATION
    buttons and turn the printer on, holding the FONT and ORIENTATION buttons
    until any operator panel lights come on.
 4. A "6" should be displayed, and all lights should go off except for the
    READY and DOWNLOAD lights.
 5. Using the 4019 Guide to Operations, page 10-7, set up the configuration as
    follows:

   Handshake Protocol - Serial DTR  (selection 1)
   Data Rate - 9600 or 19200 (selection 4 or 5)
   Data Bits-Per-Frame - 8 bits (selection 2 - Default)
   Parity - None (selection 3-Default)

 6. To save the configuration, press and release the CODE and ORIENTATION
    buttons simultaneously.
 7. To exit the printer configuration function, press and hold the CODE button
    while you press and release the RESET button.

Setting 4019 Print Modes
The 4019 is capable of operating in three data stream modes:

IBM PPDS mode (ASCII mode)
HP emulation mode (to emulate the LaserJet II series)
IBM and HP plotter emulation mode.

To check the active mode, make sure the READY light is on, then press the
ORIENTATION button to display the number (one of those referenced above).  To
change the mode, use one of the following:

o To put the printer into IBM PPDS mode, press and hold the PAPER button as the
  printer is powered on.
o To put the printer into HP emulation mode, press and hold the FONT button as
  the printer is powered on.
o To put the printer into Plotter mode, press and hold the ORIENTATION button
  as the printer is powered on.
o Release the button that has been pressed and held when any operator panel
  lights come on.

To return to the IBM Printer Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.4.2. IBM 4216 Personal Pageprinter II Setup ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman and Jeff Dean
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

4216 Personal Pageprinter as HP LaserJet Plus
The following steps explain how to configure an IBM 4216 Personal Pageprinter
for HP LaserJet Plus Emulation mode:

 1. Power off the 4216.
 2. Set the DIP switches on the 4216 as follows:

    a. Set switches 1 and 2 to UP. (This will set up the printer for parallel
       printing mode).
    b. Set switch 3 to up and switch 4 to down. (This will set up the printer
       for HP LaserJet Plus emulation).

 3. Power on the 4216.
 4. The Personal Pageprinter will output a setup sheet. Ensure that the
    Interface is set for: LaserJet Plus, PC Parallel.

IBM 4216 as PostScript Serial
The following steps explain how to set up an IBM 4216 Model 031 printer as an
OS/2 1.2 PostScript printer at 19,200 baud, attached to COM1.

 1. Set all printer DIP switches to the "down" position (configuration mode).
 2. Set the COM port to 1200 bps (via the Control Panel).
 3. Send a data file containing the PostScript commands shown on Page 20 to the
    printer using the command:

   COPY <FILENAME> COM1

 4. Set switch 4 to up to save the configuration.
 5. Turn the printer off, and then back on.
 6. Send a mode command to set up COM1 as follows:

   MODE COM1:19200,N,8,1,TO=ON, XON=OFF,DTR=ON
   (Put this into your STARTUP.CMD file so it executes each time you boot up
   your system).

 7. Make sure that you have the printer associated with COM1 (via the Print
    Manager) and with the Postscript driver that comes with EE 1.2, and SE 1.2
    (at CSD level XR04020 or later) refresh.
 8. Make sure that you have a queue set up in the Print Manager (such as COM1Q)
    and associated with the 4216 Personal Pageprinter.

To return to the IBM Printer Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5. PS/2 Hardware Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on PS/2s and related hardware products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips
                                           Introducing IBM's New SCSI Devices         The Whys and Wherefores of DASDDRVR.SYS
                                           Terminating the IBM SCSI Adapters          How Model 90/95 Selective Boot Assigns Drive Letters
Using Paradox V3.5 with the L40SX          Understanding PS/2 Model Numbers
Understanding XGA                          L40SX Battery Concerns
                                           Duplexing on a PS/2 Model 57/90/95         Communicating with the L40SX Fax/Modem
PS/1 & PS/2 System BIOS Information        Screen-Saving Tips
Comparison of 386SX/386SL/386SLC/386DX/486SX/486DX/486DX2 Processors

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.1. Introducing IBM's New SCSI Devices ΓöÇ Tip ΓòÉΓòÉΓòÉ

Greg Burton
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

What is SCSI?

SCSI stands for Small Computer System Interface. SCSI standards are defined by
ANSI X3.131.1986.  SCSI is not new to the PC industry.  Other vendors have been
using SCSI fixed disk drives for quite a while, as has IBM.  They have been
available in the IBM RT for several years.

The SCSI standards define a common command set that is programmed into ROM on
the adapters and is accessed via system BIOS as normal fixed disk commands.
Although IBM is only offering fixed disks and CD ROM devices, there are many
other devices available  within the industry.

64 Addressable devices
The SCSI architecture allows 8 devices per SCSI bus.  The controller itself is
a device so seven additional physical devices can be attached.  Each physical
device can have 7 logical devices attached to it as well.  In theory, 64
addressable devices can be attached to a single SCSI controller.

This sounds complex, so lets simplify it if we can.  One intelligent SCSI
adapter is installed into a system.  To this adapter we can attach either a
device such as a fixed disk, a printer or other device.  It occupies a physical
address as defined by switches or jumpers on the device.  It can be addressed
as device "0", having the lowest priority, or as device "6", having the highest
priority or anywhere in between.  Slow devices usually are set for a low
priority and faster devices are set for higher priorities. The controller is
fixed at address "7" and cannot be altered.  If we were to add an intelligent
device, one that functions as a "sub" controller, this intelligent device, or
more correctly, this controller can have additional devices attached to it.
These devices would have logical addresses rather than physical addresses.
These addresses are referred to as PUA's (Physical Unit Addresses) or LUA's,
(Logical unit addresses).

Two SCSI Adapters
IBM is offering two different SCSI adapters, three SCSI fixed disks and 2 CD
ROM devices.  The standard controller supplied with the PS/2 Model 65 and
certain models of the PS/2 Model 80 is a 16 bit Bus Master card.  It will fit
both a 32 or a 16 bit slot. It has a data transfer rate of 8.3MB/S between the
controller and the system and a data transfer rate of 5MB/S between the
controller and the device.  The SCSI Controller with cache is also a Bus Master
and it also can be inserted in either a 16 or 32 bit slot.  When installed in a
32 bit slot, it operates as a 32 bit adapter for a data transfer rate of
16.6MB/S.  In a 16 bit slot the rate is the same as with the standard adapter.
Both adapters can handle both internal and external devices.

Three SCSI Drives
Three new SCSI fixed disks were announced with the SCSI Adapters. The 320
million byte drive has a 12.5Ms access time making it one of the fastest in the
industry.  The 30 and 60 million byte drives are 23Ms drives and all three are
the 3.5" form factor. Up to 4 drives can be installed in the new model 65 and
the new model 80's. Two CD-ROM drives were announced with an approximately
600MB capacity.  The internal drive occupies the 5.25" drive bay of the floor
standing PS/2's and the external drive can be attached to all IBM Micro Channel
systems.  Multiple drives are supported on all systems.  These drives can play
standard audio CD's or can read data CD's.  A headphone jack is available on
the front of the drives for headphones or connections to an external amplifier.
The external drive has additional L and R audio out jacks on the rear of the
case.  Drivers are provided on the Option/Device Driver diskette to allow such
usage.  A program "IBMCDPLY" is also included that brings up a control panel on
the screen to provide an interface that looks and acts like the control panel
of an audio CD player.  Play, stop, pause, track selection and other controls
are available on the screen.  Once the playing of a CD has started, you can
exit the program and the CD continues to play to the end.  Other DOS
applications can now be run.

Note:  This is a DOS only program.  It operates neither in the OS/2 mode nor in
the DOS compatibility box of OS/2.  An OS/2 version is available with the new
drivers on the OS/2 corrective service/device drivers diskette.

Attachment Kits required
Various attachment kits and cables are also available.  KIT "A" provides a
bracket that allows two drives to be installed in the 5.25" drive bay as well
as power and signal cables.  An external "Option to Option" cable is available
for device to device attachment.  It uses the standard 50 pin SCSI connector. A
"Card to Option" cable is also available to convert the 50 pin card connector
to the 50 pin SCSI standard connector on the first external device.  The 60 pin
connector is too large to mount on the controller so a more compact connector
was used.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.2. Terminating the IBM SCSI Adapters ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

Just as ST-506 and ESDI adapters need a terminating resistor (T-RES) on the
last drive, so the SCSI adapters must be told where to find the "end of the
line".

16-Bit SCSI Adapter
The 16-bit PS/2 SCSI Adapter includes a T-RES terminator chip on the adapter.
This chip must remain in the following instances:

1) If no physical devices (also called PUNs, for Physical Unit Numbers) are
connected to the adapter because it is not currently being used.

2) If the PUNs are all internally attached, or all externally attached.

The T-RES chip must be removed if internal and external PUNs are attached.  In
this case inline terminators (which come with the option cables) are used
between the last internal and external PUNs and the cables connecting them to
the next-to-last PUNs (or the adapter, if the PUN is the only internal or
external device on the chain).

For example, to connect two internal and three external PUNs, the internal
devices would be daisy-chained from the internal 50-pin edge- connector, while
the external devices would daisy-chain from the 60- pin D-shell connector on
the back of the card, as follows.  (Note the terminators.)

Reminder:  Double-click on the highlighted text below to view the footnotes.

Internal                                     External
            Γöî<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
            Γöé            Γöé
            1      ΓöîΓöÇΓöÇΓöÇ\\\\\ΓöÇΓöÇΓöÇΓöÉ
            Γöé      Γöé Adapter * DΓöÇΓöÇΓöÇ2ΓöÇΓöÇΓöÇ>ΓöÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ  Γöî<Γöÿ      ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ        Γöé    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé PUN  ΓöéΓöÇΓöÇΓöñ                             ΓööΓöÇΓöÇΓöÇ>Γöé PUN  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ  Γöö>ΓöÉ                           Γöî<ΓöÇΓöÇΓöÇΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
            Γöé                           Γöé
            1                           3
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ    Γöé                           Γöé    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé PUN  T<ΓöÇΓöÇΓöÇΓöÿ                           ΓööΓöÇΓöÇΓöÇ>Γöé PUN  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ                                Γöî<ΓöÇΓöÇΓöÇΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                                        Γöé
                                        3
                                        Γöé    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                        ΓööΓöÇΓöÇΓöÇ>T PUN  Γöé
                                             ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

If either the internal devices OR the external devices are all removed the
T-RES chip would be needed on the adapter.  All the terminators needed are
included with the various components; however, should the T-RES chip be removed
(and lost), but be needed at a later date, a replacement may be ordered as a
service part (P/N 57F2870).

32-bit SCSI Adapter with Cache
The 32-bit PS/2 SCSI Adapter with Cache is different in the respect that it
does NOT come with an onboard T-RES chip.  There is a separate external
terminator (P/N 6451039; F/C 1039) which must be used if no external devices
are attached.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.3. How Model 90/95 Selective Boot Assigns Drive Letters ΓöÇ Tip ΓòÉΓòÉΓòÉ

The Model 95 will boot from any physical hard drive or floppy drive in the
machine, not logical drives.  For example, 2 physical hard drives could be a
160MB SCSI drive defaulting to drive C: and a 320MB drive defaulting to drive
D:.  When you use the Reference Diskette to change the boot sequence, you are
indicating what sequence you would like the system to check for bootable
devices.  For example:

            Boot device 1:  1.44MB Diskette Drive (A:)
            Boot device 2:  160MB, SCSI ID = 6    (C:)
            Boot device 3:  320MB, SCSI ID = 5    (D:)

Could be changed to this:

            Boot Device 1:  1.44MB Diskette Drive (A:)
            Boot Device 2:  320MB, SCSI ID = 5    (C:)
            Boot Device 3:  160MB, SCSI ID = 6    (D:)

In the first example the system will try to boot the diskette drive first.  If
it does not find a bootable diskette it will try to boot from the 160MB fixed
disk; then the 320MB drive.  The 160MB drive is C: and the 320MB drive is D:.
In the second example, the 320MB drive is C: and the 160MB drive is D:.
Whenever you change the boot sequence, the system warns you that drive letters
will be changed and/or rearranged.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.4. The Whys and Wherefores of DASDDRVR.SYS ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1991)

There is a lot of confusion over what DASDDRVR.SYS is, what it is used for,
which PS/2 models require it, and what exactly it fixes.  The following should
dispel the mystery surrounding DASDDRVR.SYS.

What is it?
DASDDRVR.SYS (Direct Access Storage Device Driver) is a set of software patches
that fix various BIOS bugs common to several PS/2 models.  A common
misconception is that DASDDRVR.SYS is a set of DOS patches; and additionally
that it is not needed with DOS 4.0x; only V3.3.  Both statements are incorrect.

IBM could have chosen to replace thousands of BIOS chips on PS/2 motherboards,
yet went with the software approach.  Why? A program installs DASDDRVR.SYS on a
PS/2 fixed disk drive, and adds a statement to CONFIG.SYS.  Then when the
system is booted, the BIOS patches overwrite the BIOS code in memory (that was
copied from the BIOS ROM chips).  Not only does this give IBM and the user the
flexibility of later replacing DASDDRVR.SYS with a newer version containing
additional BIOS patches, if necessary; but it also eliminates the down time and
inconvenience that would result from taking the system to an authorized
servicer to have the BIOS ROM replaced.

Who needs it?
Originally, a few BIOS bugs were found affecting several PS/2 models.  Two
different versions of DASDDRVR.SYS were written, one for Micro Channel systems,
and one for non-Micro Channel PS/2s.  As time passed, it was discovered that
several more PS/2s were affected by these or newer bugs.  Eventually the two
versions of DASDDRVR.SYS were merged into one, simplifying the effort of
determining what to install on which systems.

So, to make a long story short, DOS 3.3 and 4.0x users who encounter the
specific problems corrected by DASDDRVR.SYS (see below), on the particular PS/2
models listed, should install DASDDRVR.SYS.  The install program will determine
which model you are installing it on, and only install those fixes that apply
to that system.  (Those PS/2 models or submodels not on the list, do not need
DASDDRVR.SYS, and will not benefit by installing it.)

Why isn't DASDDRVR.SYS required on OS/2 or AIX-based PS/2s?  Because these
operating systems routinely replace the hardware BIOS code in memory with
customized software versions, anyway.  So they already contain the fixes
inherent in DASDDRVR.SYS.

What problems does it fix?
There are currently twelve different bugs fixed.  The list below describes the
fixes, and which systems are affected:

Problems                                              Systems Affected
1) Failures occur when reading some 720K
  program diskettes.                                  8530-E01/E21; 8550-021;
                                                      8560-041/071;
                                                      8580-041/071.
2) Intermittent "Not Ready" or "General failure"
  error messages when accessing diskettes.            8550-021; 8560-041/071;
                                                      8580-041/071.
3) 3.5" diskette format failures when attempting
  to format multiple diskettes consecutively.         8550-021; 8560-041/071;
                                                      8580-041/071.
4) Combined 301 and 8502 error messages at
  power on, or after power interruption.              8550-021; 8560-041/071.
5) System clock loses time (8550), or combined
  162 and 163 errors during system POST
  (8560).                                             8550-021; 8560-041/071.
6) Unable to install Power-on Password program
  with DASDDRVR.SYS installed.                        8550-021; 8560-041/071;
                                                      8580-041/071.
7) Device attached to COM2, COM3, or COM4
  not detected.                                       8530-E01/E21.
8) Devices that use interrupt request level 2
  (IRQ2) fail.                                        8530-E01/E21.
9) 3.5" diskette format failures when attempting
  to format more than one diskette.                   8570-Axx (all); 8580-Axx
                                                      (all).
10) System performance degradation from
  processor-intensive devices.                        8550-021/031/061;
                                                      8555-031/061;
                                                      8560-041/071.
11) Error in microcode routine that enhance
  long-term reliability of 60/120MB disk drives.      8550-061; 8555-061;
                                                      8570-061/121/A61/A21;
                                                      8573-061/121.
12) Time and date errors occur when resetting
  time or date.  Intermittent date changes can
  occur when system is restarted by pressing
  Ctrl-Alt-Del.                                       8530 (all).

How do I get and install it?
Most versions of the various Micro Channel PS/2 Reference Diskettes contain
some version of DASDDRVR.SYS.  (The non-Micro Channel PS/2 Model 30 286
provides DASDDRVR.SYS on the Setup Diskette, instead.)  But because there have
been several versions of DASDDRVR.SYS released along the way, with different
numbers of fixes, it is important to get the latest possible version of the
appropriate Reference Diskette.  Depending on the version of the diskette,
there may be additional fixes in a later version.

If you have access to the latest Reference Diskette, use it.  If not, you may
call 800-IBM-7282, and request the PS/2 System Update Diskette (P/N 04G3288.
This diskette contains a version of DASDDRVR.SYS, but it is possible that by
the time you read this and order it, a newer version may have been released on
a new Reference Diskette.  Still, a fairly recent version is better than an
older one you may have on the Reference Diskette that came with the system.  If
DASDDRVR.SYS is already installed on a system, but you don't know whether it is
the latest, just look at the file size.  The current version (as of July 1991)
is 3,068 bytes).

Installation is a snap.  Simply insert the diskette in the A: drive, and type:
A:INSTALL from the C> prompt.  That's all there is to it!  The install program
copies the DASDDRVR.SYS file to the fixed disk drive, and updates CONFIG.SYS to
use it.  After rebooting the system you are done.

One final note:  This driver may be ordered and installed by anyone.  It
includes instructions, and does not require dealer intervention.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.5. Using Paradox V3.5 with the L40 SX ΓöÇ Tip ΓòÉΓòÉΓòÉ

Due to publishing deadlines the following Hint was not included in the Hints &
Tips document shipped with the PS/2 Model L40 SX system:

Borland International Paradox 3.5

You must configure Paradox to run with the PS/2 Model L40 SX.  Paradox provides
a special script to configure Paradox to run with systems that it does not
recognize called CUSTOM.  Failure to run the CUSTOM script will cause your
keyboard to lock up. To customize Paradox, follow the instructions below.

Start Paradox by typing:

PARADOX CUSTOM -REAL

When the Paradox menu is displayed:

 1. Select Tune and Press Enter

 2. Select Protected Mode and Press Enter

 3. Select Configure and Press Enter

 4. Follow the instructions displayed by Paradox

Note:  The Keyboard will lock up.  This is NORMAL.  Turn the system power off
and start the process again.  You must do this at least twice.  On the third
attempt the CUSTOM script will run to successful completion.

While in the Custom script, set AUTOSAVE to NO. Select DEFAULTS, then AUTOSAVE,
than NO.  This prevents damage to disk files when doing a RESUME on the Model
L40 SX.

Copy PARADOXK.EXE to a diskette for safe-keeping.  This file can be restored if
you reinstall Paradox and you will not have to run the CUSTOM program again.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.6. Understanding PS/2 Model Numbers ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 3Q 1991)

There have been so many different PS/2 models, past and present, that it can be
difficult to tell them apart just by the model numbers.  The following is an
attempt to explain the meaning behind these numbers.  Despite appearances, the
numbers and letters do have specific meanings (although in a few cases their
use is not totally consistent).

In an attempt to simplify the process of understanding model differences,
recently IBM started using a new system for designating models.  So, below you
will find two sets of explanations, one for the older scheme, and the other for
the new method:

Note:  @ = A or B; * = Any number or letter.

Old Method: (PS/2 Models 25, 25-286, 30, 30-286, 50, 55, 60, 65, 70, P70, P75, 80)

Models    Meaning
0**       Space-saving keyboard (25-286 only)
12*       120MB Fixed Disk drive
@2*       120MB Fixed Disk drive
16*       160MB Fixed Disk drive
@16       160MB Fixed Disk drive
32*       320MB Fixed Disk drive
40*       400MB Fixed Disk drive
A**       25MHz 386 processor
A3*       25MHz 386 processor; 320MB Fixed Disk drive
B**       25MHz 486 processor
C**       Color Display
E**       10MHz 286 (30-286 only)
E6*       16MHz 386; 60MB Fixed Disk drive (70 only)
G**       Enhanced Keyboard
L0*       4MBps Token-Ring LAN adapter (25 only)
LE*       Ethernet LAN adapter (55 only)
LT*       16/4 Token-Ring LAN adapter (55 only)
M**       Monochrome Display
*2*       20MB Fixed Disk drive
*3*       30MB Fixed Disk drive (Except A3*)
*4*       45MB Fixed Disk drive
*6*       60MB Fixed Disk drive
*8*       80MB Fixed Disk drive
**0       Medialess (no Fixed Disk, no diskette drives)
**1       1 diskette drive
**1       Monochrome Display (25 only)
**2       2 diskette drives
**4       Color Display (25, 25-286 only)
**6       10MHz 286; 1 diskette drive (25-286 only)

To illustrate:

Models            Meaning
Model 25-G04      Enhanced keyboard and a built-in color display.
Model 25-036      Space-saving keyboard, a 30MB fixed disk drive, and a 10MHz
                  286 processor.
Model 70-A21      25MHz 386 processor, a 120MB fixed disk drive, and one
                  diskette drive.

New Method: (PS/2 Models 35, 40, L40, N51, 56, 57, CL57, M57, 90, 95)

Models    Meaning
0**       Standard processor complex design
1**       Advanced processor complex design; or Ethernet system
2**       16/4 Token-Ring LAN Adapter standard; or Multimedia system
4**       Custom configuration for Special Bid purchase
*2*       16MHz 386SLC
*3*       16MHz 386SX
*5*       20MHz 386SLC
*G*       20MHz 486SX
*H*       25MHz 486SX
*J*       25MHz 486DX
*K*       33MHz 486DX
*L*       50/25MHz 486DX2
*M*       50MHz 486DX
**0       No Fixed Disk, one diskette drive
**1       8512 Color Display included
**2       8511 Color Display included
**3       40MB Fixed Disk drive
**4       60MB Fixed Disk drive
**5       80MB Fixed Disk drive
**9       160MB Fixed Disk drive
**D       320MB Fixed Disk drive
**F       400MB Fixed Disk drive
**T       1GB Fixed Disk drive
**X       Medialess (no Fixed Disk, no diskette drives)

For example:

Models            Meaning
Model 35-24X      Token-Ring adapter, 20MHz 386SX processor, and no drives.
Model 40-040      20MHz 386SX processor, a diskette drive, but no fixed disk
                  drive.
Model 90-0J9      25MHz 486 processor, and a 160MB fixed disk drive.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.7. Understanding XGA ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Chris Gaskins
(From The IBM Advisor, the technical newsletter for IBM dealers; 3Q 1991)

What is XGA and how do I use it?  This is a very common question at the NSC.
Since XGA emerged, there has been much confusion about its installation and
functionality.  Hopefully, this column will clear the air on XGA installation,
and on the technology behind XGA as well.

XGA vs. 8514/A
First, I want to stress the differences between the XGA card and the 8514/A
Display Adapter.  The 8514/A card simply provides a high resolution of 1024 X
768 with 16 or 256 colors in this mode, depending on the amount of memory
installed on the card. This card works on any Micro Channel system unit that
has an adapter slot with the video extension connector.  The 8514/A card only
functions in that slot because it only has a high resolution processor and not
a VGA compatible processor.  When the system is running applications in VGA
mode (or lesser resolutions) the 8514/A card simply passes the VGA information
from the system board VGA controller through the Auxilliary Video Extension
(AVE).  When applications require high resolution, a TSR program called HDILOAD
(provided with the adapter) installs the 8514/A Adapter Interface (AI) code.
The 8514/A AI is basically a gateway to the 8514/A adapter.  Since IBM never
published the hardware register information for the 8514/A, all applications
had to write to the AI, which in turn writes directly to the hardware on the
card.  The 8514/A can not function unless it has a video system to supply VGA
mode (and lower) video signals.

So much for the review of 8514/A.  Now lets get into XGA.  The XGA card is an
entire graphics subsystem that provides a maximum resolution of 1024 x 768 as
well as all VGA modes. It does not have to rely on a video subsystem on the
motherboard of the machine where it is installed.  The XGA card is also a Bus
Master, which means it can do its own processing and memory accesses without
having to use the main system processor, providing faster video processing and
freeing up the main processor for other tasks.  The XGA card has a 32-bit Micro
Channel connector; but can be placed in a 16-bit slot; however there is a
performance penalty if the card is used in a 16-bit slot.  Another vast
difference in the XGA card is that it only functions in 386SX or higher
systems.  This is because the drivers and the card itself have been optimized
to work with the 386 32-bit instruction set, also increasing the performance of
the card.  The XGA card comes standard with 512KB of VRAM which provides a
maximum resolution of 1024 x 768 with 16 colors.  If the memory is upgraded to
a full 1MB the maximum increases to 1024 x 768 with 256 colors.

Installing XGA
Installation of the XGA card is much like the installation of any other Micro
Channel adapter.  First, simply place the card in a Micro Channel expansion
slot.  A 32-bit slot is preferred, due to the speed advantage mentioned
earlier.  There is however one slot the XGA card will not fit, and that is the
slot with the AVE.  The XGA card does have an extension that looks much like
the 8514/A extension; however, upon closer inspection you will see the
extension on this card is positioned differently.  The positioning of the XGA
extension tab will prevent it from being inserted into the slot with the
auxiliary video extension.  What is the extension for on the XGA card, you ask?
Currently only one PS/2 has an expansion slot that will accommodate the
extension on the XGA card.  That system is the PS/2 Model 95.  Why?

First, lets review the purpose of the 8514/A video extension.  Remember that
the extension of the 8514/A card allows the applications that run in VGA mode
to viewed on the screen.  The 8514/A card is simply pulling the VGA signals
from the system board through that video extension and out the display port on
the back of the adapter card.  Now, as you recall, the XGA card has its own
video processor that can handle VGA and high resolution modes.  The Model 95 is
the only PS/2 that does not have a video subsystem integrated onto its system
board, but instead is shipped with an XGA adapter already installed.

Suppose you wanted to place an adapter in the Model 95 that required VGA
signals from the main video subsystem.  This could be the IBM PS/2 Image
Adapter/A or possibly the IBM PS/2 M-Motion Adapter/A (the 8514/A card is not
supported in the Model 95).  For an adapter of this type to function in the AVE
slot the XGA card must be plugged into the one slot that can accommodate its
Base Video Extension (BVE).  The reasoning behind this is the BVE takes VGA
signals from the XGA card and routes them directly to the Auxiliary Video
Extension that the M-Motion or Image Adapter is using.  Once the card is
configured and a display attached, nothing more needs to be done to get normal
operation from the XGA card; normal operation being VGA modes only.

The XGA card only occupies 8KB of memory between 640KB and 1MB.  Since the XGA
card is a Bus Master, it can occupy any 8KB in the "C" or "D" range.  To see
which part of memory is being used by the XGA card, choose the menu option
"Display Memory Map" from the Reference Diskette.  Another great feature of the
XGA card is that you can have up to six XGA cards installed in one machine
(five if the system has XGA already on the system board, like the Model 90).
To take advantage of multiple adapters, software must be specifically written
to do so.  If you have an XGA card in a system that has VGA on the system board
and a display attached just to the XGA card, the XGA card will function in VGA
and high resolution modes.  Now, if you have the same setup as before but a
display is attached to the system board VGA port and another to the XGA card,
all VGA (and lower modes) will be displayed on the display attached to the
system board port.  The XGA card will only be used when high resolution is
required.  You will not get an echo of a VGA image onto the display attached to
the XGA port as you would using the 8514/A.

Once the card is installed, the appropriate device driver must be installed
before the high resolution can be accessed. There are two device driver
diskettes that come with the XGA card.  The first diskette contains all of the
device drivers for DOS, Microsoft Windows 3.0, Microsoft Windows 286 2.1, and
AutoCAD Release 10.  The second diskette contains support for OS/2 1.2 (OS/2
1.3 ships with an XGA driver).  The latest driver diskette is version 1.10.2,
which is currently available for downloading from the TA Bulletin Board System.

Installing device drivers for the XGA card is a subject all to itself; so I
will save that information for a later column. Hopefully this has increased
your understanding of the XGA card.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.8. L40 SX Battery Concerns ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Wally McCourt
(From The IBM Advisor, the technical newsletter for IBM dealers; 3Q 1991)

Well, the IBM L40 SX Laptop has been around a few months, and there are a few
things that have generated a number of questions. These questions have been in
the area of the battery, suspend/resume, and the PS/2 Power Management Program.
All three of these areas are very inportant to any user who wants the most from
the L40 SX; each plays a vital part in the longevity of the system on battery
power. Hopefully, the following information will help you in answering your
customers' questions and concerns.

Before I start, I want to clarify that the L40 SX has three batteries. The one
everyone is familiar with is the removeable, rechargable battery. This is
located at the back of the system behind the center door. The second battery is
the "bridge" or standby battery.  This is used when the system is in suspend
mode. The standby battery stores the state of the system when the rechargeable
battery is removed during operation. This allows batteries to be changed
without turning off the L40 SX. The standby battery needs a full 48 hour charge
when the system is first set up. The third battery is the CMOS battery. This is
a five-year lithium battery that stores the system setup information and does
not get charged at all.

Conditioning/Recharging
The first area of concern is with the battery's conditioning, length of usage,
and recharging. First, let's talk about Ni-Cad batteries. Rechargable batteries
take awhile to be conditioned.  The way Ni-Cads are conditioned is by fully
charging and discharging them. Ni-Cad batteries do not provide full power after
the initial charge.  It takes several cycles (charge and discharge) before they
reach their optimum performance level.  Ni-Cad batteries develop a "memory" of
the cycle.  In simple terms, if a new battery is charged for one hour and
discharged for one hour, they will develop a memory to deliver power for that
amount of time.  From my experience, it will take six to ten complete cycles to
condition the battery for optimum performance.  This is done by a full ten hour
charge from the A/C adapter or a 2.5 hour charge on the quick charger.
Normally, the system has used the battery charge when the low battery alarm
sounds and the system enters suspend/resume mode. This should be a sufficient
discharge before recharging.

HINT:  I had a battery that was not giving me more than forty-five minutes. I
put a couple of wires on a 12V automobile taillight and used this to do a deep
discharge of the battery; next, I recharged it.  This procedure was done
several times. I now get more than three hours out of this battery using the
power management routines discussed below.

Suspend/Resume
The second area of confusion is the Suspend/Resume feature of the L40 SX
laptop.  A key player in this function is the "bridge" battery.  As mentioned,
the "bridge" battery needs a FULL 48 hour charge before its first use.  After
that, it receives a charge from the A/C adapter or the rechargable battery.
This battery is only used when the system goes into Suspend/Resume mode
(indicated by the LCD icon to the right of the on/off switch).  The way it
works is, if you are in the middle of an application such as Lotus 1-2-3, and
the system sounds a low-battery warning, all that needs to be done is to shut
the cover of the system, remove the dead battery, and replace it with a
fully-charged battery, or plug the A/C adapter into it.  When the system cover
is reopened, the system is restored to the application that was being used.


Power Management
The third part to the equation is the Power Management program, PS2.EXE. This
is found on the reference diskette for the L40 SX and is the heart of this
complex power management system.  The PS2.EXE program controls the onboard I/O
devices and some other functions of the L40 SX, including the speed of the
processor.  This is the most important part to getting the most usage from the
battery.  This program gives the user the option to put the hard disk to sleep
after a specified number of minutes.  In addition, the display can be blanked
after a specified time along with suspend/resume being enabled after a
specified amount of time. These options can save battery power, but not as much
as a few others.

The blue switch at the left of the "dashboard" controls the processor speed. It
has two settings "A" for Automatic and "M" for Manual. The function of this
switch is controlled by PS2.EXE.  With PS2.EXE the user can set the processor
speeds to use in Automatic mode and Manual mode.  In Automatic mode the
processor can be set to High Performance (20MHz) or Long Battery Life (5 MHz).
In Manual mode the user can define the particular speed that the system is to
run, either 5Mhz, 10Mhz or 20MHz.  This allows the user to specify that when in
Automatic mode to use Long Battery Life, and by pushing the blue switch to
Manual mode go to 20Mhz for, say, a spreadsheet recalculation.  Set the
switches for the way the system is being used. More information can be found in
the reference manual for the system, including tips on how to invoke the
functions of the PS2.EXE program from BATCH files.  Other options can be set to
turn on/off the Fax/Modem, the serial port, the parallel port, and select the
keyboard speed. All of these settings can shorten or lengthen the life of a
battery charge.

The PS2.EXE program and the other tips above are the key to the advertised
maximum battery life of "up to 3 hours."  Please take the time to read the
"HINTS & TIPS" supplement enclosed with the system unit.  This will help you
and your customers get the most from the PS/2 L40SX laptop!

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.9. Communicating with the L40SX Fax/Modem ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Wally McCourt
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1992)

The Data/Fax Modem option for the IBM Personal System/2 L40SX enables the user
to communicate electronically with another computer, and send/receive
facsimiles from any RJ-11 telephone jack.

Modem
The modem portion of this option is a Hayes-compatible modem that operates at
300, 1200, or 2400 bits per second.  It is capable of using any communications
program that uses the Hayes Attention (AT) command set.  Programs such as
Crosstalk, PMcomm, Procomm, Qmodem, Unicom, IBM File Transfer and Terminal
Emulation (FTTERM), and IBM Personal Communications/3270 provide the user with
a wide variety of ways to connect to the system of their choice.  The modem
complies with International Telegraph and Telephone Consulting Committee
(CCITT) V.22bis, V.22, V.21, Bell 212A and Bell 103 specifications.  It also
supports error correction and the data compression/expansion functions of
Microcom Network Protocol (MNP) service classes 4 and 5.

Fax
The other portion of the Data/Fax Modem is the Fax.  The fax option comes with
its own Fax Utility software.  This utility enables users to send, receive,
view, and print fax images.  The fax option is based on a facsimile service
Class 1 that provides a basic service necessary to support Group 3 facsimile
machines.  The communication protocol of the fax option conforms to CCITT
recommendations V.29, V.27ter, and V.21 Channel 2 and communication protocols
that conform to CCITT T.4 and T.30.

Using the Modem
The modem will enable users to connect with their corporate mainframe
computers, mid-range systems, subscription based services (such as CompuServe
and Prodigy), bulletin board systems, and other personal computers.  This is
accomplished by using the appropriate communications software for the system
being connected to.  The table below references some commonly used software to
attach to the various environments.

Comm Environment           Comm Software
IBM Mainframe (3270)       IBM File Transfer and Terminal Emulation Program
                           (FTTERM), Personal Communications/3270
AS/400, DEC, etc.          Crosstalk, FTTERM, PMcomm, Procomm, Qmodem, Unicom
CompuServe                 CompuServe Information Manager, Crosstalk, FTTERM,
                           PMcomm, Procomm, Qmodem
Prodigy                    Prodigy Service software
Bulletin Board Systems     Crosstalk, FTTERM, PMcomm, Procomm, Qmodem, Unicom

The modem is used for information access on the type of system environments
mentioned above.  In addition to connectivity, the modem can be used to
exchange or transfer information (files) from one system to another.  An
example of this would be "uploading" or "downloading" a file from a BBS,
CompuServe or another computer system.  Follow the procedures for the
particular communications software you are using.

Using the Fax
The fax is used to send American National Standard Code for Information
Interchange (ASCII) files, Tagged Image File Format (TIFF), and the PCX
Graphical File Format.  ASCII files are standard text, without any imbedded
codes from a word processor.  A common example of this would be the
AUTOEXEC.BAT or CONFIG.SYS files.

Most word processors give the user an option to "SAVE FILE AS ASCII."  If this
step is not performed, the file will not fax correctly.  Faxed files cannot be
edited or modified; they are similar to a photograph of the document, instead
of individual words.  If a file is to be modified by the recipient then it must
be transferred to the other computer via the modem, not the fax.

Hint:  If problems are experienced when trying to fax a document created by a
word processor, fax your AUTOEXEC.BAT or CONFIG.SYS as a test of the hardware.
If this works, then it is possible the document is not stored in an ASCII
format.

TIFF and PCX files are created by a variety of "paint" or "draw" type programs
and are also supported by many scanner programs.  Microsoft Windows Paint
allows the creation of PCX files.  These files can be transmitted with the
Fax/Modem Utility as long as they do not contain color, and have not been saved
in a color file format.  ASCII information can be "cut 'n pasted" into the
Paint program and the entire file can be sent as a PCX file.

EXAMPLE:
Under Windows Paint menu select Option/ Image Attributes/ and set Colors to
Black and White.  After creating the image, select the File menu.  Choose the
Save As option.  At this point select Options and choose the PCX format.  Enter
the (filename).PCX and save the file.  The file can then fax correctly.

Similar options need to be selected for other paint and scanning programs.  If
a file is created with color, a message from the FAX utility will indicate that
the file contains color and will not fax.  TIFF is commonly used for scanned
images such as a document or picture.  The bottom line is: if the file was
stored as a color image, it will not fax. Many paint and scanning packages also
provide the capability to convert graphic file formats from one to another,
such as TIFF to PCX, or Graphical Interchange Format (GIF) to TIFF, or
Microsoft Paint format (MSP) to PCX, etc.  Basically, through these utilities
you can convert one format to another.  Utilities to convert image formats are
also available on bulletin boards, such as the NSC Technical Advisor BBS, and
CompuServe.

Reminder:  Use the modem to send a file in an editable form to another
computer.  Use the fax to send an image that is not to be updated or modified.

The IBM Fax Utility for the PS/2 Model L40SX is the only software supplied with
the L40SX Data/Fax Modem option.  This provides only the necessary basic
software for the fax feature of the option.  More sophisticated fax software
for the L40SX may also be available separately from other vendors.
Communication software for the modem must be purchased separately.

The IBM Fax Utility provides five functions: OPTIONS, SEND, RECEIVE, PRINT, and
VIEW.  The commands are preceded by the command: FAX.  To modify the Options,
type: FAX OPTIONS. This is used to "setup" the Fax Utility.  This is
user-definable information such as Tone or Dial, Printer type, communications
port, Fax Header information, etc.  The other functions are entered as:

To send:
FAX SEND FILENAME.EXT {PhoneNumber}

To receive:
FAX RECEIVE  (Fax is automatically named RECV000X.FAX, where X is incremented
for each file received)

To print:
FAX PRINT FILENAME.EXT

To view a fax:
FAX VIEW FILENAME.EXT

FAX SEND, FAX RECEIVE, FAX PRINT, and FAX VIEW are fairly self-explanatory.
Refer to the Fax Utility documentation for additional information.

Hopefully, this information has cleared up some of the confusion about using
the L40SX Fax/Modem option.  Happy Communicating!

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.10. Duplexing on a PS/2 Model 57/90/95 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Greg Burton
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1992)

If you are setting up a PS/2 Model 57, 90, or 95 system for duplex operation,
install the second SCSI controller, all drives and all options that will be in
the system.  One drive on the second controller should be set for SCSI ID 6.
This will enable the system to boot from this drive in the event of failure.
Be sure to copy all Option Diskettes to the system partition and then follow
the steps below.

 1. Boot the system to the system partition and configure the system as
    necessary. If anything has to be changed manually, this is the time to do
    it.  It will save much time later.
 2. Insert a blank 1.44MB diskette in drive A:.  (It will become a Reference
    Diskette.)
 3. Back up the system partition to the blank Reference Diskette.
 4. Turn the system off and swap the SCSI cables at the controller end.
 5. Boot to the Reference Diskette just made, and restore the system partition.

If the drives are the same, the system will not need to be reconfigured.  To
simplify recovery in the event of failure it is recommended that 1) the drives
be of the same capacity on both controllers, 2) both controllers have the same
number of physical drives, and 3) the addresses be set the same on both the
adapters and the drives.  (Each adapter has, for example, SCSI ID 7 for the
controller, SCSI ID 6 for the first drive on each controller, SCSI ID 5 for the
second drive on each controller and so forth.)  This enables the system to be
brought back up without having to be re configured in some cases.

In the event of drive failure, the cables can be swapped at the controller end
to get the system back in operation.  In the event of a controller failure, the
failing controller can be removed. Remember, both drives have system partitions
on them, but the drive set to SCSI ID 6, and attached to the SCSI adapter in
the lowest numbered slot is the only one that can load the system partition.
If we remove the adapter from slot 1, the system will boot from the adapter in
slot 2.  The system will need to be reconfigured, but that can be done from the
existing system partition on the backup drive.

If any drive or controller is removed, the system will need to be reconfigured,
but if the system is powered down and the defective component is swapped with a
good component of the same specification, the system will not need to be
reconfigured.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.11. PS/1 & PS/2 System BIOS Information ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1992)

The following table lists the BIOS Model, Submodel, and Revision Level bytes
for all PS/1 and PS/2 models, past and present.

PS/1 System Type                     Model / Submodel / Revision ─ BIOS Date
2011  (10MHz 286)                    FC / 0B / 00
2121  (16MHz 386SX)                  F8 / 30 / 00

PS/2 System Type                     Model / Submodel / Revision ─ BIOS Date
Model 25/25LS  (8MHz 8086)           FA / 01 / 00 ΓöÇ 06/26/87
                                     FA / 01 / 01 ΓöÇ 11/02/88
Model 25  (10MHz 286)                FC / 09 / 00
Model 30  (8MHz 8086)                FA / 00 / 00 ΓöÇ 09/02/86
                                     FA / 00 / 04 ΓöÇ 01/31/89
Model 30  (10MHz 286)                FC / 09 / 00 ΓöÇ 08/25/88
                                     FC / 09 / 01 ΓöÇ 11/30/88
                                     FC / 09 / 02 ΓöÇ 05/30/89
                                     FC / 09 / 03
Model 35/35LS (20MHz 386SX)          F8 / 19 / 05 ΓöÇ 03/15/91
                                     F8 / 19 / 06 ΓöÇ 04/04/91
                                     F8 / 19 / 07 ΓöÇ 06/04/91
Model 40  (20MHz 386SX)              F8 / 19 / 05
                                     F8 / 19 / 06 ΓöÇ 04/04/91
                                     F8 / 19 / 07 ΓöÇ 06/04/91
Model L40 (20MHz 386SX)              F8 / 23 / 01
Model 50  (10MHz 286)                FC / 04 / 00 ΓöÇ 02/13/87
                                     FC / 04 / 01
                                     FC / 04 / 02 ΓöÇ 11/02/89
Model 50Z (10MHz 286)                FC / 04 / 03 ΓöÇ 01/28/88
                                     FC / 04 / 04 ΓöÇ 05/12/88
Model N51 (16MHz 386SX)              F8 / 99 / 04 ΓöÇ ??/??/??
Model N51 (16MHz 386SLC)             F8 / ?? / ?? ΓöÇ ??/??/??
Model 55  (16MHz 386SX)              F8 / 0C / 00 ΓöÇ 11/02/88
                                     F8 / 0C / 01
Model 55LS (16MHz 386SX)             F8 / 1E / 00 ΓöÇ 02/08/90
Model 56  (20MHz 386SX)              F8 / ?? / ?? ΓöÇ ??/??/??
Model 56  (20MHz 386SLC)             F8 / ?? / ?? ΓöÇ ??/??/??
Model 57  (20MHz 386SX)              F8 / 26 / 01 ΓöÇ 05/10/91
Model 57  (20MHz 386SLC)             F8 / 25 / 06 ΓöÇ 08/21/91
Model CL57 (20MHz 386SX)             F8 / ?? / ?? ΓöÇ ??/??/??
Model M57 (20MHz 386SLC)             F8 / 25 / 06 ΓöÇ 08/21/91
Model 60  (10MHz 286)                FC / 05 / 00 ΓöÇ 02/13/87
Model 65  (16MHz 386SX)              F8 / 1C / 00 ΓöÇ 02/08/90
Model 70  (16MHz 386)                F8 / 09 / 02 ΓöÇ 04/11/88
                                     F8 / 09 / 03 ΓöÇ 03/17/89
                                     F8 / 09 / 04 ΓöÇ 12/15/89
Model 70  (20MHz 386)                F8 / 04 / 02 ΓöÇ 04/11/88
                                     F8 / 04 / 03 ΓöÇ 03/17/89
                                     F8 / 04 / 04 ΓöÇ 12/15/89
Model 70  (25MHz 386)                F8 / 0D / 00 ΓöÇ 06/08/88
                                     F8 / 0D / 01 ΓöÇ 02/20/89
Model 70  (25MHz 486)                F8 / 1B / 00 ΓöÇ 12/01/89
Model P70 (16MHz 386)                F8 / 50 / 00
Model P70 (20MHz 386)                F8 / 0B / 00
                                     F8 / 0B / 02
Model P75 (33MHz 486)                F8 / 52 / 00
Model 80  (16MHz 386)                F8 / 00 / 00 ΓöÇ 03/30/87
                                     F8 / 00 / 01
                                     F8 / 00 / 02 ΓöÇ 06/19/89
Model 80  (20MHz 386)                F8 / 01 / 00 ΓöÇ 10/07/87
Model 80  (25MHz 386)                F8 / 80 / 01 ΓöÇ 11/21/89
                                     F8 / 80 / 02 ΓöÇ 02/15/90
Model 90  (20MHz 486SX)              F8 / 2D / 00 ΓöÇ 04/24/91
Model 90  (20MHz 486SX)              F8 / 2F / 00 ΓöÇ 04/24/91 (With 487SX Math
                                     Coprocessor Option)
Model 90  (25MHz 486SX)              F8 / 57 / 00
Model 90  (25MHz 486SX)              F8 / 59 / 00       (With 487SX Math
                                     Coprocessor Option)
Model 90  (25MHz 486)                F8 / 11 / 00 ΓöÇ 10/01/90
Model 90  (33MHz 486)                F8 / 13 / 00 ΓöÇ 10/01/90
Model 90  (50MHz 486)                F8 / 2B / 00
Model 95  (20MHz 486SX)              F8 / 2C / 01 ΓöÇ 04/24/91
Model 95  (20MHz 486SX)              F8 / 2E / 01 ΓöÇ 04/24/91 (With 487SX Math
                                     Coprocessor Option)
Model 95  (25MHz 486SX)              F8 / 58 / 00
Model 95  (25MHz 486SX)              F8 / 5A / 00       (With 487SX Math
                                     Coprocessor Option)
Model 95  (25MHz 486)                F8 / 14 / 00 ΓöÇ 10/01/90
Model 95  (33MHz 486)                F8 / 16 / 00 ΓöÇ 10/01/90
Model 95  (50MHz 486)                F8 / 2A / 00

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.12. Comparison of 386SX/386SL/386SLC/386DX/486SX/486DX/486DX2 Processors ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

There is considerable confusion over the similarities and differences between
the various "flavors" of the 386 and 486 microprocessors used in PS/2s and
other vendors' systems; especially regarding 32-bit operating system
compatibility.  The following is an attempt to compare and contrast the salient
features of each in tabular form.

Note:  Important differences are highlighted in red.

ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Feature                     Γöé386SXΓöé386SLΓöé386SLCΓöé386DXΓöé486SXΓöé486DX2Γöé486DXΓöé
ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓö╝ΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
32-bit Instruction Set      ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
32-bit Internal Processing  ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
100% S/W Compat. with 386DX ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Supports 32-bit Op. Systems ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  ΓöéYes  ΓöéYes   ΓöéYes  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
16/32-bit External Data PathΓöé16   Γöé16   Γöé16    Γöé32   Γöé32   Γöé32    Γöé32   Γöé
                            Γöé     Γöé     Γöé****  Γöé     Γöé     Γöé      Γöé     Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Speeds available (MHz)      Γöé16   Γöé     Γöé16    Γöé16   Γöé     Γöé      Γöé     Γöé
(numbers represent internal Γöé20   Γöé20   Γöé20*   Γöé20   Γöé20   Γöé      Γöé     Γöé
and external speeds, except Γöé     Γöé25   Γöé      Γöé25   Γöé25   Γöé      Γöé25   Γöé
where noted)                Γöé     Γöé     Γöé      Γöé33   Γöé     Γöé      Γöé33   Γöé
                            Γöé     Γöé     Γöé      Γöé     Γöé     Γöé50/25 Γöé     Γöé
                            Γöé     Γöé     Γöé      Γöé     Γöé     Γöé***** Γöé50   Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Internal Processor Cache    ΓöéN/A  ΓöéN/A  Γöé8K    ΓöéN/A  Γöé8K   Γöé8K    Γöé8K   Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Internal Floating Point UnitΓöéNo   ΓöéNo   ΓöéNo    ΓöéNo   ΓöéNo   ΓöéYes   ΓöéYes  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
External Math Coprocessor   Γöé387SXΓöé387SXΓöé387SX Γöé387  Γöé487SXΓöéN/A   ΓöéN/A  Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Internal Power Management   ΓöéNo   ΓöéYes**ΓöéYes** ΓöéNo   ΓöéNo   ΓöéNo    ΓöéNo   Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Developed By                ΓöéIntelΓöéIntelΓöéIBM***ΓöéIntelΓöéIntelΓöéIntel ΓöéIntelΓöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Manufactured By             ΓöéIntelΓöéIntelΓöéIBM   ΓöéIntelΓöéIntelΓöéIntel ΓöéIntelΓöé
                            ΓöéIBM  Γöé     Γöé      ΓöéIBM  Γöé     Γöé      Γöé     Γöé
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

* The performance of IBM's 16MHz 386SLC is approximately 80% better than a
16MHz Intel 386SX; equivalent to a 25MHz 386SL.  IBM's 20MHz 386SLC is
approximately 88% better than Intel's 20MHz 386SX; 7% better than a 25MHz
386DX.  Faster 386SLC versions are planned for later in 1992.
** An important feature in laptops and other battery-operated systems.
*** Based on Intel's 386 series design.
**** The 16-bit data path results in about 10% lower performance than the 386DX
processor.
***** The Intel 486DX2 processor runs internally at twice the speed of the rest
of the system, such as 50/25MHz, producing performance faster than a 25MHz
486DX, but less than a 50MHz 486DX.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.5.13. Screen-Saving Tips ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1992)

The following are some tips to help you prevent "ghost" images from being
burned into your computer monitor, save money, and do your part to conserve
energy all at once.

Burn-in results from the same image appearing in the same place on the screen
hour after hour, day after day.  If you turn off your display when not needed
(say, when your system is "number-crunching" in the background, and nothing
much will be happening on-screen for quite a while; or while you are out to
lunch; or overnight, if you leave your computer running), or use a
"screen-blanking" program, you will have gone a long way toward preventing
burn-in.  Also, while you are actively using the monitor, turn the brightness
down to the lowest comfortable level.  Many displays allow you to "over drive"
the monitor by turning the brightness up too high.  This not only promotes
burn-in, but also tends to cause the image to become blurrier and harder to see
over the course of several years, thus shortening the monitor's effective life.

Turning off the monitor when not needed also provides a tangible financial
benefit.  Two, in fact:

 1. If, for example, you typically leave the computer (including the display)
    on 24 hours a day, every day, you are using more than four times as much
    electricity as if it is only turned on 5 days a week, for 8 hours a day.
    Less usage would mean less of a cost difference, but you get the idea.
 2. Using the same scenario, each monitor has a finite life expectancy, as we
    all do.  By leaving it on every hour of every day, it will wear out more
    than four times faster than if only turned on 40 hours a week (a week has
    168 hours, after all); which means buying a new display that much sooner.

Some people justify leaving the monitor on all the time with the argument that
the "sudden power surges generated by turning the display on cause such
stresses that it will fail sooner than if you leave it on all the time."  That
may  have been true once upon a time, but any good computer or monitor nowadays
has built-in internal surge suppression adequate to keep this from happening
(this is a separate issue from suppression of external sources, such as
lightning).  There is simply no good reason to leave the display on when it is
not being viewed.

For those times during the day when you may be absent for various periods of
time, and turning off the monitor would be a nuisance, a screen-blanker program
is useful.  What this does, after a set amount of time, or at the user's
command, is replace the text and images normally on your screen with either a
static image (something without a lot of bright spots, and straight lines,
preferably) or a set of moving pictures (a dynamic blanker).

OS/2 1.30.1 and 2.0 include a combination keyboard-password/static
screen-blanker program called Lockup, that allows you to display any OS/2
bitmap image (several are supplied, but others can be added), and can be
started either manually, or by timer.  In addition, 2.0 also includes a dynamic
blanker as part of the Cat and Mouse program (which can only be started
manually). DOS and Windows users don't get a built-in blanker, but there are
several commercial packages available, including:

o After Dark (Berkeley Systems)
o Idle Wild (part of Microsoft Windows 3.0 Entertainment Pack)
o Intermission (ICOM Systems)
o Pyro (Fifth Generation Systems)

Note:  These programs were listed as examples.  This is not a recommendation or
endorsement by IBM.

To return to the PS/2 Hardware Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6. OS/2 1.x Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on IBM OS/2 V1.x and related products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips Documents
OS/2 Performance Tuning                                 HPFS Advantages
                                                        OS/2 1.3 Enhancements                                   Patching Prodigy 3.1 to Run in the DOS Box
                                                        OS/2 Printer Driver Installation and Configuration      Backing up OS/2 .INI Files
Adobe Type 1 Font Installation in OS/2 1.3              Free OS/2 Utilities
                                                        Increasing Environment Space in OS/2-DOS Modes          Introducing IBM TCP/IP for OS/2
                                                        Maximum Partition Sizes Supported by OS/2               XGA Configuration for OS/2
                                                        Installing XGA drivers for OS/2 1.20                    Installing XGA drivers for OS/2 1.30
Stacking Multiple Commands on Command Line              OS/2 Memory Map
                                                        Minimizing OS/2 1.2 Disk Storage Requirements           Adding DOS Programs to Program Selector
                                                        Changing the Default Font Size of VIO Windows           Changing the Default VIO Window Size
                                                        Setting Up 109-Line Command Prompt Windows              Installation of OS/2 on Multiple Systems
                                                        Improving Sluggish PS/2 Mouse Performance               Printers/Plotters Supported by OS/2 1.3
3270 Emulation Tips                                     OS/2 System Limits

Or, to return to the Technical Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.1. OS/2 Performance Tuning ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

There are several simple steps that can be taken to obtain the maximum
performance from the base OS/2 V1.2 or 1.3 operating system:

1) Unless the Dual Boot feature (which allows you to boot from DOS or OS/2
interchangeably) is required, always format your disk using the High
Performance File System (HPFS).  HPFS replaces the traditional DOS-OS/2 File
Allocation Table (FAT) method of storing data on the drive with a newer, more
sophisticated method.  HPFS is affected to a much smaller degree by the number
or size of files, and file fragmentation is nearly eliminated.  There isn't
room in this column to describe HPFS in detail, but benchmarks show a 30-300%
improvement in disk performance versus a FAT partition.  (For more information
on the specifics of HPFS, please refer to the article "Design Goals and
Implementation of the new High Performance File System", by Ray Duncan, in the
IBM Personal Systems Technical Solutions, Issue 2, 1990.)

2) If Dual Boot is required, consider partitioning your bootable C: partition
as FAT, and either a second (D:) partition on the physical C: drive or a second
physical drive, with HPFS.  At least some of your program and data files will
be able to take advantage of HPFS.  (In fact, even DOS programs running in the
DOS compatibility box can run from an HPFS driveΓöÇΓöÇsomething DOS itself can't
do!)

3) If using a FAT partition, try to limit the number of files in any
subdirectory to under 200 (less if possible). You are much better off having
many directories with few files in them (as long as it makes sense from a
usability standpoint).  Because directory listings are read sequentially, the
last file on the list (which is actually the first, as directories are read
backwards) takes much longer to find than the first.  And several levels of
directories will be faster than having all directories off the root.

4) Increase the BUFFERS= statement in CONFIG.SYS to 50 buffers, from the
default of 30.  Benchmarks show a significant performance increase going to 50
buffers, but no benefit beyond 50.  This performance boost comes at a penalty
of only 10K of RAM.  Cheap at the price.

5) If you have the RAM, the best thing you can do is increase the size of the
OS/2 cache.  On a FAT system, the DISKCACHE= statement in CONFIG.SYS should be
increased from the default of 128K, to 256K.  No advantage is gained by going
beyond 256K.

On an OS/2 1.2 HPFS system, the applicable CONFIG.SYS statement is:
IFS=C:\OS2\HPFS.IFS /C:xxxx.  The default HPFS cache size is 64K (/C:64).
There is a dramatic performance improvement going from 64K to 256K, a slightly
smaller increase going from 256K to 512K, a slightly smaller gain going to 1MB,
and a smaller, but still significant, improvement going to 1.5MB.  Beyond 1.5MB
performance actually DEGRADES, as it takes so long to read the huge cache that
all gains by having the data ready to go are negated.  The closer to 1.5MB you
can get (memory permitting) the better your performance.

For OS/2 1.3, the default cache has changed from 64K to 20% of installed RAM,
however this default also can be overridden with the /C:xxxx parameter above.
You may wish to experiment to determine the best cache size for your operation.

If you have a system with both FAT and HPFS partitions, you will need to set up
both types of cache (DISKCACHE and CACHE) in CONFIG.SYS.

CAVEAT:  Never allocate so much memory to caching that there is insufficient
memory left for application use.  Lack of memory will cause disk swapping,
which will more than offset any gains made by caching.

6) On an OS/2 1.2 HPFS system, you may wish to enable "lazy writing". Caching
normally buffers the data coming from the (slow) disk drive to the (fast)
memory.  Lazy writing also allows buffering from memory back to the disk.  This
allows the system to wait until the disk drive is not in use, rather than
writing immediately and possibly having to wait for another job to finish using
the fixed disk.  To use lazy write, add the following statement to CONFIG.SYS:
RUN=C:\OS2\CACHE /LAZY:ON

In 1.3 Lazy writing is the default.  To disable it, use the preceding statement
to turn /LAZY:OFF.

There are other parameters you may wish to use, which determine the length of
time to wait before writing to the disk.  If you do not wish to set the
parameters, defaults will be supplied by the system.  For more information on
lazy writes, refer to the online Command Reference.

Note:  Because data is not immediately written to disk, you run a small risk of
losing updated information if the power drops before the file is written back
to disk.  For this reason, always run SHUTDOWN before powering off your system.

7) Another change that can produce a performance boost in memory-constrained
systems, is enabling OS/2 to swap the DOS box to disk when not active (ie, when
in the background). Normally, under OS/2 1.2, the 500-520K of RAM that is
available to DOS programs is not available for OS/2 application use.  But by
adding a parameter to the MEMMAN= statement in CONFIG.SYS this memory can be
freed up for OS/2 use.  Simply change MEMMAN=SWAP,MOVE to
MEMMAN=SWAP,MOVE,SWAPDOS.  In an environment where 512K-or-so of RAM will
reduce or eliminate swapping, overall system performance will improve.  SWAPDOS
will have no ill effect on the DOS box.  Should you wish to disable SWAPDOS,
simply change it to NOSWAPDOS.

In OS/2 1.3 SWAPDOS is the default.  It may be similarly disabled.

In summary, there is no one ideal system for everyone, however most users would
benefit from an all-HPFS system, with a 1.5MB cache and 50 buffers, with lazy
writes and SWAPDOS enabled.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.2. HPFS Advantages ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1990)

As you may recall from my last column, on OS/2 Performance Tuning, using the
High Performance File System (HPFS) can greatly improve the speed of fixed disk
file accesses.  But HPFS offers many other benefits as well.  These are
described below.  And, since the previous column didn't reveal why HPFS speeds
up disk performance, this is also discussed.

FAT Limitations
First, a little history is in order.  The File Allocation Table (FAT) file
system was originally developed in 1977 to support diskette-only systems.  FAT
was an elegant solution to the problem of managing data on such a small storage
medium but soon proved to be a limiting factor when fixed disk drives arrived
and offered much larger storage capacities.  DOS V2.0 included an enhanced FAT
that supported subdirectories, allowing data to be compartmentalized for better
organization of a large number of files.   But large numbers of files in any
given directory slow the access of data in that directory.  Fragmentation of
files on a nearly full disk drive is also a major detriment to performance,
because files broken into pieces (to fill the empty niches between other files)
take longer to access than whole files.  Other limitations, such as that of the
length of file names, also exist under FAT.

With OS/2 came the opportunity to begin with a clean slate, designing a new
file system that would minimize, if not eliminate, the restrictions and
performance penalties of the DOS FAT file system.  To this end many
improvements were designed into the new High Performance File System (HPFS).

Performance
To begin with, a balanced binary tree (a  B+ Tree, to be specific) replaced the
File Allocation Table; and run-length encoding (RLE) was used.  Besides being a
more efficient way of specifying a file's location and size, B+ Trees can find
files very quickly.  Then the RLE allows files to be extended easily, nearly
eliminating the fragmentation of files. These two enhancements alone account
for much of the performance improvement of HPFS over FAT; but it doesn't end
there.  HPFS also provides disk caching that optionally caches disk writes, as
well as reads.  By storing data temporarily (Lazy Writes) in this cache,
multiple programs are not forced to wait to access the relatively slow disk.
(Remember, OS/2 as a multitasking operating system is likely to have several
programs trying to read and write concurrently).  Additionally, the use of B+
Trees means that performance doesn't suffer when a directory has hundreds or
thousands of files in it, as it does with FAT.  Then there is the issue of data
integrity.

Data Integrity
There is always the possibility of data loss or corruption due to failing
sectors when using magnetic media.  HPFS offers two distinct mechanisms for
recovery from these problems:  Hot Fix and Autocheck.  With Lazy (delayed)
Writes to disk there is the possibility that a write error can occur in a
sector to which data is being written.  Because this could result in lost data,
HPFS provides spare sectors in case of a write error.  Rather than simply
terminating the write operation with an error, HPFS flags the bad sectors, and
uses some of those reserved sectors.  Then, the next time CHKDSK runs, it
copies the data to good sectors, deallocates the bad ones, and frees up the
spares.  This is called a Hot Fix.

Hot Fixes
Autocheck is as much a preventive measure as a recovery mechanism.  By putting
the /AUTOCHECK:x parameter (where x is one or more drive letters) at the end of
the IFS=C:\HPFS.IFS statement you are telling HPFS to automatically run CHKDSK
on the drive letters you specified, each time the system boots.  Though this
may not sound like a big deal, what it does for you is fix corrupted files
before the rest of CONFIG.SYS executes.  This means that should a necessary
driver, such as COUNTRY.SYS be corrupted, it will be fixed before OS/2 tries to
use it.  The alternative, under FAT, is to wait for the error message to flash
onscreen (identifying the file it can't open), then reboot from the
installation diskette, then run CHKDSK from the diskette containing it, and
then reboot from the hard drive.  All this can take 10-20 minutes to do.  Using
Autocheck, all you would notice is a message telling you that COUNTRY.SYS is
being rebuilt, followed by a count of the percentage of the disk already
verified by CHKDSK.  All this only adds about a minute or two to the length of
that particular boot, and requires no intervention by the user.  Autocheck also
recovers files left open when the system is powered off without first running
Shutdown.

Etcetera....
Other useful HPFS features include:

o Long file names:  With HPFS you are no longer restricted to the infamous "
  8.3" of FAT drives.  File names can be up to 255 characters long, including
  multiple periods and blanks.  For example,

         This is my.master.DATABASE file

   is a valid HPFS filename.  Notice the use of mixed case.  HPFS preserves
   this where FAT doesn't.

o Multiple large partitions:  HPFS supports up to sixteen 2GB partitions per
  drive.
o Extended Attributes:  HPFS stores more than just the familiar attribute bits.
  Such information as Last Access Date Last Modification Date, and others are
  associated with the data file.  Up to 64K of EAs can be kept per file.

There simply wasn't enough room in this column to go into all the intricacies
of HPFS.  For more information, you may read the article, "Design Goals and
Implementation of the New High Performance File System" by Ray Duncan, in IBM
Personal Systems Technical Solutions magazine, Issue 2, 1990, publication
number G325-5006.

To return to the OS/2 Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.3. OS/2 1.3 Enhancements ΓöÇ Tip ΓòÉΓòÉΓòÉ

Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1991)

OS/2 Version 1.3 brings with it many major and minor improvements over previous
versions.  Because they are not necessarily obvious from the announcement
letters, here are some details about these enhancements.

MAJOR ENHANCEMENTS

Smaller
When installing the entire operating system, there will be a savings of about
512K of memory, and 1MB or more (depending on whether it is SE or EE) of disk
space.  By selectively not installing portions of OS/2 that you may not want,
such as serviceability and diagnostic aids, online documentation, picture
utilities, and others, additional memory and disk space may be saved.  Improved
swapping techniques can also reduce disk requirements.  As a result, a savings
of one megabyte of RAM and several megabytes of disk space over OS/2 1.2 may be
realized.

Partial Installation/Reinstallation

Once OS/2 is initially installed, completely or partially, the user may at a
later time either install additional components not installed the first time,
or uninstall portions of the operating system.  This is a big improvement over
having to reinstall completely each time.

Faster
Users of systems with plenty of memory will see a performance improvement of
about 5-10%; those with memory-constrained systems (i.e., swapping occurs
frequently) will see a gain of roughly 10-25%.

REXX Language
REXX is the procedural language for OS/2.  It is based on and compatible with
the mainframe REXX language.  Previously REXX was only available for OS/2 EE,
but is now included free with both SE and EE.  REXX allows the user to turn
simple batch files i nto sophisticated programs.  Because REXX is interpretive,
no compiler is needed.

Improved Print Manager
Perhaps the biggest single improvement in 1.3 is in the number of software
fixes.  The Print Manager/Spooler was completely rewritten since 1.20, and many
of the device drivers were improved, with better performance and more features.
Overall, OS/2 1.3 is much more reliable than 1.2 was.

ATM Fonts
The use of Adobe Type Manager software as an integral part of OS/2 adds support
for Adobe Type 1 fonts.  This means not only that the user can purchase
additional fonts for OS/2 to suit their needs, but also that Printing to
PostScript printers is much faster, and now truly WYSIWYG.  OS/2 uses the same
ATM fonts for both printing and displaying text.  Because these ATM fonts are
used for non-PS printing as well, output to even dot-matrix printers is
improved when using software that allows font selection. (See the related
article, Adobe Type Font Installation for OS/2 1.30, By Dave Both.)

Faster Application Loading From LAN Server 1.3
When EE 1.3 and LAN Server 1.3 are used together, remote workstations are able
to load files across the network much faster than previously.

Modem Pooling
EE 1.3 adds the ability to redirect ACDI calls across a LAN to the LAN
Asynchronous Connection Server V2.0, which provides line and modem pooling
services for async connections.

XGA Drivers
OS/2 1.3 supplies updated drivers for the new XGA adapter.  Those supplied with
the adapter, or included with the PS/2 Models 90/95, are for OS/2 1.2 only, and
should not be used with OS/2 1.3.  Users with only 512K of video memory have
the option of 1024x768 resolution with 16 colors (the default) or 640x480x256
colors (using the XGASETUP program).  Users with 1MB of video memory
automatically see 1024x768x256 resolution.

MINOR ENHANCEMENTS

SWAPDOS
In OS/2 1.2, the default was not to swap the DOS box out to disk when
suspended.  In 1.3, the default is to swap the DOS box. This frees up
approximately 512K of RAM for OS/2 application use when the DOS box is in the
background.

Lazy Writes
In OS/2 1.2, High Performance File System (HPFS) users had to manually specify
Lazy Writes to see the benefits of two-way (read/write) caching.  This is now
the default.  FAT users still have read-caching only.

Anti-Aliased Fonts
The XGA driver supports anti-aliased text in 256-color modes (see above) for
better readability of screen text.  Anti-aliased fonts reduce the effects of
the "jaggies" by in effect gray-shading portions of the characters.

Swapping Improvements
The swapping algorithm was improved to reduce the frequency of swapping.  And
after a file swaps to disk, its space is reused by later swaps.  In the past,
every swap increased the size of the SWAPPER.DAT file.  Space no longer needed
was not reused.  This improvement can have a significant impact on those with
limited disk space.

Additional VIO Fonts
The VIO (or text) window, such as that used for an OS/2 command prompt window,
now offers more font sizes to choose from than just Large and Small; six sizes
for VGA users, twelve for 8514/A users, and fifteen for XGA users.

Additional 3270 Emulation Session Fonts
Users of the 3270 emulation module of the EE 1.3 Communications Manager, will
be pleased to see more choices.

VIO Window Paste
The VIO window now allows text to be pasted from the clipboard.  But to enable
this feature, the user must (one time only): 1) Mark some text (it doesn't
matter what) from the VIO window System Icon menu, and 2) Hold down the Shift
key while clicking on the Copy option of the VIO window pulldown.  Then close
that window.  The next time a VIO window is opened, the pulldown will include a
Paste option.

Cleaner Root Directory
The root directory of OS/2 1.2 was cluttered with dozens of *.BIO files.  These
are BIOS patches specifically designed for particular models of Micro Channel
PS/2.  Even though only one of these files applies to each system, they were
all installed any way.  OS/2 1.3 only installs the one file specific to the
system it is installed on.  This not only cleans up the root directory, but
also reduces the disk requirement of OS/2 1.3.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.4. Improving Sluggish PS/2 Mouse Performance ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

Some users of the IBM PS/2 Mouse complain that it feels "sluggish" in
comparison to other mice they have used with DOS or OS/2.  The reason for this
is not due to the mouse design, but the device driver used.

The PS/2 Mouse is programmable up to 200 Dots Per Inch (DPI) resolution,
however the PS/2 Mouse driver included with OS/2 is set for only 100 DPI.  This
means that the mouse has to be moved twice as far to get the same screen
movement as a 200 DPI mouse.

The solution is simple.  Since the PS/2 Mouse is hardware compatible with the
Microsoft PS/2 Mouse, the Microsoft driver (which is set for 200 DPI) can be
used instead of the IBM driver.  If OS/2 is already installed, and configured
for the IBM mouse, simply use the System Editor to change the following
statements in the CONFIG.SYS file from:

DEVICE=C:\OS2\IBMMOU02.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$

to:

DEVICE=C:\OS2\MSPS202.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSPS2$

Then save CONFIG.SYS.  For OS/2 1.2 users, that's all there is to it.

1.3 users have two more steps to go because 1.3 is "cleaner" than 1.2, and thus
doesn't install any drivers that are not necessary (saving disk space and
clutter).  First find the diskette containing the file MSPS202.SY@ and copy it
to the C:\OS2 directory.  Then, from the OS2 directory, use the following
command: UNPACK MSPS202.SY@.

Now reboot your system.  When it comes up it with be with a more sensitive PS/2
mouse.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.5. OS/2 Printer Driver Installation and Configuration ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Dave Both
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1991)

Printer driver installation is much easier in OS/2 1.3 than it has been in
previous versions of OS/2.  This article is intended to help you understand the
printer device driver installation process for both OS/2 1.2 and 1.3, as well
as to test your installation, and help you trouble-shoot problems which may
occur.

Five Actions
There are potentially five actions you must take to set up a Presentation
Manager (PM) printer driver in OS/2.

 1. Install the printer device driver for your supported printer or plotter.
 2. These steps are for OS/2 1.2 only.

    a. Create a queue.
    b. Create a printer.
    c. Associate the device driver with a printer.
    d. Associate the queue with a printer.

 3. Set up the communication port (only for serial printers or plotters).
 4. Use the SPOOL command to redirect printer output
 5. Specify optional Printer Properties or Plotter Properties.

Device Drivers
Device drivers are supplied with OS/2 and are used to tailor the printer data
stream to the installed printers.  OS/2 supplies a number of printer drivers.

o IBMNULL driver
o IBM Proprinter drivers
o IBM 4019 LaserPrinter driver
o IBM Quietwriter drivers
o Epson printer drivers
o PostScript Printer drivers
o HP LaserJet Printer driver

If an application program is not a Presentation Manager program, the device
drivers have little effect on printing.  They do send printer reset commands at
the beginning of each print data stream, but that is all. OS/2 full screen
applications, i.e.  n on-Presentation Manager applications, and DOS
applications which are run in the DOS compatibility box all provide complete
support internally for the printers they will use.  For this reason, the
printer data stream produced by these applications does not require the
intervention of a printer device driver.  For these applications you should use
the IBMNULL device driver.

Install Printer Driver, OS/2 1.2 and 1.3
You can install the printer drivers, that is, make OS/2 aware that the printer
drivers exist, by using this procedure in either OS/2 1.2 or 1.3.  For the
greatest speed when installing the printer device drivers, I suggest copying
the files from the driver diskettes to a temporary directory on your fixed
disk. Then, when the pop-up window appears which shows A:\ as the default
location for the installation procedure to look for the drivers, you can change
that to C:\TEMP.

 1. Select "Utilities" from the Desktop Manager window; then select "Control
    Panel."
 2. Select "Installation" from the Control Panel.
 3. Click on "Add".
 4. Type the location to search for the drivers, if it is different from the
    default, A:\.
 5. Select the device driver(s) you wish to install; multiple driver selection
    is allowed.
 6. Click on "Add".

Install Printer Driver, OS/2 1.3
In OS/2 1.3, this procedure can be used to install the printer device driver,
as well as to create the queue, create the printer and link them.  These steps
all had to be performed separately under OS/2 1.2.

 1. Select the Print Manager.
 2. Pull down the Setup menu.
 3. Select Printer Install.  At this point the install program will search for
    device drivers which have already been installed on your system, including
    those which are not currently being used.  If you choose, you may click on
    the NEW button.  This will allow you to install additional printer drivers
    from the OS/2 printer driver diskettes.
 4. All of the printers for which drivers are available are displayed in a
    scrollable window.  Select one desired printer by clicking once on it.
 5. Select a port with which to associate the printer driver. This can be COM1
    through COM3 and LPT1 through LPT3.
 6. Change the name or description fields, if desired.
 7. Press OK.  The printer install program will create a queue and a printer
    entry, associate the printer driver with the printer, and associate the
    queue with the printer.
 8. Repeat 1 through 7 to add more printers.  The printer installation program
    asks you if you have additional printers to install.

Communications Port Setup and Configuration

When setting up the communications ports in OS/2, you must take care to set
them up using both the OS/2 Control Panel and the MODE command.  You must also
redirect the output from an unused parallel printer port (LPTx) to the desired
COM port using the SPOOL command.

When printing in OS/2, the Control Panel settings affect the print jobs
originated by Presentation Manager applications, but they do not affect DOS box
applications, full screen mode applications, or some command line printing
methods.  The MODE command ensures that serial port parameters are set properly
for these applications.  The SPOOL command ensures that the printer data stream
is properly directed to the COM port from these same applications.

Set Up COM Port Through Control Panel
First ensure that you have a DEVICE=C:\OS2\COM0x.SYS statement in your
CONFIG.SYS file, where x is either 1 or 2. Use 2 for system units that
incorporate Micro Channel architecture, for example, PS/2 Model 50 and above,
and 1 for AT bus systems.

 1. Select "Utilities" from the Desktop Manager window; then select "Control
    Panel."
 2. Select "Options" from the Control Panel; then select "Communications Port."

The asynchronous communications port settings which you define in the Control
Panel must be the same as those specified on your modem, printer or plotter.

o Specify "Hardware" in the Handshake field for DTR Pacing protocol.
o Specify "None" in the Handshake field for XON/XOFF protocol.

Set COM Port Parameters With MODE Command
Issue a MODE command similar to the following one for the communications port
on which the printer or plotter is installed. This sets the communications
parameters for the desired COM port when printing is done from a DOS
application, a full screen OS/2 application, or the OS/2 command line.

MODE COMx:baud,N,8,1,TO=ON,XON=OFF

where "x" is the desired COM port, and "baud" is the desired baud rate.  A
typical baud rate is 9600 or 19200.  This command should be added to the
STARTUP.CMD file.  You can check the current settings of a COM port by issuing
the command

MODE COMx:

with no parameters.

Use SPOOL Command to Redirect Printer Output
The SPOOL command sets up printer redirection when printing is done from a DOS
application, a full screen OS/2 application, or from the OS/2 command line.
Printing done from a Presentation Manager application is done directly to the
COM port and does not require redirection.  Add the following command to your
STARTUP.CMD file:

SPOOL /D:LPTx /O:COMx

where LPTx is the parallel port you are redirecting, and COMx is the
communications port to which the printer data stream is being redirected.

Printer Properties
The various options you can choose to control the activity of your printer are
listed under Printer Properties.  To specify these properties for printers:

 1. Select "Print Manager."
 2. Select "Setup" from the Print Manager window; then select "Printers."
 3. Select the PRINTER1, and then the "Change" pushbutton in the Printers
    window.
 4. Select the printer driver you require.
 5. Select the "Printer Properties" pushbutton to display the properties window
    for your printer.

Note:  The properties which are displayed depend on the printer driver you
select.

Testing the printer
At this point, you have completed installation of the device driver and are
ready to test the printer.  The best way to do this is to start the File
Manager and select a file in the root directory, like CONFIG.SYS, and drag it
to the Print Manager icon and drop it there.  If you have installed multiple
printers, you will be asked to select which printer you wish to print on.  If
you select a PostScript printer, you will be asked whether to print the file as
text or graphics; choose text.  The printer should now print the file.

After this basic test, you can try printing from an OS/2 Presentation Manager
application program.  Almost all PM applications are sensitive to OS/2 versions
and CSD levels to varying degrees.  You should ensure that the PM application
you are using is supported by the level of OS/2 and the CSD level you have
installed on your system. If you can print using the "drag and drop" test
above, however, you can be sure that the printer driver installation and setup
has been done correctly and any problems you have printing from the application
are not with OS/2.

Troubleshooting
There are any number of problems which can cause difficulties with printing
under OS/2.  I will outline the ones on which we receive the most calls here at
the NSC, and how to fix them.

Prints Fine with DOS
The most common problem you might encounter can be characterized by a wide
range of symptoms.  You might see one of the following PMV error messages; PMV
messages are from Presentation Manager.

PMV8005 Make sure that the printer is switched on

PMV8006 There is no paper in the printer

PMV8007 The printer is switched off

PMV8008 The printer is not online

Other typical symptoms might be that print jobs appear in the Print Manager
queue and appear to be printing properly.  You will see the word "Printing"
next to the job on its status line in the Print Manager.  You would also find
that the printer will function fine under DOS (not the DOS compatibility box).

These symptoms are almost always indicative of a problem with your printer
cable.  A cable which has not been fastened properly at both ends may work its
way loose so that some of the conductors in the cable do not make proper
contact with the socket into which it is plugged on the printer or the system
unit.

OS/2, unlike DOS, requires all 25 of the conductors in a standard IBM printer
cable.  DOS, being a single tasking operating system, can afford the CPU cycles
required to poll the printer to see whether it is busy or not.  OS/2, because
it is a multitas king operating system cannot afford to waste system resources
like time and CPU cycles.  OS/2 is dependent upon receiving an interrupt signal
back from the printer when it is ready to accept more data from the data
stream.  Losing proper contact prevents some of the required signals of printer
from reaching the system, and OS/2.  OS/2 may interpret this in any number of
different ways, depending upon which signals are missing. DOS may not know the
difference.  For the same reason, non-IBM printer cables may cause the problem.
All IBM parallel printer cables have all 25 conductors, and there has only been
one part number for the IBM printer cable, 1525612.  Many non-IBM cables are
less expensive than the IBM cable, because they do not have all 25 conductors.
You get what you pay for.  IBM serial printer cables are also different from
some non-IBM serial cables in this respect.  To fix this problem, ensure that
the system has a real IBM parallel or serial printer cable, and that it is not
only plugged in, but also fastened in place properly at both ends.

Print jobs Hang in Print Manager
Print jobs appear in the Print Manager but never print.  They can be cancelled,
however.  This symptom can be caused by damage to the Print Manager information
which is stored in the OS2SYS.INI file.  The simplest way to correct this
problem is to delete the OS2SYS.INI file and create a new one.  This procedure
is outlined on Page 10-7 of the OS/2 EE 1.2, or 1.3 User's Guide, Volume 1,
Base Operating System manual, under Recovering User and System INI Files.  This
information can also be found on Page 94 of the OS/2 SE Version 1.2 Advanced
Features manual,  and Page 93 of the same manual for OS/2 SE Version 1.3.  For
this problem recover only the OS2SYS.INI file.  Do not recover the OS2.INI
file.

Garbage Printed on Serial Printer
When printing on a serial printer, the output is garbage.  This can show up as
many things, like inverted question marks (╨╕) or random characters.  This
problem can occur when the serial port is not set to the same communication
parameters as the printer.

You should be sure to set the communications port parameters identically to
those set on the printer.  You must do this with the MODE command as well as
with the Control Panel according to the procedures outlined earlier in this
article.

Latest CSD Imperative
It is imperative that users with OS/2 1.2 have installed the latest CSD
(Corrective Service Diskette), or that they upgrade to OS/2 1.3 where possible.
There were, to be sure, many problems with printing in early levels of OS/2
1.2.  These problems have mostly been corrected with the CSDs.  The current (as
of this writing) CSD levels for OS/2 SE 1.2 is XR04095, and for OS/2 EE 1.2 it
is WR04098.  Printing under OS/2 continues to be an area of great confusion. I
hope this article has improved your understanding of printer driver
installation and configuration for OS/2.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.6. Backing up OS/2 .INI Files ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1991)

Any effective backup regimen must, by definition, include periodic
complete-system backups.  Yet as anyone who has tried to backup OS/2 knows, the
OS2.INI and OS2SYS.INI files remain open at all times, making their successful
backup problematic. But never fear, there are several different solutions,
regardless of whether your backup method is via diskette, IBM Internal Tape
Backup Unit, IBM 6157 Streaming Tape drive, or IBM 2.3GB Tape drive.

The simplest solution, for 6157 or 2.3GB tape drive users, is to use the SYTOS
Plus/IBM Tape Utilities for OS/2 V1.0 (P/N 15F7193).  This new incarnation of
the venerable SYTOS tape software now supports backup of the two .INI files on
the fly.  SYTOS Plus also supports diskette users, but it is debatable whether
users who have not invested in a tape drive would spend more than $100 for
backup software.

Internal tape drive users, and those diskette users not willing to purchase
SYTOS Plus are not left out in the cold, however.  One solution is to boot from
the installation diskette, escape from the logo screen to a command prompt, and
copy C:\OS2\*.INI to a blank diskette, then reboot from the hard drive to bring
OS/2 back up.  Although simple, this approach is awkward, involving two reboots
within minutes of one another; and there is no way to automate this.  Manual
insertion and removal of the Installation diskette and a blank diskette are
required.

Fortunately, a more elegant and ultimately simpler method is possible.  Just
add the following statement to your CONFIG.SYS file:

RUN=C:\OS2\CMD.EXE /S XCOPY.EXE C:\OS2\OS2*.INI C:\OS2\*.BNI.

What this does (because CONFIG.SYS executes before the Presentation Manager
loads) is make backup copies of the .INI files using a .BNI (Backup INI)
extension, each time the system boots up, BEFORE the .INI files are locked!

Since the OS2SYS.INI file only changes when the user alters the printer setup
information in the Print Manager, and OS2.INI only changes when the user
modifies Groups, Control Panel settings, or makes other global changes it
really isn't necessary to backup these files more than every so often.  Also,
since the .INI files can become corrupted, and it is counter-productive to
backup the corrupted files, it is a good idea to REM out the RUN= statement
above after a successful backup.  This way the  good backup will not be written
over by a bad one after the next reboot.  Then for the next backup, just remove
the REM.

Not only is there no more rebooting than normal with this approach, but the
backup is automated as well.  The operator only has to occasionally add or
remove a REM in the CONFIG.SYS file.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.7. Adobe Type 1 Font Installation in OS/2 1.3 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Dave Both
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1991)

OS/2 1.30 supports Adobe Type Fonts for display and printing. This article
describes the installation and setup of these fonts. OS/2 1.30 as it comes out
of the box is provided with the basic 17 Adobe fonts, and Adobe Type Manger.
The Adobe Type Manager included with OS/2 1.30 provides the ability to install
and manipulate Adobe Type 1 fonts within the OS/2 Presentation Manager. The
fonts supplied with OS/2 1.20 are versions of the following:

o Courier
o Helvetica
o Times Roman

Because these fonts are included with OS/2, you do not need to purchase the
basic Adobe Type Manager package if you desire additional fonts.  You only need
to purchase the Adobe Type Library or the Adobe Plus Pack or any package of
Type 1 fonts. The Adobe Plus Pack provides the additional 22 fonts which are
versions of the following:

o ITC Avant Garde Gothic
o ITC Bookman
o Helvetica Narrow
o New Century Schoolbook
o Palatino
o ITC Zapf Chancery (Medium Italic)
o ITC Zapf Dingbats

(There are also some public domain Type 1 fonts available for free on some
BBSes around the country, including the IBM National Support Center BBS.  See
the IBM Non-Voice Phone Numbers section of the General Info Assistant, or the
PS2ASST.TXT file, for additional information about the NSC BBS.)

Installation
Under no conditions should you use the installation program which is supplied
with the font package!  I tried it, and it does not work.  The installation
should be accomplished with the following steps:

 1. Copy the .AFM, and .PFB files into the C:\OS2\DLL directory on your fixed
    disk.
 2. Start the Control Panel.
 3. Pull down the INSTALL choice from the Action Bar.
 4. Choose ADD FONT.
 5. Type C:\OS2\DLL for the directory and click on ADD.
 6. Select the fonts you wish to add.  They will all appear with the extension
    .AFM.  Click on ADD.

This is all you need to do to install the fonts.  They are now available for
use in any Presentation Manager application which allows font selection.  This
includes the File Manager and the System Editor.

Printing and Performance Considerations
Because of the direct support for PostScript fonts in OS/2 1.30, printing
performance is greatly enhanced when a PostScript printer is used.  The ideal
situation is to have the same PostScript fonts available in your printer as you
have in OS/2.  You should ensure that you have installed the PostScript printer
driver for your printer, or the generic PostScript driver if your printer is
not specifically supported.  IBM printers which support PostScript printing are
the IBM 4019 LaserPrinter and 4019E LaserPrinter E, as well as the IBM 4216
models 030 and 031.

If you do not have a PostScript printer, many other printers supported by OS/2
will work, too.  Among these are several IBM Proprinter models, and the IBM
4019 LaserPrinter and 4019 E LaserPrinter E when used in Personal Printer Data
Stream (PPDS) mode or HP emulation mode.  Also supported are most Hewlett
Packard Laserjet printers and virtually all Epson printers. The 17 basic
PostScript Type 1 fonts provided with IBM OS/2 1.30 correspond to the 17
PostScript fonts imbedded in the IBM 4019 and 4019 E PostScript option.  The
additional 22 fonts I installed from the Adobe Plus Pack correspond to the
PostScript fonts included in the PostScript font card for the IBM 4019 and 4019
E. These 39 fonts are also among the forty plus PostScript fonts found in the
IBM 4216 printers.

Using Printer Fonts
Best printing performance is obtained when you select fonts for your document
which are contained in your printer either as native fonts, or as cartridge or
downloadable fonts.  Using these fonts, OS/2 is able to send a much more
compact data stream to the printer because it only has to specify the font to
be used and then send the characters.  If, on the other hand, the fonts are not
resident in the printer, the OS/2 printer device driver must create an image of
the data to be printed and then send the image to the printer.  This takes more
time, i.e.  CPU power, to rasterize the image, and creates a much larger data
stream which must then be sent to the printer.

Limitations
Be aware of the fact that you cannot print to a PostScript printer from the
OS/2 command line using the COPY, PRINT, or TYPE commands.  If you need to
print an ASCII file to a PostScript printer, you may use the File Manager to
select the desired file, and drag it to the Print Manager icon and drop it
there.  The PostScript device driver will pop a window on the screen which asks
whether you wish to print the file as graphics or text.  You should always
choose text for ASCII files.  This method of printing is also highly
recommended for testing printer installation and setup.  If this works, your
printer and the printer drivers are correctly installed and configured.  Full
screen, non-PM programs generally do not support PostScript printing. This is
due to the fact that these programs do not support printing through the PM
printer device drivers.  The exception would be a program like IBM DisplayWrite
5/2 Composer which provides all support for printers from within the
application.  For these applications, you should use the IBMNULL device driver
instead of a PostScript device driver.

Many Fonts Available
Inclusion of the Adobe Type Manager in OS/2 1.30 by IBM ensures a large number
of available fonts for screen display and printing. Many Type 1 fonts are
currently available on the market and all should work perfectly when correctly
installed and used.  You should refer to the OS/2 documentation for additional
information about using Type 1 fonts.  In OS/2 1.30 Standard Edition
documentation, this information is in a little booklet called Using Type 1
Fonts.  For OS/2 1.30 Extended Edition, the information is in Chapter 2 of the
User's Guide, Volume 1: Base Operating System, beginning on Page 2-49.

Personal Observations
Mark Chapman and I have been using OS/2 1.30 with both the IBM-supplied fonts
and the Adobe Plus Pack fonts for some time now, and we are very happy with the
results.  I use a 4019 E with the 39 Font PostScript Option, both at home and
at work, for most of my printing tasks.  I use a PS/2 Model 70-121 (20MHz) at
home and a PS/2 Model 90 XP 0J5 (25MHz) at work. Print times are quite good in
both environments.  At home, I usually only have two or three programs running
under OS/2 SE 1.30, and plenty of RAM available.  At work, my Model 90 is
almost always loaded to the maximum under OS/2 EE 1.30.  I usually have two
3270 DFT sessions via coax and one 5250 Workstation session via Token Ring, two
or three in-house applications we run from the Token Ring network, and anywhere
from two to six other applications in addition to PageMaker.  I often use an
IBM internal personal information manager for OS/2, DeScribe, Lotus 1-2-3/G,
PageMaker, and Corel Draw for OS/2 all at the same time.  In this environment,
even with 16MB of RAM, my Model 90 is using at least some virtual memory.
Thus, the results I get include a modest amount of disk swapping activity.
Printing a ten page presentation using DeScribe 2.00 takes just about two
minutes from start to finish on either system.  This is just the rated speed of
the 4019 E. It took only a couple seconds for DeScribe to process the print
command and complete printing on both systems.

Using Aldus PageMaker on the PS/2 Model 90 to print the proofs for the 4th
Quarter, 1990, issue of the IBM Advisor took a total of 27 minutes and 45
seconds.  It took PageMaker 1 minute and 35 seconds to process the 24 page
document for a five color se paration printing, producing a total of 120 pages
of printed output.  This is a rate faster than 1 page per second.  The first
page began to print after 3 minutes and 9 seconds.  After this, printing seemed
to be limited only by the speed of the LaserPrinter E, as it printed pages
almost continuously.  The 24 minute and 13 second time it took the LaserPrinter
E to print all 120 pages after it started receiving the printer data stream is
only 13 seconds longer than its rated five pages per minute. While these
results are by no means scientific benchmarks, they do provide some indication
of the performance capabilities which can be achieved in a real world
environment using the PostScript support provided by OS/2 1.30 and a PostScript
printer with native and cartridge fonts.  The results seem consistent in both
light and heavy usage environments.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.8. Free OS/2 1.3 Utilities ΓöÇ Tip ΓòÉΓòÉΓòÉ

Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1991)

When DOS users upgrade to OS/2, they frequently feel the lack of certain
familiar and indispensable DOS utilities that they were forced to leave behind
in the conversion to OS/2.  At the NSC we are frequently asked about the
availability of OS/2 disk utilities to do the following tasks:  defragment
partitions, find files wherever they may be, move files from one directory to
another, sort directories in almost any order, undelete files, hide/unhide
files, and more.  Most people are surprised to learn that nearly all of these
capabilities already exist in OS/2 1.3; either inherently in the High
Performance File System (HPFS), or as a selectable option in the File Manager.
In my last column (The IBM Advisor, Vol.  1, No. 2), I discussed how the design
of HPFS virtually eliminates file fragmenting, and does so "on the fly,"
without requiring any separate steps, or special software.

OS/2 File Manager
If you haven't taken a close look at the OS/2 File Manager, now might be a good
time.  When you pull down the Action Bar Files option, you will notice a Search
option.  Selecting this gives you the ability to find any file, or group of
files by such at tributes as name, file creation date, size, flags (attribute
bytes), and even user-added comments.  Comments and other information can be
appended to a file by the Properties option, and stored in a file's Extended
Attributes (now you know what those are used for!).  Files will be found in any
directory on the target drive, and displayed in a window showing the full
pathnames of the files.

Copy/Move/Delete
Files may be moved from one directory or drive to another in one step (without
having to first copy, then delete) by using either the Move menu option, the F7
key, or by simply dragging and dropping the file icon.  The default for
drag/drop between directories on the same drive is a Move to save disk space.
The default between different  drives is a Copy for greater security.  Either
default may be overridden by holding down the Ctrl key while performing the
drag/drop.  Another handy feature is selectable copy/move/delete.  It can be
frustrating to have to work with, say, 15 files out of a directory of 50, when
they do not all have a common prefix or extension.  It usually involves typing
commands in several different steps to copy or delete them.  But the File
Manager allows you to use the mouse or keyboard to mark just the files you
want, without having to type anything, and then by simply pressing the delete
key or dragging the group to another directory, perfor ming in one step what
took many keystrokes to do before.

Directory Sort Order Selectable
File Manager automatically displays files in a directory in alphabetical order
by file name.  User selectable alternatives also include sorting by size, three
different dates (creation, last modification, last access), and file extension.
Other options include displaying full file details, just the file names, and
just the icons and file names; plus whether to include Read-only, Hidden, and
Archive files in the displays.  File Manager also includes a Change flags
options which allows the user to change the Read-only, Archive, Hidden, and
System attributes for a file, or all marked files, all by mouse clicks. No
typing is needed.

Associate Files With Applications
Associate allows the user to select a program (say the System Editor) and
designate all files that may be used to "launch" that application.  This means
that if you associate all *.DOC, *.TXT, *.ASC, and other ASCII text files with
E.EXE, you can load both the program and the file in one step by just
double-clicking on the file name from a File Manager directory listing.  If you
double-click on two file names, two System Editor sessions will be started,
making it easier to cut and paste between them. The alternative would be to
start two sessions from the menu, then go into each session, select the File
option, then manually type in the names of each file.  By the same token,
spreadsheet, database, or other programs can be associated with all their
related data files and started by double-clicking on the data file names.

And, of course, File Manager allows the user to work with multiple directory
windows simultaneously.  The only commonly asked for disk utility that OS/2
doesn't include is Undelete (this feature will be included in OS/2 2.0).  But
if the disk is formatted as FAT, some of the DOS undelete utilities may work in
the DOS box.  For HPFS users, well, a good backup is always your best defense
against data loss from an unintentional delete.  As described in my last
column,  HPFS does provide far greater data integrity features than does the
FAT system, so it is unlikely you will experience lost data from a power
failure.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.9. Introducing IBM TCP/IP for OS/2 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By John Lewman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1990)

TCP/IP Version 1.0 for OS/2 became available March 30, 1990. The types of
questions that we are getting in the National Support Center are; what is it,
what does it do, what adapters does it support, and who supplies the device
drivers for the non- IBM adapters. Version 1.1 of TCP/IP has been announced for
September 28th, 1990 availability. Version 1.1 incorporates the Network File
System (NFS) client and has support for Serial Line Internet Protocol (SLIP).
First, what is it?  TCP and IP are protocols that define a set of rules and
standards developed to address hardware and software interoperability.  These
protocols govern communication between and within networks, regardless of the
technologies implemented within each of the networks. TCP/IP is a peer to peer
architecture.  All systems, regardless of size, appear the same to all other
systems on the network. Systems using the TCP/IP functions are logically paired
in a client-server relationship.  In general, TCP/IP requests are issued from
the client, or local host, and forwarded through an internet to the server, or
foreign host.  The server performs the function and returns the results to the
client.  For example, if you need to transfer a file from a remote TCP/IP host
to the local host, invoke the client function of the file transfer at your
local host.  The request is routed through an internet to the foriegn host,
where the server function reads the file from disk and sends it back through an
internet to the local host. The client function on the local host then makes
the file available to you.

Now for what it does.  TCP/IP for OS/2 allows an OS/2 EE V1.2 system attached
to an IBM Token Ring, IEEE 802.3 Lan or Ethernet V2 Lan to interoperate with
other systems in a TCP/IP network.  In addition to IBM's Token Ring Adapters,
TCP/IP for OS/2 supports the following communication adapters:

o 3COM Etherlink II Adapter
o 3COM Etherlink/MC (Model 3C513)
o Western Digital Ethercard PLUS Adapter
o Western Digital Ethercard PLUS/A Adapter
o Ungerman-Bass NIU PC Adapter (Model PC2030)
o Ungerman-Bass NIU PS/2 Adapter (Model PC3030)

The device drivers for the above adapters are provided by OS/2 EE V1.20. Any
personal computer that the Operating System/2 Extended Edition Version 1.2
supports, will also be supported by the TCP/IP version 1.0 and version 1.1 for
OS/2 product. Refer to NDD Announcement letter 89-247 dated May 16, 1989 for
specific model types supported by OS/2 EE 1.2.

For additional information please see announcement letter NDD 90-015, dated
January 23, 1990, NDD 90-188,dated May 15, 1990, and Introducing IBM's
Transmission Protocol/Internet Protocol Products for OS/2, VM, and MVS,
GC31-6080.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.10. Increasing Environment Space in OS/2 & DOS Modes ΓöÇ Tip ΓòÉΓòÉΓòÉ

The OS/2 environment space is dynamically allocated for each process. There is
no limit to the environment size, other than the practical limit of the total
virtual memory space available in the system.  The virtual memory space is the
total of real memory plus the disk space available for segment swapping.

The DOS compatibility box of OS/2, as it is loaded by the default SHELL command
in the CONFIG.SYS file, imposes an upper limit of 127 bytes on the environment
space.  There is the /E:xxx parameter to the SHELL command which provides for
the ability to specify a larger environment.  For example:

    SHELL=COMMAND.COM /E:256 /P

would start the DOS command processor with 256 bytes of environment space.
Note that the /E parameter is NOT documented in the OS/2 User's Guide,
Reference Manual, or Technical Reference Manual.

Note:  The /P parameter causes the AUTOEXEC.BAT file to be executed; it will
not execute if the /P parameter is omitted.

Also, the COMMAND command can be used to start a second command processor in
the DOS compatibility box, and the /E parameter can be used to specify a larger
environment size.  For example:

    COMMAND /E:256

when issued in the DOS compatibility box would start a second command processor
with 256 bytes of total environment space.  This is, of course, at the expense
of reduced memory available to run application programs.  The maximum
environment space which can be specified is 320KB.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.11. Maximum Fixed Disk Partition Sizes Supported by OS/2 ΓöÇ Tip ΓòÉΓòÉΓòÉ

The maximum fixed disk partition size was 32MB for OS/2 V1.0. OS/2 1.0
supported, in addition to the primary partition, one or more extended
partitions.  An extended partition may be as large as the rest of the physical
fixed disk.  The OS/2 1.0 extended partition could be divided into multiple
logical drives of not larger than 32MB apiece.  Each logical drive was
automatically assigned a drive letter as it is created.

OS/2 1.1 through 1.3 WILL support a greater-than-32MB disk as a single logical
drive.  The full size of the fixed disk drive may be used as a single logical
drive, if desired.  (OS/2 1.1 only supported disk sizes up to 512MB; but 1.2
and 1.3 support drives up to 2GB in size.)

In support of very large fixed disks for OS/2 using the FAT system, the 16-bit
file allocation table is still used, but there is an increase in allocation
unit size of sectors per cluster.  Under OS/2 using the High Performance File
System (HPFS), large drives are supported in a different manner; one which does
not require an increase in cluster size. The HPFS maximum disk size is 2GB.

OS/2 allows up to 65,536 FAT entries or clusters.  Cluster sizes can range up
to 64 sectors which gives a 32KB cluster size.  The following table gives the
relative size correlations.

           Fixed Disk File Allocation Table Data
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDrive size  ΓöéSectors/Γöé Cluster Γöé FAT   Γöé MAX FAT Γöé MAX FATΓöé
Γöé  in MB     ΓöéCluster Γöé  Size   Γöé Size  Γöé Entries Γöé  Size  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé   0 -   16 Γöé    8   Γöé   4KB   Γöé 12-bitΓöé    4096 Γöé    6KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé  17 -   32 Γöé    4   Γöé   2KB   Γöé 16-bitΓöé   16384 Γöé   32KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé  33 -   64 Γöé    4   Γöé   2KB   Γöé 16-bitΓöé   32768 Γöé   64KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé  65 -  128 Γöé    4   Γöé   2KB   Γöé 16-bitΓöé   65536 Γöé  128KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 129 -  256 Γöé    8   Γöé   4KB   Γöé 16-bitΓöé   65536 Γöé  128KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 257 -  512 Γöé   16   Γöé   8KB   Γöé 16-bitΓöé   65536 Γöé  128KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 513 - 1024 Γöé   32   Γöé  16KB   Γöé 16-bitΓöé   65536 Γöé  128KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé1025 - 2048 Γöé   64   Γöé  32KB   Γöé 16-bitΓöé   65536 Γöé  128KB Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.12. Installation of OS/2 1.2/1.3 on Multiple Systems ΓöÇ Tip ΓòÉΓòÉΓòÉ

Many customers or dealers have a need to install OS/2 on many PS/2 systems in
as short a time as possible.  This is especially true in a large network
environment.

IBM has published a red "Cookbook" to assist customers with this need.  This
book is called OS/2 in Interconnected Environments; Guidelines for Installation
and Maintenance.  This book covers installation and maintenance of OS/2 on
large numbers of systems using networks, host systems, tape, and diskette.

Customers and dealers can order this book through their IBM Marketing Rep or
Systems Engineer as publication number GG24-3502.  The REXX files required to
perform the installation may be downloaded by the MR or SE from OS2TOOLS on VM.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.13. Installing XGA drivers for OS/2 1.20 ΓöÇ Tip ΓòÉΓòÉΓòÉ

If OS/2 is installed with a VGA driver, start at Step 5.

If OS/2 is installed with any other driver, or you are not sure which driver is
installed, or OS/2 is not installed, start at step 1.

 1. If you have an 8514/A adapter installed in your system unit, ensure that no
    display is connected to it.
 2. Follow the installation instructions supplied with OS/2.
 3. When you are asked "Do you have a Device Support diskette to install?"
    reply "No" and press the Enter key.
 4. Follow the instructions displayed to complete the installation of OS/2 with
    the VGA driver.
 5. When the "Group-Main" panel is displayed, select "OS/2 Full Screen" from
    it.
 6. Insert the XGA Device Drivers Diskette #2 in drive A.

    a. If you have only one display attached to your system unit, type:
       A:INSTALL    (and press the Enter key)

    b. If you have more than one display attached to your system unit, type:
       A:INSTALL 2   (and press the Enter key)

 7. When you are told to "Insert a Device Support diskette in drive A:", press
    the Enter key.
 8. The "Select a Device Driver" panel appears.  Select "OS/2 1.2 Device Driver
    for IBM XGA".
 9. Follow the instructions displayed to complete the installation of the
    driver.
10. When you are told to insert the OS/2 Installation Diskette in drive A:, do
    so, and DO NOT remove it until you are asked to.
11. If you have an 8514/A adapter installed in your system unit, and you want
    to connect a display to it, do so now.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.14. Installing XGA drivers for OS/2 1.30 ΓöÇ Tip ΓòÉΓòÉΓòÉ

OS/2 1.3 contains device drivers for the XGA video controller.  When OS/2 1.3
is installed, it will sense the presence of the XGA, just as it does VGA or
8514/A, and it will install the correct device drivers to support XGA.  Do not
install the drivers from the diskette accompanying the adapter (or the PS/2
Models P75/90/95).  The diskette contains OS/2 1.2 drivers and will not work
correctly under 1.3.

If problems are still present after the install procedure, confirm that the
following statements are listed in the CONFIG.SYS.

    DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
    SET VIDEO_DEVICES=VIO_IBMXWY
    SET VIO_IBMXWY=DEVICE(BVHVGA,BVHXGA)
    DEVICE=C:\OS2\XGARING0.SYS

For more details, please refer to Updating Support for Your Display Adapter on
page 2-9 of the EE 1.3 User's Guide Volume 1: Base Operating System manual; or
page 24 of the SE 1.3 Using Advanced Features manual.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.15. XGA Configuration for OS/2 ΓöÇ Tip ΓòÉΓòÉΓòÉ

When you have completed the installation of the device driver, there may be
configuration options for you to select, depending on the amount of video
memory your system has, as follows:

o If your system has 1MB of video memory (8 Video RAM modules installed), no
  options are needed.  Your system will run at high resolution (displaying
  1024x768 pixels - or dots- on the screen) and can also display up to 256
  different colors.
o If your system has 0.5MB of video memory (only 4 Video RAM modules
  installed), you can choose to operate at either:

   - high resolution (1024x768 pixels) with the ability to display up to 16
     colors simultaneously, but without the ability to use antialiased text, OR
   - medium resolution (640x480 pixels) with the ability to display up to 256
     colors simultaneously, and the ability to use antialiased text.

If your system has 0.5MB of video memory, the first time you start OS/2, high
resolution (1024x768 pixels) with 16 colors is selected. You can change to
medium resolution (640x480 pixels) with 256 colors by running the XGASETUP
program, as follows:

In the OS/2 Desktop Manager, select Screen Setup.  In the Screen Setup group,
run Screen Configuration, which lets you change screen resolution options.

If you do not know how much video memory you have, you can run the XGASETUP
program as described above to see if there are any options available to you.

Option choice depends on the type of application programs you use. High
resolution lets you get more information on the screen, but colors are limited
to 16.  Choose this configuration if your applications do not use more than 16
colors.  If more than 16 displayed colors is important, for example to better
match color images, or you want to use antialiased text, select medium
resolution with 256 colors.  Note that the XGASETUP program can be run at any
time, so you can change the mode setting as you prefer.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.16. OS/2 1.x Memory Map ΓöÇ Tip ΓòÉΓòÉΓòÉ

OS/2 loads part of its kernel into the lower 640KB of RAM, as well as device
drivers.  At least a portion of each device driver must be resident in low
memory.  OS/2 also loads part of its kernel in extended memory, beginning at
the 1MB boundary.

The memory remaining between the top of the low kernel and the 640KB boundary
can be used for DOS real mode programs.  This is also known as the DOS
compatibility box.  If DOS real mode programs are not required, this portion of
memory can also be used for OS/2 protect mode programs.  All extended memory
remaining above the high kernel can be used for OS/2 Protect Mode programs.

         OS/2 MEMORY USAGE
Address (Hex)                       Total User Memory
FFFFFFΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ16MB \
      Γöé OS/2 Protect Mode Programs Γöé      \
      Γöé                            Γöé       \
      Γöé       ^ ^ ^ ^ ^ ^ ^ ^      Γöé        \
      Γöé       Extended Memory      Γöé         \   15MB
      Γö£----------------------------ΓöñVaries   / Available
      Γöé                            Γöé        /
      Γöé        High Kernel         Γöé       /
100000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ 1MB  /
      Γöé          ROM BIOS          Γöé  ^
 F0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ  Γöé
      Γöé          Reserved          Γöé  Γöé
 E0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ  Γöé
      Γöé          Reserved          Γöé  ^
 D0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñNot available
      Γöé     ROM BIOS Expansion     Γöéto User
 C0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ  v
      Γöé        Video Memory        Γöé  Γöé
 B0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ  Γöé
      Γöé    Extended Video Memory   Γöé  v
 A0000Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ640KB  \
      Γöé        DOS Programs        Γöé        \
      Γöé                            Γöé         \ 450-520KB
      Γöé     ^ ^ ^ ^ ^ ^ ^ ^ ^      Γöé         / Available
      Γöé     DOS Real Mode Box      Γöé        /
      Γö£----------------------------ΓöñVaries /
      Γöé    OS/2 Device Drivers     Γöé
      Γö£----------------------------Γöñ115KB +/-
      Γöé      OS/2 Low Kernel       Γöé
 00000ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ  0KB

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.17. Stacking Multiple Commands on Command Line ΓöÇ Tip ΓòÉΓòÉΓòÉ

OS/2 allows the user to "stack" multiple commands on a single command line.
One way is by using the & symbol.  For example: DIR C:\OS2 & DIR A:\MISC will
result in 2 consecutive directory listings without operator intervention.

Another way to do the same thing is:

    DIR C:\OS2 A:\MISC

In addition, if you use && instead of &, the second command is executed only if
the first is successful.  For example:

    DIR C:LETTER.TXT && TYPE C:LETTER.TXT

would only TYPE the file if it is found in the directory.

Conversely, if you use || (two vertical bars; ie. two shift-backslash keys),
the second command would only execute if the first is unsuccessful.  For
example:

    DIR C:\SUBDIR. || MD C:\SUBDIR

would only create a new subdirectory if one by that name does not exist.

It is also possible to combine these "connectors".  For example:

    DIR C:\SUBDIR. || MD C:\SUBDIR &&. COPY FILE.TXT C:\SUBDIR

would only create the directory if it did not already exist, and would then
copy FILE.TXT to that subdirectory only if the subdirectory creation was
successful.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.18. Adding DOS Programs to Program Selector ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

OS/2 1.2 added the ability for DOS programs to be added to Program Groups and
started just like OS/2 programs.  Earlier versions of OS/2 did not support this
feature.

Just add the programs to the desired group; OS/2 determines that the program is
a DOS mode program and places the DOS program icon next to it in the group.
You may click twice on the DOS program's icon to start it, just as you would
start an OS/2 program.

Bear in mind that although multiple OS/2 sessions (and therefore multiple OS/2
programs) can be active at all times, only one DOS session, running one DOS
program, can be active at a time.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.19. Changing the Default VIO Window Size ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

To permanently change the default width of the VIO window (such as that used
for an OS/2 command prompt), simply hold down the Shift key while you release
the mouse button after dragging the sides or corners to change the dimensions
of the window.  This new size will be the default (until changed by this method
once again).

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.20. Changing the Default Font Size of VIO Windows ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

OS/2 1.2 provides only two choices of font size in the VIO window (such as that
used for an OS/2 Command Prompt); Large and Small.  The default is Large, and
this may be overridden temporarily from the System Menu icon (the one in the
upper left corner of the window). However, to permanently change the default to
Small (or to later change back to Large, simply hold down the Shift key while
selecting the font size you wish.  This size will become the new default.

OS/2 1.3 users have many more choices of font size than before, and whichever
is selected will become the new default when the Save button is depressed
before leaving the font selection panel.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.21. Setting Up 109-line Command Prompt Windows ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

Although the default VIO window size is 25 lines, it is possible to set the
buffer as large as 109 lines, using the MODE command, depending on the video
adapter used.  If you have an XGA Adapter, simply create a batch file called
109.CMD, containing the following statement: MODE CO80,109.  A VGA or 8514/A
user can specify up to 102 lines in similar fashion.

Executing this batch file from a windowed command prompt will allow you to
stretch the window past its usual 25-line limit.  The number of lines you will
actually be able to see on-screen will depend on the size of the font you have
selected in the VIO window, and the resolution of the display driver you are
using. A VGA system, with the font set to its smallest, can display
approximately 56 lines of text in the window.  An 8514/A user can see about 88
lines.  Use the scroll bar to see the remainder of the buffer.

To automate this procedure, the following statement may be added to
STARTUP.CMD: Start "OS/2 Command Prompt" C:\109.CMD  (You may supply any title
you wish between the quotes.  Also, be sure to use the full path for the batch
file if it is not in the root directory.)  This will open a window upon bootup.
The window will initially be sized for 25-lines, but may be manually stretched
to the desired length.

OS/2 1.3 users may prefer to add this capability to the "OS/2 Window" option on
the Main Group, to optionally start additional command prompt windows at a
later time, with 109-line buffers.  To do this, just change the Parameters
field (under Program...Properties) to read: /K "%*" d:\pathname\109.CMD  (In
other words, just add the batch file name, and the path where it can be found,
after what is already there.)

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.22. Patching Prodigy 3.1 to Run in the OS/2 DOS Box ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

There are some interrupt vectors that OS/2 will not allow to be changed by a
DOS program.  When PRODIGY V3.1 begins to load in the OS/2 1.2/1.3 DOS box, it
attempts to change them, and OS/2 stops Prodigy from doing so, issuing "A DOS
program attempted to change an interrupt vector" message.  The user has the
choice of canceling Prodigy, or of ignoring the error and continuing.  If the
user chooses to continue, the error recurs.  The error must be ignored FOUR
different times to get past it.  Although  the interrupt vectors are NOT
changed, Prodigy will run.

The following patch, which stops PRODIGY from trying to change the vectors, was
developed by an end-user.

Note:  Although this fix uses the OS/2 PATCH command, don't be afraid to try
it, even if you have never used it before.  The steps are self-explanatory, and
you should have little difficulty with them.

Warning: Be sure to make a backup copy of PRODIGY.EXE before proceeding, in
case you make a mistake.  This will give you the ability to try again with a
"good" copy, if needed.

FOLLOW THESE STEPS IN AN OS/2 WINDOW:

 1. Type:  CD d:\PRODIGY  (where d: is the drive where Prodigy is installed)
 2. Type:  COPY PRODIGY.EXE PRODIGY.DOS  (This will make a backup copy, called
    PRODIGY.DOS.)
 3. Type:  PATCH PRODIGY.EXE
 4. Type:  AE20  (The OS/2 PATCH program will display a line of data.  The
    first byte of that data should be 10.  If it is not.  Quit here (Q [Enter],
    and try again).  ELSE:
 5. Type:  0D    and press enter.
 6. Type:  AE28  and press enter.  (The first byte displayed must be 77)
 7. Type:  6f    and press enter.
 8. Type:  AE53  and press enter.  (The first byte displayed must be 10)
 9. Type:  0D    and press enter.
10. Type:  AE5B  and press enter.  (The first byte displayed must be 77)
11. Type:  6f    and press enter.
12. Now quit.  (Q [Enter])

Now try the new PRODIGY.EXE.  If it runs with no interrupt vector errors (or
others), you have patched the file correctly.  If errors occur, repeat these
steps again, being careful to follow them exactly.

(PRODIGY.DOS is your unchanged version, in case you need it (simply rename it
PRODIGY.EXE).)

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.23. Minimizing OS/2 1.2 Disk Storage Requirements ΓöÇ Tip ΓòÉΓòÉΓòÉ

           TITLE: IWSY FLASH 9036--DISK STORAGE REQUIREMENTS FOR OS/2

INTRODUCTION

There has been considerable discussion about the amount of DASD required to run
OS/2 V1.2.  IBM has investigated what a 'bare bones' OS/2 system might consist
of and what steps would be required to achieve such a configuration.

Note:  Most of these filenames are the same in OS/2 1.3, and may be deleted for
the same reasons.

The purpose of this FLASH is to help OS/2 users free up as much space as
possible on their C: drive to make room for application space.

Part 1 describes the files that are included as part of OS/2 SE 1.2.  Part 2
goes on to examine the OS/2 EE system.

These file sizes were recorded on a PS/2 system.  Where sizes are missing, it
is because these files are only installed on AT type systems or the
installation program did not install them due to configuration options selected
when the system was installed.  Note also that the file sizes may change due to
maintenance level, but that will not significantly affect the totals.

Totals are included where appropriate to make it easier to see the effect of
deleting an entire component from the system.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

                           OS/2 SE System Requirements
                           OS/2 EE System Requirements

Or, return to the OS/2 1.x Tips header.


ΓòÉΓòÉΓòÉ <hidden> Part 1ΓöÇOS/2 SE System Requirements ΓòÉΓòÉΓòÉ

To jump directly to the OS/2 EE System Requirements section of this document,
press the Enter key.  Or, return to the OS/2 1.x Tips header.

        OS/2 SE System Requirements
FILENAME  EXT  DIRECTORY     SIZE   (TOTAL)

These required files may not be deleted:
ANSI    EXE  \OS2
ANSICALL  DLL  \OS2\DLL
BKSCALLS  DLL  \OS2\DLL
BMSCALLS  DLL  \OS2\DLL
BVHINIT   DLL  \OS2\DLL
BVHWNDW   DLL  \OS2\DLL
BVSCALLS  DLL  \OS2\DLL
CHKDSK   COM  \OS2
CMD     EXE  \OS2
COMP    COM  \OS2
COUNTRY   SYS  \OS2\SYSTEM
DDINSTAL  EXE  \OS2\INSTALL
DISKCOMP  COM  \OS2
DISKCOPY  COM  \OS2
DOSCALL1  DLL  \OS2\DLL
DOSCALLS  LIB  \OS2
E      EXE  \OS2
EAUTIL   EXE  \OS2
EHXDDLG S  DLL  \OS2\DLL
EHXDL    DLL  \OS2\DLL
EHXHP    HLP  \OS2\HELP
EXTDSKDD  SYS  \OS2
FIND    EXE  \OS2
FKA     DLL  \OS2\DLL
FORMAT   COM  \OS2
HARDERR   EXE  \OS2\SYSTEM
HELP    BAT  \OS2
HELP    CMD  \OS2
HELPMGR   DLL  \OS2\DLL
HELPMSG   EXE  \OS2
HMHELP   HLP  \OS2\HELP
INI     RC   \OS2
INISYS   RC   \OS2
KBDCALLS  DLL  \OS2\DLL
MAKEINI   EXE  \OS2
MODE    COM  \OS2
MONCALLS  DLL  \OS2\DLL
MORE    COM  \OS2
MOUCALLS  DLL  \OS2\DLL
MSG     DLL  \OS2\DLL
NAMPIPES  DLL  \OS2\DLL
NLS     DLL  \OS2\DLL
OS2SM    DLL  \OS2\DLL
OS2SMDUM  DLL  \OS2\DLL
OSO001   MSG  \OS2\SYSTEM
OSO001H   MSG  \OS2\SYSTEM
PMAVIO   DLL  \OS2\DLL
PMBIND   DLL  \OS2\DLL
PMCPL    EXE  \OS2
PMCPLH   HLP  \OS2\HELP
PMDD    SYS  \OS2
PMEXEC   EXE  \OS2
PMEXECH   HLP  \OS2\HELP
PMFILE   EXE  \OS2
PMFILEH   HLP  \OS2\HELP
PMGPI    DLL  \OS2\DLL
PMGRE    DLL  \OS2\DLL
PMHINIT   DLL  \OS2\DLL
PMMLE    DLL  \OS2\DLL
PMPIC    DLL  \OS2\DLL
PMSHAPI   DLL  \OS2\DLL
PMSHELL   EXE  \OS2
PMSHELLH  HLP  \OS2\HELP
PMSHLTKT  DLL  \OS2\DLL
PMTKT    DLL  \OS2\DLL
PMVIOP   DLL  \OS2\DLL
PMVIOP   HLP  \OS2\HELP
PMWIN    DLL  \OS2\DLL
PMWINDUM  DLL  \OS2\DLL
PRINT    COM  \OS2
PSHH    HLP  \OS2\HELP
QUECALLS  DLL  \OS2\DLL
REPLACE   EXE  \OS2
SESMGR   DLL  \OS2\DLL
SWAPPER   EXE  \OS2\SYSTEM
SYSLEVEL  EXE  \OS2
SYSLEVEL  OS2  \OS2\INSTALL
UNPACK   EXE  \OS2
VDISK    SYS  \OS2
VIOCALLS  DLL  \OS2\DLL
VIOTBL   DCP  \OS2
XCOPY    EXE  \OS2
BASEDD01  SYS  \      (PC AT only)
BASEDD02  SYS  \      (PS/2 only)
BASEDD03  SYS  \      (PS/2 Mod 30/286 only)

If the command reference is not needed, these files can be deleted:
CMDREF   INF  \OS2\BOOK     366050
VIEW    EXE  \OS2        26672
VIEWDOC   EXE  \OS2        25392
VIEWH    HLP  \OS2\HELP      15615  (433,729)

If DOS support is not needed, these files can be deleted:
ANSI    SYS  \OS2         1976
APPEND   EXE  \OS2         6946
ASSIGN   COM  \OS2         1517
BASIC    COM  \OS2         585
BASICA   COM  \OS2        36253
COMMAND   COM  \OS2        29009
DOS     SYS  \OS2         2100
EDLIN    COM  \OS2         7996
EGA     SYS  \OS2         2599
GRAFTABL  COM  \OS2         8401
JOIN    EXE  \OS2        24848
MORTGAGE  BAS  \OS2         6380
SETCOM40  EXE  \OS2         9387
SUBST    EXE  \OS2        24848  (162,845)

If Dual Boot is not needed, this file can be deleted:
BOOT    COM  \OS2        42384

If a font is not needed, it may be deleted:
COURIER   FON  \OS2\DLL      307760
HELV    FON  \OS2\DLL      545456
SYSMONO   FON  \OS2\DLL      39424
TIMES    FON  \OS2\DLL      603440  (1,496,080)

If HPFS is not used, these files may be deleted:
CACHE    EXE  \OS2        13984
HPFS    IFS  \OS2        100378
STARTLW   DLL  \OS2\DLL       1076
UHPFS    DLL  \OS2\DLL      157024 (272,462)

If the TOOLKIT or IBM programming languages will not be installed,
these files can be deleted:
CPISPFPC  DLL  \OS2\DLL      129588
DMPC    EXE  \OS2\INSTALL     2798
DTM     DLL  \OS2\DLL       1786
INACALL   DLL  \OS2\DLL       1560
INSTAID   CMD  \OS2\INSTALL     254
INSTAID   CNF  \OS2\INSTALL     225
INSTAID   LIB  \OS2\INSTALL    27648
INSTAID   PRO  \OS2\INSTALL     175
INSTAIDE  EXE  \OS2\INSTALL    93827
ISPD    MSG  \OS2\INSTALL     4551
ISPM    MSG  \OS2\INSTALL     1489
STXTDMPC  DLL  \OS2\DLL      14171  (278,072)

If Introducing OS/2 is not needed, these files can be deleted:
INTROE   EXE  \OS2\INTRO     16905
INTROI   TUT  \OS2\INTRO     56788
INTROS   TUT  \OS2\INTRO     39567  (113,260)

If Mouse support is not needed, these files can be deleted:
IBMMOU01  SYS  \OS2
IBMMOU02  SYS  \OS2         3124
MOUSE    SYS  \OS2        18484
MSBUS01   SYS  \OS2
MSINP01   SYS  \OS2
MSPS201   SYS  \OS2
MSPS202   SYS  \OS2         3636
MSSER01   SYS  \OS2
MSSER02   SYS  \OS2         3636
PCMOU01   SYS  \OS2         3124
PCMOU02   SYS  \OS2         3124
POINTDD   SYS  \OS2         6562
VISION01  SYS  \OS2         3124
VISION02  SYS  \OS2

If National Language support is not needed, these files can be deleted:
4201    DCP  \OS2        10683
5202    DCP  \OS2         404
KEYB    COM  \OS2        17769
KEYBOARD  DCP  \OS2        94007 (122,863)

If any of these utilities are not needed, they can be deleted:
ATTRIB   EXE  \OS2        37619
BACKUP   EXE  \OS2        29095
FDISKPM   EXE  \OS2        82640
FDISKPMH  HLP  \OS2\HELP      10508
LABEL    COM  \OS2        33383
LINK    EXE  \OS2        142578
RECOVER   COM  \OS2        53184
RESTORE   EXE  \OS2        39285
SORT    EXE  \OS2        34385
TREE    COM  \OS2        36461
PICH    HLP  \OS2\HELP      11973
PICICHG   EXE  \OS2        35280
PICPH    HLP  \OS2\HELP      33413
PICPRINT  EXE  \OS2        126512
PICSHOW   EXE  \OS2        48608

If OS/2 problem determination support is not needed, these files can be deleted:
CREATEDD  EXE  \OS2        50976
LOGDAEM   EXE  \OS2\SYSTEM     27867
OS2SM    PDF  \OS2         2676
PATCH    EXE  \OS2        43509
PMC00000  TFF  \OS2\DLL       4228
PMC10000  TFF  \OS2\DLL       7125
PMC20000  TFF  \OS2\DLL      26425
PMC30000  TFF  \OS2\DLL       1450
PMC40000  TFF  \OS2\DLL       365
PMC50000  TFF  \OS2\DLL      21507
PMC60000  TFF  \OS2\DLL       2872
PMC70000  TFF  \OS2\DLL       4698
PMC80000  TFF  \OS2\DLL       469
PMGPI    PDF  \OS2         7013
PMGRE    PDF  \OS2         363
PMPIC    PDF  \OS2         231
PMSHAPI   PDF  \OS2         1531
PMSPL    PDF  \OS2         1322
PMTRACE   DLL  \OS2\DLL       3444
PMWIN    PDF  \OS2         7740
PSTAT    EXE  \OS2        18047
SPL1B    PDF  \OS2         2112
SPL2B    PDF  \OS2         288
SYSLOG   EXE  \OS2        91776
TRACE    EXE  \OS2        27103
TRACEFMT  EXE  \OS2        73744
TRSEL    EXE  \OS2        19281

If the spooler will not be used, these files can be deleted:
IBM4201   DRV  \OS2\DLL      83056
OS2SPLFS  DLL  \OS2\DLL       3582
PMPRINT   QPR  \OS2\DLL      12784
PMSPL    DLL  \OS2\DLL      13086
PMSPOOL   EXE  \OS2        101648
PMSPOOLH  HLP  \OS2\HELP      31060
SPL1B    DLL  \OS2\DLL      69520
SPL2B    DLL  \OS2\DLL       3759
SPLDVWRK  EXE  \OS2         9408
SPLPRM   EXE  \OS2        16848
SPOOL    EXE  \OS2        21309
SPOOLCP   DLL  \OS2\DLL      10178  (376,238)

These files can summarily be deleted:
SYSINST   SCD  \OS2\INSTALL    5968
CONVERT   EXE  \OS2

These files are used for display support.  If they are not referenced in
CONFIG.SYS, they may be deleted:
BVH8514A  DLL  \OS2\DLL      8810
BVHCGA   DLL  \OS2\DLL
BVHEGA   DLL  \OS2\DLL
BVHMPA   DLL  \OS2\DLL
BVHVGA   DLL  \OS2\DLL      36970

After the correct file is copied to DISPLAY.DLL.  These files can be deleted:
IBMBGA   DLL  \OS2\DLL
IBMCGA   DLL  \OS2\DLL
IBMEGA   DLL  \OS2\DLL
IBMVGA   DLL  \OS2\DLL

These are the serial support files. If a file is not referenced in CONFIG.SYS,
it can be deleted:
COM01    SYS  \OS2
COM02    SYS  \OS2        16948

Any files not mentioned in this Flash can most likely be deleted without
adverse effect to OS/2.


ΓòÉΓòÉΓòÉ <hidden> Part 2ΓöÇOS/2 EE System Requirements ΓòÉΓòÉΓòÉ

To jump directly to the OS/2 SE System Requirements section of this document,
press the Enter key.  Or, return to the OS/2 1.x Tips header.

                           OS/2 EE System Requirements

INITIAL OS/2 EE INSTALLATION

A minimum configuration (answering 'NO' to install prompts) was installed with
the following:

  o NO serial device support

  o NO retrieve command support

  o NO command reference

  o NO device support diskette to install

  o Communications Manager with test config file

  o Database Manager, RDS and Query Manager included
    - Requester only, NO local databases to be used

  o LAN Requester

The amount of DASD left on the test system was 13,582,336 versus 12,357,632
for  a maximum configuration setup (answering 'YES' to install prompts).  This
constitutes a savings of 1,224,704 MB after INITIAL installation.

COMMUNICATIONS MANAGER FEATURES

Once Communications Manager has been installed and  customized,  the  keyboard
remap  and  configuration services files can be deleted by doing a 'REINST' of
Communications Manager and specifying that you want to remove the above.

Note:  Once configuration services is removed, modifications to the
Communications Manager configuration file is not allowed.  In addition,
verification of other configuration files will not be possible.  However,
configuration files that have already been verified can be copied over and
Communications Manager will execute normally.

This amounts to a savings of over 3.5 MB!!

REINSTALLATION FEATURES

There are a number of files that have to do with the installation and removal
of EE subsystems (eg. Communications Manager, Database Manager, LAN Requester)
that can be deleted.  It is important to understand that once these files are
removed, that a REINST can NEVER be done again.  Before doing this, make sure
that the system is configured correctly or devise a backup scheme for the
deleted files so that they can be restored again if ever desired.  The filenames are as follows:

Path: \OS2\INSTALL
CMDIR.DA*
CUSTBLD.PI*
CUSTINST.CM*
DBDIR.DA*
EEIN.MS*
EEINST.CN*
EEINST.LI*
EEINST.PI*
EEINST.PR*
EELOG.DA*
EICCNVSV.EX*
EICDELSV.EX*
EICERCON.PI*
EICERROR.PI*
EICLGMSG.PI*
EICSRVCS.EX*
EIDPNTXT.DA*
LPOINST.PI*
LRDIR.DA*
MUGDIR.DA*
R0CSDD.EX*
REINST.CM*
RFRSHICO.EX*
VIEWBLOG.CM*
VIEWBLOG.PI*
VIEWLOG.CM*
VIEWLOG.PI* 335,524 bytes

Path: \OS2\DLL
ACS3ECT.DL*
ACSGCBLD.DL*
ACSMSGFM.DL*
ACSSVC.DL*
ISPMALLC.DL*
PICTDMPC.DL*
RCDAPIEX.DL*
RCFGFILE.DL*
RCOMAIN.DL*
RCVMAIN.DL*
RNLCHARS.DL*
RPSMAIN.DL*
RSMMAIN.DL*

Path: \OS2\INSTALL
CMCUBLD.PI*
CMCUINST.PI*
CMINST.PI*
CMREMOVE.CM*
CMREMOVE.PI*
CMRMPREV.CM*
CMTITLE.TX*
DBCUBLD.PI*
DBCUINST.PI*
DBDSGC1.DA*
DBDSGC2.DA*
DBDSGC3.DA*
DBDSGC4.DA*
DBDSGWSN.PI*
DBDSINST.PI*
DBDSIPAN.PI*
DBINST.PI*
DBLOADFT.PI*
DBQMGC.DA*
DBQMINST.PI*
DBREMOVE.PI*
DBRMPREV.CM*
DBRMVDS.PI*
DBRMVQM.PI*
DBSETVAR.PI*
DBSPACE.PI*
DELTITLE.EX*
EIPCFGSY.PI*
EIPCHECK.PI*
EIPCMPIN.PI*
EIPERROR.PI*
EIPICECL.PI*
EIPINITL.PI*
EIPIPLUP.PI*
EIPSAVHV.PI*
EIPYES.TX*
IBMLAN.EX*
LRCHKSPC.PI*
LRCOPFIL.PI*
LRCUBLD.PI*
LRCUINST.PI*
LRDOINST.PI*
LRFIXINI.PI*
LRINST.PI*
LRMUGINS.PI*
LRREMOVE.PI*
LRRMPREV.CM*
LRSETVAR.PI*
LRSPECNM.PI*
LRUPDAIF.PI*
LRWKSSVC.PI*
MUGINST.EX*
MUGINST.PI*
REXXINST.PI*
SQLEMGDB.EX*
SQLENODE.EX* 249,185

Path: \OS2\INSTALL
ACSBIND.MS*
ACSE.MS*
APPCPC.DA*
CFG.DA*
CIKS.CN*
CIKS.LI*
CIKS.MS*
CIKS.PR*
CIKSTART.EX*
EECFG.CM*
ISPD.MS*
ISPM.MS*
PICT.MS*   421,976

Under the test configuration, all of these files were deleted except those in
the second group which were not present.  The DASD savings totaled 1,006,685
bytes.

MISCELLANEOUS FEATURES

Once OS/2 has been installed, there are a number of files that can be deleted;
these files may not be needed depending on the user-install base.

\OS2\INTRO  (OS/2 tutorial and introduction)  797,680
\OS2\BOOK  (used by command reference)  365,717
\OS2\DLL   (used by Database Services)  360,876

TOTAL DASD SAVINGS

Initial installation savings: 1,224,704
OS/2 intro: 797,680
Files listed above: 1,006,685
Communications Manager 'REINST': 3,500,000
TOTAL: * 6,529,069 *

CONCLUSION

After deleting all unnecessary files, OS/2 EE requires approximately 25 MB of
DASD.

Note:  This number does not reflect the SWAPPER.DAT file.


ΓòÉΓòÉΓòÉ 6.6.24. Printers/Plotters Supported by OS/2 1.3 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

There is a perception that OS/2 supports very few printers.  While this is true
to some extent, as far as brands are concerned, there are far more output
devices supported than many people realize.  In fact there are nearly 200
printers and plotters directly supported by V1.3, and many more through the
IBM, Epson, or HP emulation modes of many printers, as well as the generic
PostScript driver.  OS/2 V2.0 will add significantly to this list of supported
printers and plotters.

The following is a list of all printers and plotters supported, and which
drivers to install from the installation diskettes, for the respective devices.
(Once a "family" driver, such as EPSON, IBM42XX, IBM42XX, LASERJET, PLOTTER, or
PSCRIPT is installed, it reveals multiple individual printer drivers that can
be installed from the Print Manager.)

Note:  Printer names followed by an asterisk (*) indicate drivers added to OS/2
beginning with V1.30.2 (CSD 5050).  (Use the SYSLEVEL command to determine your
CSD level.)

Printers Supported                                             Driver
Agfa-ChromaScript v51.8                                        PSCRIPT.DRV
Agfa-Compugraphic 400P                                         PSCRIPT.DRV
Agfa-Compugraphic 400PS                                        PSCRIPT.DRV
Agfa-Compugraphic 9400P v49.3                                  PSCRIPT.DRV
Apple LaserWriter                                              PSCRIPT.DRV
Apple LaserWriter II NT                                        PSCRIPT.DRV
Apple LaserWriter II NTX                                       PSCRIPT.DRV
Apple LaserWriter Plus                                         PSCRIPT.DRV
Apple LaserWriter Plus v42.2                                   PSCRIPT.DRV
AST TurboLaser                                                 PSCRIPT.DRV
Colormate PS *                                                 PSCRIPT.DRV
Dataproducts LZR 1260 v47.0                                    PSCRIPT.DRV
Dataproducts LZR 2665                                          PSCRIPT.DRV
Digital LNO3R ScriptPrinter                                    PSCRIPT.DRV
Digital LPS PrintServer 40                                     PSCRIPT.DRV
Epson DFX-5000 *                                               EPSON.DRV
Epson DFX-8000                                                 EPSON.DRV
Epson EPL-6000 Laser *                                         EPSON.DRV
Epson EPL-7000 Laser *                                         LASERJET.DRV
Epson EPL-7500 Laser v52.3 *                                   PSCRIPT.DRV
Epson EX-800 Color                                             EPSON.DRV
Epson EX-1000 Color                                            EPSON.DRV
Epson FX-1050                                                  EPSON.DRV
Epson FX-286e                                                  EPSON.DRV
Epson FX-850                                                   EPSON.DRV
Epson JX-80 Color                                              EPSON.DRV
Epson LP-570 *                                                 EPSON.DRV
Epson LP-870 *                                                 EPSON.DRV
Epson LP-1170 *                                                EPSON.DRV
Epson LQ-500                                                   EPSON.DRV
Epson LQ-510                                                   EPSON.DRV
Epson LQ-850                                                   EPSON.DRV
Epson LQ-860 Color *                                           EPSON.DRV
Epson LQ-950                                                   EPSON.DRV
Epson LQ-1010 *                                                EPSON.DRV
Epson LQ-1050                                                  EPSON.DRV
Epson LQ-2500 Color                                            EPSON.DRV
Epson LQ-2550 Color                                            EPSON.DRV
Epson LX-800                                                   EPSON.DRV
Epson LX-810                                                   EPSON.DRV
Epson Generic 9-Pin                                            EPSON.DRV
Epson Generic 24-Pin                                           EPSON.DRV
Generic PostScript (for all PS printers not listed)            PSCRIPT.DRV
HP DeskJet 500 * (Emulating an Epson EPL-6000)                 EPSON.DRV
HP LaserJet Classic                                            LASERJET.DRV
HP LaserJet Plus *                                             LASERJET.DRV
HP LaserJet 500                                                LASERJET.DRV
HP LaserJet 2000                                               LASERJET.DRV
HP LaserJet II                                                 LASERJET.DRV
HP LaserJet IID                                                LASERJET.DRV
HP LaserJet IID v52.2 *                                        PSCRIPT.DRV
HP LaserJet IIP                                                LASERJET.DRV
HP LaserJet IIP v52.2 *                                        PSCRIPT.DRV
HP LaserJet III v52.2 *                                        PSCRIPT.DRV
HP LaserJet IIID v52.2 *                                       PSCRIPT.DRV
HP LaserJet IIIP v52.2 *                                       PSCRIPT.DRV
HP LaserJet IIISi v52.2 *                                      PSCRIPT.DRV
HP LaserJet Plus                                               LASERJET.DRV
HP 7440A Plotter (ColorPro)                                    PLOTTER.DRV
HP 7470A Plotter                                               PLOTTER.DRV
HP 7475A Plotter                                               PLOTTER.DRV
HP 7550A Plotter                                               PLOTTER.DRV
HP 7570A Plotter (DraftPro)                                    PLOTTER.DRV
HP 7580A Plotter                                               PLOTTER.DRV
HP 7580B Plotter                                               PLOTTER.DRV
HP 7585A Plotter                                               PLOTTER.DRV
HP 7585B Plotter                                               PLOTTER.DRV
HP 7586B Plotter                                               PLOTTER.DRV
HP 7595A Plotter (DraftMaster I)                               PLOTTER.DRV
HP 7596A Plotter (DraftMaster II)                              PLOTTER.DRV
IBM 2380 PPS II *                                              IBM42XX.DRV
IBM 2381 PPS II *                                              IBM42XX.DRV
IBM 2390 PPS II *                                              IBM42XX.DRV
IBM 2391 PPS II *                                              IBM42XX.DRV
IBM 3812 Pageprinter Model 2 (Emulating an IBM
 5152 Graphics Printer)                                        IBM5152.DRV
IBM 3816 Pageprinter (Emulating an IBM Quietwriter III)        IBM5202.DRV
IBM 3852 Color Jetprinter                                      IBM3852.DRV
IBM 4019 LaserPrinter/LaserPrinter E                           IBM4019.DRV
IBM 4019 LaserPrinter/LaserPrinter E                           LASERJET.DRV
IBM 4019 LaserPrinter/LaserPrinter E with 17-Font
 PS Option                                                     PSCRIPT.DRV
IBM 4019 LaserPrinter/LaserPrinter E with 39-Font
 PS Option                                                     PSCRIPT.DRV
IBM 4029 LaserPrinter 5E *                                     IBM4019.DRV
IBM 4029 LaserPrinter 5E *                                     LASERJET.DRV
IBM 4029 LaserPrinter 6 *                                      IBM4019.DRV
IBM 4029 LaserPrinter 6 *                                      LASERJET.DRV
IBM 4029 LaserPrinter 10 *                                     IBM4019.DRV
IBM 4029 LaserPrinter 10 *                                     LASERJET.DRV
IBM 4029 LaserPrinter 10L *                                    IBM4019.DRV
IBM 4029 LaserPrinter 10L *                                    LASERJET.DRV
IBM 4029 LaserPrinter with 17-Font PS Option
 (300 dpi) *                                                   PSCRIPT.DRV
IBM 4029 LaserPrinter with 17-Font PS Option
 (300 dpi) *                                                   PSCRIPT.DRV
IBM 4029 LaserPrinter with 39-Font PS Option
 (600 dpi) *                                                   PSCRIPT.DRV
IBM 4029 LaserPrinter with 39-Font PS Option
 (600 dpi) *                                                   PSCRIPT.DRV
IBM 4072 ExecJet (Emulating an EPSON LQ-1050)                  EPSON.DRV
IBM 4072 ExecJet (Emulating an IBM Proprinter XL24E)           IBM42XX.DRV
IBM 4072 ExecJet (Emulating an IBM Quietwriter III)            IBM5202.DRV
IBM 4201 Proprinter I                                          IBM42XX.DRV
IBM 4201 Proprinter II                                         IBM42XX.DRV
IBM 4201 Proprinter III                                        IBM42XX.DRV
IBM 4202 Proprinter XL                                         IBM42XX.DRV
IBM 4202 Proprinter II XL                                      IBM42XX.DRV
IBM 4202 Proprinter III XL                                     IBM42XX.DRV
IBM 4207 Proprinter X24                                        IBM42XX.DRV
IBM 4207 Proprinter X24E                                       IBM42XX.DRV
IBM 4208 Proprinter XL24                                       IBM42XX.DRV
IBM 4208 Proprinter XL24E                                      IBM42XX.DRV
IBM 4216 Personal Page Printer                                 PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 030                    PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 031 v51.4              PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 031 v51.4
  (with automatic sheetfeed option)                            PSCRIPT.DRV
IBM 4224 Models 01/02/E3                                       IBM42XX.DRV
IBM 4224 Model C2                                              IBM42XX.DRV
IBM 4226 Model 302 *                                           IBM42XX.DRV
IBM 5152 Graphics Printer                                      IBM5152.DRV
IBM 5182 Color Printer                                         IBM5182.DRV
IBM 5201 Quietwriter I                                         IBM52011.DRV
IBM 5201 Quietwriter II                                        IBM52012.DRV
IBM 5202 Quietwriter III                                       IBM5202.DRV
IBM 5204 Quickwriter (Emulating an IBM Quietwriter III)        IBM5202.DRV
IBM 5216 Wheelprinter (not Wheelprinter E)                     IBM5216.DRV
IBM 6180 Plotter                                               PLOTTER.DRV
IBM 6182 Plotter                                               PLOTTER.DRV
IBM 6184 Plotter                                               PLOTTER.DRV
IBM 6186 Plotter Model 1                                       PLOTTER.DRV
IBM 6186 Plotter Model 2                                       PLOTTER.DRV
IBM 7371 Plotter                                               PLOTTER.DRV
IBM 7372 Plotter                                               PLOTTER.DRV
IBM 7374 Plotter                                               PLOTTER.DRV
IBM 7375 Plotter Model 1                                       PLOTTER.DRV
IBM 7375 Plotter Model 2                                       PLOTTER.DRV
IBM Null Printer                                               IBMNULL.DRV
Kyocera F-800A/F-800 *                                         LASERJET.DRV
Kyocera F-820A *                                               LASERJET.DRV
Kyocera F-1000A/F-1000 *                                       LASERJET.DRV
Kyocera F-2000A/F-2000 *                                       LASERJET.DRV
Kyocera F-3000A/F-3000 *                                       LASERJET.DRV
Kyocera F-5000A/F-5000 *                                       LASERJET.DRV
Kyocera P-2000 *                                               PSCRIPT.DRV
Kyocera Q-8010 *                                               PSCRIPT.DRV
Linotronic 100 v38.0                                           PSCRIPT.DRV
Linotronic 100 v42.5                                           PSCRIPT.DRV
Linotronic 200 v47.1                                           PSCRIPT.DRV
Linotronic 200 v49.3                                           PSCRIPT.DRV
Linotronic 300 v47.0                                           PSCRIPT.DRV
Linotronic 300 v47.1                                           PSCRIPT.DRV
Linotronic 300 v49.3                                           PSCRIPT.DRV
Linotronic 500 v49.3                                           PSCRIPT.DRV
NEC LC-890                                                     PSCRIPT.DRV
NEC Silentwriter LC 890XL v50.5 *                              PSCRIPT.DRV
NEC Silentwriter2 Model 90 v52.0 *                             PSCRIPT.DRV
NEC Silentwriter2 Model 290 v52.2 *                            PSCRIPT.DRV
Olivetti LP-5000                                               PSCRIPT.DRV
Panasonic KX-P1123 * (Emulating an Epson LQ-850)               EPSON.DRV
Panasonic KX-P1124 * (Emulating an Epson LQ-2500)              EPSON.DRV
Panasonic KX-P1124i * (Emulating an Epson LQ-850)              EPSON.DRV
Panasonic KX-P1180 * (Emulating an Epson FX-86e)               EPSON.DRV
Panasonic KX-P1191 * (Emulating an Epson FX-86e)               EPSON.DRV
Panasonic KX-P1624 * (Emulating an Epson LQ-2500)              EPSON.DRV
Panasonic KX-P1654 * (Emulating an Epson LQ-1050)              EPSON.DRV
Panasonic KX-P1695 * (Emulating an Epson FX-1050)              EPSON.DRV
Panasonic KX-P2624 * (Emulating an Epson LQ-1050)              EPSON.DRV
Panasonic KX-P4420 *                                           LASERJET.DRV
Panasonic KX-P4450 *                                           LASERJET.DRV
Panasonic KX-P4450i *                                          LASERJET.DRV
Phaser Card *                                                  PSCRIPT.DRV
Phaser-CP *                                                    PSCRIPT.DRV
QMS ColorScript 100                                            PSCRIPT.DRV
QMS ColorScript 100 Model 10 *                                 PSCRIPT.DRV
QMS ColorScript 100 Model 30 *                                 PSCRIPT.DRV
QMS ColorScript 100 Model 30si *                               PSCRIPT.DRV
QMS ImageServer X320 *                                         PSCRIPT.DRV
QMS PS-410 *                                                   PSCRIPT.DRV
QMS PS-800                                                     PSCRIPT.DRV
QMS PS-800 v46.1                                               PSCRIPT.DRV
QMS PS-800 Plus                                                PSCRIPT.DRV
QMS PS-800 Plus v46.1                                          PSCRIPT.DRV
QMS PS-810                                                     PSCRIPT.DRV
QMS PS-810 Turbo *                                             PSCRIPT.DRV
QMS PS-815 *                                                   PSCRIPT.DRV
QMS PS-815 MR *                                                PSCRIPT.DRV
QMS PS-820 *                                                   PSCRIPT.DRV
QMS PS-820 MR *                                                PSCRIPT.DRV
QMS PS-825 *                                                   PSCRIPT.DRV
QMS PS-825 MR *                                                PSCRIPT.DRV
QMS PS-1500 *                                                  PSCRIPT.DRV
QMS PS-2000 *                                                  PSCRIPT.DRV
QMS PS-2200 *                                                  PSCRIPT.DRV
QMS PS-2210 *                                                  PSCRIPT.DRV
QMS PS-2220 *                                                  PSCRIPT.DRV
Qume ScripTEN                                                  PSCRIPT.DRV
Seiko Colorpoint Model 04 *                                    PSCRIPT.DRV
Seiko Colorpoint Model 14 *                                    PSCRIPT.DRV
TI microLaser v52.1 with 17-Font PS Option *                   PSCRIPT.DRV
TI microLaser v52.1 with 39-Font PS Option *                   PSCRIPT.DRV
TI Omnilaser 2108                                              PSCRIPT.DRV
TI Omnilaser 2115                                              PSCRIPT.DRV
Varityper VT-600                                               PSCRIPT.DRV
Wang LCS15                                                     PSCRIPT.DRV
Wang LCS15 FontPlus                                            PSCRIPT.DRV

Additional drivers may be available from the respective printer vendors.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.25. 3270 Emulation Tips ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Jim Pearson
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1992)

This item was inspired by the number of calls received from technicians having
trouble installing 3270 emulation in the DOS or OS/2 SDLC or 802.2 LAN
environment.  Gateway configuration problem calls far out-number those for
standalone configurations. Most of the problems that the NSC helps resolve
involve missing and/or incorrect information.  We believe there are two main
reasons for the problems.

Reasons
One reason is the lack of training or experience installing and troubleshooting
3270 emulation programs in the LAN and Gateway environment.  Training is now
available in the form of a self-study Interactive Video Disk (available through
Business Partner Education).  This means training can now be self-paced and
done right at the work location, with no travel required.

The other reason is a lack of planning and site preparation.  The emulation
program manuals have installation planning information that is quite valuable.
Worksheets and questions about the intended installations when properly used
would reduce the install time and prevent many of the problems.  Using the
worksheets and planning guides with the help of the host site (the mainframe on
the other end to which you are connecting) would eliminate the guess work about
what to input for various parameters.  Reviewing the worksheets with the proper
host site personnel before the installation is begun would ensure the correct
information.  Some installations will be more complex than others.  This
increases the risk of problems and failing to complete the install in a timely
manner.  By asking for assistance from the host personnel before and during
installation one can greatly reduce the chances of problems.

The following is a list of the parameters required by the two most troublesome
connection types, SDLC and LAN 802.2 when using Personal Communications/3270
emulation:

SDLC                                    802.2
Block ID                                Destination Address
Physical Unit ID                        Physical Unit ID
PIU Size                                Block ID
Switched Line (Yes/No)                  PIU Size
SDLC Station Address                    Number of Sessions
Continuous Carrier (Yes/No)             Number of Sessions per Gateway
Half Speed (Yes/No)                     Adapter Number
NRZI Encoding (Yes/No)                  Remote SAP
Answer-Tone Generation (Yes/No)
Number of Sessions
Adapter Number
Number of Sessions per Adapter

One little-used feature that can be of great help is the "F1" key.  This key
when used in a parameters field will provide hints and additional information
about the field requiring input.  I urge anyone who has not already used this
feature, to try it.

Three important items to consider at the workstation end are:

 1. The LAN Support program.  (Make sure you choose the correct drivers for
    your particular configuration.)
 2. Modifications to the CONFIG.SYS.  (Verify that CONFIG.SYS has the correct
    path and filename for these drivers.)
 3. The number of Link Stations assigned.  (The number of Link Stations should
    be increased if you have trouble getting all the workstations through the
    gateway.)

OS/2 Extended Edition's 3270 emulation brings with it the same types of
problems found in the DOS 3270 emulator, as well as other complexities.  I
highly recommend ordering additional manuals to assist with OS/2 communications
configurations.  Two such manuals are:

 1. The red cookbook, Communications Manager SDLC, X.25, and LAN Environment
    (Form # GG24-3554).
 2. Systems Administrator's Guide for Communications (01F0302).

These publications may be ordered through your IBM branch office.

Important Parameters
Some OS/2 Communications Manager parameters require very close attention and
coordination with the host site personnel. These parameters are:

 Local LAN Adapter Address (12 hex characters)
 LAN Destination Address (12 hex characters)
 Node ID (5 hex characters)
 LU Local Address (NAU)
 Local SDLC Station Address (2 hex characters)
 Maximum RU Size
 Maximum Number of Link Stations
 Modem Rate (Full or Half Speed)

Consult with the host site personnel and supporting documentation for details.
Make it easy on yourself: plan ahead and prepare for your installations with
the host site personnel and related documentation.

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.26. OS/2 System Limits ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

The following tables list the various limits to OS/2 in the areas of Sessions,
Resources, Memory, Presentation Manager, Hardware, and SQL.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

To return to the OS/2 1.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.6.26.1. OS/2 Session Limits ΓòÉΓòÉΓòÉ

The table below lists specific session limits imposed by OS/2.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé                      SESSION LIMITS                     Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                          Γöé OS/2 1.2  Γöé Used ByΓöéAvailableΓöé
Γöé                          ΓöéSystem Max.ΓöéOS/2 1.2ΓöéFor Apps.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Full-Screen Sessions     Γöé       16  Γöé     4  Γöé     12  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PM Sessions              Γöé       16  Γöé     2  Γöé     14  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VIO Sessions             Γöé       16  Γöé     0  Γöé     16  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS Compat. Mode SessionsΓöé        1  Γöé     0  Γöé      1  Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 System Limit                                 OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.6.26.2. OS/2 Resource Limits ΓòÉΓòÉΓòÉ

The table below lists specific overall system limits imposed by OS/2.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé                       RESOURCE LIMITS                    Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                           Γöé OS/2 1.2  Γöé Used ByΓöéAvailableΓöé
Γöé                           ΓöéSystem Max.ΓöéOS/2 1.2ΓöéFor Apps.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Processes                 Γöé     511   Γöé     7  Γöé    504  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Threads                   Γöé     511   Γöé    28  Γöé    483  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Threads per Process       Γöé      53   Γöé     0  Γöé     53  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Open File Handles         Γöé     64K   Γöé    73  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Pipes                     Γöé  Part of Open File Handles   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Pipe Size                 Γöé     64K   Γöé     0  Γöé    64K  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Queues                    Γöé   1,448   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Queue Elements per Queue  Γöé   3,268   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Queue Priorities          Γöé      16   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Timers                    Γöé  Equal to Number of Threads  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Timers per Process        Γöé       6   Γöé     0  Γöé      6  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé System Semaphores         Γöé     256   Γöé    43  Γöé    213  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Semaphores with           Γöé           Γöé        Γöé         Γöé
Γöé   Outstanding Wait        Γöé     128   Γöé     2  Γöé    126  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Semaphores per Muxwait    Γöé      16   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé System Signals per ProcessΓöé       3   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé User Signals per Process  Γöé       3   Γöé     0  Γöé    ---  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Named Shared Segments per Γöé           Γöé        Γöé         Γöé
Γöé   Process                 Γöé      30   Γöé     0  Γöé     30  Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

Notes:

Threads:  The minimum available space on the stack for a thread calling OS/2
functions is 4KB.  The system allows only one timer per thread.

Semaphores:  System semaphores have a use count and a reference count:

 1. The use count is the number of events a system semaphore can represent.  A
    system semaphore is limited to having no more than 255 concurrent uses.  A
    use is any one of the following events:

    a. Creating a system semaphore.
    b. Opening a system semaphore.
    c. Specifying the handle of the system semaphore on a call to an OS/2 API,
       for example, DosTimerAsync.

 2. The reference count is the number of threads waiting for an exclusive
    system semaphore.  A system semaphore is limited to having no more than 255
    concurrent references.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.6.26.3. OS/2 Memory Limits ΓòÉΓòÉΓòÉ

The table below lists specific memory limits imposed by OS/2.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé                      MEMORY LIMITS                       Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                          Γöé  O/2 1.2  Γöé Used ByΓöé AvailableΓöé
Γöé                          ΓöéSystem Max.ΓöéOS/2 1.2Γöé For Apps.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Segment Size             Γöé     64K   Γöé     0  Γöé     64K  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Segments                 Γöé  50,967   Γöé   814  Γöé  50,153  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Swappable Segments       Γöé  16,000   Γöé   412  Γöé  15,588  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Discardable Segments     ΓöéAvail. Mem.Γöé   250  ΓöéA.M.-250  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Non-Shared Segments      Γöé   2,908   Γöé     0  Γöé   2,908  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Shared Segments per      Γöé   6,144   Γöé     0  Γöé   6,144  Γöé
Γöé Process                  Γöé           Γöé        Γöé          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Fixed Segments           ΓöéAvail. Mem.Γöé    53  Γöé A.M.-53  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Libraries                ΓöéAvail. Mem.Γöé    29  Γöé A.M.-29  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Global Descriptor Tables Γöé           Γöé        Γöé          Γöé
Γöé   (GDTs)                 Γöé       1   Γöé     1  Γöé       1  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GDT Entries              Γöé   8,191   Γöé 1,195  Γöé   6,996  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Local Descriptor Tables  Γöé           Γöé        Γöé          Γöé
Γöé   Per Process            Γöé       1   Γöé     0  Γöé       1  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LDT Entries per LDT      Γöé   8,192   Γöé     0  Γöé   8,192  Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limit                                 OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.6.26.4. OS/2 PM Limits ΓòÉΓòÉΓòÉ

The table below lists specific limits imposed by OS/2 Presentation Manager.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé          PRESENTATION MANAGER LIMITS          Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                                  Γöé  OS/2 1.2  Γöé
Γöé                                  ΓöéSystem Max. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PM Objects                       Γöé  ~900 (4u) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé String Atoms                     Γöé     16,000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Integer Atoms                    Γöé     48,000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Heap Size                        Γöé        64K Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Segments in Segment store of     Γöé            Γöé
Γöé   Presentation Space             Γöé     16,378 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Local Fonts/Presentation Space   Γöé        254 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Logical Color Table              Γöé        31K Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Presentation Space (One Segment) Γöé        64K Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Presentation Spaces per Process  Γöé         32 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Horizontal Scan Lines per Cursor Γöé         32 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Cursor Width (Text Mode)         Γöé          1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Clipboard Size                   Γöé        64K Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.6.26.5. OS/2 Hardware Limits ΓòÉΓòÉΓòÉ

The table below lists specific hardware limits imposed by OS/2.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé                      HARDWARE LIMITS                   Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                                Γöé  OS/2 1.2 Γöé  OS/2 1.3 Γöé
Γöé                                ΓöéSystem Max.ΓöéSystem Max.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Fixed Disk Drives Supported    Γöé      15   Γöé      24   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Logical Drives Supported       Γöé      26   Γöé      26   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Maximum Disk Partition Size    Γöé     2GB   Γöé     2GB   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Maximum # of Partitions/Drive  Γöé      16   Γöé      16   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Diskette Drives Supported      Γöé       3   Γöé       3   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Parallel Ports Supported       Γöé       3   Γöé       3   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Serial Ports Supported         Γöé       3   Γöé       3   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Displays Supported ConcurrentlyΓöé       1   Γöé       1   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Mice Supported                 Γöé       1   Γöé       1   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Keyboards Supported            Γöé       1   Γöé       1   Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limit                               OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.6.26.6. OS/2 SQL/DBM Limits ΓòÉΓòÉΓòÉ

The table below lists specific limits imposed by OS/2 Structured Query Language
and/or the OS/2 Database Manager.

ΓöîΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÉ
Γöé              SQL & DATABASE MANAGER LIMITS              Γöé
Γö£ΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöñ
Γöé                              Γöé       OS/2 1.2/1.3       Γöé
Γöé             Item             Γöé      System Maximum      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest DATE value (in ISO    Γöé                          Γöé
Γöé format)                      Γöé         9999-12-31       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest DECIMAL value         Γöé 999...999(thirty-one 9s) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest FLOAT value           Γöé    Approx. +1.79769E+308 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest INTEGER value         Γöé            2,147,483,647 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest negative FLOAT value  Γöé      Approx. -2.225E-307 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest SMALLINT value        Γöé                   32,767 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest TIME value (in ISO    Γöé                          Γöé
Γöé format)                      Γöé          24.00.00        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLargest TIMESTAMP value (in   Γöé                          Γöé
Γöé ISO format)                  Γöé9999-12-31-24.00.00.000000Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest authorization ID,     Γöé                          Γöé
Γöé table qualifier, view quali- Γöé                          Γöé
Γöé  fier, or plan name          Γöé                        8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest correlation-name or   Γöé                          Γöé
Γöé name of a column, table,     Γöé                          Γöé
Γöé view, or index               Γöé                       18 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest host variable used forΓöé                          Γöé
Γöé  insert and update, in bytes Γöé                   32,700 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest index key             Γöé                      255 Γöé
Γöé                              Γöé   (less # of key columns Γöé
Γöé                              Γöé    that allow nulls)     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest row of a table or     Γöé                          Γöé
Γöé view, in bytes,including all Γöé                          Γöé
Γöé overhead                     Γöé                    4,005 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest SQL statement in bytesΓöé                   32,765 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLongest SQLDA, in bytes       Γöé                   32,767 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum database size         Γöé Available Partition SpaceΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum length of a CHAR      Γöé                          Γöé
Γöé column, in bytes             Γöé                      254 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum length of a character Γöé                          Γöé
Γöé constant                     Γöé                    4,000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMax length of a LONG VARCHAR  Γöé                          Γöé
Γöé column, in bytes             Γöé                   32,700 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum length of a VARCHAR   Γöé                          Γöé
Γöé column, in bytes             Γöé                    4,000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum number of columns in  Γöé                          Γöé
Γöé a table                      Γöé                      255 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum number of rows in a   Γöé                          Γöé
Γöé table                        Γöé Available Partition SpaceΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum total length of       Γöé                          Γöé
Γöé columns in a GROUP BY clause Γöé                    4,005 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum total length of       Γöé                          Γöé
Γöé columns in the SELECT list,  Γöé                          Γöé
Γöé when an ORDER BY or SELECT   Γöé                          Γöé
Γöé DISTINCT clause is used      Γöé                    4,005 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMaximum total length of host  Γöé                          Γöé
Γöé and indicator variable       Γöé                          Γöé
Γöé pointed to in an SQLDA       Γöé      System Storage      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost active cursors in a      Γöé                      300 Γöé
Γöé single program               Γöé                          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost columns in a table or    Γöé                          Γöé
Γöé view (the value depends on   Γöé                          Γöé
Γöé the complexity of the CREATE Γöé                          Γöé
Γöé VIEW statement               Γöé                      255 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost columns in an index key  Γöé                       16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost elements in a select listΓöé                      255 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost functions in a select    Γöé                          Γöé
Γöé list                         Γöé      System Storage      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost host variables in a      Γöé                      512 Γöé
Γöé precompiled program          Γöé                          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost host variables occur-    Γöé                          Γöé
Γöé rences in an SQL statement   Γöé                    1,490 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost indexes on a table       Γöé      System Storage      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost predicates in a WHERE or Γöé                          Γöé
Γöé HAVING clause                Γöé      System Storage      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMost table names in an SQL    Γöé                          Γöé
Γöé statement.  (In a complex    Γöé                          Γöé
Γöé SELECT, the number of tables Γöé                          Γöé
Γöé that can be joined may be    Γöé                          Γöé
Γöé significantly less.)         Γöé                       15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest DATE value (in ISO   Γöé                          Γöé
Γöé format)                      Γöé         0001-01-01       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest DECIMAL value        Γöé-999...999(thirty-one 9s) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest FLOAT value          Γöé    Approx. -1.79769E+308 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest INTEGER value        Γöé           -2,147,483,647 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest positive FLOAT value Γöé      Approx. +2.225E-307 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest SMALLINT value       Γöé                  -32,768 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest TIME value (in ISO   Γöé                          Γöé
Γöé format)                      Γöé          00.00.00        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmallest TIMESTAMP value (in  Γöé                          Γöé
Γöé ISO format)                  Γöé0001-01-01-00.00.00.000000Γöé
ΓööΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓöÿ

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Sections
OS/2 Session Limits                               OS/2 Resource Limits
OS/2 Memory Limits                                OS/2 PM Limits
OS/2 Hardware Limits                              OS/2 SQL/DBM Limits

Or, to return to the OS/2 System Limits header.


ΓòÉΓòÉΓòÉ 6.7. OS/2 2.x Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on IBM OS/2 V2.x and related products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Tips Documents
What's New in Version 2?                                OS/2 2.0 Update
OS/2 2.0: The Real Deal
                                                        Windows 3.0 Enhanced Mode vs. OS/2 2.0
Systems Supported by OS/2 2.0
                                                        Printers/Plotters Supported by OS/2 2.0
What Documentation Comes With OS/2 2.0
                                                        Recreating the OS/2 2.0 Command Prompts Folder
Setting Up 109-Line Command Prompt Windows |            Supported SCSI Adapters
                                                        |

Or, to return to the Tips-and-Techniques header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.1. What's New in Version 2?ΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1991)

OS/2 Version 2.0 will be a landmark in personal computer operating systems.  On
April 18, 1991, I had the opportunity to watch the IBM FTN (Field Television
Network) broadcast discussing and demonstrating this technical marvel.

I know many of you also watched the FTN, or were fortunate enough to actually
be invited to the three-day "relaunch" of OS/2 held in New York.  For you
readers, this column may be largely a repetition of what you already heard.
But stay with me, please.  There is more to V2.0 than was brought up at the
relaunch.  To recap, for those who haven't already heard, OS/2 will offer the
following capabilities and features:

BACKWARD COMPATIBILITY

The biggest concern for most DOS and Microsoft Windows users considering
upgrading to OS/2 is what to do with all their old programs.  It costs too much
to replace all the programs at once; and in many cases OS/2 versions of their
favorite (or mission-critical) applications don't yet exist.  So for OS/2 2.0
to be a success, it must provide a way for customers to continue using their
existing apps until inexpensive OS/2 upgrades are available to take the user
beyond the limits of DOS and Windows.  OS/2 should also provide enough
additional function to differentiate it from Windows.  The following topics
describe the OS/2 2.0 features that do just that.

32-Bit Addressing, Etc.
The single most important enhancement to V2.0 is its ability to fully utilize
the 32-bit architecture of the Intel 386/486 family of microprocessors
(including the SX varieties).  Instead of being limited to a "paltry" 16MB of
RAM, 2.0 will let you spread out into 4GB (that's 4,096 MB for those not used
to thinking in gigabytes!)  if need be.  And if that's not enough, it can
access up to 64TB (terabytes, or 64 million MB) of virtual memory!  (I wonder
how long it will be before someone exceeds that memory limit!)  It also means
that all data transfers to and from the processor will be 32-bit transfers, for
better performance.  (The expected performance improvement upgrading from a
16-bit program to a 32-bit version ranges from 5-60%, depending on how an
application is written, and what 32-bit features it uses.)  It also means that
the 32-bit instructions unique to the 386 (et. al.)  chip can be used for
better memory management.  It is this feature that allows the multiple
concurrent DOS window capability in V2.0.

MVDM
Speaking of the multiple DOS windows, the 32-bit instruction set allows OS/2 to
create Multiple Virtual DOS Machines; which means in essence that each DOS
session runs independently of (and more importantly, protected from) one
another.  So if one DOS session should purchase a plot on Boot Hill, it is
incapable of hanging the entire system, or even another DOS, Windows or OS/2
session; simply cancel the frozen session, and start a new one.  None of the
other sessions are affected.

As of this writing, I have not yet seen Windows 3.1; but most people who have
used Windows 3.0 to any great extent recognize that periodic lockups, resulting
in a loss of data in all sessions, is an occupational hazard when running
multiple DOS sessions.  This will not be a problem under OS/2 2.0.

DOS Box Memory
Another advantage that 2.0 gives us is the ability to load all device drivers
into >640K memory, leaving only a small "bootstrap" driver in low memory to
point to the others.  This means that even after network and other drivers are
loaded, almost all of the DOS mode memory is available to the user!  How much,
exactly?  Well, the numbers are not final yet, as we are still dealing with
beta code, but the latest estimate I have heard is approximately 633K free.  By
comparison, DOS 5.0 will provide about 623K before drivers, and somewhere in
the 500's after.  Running Windows 3.0 on top of DOS 3.3/4.0 will leave even
less (exact numbers, of course, depend on the version of DOS, and the unique
combination of drivers used in each configuration).

If 630K+ is not enough, DOS EMS drivers can be used to access up to 32MB of EMS
4.0 memory; and programs that incorporate "DOS memory extenders" that use DPMI
(DOS Protected Mode Interface) technology are also supported.

More DOS Goodies!
In addition, each DOS session starts with an individual copy of CONFIG.SYS and
AUTOEXEC.BAT.  This means that each program can set its own unique environment,
using whatever DOS device drivers and application drivers it needs.  Yes, I
said DOS device drivers.  The CONFIG.SYS file booted in the DOS boxes will be
the same ones you would use if booting from a DOS-only system, containing all
the DOS device drivers you have accumulated for your hardware.  In addition, if
your DOS apps contain their own drivers (such as the hundreds of printer
drivers Word Perfect supplies), your app will be able to use those drivers as
well.  In other words, you will have the best of both worlds:  All the OS/2
drivers you can get your hands on, plus all the DOS drivers you already have.

But even that is not all.  Should you encounter any software that for whatever
reason will not run in a "DOS session" (which is really OS/2 emulating DOS
3.3/4.0), the user has the option of actually booting a copy of "real" DOS in
one or more DOS sessions.  So you would be able to run a DOS program that uses
undocumented DOS hooks (and so won't run in a DOS emulation session) under real
DOS inside an OS/2 DOS box.  The only limitation I have heard is that the
version of DOS used must be new enough to sup port the hardware it is run on
(for example, DOS 3.3 or later on PS/2s; or 3.0 on an IBM AT).

By the way, as a test of compatibility and performance, the FTN showed two
copies of Microsoft Flight Simulator running concurrently, with no apparent
difference in performance as compared to one copy flying solo.  Another session
showed a version of Norton Utilities running in a DOS box as well!

If your communications needs can't be met by OS/2 software, you can run
multiple DOS and OS/2 sessions, each with its own comm software and drivers.
As long as they don't try to use the same modems or other communications
hardware at the same time, they can all be running concurrently.  So you might
have an Async session in one window, a 3270 session in another, a LAN session
in another, and so on.  And it doesn't matter which ones are DOS and which are
OS/2.

OS/2 Does Windows!
A feature of importance to Windows users is the ability to run Windows apps
unmodified, without needing Windows itself.  A cross-licensing agreement
between IBM and Microsoft allows IBM to include the Windows code inside OS/2,
so a Windows program won't know the difference.  This permits multiple Windows
2.x and 3.x apps to run alongside multiple DOS apps, multiple OS/2 16-bit
programs, and multiple OS/2 32-bit packages.  So a user's investment in DOS and
Windows software is preserved.  The apps may not take advantage of all the OS/2
features a real OS/2 app might use (such as multi-threading, for example), but
they will work as well as they do under DOS or Windows, and without those fatal
system hangs.

You might expect that Windows software running under OS/2 would perform poorly
compared to running under Windows 3.0 itself.  In fact, the apps ran
considerably faster under 32-bit OS/2 in a side-by-side multi-tasking
comparison against Windows, running o n identically configured 20MHz PS/2 Model
70s with 6MB of RAM.

Another important capability of OS/2 2.0 was demonstrated at the relaunch.
When a Windows 3.0 user, running in Enhanced mode (to take advantage of the
memory management capabilities), wants to run a Windows 2.x app, he must close
all the programs currently running, end Windows, and restart it in Standard or
Real mode.  Then he must reverse the process to go back to Windows 3.x programs
that run in Enhanced mode.  OS/2 2.0 allows Windows 2.x and 3.x apps to be
running concurrently without any cumbersome s topping and starting between
modes.

A feature unique to the PM environment is the ability for these DOS and Windows
apps to work with the OS/2 system clipboard. This means that you can highlight
and copy a section of an Excel for Windows spreadsheet (or a 1-2-3 V2.2 DOS
spreadsheet, for that matter), and paste it into a Word Perfect 5.1 for DOS
documents, or vice versa; even though some of the apps themselves don't support
cutting, copying, and pasting.  This ability was demonstrated at the relaunch
and took less than 2 seconds to accomplish.  In addition, all Windows and OS/2
apps that support Dynamic Data Exchange (DDE) and/or Named Pipes, can exchange
data by those techniques, as well.

NEW OS/2 FEATURES

So far we have been talking about how OS/2 2.0 allows you to run all your old
DOS and Windows apps, and run them better than they did in their native modes
(faster, and with more available memory, and with the ability to cut and paste
between multiple windowed sessions).  Now we'll discuss all the new features
provided for installing and using OS/2 2.0 and OS/2 programs.

Intelligent Graphical Installation
A good place to start is the new installation interface.  No longer are you
faced with an endless series of full-screen panels asking for information,
without always explaining fully what is needed.  A new PM interface, (with a
colorful photo of a space shuttle launch as the backdrop) uses check boxes and
selection boxes to let you quickly select the features you want, and don't
want, to install.  If you are prompted for some bit of information (say the
drive letter on which to install a feature), but don't know what you are being
asked for, a popup help window is only a double-click away.  Once you
understand what the prompt means, but don't know what information to supply, in
many cases you can "rotate" a list of permissible choices (say all the drive
letters available).  There is also much greater flexibility in the placement of
operating system files on drive letters besides C :.

Plus, the installation program is "intelligent" enough to figure out what
hardware is installed in the computer (at least on Micro Channel systems), and
automatically configure the appropriate device drivers for you.  This saves you
from having to answer a lot of questions about the type of display, mouse,
printer, etc., you have attached; and it eliminates erroneous responses.  (I
believe there is also the ability to override these options, in case, for
example, you prefer to use the Microsoft PS/2 mouse driver with your IBM mouse,
instead of the IBM driver.)

According to Lee Reiswig, IBM Assistant General Manager of Personal Systems
Programming, who demonstrated the installation process, you should "never see
CONFIG.SYS again."  Everything will be done though the graphical
install-reinstall process.

This is already a huge usability improvement over previous versions, yet
there's more.  The installation process also includes an option to have apps
that are already on the hard drive install themselves to menus!

Network Installation
And if that's not enough, network users have the option of installing the
operating system across an OS/2 LAN Server network! No longer do you have to
(im)patiently walk around to 100 workstations, installing each one
individually.  All the installations can be done centrally from the server, and
each installation can be tailored for the particular hardware configuration of
each of the remote nodes.  Because of the intelligent graphical install
process, and because the installation of the nodes is proceeding from the
server's fixed disk, instead of diskettes, an installation shouldn't take more
than about 30 minutes, according to Reiswig; perhaps only 10-15 minutes,
depending on the options installed.

User-Selectable Interface
Okay, so now that OS/2 2.0 is installed, what does it look like?  Well, that's
a difficult question to answer.  Difficult because the user has the option to
make it look like DOS 4.0, DOS 5.0, Windows 3.0, OS/2 1.3, or OS/2 2.0.  This
gives a customer who is used to one of the DOS or Windows interfaces the
ability to continue using that interface until they have a chance to get
comfortable with the new PM "workplace" paradigm.  Then at any time, the user
can switch to another interface. This also helps in a "three shift"
environment.  Each user can tailor the interface to his or her preference in
seconds.

OS/2 Workplace Model
OS/2's new desktop metaphor is called a workplace model.  There were very few
details mentioned in the FTN, but it was evident that the changes will be
significant.  The new metaphor will incorporate file drawers and folders.  The
drag-and-drop capabilities will be greatly enhanced over what currently exists
in 1.3.  And most excitingly, applications and files that are open when the
system is shut down will automatically reopen to exactly the point where they
were when the system was shut down. The demo seemed to imply that if a program
was compiling (or recalculating, or sorting) when the system was shut down, it
would not only reopen when the system was restarted, but the compilation,
recalc, or sort would pick up right where it left off!

The Control Panel is also being spiffed up.  For example, if you want to change
the color of certain objects, simply drag a color from the "color wheel" to a
button, panel, scroll bar, etc., and all such objects will default to the new
color.

Online Documentation
Now let's say that you are using some aspect of OS/2 and have a question about
using the File Manager, or about the Database Manager.  All documentation for
any part of OS/2 2.0, with the exception of a slim installation manual, will be
in the form of on line books.  This is a continuation of the process begun in
V1.2 with the online OS/2 Command Reference manual, taken to its logical
conclusion.  No longer will you have to figure out where you left your manual
last, or who borrowed it yesterday.  And even if you don't normally misplace
your books, you won't have to fumble through the index or table of contents to
find the information you are looking for.  Simply perform a keyword search to
locate the data.  And when you find it, use an electronic bookmark to "dog-ear"
the page for future reference.  Another advantage to this approach is that the
OS/2 packaging consists of one tiny box, just big enough to hold the diskettes
and installation manual.  This will save a lot of shelf space for dealers, and
customers alike (both pre-sale and post-sale).

For those who normally don't find the time to read manuals (except in the
john); or who like to take the books with them to customer installation sites;
despair not.  Each manual should also be available in hard-copy form, at a
nominal charge.

Applets & Games
One of the complaints about OS/2 in the past has been that it didn't include a
bunch of games and simple utilities, the way Windows does.  This too has
changed.  Although I don't know the final list of what is bundled with 2.0, I
have heard that it would be "more than Windows includes."  A few such
mini-apps, or "applets" were mentioned in the FTN, including a "notewriter," a
calendar, solitaire, and "cat-and-mouse."

Some of you may be familiar with a program called PM-Eyes, or X-Eyes (for OS/2
and Unix, respectively), available on many bulletin boards.  It consists of an
icon of two large eyes that do nothing more than watch the mouse pointer move
about the screen.  The cat-and-mouse version consists of an image of a kitten
that chases your mouse pointer (get it?)  all over the screen.  When the
pointer stops, the furry feline stops, sits, yawns, and eventually goes to
sleep until the mouse moves again. It is silly, admittedly, but engaging
nonetheless.  (For some real laughs, try starting multiple copies of this
program, and watch a herd of kittens bouncing all over the place vainly
attempting to intercept the rodent you are zigzagging across your desk!)  If
nothing else, it makes OS/2 seem friendlier and more fun to use; comments that
always seem to be used in reference to Windows, largely because of such
programs.

ES & LS
So far, with the exception of the mentioning how to install OS/2 across a LAN,
I have described only the base operating system. Users of IBM's Extended
Edition, and LAN Server products might also be interested in what is coming, so
I'll tell you what I k now, which unfortunately is not all that much yet.

EE, which under OS/2 V1.x consists of the base (SE) operating system kernel, as
well as Database Manager (DBM), Communications Manager (CM), and OS/2 LAN
Requester (OLR) modules, will be undergoing a major transformation.  Gone will
be the kernel and the requester.  The remaining CM and DBM modules will be
repackaged as OS/2 Extended Services (ES), and will run on top of SE, rather
than as a "competitive" product.

OS/2 LAN Server, which previously included the server program, and downloadable
DOS LAN Requester (DLR) code, now picks up the OLR module, and changes its name
to OS/2 LAN Services.  It also adds "peer services," allowing node-to-node file
transfer without going through the server.

At first glance this reorganization of function may seem no more than window
(pardon the expression) dressing, but it actually serves an important customer
goal:  cost reduction; especially on a large LAN.  With earlier OS/2 versions,
one copy of the LAN Server code was needed (currently $1,040 list price), plus
a copy of EE (at $830 a shot) for every OS/2 node.  (Up to 128 DOS users could
be connected to the server for free, via the DLR code included with the LAN
Server package.)  So let's say a company had a hundred OS/2 users on the
network.  Their cost would be $84,040 (less discounts, of course, and including
the LAN Server).  The recent price reduction on EE 1.3 brings that total to
"only" $69,000, but still a pretty penny!

Now let's compare the 2.0 way of doing things:  You still need one copy of the
LAN Server package.  But instead of buying 100 copies of EE, you buy 100 copies
of SE, for $150 list (after the price reduction) apiece.  That amounts to only
$16,040!  (The price of LAN Services is expected to be the same as that of LAN
Server.)  So the more nodes you add, the bigger the savings. For every 128 OS/2
nodes, you need one more copy of LAN Services, but that's a whole lot less
money than the difference between another 128 copies of SE and EE.

Of course, OS/2 users who use the DBM and CM portions of EE currently will need
the ES module in the second scenario, but only those users will have to spend
the extra money for those features, not every OS/2 node on the network.

As for enhancements to the CM and DBM modules themselves, details are sketchy.
The only enhancements I know of for sure are that:  1) the 5250 emulation
module will be upgraded to PM status; 2) ACDI redirection will be added
(replacing the separate LAN Asynchronous Connection Server, or LANACS,
package--a further cost savings); and 3) there will be more PM database tools
included (in addition to the Query Manager), to handle forward recovery
(snapshots since the last COMMIT), configuration, and directory management.

Send in the Clones!
One of the other major announcements to come out of the relaunch was that IBM
OS/2 2.0 would be supported by IBM on a number of non-IBM systems.  At least
fourteen other vendors (and possibly more by the time 2.0 ships) have (or will
have) verified the compatibility of their systems with an IBM-supplied test
suite.  All systems that pass will be fully supported by IBM, and those
vendors, to run OS/2 2.0.  Although the list of vendors has not been made
public, these vendors include the largest vendors in the industry, and amount
to a majority of the systems sold in the world, not just the USA.  A few of the
vendors were mentioned by name:  Compaq, Tandy/Grid, Siemens/Nixdorf, and
Olivetti (the latter two much more prevalent in Europe than in the States).

CSD Process Enhanced
One of the biggest sore spots for current OS/2 users is the subject of
Corrective Service Diskettes, or CSDs.  Although it is preferable to get
periodic updates to correct known bugs and quirks in the operating system than
to not get them, the installation of these CSDs on many systems was
problematic.  No one liked having to manually install multiple diskettes worth
of patches on dozens or hundreds of systems.  Fortunately, 2.0 addresses this
problem by allowing CSDs to be installed across a network.  Even more
importantly, the graphical PM installation program allows the installer to
select which parts of the CSD he wishes to install, or not install!  This can
help avoid the problem of fixing one problem via the CSD, but creating another.

Price Cuts & Upgrades
As if all this isn't enough, the prices of EE and SE, as previously mentioned
were cut drastically; with SE selling for the same price as Windows, but with
vastly more function and power.  In addition, DOS users can upgrade to OS/2 for
only $99, through t he end of the year, and all OS/2 1.x users will be able to
upgrade to 2.0 for free, also through the end of the year (though there is the
possibility of this deadline being extended, depending on when 2.0 actually
ships).

Other Marketing Strategies
IBM is determined to make OS/2 the kind of success we all would like to see.
To that end we will be taking a number of different approaches.  Among them
will be an aggressive advertising campaign; an enhanced Developer Assistance
Program, with improved loaner and discount hardware provisions; a larger Early
Support Program and Early Experience Program (for end user beta testers); a
bigger business show presence; and other plans not yet announced.

(Remember, what I have discussed here is based on the April 16th FTN and other
information obtained in April.  It is possible that features and functions may
be added, deleted, or changed by the time the product ships; or that I
misinterpreted some information; but the final product should be essentially
the same as described here.)

In summary, OS/2 V2.0 is "A Better DOS than DOS 5.0; a better Windows than
Windows 3.0; and a better OS/2 than OS/2 1.3!"  What more could you ask from an
operating system?

The next few months, in anticipation of the "real thing" arriving, promise to
be both frustrating and exciting.  I can't wait!

To return to the OS/2 V2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.2. OS/2 2.0 UpdateΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 3Q 1991)

By now, those of you who attended the Technical Advisor conference in June
should have received the OS/2 2.0 beta code we promised you (if not, contact
the NSC).  In addition, end-users who were registered on the IBM NSC BBS before
April 30, 1991 are also eligible to receive copies under the OS/2 2.0 Early
Experience Program.  They just have to ask for it via the BBS.

In my last column, I described what would be coming in the final ship-level 2.0
package, based on what I had discovered about it so far.  Since then I have had
a chance to learn more about the final product.

To begin with, beta testers should automatically receive two more beta releases
before 2.0 ships (but, as with most aspects of beta code, dates are subject to
change).  Some of the following features are there now, and some will follow in
later beta releases:

Base Operating System

MOST
The Multiple Operating System Tool (or multiboot) is installed by 2.0 in a
special 1MB disk partition.  When the system is booted, the user is greeted
with the MOST menu, which lists up to three primary partitions created by the
user, each containing an operating system.  The user then decides whether to
boot from, say DOS 4.0, OS/2 1.3, or OS/2 2.0 (or DOS 5.0, DR DOS 5.0, UNIX, or
whatever else).  Whichever partition is selected will then boot as the C: drive
(and the other primary partitions are hidden; ie. they get no drive letters).
If the user makes no selection, after a predetermined amount of time MOST will
boot from the default partition (also predetermined by the user).  In the
version I used when writing this, any of the C: drive primary partitions are
bootable.  I'm told that by the ship-level, all primary partitions on ANY fixed
disk drive (even non-bootable ones) may be booted by MOST.  But, again, this is
subject to change.

MVDM
Not only will you be able to boot "real" DOS inside a Virtual DOS Machine (VDM)
session, but DR DOS 5.0 and Desqview can also be booted.

In comparisons of the available memory in an OS/2 2.0 DOS session versus a
system with DOS 5.0 running MS Windows 3.0, the 2.0 DOS session had about 48K
more memory available for running DOS programs.

V2.0 will include DOS Protected Mode Interface (DPMI) support (a DOS extender
technology).  Plus, IBM is working with VCPI (Virtual Control Programming
Interface) extender product vendors, including Phar Lap, Rationale, and Ergo,
to convert their products to support DPMI.  (Interleaf Publisher and AutoCAD
are examples of applications that use VCPI DOS extenders to access more than
640K of RAM.)

By the way, while "regular" DOS apps are limited to "only" 48MB of RAM, DOS
apps written to the DPMI spec can access up to 512MB of memory!

There is virtual "A20 line" support in each DOS session, for apps that use the
A20 line to access the first 64K of "high memory".

Each VDM will be able to load it's own drivers and set attributes and tuning
parameters for that particular DOS session. So each session can be uniquely
configured.

V2.0 allows up to 256 sessions to be open at once (but memory and screen space
are more likely to be the limiting factors); of which 240 can be windowed (PM,
VIO, DOS, or Windows), and 16 are reserved for full-screen apps.

DOS and Windows 3270 emulation programs that use EHLLAPI (such as IBM Personal
Communications/3270, and IBM Windows Connection) will run in a DOS session.

Workplace Shell
"Sticky" keys and other features will be added to support OS/2 use by persons
with disabilities.  (Keys programmed to be sticky can be selected in sequence,
rather than requiring simultaneous depression; as Ctrl-Alt-Del, for example,
normally does.)

Icons will be provided that, when maximized, will make the screen look like DOS
4.0, DOS 5.0, Windows 3.0, and OS/2 1.3. This is for users who are upgrading
from these environments but don't want or need the Workplace Shell usability
enhancements.  For example, a DOS 4.0 user who upgrades purely to multitask DOS
apps might feel more comfortable with the DOS 4.0 DOSSHELL screen to work from.
As far as he is concerned he is running a multitasking DOS 4.0 system.  By
saving the Workplace Shell desktop with the 4.0 window maximized, the user
would never again have to see any interface but the DOS 4.0 shell, if desired.

At PC Expo, in June, in a demonstration of the drag/drop functionality of the
2.0 Workplace Shell, I watched as a document icon was dragged from a LAN Server
network drive and dropped on a NetWare LAN network drive; then dragged and
dropped on a Banyan Vines network drive.  As simple as that to move a file from
one bridged network to another!

Performance
Interestingly, OS/2 2.0 was not developed for the 386 processor, but for the
486.  What this means is that, while it will run fine on the various flavors of
the 386 (SX/DX), it will also take advantage of the advanced 486 features
(things like burst mode, and "TLB flushing"); thus giving 2.0 a little extra
boost when running on a 486 system.

2.0 is also optimized to use all (fast) motherboard memory before using any
(slow) adapter RAM; in contrast to the way 1.3 worked.

Another plus is that  because paging will replace segment swapping, not only
will "swapping" to disk be faster, but it is also probable that there will be
fewer memory chip failures (TRAP 2s) caused by frequent memory compaction,
which is no longer needed.

By taking advantage of improvments in the file system, the 2.0  print spooler
also will be much faster.

Finally, our Business Partner Micrografx is ahead of schedule in developing the
new 32-bit implementation of the Presentation Manager graphics "engine" that
will make PM screen redraws and object handling much faster.  It is presently
undergoing final testing.

Device Drivers
OS/2 16-bit drivers will continue to work, but performance will not be as good
as 32-bit drivers would be.  Also, DOS apps will be able to use all of the
built-in drivers included in DOS apps; and Windows 2.x and 3.0 programs will be
able to continue using all of the Windows drivers supplied or acquired.

SCSI Support
Currently, the only SCSI adapter support built into OS/2 is for the IBM
controllers. 2.0 will include a generic SCSI driver (in fact it is already
included with the 6.149 build), SCSI.SYS in support of the LADDR model.  This
driver will support the scatter/gather capability of the SCSI specification.

Virtual Math Coprocessor
Some calculation-intensive software will terminate if it doesn't detect the
presence of a floating-point math coprocessor. 2.0 will include a 32-bit 387
emulator.  So software that looks for a 387 will find one.  Although the
performance will not be as high as a real 387 would provide, it saves the
customer the cost of buying one, if speed isn't as important as the cost
(perhaps in a test environment, or for a program that is used only
occasionally).

IPC
Inter-Process Communications, a feature of OS/2, is being extended to DOS and
Windows apps.  Any application that uses Named Pipes can communicate with any
other app that does so, regardless of the "type" of app it is.  In addition,
apps can also communicate with other types via DDE.  And at the very minimum,
cut/copy/paste can be between MVDM, Windows 2.x/3.x, and PM session windows.

Applets
PM Chart, a subset of Micrografx's Charisma graphics program, will be included
as one of the applets shipped with 2.0.

32-bit Applications
Many people have expressed a concern that all this 32-bit performance won't do
much good unless there are 32-bit apps available to take advantage of it. While
there is some merit to this, don't forget that much of OS/2 will be written to
use the 32-bit instruction set and flat memory management, which by itself will
make not only OS/2 run faster, but DOS, Windows, and OS/2 16-bit apps as well.

In addition, more than 30 vendors have announced that they plan to have 32-bit
OS/2 apps ready to go about the same time as OS/2 2.0.  A list of these will be
published when 2.0 is announced.

Programmer's Workbench
Instead of the current Programming Tools and Information kit, selling for $650,
2.0 will offer the Programmer's Workbench. This toolkit will contain the same
kinds of software tools as before, but no manuals.  All documentation will be
in online books, similar to the OS/2 1.3 Command Reference.  Not only will this
mean much smaller, lighter packages, but also keyword searches, to make it
easier to find the information the developer is looking for.  And because  the
paper and printing costs are eliminated, the cost of the toolkit will be much
lower: less than $200.

For those who can't live without hard-copy manuals, those will be offered
separately as the OS/2 Technical Lbrary, also for under $200.  (I know some of
you only read manuals in the john; so physical manuals are a must!)

Finally, IBM will offer a 32-bit C compiler developed by IBM Canada.  This will
be in addition to a 32-bit C compiler offered by Borland, and a 32-bit C++
compiler from Zortech.

ES/LS

Since my last column, a lot more information about the Extended Services and
LAN Services products has been made available. Here is what I have learned so
far.

Installation
ES and LS will run on top of either SE 1.30.1, or 2.0 (but not 1.30); for the
best performance, 2.0 should be used.

The installation process will be much simpler, with ES/LS figuring out much of
the hardware configuration by itself.  And there will be much more online help
to explain what is needed by some of the prompts.

ES/LS can be installed to any partition or drive; not just C:.  To support the
multiboot (MOST) capability of the base operating system, ES/LS will install to
whatever partition is booted.

Should the need arise, an installation can be aborted, by a Ctrl-Esc, and then
restarted from that point at a later time. The installation won't fail if some
files are locked (in use); the new files will simply be stored on disk, and
then later, when the files are no longer in use (say after a reboot), these
files will automatically finish installing.

The use of more efficient compression/decompression programs have reduced the
diskette storage requirement by 40%, while decreasing the unpacking time by
60%.  So standalone installations will be significantly faster.

Currently, the only way to install OS/2 across a network is to use a tool
called NetView Distribution Manager/2 in association with the NetView DM
program product on an MVS host.  This is a very expensive proposition today.
LS 2.0 will provide this function, in a LAN-only environment.

To illustrate the major time-savings this provides the LAN administrator,
recently a large IBM customer used NetView DM/2 to install EE 1.3 on 40
workstations on a LAN in under an hour, total.  By comparison, in a normal
manual installation, EE 1.3 can take as much as 1.5 hours per system.

By  allowing OS/2 to be installed across a LAN, you are able to keep one copy
of the software on the server, and transfer the data at network speeds, rather
than diskette transfer rates.  Plus it enables you to keep one or more standard
configuration setups on the LAN and "broadcast" them to the appropriate systems
as they are being setup.

CSDs
We are all aware of how difficult and time-consuming CSD (patch) installation
is; again, installed manually per workstation. 2.0 will change all that
forever.  Not only can the CSDs be installed across a LAN, much like OS/2
itself, but a new utility, called FIXTOOL, will seek out all files needing
updating, automatically, and replace only those files.  No longer does the user
have to figure out whether there are any files (DOS, for example) or
directories that need to be protected on each drive. FIXTOOL does all the work
for you.

DMA Serial Support
The PS/2 Models 57, 90, and 95 contain serial ports that, by using DMA data
transfers, are capable of transfer rates up to 345.6 Kbps.  OS/2 1.3 only
supports speeds of up to 19.2 Kbps, even on the DMA serial ports.  But ES will
support up to two DMA serial ports, at speeds up to 64 Kbps; and future
releases will increase that amount until it reaches the full 345.6 Kbps.

Network Adapters
In addition to the IBM and OEM network adapters currently supported under 1.3,
2.0 will add support for the IBM Token-Ring 16/4 Bus Master Server Adapter/A,
and additional OEM adapters; both on IBM systems and clones (using the OEM
version of OS/2 SE).  During installation, users will be given the option of
specifying which adapter they are using.

ACDI Redirection
In an enhancement over EE 1.3, async apps that are written to use the
Asynchronous Communications Device Interface (ACDI) can be redirected across a
LAN to a modem on another system.

3174 Peer Communications
A LAN composed of 3174 workstations can bridge to an LS 2.0 network via coax
attachment.

Protocol Support
LS 2.0 will support NetBIOS, 802.2, TCP/UDP/IP, IPX/SPX, XNS, and other
protocol stacks.  It also adds a Media Access Control (MAC) layer interface
(NDIS 1.02).

Performance
Faster, 32-bit, drivers will enable the 16 Mbps Token-Ring and 10 Mbps Ethernet
adapters to be driven much closer to their theoretical limits than in the past,
resulting in much higher overall throughput across a LAN.

A faster NETBEUI, JETBEUI, will be provided (with DIX 2.0 and error logging
support).

Response time for small-to-medium sized record read/writes (where IBM typically
falls behind the competition today) will be greatly improved.  Response time
for large record read/writes (where IBM typically races ahead of the
competition) will also be improved, but not to the same extent.

Database/Query Manager
The Query Manager will be essentially unchanged; but there is much improvement
in DBM.  There will be Roll Forward Recovery, which archives transactions as
they occur, so they can be reapplied if you lose the file and your backup isn't
current.  In other words, it will apply the changes made since your last
backup.

Many of the QM tools have been moved to a new function, called DBTOOLS
(Database Tools).  Eventualy all of QM will be incorporated into DBTOOLS.
Other new tools include a trace facility for DBM, a reorg check, and a
user-defined collating sequence.

DOS Requester/Client
The old term, DOS Requester, is being replaced with a new one, DOS Client, to
better reflect the Client/Server strategy of ES. The DOS Client will now
operate in a window under Windows 3.0 (but there is no QM front-end for
Windows, as there is for PM).

UPS Support
LS 2.0 will contain support for Uninterruptable Power Source (UPS)
programmability.  A UPS that has a connection to a serial port can signal OS/2
when it kicks in (due to a loss of external power).  This tells LS to signal
all users on the LAN that the LAN may come down in X minutes (depending on the
capacity of the UPS), and to save their work.  Then if power isn't restored
before then, another message is sent from the UPS to the Server telling it to
shutdown.  LS then does an orderly shutdown of all sessions.

More!
There are already more than 10,000 customers, dealers, and IBMers around the
world beta testing OS/2 2.0, pointing out bugs and incompatibilities, and
offering suggestions.  When it ships 2.0 should be the best PC operating system
product ever produced!

There is much more I could talk about, but no more room in which to say it.
Remember, what I have told you so far in these last two columns is in reference
to beta code, and as such is subject to change.  By the next issue of this
newsletter, in another two to three months, I should know EXACTLY what is
coming in the final shipment.  So stay tuned for the next thrilling installment
in the 2.0 saga!

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.3. OS/2 2.0: The Real Deal, Part 1ΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 4Q 1991)

As promised in my last column, here are the official announcement details for
IBM OS/2 2.0, IBM Extended Services/2 for OS/2, and IBM LAN Server 2.0.  But
first . . . .

By now you have probably already heard the "bad" news, about how OS/2 2.0
"slipped" into 1992.  So let me tell you why that is not as bad as it sounds,
and is in fact good in many ways.  IBM could have shipped 2.0 by the end of the
year, as intended, but feedback from many customers indicated that the product
as it stood (without such features as "seamless" Windows operation--more on
this later) would not have met their requirements.  This means that many users
would have felt that 2.0 was not as compatible or function-rich as they had
hoped, and might have given upon it entirely.  The alternative, taking a few
months more to add in these and other important features, and performing
additional debugging on all the code, would result in a superior product, but
later than hoped for.  After some heavy soul-searching, the powers-that-be
decided on the latter course of action.  While this may be frustrating for
those of us who have long awaited 2.0's appearance, in the long run we will all
benefit because 2.0 will be a better product.

Now for the features and other details of what is coming.  Rather than
reiterate everything in my last two columns, I will list the features, and only
discuss in detail those that 1) are newly added,  or 2) have changed since I
wrote about them.

                                    OS/2 2.0
The scheduled, real, official, ship date for OS/2 2.0 is March 31, 1992.  The
minimum hardware requirement is for a 386SX-based system, with at least 3MB of
RAM and a 40MB fixed disk drive.  IBM recommends at least 4MB of RAM and a 60MB
fixed disk for best results (less swapping and more storage space for
applications and data) on a stand-alone system or network workstation.  Servers
and other configurations may require considerably more processor speed, memory,
and disk storage.  (For information on how to calculate your exact
requirements, refer to the OS/2 2.0 Installation and Planning Guide, form
number G326-0160, available about the same time as 2.0 itself.)  The list price
of OS/2 2.0 is $195., and the part numbers are 84F7586 for 3.5" media, and
10G2991 for 5.25".

The pertinent features provided by 2.0 are:

DOS Application Compatibility
 Up to 240 DOS sessions running concurrently, each protected from one another
and from other OS/2 and Windows apps.
 Each session will have more than 630K of RAM available to the apps,
regardless of how many drivers are loaded, or how large they are.
 Each DOS session can load its own device drivers, independent of what the
others use.
 If the provided DOS emulation is not adequate for certain applications, DOS
itself (PC DOS 3.3/4.01/5.0, DR DOS 6.0, etc.) can be bootedinside a DOS
session.
 The OS/2 system clipboard can be used to cut/copy-and-paste between DOS
sessions, or between DOS and Windows or OS/2 sessions.
 DOS programs should run at least as fast as they do on a DOS 5.0 system.
 DOS apps can run in windowed and full-screen sessions, in the foreground and
background.
 Those apps written to the DPMI memory extension specification  can access up
to 512MB of RAM; other apps have access to 16MB of extended (XMS) memory, and
32MB of EMS 4.0 expanded memory.

Windows Application Compatibility
 Because Windows source code is actually built into 2.0, all Windows 2.x and
3.0 applications will run under 2.0, exactly as they would on a DOS/Windows
system. (3.1 support may also be in by March, depending on when Microsoft
actually releases 3.1.)
 Windows apps are protected from one another, and from DOS and OS/2 programs,
so the failure of one app will not affect any other.  No longer can UAEs crash
the system.
 Windows apps should run faster than under Windows itself on a DOS system, due
to preemptive multitasking, better memory management (32-bit flat memory
model), and faster file systems (enhanced HPFS, and enhanced FAT).
 The OS/2 system clipboard can be used to cut/copy-and-paste between Windows
sessions, or between Windows and DOS or OS/2 sessions.
 Dynamic Data Exchange (DDE) is supported between Windows apps, and between
Windows and OS/2 apps.
 Object Linking and Embedding (OLE) is supported between Windows apps running
in the same DOS Session.

OS/2 16-Bit Application Compatibility
All 16-bit OS/2 apps that were written to the published interfaces will
continue to run the same as before, but probably faster (again due to the
faster file systems and better memory management).

OS/2 32-Bit Application Advantages
 Naturally, applications written using the new 32-bit compilers from IBM,
Borland, Watcom, Zortech, and others, will take advantage of the capabilities
provided by the 386/486 chips (and derivatives such as the SL, SLC, and SX
varieties), including 32-bit instructions, the flat memory model (no more 64K
segments), and so on.
 A 32-bit 80387 emulator will be provided for those programs that will not run
without a 387 processor in the system.  This will allow users with little
money, and no need for great speed to run this software; as well as software
testers who will only try out a package for a few days or weeks, and wouldn't
need a 387 permanently.
 32-bit REXX language for better performance of REXX procedures.

Non-IBM Hardware Support
 IBM will be shipping one "universal" copy of 2.0 (rather than require every
system vendor to customize a version for their hardware).
 A number of non-IBM systems are being tested for compatibility by IBM and the
system manufacturers.  A complete list of those supported by IBM will be
published shortly before 2.0 ships.  Additionally, vendors may announce their
support for additional systems running 2.0, beyond those brands and models
supported by IBM.
 A generic SCSI driver will be provided to support most or all brands of SCSI
adapters on the market (again, the details will be released shortly before 2.0
is).
 Hundreds of printers, disk/diskette/CD-ROM/optical disk drives, video
adapters, and other devices will be expressly or implicitly supported (many
through built-in emulation of other, supported, devices).  The approximately
100 additional printer and plotter drivers include those for HP LaserJet
III/IIID/IIIP/IIISi and DeskJet models, a number of Panasonic, Seiko, Kyocera
and other brands not before represented, and nearly 20 color printers
(including the HP PaintJet models).

Workplace Shell
 The Workplace Shell object-oriented user interface changes the whole PM
interface from a menu-selection method to a fully drag-and-drop process .  Now
users can merely select objects on the desktop (files, programs, printers,
physical/logical/network drives) and drag/drop one on another (such as a file
icon onto a printer icon to print the document).  Even DOS and Windows
applications running under 2.0 will operate this way.  Many people will find
this interface to be very "Mac-like," providing much of the same ease-of-use
features, and yet better in many ways.  For those who feel more productive from
a command line interface, there are still command prompt windows that can be
opened as desired.
 Objects can be grouped into folders, and folders grouped within other
folders, much as paperwork is organized in a typical office.  To move multiple
objects from one folder to another, the user simply uses the mouse to "draw" a
box around the objects desired and then drags the group to another folder and
drops them there.  That's all there is to it, even if the new folder is on
another physical drive, and even if the folders are on different network
domains.
 Those who feel more comfortable with their familiar DOS or Windows user
interfaces can specify that they want 2.0 to look and act that way for as long
as they want, and later switch to the newer "look and feel."

Client/Server Platform
 When used with various network software products, 2.0 will support the use of
several different requesters simultaneously, including IBM and Novell, on the
same system.
 2.0 supports remote IPL of network adapters so equipped, used in workstations
(usually medialess).

Enhanced Installation
 A graphical interface is now provided for OS/2 installation.  It includes
much more help information about the various installation options than in
previous versions.  There is also a tutorial for those unfamiliar with mouse
usage.
 A selective install process allows the user to determine, feature by feature,
what to install and what to leave out.  To simplify this process, two
preselected installation profiles are provided.  One supplies a certain group
of features that most users would want, and the other is a "give me everything"
choice.  Either way the user can later add or delete features as needed.
 Operating system and application installation may be performed from any
physical or logical drive, including network drives.
 A "response file," or installation script, can be created by an experienced
user to simplify installation by novice users, automatically answering
installation questions as they appear onscreen.
 The installation facility automatically checks the fixed disk for DOS,
Windows, and OS/2 applications.  If found, apps are automatically registered
with the Workplace Shell and placed inside DOS, Windows, and OS/2 folders,
respectively.  The "DOS Properties" of many DOS and Windows apps found are
automatically configured from a database of setup information provided by the
application vendors, so they are already optimized for use with OS/2 2.0 before
you even finish installing OS/2.

Online Documentation
 As with earlier versions of OS/2, 2.0 uses the Information Presentation
Facility (IPF) to display documentation online, provides keyword searches of
the text, and hypertext links to footnotes and between sections.  This greatly
simplifies and speeds up information lookup.
 In the past, only an online Command Reference was supplied with OS/2.  Other
manuals were included on paper.  Included with 2.0 is all system documentation,
including the Command Reference, User's Guide, REXX tutorial, etcetera.  Only
the installation instructions are provided in hard-copy (after all, you have to
be able to install OS/2 before you can use the online books).
 Other online books, such as those provided with the Extended Services/2 and
LAN Server 2.0 products can later be "plugged in" when received.  (Another set
of books, providing marketing, technical, service, and general information
about OS/2 and PS/2 products, called the PS/2 Assistant, can be downloaded from
the National Support Center/Technical Advisor BBS.  For more information about
the PS/2 Assistant, refer to the IBM Advisor, Vol. 1 No. 2, or Vol. 2 No. 3.)

Applets
To help users learn how to use 2.0 quickly and simply a number of small
applications, or "applets" are supplied.  Each is functional, but not likely to
cause any commercial software vendors to lose sleep over the competition.  The
applets fall into two categories: Productivity and Entertainment.  The list of
applets included are as follows:

 Productivity
 - Enhanced Editor (text editor), Softerm Custom (comm software), PM Chart
(graphing program), calendar, alarm clock, note pad, calculator, mini-database,
mini-spreadsheet, and daily and monthly planners.
 Entertainment
 - Chess (LAN version), Klondike Solitaire, Jigsaw, Cat-and-mouse, Scramble,
and Reversi.

Boot Manager
Previously referred to as Multiple Operating System Tool (MOST), the Boot
Manager allows users to create as many as four bootable partitions per physical
disk drive, and boot to whatever operating system is installed there.  Thus a
user could, if desired, have IBM DOS 3.3, IBM DOS 4.01 with Desqview, MS DOS
5.0 with Windows 3.0, DR DOS 6.0, OS/2 1.3, OS/2 2.0, and AIX 1.2.1 (just to
name a few possibilities) installed in different partitions on two or more
drives and be able to boot from any of them as needed, from one common boot
menu.  This can be a real boon for technical support personnel who support
multiple operating environments.  Not only is everything there in one place for
easy access, but having it all on one system cuts hardware expenses for
multiple test systems, and with it electrical and air-conditioning costs to
boot (pun intended).

Technical Support Offerings
In order to better serve our customers, IBM is offering four different support
vehicles, three of them new.  Each has its own advantages, depending on the
customer's needs:

OS/2 Support Line
This offering allows users to register for 60 days of unlimited free 800#
telephone support on installation, setup, usage, and "how to" questions about
OS/2 2.0 only.  To register, users only need to mail the registration card
supplied with OS/2 2.0, or call 800-237-5511.  Before the expiration of the
free 60 day period, users will be offered an opportunity to continue support,
for $129 per year, on a subscription basis.  This subscription includes not
only unlimited voice support for that period, but access to an additional
selection of applets.  The OS/2 Support Line is targeted at home and small
business users.  Hours are 8:00 am to 5:00 pm (local time), M-F, except
national holidays.

OS/2 BBS
The BBS enables the user to electronically access OS/2 technical information,
converse with other users, submit "bug reports," and receive notice of the
availability of fixes.  Instructions for accessing this BBS are contained on
the Service/Support Information Card included in the OS/2 2.0 package.
(Details on hours of operation and cost, if any, have not yet been announced
but will be provided before 2.0 ships.)

SystemXtra for Personal Systems
SystemXtra is aimed at customer Technical Coordinators, and other technical
focal points, who in turn support a number of users within a company or
organization.  It is IBM's premier level of software service for OS/2 1.3/2.0,
LAN Server 2.0, Extended Services/2 1.0, DDCS/2, NetWare from IBM, and other
selected software products running on PS/2s.  SystemXtra provides toll-free
telephone support (800-IBM-XTRA) and electronic support (for customers with
IBMLink authorization).  IBM will provide callback response within one hour.
Fees are determined by the number of designated focal points and the total
number of systems supported, with quantity price-breaks.  The minimum number of
systems accepted for coverage is five.  Hours are 8:00 am to 5:00 pm (local
time), M-F, except national holidays.  SystemXtra contracts can be sold by IBM
authorized remarketers starting November 29, 1991.

End User Support
The Tampa End User Support Center has been in operation for more than a year.
This fee offering provides 800# voice assistance with problems and questions
about a variety of IBM and non-IBM products, for a per-workstation fee.
Because the service is strictly by subscription, nearly any product or
combination of hardware, operating system, and application software products
can be supported at the customer's request.  Fees depend on the number of
systems supported (quantity discounts are available), and the hours of coverage
(7:00 am to 7:00 pm, or 24 hrs).  For more information, call 800-825-USER.

Besides OS/2 2.0, a number of related products were announced.  Here are some
brief descriptions of the products, a list of highlights, and when they will
ship.

                               Extended Services/2
IBM Extended Services/2, shipping April 24, 1992, comprises the Database
Manager (including Query Manager) and Communications Manager portions of OS/2
Extended Edition, without the base operating system or LAN Requester program.
It will run, like a set of application programs, on top of either OS/2 1.30.1
(but not 1.30, unless CSDs are installed to bring it up to the 5015 level, or
higher) or 2.0.  If installed on an EE 1.30.1 system, it will take the place of
the DBM and CM components already installed.  Besides IBM's OS/2 1.30.1,
systems running certain selected non-IBM versions of OS/2 functionally
equivalent to 1.30.1 will also be supported for use with ES/2.

The list of systems supported in this manner is as follows:
AST Research:
 Premium 486-33TE
 Premium II 486SX-20
Compaq:
 Deskpro 386/s
 Deskpro 386/25e
 Systempro
Compuadd:
 320sc
 333T
NCR:
 PC386sx/MC20
Olivetti:
 P750
Siemens/Nixorf:
 PCM-3Dsx
 PCD-3Msx20
 PCD-4T33
Tandy:
 4020SX
 4025LX
GRiD:
 386is-25
 386sx-MFP20

Other systems and vendors may be added to this list before ES/2 ships.

In a break from the past, there will actually be two ES/2 products, called
Extended Services (ES) and Extended Services with Database Server (ESDS),
respectively.  Both products will be available either as is or in the form of
an Administrator's Kit, which adds documentation helpful in the planning and
implementation of ES/2 in a LAN or host-connected environment.

The only difference between the ES and ESDS packages is that the latter
includes a distributed (LAN) feature called Database Client Application
Enablers.  This allows DOS, Windows, and OS/2 clients to access an ES database
server on a LAN.  A system set up as a database server would use the more
expensive ESDS package.  For $1,995. (list price) ESDS provides the DB server
code and licenses to share the server to all users on the LAN who require only
remote database access.  Those requiring local (on their own system) databases,
and possibly remote database access as well, would use the much less costly
($595.) ES package. (Add another $165. to the cost of each if the
Administrator's Kit package is ordered.)

In addition to the CM and DBM features previously included in OS/2 EE, ES/2
adds new ones, and enhances many of those carried forward from EE.  The new or
improved features are:

Communications Manager
 Now users of PCs emulating 3270 terminals, connected via coax cables into a
3174 controller, can participate in a Token-Ring network.  The 3174 is treated
as a LAN gateway for those PCs.
 The 3270 EHLLAPI (Emulator High-Level Language Application Program Interface)
has been enhanced to include support for structured fields, and allow multiple
simultaneous access by more than one application.
 Extensions to the REXX procedural language allow 5250 and 3270 EHLLAPI
functions to be accessed from REXX programs.
 Another REXX extension allows better installation and configuration  of CM
via the new Programmable Configuration support (replacing the Batch
Configuration Utility).
 Through the use of Virtual Device Drivers (VDDs) in OS/2, multiple DOS and
OS/2 programs that use NETBIOS can share the same network adapters.
 Advanced Peer-to-Peer Network (APPN) support has been added to the previous
APPC (Advanced Program-to-Program Communications) feature, allowing existing
APPC apps to take advantage of peer networks. Advantages include simplified
configuration, improved performance, better availability through dynamic
routing, and easier network maintenance.
 HPFS long-filename support has been added for file transfers.
 SNA gateways support more active workstations concurrently; and SNA gateway
LU pooling has been improved.
 5250 emulation sessions run in a window (this feature was included in 1.30.1,
but not 1.3).
 An NDIS (Network Device Interface Specification) interface was added to
provide support for a wider range of network adapters, those that are
NDIS-compliant.
 CM now includes the System/370 Remote Operations Facility for NetView (ROPS,
pronounced "ropes"), which allows a host-based console to issue CLISTs or REXX
execs that invoke OS/2 commands remotely on a ROPS-attached PC.
 Persistent Verification provides ID checking for PCs connected to host CICS
APPC applications.

Database Manager
 Existing DOS and Windows-based PCs can participate as database clients on a
LAN.  Windows users will see a user interface very similar to that provided for
OS/2 database clients.
 Roll-forward recovery (archive logging) will significantly reduce the need
for manual recovery after a system failure (due to power outage, hardware
problem, etc.).
 The addition of First Failure Support Technology/2 (FFST/2) provides better
support for database applications by providing error logging automatically at
the time the error occurs.  This eliminates the need for customers to try to
duplicate the problem before solving it.
 The new Database Tools are a set of PM utilities for managing databases and
database directories, and for configuring an ES/2 database workstation.  The
Database Tools work in conjunction with the Query Manager.
 An SQL command line was added so those familiar with the SQL language will
have the ability to type the commands in directly, without having to go through
the Query Manager or programming language.  This permits quicker access to the
Database Manager functions for those who are comfortable with SQL commands.
This interface also can be used to access host data through the SAA DDCS/2
program (see following section for details).
 Remote Data Services (RDS) now supports NETBIOS access as well as APPC, for
better performance.
 The addition of date and time arithmetic and scalar functions to the SQL
language brings the Database Manager up to SAA Level 1 compliance for SQL,
consistent with the mainframe SQL/DS product.

The part numbers for ES are:  96F8326 (3.5"), 96F8327 (5.25"), 96F8328 (3.5",
with Administrator's Kit), and 96F8329 (5.25", with Administrator's Kit).  The
part numbers for ES with Database Server are:  04G1047 (3.5"), 04G1048 (5.25"),
04G1049 (3.5", with Administrator's Kit), and 04G1050 (5.25", with
Administrator's Kit).

               SAA Distributed Database Connection Services/2 V1.0
DDCS/2 is the connection between the ES/2 Database Manager and host databases.
It allows clients and client/server workstations to access DB2, SQL/DS, and
OS/400 databases.  Like ES/2, DDCS also comes in two "flavors," in this case
single-user and multi-user.

The single-user package allows stand-alone and LAN-attached OS/2 workstations
to access the host databases, using the APPC (LU 6.2) capabilities of ES/2, and
supports "remote units of work," static and dynamic SQL, and SQL unique to the
target database server.

The multi-user implementation, in addition to the above also allows DOS,
Windows, and OS/2 workstations to access the host database through a DDCS
server or client/server workstation.

DDCS/2 extends the host Distributed Relational Database Architecture (DRDA)
advantages to the workstation.  (If you have a mainframe using DRDA you
probably already know these advantages; if not, it probably doesn't matter to
you, so I won't go into details here.)

DDCS/2 is scheduled to ship on April 24, 1992.  The list price for the Single
User package is $500., and the part numbers are 04G1082 (3.5") and 04G1083
(5.25").  For the Multi-User package, the cost is $4,680, and the P/Ns are
04G1087 and 04G1087, for the 3.5" and 5.25" versions, respectively.

                                 LAN Server V2.0
Once again, we have a two-for-one split.  IBM's LAN Server 2.0 will offer an
Entry version, selling for less than LS 1.3 (only $795., down from $1,040.)
with the same basic features, and an Advanced version, which includes major
fault-tolerance function and higher-performance for significantly more money
($2,295.).  Both versions are scheduled for April 24, 1992.

Entry Version
LAN Server 2.0-Entry is similar to LAN Server 1.3, but with enhancements, and
the addition of the OS/2 LAN Requester code that was previously provided with
OS/2 Extended Edition.  It will run on top of both OS/2 1.3 (actually 1.30.2 or
CSD 5050, or later) and 2.0.

New features include:
 Double Byte Character Set (DBCS) support for the DOS LAN Requester.
 Support for Windows 3.0 users to access network files, printers, applications
and other services available on an OS/2 LAN Server domain, through the Windows
GUI.
 OEM support (see the list under Extended Services/2, above).
 Remote IPL from the server by DOS and OS/2 requesters either with or without
built-in disk drives (Token-Ring, PC Network, or Ethernet).
 Multiple logon capability allowing a user to log on at several workstations
in the same domain at the same time.
 Support for the mixing of LAN Server 1.3 and LAN Server 2.0 servers on the
same domain, including both the Entry and Advanced versions of LS 2.0.  (LS 1.3
must be at CSD level 5015 or later.)
 NDIS-compliant IBM and OEM LAN adapter support.
 The IBM Token-Ring 16/4 Busmaster Server Adapter/A is now supported (it was
previously only supported on NetWare and Vines network servers).
 Support for up to four network adapters, and up to four logical networks
concurrently (Token-Ring, PC Network and Ethernet networks) on the same server.
 DOS LAN Requester support for DOS 5.0 Upper Memory Blocks (UMBs).
 DOS and OS/2 LAN Requesters can log on to both OS/2 and NetWare servers and
access resources on both servers.
 Single Systems Image allows the user to view both local and remote resources
as if they are part of the local workstation.
 Time source service allows a domain controller to act as a network time
server, for application time synchronization.
 Uninterruptible Power Supply (UPS) service.  When supported UPS devices
detect a power loss, they signal the Server that power may come down soon, so
users can begin to manually close their applications.  If power does not come
back up in time, the Server will perform an orderly shutdown of the network
before the UPS backup power is exhausted.
 U.S. Government Data Encryption Standard (DES) encryption algorithm is used
for password encryption.

Advanced Version
In addition to the features offered by the Entry product Advanced offers the
following:

 Exploitation of the 386 instruction set, for better performance.
 HPFS386 for better disk I/O performance.
 HPFS386 for file protection against unauthorized access of server files.
 Customized network file I/O device drivers for better performance.
 Disk mirroring/duplexing.
 Local server security.
 Same APIs and function as Microsoft LAN Manager 2.0, plus IBM LAN Server
enhancements.
 Server code runs in Ring 0 for better performance, applications run in Ring 3
for better data integrity.
 File replication service that enables a set of files stored on a server to be
selectively replicated to other servers or OS/2 requesters on the network.

Limitations/considerations:
 Currently, only OS/2 1.30.2 is supported by the Advanced version (IBM intends
to enhance it to run on the 32-bit OS/2 2.0 operating system).
 If installing on an EE 1.3 system, the Database and Communications Manager
modules are rendered inactive. To regain the function, Extended Services/2 must
be installed.
 Advanced requires a 386SX or higher system unit, even when run on OS/2 1.3
(due to the use of HPFS386 and other 386-specific functions).
The part numbers for the Entry product are 04G1051 (3.5") and 04G1052 (5.25").
The 3.5" and 5.25" versions of the Advanced package are 04G1055 and 04G1056,
respectively.

To jump to OS/2 2.0: The Real Deal──Part 2 double-click here.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.4. OS/2 2.0: The Real Deal, Part 2ΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

OASAS I V1.0

This product, from Integra Technologies, Inc., and remarketed by IBM, serves
two purposes for OS/2 1.30.1 and 2.0 users.  1) It manages a disk array of
between three and seven IBM SCSI fixed disk drives on a PS/2, and 2) It offers
fault tolerant protection against disk failure.  OASAS I is currently
available, for $795 (list), using part number 92F1858 (3.5" media only).

Features:
 Provides data striping across all drives.
 Supports FAT or HPFS for entire array.
 Provides RAID (Redundant Array of Inexpensive Disks) level 5 support.
 Once all the drives are formatted with the OASAS software, they appear as one
large contiguous volume.
 When fault-tolerance is enabled, the failure of one drive does not result in
data loss.  In fact, if the failing drive is housed in an external 3510 SCSI
expansion unit, the PS/2 doesn't even have to be powered off to replace the
failing drive.  The array continues to operate, albeit more slowly, while the
drive is replaced and the array structure is rebuilt on the new drive.  The
recreation process can operate as a background task while the other drives are
being accessed.
 Fault tolerance may be disabled for better performance, and then resumed at a
later time.
 Disk seeks are overlapped across multiple disk drives for enhanced
performance.

Limitations/considerations:
 Only IBM Micro Channel PS/2s with SCSI controllers are supported, and only
with IBM 160/320/400MB drives.
 All drives in the array must be identical.  In other words, all 160MB drives,
or all 320s, or all 400s.
 The storage equivalent of one entire drive out of the array is reserved for
the array data protection overhead.  In other words, if three 400MB drives are
used in the array, 400MB are unavailable for data storage. On the other hand,
if seven 400MB drives are used, there are still only 400MB reserved by the
array.  By comparison, the "disk mirroring" technique of fault tolerance, where
all data is duplicated on two identical drives reserves 50% of the total space.

OS/2 2.0 Tools

OS/2 2.0 Developer's Toolkit
The OS/2 2.0 Developer's Toolkit is a comprehensive set of build, resource, PM,
and productivity tools, including:

 A PM dialog box editor.
 A PM font editor
 An editor for icons, bitmaps and pointers.
 An online help (.HLP and .INF) file compiler
 Tools to convert resource editor files to binary format; convert error, help,
prompt, or general text information file to binary format; and to create and
access classes of objects in application programs.
 Sample program source code
 Online documentation.

The Developer's Toolkit begins shipping March 31, 1992.  The part numbers are
10G3355 (3.5") and 10G4335 (5.25"), and they list for $119.

C Set/2 V1.0
C Set/2 V1.0 is an IBM-developed 32-bit C compiler, offering an extensive
run-time library.  When used with the IBM WorkFrame/2 (see below), runtime
libraries are selectable via menu-driven compile-time options.  The focus has
been on code optimization to produce the fastest possible OS/2 applications.

Features and capabilities:
 Supports the development of both single-and multi-tasking applications.
 Provides static and dynamic fully reentrant C runtime libraries.
 Allows the programmer to build Dynamic Link Libraries (DLLs) easily.
 View information and error messages, during compilation, on three levels.
 LINT-like warning messages grouped in subsets (optionally turned off and on
at compile time).
 IBM's linkage-register convention to improve performance by using registers
to pass parameters.
 Other performance enhancements include inlining of selected library
functions, memory file I/O support, asynchronous I/O, and fast floating-point
optimizations.
 Extensive runtime library support that allows programmers not only to take
advantage of the range of 32-bit runtime libraries, but also to use existing
16-bit libraries or APIs, as needed.
 Migration support from IBM C/2 V1.1, or Microsoft C V6.0 source code.
 Implements the C programming element of the SAA Common Programming Interface
(CPI), so applications written to the CPI-C standard are source-code compatible
with other SAA platforms, including the S/370-390, AS/400, and RISC
System/6000.
 Online documentation
 32-bit PM debugger, providing:
 - Source-level debugging that permits programmers to stop a program at
selected breakpoints; add/save/delete breakpoints or conditional breakpoints;
display and change variables at breakpoints; control execution of multiple
threads individually, and evaluate expressions in the program.
 - Step mode debugging, that allows the programmer to bypass previously
debugged code and focus on problem areas.
 - PM debugging, offering the programmer two ways to debug a PM app,
synchronous and asynchronous.  The app window can be operated concurrently with
the debugger windows.

C Set/2 is scheduled to ship on April 7, 1992.  The list price is $696., and
the part numbers are 10G2996 for 3.5" diskettes, or 10G3293 for 5.25 inch.

WorkFrame/2
The IBM WorkFrame/2 product is the integration platform for many developmental
tools, both from IBM and other sources.  All of the other tools mentioned here
"plug in" to the WorkFrame/2 to work together synergistically.

WorkFrame/2 can be used as:
 A tools integrator, allowing different, or multiple, editors, compilers, and
debuggers to be used together seamlessly.  The default is to use the OS/2
Enhanced Editor applet for editing, and the C Set/2 product as the compiler and
debugger, but other combinations are possible, and simple to implement.
 An organizer, grouping files into logical units or projects.  It:
 - Sets up projects, consisting of source files, object files, and one target
file (EXE, DLL, and so forth).
 - Allows the combining of projects into composite projects.
 - Associates each project with a compiler/debugger/maker/linker.
 - Documents all actions on every project, as well as all return codes, in an
Action Log.

Other features include:
 Resource tools to augment those provided with the Developer's Toolkit, above.
 The ability to create, delete, extract, add, and replace modules in object
libraries for input to the linker.
 Programming language independence.
 PM interface.

WorkFrame/2 will ship on March 31, 1992.  The part numbers are 10G2994 (3.5" )
and 10G3293 (5.25"), and the cost is $90.

Developer's WorkBench Convenience Kit
This package combines the Developer's Toolkit and WorkFrame/2, above, and sells
for $199 in either 3.5" (10G4333) or 5.25" (10G4334).  It is scheduled to ship
March 31, 1992.

C Developer's WorkSet/2 Convenience Kit
This bundle is similar to the Developer's WorkBench, but with the addition of
the C Set/2 compiler, above.  The part numbers are 10G2995 for 3.5" or 10G3363
for 5.25".  Both sizes list for $895.  It is scheduled to ship April 7, 1992.

Technical Library
The Technical Library, shipping March 31, 1992, is simply a set of hard-copy
manuals as a companion to the online books included with the Developer's
Toolkit, for those who want them.  The price is $299, and the P/N is 10G3356
(no diskette media).

Upgrade Information

Upgrade order forms for the following products, containing the upgrade details,
will be made available before 2.0 ships.

Standard Edition
All SE 1.x users are eligible for a free upgrade to OS/2 2.0, a $195. retail
package.  The free upgrade period will be from March 31, 1992 through July 31,
1992.

Extended Edition
All EE 1.x users are eligible for a free upgrade to Extended Services/2 with
Database Server V1.0, a $1,995. retail value.  The free upgrade period will be
from April 24, 1992 through August 24, 1992.

LAN Server
All LS 1.x users are eligible for a free upgrade to LAN Server V2.0 Entry, a
$795. retail package.  The free upgrade period will be from April 24, 1992
through August 24, 1992.

PC LAN Program V1.3
PCLP licenses can be upgraded to LAN Server 2.0-Entry for $650; or to LAN
Server 2.0-Advanced for $2,150.

LAN Server 2.0-Entry
LAN Server 2.0-Entry licenses may be upgraded to LAN Server 2.0-Advanced for
$1,570.

IBM 3270 Emulation Program-Entry V1.x, 3270 Emulation Program V3.0, PC/3270
V1.x, or 3270 Workstation Program V1.x
These licences may be upgraded to Extended Services for $445.; or to Extended
Services with Database Server for $1,845.

To jump to OS/2 2.0: The Real Deal──Part 1 double-click here.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.5. Windows 3.0 Enhanced Mode vs. OS/2 2.0ΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 1Q 1992)

When many people hear that the OS/2 2.0 ability to run Windows 3.0 applications
does not include running them in Enhanced mode, they write OS/2 off as a "nice
try, but not good enough to replace DOS and Windows."

But what does Enhanced mode really mean, and how is it different from Standard
mode?  And what is the difference between an application that is compatible
with Enhanced mode, and one that requires Enhanced mode?

A Standard mode Windows application is one that can take advantage of the
ability of a 286 processor (or higher) to run in Protected mode.  This allows
the application to use more than 640K of memory, while affording a measure of
protection from other concurrently-running Windows apps that might crash.

Enhanced mode, which requires a 386SX (or higher) processor, utilizes some
additional 386 instructions to provide added function, including advanced
memory management capabilities and access to some 32-bit instructions by the
Windows apps themselves.

A Windows Enhanced mode-compatible app is one that takes advantage of the
additional features of the 386 to multi-task DOS and Windows apps, improve
performance, and offer memory protection between DOS and Windows apps running
concurrently.  This group consists of virtually all Windows apps.

In addition, a Windows program that requires Enhanced mode is one that uses
some 32-bit instructions to boost performance. There are fewer than half a
dozen such programs in existence!

Because advanced memory management features, memory protection between
applications, and multitasking are inherent in OS/2 2.0, all applications -
DOS, Windows, and OS/2 - automatically benefit from them.

Thus although Windows Enhanced mode-compatible applications may run in Standard
mode under 2.0, they run exactly as if they were in Enhanced mode under Windows
3.0.

Which brings us to that handful of 32-bit Windows applications mentioned
earlier.  But don't dispair.  Most, if not all, of these programs are being
ported to 32-bit OS/2 2.0 apps.  That leaves you to enjoy running all DOS,
OS/2, and 99.99% of Windows 2.x and 3.0 apps in the meantime, concurrently!

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.6. Systems Supported by OS/2 2.0ΓöÇΓöÇTip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1992)

In response to concerns that OS/2 2.0 may not run on enough non-IBM systems,
the following is the current list of more than 50 brands and 200 models of
systems and processor enhancements on which the ship-level version of OS/2 2.0
has passed compatibility testing.

Many more systems are currently undergoing testing and will be added to this
list when testing has been completed.

Note:  This list is very specific as to brand and model of systems supported.
It should not be assumed that another model from the same vendor will also be
supported at a later time.  Differences in system BIOS, video controller, fixed
disk drive controller and other components may render similar-seeming systems
incompatible.  On the other hand, the fact that a brand or model is not on the
list does not indicate incompatibility; only that the system has not yet been
tested, or that testing has not been completed for that system.

Brands                   Models
Acer                     1125E
                         AcerMate 386/33
                         AcerMate 386SX/20N
                         AcerPower 386SX
                         AcerPower 486SX
AEG Olympia              Olystar 70V
                         Olystar 80S
ALR                      BusinessSTATION 386DX Model 1
                         BusinessSTATION 486SX/20 Model 101
                         BusinessVEISA 386/33 Model 1
                         BusinessVEISA 486/33 Model 101
                         MPS Modular 386/33 Model 1
                         MPS Modular 486/33 Model 101
                         PowerFlex 20SX Model 80
                         PowerFlex Flyer Model 60
                         PowerPro 33/486 Model SMP 128/150
AMAX                     PC/486
AMI                      EZ-Flex
Amstrad                  PC3386 SX
AOX                      MicroMaster 386 (processor upgrade) in a PS/2 Model 60
                         MicroMaster 486 (processor upgrade) in a PS/2 Model 55
Apricot                  LS 386SX-20
                         Qi 386-25
                         Qi 486-25
ARES                     TP 386/33 Sonic
ASEM                     DS 486/33
AST                      Bravo 486/25 83V
                         Premium 486/33TE
                         Premium SE 4/33
                         Premium II 386/33
                         Premium II 486SX/20
                         Premium Exec 386SX/20
AT&T                     Safari
CAS                      386SX-20
Club America             Falcon 433
Compaq                   DeskPro 386/25E
                         DeskPro 386/33L
                         DeskPro 386/25M
                         DeskPro 386/s
                         DeskPro 386S/20
                         DeskPro 486/16M
                         DeskPro 486/50L
                         LTE 386s/20
                         SystemPro 386
                         SystemPro 486
                         386/20
CompuAdd                 320SC
                         325
                         333T
                         433E
Cumulus                  GLC 386SX/20
                         GLC 386DX/25
                         GLC 386DX/33
                         GLC 486DX/33
                         Workbox 16
                         Workbox 20
                         486SX/20
Dell                     433DE
                         320N+
                         320SX
                         325P
                         333D
                         450SE
                         486D/25
                         486P/33
Dynex                    386-25
Everex                   486/33 EX0-2804-000L
                         486/33 EX0-2904D-B1
                         486/33E EX0-2904D-01EL
                         486/33E EX0-2908D-01EC
                         486SX/20 EX0-2904A-010L
                         Tempo 386/33 EX0-4408M-00HL
                         Tempo 386/33c EX0-4404M-00HS
                         Tempo 486/20 EX0-4504J-00HL
                         Tempo 486/33c EX0-4608M-00HS
                         Tempo 486SX/20c EX0-4504J-00HS
Gateway 2000             386SX/20C
                         486/33C
Grid                     GridCase 1550sx
                         MFP/420s
                         386is-25
                         386sx-MFP20
                         4020SX
                         4025LS
                         4025LX
G2                       S1-SX
Hertz                    486/33
Hewlett-Packard          QS/20
                         Vectra RS/25C
                         Vectra 386/16N
                         Vectra 386/25
                         Vectra 486/25T
                         Vectra 486/33T
                         Vectra 486s/25
ICL                      CX386s
                         CX3486s
Intel                    DT386-33H
                         LP486SX/25E
                         SnapIn/386 - IBM PC/AT (processor upgrade)
                         SnapIn/386 - PS/2 Model 50Z (processor upgrade)
                         SnapIn/386 - PS/2 Model 60 (processor upgrade)
                         XBASE6E4
Investronica             WS-900 SX
                         WS-600 Cache
Kingston                 SX/Now! 50Z (processor upgrade for PS/2 Model 50Z)
                         SX/Now! 60 (processor upgrade for PS/2 Model 60)
Locland                  486 Convertible
                         486 EISA Convertible
Memorex-Telex            Model 8257
                         Model 8267
                         Model 8280
                         Model 8290
Mitac                    MiStation 3052E
                         Personal Computer 3060F
NCR                      PC386sx/MC20 Model 2410
                         System 3300/3421 Model 2014
                         System 3300/3432 Model 1000
                         System 3300/3433 Model 2000
                         System 3400 Model 3000
NEC                      PowerMate 386/33i
                         PowerMate 486/33E
                         PowerMate 486/33i
Nixdorf                  PWS M45
                         PWS M50
Olivetti                 LSX5010
                         LSX5020
                         M300-10
                         M300-25
                         M380-40
                         M400-10
                         M480-30
                         P750
Packard-Bell             486-33
Phocus                   PD340-240
                         PS333-105
                         PST433-425
                         PT433-670
                         PW325-105
Reply                    D16 3SX-160 Model 16 MCA
                         D32 386-20C Model 32 MCA
                         D32 386-33C Model 32 MCA
                         D32 4SX-200 Model 32 MCA
                         D32 486-250 Model 32 MCA
                         D32 486-330 Model 32 MCA
                         D32 486-50C Model 32 MCA
Research Machines        QE 486 33c
Samsung                  DeskMaster 386S/25
                         NoteMaster 386S/25
Scandic Products         1-45201i
                         1-34201i
                         3-45201E
Siemens/Nixdorf          PCD-3Bsx
                         PCD-3Msx/20
                         PCD-4T/33
                         PCM-3Dsx/16
                         PCM-4T
Swan                     386/33M
Tandon                   OPTIoN T3000
                         OPTIoN PRO T30050
Tandy                    4020SX/386
                         4025LX/386
Tatung                   TCS8160S
                         TCS8640S
                         TCS8800D
                         TCS8960S
                         TCS9600T
Texas Micro Systems      3014A
TI'KO                    PS325
                         PS325C
                         PS340C
                         PS420C
                         PS433C
                         PS450C
Toshiba                  T2000SX
                         T2000SXe
                         T2200SX
                         T3100SX
                         T3200SX
                         T3300SL
                         T3200SXC
                         T4400SX
                         T5200/100
                         T5200
                         T6400SX
                         T8500 Model 25
Unisys                   PW2-4163-SX
Victor                   V386/33M
                         V486/20MX
                         V486/33M
Viglen                   Genie Executive 4DX33
                         Genie Micro 4SX20
Wang                     EC-480-33C
                         PC-350-40C
Wearnes                  Boldline 385SX-25
Zenith                   Z-486/33EE
                         Z-486/33ET
                         Z-486SX/25
Zeos                     386DX-33CT
                         386SX-208DT
                         486-33/8
                         486DX-33T

Total Vendors: 57        Total Models: 201

In addition, OS/2 2.0 is supported on the following IBM systems:

o PS/1 386 (all models)
o PS/2 Model 35 (all models with a 40MB or larger drive)
o PS/2 Model 40 (all models with a 40MB or larger drive)
o PS/2 Model L40 laptop (all models)
o PS/2 Model N51 notebook (all models)
o PS/2 Model 55 (all models with a 40MB or larger drive)
o PS/2 Model 56 (all models)
o PS/2 Model 57 (all models)
o PS/2 Model CL57 laptop (all models)
o PS/2 Model M57 (all models)
o PS/2 Model 65 (all models)
o PS/2 Model 70 (all models)
o PS/2 Model P70 portable (all models with a 60MB or larger drive)
o PS/2 Model P75 portable (all models)
o PS/2 Model 80 (all models)
o PS/2 Model 90 (all models)
o PS/2 Model 95 (all models)

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.7. Printers/Plotters Supported by OS/2 2.0 ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1992)

The following is a current list of the more than 200 printers and plotters
directly supported by V2.0 (not counting all those that will work through the
IBM, Epson, or HP emulation modes of many printers, as well as the generic
PostScript driver), and which drivers to install from the installation
diskettes, for the respective devices.  (Once a "family" driver, such as EPSON,
IBM42XX, IBM52XX, LASERJET, PLOTTER, or PSCRIPT is installed, it reveals
multiple individual printer drivers that can be installed from a printer
object's Settings.)

Note:  Printer names followed with an asterisk (*) indicate drivers added to
OS/2 2.0 that were not available in OS/2 1.3.

This document will be updated as additional printer drivers are released (via
CSDs or on the NSC BBS).

Printers Supported                                             Driver
Agfa-ChromaScript v51.8                                        PSCRIPT.DRV
Agfa-Compugraphic 400P                                         PSCRIPT.DRV
Agfa-Compugraphic 400PS                                        PSCRIPT.DRV
Agfa-Compugraphic 9400PS v49.3                                 PSCRIPT.DRV
Apple LaserWriter                                              PSCRIPT.DRV
Apple LaserWriter II NT                                        PSCRIPT.DRV
Apple LaserWriter II NTX                                       PSCRIPT.DRV
Apple LaserWriter Plus                                         PSCRIPT.DRV
Apple LaserWriter Plus v42.2                                   PSCRIPT.DRV
AST TurboLaser                                                 PSCRIPT.DRV
Colormate PS                                                   PSCRIPT.DRV
Dataproducts LZR 1260 v47.0                                    PSCRIPT.DRV
Dataproducts LZR 2665                                          PSCRIPT.DRV
Digital LNO3R ScriptPrinter                                    PSCRIPT.DRV
Digital LPS PrintServer 40                                     PSCRIPT.DRV
Epson AP-800 Color *                                           EPSON.DRV
Epson DFX-5000                                                 EPSON.DRV
Epson DFX-8000                                                 EPSON.DRV
Epson DLQ-2000 *                                               EPSON.DRV
Epson EPL-6000                                                 EPSON.DRV
Epson EPL-7000                                                 LASERJET.DRV
Epson EPL-7500 v52.3                                           PSCRIPT.DRV
Epson EX-800 Color                                             EPSON.DRV
Epson EX-1000 Color                                            EPSON.DRV
Epson FX-286e                                                  EPSON.DRV
Epson FX-850                                                   EPSON.DRV
Epson FX-1050                                                  EPSON.DRV
Epson GQ-3500 *                                                EPSON.DRV
Epson GQ-5000 *                                                EPSON.DRV
Epson JX-80 Color                                              EPSON.DRV
Epson LP-570                                                   EPSON.DRV
Epson LP-870                                                   EPSON.DRV
Epson LP-1170                                                  EPSON.DRV
Epson LQ-400 *                                                 EPSON.DRV
Epson LQ-500                                                   EPSON.DRV
Epson LQ-510                                                   EPSON.DRV
Epson LQ-550 *                                                 EPSON.DRV
Epson LQ-570 *                                                 EPSON.DRV
Epson LQ-750 *                                                 EPSON.DRV
Epson LQ-850                                                   EPSON.DRV
Epson LQ-860 Color                                             EPSON.DRV
Epson LQ-870 *                                                 EPSON.DRV
Epson LQ-950                                                   EPSON.DRV
Epson LQ-1010                                                  EPSON.DRV
Epson LQ-1050                                                  EPSON.DRV
Epson LQ-1060 Color *                                          EPSON.DRV
Epson LQ-1170 *                                                EPSON.DRV
Epson LQ-2500 Color                                            EPSON.DRV
Epson LQ-2550 Color                                            EPSON.DRV
Epson LX-400 *                                                 EPSON.DRV
Epson LX-800                                                   EPSON.DRV
Epson LX-810                                                   EPSON.DRV
Epson LX-850 *                                                 EPSON.DRV
Epson SQ-850 *                                                 EPSON.DRV
Epson SQ-2500 *                                                EPSON.DRV
Epson SQ-2550 *                                                EPSON.DRV
Epson TLQ-4800 *                                               EPSON.DRV
Epson TSQ-4800 *                                               EPSON.DRV
Epson Generic 9-Pin                                            EPSON.DRV
Epson Generic 24-Pin                                           EPSON.DRV
Generic PostScript (for all PS printers not listed)            PSCRIPT.DRV
HP DeskJet 500 (Emulating an Epson EPL-6000)                   EPSON.DRV
HP LaserJet Classic                                            LASERJET.DRV
HP LaserJet Plus                                               LASERJET.DRV
HP LaserJet 500                                                LASERJET.DRV
HP LaserJet 500 Plus *                                         LASERJET.DRV
HP LaserJet 2000                                               LASERJET.DRV
HP LaserJet II                                                 LASERJET.DRV
HP LaserJet IID                                                LASERJET.DRV
HP LaserJet IID v52.2                                          PSCRIPT.DRV
HP LaserJet IIP                                                LASERJET.DRV
HP LaserJet IIP v52.2                                          PSCRIPT.DRV
HP LaserJet IIP Plus *                                         LASERJET.DRV
HP LaserJet III *                                              LASERJET.DRV
HP LaserJet III v52.2                                          PSCRIPT.DRV
HP LaserJet IIID *                                             LASERJET.DRV
HP LaserJet IIID v52.2                                         PSCRIPT.DRV
HP LaserJet IIIP *                                             LASERJET.DRV
HP LaserJet IIIP v52.2                                         PSCRIPT.DRV
HP LaserJet IIISi *                                            LASERJET.DRV
HP LaserJet IIISi v52.2                                        PSCRIPT.DRV
HP LaserJet Plus                                               LASERJET.DRV
HP PaintJet Color *                                            SMGXPJET.DRV
HP PaintJet XL Color *                                         SMGXPJET.DRV
HP 7440A Plotter *                                             PLOTTER.DRV
HP 7470A Plotter                                               PLOTTER.DRV
HP 7475A Plotter                                               PLOTTER.DRV
HP 7550A Plotter                                               PLOTTER.DRV
HP 7570A Plotter *                                             PLOTTER.DRV
HP 7580A Plotter                                               PLOTTER.DRV
HP 7580B Plotter                                               PLOTTER.DRV
HP 7585A Plotter                                               PLOTTER.DRV
HP 7585B Plotter                                               PLOTTER.DRV
HP 7586B Plotter                                               PLOTTER.DRV
HP 7595A Plotter *                                             PLOTTER.DRV
HP 7596A Plotter *                                             PLOTTER.DRV
IBM 2380 PPS II                                                IBM42XX.DRV
IBM 2381 PPS II                                                IBM42XX.DRV
IBM 2390 PPS II                                                IBM42XX.DRV
IBM 2391 PPS II                                                IBM42XX.DRV
IBM 3816 Pageprinter 01D/01S (Emulating an IBM Quietwriter III)IBM52XX.DRV
IBM 4019 LaserPrinter/LaserPrinter E                           IBM4019.DRV
IBM 4019 LaserPrinter/LaserPrinter E                           LASERJET.DRV
IBM 4019 LaserPrinter/LaserPrinter E with 17-Font
 PS Option                                                     PSCRIPT.DRV
IBM 4019 LaserPrinter/LaserPrinter E with 39-Font
 PS Option                                                     PSCRIPT.DRV
IBM 4029 LaserPrinter 5E                                       IBM4019.DRV
IBM 4029 LaserPrinter 5E                                       LASERJET.DRV
IBM 4029 LaserPrinter 6                                        IBM4019.DRV
IBM 4029 LaserPrinter 6                                        LASERJET.DRV
IBM 4029 LaserPrinter 10                                       IBM4019.DRV
IBM 4029 LaserPrinter 10                                       LASERJET.DRV
IBM 4029 LaserPrinter 10L                                      IBM4019.DRV
IBM 4029 LaserPrinter 10L                                      LASERJET.DRV
IBM 4029 LaserPrinter with 17-Font PS Option
 (300 dpi)                                                     PSCRIPT.DRV
IBM 4029 LaserPrinter with 17-Font PS Option
 (300 dpi)                                                     PSCRIPT.DRV
IBM 4029 LaserPrinter with 39-Font PS Option
 (600 dpi)                                                     PSCRIPT.DRV
IBM 4029 LaserPrinter with 39-Font PS Option
 (600 dpi)                                                     PSCRIPT.DRV
IBM 4072 ExecJet (Emulating an EPSON LQ-1050)                  EPSON.DRV
IBM 4072 ExecJet (Emulating an IBM Proprinter XL24E)           IBM42XX.DRV
IBM 4072 ExecJet (Emulating an IBM Quietwriter III)            IBM5202.DRV
IBM 4201 Proprinter I                                          IBM42XX.DRV
IBM 4201 Proprinter II                                         IBM42XX.DRV
IBM 4201 Proprinter III                                        IBM42XX.DRV
IBM 4202 Proprinter XL                                         IBM42XX.DRV
IBM 4202 Proprinter II XL                                      IBM42XX.DRV
IBM 4202 Proprinter III XL                                     IBM42XX.DRV
IBM 4207 Proprinter X24                                        IBM42XX.DRV
IBM 4207 Proprinter X24E                                       IBM42XX.DRV
IBM 4208 Proprinter XL24                                       IBM42XX.DRV
IBM 4208 Proprinter XL24E                                      IBM42XX.DRV
IBM 4216 Personal Page Printer                                 PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 030                    PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 031 v51.4              PSCRIPT.DRV
IBM 4216 Personal Page Printer II-Model 031 v51.4
 (with automatic sheetfeed option)                             PSCRIPT.DRV
IBM 4224 Models 01/02/E3                                       IBM42XX.DRV
IBM 4224 Model C2                                              IBM42XX.DRV
IBM 4226 Model 302                                             IBM42XX.DRV
IBM 5201 Quietwriter II                                        IBM52012.DRV
IBM 5202 Quietwriter III                                       IBM52XX.DRV
IBM 5204 Quickwriter                                           IBM52XX.DRV
IBM 6180 Plotter                                               PLOTTER.DRV
IBM 6182 Plotter                                               PLOTTER.DRV
IBM 6184 Plotter                                               PLOTTER.DRV
IBM 6186 Plotter Model 1                                       PLOTTER.DRV
IBM 6186 Plotter Model 2                                       PLOTTER.DRV
IBM 7371 Plotter                                               PLOTTER.DRV
IBM 7372 Plotter                                               PLOTTER.DRV
IBM 7374 Plotter                                               PLOTTER.DRV
IBM 7375 Plotter Model 1                                       PLOTTER.DRV
IBM 7375 Plotter Model 2                                       PLOTTER.DRV
IBM Null Printer                                               IBMNULL.DRV
Kyocera F-800A/F-800                                           LASERJET.DRV
Kyocera F-820                                                  LASERJET.DRV
Kyocera F-1000A/F-1000                                         LASERJET.DRV
Kyocera F-1800A/F-1800 *                                       LASERJET.DRV
Kyocera F-2000A/F-2200S *                                      LASERJET.DRV
Kyocera F-3000A/F-3300 *                                       LASERJET.DRV
Kyocera F-5000A/F-5000                                         LASERJET.DRV
Kyocera P-2000                                                 PSCRIPT.DRV
Kyocera Q-8010                                                 PSCRIPT.DRV
Linotronic 100 v38.0                                           PSCRIPT.DRV
Linotronic 100 v42.5                                           PSCRIPT.DRV
Linotronic 200 v47.1                                           PSCRIPT.DRV
Linotronic 200 v49.3                                           PSCRIPT.DRV
Linotronic 300 v47.0                                           PSCRIPT.DRV
Linotronic 300 v47.1                                           PSCRIPT.DRV
Linotronic 300 v49.3                                           PSCRIPT.DRV
Linotronic 500 v49.3                                           PSCRIPT.DRV
NEC Colormate PS v51.9 *                                       PSCRIPT.DRV
NEC LC-890                                                     PSCRIPT.DRV
NEC Silentwriter LC 890XL v50.5                                PSCRIPT.DRV
NEC Silentwriter2 Model 90 v52.0                               PSCRIPT.DRV
NEC Silentwriter2 Model 290 v52.2                              PSCRIPT.DRV
Olivetti LP-5000                                               PSCRIPT.DRV
Panasonic KX-P1123 (Emulating an Epson LQ-850)                 EPSON.DRV
Panasonic KX-P1124 (Emulating an Epson LQ-2500)                EPSON.DRV
Panasonic KX-P1124i (Emulating an Epson LQ-2500)               EPSON.DRV
Panasonic KX-P1180 (Emulating an Epson FX-86e)                 EPSON.DRV
Panasonic KX-P1191 (Emulating an Epson FX-86e)                 EPSON.DRV
Panasonic KX-P1624 (Emulating an Epson LQ-2500)                EPSON.DRV
Panasonic KX-P1654 (Emulating an Epson LQ-1050)                EPSON.DRV
Panasonic KX-P1695 (Emulating an Epson FX-1050)                EPSON.DRV
Panasonic KX-P2624 (Emulating an Epson LQ-1050)                EPSON.DRV
Panasonic KX-P4420                                             LASERJET.DRV
Panasonic KX-P4450                                             LASERJET.DRV
Panasonic KX-P4450i                                            LASERJET.DRV
Panasonic KX-P4455 *                                           PSCRIPT.DRV
QMS ColorScript 100                                            PSCRIPT.DRV
QMS ColorScript 100 Model 10                                   PSCRIPT.DRV
QMS ColorScript 100 Model 30                                   PSCRIPT.DRV
QMS ColorScript 100 Model 30si                                 PSCRIPT.DRV
QMS ImageServer X320                                           PSCRIPT.DRV
QMS IS-X320T *                                                 PSCRIPT.DRV
QMS PS-410                                                     PSCRIPT.DRV
QMS PS-800                                                     PSCRIPT.DRV
QMS PS-800 Plus                                                PSCRIPT.DRV
QMS PS-810                                                     PSCRIPT.DRV
QMS PS-810 Turbo                                               PSCRIPT.DRV
QMS PS-815                                                     PSCRIPT.DRV
QMS PS-815 MR                                                  PSCRIPT.DRV
QMS PS-820                                                     PSCRIPT.DRV
QMS PS-820 Turbo *                                             PSCRIPT.DRV
QMS PS-825                                                     PSCRIPT.DRV
QMS PS-825 MR                                                  PSCRIPT.DRV
QMS PS-1500                                                    PSCRIPT.DRV
QMS PS-2000                                                    PSCRIPT.DRV
QMS PS-2200                                                    PSCRIPT.DRV
QMS PS-2210 v51.0 *                                            PSCRIPT.DRV
QMS PS-2220                                                    PSCRIPT.DRV
Qume ScripTEN                                                  PSCRIPT.DRV
Seiko Colorpoint PS Model 04                                   PSCRIPT.DRV
Seiko Colorpoint PS Model 14                                   PSCRIPT.DRV
Seiko Personal Colorpoint PS *                                 PSCRIPT.DRV
Tektronix Phaser Card V1.1                                     PSCRIPT.DRV
Tektronix Phaser II PX v2_02 *                                 PSCRIPT.DRV
Tektronix Phaser II PXi v2010 *                                PSCRIPT.DRV
Tektronix Phaser III PXi v2010 *                               PSCRIPT.DRV
TI microLaser v52.1 with 17-Font PS Option                     PSCRIPT.DRV
TI microLaser v52.1 with 39-Font PS Option                     PSCRIPT.DRV
TI Omnilaser 2108                                              PSCRIPT.DRV
TI Omnilaser 2115                                              PSCRIPT.DRV
TI 2115 (13 fonts) v47_0                                       PSCRIPT.DRV
Varityper VT-600                                               PSCRIPT.DRV
Wang LCS15                                                     PSCRIPT.DRV
Wang LCS15 FontPlus                                            PSCRIPT.DRV

Additional drivers may be available from the respective printer vendors.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.8. What Documentation Comes With OS/2 2.0? ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1992)

Now that OS/2 2.0 is shipping there are so many different aspects to discuss,
including hardware and software compatibility, upgrades, end-user support, "how
to" issues, and so on, that there just isn't enough room in either this column
or indeed the entire newsletter to discuss them all. For this first issue A.O.
(After OS/2) I have attempted to address the hardware compatibility issues, at
least as far as system and printer support, in two related articles elsewhere
in this issue.  In addition, nearly 50 Qs & As address many small but important
points of concern, including the new Workplace Shell, setup, HPFS, and others.
So what is there to talk about in this column?  In upcoming newsletters I will
address whatever issues seem to be important, or causing the most confusion, at
the time.  But for now, let's start with something basic:

What Documentation Comes With OS/2 2.0?
First, inside the OS/2 2.0 shrink-wrapped box is:

 1. An Installation Guide which in 112 pages describes a basic installation, a
    dual boot environment, the Boot Manager, using response files, setting up a
    migration database, and using bootable DOS images.
 2. A Getting Started booklet that provides a 58-page overview of what OS/2 is,
    and what features it includes (such as REXX,  productivity applications and
    games, how to copy and move objects, and the like).
 3. Another booklet, entitled Migrating to the OS/2 Workplace Shell.  It
    discusses the similarities and differences between the new WPS and the way
    Windows 3.0 and OS/2 1.3 interfaces worked, in 40 pages.
 4. The 70-page Using the Operating System describes how to find, open, move,
    copy and delete objects, how to switch between programs and shut down the
    system, and the other basics necessary to use OS/2.
 5. A Compatibility Information booklet, detailing in 11-pages what kinds of
    programs are likely to have compatibility problems, and the various
    supported video modes.
 6. Another 11 pages on setting up and using the ATM included in OS/2 for use
    with Windows applications, in Adobe Type Manager for Win-OS/2.
 7. The OS/2 Quick Reference is a 6-sided fanfold card that points you to the
    online tutorial, the Master Help Index, and how to start the installation
    of OS/2, plus it identifies all of the standard objects found on the WPS
    desktop.
 8. A Service and Support Information Card, a 6-sided fanfold card (including
    two tear-off mail-in cards for registering for OS/2 support and for
    reporting bugs).  It details the IBM support offerings available, including
    electronic BBS (not the TA BBS, but another one), free 60-day end-user
    technical and service support, and $129. per year ($159. in Canada)
    extended support.  To register a user must mail in the form, or call
    800-237-5511.  Upon registration the user will be assigned a registration
    number to use for further support.  The 60-day support window is from the
    date of the first call, not from the purchase date.
 9. A 3-page booklet called OS/2 Electronic Device Driver Distribution
    Mechanism, that describes how to download drivers and other files from the
    IBM NSC/TA BBS.
10. A License Information booklet that lists in seven pages the important
    features of OS/2 2.0, and minimum hardware requirements.
11. An OS/2 Publications Order Form.  This allows you to order printed copies
    of the online OS/2 Command Reference ($35.75), the OS/2 Keyboards and Code
    Pages book ($8.10), and a "how to" video on the Workplace Shell ($14.95).
12. A 15-page (6-language) Program License Agreement, listing the users legal
    rights and remedies.
13. There is a separate Registration Card for registering the software itself
    (as opposed to registering for support, as above).
14. There is also a Registration Change of Address Card in case your address
    changes after submitting the original registration card.
15. Finally, and perhaps most important, is the Proof of License card.  It is
    this card that you will need for future free or discounted upgrade
    opportunities.  So keep this card in a safe place!

More Goodies
Perhaps loosely termed "documentation" are the following, also included in the
OS/2 box:

 1. An offer of a free copy of the Inside OS/2 monthly journal, with your
    subscription.
 2. An order form for the IBM OS/2 Application Solutions catalog ($19.95) of
    several thousand 16- and 32-bit IBM and OEM applications announced for
    OS/2.  It contains descriptions, prices, phone numbers and addresses for
    the software vendors.  It's a good way to find out what is available for
    OS/2, and what is shipping in the next few months.  The same card can be
    used to subscribe to the IBM Personal Systems Developer magazine ($39.95
    per year) for OS/2 programmers.
 3. A special discount offer form toward the purchase of one of several sets of
    Adobe Type Set packages ($59).  These are collections of Adobe PostScript
    Type 1 fonts for use with OS/2 and Windows applications.
 4. A set of OS/2 2.0 stickers (hidden under the blue "Open" sticker in the
    box) in various sizes, suitable for advertising the fact that you were
    smart enough to upgrade to the next generation operating system!

Online Books, too!
Besides all this there is a collection of online books that are accessible
during and after installation:

 1. Shortly before installation is complete (while files are being unpacked,
    icons are being created, and other first-time setup processes are going on
    in the background, as an early taste of multitasking) the user is presented
    with a basic OS/2 Tutorial, which explains how to use a mouse, identifies
    the objects on the OS/2 desktop, and other things a first-time GUI user
    would need to know about OS/2.
 2. After installation is complete a user will see three very important icons
    on the desktop:

    a. A green "bull's-eye" with the icon text "Start Here."  This continues
       the basic OS/2 education, and expands on it with a number of different
       topics,  including "Adding/Using Programs," "Customizing Your Desktop,"
       "Doing Everyday Tasks," "Installing Printers," and the like.  Ease of
       learning is enhanced with hypertext links to other related topics, and
       even links to a system glossary to help untangle all the acronyms and
       other jargon.
    b. After absorbing the Start Here information, the user still may be in
       need of more.  From there he should go to the green icon shaped like a
       book, with a white question mark on its cover.  This is the Master Help
       Index.  It is the place to go when you don't know where to start.  As
       the name implies, it is an index to all the online information available
       in the system.  By leafing through the notebook tabs (alphabetically,
       letter by letter) the user can find almost any topic by its description.
       If even this is not enough, there is a keyword search facility within
       the index (and indeed within all OS/2 online documentation) that allows
       any word to be located in all areas of the documentation, and presented
       in a "hit list" for the user's selection.
    c. Beyond the Master Help Index, there is another icon, which looks like a
       lower case "i" inside a blue circle.  That is the international symbol
       for information, and not surprisingly this is the Information folder.
       Inside the folder (opened by double-clicking on the icon) can be found
       the OS/2 Command Reference, the REXX Information manual, the system
       Glossary (mentioned earlier), and the OS/2 Tutorial (the same one that
       comes up during installation).  Between the Command Reference and the
       REXX manual there is more than a megabyte of information about all of
       the OS/2 system and REXX commands, CONFIG.SYS and AUTO-EXEC.BAT
       parameters, and related information, compiled into about 600K of binary
       data.  This is the same Command Reference that can be ordered in printed
       form using the card included in the OS/2 box.  Other online books, such
       as the Comm and Database Manager and LAN books supplied with OS/2
       Extended Services 1.0 and LAN Server 2.0, may also be installed here.
       In addition, the OS/2 Developer's Toolkit may be used by customers to
       write their own online books (like the PS/2 Assistant books I developed
       for dealer and customer use).  (See the related article on p. 9 of this
       issue for a description of what the PS/2 Assistant is, and how to get
       it.)  These books may be placed in the Information folder, or any other
       the user desires.
    d. One final, and very important source of information included with OS/2
       2.0 is a README file located inside the Information folder.  By
       double-clicking on the file icon, the OS/2 System Editor will start up
       and load this file.  It contains about 76K of information about
       application and hardware compatibility issues, work-arounds and
       limitations, as well as instructions on how to install or set up SVGA
       and SCSI adapters for use with 2.0.  This file has all the late-breaking
       information that wasn't ready in time for the printed documentation
       supplied in the OS/2 box.  It can be printed if a hard copy is needed
       (although the keyword search facility inside the System Editor makes
       searching electronically a simpler job than visually scanning 35 printed
       pages).

With all this information available to the user before, during, and after
installation, and with the 60 days of ree technical and defect support via 800#
(not to mention the OS/2 BBS), users should be well-supplied with the answers
they need to install and make productive use of OS/2 2.0.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.9. Recreating the OS/2 2.0 Command Prompts Folder ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman
(From The IBM Advisor, the technical newsletter for IBM dealers; 2Q 1992)

Recently the NSC received calls from several new OS/2 2.0 users who
accidentally deleted their Command Prompts folder and were asking how to
reinstall it, or create a new one (without it they had no way to start a DOS or
Windows command prompt, or start the full-screen Windows Desktop session).  I'm
not aware of any way to reinstall it, but rebuilding it is relatively simple:

 1. Go to the Templates folder inside the OS/2 System folder.  Find the Folders
    icon and drag/drop it on the  OS/2 System folder.  This creates a new
    folder there called Folder.  Hold down the Alt key and click on the folder
    icon with Mouse Button 1 (the left button for right handed users).  This
    allows you to change the icon name to Command Prompts.  Now double-click on
    the Command Prompts folder to open it.
 2. Find the Programs icon in the Templates folder and drag it to the new
    Command Prompts folder you just created.  Change the name of the icon (as
    we did in step 1) to DOS Window. Go into the settings for this new icon (by
    using Mouse Button 2, then selecting Open from the resulting pull-down
    menu, then Settings) and click on the Program "notebook" tab.  Where it
    asks for Path and file name just type an asterisk (*).  This tells OS/2
    that you want a command prompt.  Then click on the Session tab.  From there
    click on the DOS Window button, then double-click on the icon in the
    upper-left corner of the Settings window to close it and save the settings.
 3. Repeat this process three more times, to create a combination of DOS Full
    Screen, OS/2 Window, and OS/2 Full Screen sessions (with appropriate
    names).  Icon names can be changed either by using the Alt-Button 1 method,
    as above, or by clicking on the General tab in the settings.  Use whatever
    is more comfortable for you.
 4. Repeat the process one more time setting up an icon identical to the DOS
    Full Screen object, but with one additional step.  From the Session tab
    click on the DOS Settings button. Then find the setting called
    DOS_STARTUP_DRIVE.  Click on it to select it and type A: in the entry field
    that pops up in the upper-right corner of the window. Then press the Save
    button.  This will return you to the Session screen, where you can close
    the settings as before.  The last step is to name this icon DOS from Drive
    A.
 5. Finally, create another DOS Full Screen icon, but for the Path and file
    name type WINOS2.COM instead of the asterisk.  Then change the icon name to
    Win-OS/2 Full Screen.

That's all there is to it.  When you read all this it might sound complicated
or lengthy, but it actually should take less than five minutes from start to
finish.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.10. Setting Up 109-line Command Prompt Windows ΓöÇ Tip ΓòÉΓòÉΓòÉ

By Mark Chapman

| Although the default VIO window size is 25 lines, it is possible to set a
scroll-back buffer as large as 109 lines, using the MODE command, depending on
the video adapter used.  If you have an XGA Adapter, simply create a batch file
called 109.CMD, containing the following statement: MODE CO80,109.  A VGA or
8514/A user can specify up to 102 lines in similar fashion.

Executing this batch file from a windowed command prompt will allow you to
stretch the window past its usual 25-line limit.  The number of lines you will
actually be able to see on-screen will depend on the size of the font you have
selected in the VIO window, and the resolution of the display driver you are
using. A VGA system, with the font set to its smallest, can display
approximately 56 lines of text in the window.  An 8514/A user can see about 88
lines.  Use the scroll bar to see the remainder of the buffer.

To automate the procedure, you can add this capability to the "OS/2 Window"
icon.  To do this, open the Settings for the OS/2 Window and change the
Parameters field (under the Program notebook tab) to read:

/K d:\pathname\109.CMD
(In other words, just add the batch file name, and the path where it can be
found.  If the batch file is in the root directory, no path is necessary.)

Then close the Settings to save the changes.  Now, whenever you start up an
OS/2 Window, it will automatically open with a 102 or 109-line scroll-back
buffer.

Note:  The same can be done with the DOS Window icon, as well as the DOS and
OS/2 Full-Screen  icons, howver in these cases, the limit is a 50-line buffer,
not 102/109.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.7.11. Supported SCSI Adapters ΓöÇ Tip ΓòÉΓòÉΓòÉ

| Support for the following Adaptec and Future Domain SCSI Adapters is shipped
with OS/2 2.0. When any of the following adapters is installed in a PC its
presence is automatically detected, and the appropriate device support is
subsequently installed.  For reference, the names of the device drivers that
support each adapter are provided below:

SCSI Adapter                                 Driver Name
Adaptec AIC 6260                             AHA152X.ADD
Adaptec AHA 1510                             AHA152X.ADD
Adaptec AHA 1520/1522                        AHA152X.ADD
Adaptec AHA 1540/1542                        AHA154X.ADD
Adaptec AHA 1640                             AHA164X.ADD
Adaptec AHA 1740/1742/1744
 (In standard mode)                          AHA154X.ADD
 (In enhanced mode)                          AHA174X.ADD
Future Domain TMC-850/860/875/885            FD8XX.ADD
Future Domain TMC-1660/1670/1680             FD16-700.ADD
Future Domain MCS-600/700                    FD16-700.ADD
Future Domain TMC-850IBM                     FD850IBM.ADD

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

 1. Locate installation diskette #8, which contains the file DASDDRVS, and
    insert it in drive A:.
 2. Change directory (CD\) to the root directory of the startup drive (usually
    C:).
 3. Type: UNPACK A:DASDDRVS \OS2 /N:xxxxxxxx.ADD  (where xxxxxxx represents the
    driver name from the list, above)
 4. Add the following line to the CONFIG.SYS file:
 5.   BASEDEV=xxxxxxx.ADD
 6. Save CONFIG.SYS and reboot the system.

These are the only SCSI adapters expressly supported.  Many other SCSI adapters
will work using the default "interrupt 13" disk drive device driver,
IBMINT13.I13.

Note:  AMI Fast Disk, and Fast Disk II SCSI adapters are incorrectly recognized
as as Adaptec adaptec.  If you have one of these adapters installed, do the
following:

o At the final restart after the installation is complete, delete from
  CONFIG.SYS any lines containing: BASEDEV=AHA1xxxx.ADD (xxxx can be any
  characters).
o Ensure that the line: BASEDEV=IBMINT13.I13 appears in CONFIG.SYS, or add it
  if it does not.  Then save CONFIG.SYS.
o Reboot the system.

To return to the OS/2 2.x Tips header, double-click here.


ΓòÉΓòÉΓòÉ 6.8. PS/2 Assistant Tips ΓòÉΓòÉΓòÉ

This section contains helpful tips, how-to documents, and introductory pieces
on IBM OS/2 and related products.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

PS/2 Assistant Tips
Setting Up an OS/2 LAN Server to Share Online Books
X-Referencing PartnerLink Pricing with PS/2 Assistant P/Ns

To jump directly to the Tips & Techniques header, double-click with the mouse,
or use the Tab and Enter keys.


ΓòÉΓòÉΓòÉ 6.8.1. X-Referencing PartnerLink Pricing with PS/2 Assistant P/Ns ΓöÇ Tip ΓòÉΓòÉΓòÉ

Here's a tip for dealers using PartnerLink, who would like to be able to
cross-reference the part numbers and list prices in the PS/2 Assistant with the
dealer prices contained in PartnerLink.

Within PartnerLink, under the LIBrary, go into PRC.  Download the dealer price
schedule for ALL Products.  Then create a batch file called F.CMD, containing
the following statement:

FIND "%1" C:\PRICE.LST|MORE

(Assuming you named the downloaded price list PRICE.LST.)  From a command
prompt you can enter: F SOMETHING and it will search the file in a second or
two and pop up all occurances of SOMETHING.  (Make sure whatever you type is
all caps ).  For example, to find out the cost of an IBM Quickwriter Printer,
type: F QUICKWRITER.  It would then display the Part Number, Description,
Dealer Cost, Retail, and minimum order quantity.

This is an extremely fast and easy way to find pricing information.  The PS/2
Assistant helps you find a part number, then F.CMD provides the dealer cost.

To return to the PS/2 Assistant Tips header, double-click here.


ΓòÉΓòÉΓòÉ 7. Technical Qs & As ΓòÉΓòÉΓòÉ

The following are the answers to some marketing questions that the National
Support Center has received recently.  These are questions which have come up
frequently, and therefore appear to have applicability to a wide number of
people.  Additional Qs & As will be added over time.

To jump directly to the other sections of this document, use the mouse, or Tab
and Enter keys, to select the section to which you wish to jump, below:

Q&A Sections
AIX PS/2 Technical Qs & As
                                                  Applications Technical Qs & As
Networking Technical Qs & As                      IBM Printer Technical Qs & As
PS/2 Technical Qs & As                            OS/2 1.x Technical Qs & As
PS/1 Technical Qs & As                            OS/2 2.x Technical Qs & As
PS/2 Assistant Qs & As

To jump directly to the Technical Information header, double-click with the
mouse, or use the Tab and Enter keys.


═══ 7.1. AIX PS/2 Technical Qs & As ═══

Q.  How can I make a backup copy of the AIX PS/2 diskettes before I install
AIX, since DOS can't read the diskettes?
A.  Boot with the AIX PS/2 Boot Diskette option, and choose the Copy Diskette
option.  This will copy your diskettes and format the target diskettes as it
goes.  After completing the copy process you will be asked if you want to make
another copy.  Unlike DOS DISKCOPY, this means "Do you want another copy of the
same diskette?"  If you need only one copy, answer No.  AIX Access for DOS
Users, and X-Windows for DOS, diskettes will have to be copied by the DOS
DISKCOPY command, because they are DOS program diskettes.

Q.  How do I connect AIX PS/2 and Novell Netware?
A.  AIX and Novell will operate on the same physical network. However, with the
difference in communication protocols, they will not work together as a
seamless network.  To our knowledge, Novell supports TCP/IP and therefore will
allow AIX and Novell networks to communicate and transfer files.

Q.  What is the difference between TCP/IP for OS/2 Version 1.1 and TCP/IP for
OS/2 Version 1.2?
A.  TCP/IP for OS/2 V1.2 offers:
- X-Windows and NFS Server support
- X.25 support for IP
- NDIS support
- VT220 Emulation
- Support for OS/2 1.3 and 2.0

Q. Is AIX PS/2 1.2 supported on the PS/2 Models 90 and 95?
A.  No.  AIX 1.2 is not supported on these PS/2 models currently, but it is
expected they will be supported in the next release, later this year.

Q.  Is the internal tape drive supported under AIX PS/2 1.2?
A.  Yes.  AIX PS/2 support for the Internal Tape Backup Unit was released as
PTF 1008.

Q.  What is the best way for an OS/2 user in a LAN environment to communicate
with an AIX system?
A.  TCP/IP V1.1 for OS/2 is the solution offered by IBM to allow OS/2
workstations to communicate with the machines in the Unix world such as IBM
RT's and RISC/6000 units running AIX.  A good many of the Unix machines in use
utilize TCP/IP, allowing this to be a common communications platform among
machines provided by various vendors. TCP/IP V1.1 for OS/2 comes with many
TCP/IP standard applications such as NFS, FTP, TELNET, and a mail system.
Running under OS/2 Extended Edition V1.20, TCP/IP V1.1 can run on both Ethernet
and Token Ring networks, and even act as a TCP/IP router between Ethernet and
Token Ring.

To return to the Technical Qs & As header, double-click here.


═══ 7.2. Applications Technical Qs & As ═══

Q.  What is the difference between TCP/IP for OS/2 Version 1.1 and TCP/IP for
OS/2 Version 1.2?
A.  TCP/IP for OS/2 V1.2 offers:
- X-Windows and NFS Server support
- X.25 support for IP
- NDIS support
- VT220 Emulation
- Support for OS/2 1.3 and 2.0

Q.  Is IBM Current networkable?
A.  Current was designed as a single-workstation application.  As such the
current version (1.2) is not networkable.

Q.  Is there an HP LaserJet III driver for DisplayWrite 4?
A.  No, however there is in DisplayWrite 5.  Your options are either to upgrade
to DW5, or to use the HP LaserJet II driver under DW4 (which will work, but
will only support the features of the HPLJ II; not the additional capabilities
of the HPLJ III).

To return to the Technical Qs & As header, double-click here.


═══ 7.3. Networking Technical Qs & As ═══

The following sections contain Qs & As related to Networking.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Technical Qs & As header, double-click here.


═══ 7.3.1. Network Installation Qs & As ═══

Q.  Why do I not see the correct system level from my DOS LAN Requester
workstation after installing updates?
A.  The syslevel shows when doing NET START RDR on DOS LAN Requester machines:
- The level shows 4000 for 1.2, 1.3 and 1.30.1
- The level shows 5015 if you have WR05015 (which is slightly different than
the shrink-wrapped 1.30.1) installed
- DLR syslevel is pulled from the NETWORK.MSG file:
 -- the syslevel change in 5015 did not make it into the 1.30.1 Refresh
 -- the syslevel change did not make it into the DOS 5.0 Upgrade Package (shows
4000 if you install over 5015)
- Later CSDs show current version of CSD
- DOS 5.0 will work with Requesters at 5015 if they do not RIPL from a Server
- IC02963 patch from defect support is required to RIPL DOS 5.0 LAN Requesters
from a Server

Q.  Why is it that sometimes my DOS LAN Requester using DOS 5.0 is not able to
execute any EXE or COM files that are loaded from a PCLP DOS 5.0 server? The
DOS LAN Requester is at CSD level 5015 and the PCLP 1.34 system is at the
latest level of code.  The DLR system can access the 'Net Shared' resource, it
can perform a 'DIR' and even copy the file to the 'local' hard drive.  But,
when the DLR system attempts to run the EXE or COM file from the PCLP server a
DOS error, 'Cannot execute file [filename]' occurs.  Even when the resource is
setup through the OS/2 LAN Server and shared as an external resource the same
DOS error is returned.
A.  This is a known, but not frequent, situation.  The problem involves locking
executable files using the REDIR40.EXE file. There is a fix.  The fix is in the
form of a new REDIR40.EXE that can be obtained from IBM Software Defect
Support.  The ID for the fix is IC03020, it includes one file and is applied as
a replacement for the previous version of that file.

Q.  How do I find the 12 digit hexadecimal address of a Micro Channel
Token-Ring adapter?
A.  Boot to the system's Reference Diskette and go into Advanced Diagnostics
(CTL-A).  Run the diagnostic test on the Token-Ring adapter.  Detailed
information about the adapter, including its adapter address, will be
displayed.

Q.  How do I find the adapter address for my PC Network Broadband or PC Network
Baseband adapter?
A.  Boot to the Adapter Diagnostics diskette which comes with the PC Network
adapter.  Run the Transmit and Receive Test. When the test is complete, the
adapter's address will be displayed.

Q.  What version of NetWare from IBM is required to run NFS and FTAM?
A.  NFS and FTAM require Netware V3.11 (or later) from IBM.

Q.  I get "Insufficient Memory" errors when I try to install NetWare, but I
have plenty of memory in my system.
A.  If a memory driver has grabbed all of your memory above 1MB (as HIMEM.SYS
does) NetWare will not "see" the memory.  Remove any memory drivers from
CONFIG.SYS.  NetWare will the install correctly.

Q.  If I run a bridge over lines using V.35 protocol, do I need both the ARTIC
V.35 cable and a modem cable?
A.  No; just the V.35 cable (P/N 53F2648) from the ARTIC card to the modem.

Q.  Is there any way to use IBM Personal Communications/3270 and Novell IPX at
the same time?
A.  Yes.  Two rules apply, however: 1) PC/3270 must be loaded first; and 2)
Once PC/3270 is loaded, it must not be removed from memory.

Q.  Since installing the IBM Distributed Console Access Facility (DCAF) on my
OS/2 LAN Server, the LAN refuses to work.  It produces the following errors:
NET3056 OS/2 error 59, followed by SYS0059.
A.  Most likely the MAXIMUM NAMES parameter in your NETBIOS profile is
insufficient.  Try the following:

 1. Start the Comm manger.
 2. Choose "Advanced," "Configuration," "LAN Features profile," "Change,"
    "NETBIOS Profile."
 3. Then increase the MAXIMUM NAME (how many you need will vary from network to
    network, so you will have to experiment with the best number).
 4. Verify the changes and exit Comm Mgr.

The next time you reboot, the problem should be resolved.

Q.  We have a network with an OS/2 LAN Server system as the domain controller.
The users sometimes receive a message that they "cannot access home directory"
when attempting to log on to the domain.  This problem occurs intermittently on
various systems. Sometimes about ten systems will come up, while other times as
many as fourteen or fifteen will come up.  What's the problem.
A.  Most likely the MAXSHARES parameter in the server's \IBMLAN\IBMLAN.INI file
is still at the default of sixteen.  If so, you need to increase your MAXSHARES
and MAXCONNECTIONS parameters.  The MAXSHARES parameter must be equal to or
greater than the total number of aliases (files, printers, serial devices and
external resources) + home directories.  The equation for the MAXCONNECTIONS
parameter is: MAXCONNECTIONS = #requesters * (2 + #new uses per requester).

Q.  Is there any plan to put the PC LAN Program or the DOS LAN Requester
portion of OS/2 LAN Server 1.2 or 1.3 into extended or expanded memory?
A.  Portions of the DOS LAN Requester can be loaded into expanded or high
memory, but not the PCLP.  There are no current plans to do so with the PCLP.
For information on configuring your requester for EMS or high memory, refer to
the /EMS and /HIM parameters to the NET START command in your DOS LAN Requester
Users Guide.

Q.  Why do I get an "Incorrect DOS version" message when trying to install the
PC LAN Program V1.2 on a DOS 4.0 system?
A.  The PCLP V1.2 is not compatible with DOS 4.0.  If PCLP 1.2 is used, you
must be running under DOS 3.3. Alternatively, you can upgrade to PCLP 1.3 if
you wish to use DOS 4.0.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration & Setup Qs & As Qs & As           Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Networking Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.3.2. Network Configuration & Setup Qs & As ΓòÉΓòÉΓòÉ

Q.  How can I set up my OS/2 network requesters to automatically logon the
users?
A.  In each user's STARTUP.CMD file, add the following statements:
 NET START REQ     (to start the requester)
 LOGON xxx /P:yyy   (where XXX is the userid and yyy is the password)
If the requesters don't require passwords, leave out the /P: parameter
entirely.  If you want to force the users to input a password, use the /P:
parameter without including the password.

Q.  How do I enable the Windows-specific DOS LAN Requester files (specifically
NETPOP.EXE) with OS/2 LAN Server 1.3?
A.  First, copy the NETAPI.DLL, PMSPL.DLL, and NETPOPUP.EXE files to the DOSLAN
subdirectory.  Next, verify that you have the /POP, /API, and /NMS:1 parameters
in your DOSLAN.INI file, and have your network selection in Windows set to
LANMAN 2.0 Enhanced (or 100% compatible).  Then, make sure you start DLR logon
and issue all NET USEs before starting Windows.  Refer to the DOS LAN Requester
1.3/MS Windows 3.0 Installation and Configuration Guide, form number S33F-9436
for more information on running Windows 3.0 with DLR 1.3..

Q.  I'm running NetWare and ICLAS and trying to load the Private Tutor Series.
When I load PT it prompts me for a drive where the lesson is.  Each drive I
select gives me an error.
A.  Login as a student, press ALT then the letters E, S and C (not the ESC key)
and at the prompt type MAP.  Look for the drive mapped to courses.  It should
be drive Q.  That is the drive you need to enter for the lesson prompt.

Q.  I have an OS/2 LAN Server network running on Ethernet, and everything seems
to be set up correctly.  All the drivers load properly, but when I try to logon
with my DOS LAN Requester, I get an error message saying that the domain could
not be found.  Why?
A.  You need to change the protocol used by your LAN Server and any OS/2
requesters so that they use the 802.3 protocol. OS/2 uses a default of Ethernet
DIX Version 2.0.  The LAN Support Program on the DOS requesters uses IEEE 802.3
as the default.  This causes a mismatch of the two protocols.  To change this
you need to go into Communications Manager Advanced Configuration.  Choose LAN
Features Profile.  Then select 802.3 and Change.  When the screen that asks for
the protocol used by the adapter appears, choose 802.3 (the only other choice
will be Ethernet DIX Version 2.0).  Then exit (do not use ESC or you will lose
your changes), making sure that you verify the changed configuration file.  You
will need to Shutdown the system and reboot.

Q.  Why does my screen become trashed on some DOS LAN Requesters after
receiving a NETPOPUP Message and pressing ESC to clear the screen?
A.  This may have been a problem with the earlier IBM mouse driver V1.0. An
easy way to fix this is to make sure you load the mouse driver after the NET
START in your AUTOEXEC.BAT file.

Q.  Is the Token-Ring 16/4 Busmaster Server Adapter/A supported by OS/2 LAN
Server V1.2 or 1.3?
A.  OS/2 LAN Server 1.x does not support the new adapter.  IBM OS/2 LAN Server
2.0 does support this adapter.  In addition, the following other software
products also support the adapter:
   NetWare from IBM - IBM Corp.
   NetWare 386 V3.1 - Novell, Inc.
   Vines V4.0 - Banyan Systems, Inc.

Q.  How do I configure NetWare from IBM V3.11 to use the Token-Ring 16/4
Busmaster Server Adapter/A?
A.  First, make a directory on the DOS partition of the server's fixed disk
drive) or on the boot diskette for a server with no DOS partition) called
\FIRMLOAD.  Next, copy the FIRMLOAD.COM file from the SYSTEM-2 diskette into
the \FIRMLOAD directory and copy MONT400.BIN and WRTRAM.BIN from the options
diskette that comes with the Busmaster adapter into the same directory.  Create
the following AUTOEXEC.BAT file, which when executed will cause the microcode
to be downloaded to the Busmaster adapter and the start the NetWare server:
   CD\FIRMLOAD
   FIRMLOAD
   CD\
   SERVER
In addition, TOKENDMA.LAN, which is found on the SYSTEM-2 diskette, should be
used as the network driver loaded by NetWare.

Q.  I keep setting the time on my PC, and every morning when I turn it on it is
off by one hour.  I can't figure out why.
A.  If your PC is on a network, check the time on the server.  If the server is
off (perhaps because of Daylight Savings Time), and your system synchronizes
its time to that of the server, it will reset it incorrectly each morning,
despite the changes you make.

Q.  I have a network with twenty DOS workstations and an OS/2 LAN Server V1.0
system functioning as my domain controller.  I was able to define all of my DOS
users, and all are able to log on.  However I am not able to log on more than
eight DOS users at one time.  Why?
A.  The OS/2 LAN Server V1.0 defaults to allowing only eight DOS users to log
on.  There are a number of parameters that need to be changed in several of the
LAN Server configuration files to allow more DOS users to log on.  These
parameters will be different from LAN to LAN, so the best thing to do is to
refer to the Planning, Installation and Customization Guide for OS/2 LAN Server
1.0 (Pub. Number GG24-3402). A similar manual for PC LAN Program V1.3 is
GG24-3267.

Q.  Our OS/2 Requesters are timing out due to inactivity.  How can we change it
to never time out?
A.  There is a parameter in the LAN Server's IBMLAN.INI file called
'AUTODISCONNECT=.'  If you set this value to -1, the server will never
disconnect inactive sessions.  Please refer to Appendix A of your OS/2 LAN
Server Network Administrator's Reference for information on all the IBMLAN.INI
parameters.

Q.  What are the distance limitations for Token-Ring networks?
A.  The maximum distance a Token-Ring network can span depends on several
variables:

o The number of MAUs
o The number of wiring closets
o The type of cabling
o The data rate

Because each network has a unique combination of these variables, there is no
single answer to this question.  But the Token- Ring Introduction and Planning
Guide (Publication Number GA27-3677) includes charts that will help pinpoint
the answer for your specific installation.

Q.  While configuring an OS/2 LAN Server 1.2 network, I was trying to determine
the numreqbuf based on the formula in the OS/2 LAN Server Network
Administrator's Guide, but it is incomplete.  What is the correct formula?
A.  The correct formula can be found in the OS/2 LAN Server 1.2 Planning,
Installation, and Customization Guide (Pub. No. GG24-3506).  It is as follows:
numreqbuf=65536 / (sizereqbuf + 260) x 8.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Networking Qs & As header, double-click here.


═══ 7.3.3. Network Printing Qs & As ═══

Q.  On an OS/2 LAN Server V1.2 output can be directed to one queue serviced by
a PostScript printer driver, or to a different queue for Non-PostScript output,
and a 4216 Personal Pageprinter's mode will be switched when the appropriate
queue is activated.  Since DOS requires special software to accomplish this
switch, how does OS/2 manage it? And if a DOS PCLP node wishes to go through
the print server to do the same, how is this accomplished?
A.  In the 4216 Model 031, the print mode switching is done internally.  No
special software is needed.  The OS/2 method of harnessing the 4216-031
separates print job routing into two queues to make sure the data stream is
formatted properly by the OS/2 printer driver.  The OS/2 driver "tells" the
4216 what format the data stream is in and it "switches" itself to that mode.
To do this under the PC LAN Program, follow OS/2s method and define two aliases
for users to associate with their applications: one for PostScript, and the
other for Proprinter (non-PostScript) emulation.  Newer printers, such as the
IBM 4019 and 4029 LaserPrinters, provide their own Automatic Emulation
Switching (AES) software, for both DOS and OS/2.

Q.  When I print from a workstation to an OS/2 server, my jobs appear in the
queue, but never print.  If I try to print from the server, it may or may not
print.  What's the problem?
A.  Go into the Print Manager on the server.  choose SETUP for QUEUES. Choose
the desired queue and CHANGE.  The NETWORK OPTIONS should read: NETWORK
OPTIONS: DRIVER="XXXXXXXXX" (where the X's represent the name of the driver
loaded for the queue)  Everything must be in capital letters. Reboot the server
after saving this change.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Networking Qs & As header, double-click here.


═══ 7.3.4. PS/2 Model 55 LS Qs & As ═══

Q.  Does the PS/2 Model 55 LS (LAN Station) come with a Reference Diskette?
A.  No, because the 55 LS is a diskless workstation, so there would be no place
to insert the diskette.  A disk image must be created on the server and
downloaded to the 55 LS; therefore only one Reference Diskette is needed per
network (not one per 55 LS).  A separate package may be ordered for the 55 LS
to obtain the necessary Reference Diskette and Option Diskette for the specific
model of 55 LS.  For the 55-LT0, order P/N 15F2230 for the Token-Ring
Information Guide, and PS/2 Model 55/65 Reference Diskette and 16/4 Token Ring
Network Adapter/A Option Diskette.  For the 55-LE0, order 15F2232 for the
equivalent Ethernet materials.  Alternately, Business Partners registered as
Technical Advisors may download these diskettes from the IBM Technical Advisor
BBS.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Networking Qs & As header, double-click here.


═══ 7.3.5. ICLAS/EDLAN Qs & As ═══

Q. None of the print jobs will print until the user exits from the application
program.  What's wrong?
A. The timeout is not set correctly.  Choose NetWare Utilities from the Sysop
menu, then choose System Configuration, Supervisor Options, and System Login
Script. On the line that begins with #spool, change the timeout to timeout=5,
or some other number.  If you have it set to 0, the timeout feature is disabled
and nothing will print until you exit.  If you change the value to a nonzero
number the print spooler will wait that number of seconds before releasing the
print job.  If this value already is nonzero, check the application's start
instructions to see if a spool or capture command is used; if so make changes
to the timeout there.

Q. I'm trying to create a printstation in ICLAS V1.4 and get an error message,
"Another user is making printstations at this time.  Printstations can only be
created on one workstation at a time." But I'm the only one doing so.
A.  When you are creating a printstation, there is a file called UNLOCKED that
is renamed LOCKED.  Look in the LOGIN\LANSPOOL subdirectory.  If you see a file
called LOCKED, rename it to UNLOCKED.  If both files exist, delete LOCKED.

Q.  I'm running NetWare and ICLAS and trying to load the Private Tutor Series.
When I load PT it prompts me for a drive where the lesson is.  Each drive I
select gives me an error.
A.  Login as a student, press ALT then E, S, C (the letters, not the ESC key)
and at the prompt type MAP.  Look for the drive mapped to courses.  It should
be drive Q.  That is the drive you need to enter for the lesson prompt.

Q.  When using a banner page, the first user of the day prints fine.  Every
user after that gets a banner page with the name of the first user.
A.  There is a known problem with the Novell capture file.  Download CAP121.ZIP
from NetWire, or order it from IBM Defect Support.

Q.  I am trying to run the tape backup program from the SysOp main menu and
don't have the correct batch file.
A.  For ICLAS 1.4 you will need to apply the patch INTTAPE4, which is available
from your Education SE, or the TA BBS.  For ICLAS 1.2 or 1.3, use INTTAPE2.

Q.  The printer attached to the server won't print.  The print jobs never
appear in the queue.
A.  1) If it is Novell 2.15 or 2.12, check to see if there is an AUTOEXEC.BAT
file in the \SYSTEM subdirectory.  If it exists, delete it.  2)  Go into
PCONSOLE and choose Print Queue Information, then Currently Attached Servers.
If it is blank, choose Queue Server, insert, and choose SERVERNAME_ls_vap.
Exit PCONSOLE and down the server.  When you reboot the server, make sure you
answer Yes to Loading the vaps.

Q.  I am getting an error message, "VAP not able to login as printstation."
A.  Some files have become corrupted.  Go to the subdirectory LOGIN\AUTOLOG for
ICLAS 1.3 and earlier versions.  For ICLAS 1.4, it is in the AUTOLOG2
subdirectory.  Delete the file clswsdef that has no extension.  Go to the
LOGIN\LANSPOOL subdirectory and delete the lanspool.ini file.  Go into PCONSOLE
and choose Print Queue Information and delete all the ls_print_queues, leaving
only printq_0 and printq_1.  Down the server, bring it back up and reinstall
ICLAS from diskettes (see installation manual for information) and down the
server again.  After bringing up the server, this message should not reappear.

Q.  I am trying to install Edlan but I'm getting the message, "In order to
install Advanced Netware, you must perform the following steps:
A.  This indicates that you probably do not have enough memory.  Edlan requires
a minimum of 4MB to install and run.

Q.  I am installing Edlan 1.0 or 1.01 and can't get it to work on the Model
90/95.
A.  The Models 90 and 95 require the latest SCSI drivers, which were not
included on the Edlan tape.  You will need to install NetWare from diskette on
the Models 90 and 95 after you get the latest SCSI drivers and copy them onto
the DSK_DRV_001 diskette.  You can then install ICLAS and the tools from the
tape.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As                                ICLAS/EDLAN Qs & As

To return to the Networking Qs & As header, double-click here.


═══ 7.3.6. Miscellaneous Network Qs & As ═══

Q.  When I issue a NET WHO at my domain controller, I often get some users
whose systems are off, and who are not listed in NET SESSION.  Why?
A.  This problem is caused by the users shutting down their systems without
logging off.  Have them log off first and this problem will go away.

Q.  What is the difference between TCP/IP for OS/2 Version 1.1 and TCP/IP for
OS/2 Version 1.2?
A.  TCP/IP for OS/2 V1.2 offers:
- X-Windows and NFS Server support
- X.25 support for IP
- NDIS support
- VT220 Emulation
- Support for OS/2 1.3 and 2.0

Q.  Which Remote Program Load (RPL) chip do I need for my Token-Ring adapter?
A.  The 24-pin RPL chip (P/N 83X7839) is used for the original Token-Ring
Adapter, and Token-Ring Adapter II.  The 28-pin RPL chip (25F8887) is for the
Token-Ring Adapter/A, Token-Ring 16/4 Adapter, and Token-Ring 16/4 Adapter/A.

Q.  What is the Home Directory?
A.  The Home Directory refers to the hard disk space on the server that has
been allocated strictly for that user's applications and needs.  This disk
space can be used for both application and data storage.  The Home Directory is
the default area of access to the user for his session, and additional access
depends upon the user's profile as configured by the system administrator.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Network Installation Qs & As
                                                        PS/2 Model 55 LS Qs & As
Network Configuration Qs & As Qs & As                   Miscellaneous Qs & As
Network Printing Qs & As

To return to the Networking Qs & As header, double-click here.


═══ 7.4. IBM Printer Technical Qs & As ═══

The following sections contain Qs & As related to IBM printers and options.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
4019 LaserPrinter Qs & As
4029 LaserPrinter Qs & As

To return to the Technical Qs & As header, double-click here.


═══ 7.4.1. IBM 4019 LaserPrinter Technical Qs & As ═══

Q.  What are the duty cycles of the 4019 and 4019E printers?
A.  The 4019/4019E printers are rated at 12,000 and 20,000 pages per month,
respectively.

Q.  What is the expected life of the print (toner) cartridge?
A.  The average life expectancy of the print unit is 10,000 pages, based on
2.8% coverage of the page (typical of a business letter).

Q.  Manually switching the IBM 4019 Laser Printer between PostScript, HP, ASCII
and Plotter modes via the control panel is awkward.  Is there an Automatic
Emulation Switching (AES) program available for the 4019, as there is for the
IBM 4216?
A.  IBM recently announced an enhanced PostScript hardware option for the 4019
(P/N 1424017, replacing 1058237) that includes a hardware implementation of AES
with software drivers.  This is the basic 17-font PS option.  The additional PS
22-font card (1038100) remains the same.  (The new 39-font Premium package,
1424039, includes both the basic PS AES option with AES, and the 22-font card.)
While there is a separate AES software product called the 4019 Supplemental
Utilities (P/N 1424000), it requires a PostScript to work.  It is only offered
as a separate option as a replacement copy, if needed.

Q.  Is the 4019 Laser Printer Sharing Option (P/N 1038958) an intelligent
device?
A.  No. There is no built-in microprocessor or memory.  The Sharing Option uses
a spooler program running in the memory of the attached computers to
temporarily store print jobs if the printer is not ready for them.  This allows
the user to continue working without having to wait for the printer to become
available for their print job.

Q.  What cables are needed to set up the Printer Sharing Option?
A.  A standard parallel printer cable (P/N 1525612) is used to connect the 4019
to the Sharing Option.  The Sharing Option is connected to the system units by
serial cables. Two sizes are available, 20 ft. (8509386) and 50 ft. (1038693).
For customers with standard serial cables, a special connector (1319143) may be
used to convert it to the correct type.

Q.  Can a 4019 LaserPrinter be used serially?
A.  Yes.  To attach serially, use the special 25-pin D-Shell to 34-pin
Centronics interface conversion cable, P/N 6486685. No other hardware is
needed.

Q.  If a program doesn't offer a specific 4019 driver, what others can I use?
A.  In PostScript mode, use the Generic PS (PSCRIPT.DRV) driver.  In ASCII
(PPDS) emulation mode, use either the IBM Quietwriter III (5202) driver, or an
IBM Proprinter (42xx) driver. In HP mode, use the HP LaserJet II driver.  In
plotter mode, use an IBM 7372, or an HP 7475A driver.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
4019 LaserPrinter Qs & As
4029 LaserPrinter Qs & As

To return to the IBM Printers Technical Qs & As header, double-click here.


═══ 7.4.2. IBM 4029 LaserPrinter Technical Qs & As ═══

Q.  What models of the IBM 4029 LaserPrinter were recently annnounced, and are
any upgradeable?
A.  Four models were announced: The Model 5E (5ppm), P/N 4029010; the Model 6
(6ppm), 4029020; the Model 10 (10ppm), 4029030; and the Model 10L (10ppm, 700
sheet input, 250 sheet output), 4029040.  The Model 6 is upgradeable to the
Model 10.

Q.  What is the maximum resolution of the 4029 LaserPrinter?
A.  Out-of-the-box the maximum resolution is 300x300 dpi; however if the
PostScript option and at least another 4MB of printer memory is installed in
the Models 6, 10, and 10L, the printers are capable of 600x600 resolution
PostScript printing. The Model 5E is limited to 300 dpi, even with the PS
option and the extra memory.

Q.  What is the standard and maximum memory in the 4029 LaserPrinter?
A.  All 4029 models come with 1MB standard, and support up to 9MB total, using
two special memory SIMM sockets.  1MB, 2MB, and 4MB SIMMs are available for
upgrading beyond the first 1MB.

Q.  What emulation modes are standard and optional in the 4029 LaserPrinter?
A.  All 4029 models include IBM Personal Printer Data Stream (PPDS, or ASCII),
HP LaserJet Series II (PCL4), and HP Plotter (HPGL) emulation modes, standard.
In addition, HP LaserJet Series III (PCL5) and PostScript options can be added.

Q.  Can both the PCL5 and the PS options be added to a 4029 LaserPrinter?
A.  The Models 6, 10 and 10L have two option connectors, allowing both options
to be attached concurrently, and providing all five printer modes at all times
(ASCII, HPGL, PCL4, PCL5, and PS).  They are complementary, not mutually
exclusive.  The Model 5E, because it only has one option connector, can only
hold either the PCL5 or PS option, but not both.  This still provides four
printer modes in a low-cost, high-quality laser printer.

Q.  What is the 4029 "100 Sheet Auxiliary Feeder" and why would I use it?
A.  The auxiliary feeder is attached in place of the envelope feeder, and
provides a second or third input paper source (in addition to the standard 200
sheet drawer and optional 500 sheet drawer). It can be freely interchanged with
the envelope feeder, but cannot be used concurrently.

Q.  Why do the 1MB and 2MB memory kits for the 4029 have different part numbers
and prices than the kits for the 4019 printer models?
A.  While the 4019 printers use special memory daughtercards, the 4029 models
use SIMMs.  This makes installation simpler, leaves room for two upgrades (as
opposed to one, in the 4019s), and costs less for the equivalent amount of
memory.

Q.  Can I use standard DRAM SIMMs in the 4029?
A.  The SIMMs used in the 4029 are NOT standard SIMMs, but were designed
especially for the 4029.  Standard SIMMs will not work.

Q.  Can a 4029 LaserPrinter be used serially?
A.  Yes.  To attach serially, use the special 25-pin D-Shell to 34-pin
Centronics interface conversion cable, P/N 6486685. No other hardware is
needed.

Q.  If a program doesn't offer a specific 4029 driver, what others can I use?
A.  If available, in PostScript mode, use an IBM 4019 LaserPrinter driver.  In
ASCII (PPDS) emulation mode, use either the IBM 4019, the IBM Quietwriter III
(5202), or an IBM Proprinter (42xx) driver, in order of preference. In HP mode,
use the HP LaserJet III driver.  In plotter mode, use an IBM 7372, or an HP
7475A driver.

Q.  Is there an OS/2 1.3 driver for the IBM 4029 LaserPrinter?
A.  Yes, but the system must be at CSD level 5050 or higher (V1.30.2).  Make
sure that you have the PSCRIPT.DRV driver installed before applying the 5050
CSD; this will make sure the new PostScript driver, which includes the 4029
drivers) is installed.  Installing the shrink-wrapped 1.30.2 package will have
the same effect; just make sure to install the PSCRIPT.DRV driver.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
4019 LaserPrinter Qs & As
4029 LaserPrinter Qs & As

To return to the IBM Printers Technical Qs & As header, double-click here.


═══ 7.5. PS/1 Systems Technical Qs & As ═══

Q.  What is so great about the new PS/1 models?
A.  There are two models, the B82 and the C42.  Each comes with a 16MHz 386SX
processor, 2MB of memory (upgradeable to 6MB without using an adapter slot),
and either a 40MB (C42) or 80MB (B82) fixed disk drive.  This is in contrast to
the 10MHz 286-based models earlier with either 512K of memory and no fixed disk
drive, or 1MB of RAM and a 30MB drive. In addition, the B82 model contains two
11" AT-style adapter slots that are compatible with network and emulation
adapters, and many other PC-compatible adapters.  The B82 also adds Microsoft
Windows 3.0 and Microsoft Productivity Pack for Windows software in addition to
all the other software included with the other PS/1 models.  A PS/1 model is
planned for Spring 1992 that will include 32-bit OS/2 2.0 pre-installed.

Q.  Can I add the 3-slot Adapter Card Unit to the PS/1 model B82?
A.  No.  It already includes two slots inside the system unit, and has no way
to connect the external Adapter Card Unit.

To return to the Technical Qs & As header, double-click here.


═══ 7.6. PS/2 Systems Technical Qs & As ═══

The following sections contain Qs & As related to PS/2 systems and options.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the Technical Qs & As header, double-click here.


═══ 7.6.1. Model 30/30-286 Qs & As ═══

Q.  Can the 45MB fixed disk drive announced for the PS/2 Model 30-E41 be
installed in older Model 25s and 30s (either the 8086 or 286-based models)?
A.  The Model 30-E41 BIOS adds support for the new drive type 37, first used in
the E41.  Older Model 25s and 30s do not support a drive type 37.

Q.  Can a 20MB or 30MB fixed disk option be installed in a Model 30-002?
A.  The Model 30-002 was sold with two diskette drives, and never intended to
have a fixed disk drive.  But later models incorporated a revised BIOS that
does support fixed disk drives.  If the user is willing to replace the second
diskette drive with a 20MB or 30MB IBM fixed disk drive (the ones supported by
the 30-001), and if the system's serial number falls between 55A0001-55Z9999,
or 7000000-7499999, the drive can be installed and will work.

Q.  When does the configuration program need to be run on the Model 30-286?
A.  Automatic Configuration needs to be run any time any of the following are
added or removed:  memory, diskette drive, fixed disk, or math coprocessor.
Change Configuration would have to be run if the address of the parallel port
is changed, or the serial and/or parallel port needs to be disabled.

Q.  Why don't I see the Token-Ring adapter show up in the configuration program
on the Model 30-286?
A.  The configuration program on the 30-286 does not need to be run when
adapters are installed (unless it is an extended memory adapter - see above
explanation.) Therefore, no adapters will be visible when the View
Configuration option is executed.  The appropriate diagnostic routines need to
be run if a suspected problem is encountered with an adapter.

Q.  Why can't I get the PS/2 Model 30-286 to recognize expanded memory?  When I
load the DOS 4.0 Expanded memory drivers I get error messages.
A.  The 30-286 does not support expanded memory via the DOS 4.0 drivers.
Either the All Chargecard or AboveDisc software must be used to achieve
expanded memory.  Neither option is currently marketed by IBM, but are
available from their respective vendors (All, Inc. and Above Software (formerly
TeleWare West), respectively).

Q.  How can I attach the 1.2MB external 5.25" diskette drive (4869002) to a
PS/2 Model 30 286?
A.  The 1.2MB diskette drive requires a 1.2MB adapter, and the only one
currently available is a Micro Channel adapter. Therefore the 1.2MB drive can
only be used on PS/2 Model 50 or higher.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.2. Model 35 Qs & As ═══

Q.  What parameters do I need to use to format a 1.44MB diskette to 1.44MB in a
2.88MB drive?
A.  Because the 2.88MB drive is media-sensing, no special parameters are needed
with the FORMAT command.  Simply typing FORMAT A: (or whatever drive letter is
appropriate for that drive) will format a 720K or 1.44MB diskette to the
appropriate capacity, barring a hardware problem.

Q.  I tried to format a 1.44MB diskette to 1.44MB capacity in a 2.88MB drive,
using FORMAT A:, but I get "sector not found" errors.  The same diskette works
in a 1.44MB drive.  What's the problem?
A.  If a 1.44MB diskette was previously formatted to 720K, or vice-versa, it
may fail when attempting to format it to the "correct" capacity in the future.
Try formatting it to 1.44MB on a 1.44MB drive.  Then, if successful, try
formatting it to 1.44MB again on the 2.88MB drive.  It may work this time.  If
not, do not use it on a 2.88MB drive.

Q.  What happens if I use selectable boot and make my system not see my 1.44,
A: drive?
A.  There is a "safety" device that always looks at the A: drive for a
Reference Diskette.  If there is a Reference Diskette in the drive it will
override "selectable boot".

Q.  When I try to install OS/2 1.3 on a PS/2 Model 35, 40, or 57, the system
won't even install.  What's wrong?
A.  Those systems require OS/2 1.30.1 (CSD 5015) or higher, and will not boot
from earlier versions.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.3. Model 40 Qs & As ═══

Q.  What parameters do I need to use to format a 1.44MB diskette to 1.44MB in a
2.88MB drive?
A.  Because the 2.88MB drive is media-sensing, no special parameters are needed
with the FORMAT command.  Simply typing FORMAT A: (or whatever drive letter is
appropriate for that drive) will format a 720K or 1.44MB diskette to the
appropriate capacity, barring a hardware problem.

Q.  I tried to format a 1.44MB diskette to 1.44MB capacity in a 2.88MB drive,
using FORMAT A:, but I get "sector not found" errors.  The same diskette works
in a 1.44MB drive.  What's the problem?
A.  If a 1.44MB diskette was previously formatted to 720K, or vice-versa, it
may fail when attempting to format it to the "correct" capacity in the future.
Try formatting it to 1.44MB on a 1.44MB drive.  Then, if successful, try
formatting it to 1.44MB again on the 2.88MB drive.  It may work this time.  If
not, do not use it on a 2.88MB drive.

Q.  What happens if I use selectable boot and make my system not see my 1.44,
A: drive?
A.  There is a "safety" device that always looks at the A: drive for a
Reference Diskette.  If there is a Reference Diskette in the drive it will
override "selectable boot".

Q.  When I try to install OS/2 1.3 on a PS/2 Model 35, 40, or 57, the system
won't even install.  What's wrong?
A.  Those systems require OS/2 1.30.1 (CSD 5015) or higher, and will not boot
from earlier versions.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.4. Model L40 Qs & As ═══

Q.  Does the L40SX Quick Charger perform a deep discharge on a battery before
recharging it?
A.  No.  There is no deep discharge function built into the Quick charger.

Q.  Is there any way to attach a LAN or terminal emulation adapter to the
L40SX?
A.  The PS/2 Communication Cartridge I is an A/C-powered external expansion
cabinet that can take one half-length adapter.  It is intended for use with
network or terminal emulation adapters (such as 3270 and 5250). At 7.1 x 3.4 x
5.7 inches, and 2.6 lbs., it is small and light enough to be taken on the road
with the laptop.

Q.  Despite having the A/C adapter plugged into the L40, the battery icons
indicate that the battery is still being drained.  I checked that the A/C
adapter is plugged into both the wall and the L40.  Do I have a bad battery?
A.  It is possible, but before replacing it, there is a third connection to
double-check: the plug from the L40 to the A/C adapter.  It may have worked its
way loose.

Q.  What is the syntax of the FAX command to use the L40 Fax/Modem?
A.  The FAX command must be followed by a file name and phone number to dial.
There is no "front end" to the program; it is strictly command line driven.
The file transmitted must be straight ASCII or a PCX graphics file.  You may
use a plus (+) sign between files to send them contiguously, without page
breaks between (for example, a business letterhead followed by the letter) or
just one name after another to send them as separate pages.  The phone number
uses the standard Hayes (AT) modem command set.

Q.  What's the minimum OS/2 version required for the L40?
A.  OS/2 SE or EE V1.30.1 is the minimum requirement for the L40.

Q.  What problems might I encounter if I use ship-level OS/2 1.3 on the L40
(until the 1.30.1 update arrives)?
A.  The 1.30.1 update fixes problems in several areas: 1) Random read/write
errors on the diskette drive, 2) the inability to print, and 3) the inability
to display the "key" symbol for the Power-On Password feature.  In addition,
the update supplies a new driver to enable the Trackpoint to work as a
trackball.  The PS/2 Mouse driver will only support the Trackpoint as a mouse.

Q.  What's the difference between the 1.30.1 "update" and CSD 5015?
A.  There is no difference except packaging and the ordering method.  1.30.1 is
now being shipped in the same shrink-wrap packaging as 1.30 was (it has a
bright orange sticker on the package identifying the new level), as well as
being orderable through the 800# above, for L40 users.  CSD 5015 (either
WR05015 for EE, or XR05015 for SE) is obtainable through the normal CSD
process.  It can be used to upgrade the ship-level 1.30 version (XR00000 for
SE, or WR05000 for EE) to 1.30.1.

Q.  I can't get an external monitor to work off the PS/2 Model L40 VGA port;
the monitor is blank. What's wrong?
A.  To use the external VGA port, you must first use the setup program to
change the display type from LCD to CRT. Once this is done, the video signal
will be rerouted to the external monitor.

Q.  When I attach an external monitor or projection device to the PS/2 Model
L40 VGA port, the LCD goes blank.  Is there any way to have both displays
working simultaneously (for doing demonstrations to large audiences)?
A.  Only one display can be used at a time; either the built-in LCD, or an
external monitor or projection device.  However, some devices that convert VGA
output to "standard" analog RGB output for video projectors have video cables
with "piggyback" VGA connectors, so that a monitor can connect to the back of
the plug that goes into the VGA port.  In this manner, the demonstrator has an
external monitor to look at, while the audience sees the projection screen.
(One such conversion box is called the Extron 109, manufactured by Covid
Electronics.  Other such products may also exist; this is not meant as an
endorsement of this particular vendor or product; merely an example.)

Q.  If I don't mind a reduced battery life, is it possible to use normal
"high-power" SIMMs in the L40 SX, instead of the expensive low-power CMOS
SIMMs?
A.  Because of the possibility of damage to the SIMMS, the L40 system board, or
both, the L40 SIMM sockets are "keyed" differently than normal SIMM sockets.
Thus, SIMMs not designed for the L40 are physically incapable of being inserted
in the L40.

Q.  What fax software can I use with the PS/2 Model L40 Fax/Modem option?
A.  No special software is needed.  The Fax/Modem option includes a program
that provides basic Send/Receive, View, Print, and Set Options features.  The
software will accept ASCII, PCX, TIFF, or fax file formats for transmission.

Q.  After receiving a Fax on a PS/2 Model L40, is there any way to manipulate
or edit the Fax image?
A.  Yes.  Using the software included, first view the image with the command:
FAX VIEW filename.FAX, and clip out the portion of the Fax you wish to keep.
Then save the resulting image.  The file will be saved in a PCX format, which
is compatible with many popular image and graphics programs, and may be further
edited by those programs.

Q.  If I have the Fax/Modem installed in a PS/2 Model L40, with the speed
turned down to 5 or 10MHz, will this affect the performance or accuracy of the
Fax input/output?
A.  The Fax/Modem is not supported at 5MHz; and for best results in a
multitasking environment, such as in the OS/2 DOS box, or under Windows, the
20MHz speed should be used.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.5. Model N51 Qs & As ═══

Q. How does a Model N51SLC notebook (using the IBM 386SLC processor) compare to
other 16MHz 386SX notebook systems?
A. The 16MHz 386SLC processor used in N51SLC is the only one to use an internal
8K cache.  All other notebooks use the standard Intel 16MHz 386SX processor.
By comparison, the internal cache makes the Models N51SLC as much as 80% faster
than competitive 16MHz 386SX systems (or the N51SX), and even equivalent to
25MHz 386SL notebooks!

Q.  What's the minimum OS/2 version required for the N51 notebook?
A.  OS/2 SE or EE V1.30.1 is the minimum requirement for the N51SX; the N51SLC
requires V1.30.2.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.6. PS/2 Model 55 LS Qs & As ═══

Q.  Does the PS/2 Model 55 LS (LAN Station) come with a Reference Diskette?
A.  No, because the 55 LS is a diskless workstation, so there would be no place
to insert the diskette.  A disk image must be created on the server and
downloaded to the 55 LS; therefore only one Reference Diskette is needed per
network (not one per 55 LS).  A separate package may be ordered for the 55 LS
to obtain the necessary Reference Diskette and Option Diskette for the specific
model of 55 LS.  For the 55-LT0, order P/N 15F2230 for the Token-Ring
Information Guide, and PS/2 Model 55/65 Reference Diskette and 16/4 Token Ring
Network Adapter/A Option Diskette.  For the 55-LE0, order 15F2232 for the
equivalent Ethernet materials.  Alternately, Business Partners registered as
Technical Advisors may download these diskettes from the IBM Technical Advisor
BBS.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.7. Model 56/57 Qs & As ═══

Q.  Is it possible to boot to an internal 5.25 drive in a 57/90/95?
A.  Yes. With our new systems you have the option to use "selectable boot" from
the Reference Diskette to select what drive you would like to boot from.
Caution:  If you use this your logical drive letters may change.

Q.  What parameters do I need to use to format a 1.44MB diskette to 1.44MB in a
2.88MB drive?
A.  Because the 2.88MB drive is media-sensing, no special parameters are needed
with the FORMAT command.  Simply typing FORMAT A: (or whatever drive letter is
appropriate for that drive) will format a 720K or 1.44MB diskette to the
appropriate capacity, barring a hardware problem.

Q.  I tried to format a 1.44MB diskette to 1.44MB capacity in a 2.88MB drive,
using FORMAT A:, but I get "sector not found" errors.  The same diskette works
in a 1.44MB drive.  What's the problem?
A.  If a 1.44MB diskette was previously formatted to 720K, or vice-versa, it
may fail when attempting to format it to the "correct" capacity in the future.
Try formatting it to 1.44MB on a 1.44MB drive.  Then, if successful, try
formatting it to 1.44MB again on the 2.88MB drive.  It may work this time.  If
not, do not use it on a 2.88MB drive.

Q. What exactly is the "PS/2 Cached Processor Option" for the Models 56SX/57SX?
A. It consists of a card that plugs into the 387SX math coprocessor socket of a
Model 56 or 57 system board.  This card contains an IBM-developed derivative of
the Intel 386SX chip, called the 386SLC.  This processor, while running at the
same 20MHz speed as the 386SX, performs as much as 88% faster than the
equivalent speed 386SX chip, due to an internal 8K processor cache.  This is
similar in concept to the internal cache in the Intel 486 processor.  This card
supersedes the built-in 386SX chip and takes over control of the system.  If
the user needs a math coprocessor, once can be installed in the 387SX socket on
the PS/2 Cached Processor Option.

Q. Does the original 386SX chip need to be returned to IBM when the PS/2 Cached
Processor Option is installed?
A. No.  Both processors (old and new) remain the the system (the 386SX is
soldered to the Model 57 motherboard).

Q. In what other systems can I use the PS/2 Cached Processor Option, besides
the Models 56 and 57?
A. None, at this time.  Not only do the 56/57 systems contain BIOS enhancements
to support the Option, but there are specific hardware changes required to
support it. Currently no other IBM or non-IBM systems have these necessary
enhancements.  The PS/2 Ultimedia Model M57 SLC, designed for the multimedia
market, is essentially a standard Model 57SX, with the 386SLC processor built
in, and various multimedia-related options installed (see below for more
details).

Q. What's the practical difference between buying a standard Model 56SX/57SX
and adding the Cached Processor Option, versus buying a 56SLC/57SLC outright?
A. Ultimately, none.  Starting with the SX models allows you to keep the
initial cost down.  Then when more performance is needed, or funds are
available, the systems can be upgraded. The end result is the same, because
performance is identical, and since the Cached Processor Option includes a math
coprocessor socket, expansion is identical.  When faster SLC chips are
available, either configuration may be upgraded.  The SLC model by adding the
new Cached Processor Option, and the SX model by replacing the old Cached
Processor Option with the new one.

Q. How does a Model 56SX or 57SX, with the PS/2 Cached Processor Option
installed (or a Model 56SLC or 57SLC) compare to other "cached 20MHz 386SX"
systems?
A. The 386SLC processor used in the PS/2 Cached Processor Option is the only
one to use an internal 8K cache.  All other systems use the standard Intel
386SX processor, and add an external cache.  By comparison, the internal cache
makes the Models 56/57 with the PS/2 Cached Processor Option installed as much
as 67% faster than competitive cached 20MHz 386SX systems, and even as much as
7% faster than 25MHz 386DX systems!  Compared to a standard Model 56SX/57SX the
difference is up to 88% faster.

Q.  What does the "SLC" in 386SLC processor stand for?
A.  It stands for "SX processor, Low-power, Cached."

Q.  Does the IBM 386SLC processor include integrated power management
capabilities, like the Intel 386SL processor?
A.  Yes.  The power management capabilities are not identical at the hardware
level, but they are compatible at the software interface level.

Q.  Is this chip Intel 386/386SX-compatible?
A.   Yes; every bit as software compatible as the 386SX itself.  It has been
certified as such by Intel, and in fact was developed with Intel's cooperation.
It is even pin-compatible; however the 386SX as defined by Intel leaves some
pins unused.  The IBM 386SLC uses some of these pins for power management,
asynchronous operation, and cache controllability.  This is why a 386SX can't
simply be removed and replaced by the 386SLC.  Additional circuitry is needed
by the system to utilize these advanced features.  Thus the reason for the PS/2
Cached Processor Option.

Q.  Does the IBM 386SLC processor use a "static" design, suitable for low-power
application?
A.  Yes.

Q.  Are there any limitations or incompatibilities to watch out for with the
PS/2 Cached Processor Option.
A.  The only known conflict is with the IBM ARTIC Portmaster Adapter/A and
related options.  This adapter and the Option are mutually exclusive.

Q.  What does IML stand for?
A.  Initial Microcode Load, This is where your BIOS and your copy of the
Reference Diskette is stored in a 3MB protected partition on your fixed disk.

Q.  On what drive does the IML reside on a 57/90/95?
A.  The IML has to reside on the first SCSI drive on the first SCSI adapter,
set to SCSI ID 6.

Q.  What happens if I use selectable boot and make my system not see my 1.44,
A: drive?
A.  There is a "safety" device that always looks at the A: drive for a
Reference Diskette.  If there is a Reference Diskette in the drive it will
override "selectable boot".

Q.  When I try to install OS/2 1.3 on a PS/2 Model 35, 40, or 57, the system
won't even install.  What's wrong?
A.  Those systems require OS/2 1.30.1 (CSD 5015) or higher, and will not boot
from earlier versions.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.8. Model CL57 Qs & As ═══

Q.  What's the minimum OS/2 version required for the CL57 color laptop?
A.  OS/2 V2.0 is the minimum requirement for the CL57.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.9. Model P70/P75 Qs & As ═══

Q.  Can I run both the built-in plasma display, and an external color display
at the same time on a PS/2 Model P70 or P75?
A.  During POST on the P70, the BIOS checks to see if there is an external
monitor attached.  If so, the plasma display is disabled.  The P75, however
will allow both monitors to work concurrently.  Simply boot from the Reference
Diskette, go into Change Configuration, and use the F5/F6 keys to change the
display setup information to allow dual displays.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.10. Model 90/95 Qs & As ═══

Q.  What does IML stand for?
A.  Initial Microcode Load, This is where your BIOS and your copy of the
Reference Diskette is stored in a 3MB protected partition on your fixed disk.

Q.  On what drive does the IML reside on a 57/90/95?
A.  The IML has to reside on the first SCSI drive (set to SCSI ID 6) on the
first SCSI adapter.

Q.  Is there a limitation to the size of SCSI drives that I can install in a
90/95?
A.  Yes, at the present time there is a 1GB limitation for the primary drive
that will be holding the IML.  Also, if using a drive that is larger than 1GB
as a non-primary drive, the Reference Diskette may not display the correct
size.  Contact the drive vendor for compatibility information.

Q.  What do I need to do if I want to install a second fixed disk in a 90/95?
A.  All our fixed disk SCSI drives come pre-set at ID 6.  When installing a
second drive you need to first change the ID; then install the drive and run
the Reference Diskette Auto-config program.

Q.  If I want to install 4MB of additional memory in the 90/95, what do I need?
A.  To install 4MB ofany memory you will need to add pairs of memory SIMMs at
the same speed, in matching slots (except for the new 0Hx models).  See the HMR
manual for more information on matching slots.

Q.  Can I add the 256K memory cache option to the 486SX processor in a 90/95?
A.  No, only the 486DX processor complex will support the 256K cache.

Q.  How do I know if the 256K cache is working properly?
A.  Once the Level 2 cache is installed it will not show up in configuration
nor in diagnostics.  If there is a problem "POST" will give an error.
Otherwise it is working correctly.

Q.  What is the latest 90/95 Reference Diskette version?
A.  Both Reference Diskettes are at V1.3.

Q.  Is it possible to boot to an internal 5.25 drive in a 57/90/95?
A.  Yes. With our new systems you have the option to use "selectable boot" from
the Reference Diskette to select what drive you would like to boot from.
Caution:  If you use this your logical drive letters may change.

Q.  What happens if I use selectable boot and make my system not see my 1.44,
A: drive?
A.  There is a "safety" device that always looks at the A: drive for a
Reference Diskette.  If there is a Reference Diskette in the drive it will
override "selectable boot".

Q.  Which SCSI adapter comes with the 90/95?
A.  The IBM SCSI Adapter with Cache (32-bit) comes standard.

Q.  When I try to boot from a DOS diskette to install the operating system, the
system goes straight to BASIC.  Yet when I boot to the Reference Diskette, it
works fine.  What's the problem?  I've tried two copies of DOS, so it's not a
bad diskette.
A.  Boot from the Reference Diskette, and look at the drive boot sequence.
Most likely the boot bequence does not include the A: drive (which may have
been intentionally or accidentally excluded).  With the A: drive excluded, only
the Reference Diskette will boot from it. Adding the A: drive to the boot
sequence should correct the problem.

Q.  Is the IBM Data Migration Facility (DMF) supported on the PS/2 Models 90
and 95?
A.  DMF is supported on all PS/2 models except the 90 and 95.

Q.  When the "L2" (level 2, or external) cache option is installed in a PS/2
Model 90 or 95, will it show up on the Reference Diskette configuration
screens?
A.  No.  If everything is working as expected you will receive no indication.
If there is a hardware problem, it will show up during POST or Advanced
Diagnostics, just as with any other hardware problem.

Q.  On the PS/2 Models 90 and 95, does the SCSI drive that contains the BIOS
and Reference Diskette need to be set up differently than the other drives?
A.  Yes.  This drive must be configured for SCSI ID 6. The system board ROM
will always look for the drive configured as SCSI ID 6 to find the BIOS and
Reference Diskette information, regardless of which drive is currently
designated as the primary bootable drive.

Q.  What is the DISK386.SYS driver for?
A.  The PS/2 Model 90 and Model 95 Reference Diskettes contain an update
program (DISK386.SYS) and an installation program.  The update program
maintains compatibility between SCSI devices, IBM DOS, and some of the
following types of programs that assume the fixed disk drive will utilize the
system Direct Memory Access (DMA) controller:

o Multitasking DOS programs
o Programs written for the 80386 microprocessor only
o Programs that use the virtual 8086 mode of the 80386 microprocessor
o Programs that emulate expanded memory specification (EMS) in extended memory.

The update program should only be installed when applications providing DOS
and/or memory extensions fail to work properly.  For example, an application
may fail to load and return the DOS prompt or when attempting to access a SCSI
device, the system may hang or the screen may go blank.

With this update program installed, a buffer is provided in the first megabyte
of system memory, which serves as an intermediate location for data being
transferred between the SCSI adapter and the requesting program buffer.  While
this update program allows applications that utilize the system DMA controller
to run, some performance degradation in file access time may be experienced.
Only after problems have been experienced, and the performance implications
considered, should this update program be utilized.

Q.  What could cause the PS/2 Models 90 and 95 not to be able to boot from the
primary fixed disk drive if they pass diagnostics?
A.  If you know you have an operating system installed on the drive, and you
can do a DIR from a bootable DOS diskette, then make sure that the fixed disk
drive on which you have installed the operating system is designated as a
bootable drive when you set up selectable boot.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.11. PS/2 General Video Qs & As ═══

Q.  Does the 8516 touch screen display require special software to operate?
A.  Not necessarily.  To take full advantage of the 8516's 256-levels of
pressure sensitivity, software would have to be redesigned.  However, the 8516
also fully emulates an IBM or Microsoft mouse plugged into a PS/2 mouse port.
So all existing OS/2 or Windows software should work with the 8516 just as it
would with a mouse.  In addition, both the mouse and the 8516 can be used
simultaneously where a combination of the two is desirable.

Q.  My 8516 touch screen doesn't seem to be as "accurate" as it used to?  Does
it need servicing?
A.  Not necessarily.  If you have relocated the display, or have bumped or
otherwise moved the 8516 on the desk, it may just require recalibration.  This
can be done quickly and easily by the user following the instructions included
with the display, using the supplied software.

Q.  What drivers come with the XGA adapter?
A.  DOS 3.3/4.0, OS2 1.2 (OS/2 1.3 includes an XGA driver), Windows/286 V2.1,
Windows 3.0, AutoCAD release 10 and AutoCAD/386 release 10.  These are all on
two diskettes that are shipped with the systems and with the adapter, if sold
separately.

Q.  What makes XGA better than 8514/A or VGA?
A.  Several things.  First, it is a 32-bit Bus Master adapter optimized for
bitmapped applications (such as Windows and OS/2), which means significantly
better performance than the 8514/A in 1024x768 resolution mode; both because of
the wider data path and the on-board processor.  Then, the use of built-in
16-bit VGA circuitry means better performance in VGA mode than the 8-bit VGA
built into previous PS/2 motherboards, which was also passed through from the
motherboard VGA chip to the 8514/A adapter. Finally, XGA provides up to 65,535
colors in 640x480 mode (if an application is written to utilize this mode), in
addition to the 16 and 256 color modes offered for that resolution by the
8514/A.

Q.  If XGA is so much better than 8514/A, does this mean that the 8514/A
adapter is obsolete?
A.  No.  For one thing, the 8514/A is compatible with all PS/2s from the Model
50-80 (except P70/P75); but the XGA requires a system with a 32-bit processor
(for 32-bit instructions).  This means that the XGA cannot be used in any
286-based PS/2s, including the Models 50, 50Z, and 60.  Also, there is a large
body of 8514/A software available, so there is no danger of existing adapters
suddenly becoming unusable.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       .General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.12. PS/2 General Disk Drive Qs & As ═══

Q.  If I want to install more than two drives in my system, do I need to do
anything with my software?
A.  It depends on your operating system type and version.  For DOS 4.0 you need
CSD 31300 or higher, and for OS/2 1.2 you need CSD 4098 or higher.  DOS 3.3
will not support more than two drives.  OS/2 version 1.3 and higher, and DOS
version 5.0 will support up to 24 fixed disk drives/partitions. Nothing special
needs to be done to application software.

Q.  What happens if I use selectable boot and make my system not see my 1.44,
A: drive?
A.  There is a "safety" device that always looks at the A: drive for a
Reference Diskette.  If there is a Reference Diskette in the drive it will
override "selectable boot".

Q.  If I have a problem with my SCSI Adapter with Cache, do I take my memory
off before sending it in to the dealer Warranty Claim Center?
A.  No, you must send this card in with memory intact.  The card you receive
will have memory on it.

Q.  Does the IBM CD-ROM drive conform to the High Sierra (ISO 9660) standard,
and/or the Microsoft CD-ROM Extensions?
A.  Yes, to both standards.

Q.  I have an external 5.25" 1.2MB diskette drive connected to a PS/2 via the
1.2MB diskette drive adapter (P/N 6451007). It defaults to the next available
drive letter after C:.  Is there any way to make this adapter act as drive B:?
A.  Yes.  Under DOS the ASSIGN command may be used to swap the addresses to two
drives.  For example: ASSIGN B: D: (where D: is the current designation).  Most
programs will recognize the external 1.2MB drive as B:, however some programs
may not. There is no equivalent function in OS/2.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.6.13. Miscellaneous PS/2 System Qs & As ═══

Q.  Is there a good technical publication describing the features and benefits
of the new PS/2 486 systems?
A.  Yes.  You can order the document Personal System/2 Models 95 XP 486, 90 XP
486, 55 LS and P75 486 Fundamentals, Form Number GG24-3616.  It explains such
details as Level 2 caching, selectable boot, XGA, and anti-aliased fonts, as
well as describing some of the new options, including the 2.3GB SCSI tape drive
and the External SCSI Storage Enclosure.  The cost is minimal.

Q.  Can a desktop PS/2 be used in a vertical position?
A.  Based on the requirements of the various approval agencies to which IBM
products are certified, IBM does not support the mounting of PS/2 Models
30/50/55/70/90 in any orientation other than horizontal.  IBM's concerns are
threefold:

 1. Absent a stabilizing brace, the physical stability of the machines will not
    meet UL safety standards.
 2. The machines side cover louvers will not meet various requirements designed
    to restrict the introduction of conductive materials (such as paper clips,
    etc.) into the machine enclosure.
 3. The machine's side cover louvers do not meet bottom enclosure requirements
    designed to prevent the escape of molten materials from a machine that has
    been subject to an internal fire or severe electrical short circuit.

Note:  Vertical mounting does not subject these systems to functional problems
and therefore will not void the end-user warranty. However, customers who have
mounted such machines in an orientation other than horizontal should be made
aware that such use may invalidate UL and/or SCA safety listings.  Reference
Underwriters Lab 478, sections 5.15-5.19; Canadian Standards Association No.
Canadian Standards 220, sections 4.2.3.2 and 4.2.7.4-5.

Q.  PS/2 Models 35/40/56/57 don't appear in the list of desktop PS/2 that
shouldn't be used standing on end.  Why?
A.  These newer models were designed specifically to be used either vertically
or horizontally.  The Models 40 and 57 include a floor stand for vertical use,
and the Models 35 and 56 offer the floor stand as an option.

Q.  Can a floor-standing PS/2 be used in a horizontal position?
A.  Based on the requirements of the various approval agencies to which IBM
products are certified, IBM does not support the mounting of PS/2 Models
60/65/80/95 in any orientation other than vertical.  IBM's concern is the same
as #2 in the previous question, about vertical mounting of desktop PS/2s.
Horizontal mounting of these systems does not void the end-user warranty.  But
see the note following the question about vertical mounting. above.

Q.  Why does the keyboard password program (KP.COM) for DOS sometimes ask for a
password to use, but not always?
A.  Typing in the command KP at the command prompt will invoke the power-on
password in effect at the time.  If no power-on password is used, or if a warm
boot (Ctrl-Alt-Del) has been performed since the last power-on, no password
will be in memory for the KP program to use.  In this case a popup window will
appear requesting a password to use.  This password will stay in effect for
future uses of KP until the next power-off.

Q.  I have a PC Convertible that will not talk to a printer attached to the
serial/parallel port when the Convertible is running on battery power; but
everything passes diagnostics.  What's the problem?
A.  Make sure the configuration program is set up to run the serial/parallel
adapter from the battery.  The default is "No."

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Model 30/30-286 Qs & As                                 Model CL57 Qs & As
Model 35 Qs & As                                        Model P70/75 Qs & As
Model 40 Qs & As                                        Model 90/95 Qs & As
Model L40 Qs & As                                       General Video Qs & As
Model N51 Qs & As
                                                        General Disk Drive Qs & As
Model 55LS Qs & As
                                                        Miscellaneous System Qs & As
Model 56/57 Qs & As

To return to the PS/2 Systems Qs & As header, double-click here.


═══ 7.7. OS/2 1.x Technical Qs & As ═══

The following sections contain Qs & As related to IBM OS/2 1.x.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the Technical Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.1. OS/2 1.x Configuration and Setup Qs & As ΓòÉΓòÉΓòÉ

Q.  I am trying to install OS/2 on a non-IBM system, but get an "FDISK Failure"
error almost immediately.  What's wrong?
A.  This error indicates that OS/2 doesn't recognize the fixed disk drive
controller.  Contact the system vendor, or the hard drive controller
manufacturer (which may be the hard drive manufacturer, if the controller is
integrated with the drive) for compatibility instructions.  There may be a dip
switch or jumper setting that will emulate a supported controller, or possibly
a BIOS upgrade that will make the controller work with OS/2.  As a last resort,
the hard drive controller may have to be replaced with one that is compatible
with OS/2.

Q.  I just installed OS/2, but my serial mouse doesn't work.  It worked fine
under DOS.
A.  If you have already followed the instructions in the OS/2 Command Reference
for the MOUSE.SYS and mousespecific driver statements (eg., MSSER01.SYS) in
CONFIG.SYS, make sure that if your mouse is connected to COM1 any dip switches
or jumpers on the mouse are not set to use interrupt 4 (IRQ4); if it is
connected to COM2, make sure it is not set to use IRQ3.  This would conflict
with the interrupts OS/2 uses for these ports.

Q.  Is there any way to auto-start a DOS application, either from STARTUP.CMD,
or a Group?
A.  Not in OS/2 1.3.

Q.  When I try to install OS/2 1.3 on a PS/2 Model 35, 40, or 57, the system
won't even install.  What's wrong?
A.  Those systems require OS/2 1.30.1 (CSD 5015) or higher, and will not boot
from earlier versions.

Q.  I already have a copy of OS/2 1.3, and the 5015 CSD to apply to bring it up
to the 1.30.1 level.  But if I can't even boot from the 1.3 installation
diskette on a PS/2 Model 35, 40, or 57, how can I install the CSD to bring it
up to the required level?
A.  You can't.  However IBM has instituted a policy allowing users who are in
this situation to trade in their 1.30 version for a shrink-wrapped 1.30.2
version which is bootable on those systems that won't boot from 1.30.  An IBM
Authorized dealer may contact the NDD National Support Center for this
trade-in.  IBMers can do this by sending a PROFS note to Dave Whiter (WHITER @
BCRVMPC1), who will make arrangements to replace the customer's 1.30 copy with
1.30.2.  All copies of OS/2 currently shipping to dealers are at the 1.30.2
level, but some dealers may still have the 1.30 level in stock.

Q.  When I try to start multiple occurrences of VIEW.EXE (to display online
books like the OS/2 Command Reference or the PS/2 Assistant), automatically via
STARTUP.CMD, I get a message after the first one that it is unable to open the
input file.  How can I accomplish this?
A.  OS/2 1.30 ship-level had a bug that prevented this.  But 1.30.1 (CSD level
5015) resolves the problem.

Q.  What causes TRAP 02/002/0002 errors?
A.  Usually it is caused by defective, or incompatible memory SIMMs or
adapters, but can also be caused by "auto-switching" EGA adapters. If you have
such an adapter, make sure the auto-switching feature is disabled.

Q.  What causes TRAP 0D/00D/000D errors?
A.  Sometimes it is caused by defective, or incompatible memory SIMMs or
adapters, but can also be caused by corrupted or incompatible software. If the
error occurs every time you load a particular program, most likely it is the
software at fault.  Try re-installing from the original diskettes. If the
problem doesn't go away, and the program has never worked, most likely the
program itself is not compatible with that version of OS/2.  Other programs may
occasionally fail, but if restarting them usually works, you may have an
intermittent memory failure.

Q.  What's the difference between the 1.30.1 "update" and CSD 5015?
A.  There is no difference except packaging and the ordering method.  1.30.1 is
now being shipped in the same shrink-wrap packaging as 1.30 was (it has bright
red lettering on the package identifying the new level).  CSD 5015 (either
WR05015 for EE, or XR05015 for SE) is obtainable through the normal CSD
process.  It can be used to upgrade the ship-level 1.30 version (XR00000 for
SE, or WR05000 for EE) to 1.30.1.  Also, the CSD includes a file on the last
diskette that lists the changes from 1.30 to 1.30.1.  The 1.30.1 shrink-wrapped
set does not include this file.

Q.  What's the minimum OS/2 version required for the L40 laptop?
A.  OS/2 SE or EE V1.30.1 is the minimum requirement for the L40.

Q.  What problems might I encounter if I use ship-level OS/2 1.3 on the L40?
A.  The 1.30.1 update fixes problems in several areas: 1) Random read/write
errors on the diskette drive, 2) the inability to print, and 3) the inability
to display the "key" symbol for the Power-On Password feature.  In addition,
the update supplies a new driver to enable the Trackpoint to work as a
trackball.  The PS/2 Mouse driver will only support the Trackpoint as a mouse.

Q.  What's the minimum OS/2 version required for the N51 notebook?
A.  OS/2 SE or EE V1.30.1 is the minimum requirement for the N51SX; the N51SLC
requires V1.30.2.

Q.  What's the minimum OS/2 version required for the CL57 laptop?
A.  OS/2 V2.0 is the minimum requirement for the CL57.

Q.  When my OS/2 1.3 system boots, I get a SYS1728 error ("The system does not
have enough storage to enable disk caching."), but I have plenty of memory and
disk space.  What's wrong?
A.  This error means that your DISKCACHE= parameter in CONFIG.SYS is too small.
If it is set at the default, 64K, try increasing it to 256K.  Then reboot.  If
the error goes away, you may leave the cache at this size, or change it to
something higher or lower, at your discretion, depending upon your available
memory.

Q.  I have a PS/2 with OS/2 1.2 installed on it; but when I try to install OS/2
1.3 I get the following error when I boot from the OS/2 1.3 installation disk:
SYS1045: The application program is not compatible with the version of the
operating system being used.
A.  This is the result of a previous aborted installation of 1.2 (or of an EE
component of 1.2); it left behind a C:\OS2\INSTALL\DDITEMP directory containing
installation files from a previous attempt.  Delete the DDITEMP directory and
you should be able to reboot from the Installation Diskette and install 1.3
normally.

Q.  I expected that going from FAT to HPFS with Lazy Writes would improve my
disk performance, and it has, except for the Database Manager. It doesn't
appear any faster than before.  What can I do to speed it up?
A.  Nothing, unfortunately.  For data-integrity reasons, the DBM uses
COMMIT/ROLLBACK.  If data were permitted to go through the delayed-write
caching provided by Lazy Writes, it would defeat the purpose of
COMMIT/ROLLBACK.  Therefore DBM bypasses the Lazy Writes and writes directly to
the disk. Although this results in poorer performance for the Database Manager
than if it used Lazy Writes, it means assured data integrity.

Q.  Does IBM OS/2 1.x support OEM SCSI drives?
A.  IBM OS/2 provides a device driver for the IBM SCSI adapters.  Although IBM
has not tested any non-IBM SCSI drives with OS/2, any SCSI drive that is
compatible with the IBM SCSI adapters, should be usable under OS/2 when used
with the IBM SCSI adapters.  The device driver support is for the controller,
not the drives themselves.  Questions about the compatibility of specific
drives with the IBM SCSI adapters should be addressed to the respective drive
vendors.

Q.  Is there a shortcut for finding information in an online book, from the
command line?
A.  Yes.  The syntax of the VIEW.EXE command is:  VIEW bookname string.  If you
type VIEW CMDREF COPY, you will jump directly to the COPY command topic in the
OS/2 Command Reference.  If you type VIEW PS2A_MKT OS/2, you will go to the
first section of the PS/2 Marketing Assistant containing OS/2 in its title.
This shortcut only works for text contained in menu headings, and only finds
the first occurrence of the string. For more flexible search capability, use
the Search option from the Action Bar.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.2. OS/2 1.x PM/User Interface Qs & As ΓòÉΓòÉΓòÉ

Q.  In OS/2 1.3, is there any way to "screen capture" the entire PM desktop?
A.  Not built into OS/2 1.3, however a number of commercial and shareware
utilities provide this function.

Q.  In OS/2 1.3, is there any way to start a DOS program in the DOS box from an
OS/2 command line, or batch file?
A.  No.  DOS programs can only be started from an OS/2 group (menu), or within
the DOS box itself.  A DOS batch file (AUTOEXEC.BAT or other) can be set up to
start a DOS app in the DOS box, but the DOS box still must be started manually
(by double-clicking on the DOS icon) before the DOS box AUTOEXEC.BAT batch file
will execute.

Q.  Can a DOS program set up in an OS/2 1.3 group be "auto-started" the way
OS/2 programs can?
A.  No.  Only OS/2 programs can be auto-started under OS/2 1.3.

Q.  I have a PostScript printer, and it works fine on PS documents, but when I
send an ASCII document to print, it just seems to get "swallowed" by the
printer.  Nothing comes out.  What can I do?
A.  If your printer offers an ASCII mode in addition to the PS mode, you have
several options: 1) If the printer vendor offers an automatic emulation
switching driver or hardware option, that would allow the printer to jump into
the appropriate mode automatically.  2) You can go into the File Manager, find
the file you want to print, and drag the file icon to the Print Manager icon,
and drop it.  You will be prompted for the printer driver to use, and whether
the file is text or graphics.  After responding, your document will print
correctly.  3) Again using the File Manager, instead of dragging/dropping the
file icon, you can simply highlight the file by single-clicking on the file
name, and then press the Shift-Print keys.  This will bring up the same
printing prompts as the previous step, but without the need to drag/drop, which
requires that the Print Manager icon be visible on the desktop.

Q.  Is there a quicker way to find the session I want from the Task List than
using the scroll bar?
A.  Yes.  You may either use the PgUp/PgDn keys, or type the first letter of
the task name.  If there is more than one task beginning with that letter, you
will jump from one name to the next using that letter.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.3. OS/2 1.x Printing/Printer Driver Qs & As ΓòÉΓòÉΓòÉ

Q.  In OS/2 1.3, is there any way to "printscreen" the entire PM desktop?
A.  Not built into OS/2 1.3, however a number of commercial and shareware
utilities provide this function.

Q.  What printers are supported by OS/2 1.3?
A.  For a complete list of the nearly 200 printers supported, see the tip
entitled Printers/Plotters Supported by OS/2 1.3 in the OS/2 1.x Tips section
of the IBM PS/2 Technical Assistant.

Q.  Is there an OS/2 1.3 driver for the IBM 4029 LaserPrinter?
A.  Yes, but the system must be at CSD level 5050 or higher (V1.30.2).  Make
sure that you have the PSCRIPT.DRV driver installed before applying the 5050
CSD; this will make sure the new PostScript driver, which includes the 4029
drivers) is installed.  Installing the shrink-wrapped 1.30.2 package will have
the same effect; just make sure to install the PSCRIPT.DRV driver.

Q.  Is there an OS/2 1.3x driver available for the HP LaserJet
III/IIID/IIIP/IIISi family?
A.  Yes, but the system must be at CSD level 5050 or higher (V1.30.2).  Make
sure that you have the LASERJET.DRV driver installed before applying the 5050
CSD; this will make sure the new PostScript driver, which includes the 4029
drivers) is installed.  Installing the shrink-wrapped 1.30.2 package will have
the same effect; just make sure to install the LASERJET.DRV driver.
Alternatively, it is available for downloading from the IBM NSC BBS
(404-835-6600), in file download area 17.

Q.  Is there an OS/2 1.3x driver available for the HP PaintJet XL printer?
A.  There are no drivers available specifically for the PaintJet XL, however
the HP Laserjet Classic driver will work (for black-and-white printing only)
with the PaintJet printer.  OS/2 2.0 has PaintJet drivers.

Q.  Is there an OS/2 1.3x driver available for the HP Deskjet or Deskjet 500
printers?
A.  Yes, but the system must be at CSD level 5050 or higher (V1.30.2).  Make
sure that you have the EPSON.DRV driver installed before applying the 5050 CSD;
this will make sure the new PostScript driver, which includes the 4029 drivers)
is installed.  Installing the shrink-wrapped 1.30.2 package will have the same
effect; just make sure to install the EPSON.DRV driver.  When you use Printer
Install from the Print Manager Setup option there will be a listing for the HP
DeskJet 500 emulating an Epson EPL-6000.  Alternatively, you may use the
LaserJet Classic driver.

Q. Is there an OS/2 driver for the IBM 4216-020?
A. Not from IBM; OS/2 only includes drivers for the 4216-030 and -031 models.
There is a company, called David Goodenough & Associates, Limited that
developed an OS/2 1.1/1.2 driver for the model 20.  It is possible that they
also offer 1.3 and/or 2.0 versions of the driver.  For more information,
contact the vendor at:

   David Goodenough & Associates, Ltd.
   283 City Road
   London, ECIV 1LA
   United Kingdom

   Phone: [phone]
   Fax: [phone]

Note:  This is not an endorsement of the product, nor a recommendation by IBM;
simply information for your benefit.

Q.  Within a 3270 emulation session window, a print-screen copies all the text
in the window, plus the status information on the bottom line of the screen.
Is there any way to print only part of the text, and exclude the status line?
A.  Yes.  The Shift-PrtSc key combination by itself will include all text
within the window, plus the status line at the very bottom. By using the mouse
to draw a box around a portion of the text on the screen, you can exclude all
other text, but the status information will still print.  To avoid printing the
status line you must go to the 3270 Print Control icon, open the session, and
select the Setup pulldown.  From there toggle the Print OIA option so that no
check mark appears.  This will prevent the status line from printing.

Q.  My Print Manager somehow died with a Trap error, and when I tried to
restart it from the main group I received a message saying that it was already
started, but it wasn't anywhere to be found.  What can I do to get the Print
Manager back?
A.  There are two simple ways to do this.  Either 1) reboot your system, which
will automatically restart it, or 2) Double-click on the file PMEXEC.EXE in the
File Manager (or type START PMEXEC.EXE from the command line), which will
manually restart the Print Manager.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.4. Other OS/2 1.x Device Driver Qs & As ΓòÉΓòÉΓòÉ

Q.  When I tried to install the COM02.SYS driver on my AT-bus system so that I
could use COM2, I received an error, and still can't access COM2.  What am I
doing wrong?
A.  COM02.SYS provides support for COM1 through COM3 on Micro Channel systems
only.  COM01.SYS supports COM1 and COM2 on an AT-bus computer.  The 01 and 02
designations refer not to the COM port number, but the type of bus
architecture.  Use COM01.SYS on your system and you should be able to access
both of your serial ports.

Q.  What is EGA.SYS for?
A.  The EGA.SYS device driver is used to support both the EGA and VGA adapter
modes in the DOS Compatibility Box. It is useful for those programs that expect
EGA register compatibility (which the IBM VGA controller does not provide--only
BIOS compatibility).  This driver provides software registers for such programs
to use, and thus allows them to operate correctly in the DOS box.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.5. OS/2 1.x Communications Manager Qs & As ΓòÉΓòÉΓòÉ

Q.  When I used REINST (or EECFG) to add additional Comm Manager features (or
reinstall existing ones), the install aborted with 01 (Unpack) errors. What
does this mean, and what can I do about it?
A.  An unpack error during a REINST or EECFG usually indicates that one of the
files that the installation program is trying to copy to your hard disk drive
already exists, and is in use by another part of Comm Manager.  If CM is
already running, hot-key to another session and shut CM down.  This may allow
you to continue.  If you can't continue, abort the installation, and try again
(but make sure that no LAN Requester or other CM functions are currently
running) from the REINST or EECFG command.

Q.  Is there any way to run 5250 sessions in windows, like the 3270 Emulation
sessions?
A.  Yes.  All you need is OS/2 1.30.1 (CSD level 5015 or higher).  It provides
the ability to run 5250 sessions in windows.  The instructions are contained in
a file called 5250.TXT on diskette 13.  Briefly, all that is needed is to go
into \CMLIB and edit the file CM2.CMD.  Find the statement: REM SET EM5250=WIN,
and change it to SET EM5250=WIN.  Then close the Comm Manager (if started), and
restart it.  When the 5250 emulation session starts up it will be in a window,
similar to that for 3270 Emulation.

Q.  Within a 3270 emulation session window, a print-screen copies all the text
in the window, plus the status information on the bottom line of the screen.
Is there any way to print only part of the text, and exclude the status line?
A.  Yes.  The Shift-PrtSc key combination by itself will include all text
within the window, plus the status line at the very bottom. By using the mouse
to draw a box around a portion of the text on the screen, you can exclude all
other text, but the status information will still print.  To avoid printing the
status line you must go to the 3270 Print Control icon, open the session, and
select the Setup pulldown.  From there toggle the Print OIA option so that no
check mark appears.  This will prevent the status line from printing.

Q.  What is the best way for an OS/2 user in a LAN environment to communicate
with a Unix-type system?
A.  TCP/IP V1.1 for OS/2 is the solution offered by IBM to allow OS/2
workstations to communicate with the machines in the Unix world such as IBM
RT's and RISC/6000 units running AIX.  A good many of the Unix machines in use
utilize TCP/IP, allowing this to be a common communications platform among
machines provided by various vendors. TCP/IP V1.1 for OS/2 comes with many
TCP/IP standard applications such as NFS, FTP, TELNET, and a mail system.
Running under OS/2 Extended Edition V1.20, TCP/IP V1.1 can run on both Ethernet
and Token Ring networks, and even act as a TCP/IP router between Ethernet and
Token Ring.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.6. OS/2 1.x Database Manager Qs & As ΓòÉΓòÉΓòÉ

Q.  Does Database Manager Remote Data Services (RDS) require OS/2 LAN server
for remote data access across a LAN?
A.  No.  RDS does not need LAN Server, nor Communications Manager, as it has
its own LAN communications layer built-in.  However, all locally administered
LAN adapter addresses must be explicitly identified to remotely access a
database.  And, not using the LAN Server product limits a database client to
accessing only one database server, and printing locally. On the other hand,
installing LAN Server means that all links between users will automatically be
made by the LAN Server/LAN Requester code, eliminating all the manual naming
effort.  Plus, it allows clients to link to any or all database and print
servers on the network.  Thus, while LS is not required, its presence makes the
setting up of remote database clients simpler and more automatic.

Q.  With LAN Server installed, does a Database server have to also be a LAN
server, or can a DB server be installed on just a LAN requester workstation?
A.  A Database server can be installed on either a LAN server or requester
node, and still be accessed by all authorized users on the network.

Q.  I know there is a system timestamp data type for the Database Manager, but
I can't seem to find out how to set it up.
A.  The Edit Code that represents the timestamp (system date and time) is TSI.
For more information about this data type, please refer to the EE 1.3 User's
Guide, Vol. 3, Chapter 5-10, and Appendix I-6.

Q.  Is there any way to specify compressed print for a QM query?
A.  Yes.  From the Databases menu of the Query Manager, select System from the
action bar, and then Open printer pickname  Enter the name of an existing
nickname, or a new one to be created, and press Enter.  From the Printer
Nickname panel, specify the printer port you will print to, a printer type
compatible with your printer, and the appropriate paper size.  Then press Enter
and Cancel to return to the Databases menu.  This only has to be done one time.
Once this is setup, run the query you wish to print compressed.  When the query
results appear on your screen, select Actions from the action bar, and then
Print.  When the Print panel pops up, select To printer. At this point you will
be prompted for a Line width, and Print type, among other things.  Just click
on the Compressed option for the Print type and press Enter, and your output
will be compressed.

Q.  Is there any way to change the order in which the cursor jumps from field
to field in a Query Manager data entry panel?
A.  The cursor moves in a strictly defined manner:  Starting with the top
left-most field, it jumps from left to right until it reaches the last field on
the line.  Then it down jumps to the left-most field on the next line and moves
to the right, and so on, until it reaches the right-most field on the last
line.  There is no way to program the cursor to jump in any other fashion than
this.

Q.  Is there any way to create a Query Manager panel in the form of a menu that
allows you to execute REXX and other executable (EXE) programs?
A.  The Query Manager is strictly a Database Manager interface, not an
operating system shell.  Consequently, only DBM/QM procedures may be executed
from a Query Manager menu panel.

Q.  How do you change the name of an OS/2 Database Manager database?
A.  To rename a database:

 1. Verify the password of the database you are renaming (so you will know what
    it is later when you need it).
 2. Select the database using the spacebar, from the main database selector
    screen.
 3. Select Uncatalog from the Tools menu of the Action Bar, and uncatalog the
    selected database.
 4. Select '--NEW--' from the main database selector screen.
 5. Select Catalog from the Tools menu.
 6. Enter the original database name at the 'Database name' field, the desired
    new database name at 'Nickname,' the drive letter on which the database is
    stored, and a new comment (if desired).
 7. Query Manager will then prompt you for the original database's password.
 8. If all these steps are followed correctly, Query Manager will add the
    database with the new name (and new comment, if any) to the main database
    selector screen.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.7.7. Miscellaneous OS/2 1.x Qs & As ΓòÉΓòÉΓòÉ

Q. What versions of OS/2 support Extended Services 1.0?
A. OS/2 1.30.1 (CSD level 5015 or later), and OS/2 2.0.

Q.  I keep seeing references to "CSD levels."  What does this mean, and how do
I find out what CSD level I am at?
A.  CSD means Corrective Service Diskette, or patch diskette.  A CSD level
reflects how up-to-date a system is in regards to software patches.  To
determine your CSD level just type SYSLEVEL at any OS/2 command prompt.  You
will be shown one or more screens informing you of the current and previous
levels of the base operating system, and various components of the OS/2
Communications and Database Managers, if installed.  If you discover that you
need newer CSDs than you presently have, there are several ways to obtain them.
1) Download them from the IBM NSC BBS (404-835-6600); 2) Ask your dealer for a
copy (a dealer can either order them from the IBM Defect Support Center or
download them from the BBS via a special 800#); 3) Order them directly from the
IBM Defect Support Center (if you have a registered 7-digit IBM customer
number).

Q.  What is the difference between TCP/IP for OS/2 Version 1.1 and TCP/IP for
OS/2 Version 1.2?
A.  TCP/IP for OS/2 V1.2 adds:
- X-Windows and NFS Server support
- X.25 support for IP
- NDIS support
- VT220 Emulation
- Support for OS/2 1.3 and 2.0

Q.  Is there an easy way to protect all the files in a directory from erasure
or modification?
A.  Yes.  You can use the File Manager to set the attributes to Read-only, and
even Read-only and Hidden, if desired.  To do this, start the File Manager and
open the directory you with to protect.  Then using the File menu from the File
Manager action bar choose Select All.  This will highlight all files in that
directory.  Then select Change Flags from the File menu. Finally, specify the
attributes you wish all selected files to have.  After using the Change button
to save your selections, all attributes will be set to your specifications.
(You may also want to make sure that you also use View...Include from the
action bar to include or omit Read-only and/or Hidden files from the list of
files to display when you open a directory window, depending on your
preferences.)

Q.  Does OS/2 1.3 include an Undelete feature?
A.  No, however at least one software vendor sells an OS/2 utilities package
that includes an undelete program.  GammaTech can be reached at 405-359-1219;
or PO Box 70, Edmund, OK, 73083-0070.  Similar products from other vendors may
also exist; this is not meant as an endorsement of this particular vendor or
product; merely an example. OS/2 2.0 does include an Undelete feature.

Q.  When running CHKDSK on an HPFS partition I get a message that some files
are "cross-linked."  What can I do to fix these files?
A.  If you boot from the Installation diskette (and ESCape from the IBM logo
screen to the A> prompt) then run CHKDSK C: /F, the files will be recovered.
If the cross-linked files are on a partition other than C:, run CHKDSK d: /F
from the C: drive (where d: = the appropriate drive letter). It is not
necessary to boot from the Installation Diskette in this case.

Q.  Is there any way to strip the Extended Attributes from files, if desired?
A.  Yes.  The command EAUTIL is expressly intended for that purpose.  It strips
the EA from files, and puts them in a separate file using a name you provide.
It also allows the EAs to be reattached at a later time.  For more information,
refer to the EAUTIL command in the OS/2 Command Reference.

Q.  How do I obtain a product called Graphical Data Display Manager (GDDM) OS/2
1.2?
A.  This is not available as a separately orderable product.  It must be
ordered as a feature by the mainframe location, through their IBM marketing
rep.

Q.  Is there a keyboard-password/screen-saver program for OS/2?
A.  Not included with OS/2 1.0-1.2, and not in ship-level 1.3.  But beginning
with the 1.30.1 version (also called CSD 5015), a keyboard-and-mouse locking
utility called LOCKUP.EXE is included.  It also provides a screen blanking
feature, to protect the screen from "burn-in."  To determine whether you are at
OS/2 V1.30.1 or later, use the SYSLEVEL command from the command prompt to see
the current CSD level.  For those at earlier versions, there are shareware
keyboard locking programs available on public BBSes.

Q.  Is there any way to use the LOCKUP.EXE program as strictly a
screen-blanker, without the password feature?
A.  No.  Keyboard password security is its primary function.  The
screen-blanking feature is a useful enhancement but cannot be run "standalone."

Q.  Why do we have to purchase several key OS/2 Extended Edition manuals
separately?
A.  Effective immediately, both dealers and customers may order the following
EE 1.3 publications, free of charge, by calling 800-IBM-7282&

o System Administrator's Guide For Communications (P/N 01F0302)
o Database Manager Administrator's Guide (01F0291)
o Problem Determination Guide For the Service Coordinator (01F0301)

Q.  What is the EA DATA. SF file for, and do I need it?
A.  On HPFS partitions, a file's Extended Attributes (which includes such
information as Last Modification Date, Last Access Date, and user-added
comments) is attached to the file itself. But on fixed disk partitions
formatted as FAT, and diskettes, there is no way to attach this data to the
file.  OS/2 creates the EA DATA. SF file as a receptacle for this information.
Deleting this file will not damage the data files themselves, but will result
in annoying "Extended Attributes not found for this file" messages when files
that used to have EAs are accessed.  For this reason it is not recommended that
you delete EA DATA. SF.

Q.  Is there a way to see the list of keyboard commands in the Command Retrieve
buffer? A.  Yes.  Just type KEYS LIST at the command line.  The commands in the
buffer will be displayed in reverse order.  Using the up and down cursor keys
will let you scroll through those commands in either forward or reverse order.

Q.  What are the *.BIO files cluttering up my OS/2 1.2 root directory, and is
there any way to get rid of them?
A.  These files are patches to the Advanced BIOS (ABIOS) chip in all Micro
Channel PS/2s.  Each file is unique to a particular model of PS/2. OS/2 1.2
does not distinguish between the various PS/2 models, and so installs all the
files on each system.  The ABIOS.SYS file (on Micro Channel Systems) is nothing
more than an ASCII file listing all the *.BIO files in the root directory.
These files should not be deleted unless the user is sure he knows what he is
doing.  A better alternative for "uncluttering" the root is to use the File
Manager to hide the *.BIO files.  They will still be usable by OS/2, but not
visible to the user.  The good news is that OS/2 1.3 only installs the one .BIO
file needed by that particular system.  This eliminated the clutter completely.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
PM/User Interface Qs & As
                                                        Database Manager Qs & As
Printing/Printer Driver Qs & As                         Miscellaneous Qs & As
Other Device Driver Qs & As

To return to the OS/2 Qs & As header, double-click here.


═══ 7.8. OS/2 2.x Technical Qs & As ═══

The following sections contain Qs & As related to IBM OS/2 2.x.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the Technical Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.1. OS/2 2.x Configuration and Setup Qs & As ΓòÉΓòÉΓòÉ

Q. I've heard lots of rumors, but what are the real hardware requirements for
OS/2 2.0?
A. Any PC with a 386SX (or higher) processor, 4MB or more of RAM, and a 60MB
hard drive.  In many cases more memory and disk will be needed, depending on
the user's needs.  The base operating system itself uses about 3.5MB of RAM and
16-29MB of fixed disk (depending on what you choose to install).  The remainder
is available for application and data use.  As most users eventually run more
programs concurrently than they anticipated at first, make sure your system
allows for growth if you are starting with near the minimum.  Currently more
than 200 non-IBM PCs have passed IBM's OS/2 compatibility testing, with more
coming.  (This list can be found in the OS/2 2.0 Tips section of the Technical
Assistant.)  Others are being tested, and the list is updated monthly.

Q. If I install OS/2 2.0 on a PC that is not on the compatibility list, am I
out of luck if I run into problems?
A. No.  Call the IBM Defect Support Center at 800-237-5511 and explain your
problem.  They will attempt to resolve your problem.  If they can't step you
though a workaround to the problem, or develop a patch to fix it within 90
days, you will be offered your money back for the OS/2 purchase.

Q. Can OS/2 2.0 be installed from any drive besides A:?
A. Yes, to a degree.  The operating system itself, and Extended Services can be
installed from a network drive (which can be any letter above C:). As far as
physical diskette drives are concerned, it must be the A: drive.  However, on
many systems (such as the PS/2 Models 57/90/95), the system can be configured
to boot from any internal diskette drive, making that drive the "A:" drive,
regardless of cabling or physical position.  Some systems also allow the cables
to be swapped (perhaps with other adjustments) to produce a new "A:" drive.
Consult your system vendor for directions.

Q. In the README file that comes with OS/2 (in the root directory, viewable in
the Information folder), there is reference to a SCSI driver called
OS2SCSI.SYS, supposedly in \OS2, yet I can't find it.  Where is it?
A. This is a typo in the README file.  The name is actually OS2SCSI.DMD, not
.SYS.

Q. I understand that most DOS and Windows apps should run under OS/2, but what
kinds of programs are likely to fail?
A. 1) Those that could compromise the integrity of the operating system, such
as VCPI memory extenders and certain low-level disk utilities; 2) Those
requiring extremely high interrupt rates (typically more than 1,000 interrupts
per second), including software to support some fax and sound boards.  3) Those
requiring a specific version of DOS.  OS/2 2.0 provides an emulation of DOS
5.0, but some applications may need DOS 3.3, for example, and won't work with
anything else.  In this case, start a DOS image of the DOS 3.3 diskette (within
a VDM), and run the the application under real DOS 3.3 inside a VDM.

Some other applications may require special DOS Settings, and some may run with
limited function.  But overall, the large majority of programs will run "as
is", and as faster or faster than before, with greater data integrity.

Q. In OS/2 1.3 there was a Program Properties option to start an application on
bootup.  How do I "autostart" apps under 2.0?
A. Two ways: 1) Use Create Shadow from an application pull-down menu to copy
the application icon to the Startup folder; or 2) Leave the application running
when you Shutdown the system.  All running apps will autostart upon bootup.

Q. Is there any way to set different execution priorities for individual DOS
applications?
A. No.  Application priority is set by the application programmer.  Since DOS,
unlike OS/2, doesn't provide for multiple execution priority levels for apps
there is no reason or way to build them into DOS apps.  Therefore when they are
run in a DOS session under OS/2 there is no inherent priority level
distinction, and no way for a user to impose unique priority levels externally
to the programs.

Q.  What's the minimum OS/2 version required for the CL57 color laptop?
A.  OS/2 V2.0 is the minimum requirement for the CL57.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.2. OS/2 2.x WPS/User Interface Qs & As ΓòÉΓòÉΓòÉ

| Q. Is there any way to change the color of the icon text?  When I drag/drop a
color from the Color Palette it changes the Desktop color, not the icon text.
A. Just hold the Ctrl key while dragging/dropping the color.  This will change
the text color instead of the Desktop.

Q. I'm tired of always using the Sort option on a folder pulldown to arrange
the icons the way I want them. Is there any way to make the icons sort
automatically?
A. Yes.  Just Open the Settings for a folder, select the Sort notebook tab, and
click on the check-box called "Always maintain sort order." Then close the
Settings.  This will make the change permanent for that folder, using whichever
sort order you select.  You can always change the sort order later, and the
"auto-sort" will stay in effect, using the new sort order.

Q. I went into the Desktop pulldown to change some settings, including
"Minimize to desktop", so that my icons don't disappear when I minimize them.
But now only some objects minimize to the desktop, while others still hide.
What's wrong.
A. By using the Desktop settings you changed only the behavior of icons on the
Desktop; not icons contained in other folders.  To make global changes to the
way objects hide/minimize, go to the OS/2 System folder, then the System Setup
folder, then open the System icon.  From the Window notebook tab make the
changes you want for all folders.

Q. Is there any way to disable the Print Screen function?
A. To enable or disable Print Screen, go to the OS/2 System folder, then the
System Setup folder, then open the System icon.  From the Print Screen notebook
tab make your choice.

Q. Why are the titles of some of my icons lighter in color than the others?
A. These icons represent "shadows" of the original object.  The lighter text is
a way of distinguishing between originals and shadows.

Q. What are "Shadow" icons and why would I want them?
A. Each folder represents a directory on your disk.  Each icon/object
represents a file in that directory.  If you copy an object from a folder to
the Desktop, for example, you are also copying the file associated with that
object.  By creating a shadow of the original object you can put "pointers" to
the file in many different folders or on the Desktop (which is actually a
folder itself) for convenience, without also duplicating the file multiple
times (and wasting a lot of disk space).  In addition, if you duplicate the
file, each is a separate copy, and updating one doesn't affect the others.  By
using shadows you can access the same copy of the file from multiple places,
insuring that you are always working with the same version of the file.

Q. If I shred an object (icon), does that delete the data file or program that
it represents?
A. No.  Objects are independent of the physical disk files.  There can be
multiple objects representing the same files.  Therefore there must be a way to
delete some of them without also deleting the file they represent.

Q. Is there a difference between deleting a shadow object and the original?
A. Yes.  If you delete a shadow, it does not affect other shadows of the
original, or the original object itself.  However if you delete the original,
all shadows are deleted with it.

Q. Am I limited to 11 character icon/object names on a FAT system?
A. No.  Like HPFS partitions, FAT partitions will support up to 254 character
object names (however the physical file names on disk are still limited to 11
characters; that is a FAT limitation, not a Workplace Shell limitation).

Q. I would like to get more icons side by side on my Desktop, but some of the
icon names are so long that I can only get a few icons on each line.  What can
I do?
A. You have two options 1) Rename the icons to something shorter (such as
Windows Apps #2, instead of Additional Windows Programs); or 2) Insert carriage
returns (using the Enter key) in the name to break the name into multiple short
lines of text.

Q. How do I copy or move an object with the mouse?
A. To move, just press and hold the right mouse button over the object you wish
to move, while dragging and dropping it elsewhere.  To copy, press and hold the
Ctrl key while dragging and dropping with the mouse.

Q. I have noticed that different people have the icons on their desktop
arranged differently.  Some have them all over the screen, others have a single
column down the left side of the screen with the icon text to the right (and a
scroll bar to see those of the screen), and still others have multiple columns
of icons.  How do I select which way I want it?
A. Press the right mouse button on a blank part of the Desktop to bring up the
Desktop menu; then select Open, Settings.  Finally, from the Settings screen
select "Flowed" for multiple columns, "Non-Flowed" for single-column, or
"Non-grid" (the default) for left-to-right, top-to-bottom arrangement all over
the screen.  Then close the Settings to save.

Q. What is a "work area"?  I see that option in a number of Settings notebooks
under the File tab.
A. A work area is a special kind of folder.  The Desktop is a work area.  When
a work area is minimized or maximized, all active objects within that work area
are also minimized or maximized.  When a work area is closed, all open objects
are also closed.  When a work area is opened, all previously open objects are
reopened (this is how the Desktop restarts your apps when you boot the system).
For more information, open the Settings to the File tab and press the Help
button, or search for "work area" in the Master Help Index object.

Q. I see objects across the bottom of my desktop that have "halos" or boxes
around them.  What are they?
A. They are minimized objects.  Depending on how the desktop is setup, objects
can be minimized on the desktop, minimized inside the Minimized Viewer folder
(which can be opened on the desktop to see the minimized icons), or Hidden.
Hidden objects can be seen by double-clicking on the original object.  To
specify which way you would like your objects to appear, go to the Desktop
settings (right mouse button, Open, Settings.), go to the Window tab, and make
your selection in the "Minimized Window Behavior" box.  If you specify one of
the Minimized options, make sure to also change the "Button appearance for
windows" box to "Minimize button".  If you leave it set to "Hide button" the
icons will be hidden rather than minimized.

Q. How do I start another copy of a program from an icon without having to
duplicate the object?  When I click on the icon the already-running session
pops up.
A. Go to the Desktop settings (right mouse button, Open, Settings.), go to the
Window tab, and specify "Create new window" in the "Object open behavior" box.
Then close the Settings to save the changes.

Q. Where is the Shutdown option?  There is no Desktop Manager, as there was in
OS/2 1.x.
A. Just press the right mouse button with the pointer over any blank part of
the desktop.  This will bring up the Desktop menu.

Q. Where is the keyboard Lockup option?  There is no Utilities Group, as there
was in OS/2 1.x.
A. Just press the right mouse button with the pointer over any blank part of
the desktop.  This will bring up the Desktop menu.  From there select Lockup
now to initiate it, or open the Settings to the Lockup notebook tab to change
the Lockup settings (note that there are three pages of Lockup settings to be
changed).

Q. Is there a "screen blanker" program in OS/2 2.0?
A. Yes; two in fact.  One is the Lockup program, which allows you to specify a
timeout value after which to blank out the screen, and replace it with a bitmap
image.  The program also prompts for a keyboard password to use when locking
the keyboard.  There is also an autodim feature.  There is no way to use this
program as a screen blanker without the keyboard password feature, though.  The
other program, Cat and Mouse, offers a "hide" button that blanks the screen and
displays only the icon of a cat running around the screen.  This feature does
not require a keyboard password, but also doen't offer an auto-timeout feature
(unlike the Lockup program).  Cat and Mouse must be manually started.

Q. Is there a way to printscreen the entire WPS desktop?
A. Yes.  Simply use the left mouse button to click on an empty part of the
desktop and then use the Print Screen key. Or to print only one window on the
desktop, select that window and then use the Print Screen key.

Q. Does OS/2 2.0 require a mouse?
A. No, 2.0 is fully enabled for keyboard-only use; however most users will find
the mouse more convenient for many tasks.

Q. Is there any way to get to the Selective Install panel from a command
prompt?
A. Yes.  Just type INSTALL.

Q. I understand that OS/2 is supposed to be completely keyboard accessible, but
I can't seem to figure out how to select icons without a mouse.
A. Use the cursor (arrow) keys to move from icon to icon, then press the Enter
key to select the one you want.

Q. Is there an easy to change a DOS or Windows full-screen session into a
windowed session, or vice-versa?
A. Yes.  Just use the Alt-Home key combination to toggle between full-screen
and windowed. This procedure does not work for OS/2 sessions; just DOS or
Windows apps.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.3. DOS/Windows Sessions (VDMs) Qs & As ΓòÉΓòÉΓòÉ

Q. I understand that most DOS and Windows apps should run under OS/2, but what
kinds of programs are likely to fail?
A. 1) Those that could compromise the integrity of the operating system, such
as VCPI memory extenders and certain low-level disk utilities; 2) Those
requiring extremely high interrupt rates (typically more than 1,000 interrupts
per second.  3) Those requiring a specific version of DOS.  OS/2 2.0 provides
an emulation of DOS 5.0, but some applications may need DOS 3.3, for example,
and won't work with anything else.  In this case, start a DOS image of the DOS
3.3 diskette (within a VDM), and run the the application under real DOS 3.3
inside a VDM.

Some other applications may require special DOS Settings, and some may run with
limited function.  But overall, the large majority of programs will run "as
is", and as faster or faster than before, with greater data integrity.

Q. Are there any restrictions to what versions of DOS can be used in a Boot
Image (Virtual DOS Boot)?
A. Only that you must use a version of DOS that supports your hardware.  (For
example, you can't use DOS 2.0 on a system with 1.44MB diskette drives, because
DOS 2.0 doesn't recognize anything larger than 360K diskette drives).  Other
than that, you are free to use any operating system that will run on an 8086
processor (including IBM DOS, MS DOS, DR DOS, and even CPM/86).

Q. Is DDE supported?
A. Yes; between any combination of Windows and OS/2 applications.

Q. Is OLE supported?
A. Yes; between Windows applications.

Q. I just tried to cut-and-paste between an OS/2 application and a Windows
program, but the Paste option in the Winapp's menu was "grayed-out".  What do I
have to do to cut/paste between applications?
A. Either your Windows clipboard or your OS/2 clipboard, or both, were set to
"private".  Both must be set to Public before you can do any cutting and
pasting back and forth.  When you start the full-screen Windows session, or a
Windows app, there will be a clipboard icon opened on the Windows Desktop.  If
you start a Windows or OS/2 app in a window, the clipboard icon will appear on
the OS/2 desktop.  From within both the Windows and OS/2 clipboard icons, there
is an Option choice on the action bar.  Clicking on this will show whether the
clipboard is Public (indicated by a check-mark) or not.  If not, click on the
line that says Public clipboard.  This will change the clipboard to public.
After you have ensured that both clipboards are public, you should have no
trouble cutting and pasting between applications.  If you still can't paste,
close the program you can't paste into, and restart it.  It should work now.

Q. I know that OS/2 2.0 comes with Adobe Type Manager for OS/2, but will I have
to buy ATM for Windows for my Windows apps?
A. No.  OS/2 2.0 supplies ATM for both OS/2 and Windows applications.

Q. When I "migrate" DOS and Windows apps to OS/2 to "register" them with the
OS/2 Workplace Shell, how do I know what DOS Settings to use for each
application.
A. In most cases the default settings will work, but in some cases tuning may
be required or desirable.  OS/2 2.0 ships with a database of settings for more
than 225 of the most popular DOS and Windows applications.  These are
automatically applied when you migrate these applications.  Settings for other
applications will be added with future versions and Corrective Service (patch)
Diskettes.

Q. I have a DOS application that requires Alt-ESC (or Ctrl-Esc) to switch
between screens.  But OS/2 reserves those key combinations for switching
between sessions.  Is there any way to free up one or both of these
combinations for DOS apps?
A. Yes.  From a Virtual DOS Machine (VDM) that will be running such a DOS app
simply go into the DOS Settings (right mouse button from the application icon,
then select Settings, O pen; then Session DOS Settings) and find the setting
called KYBD_CTRL_BYPASS. Select this and from the selection box in the upper
right-hand corner choose either ALT_ESC or CTRL_ESC.  Finally, press the Save
pushbutton and close the Settings.

Q. Can I use my favorite DOS memory manager in a VDM (DOS session)?
A. No, but there is no need for one, since each VDM already includes EMS, XMS,
and DPMI memory managers.

Q. Can I use my favorite DOS memory manager from inside a bootable DOS image?
A. Even inside a bootable DOS image (actually named a Virtual DOS Boot, or VDB)
the answer is the same, since the OS/2 memory managers are still available
inside a VDM running a VDB image.

Q. Can I use my favorite DOS/Windows disk caching utility in a VDM (DOS
session)?
A. No, but there is no need for one, since each all applications, DOS, Windows,
and OS/2 are automatically cached by OS/2.

Q. What EMS (Expanded Memory Specification) level is provided in a VDM?
A. EMS V4.0, the same as DOS 4.0/5.0 provide.

Q. Does using multiple Virtual DOS Machines for several different DOS programs
simplify the complicated process of finding available address space between
640K and 1MB for Expanded memory (EMS) and certain kinds of adapters?
A. Yes, since network adapters, SCSI controllers, and most other device
addresses are actually loaded in the address space above 1MB, there should be
few conflicts with EMS memory drivers.

Q. Are DOS TSRs supported in VDMs?
A. Yes.  Even though they have never been officially supported in true DOS (due
to a lack of any standard TSR specification, and the likelihood of system
lockups when using multiple TSRs concurrently) they will be supported under
2.0.  Because TSRs are loaded into a VDMs Upper Memory Blocks (UMBs), they run
in Protected mode and are prevented from touching other VDMs or OS/2 sessions.
There is no opportunity for a TSR to crash the entire system.  The worst it can
do is lock up its own sessions, which can then be terminated from the OS/2
desktop.  No rebooting of the system (with possible loss of data) is necessary.

Q. Can EMS/XMS/DPMI drivers be loaded globally for all VDMs, or must I set them
separately in each VDM?
A. Either.  Global settings are done from CONFIG.SYS using device drivers.  In
addition, individual VDMs can enable or disable this support from the DOS
Settings.  For driver details, refer to the OS/2 Command Reference.

Q. When EMS memory is enabled in CONFIG.SYS, what is the default memory
allocation?
A. 4MB, but up to 32MB may be specified, per VDM, if needed.

Q. Will all EMS-compatible DOS and Windows programs work in a VDM?
A. It depends on the application.  All DOS apps that use the EMS 4.0 driver
provided with DOS 4.0 and higher, including all Windows apps, will work.  Older
applications that directly invoked EMS memory (without using an external DOS
driver) may not work.

Q. Are there any suggestions for the order in which to load EMS and XMS
drivers?
A. For the best performance, load the EMS driver (VEMM.SYS) first, then all
drivers that use expanded memory; then load the XMS driver next, followed by
all drivers that use XMS.  Lastly, load all drivers that use UMBs.

Q. If an application supports more than one choice of EMX/XMS/DPMI memory, is
there any preference?
A. For performance reasons, choose XMS or DPMI over EMS.  On the other hand,
EMS and DPMI support more total RAM than XMS (32MB, 512MB, and 16MB,
respectively).

Q. Does the XMS (Extended Memory Specification) driver support the use of the
High Memory Area (HMA)?
A. Yes.  The HMA (the 64K immediately above 1MB) is supported for Upper Memory
Block (UMB) usage.  To enable the HMA for UMB use specify DOS=HIGH in
CONFIG.SYS.

Q. Are there any limitations to High Memory Area (HMA) use?
A. Yes.  If multiple device drivers access HMA, make sure the XMS driver is
loaded last, to avoid conflicts.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.4. OS/2 2.x Printing/Printer Driver Qs & As ΓòÉΓòÉΓòÉ

Q. What printers are supported by OS/2 2.0?
A. For a complete list of the nearly 200 printers supported, see the tip
entitled Printers/Plotters Supported by OS/2 2.0 in the OS/2 2.x Tips section
of the IBM PS/2 Technical Assistant.

Q. How do I install downloadable (soft) fonts for my printer?
A. First, find the printer object (icon) you wish to install the fonts for.
Next, use the right mouse button to bring up the menu.  From there select Open,
Settings, Printer driver.  Then select the driver you wish to install the fonts
to, and use the right mouse button to bring up the menu.  Again select Open and
Settings.  At the bottom of the Printer Properties dialog box press the Fonts
button.  Finally, specify the drive letter and path where the fonts can be
found and press the Open button.  You will see a list of the soft fonts you can
select.  Single-click on each one you want to add.  When you have highlighted
all you intend to add, press the Add button.  The highlighted fonts will
disappear from the "New Soft Fonts" window on the left and appear in the
"Installed Fonts" window on the right.  When they have all been installed,
press the OK button to end and save your work.  Then press OK on the Printer
Properties dialog to return to the Settings book.  From there close the
settings and you are done.

Q. Is there an OS/2 driver for the IBM 4216-020?
A. Not from IBM; OS/2 only includes drivers for the 4216-030 and -031 models.
There is a company, called David Goodenough & Associates, Limited that
developed an OS/2 1.1/1.2 driver for the model 20.  It is possible that they
also offer 1.3 and/or 2.0 versions of the driver.  For more information,
contact the vendor at:

   David Goodenough & Associates, Ltd.
   283 City Road
   London, ECIV 1LA
   United Kingdom

   Phone: [phone]
   Fax: [phone]

Note:  This is not an endorsement of the product, nor a recommendation by IBM;
simply information for your benefit.

Q. If I have Windows drivers for printers not supported by OS/2, is there any
way to use them?
A. Yes.  They can be installed through the Windows desktop, and made available
to all Windows applications, however OS/2 programs will not be able to use
them.

Q. Is there any way to print to a disk file, instead of printing?
A. Yes.  From the printer icon, press mouse button 2 (usually the right
button), then Open...Settings, then press the Output notebook tab. From the
Output panel click on the Output to file checkbox, then close the Settings.
Now when you send a print job to the printer, you will be prompted for a disk
file name to print to.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


═══ 7.8.5. Other OS/2 Device Driver Qs & As ═══

Q. In the README file that comes with OS/2 (in the root directory, viewable in
the Information folder), there is reference to a SCSI driver called
OS2SCSI.SYS, supposedly in \OS2, yet I can't find it.  Where is it?
A. This is a typo in the README file.  The name is actually OS2SCSI.DMD, not
.SYS.

Q. Is Super VGA (SVGA) supported by OS/2 2.0?
A. Yes, to some extent.  The following Super VGA boards have been tested and
found to work with OS/2 2.0 for DOS applications (only) that make use of SVGA
modes:

o  Orchid ProDesigner IIs by Orchid Technology (ISA and MCA versions)
o  Trident TVGA by Trident Microsystems, Inc. (8900b and c levels)
o  STB PowerGraph VGA by STB Systems, Inc.
o  Video Seven VRAM II, by Video Seven
o  Boca Super VGA by Boca Research Inc.
o  VGA Wonder XL Series by ATI Technologies, Inc.
o  8514 Ultra by ATI (Must be installed as an 8514 and as a primary display;
  it will default to high-resolution mode.  Do not install it as VGA.)

Additional SVGA support, as well as SVGA drivers for Windows and OS/2
applications will be shipping in a free update later this summer.  For more
information about SVGA support in OS/2 2.0, refer to the README file in the
Information folder.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


═══ 7.8.6. HPFS/FAT Qs & As ═══

Q. What is the maximum partition size supported by 2.0?
A. The maximum is 64GB (raised from 2GB in 1.3), but a practical usable size is
5-7GB per partition.

Q. What enhancements have been made to FAT partitions for 2.0?
A. Better performance, partly due to adding Lazy Write support, and Autocheck
support; both previously available only with HPFS.

Q. I have heard rumors that due to the performance enhancements made to "super
FAT" in 2.0 it is now faster than HPFS.  Is this true?
A. At one point during beta testing the enhanced FAT support was improved to
the point that it was faster than the early HPFS code; but subsequent tuning of
HPFS turned this back around.  In nearly all instances, HPFS is faster, has
better data integrity, and uses less disk space than FAT.

Q. In what cases would FAT be better than HPFS?
A. If you have the minimum 60MB hard drive, there may be no performance
advantage to HPFS (unless there are more than about 100-200 files in some
directories), access on an HPFS drive would be faster than FAT.), and the
savings in disk space produced (allocation unit) size used by HPFS would be
offset by the 300K disk overhead for an HPFS partition.  But HPFS would still
have the edge in data integrity, due to Hot Fixes.  In all cases of >60MB
partitions, HPFS has the performance edge.

Q. What was that about cluster size?
A. In a FAT partition, to get around a hard limitation of the number of
clusters (now called allocation units) available that produced the infamous
"32MB limit", the cluster size doubles every time the partition size doubles
(64MB partition=4K cluster; 128MB=8K; 256MB=16K; 512MB=32K; 1GB=64K; 2GB=128K).
And since a 5 byte batch file takes a minimum of 1 allocation unit, and since
on average each file wastes half of an allocation unit, large FAT partitions
waste a lot of space.  Because HPFS partitions always use 512 byte (1 sector)
allocation units, it wastes far less space, especially on large partitions,
than FAT.  Cases have been reported where a user reformatted a 1GB drive from
FAT to HPFS, restoring all the same files as before, and "recovered" 100MB of
previously wasted disk space.  (Obviously, the amount of wasted space depends
on how many small files are on the drive).

Q. What is a "Hot Fix"?
A. Hot Fixes are a mechanism whereby HPFS works around bad sectors on the disk
and temporarily uses "spare blocks" of disk space to store the data that would
normally have been written to the bad sector.  Then when the system is
rebooted, AUTOCHECK runs CHKDSK, marks the defective sector as bad, copies the
spare block to a good sector, and makes the spare block available for reuse.
In a FAT partition, on the other hand, the data would have been written to the
bad sector, and the user would not have known until the next time he tried to
access the data and received an error.  The corrupted data would have been
lost, at the least, and in the case of an indexed file all data after the bad
sector may have been lost.  If a binary file, such as a word processing
document, spreadsheet, or other, it is possible that the entire file would have
been rendered unusable.  This is the big data integrity aspect of HPFS.  (By
the way, when a Hot Fix is applied OS/2 presents an informational message to
that effect, letting you know what has occurred.)

Q. Under DOS, directory file names appear on the left side of the directory
listing.  But I installed OS/2 and now the names are on the right side?  Why?
A. File names in DOS and OS/2 FAT partitions are limited to 11 characters
(XXXXXXXX.XXX).  Because filenames in an HPFS partition can be up to 254
characters long, putting the names on the right side of the DIR list allows the
filenames to wrap to the next line (or more than one line) as necessary without
disrupting the orderly columns of file size, date, and other information.

Q. When I do a DIR of an HPFS partiton there is a column of numbers immediately
to the left of the file and directory names that doesn't appear on a FAT
partition directory listing.  What is this information?
A. It is the number of bytes of extended attributes associated with those files
and directories.

Q. Is there any way to format a diskette or optical disk drive to HPFS?
A. Only FAT formats are supported for removable media in OS/2 1.0-2.0.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.7. OS/2 2.x Communications Manager Qs & As ΓòÉΓòÉΓòÉ

Q. Has anything been done to improve LAN support?
A. Yes.  Adoption of the new LAN Adapter and Protocol Support (LAPS) provides
more efficient processing of the IEEE 802.2 and NETBIOS protocols with
increased performance in both cases across tsupported LANS.

Q. How many simultaneous workstations are supported through the Comm Manager
SNA Gateway?
A. 254 attached via either single or multiple adapters.  (Successful operation
in a given environment may depend on other factors, such as application load
and/or line speed, so the ability to exploit a full complement of 254
workstations should not be assumed for all cases.)

Q. What is the maximumnumber of LU sessions per gateway?
A. 254, the same as EE 1.3.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.8. OS/2 2.x Database Manager Qs & As ΓòÉΓòÉΓòÉ

Q. Does an ES Database Server support the use of EE 1.x clients?
A. Yes.  EE 1.2 or 1.3 SQLLOO and APPC clients may access shared databases on a
LAN, or host (via DDCS/2).

Q. What is the maximum number of configurable applications under ES Database
Server?
A. 252, however successful operation in a given environment may depend on other
factors, such as application load and/or available memory, so the ability to
exploit a full complement of 252 applications should not be assumed for all
cases.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.9. LAN Server 2.x Qs & As ΓòÉΓòÉΓòÉ

Q. Have there been any performance enhancements made to LAN Server 2.0?
A. Yes.  LS 2.0 is significantly faster than LS 1.3 for a number of reasons.
The Entry package includes a much improved LAN transport, at a lower price than
1.3.  In addition to faster LAN transport, the Advanced package includes
HPFS386 (32-bit).  As a result, the Advanced package is 2-5 times faster than
LS 1.30.1 for server functions, and 1.1 to 2.5 times faster for requester
activity.  The superior performance of the Advanced package is particularly
evident in heavy workload environments, such as the remote IPL of OS/2
Requesters.

Q. Does LAN Server 2.0 support the IBM Token-Ring 16/4 Busmaster Server
Adapter/A, unlike LAN Server 1.x?
A. Yes.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.10. Productivity Apps/Games Qs & As ΓòÉΓòÉΓòÉ

Q. Are any of these so-called "productivity" applications really useful, or are
they just "toys" to give us a chance to "play" with OS/2 before buying useful
software.
A.  Certainly it depends on your definition of "useful," but many of the
Productivity apps are adequate for the needs of many users, without additional
software.  The PM Term async communications program, Enhanced Editor, PM Chart,
calculator, notepad, Sticky Pad, alarm clock, calendar, to do list, Seek and
Scan file browser, and others can all be used productively.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


ΓòÉΓòÉΓòÉ 7.8.11. Miscellaneous OS/2 2.x Qs & As ΓòÉΓòÉΓòÉ

Q. How does the "free 60 day OS/2 support" work?
A. Users experiencing difficulty installing or using OS/2 2.0 may call the IBM
Defect Support Center at 800-237-5511.  From the time of the first call the
user gets 60 days of unlimited free technical and service support through this
number.  After 60 days, if the user wishes to cintinue the service they may
subscribe for $129 per year.

Q. How does this differ from SystemXtra?
A. SystemXtra is IBM's premier level of support for Personal System products,
including OS/2.  For more information about SystemXtra, call 800-IBM-XTRA.

Q. Can you explain how the "OS/2 BBS" works?
A. That can mean either of two different services.  1) There is an official
BBS, accessed through an 800#, offered on a subscription basis for a fee, and
only available to subscribers.  For more information about this BBS and what it
offers, call 800-547-1283; or 2) The IBM NSC BBS, which is open to the public,
for free but as a long-distance call for those outside the local dialing area.
It contains a number of "conferences" for the discussion of such products as
OS/2, DOS, PS/2s and Networking.  There is a large variety of downloadable
software and software patches available. In addition there are online bulletins
and databases of OS/2 software, non-IBM adapters for Micro Channel systems, and
local PC User Groups.  The number call for the IBM NSC BBS is 404-835-6600
(N,8,1).  Registration is done on the fly for new users.

Q. Q. How many COM ports does OS/2 2.0 support?
A. COM1-COM4 are supported on Micro Channel systems, and COM1-COM2 are
supported on AT bus (ISA) computers.

Q. I understand why I would want to limit the available drive letters on a LAN,
using LASTDRIVE= in CONFIG.SYS, but is there any reason to do so in a
standalone environment?
A. Yes.  Each drive letter that is available for use reserves about 100 bytes
of memory.  So limiting the drive letters to E:, for example, frees up about 2K
of RAM for other use.

Q. What versions of OS/2 support Extended Services 1.0?
A. OS/2 1.30.1 (CSD level 5015 or later), and OS/2 2.0.

Q. Does the OS/2 2.0 Developer's Toolkit include a kernel debugger and a PM
application debugger?
A. Yes.  Unlike the OS/2 1.3 toolkit which only includes a source code debugger
(CodeView), the 2.0 toolkit includes all three.

Q. Does the SWAPPER.DAT file ever shrink in OS/2 2.0?
A. Yes.  Unlike OS/2 1.3, where SWAPPER.DAT was always as large as the largest
block of data swapped to disk during the day (then reset to 512K at bootup),
2.0 expands and shrinks SWAPPER.DAT as needed, in 512K increments.

Q. Does OS/2 2.0 offer an UNDELETE command, like DOS 5.0?
A. Yes.  All deleted files are temporarily stored in a \DELETE directory in
each partition.  These files are purged upon bootup, so files must be undeleted
before shutting down the system.  Note: During installation the statement SET
DELDIR=... that defines the directory to hold the deleted files is installed in
CONFIG.SYS but disabled (to save disk space).  To activate UNDELETE, you must
remove the "REM " from the statement: REM SET DELDIR=....

Q. What is a "thunk" or "thunking layer?"
A. It is the code that allows 16-bit applications to run correctly in a 32-bit
address space.

To jump directly to the other sections, use the mouse, or Tab and Enter keys,
to select the section, below:

Qs & As
Configuration and Setup Qs & As
                                                        Communications Manager Qs & As
WPS/User Interface Qs & As
                                                        Database Manager Qs & As
DOS/Windows Sessions (VDMs) Qs & As                     LAN Server 2.x Qs & As
Printing/Printer Driver Qs & As
                                                        Productivity Apps/Games Qs & As
Other Device Driver Qs & As                             Miscellaneous Qs & As
HPFS/FAT Qs & As

To return to the OS/2 Qs & As header, double-click here.


═══ 7.9. IBM PS/2 Assistant Qs & As ═══

Q.  When I try to start multiple occurrences of VIEW.EXE (to display online
books like the OS/2 Command Reference or the PS/2 Assistant), automatically via
STARTUP.CMD, I get a message after the first one that it is unable to open the
input file.  How can I accomplish this?
A.  OS/2 1.30 ship-level had a bug that prevented this.  But 1.30.1 (CSD level
5015) resolves the problem.

Q.  Is there any way to change the colors used in the PS/2 Assistant?
A.  Yes.  The foreground, background, and highlighting colors used are
determined by your Control Panel color settings for Help Foreground, Help
Background, and Help Highlighting, respectively.  The only colors that can't be
changed, are the red headings, and the red keyword search results highlighting.

To return to the Technical Qs & As header, double-click here.


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

Footnotes:
                              
This - See how easy it is?  Now press the ESC key (or double-click on the icon
in the upper left corner of this window), to close this panel.


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

                              
Help - The Action Bar Help option may be selected for information on using the
Help facility.  In addition, you may press the F1 key for more information on a
specific topic.  Help is context-sensitive, so if you highlight a menu option,
and press F1, you will get help for that menu option.  Pressing F1 on an entry
panel will get help on those selection choices.


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

                              
Bookmark - When you place a bookmark on a topic, it is added to a list of
bookmarks you have previously set.  You can view the list, and you can remove
one or all bookmarks from the list.  If you have not set any bookmarks, the
list is empty.

To set a bookmark, do the following:

 1. Select a topic from the Contents.
 2. When that topic appears, choose the Bookmark option from the Services
    pull-down.
 3. If you want to change the name used for the bookmark, type the new name in
    the field.
 4. Click on the Place radio button (or press the Up or Down Arrow key to
    select it).
 5. Click on OK (or select it and press Enter). The bookmark is then added to
    the bookmark list.


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

                              
Search - You can specify a word or phrase to be searched.  You can also limit
the search to a set of topics by first marking the topics on the Contents list.
Multiple topics may be marked. To mark a topic, simply hold the Ctrl key and
click on a topic with the mouse.  You will notice that the topic highlighting
bar will be enlarged.  This indicates that the topic has been marked.  To
unmark a topic, just repeat this procedure.

To search for a word or phrase in all topics, do the following:

 1. Choose the Search option from the Services pulldown.
 2. Type the word or words to be searched.  (An asterisk (*) can be used before
    and/or after the search string to perform a wildcard search on a portion of
    a word.)
 3. Click on All sections (or press the Up or Down Arrow keys to select it).
 4. Click on Search (or select it and press Enter) to begin the search.
 5. The list of topics where the word or phrase appears is displayed. If you do
    not get a "hit" on a phrase, try just one of the words in the phrase. You
    may have better luck that way.  Double-clicking on a topic heading will
    display the contents of that section, and the search criteria will be
    highlighted in red, to make them easier to find.


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

                              
Print - You can print one or more topics.  You can also print a set of topics
by first marking the topics on the Contents list.  Multiple topics may be
marked.  To mark a topic, simply hold the Ctrl key and click on a topic with
the mouse.  You will notice that the topic highlighting will be enlarged.  This
indicates that the topic has been marked.  To unmark a topic, just repeat this
procedure.

To print the document Contents list, do the following:

 1. Choose Print from the Services pull-down.
 2. Click on Contents (or press the Up or Down Arrow key to select it).
 3. Click on Print (or select it and press Enter).
 4. The Contents list is printed on your printer.


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

                              
Copy - You can copy a topic you are viewing into a temporary file named
TEXT.TMP.  You can later edit that file by using the System Editor.

To copy a topic, do the following:

 1. Expand the Contents list and select a topic.
 2. When the topic appears, choose Copy to file from the Services pull-down.
 3. The system puts the text pertaining to that topic in the temporary TEXT.TMP
    file.

For information on one of the other choices in the Services pull-down,
highlight the choice and press the F1 key.


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

                              
Options - You can control the appearance of the Contents list.

To expand the Contents and show all levels for all topics, choose Expand All
from the Options pulldown. You can also press the Ctrl and * keys together.

For information on one of the other choices in the Options pull-down, highlight
the choice and press the F1 key.


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

D - D-shell connector


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

T - Terminator


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

* - T-RES chip removed


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

1 - Cable included with option


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

2 - Card to Option Cable (P/N 6451041; F/C 1041)


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

3 - Option to Option Cable (P/N 6451042; F/C 1042)


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

(4u) - The number of PM Objects is variable, because PM Objects may be variable
sizes. 900 objects is an approximation.  The actual number may vary.