OS/2 2.0 Product Considerations


 * 02/1992 Early Experience Program (EEP)
 * By IBM

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

These terms include: Terms denoted by a double asterisk in this booklet (**) are trademarks of other companies. Other trademarks appearing in this booklet are owned by their respective companies. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1992, all rights reserved.
 * Current PM
 * IBM Presentation Manager Operating System/2 PS/2
 * OS/2 Personal System/2
 * XGA WIN-OS/2
 * Microsoft, MS Bookshelf, MS Excel, MS Flight Simulator, MS Money, and Windows are trademarks of Microsoft Corporation.

Introduction
Welcome to the IBM* OS/2* 2.0 02/92 Early Experience Program (EEP). This offering, level 6.304E, is available to those customers who wish to test new functions that have been added to the Limited Availability (LA) product. Not only does this version contain the key functions that were announced for the LA offering at COMDEX/Fall 1991, (including DOS and Windows** compatibility and the OS/2 Workplace Shell, an easy-to-use, icon-based graphical user interface), this version also supports: Application developers using pre-release code at level 6.177 may choose to maintain their development environment on 6.177 rather than move to 6.304E. A development environment on 6.304E requires a Developer's Toolkit at level 6.304E. When this product becomes generally available, it is IBM's intent to additionally: This booklet describes those product considerations about which you should be aware as you install and use this version of the product. IBM will continue to make enhancements before the product becomes generally available, and we welcome your feedback. This booklet also includes helpful tips and techniques. We recommend that you read this booklet before installing and using the system. This document is a supplement to OS/2 2.0 Getting Started, OS/2 2.0 Using the Operating System,  OS/2 2.0 Installation Guide, and OS/2 2.0 Quick Reference. If you are migrating from OS/2 Version 1.3 or Windows Version 3.0, we recommend that you read OS/2 2.0 Migrating to the OS/2 Workplace Shell.
 * DOS, Windows, and OS/2 applications running in windows, side-by-side, on a single desktop, including Windows applications that run in a PM* window when the primarydisplay adapter is configured for VGA
 * A superior platform for customer networking and communications environments, including a graphical login/logout and connection to a LAN, and an ability to browse file server devices (such as printers and disks).
 * Provide a superior operating environment through system integrity, performance, interoperability, and ease of use when running DOS, Windows, and OS/2 applications
 * Run on Intel 386SX and higher systems.

Installation
OS/2 Version 1.2, OS/2 Version 1.3, DOS, or Windows.
 * If you are installing this version over an earlier OS/2 2.0 level, select the Format your disk during installation  option. This process ensures that any earlier-level files will not be left inadvertently on your hard disk. Be sure to back up any files that you want to save before starting the OS/2 2.0 Installation process.
 * If you install this version, you will have to select the Format your disk during installation  option when you install the product when it becomes generally available.
 * You do not have to format your disk if you are installing over
 * When first prompted to restart (reboot) your system after installation, note that the restart can take about 5 minutes, allowing the OS/2 Workplace Shell to initialize itself.
 * If you are installing using a response file, you cannot use the value for Migrate Applications  provided in the sample response file. If you wish to migrate existing applications, you must select the Migrate Applications object located in the System Setup folder after OS/2 2.0 has been installed.
 * Be sure, if you install a mouse, that it is connected whenever you start your system.
 * This product supports two display adapters. If the secondary display adapter is an XGA* or 8514/A adapter, it will run in VGA mode.
 * Specific small computer systems interface (SCSI) adapter support for selected SCSI adapter interfaces is included. The device drivers which produce this support are installed in your \OS2 directory, as follows:

SCSI Adapter Filename (in \OS2 Directory) Adaptec 152x AHA152X.ADD Adaptec 154x AHA154X.ADD Adaptec 164x AHA164X.ADD Future Domain TMC-8xx FD8XX.ADD Future Domain TMC-16xx FD16-700.ADD Future Domain MCS-600 FD16-700.ADD Future Domain MCS-700 FD16-700.ADD You can manually install this support by adding a BASEDEV=filename statement into CONFIG.SYS. For example, if you have an Adaptec 1542 SCSI adapter in your system, you can install OS/2 support by including the statement BASEDEV=AHA154X.ADD at the end of your CONFIG.SYS file. Make sure you do not include a drive letter or path in this statement.
 * Note: For the Future Domain TMC-8xx series, the BIOS must be enabled in order for these 8-bit adapters to function.

The CONFIG.SYS statement BASEDEV=IBMINT13.I13, included in the CONFIG.SYS file (by default), replaces the DSKBIOS1 function. No special action is required to use any other SCSI hard files. They are supported through the IBMINT13 generic DASD device drivers.

Product Considerations
IBM will continue testing and enhancing this product before it becomes generally available, and we welcome your feedback. It is our intent to address the limitations described in this Product Considerations section before this product becomes generally available. Where available, we have provided temporary work-arounds.

Performance
IBM strongly recommends that you do not use this version of the OS/2 2.0 product for performance benchmarking. We will continue to improve performance before the product becomes generally available. IBM's performance objectives for the OS/2 2.0 product are to run DOS and Windows applications equal to or better than they run in their native environments and to run OS/2 applications equal to or better than they run on OS/2 Version 1.3. Based on IBM's measurements of application performance on this version of the product, IBM believes that from a user's perspective, on balance, these performance objectives have been met. Users may experience slower response times when using some system functions, such as loading programs, starting sessions, and switching between sessions. A minimum of 6MB of system memory will improve performance.

OS/2 Workplace Shell

 * The OS/2 2.0 product was designed for use with a mouse. We recommend that you operate the system with a mouse to ensure consistent results.

To ensure that an object automatically starts when the system is restarted, move the object from its original folder to the desktop. Then, if the object is open when the system is shut down, it will start the next time the system is started.
 * In some instances, Help is not available from the Help  push button or the F1 key. Refer to the Master Help Index for help on specific topics.
 * Copying a folder containing program objects onto a diskette appears successful, but if you try to start or copy the programs from diskette onto another system under this version of the product, the program objects will not be present. (When the OS/2 2.0 product becomes generally available, program objects will not be allowed to be dropped on diskettes).
 * The pop-up menu for multiple-selected items does not always display the actions that are common to all the selected objects.
 * The size and position of some windows may not be restored after you restart your system.
 * Program objects started from command files must have the proper .BAT or .CMD extension specified.
 * Copying a read-only folder into another folder creates two folders.
 * Displaying an object in Details view does not always display current information about the object. The last access and modification dates may not be current. The column titles may be displayed for file-type objects when none are present in the folder.
 * The hard-disk icon in the Drives folder represents tape drives and CD-ROM drives in addition to hard disks.
 * The Undo option on the Associations page in the Settings notebooks for a Program object and the Color Palette object are not operational.
 * On systems with an XGA adapter connected, you must close each section of the Tutorial before moving to the next section.
 * The Special Needs page of the Keyboard object has limited customization capabilities.
 * Make sure you select Shut down before you turn off your computer or you might lose data or the position of your icons.
 * The Settings notebook for ]SystemØ in the System Setup folder has two pages with a ]windowØ tab. The page with the radio buttons for Animation should be used. The other page will be removed.
 * If any objects, including folders and programs, are open and running when the system is shut down, only those that were started directly from the desktop will restart when the system is restarted.

Desktop Customization
Shell to understand the usability features of your new desktop. The book explains how to make OS/2 2.0 look like OS/2 1.3 or Windows 3.0.
 * If you customize your OS/2 2.0 Desktop to OS/2 1.3 or Windows 3.0, we recommend you read Migrating to the OS/2 Workplace

DOS Support

 * When you start a specific version of DOS from a diskette, be sure to insert the diskette in the drive before you start the session.

Windows Support

 * Before cutting and pasting to the OS/2 system clipboard from or to Windows programs, you must start the Clipboard Viewer located in the Productivity folder.


 * Bit maps and metafiles greater than 200KB in size will not be transferred successfully to the public clipboard.
 * Before running WIN-OS/2* in real mode, reset the DOS setting EMS_ MEMORY_ LIMIT to 0 for the VDM to be used.
 * If you choose to copy an existing Windows desktop configuration, it may be necessary to change the MOUSE.DRV statement in SYSTEM.INI. If you are currently using a mouse that creates a statement other than MOUSE.DRV=MOUSE.DRV in the boot.description section of the C:\OS2\MDOS\WINOS2\SYSTEM.INI file (where C: is the startup drive), you will need to change the statement to read MOUSE.DRV=MOUSE.DRV


 * Be certain that Windows applications have completed their initialization before switching back to the OS/2 desktop.

OS/2 Printing

 * Ensure that all print job settings notebooks are closed before closing a print object icon or detail view.

Numeric Coprocessor Emulation
This version of the product will include a numeric coprocessor emulator for use in machines that do not have a numeric coprocessor installed. Currently, we are continuing to improve the accuracy of the results obtained from this emulator. The results obtained from the emulator provided in this version of the product may contain errors and cannot be guaranteed. Examples of computations which may lead to erroneous results are those involving high-precision operations, operations combining high-precision operands, boundary conditions such as very large or very small quantities, rounding, and underflow. If you intend to use floating-point operations in mission-critical applications, you must use an 80387 math coprocessor. Installation of an 80387 math coprocessor requires a stepping level of B1 or higher on the 80386 microprocessor. If you are in doubt about whether your application uses floating-point operations, contact the application vendor.

Local Area Network Support
Refer to Product Supplemental Information for LAN Server Version 2.0 for current information regarding network support.
 * Opening a network group folder in a tree may be slow if your network contains many servers. It is recommended that you use icon view instead.
 * The network folder cannot be moved from the desktop.
 * The *Alias server folder displayed by LAN Server 2.0 is not functional.
 * If you are a LAN Server Network Administrator, do not change the printer configuration on a server once it has been shared.
 * If you log in as a LAN Server Network Administrator and some functions are not available, display the pop-up menu and select Refresh. The administrator functions are now available.
 * Occasionally, the pop-up menu of a network object might show login when you are already logged in, or logout  when you are already logged out. Click on login/logout  and redisplay the pop-up menu.
 * In this version, do not attempt to access DOS LAN requesters from WIN-OS/2 when you are running a specific version of DOS in a DOS session.

Peripheral Devices
For example, when the Serial Port is set to SERIAL 2 in the hardware configuration, its corresponding Serial Transmit Arbitration Level should be set to DEDICATED 3. The Serial Receive Arbitration Level must be set to DEDICATED 4. When both levels of a serial port are set to Shared, data communication and printing from the COM port with Enhanced set to ON will not operate properly. Run the Setup/Diagnostics diskette and follow the instructions on the screen to change your hardware configuration.
 * When using your Logitech mouse when running in standalone DOS, you may experience problems with your mouse under OS/2. If so, unplug and then plug in your mouse, or, after shutdown, power down and then power up your system.
 * When using the COM port on a PS/2* Model 90 or 95 with Enhanced set to ON, be sure that the Serial Transmit and Serial Receive Arbitration Levels in the hardware configuration are set to Dedicated, with different numbers specified.


 * The OS/2 2.0 product has been designed to allow most DOS and Windows applications to run more reliably than in their native environments.

One or more DOS applications typically can be run concurrently in windows while in the background, although there are some performance trade-offs when DOS graphics applications are run in a window. To realize the full benefits of the OS/2 2.0 product, run these applications in full-screen sessions. There are three cases in which DOS graphics applications may be suspended (receive no processor time) when running in the background:
 * In the first case, a DOS multiplane application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended, regardless of the graphics adapter installed, if any other DOS application is running in the foreground in a full-screen session.


 * In the second case, a multiplane DOS application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended when a Presentation Manager session is running in the foreground in XGA mode. Currently, this situation occurs even if you have an Extended Graphics Array (XGA) and a Video Graphics Array (VGA) adapter connected to your system.


 * In the third case, a multiplane DOS application that uses 1024x768x16 graphics mode will be suspended when a Presentation Manager session is running in the foreground in 8514/A mode.

Note that suspending DOS applications running in the background generally poses no problem unless the applications are timing-dependent, such as communications or process-control applications. In these cases, suspending them may cause them to fail. Avoid this situation by running these applications in the foreground in full-screen sessions only. If they are graphics applications, run them only in a single-plane mode, such as 640x200x2, 320x200x256, or 640x480x2, in full-screen sessions. Note also that for WIN-OS/2 sessions, set the VIDEO_ SWITCH_ NOTIFICATION DOS setting to ON to avoid having Windows programs suspended when running in the background.

Personal Computer Manufacturers - Compatibility
The following list depicts those Personal Computer Manufacturers' systems that have passed IBM's compatibility test with the current OS/2 2.0 EEP product. IBM's compatibility test verifies (18) key functions of the OS/2 2.0 operating system. These test results are based on selected model configurations provided by the PCM to IBM. This list is preliminary, and IBM will continually update the list as we proceed with our testing. Current information will be disseminated on various electronic forums and bulletin boards. 386/25þ REPLY D32-486-250 Model RS/25Cþ REPLY 486-33 486/33T 386S/25 8267þ SIEMENS NIXDORF 8290þ TATUNG TCS8640S Model 2014þ TATUNG TCS9600T Model 1000þ TOSHIBA T5200/100 Model 2000 Z-486SX/25E Note: The compatibility test information provided herein is provided for information purposes. IBM MAKES NO WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE OPERATION OF THE PERSONAL COMPUTERS LISTED.
 * ACER 1125Eþ COMPAQ 486/50L
 * ALR BusinessSTATIONþ COMPUADD 320SC Model 486SX/20 Model 101 A002
 * ALR BusinessSTATIONþ COMPUADD 325 Model 386DX Model 1 A000
 * ALR BusinessVEISA 486/33þ COMPUADD 333T Model Model 101 A005
 * ALR BusinessVEISA 386/33þ COMPUADD 433E Model Model 1 A005
 * ALR MPS Modular 386/33þ CUMULUS GLC 486DX/33
 * ALR MPS Modular 486/33þ CUMULUS 486SX/20
 * ALR POWERPRO 33/486þ CUMULUS GLC 386SX/20 Model SMP 128/150þ CUMULUS GLC 386DX/25
 * ALR PowerFlex 20Xþ CUMULUS GLC 386DX/33
 * ALR PowerFlex Flyerþ DELL PowerLine 433DE
 * AMAX PC/486-33þ DELL System 320SX
 * APRICOT LS 386SX-20 w/cache
 * APRICOT Qi 486-25þ DELL System 333D
 * AST Premium II 486SX/20þ DELL System 486D/25
 * AST Premium II 386/33þ DELL System 325P
 * AT&T SAFARI NSX/20þ DELL System 320N+
 * COMPAQ DESKPRO 386/25Eþ DYNEX 386-25
 * COMPAQ DESKPROþ EVEREX 486/33E 386/25M EX0-2904D-01EL
 * COMPAQ DESKPRO 386/Sþ EVEREX 486/33
 * COMPAQ SYSTEMPRO EX0-2904D-B1 Model 3002þ EVEREX 386/33
 * COMPAQ SYSTEMPRO EX0-2804-000L Model 3000þ GRID GRIDCASE 1550sx
 * GRID MFP/420sþ OLIVETTI P750 Model
 * GRID 386sx/MFP20 XP2670
 * HERTZ 486/33þ REPLY D32-386-330 Model
 * HEWLETT PACKARD Vectra 32MCA
 * HEWLETT PACKARD Vectra 32MCA
 * HEWLETT PACKARD Vectraþ SAMSUNG DeskMaster
 * INTEL LP386SX/20þ SIEMENS NIXDORF
 * MEMOREX-TELEX Model PCD-3Msx/20
 * MEMOREX-TELEX Model PCD-3Bsx
 * NCR SYSTEM 3300/3421þ TATUNG TCS8800D
 * NCR SYSTEM 3300/3432þ TOSHIBA T3100SX
 * NCR SYSTEM 3300/3433þ ZENITH Data Systems
 * NCR SYSTEM 3400 Modelþ ZENITH Data Systems 3000 Z-486/33E
 * OLIVETTI M300-10 Modelþ ZEOS 386DX-33CT XP2655þ ZEOS 386SX-208DT
 * ZEOS 486DX-33T
 * In order for microchannel systems with ESDI hard disks to operate properly:

1. On OS/2 Diskette 1, rename ABIOS.SYS to ABIOS.HLD.

2. Create a null file called ABIOS.SYS. For example: COPY CON: ABIOS.SYS blank space Enter PF6 Enter

3. Begin your installation. Change BASEDEV=IBM1FPLY.ADD to BASEDEV=IBM1FLPY.ADD /PS2 and Change BASEDEV=IBM2FLPY.ADD to rem BASEDEV=IBM2FLPY.ADD After Installation Diskette 4: 1. Put the Installation Diskette in drive A. 2. Reboot.
 * An ABIOS timing condition between OS/2 2.0 and the ALR MPS systems can occur during operation. To ensure this condition is not encountered, IBM and ALR have agreed to a temporary solution. The following change should be made to the CONFIG.SYS file on Installation Diskette 1 and after installation, ensuring that the same change appears in the CONFIG.SYS file on the hard disk.

3. Continue until Diskette1 introduction. 4. Escape (Esc) from Diskette1 to the A: prompt.

5. Make the same change to C:\CONFIG.SYS.

6. Copy IBM1FLPY.ADD to C:\OS2 directory.

7. Remove the diskette.

8. Reboot and continue the installation.

Tips and Techniques

 * You can improve the performance of some applications by adjusting the DOS settings. If the application does not use extended or expanded memory, these values can be set to zero:
 * IDLE_ SENSITIVITY
 * EMS_ MEMORY_ LIMIT
 * XMS_ MEMORY_ LIMIT.

For more information on DOS settings, refer to the OS/2 2.0 online Master Help Index.

DEVICE=C:\OS2\APPS\SASYNCDB.SYS For 80386 compatibles, install the SASYNCDA.SYS driver: DEVICE=C:\OS2\APPS\SASYNCDA.SYS When files are transferred to or from a drive other than drive C in PM Terminal, the dialog box may not display all the subdirectories. To correct this problem, select the C drive and then reselect the correct alternative drive.
 * If you want to use the asynchronous communications device interface (ACDI) support in the OS/2 2.0 mini-application called PM Terminal, you must edit your CONFIG.SYS file and then restart your system. For IBM PS/2 computers, install the SASYNCDB.SYS driver:


 * Using the OS/2 Enhanced Editor:
 * The maximum line length is 237 characters.
 * When naming your files, you are unable to use blanks and some nonalphanumeric characters, such as double quotes, apostrophes, and brackets.


 * The FIND option in the OS/2 System Editor does not display the results of a search. To view these results, press Alt+F6 to move the focus from the Find dialog box to the text entry area.

Use the IFS= statement to define the maximum I/O record size that can be cached using the HPFS.
 * We have improved the high-performance file system (HPFS) by adding new options that users can specify. Also, we have improved both the HPFS and the File Allocation Table (FAT) file systems by expanding the read-ahead logic for small-record input/output (I/O) of less than 512 bytes in size. These enhancements are expected to provide faster performance when sequential reads are performed.

If you receive an error indicating that your WIN-OS/2 session has insufficient memory, you can try adjusting the memory to 3MB or 4MB. However, this setting should not be set high arbitrarily because the OS/2 swap file (SWAPPER.DAT) will be allowed to grow in proportion to the amount of additional memory you allocate. The optimum size of the swap file is relative to your environment. If the swap file is located in its own partition, it is preferable to be conservative when you specify the size of that partition. These specifications may be helpful. 4MB system : 7 to 12MB 6MB system : 5 to 10MB 8MB system : 3 to 8MB
 * By default, 2MB is the amount of memory allocated to each WIN-OS/2 session. Currently, we recommend 2MB for each WIN-OS/2 session you plan to run.


 * OS/2 allows you to run a specific version of DOS in a DOS session along with the OS/2 2.0 product. This feature helps to ensure compatibility with applications, such as block device drivers, that otherwise would be incompatible with the OS/2 2.0 environment. Currently,
 * If you have already started a version of DOS from a diskette, you will not be able to start another version of DOS from your hard disk.
 * You may experience problems when starting, or booting, DOS from your A drive or from other drives.
 * You cannot start multiple copies of a specific version of DOS using a single image. To make multiple images, create them on your hard disk using the VMDISK.EXE utility located in the \OS2\MDOS\ directory. Change the DOS_ STARTUP_ DRIVE DOS setting to start from the image you created.


 * When asked to specify a directory from which to add fonts, do not specify the C:\OS2\DLL path, where C: is your startup drive.

Temporary Limitations
IBM has tested many DOS, Windows and OS/2 applications. Most of them run unchanged, but some require special attention when running on this version of the product. IBM currently plans to address these limitations before the OS/2 2.0 product becomes generally available. Where available, we have suggested temporary work-arounds.

Other Limitations
Some categories of applications, usually because of their design or because they use undocumented interfaces, will not operate properly with the OS/2 2.0 product. IBM is in the process of contacting these vendors about resolving these incompatibilities. Some vendors have already developed a fix and are willing to make the fix available. These have been noted. These five categories of applications include:
 * Applications that use the DOS Protect-Mode Interface, the Expanded Memory Specification (EMS), or the Extended Memory Specification (XMS) are supported. Other DOS extenders, such as the virtual control-program interface (VCPI), that require exclusive access to the 80386 control registers, are not supported because they could violate the integrity of the system.
 * Functions in applications that directly address the physical sectors to perform write operations are not supported because these operations could violate the integrity of the system.
 * Some Windows applications invoke the Windows mini-applications to run a subset of function. If you did not format your hard disk when you installed this version of the product, and if you already had Windows Version 3.0 installed, these mini-applications will be invoked automatically.
 * Windows applications that require enhanced mode
 * DOS or Windows applications that use undocumented DOS or Windows interfaces

Improvements from the LA Product
Some of the restrictions identified in the LA Product Considerations document have been corrected in this EEP version of the product. These items include:

Installation Improvements

 * A response file can be used to install OS/2 2.0. See the OS/2 2.0 Installation Guide for details.
 * The DSKBIOS1 function discussed in the LA document is now included in the BASEDEV=IBMINT13.I13 CONFIG.SYS statement, by default. No special actions are required to operate SCSI devices.
 * If you select not to install some Productivity and Games programs, blank icons representing these programs will no longer be installed.
 * DOS LAN requesters no longer require that DOS have control of the system. They will run on a booted version in a VDM.
 * The time needed to install the OS/2 has been reduced.

OS/2 Workplace Shell

 * You can delete multiple objects individually, or you can delete them all at one time.
 * An icon representing Drive A will appear on the desktop.
 * Double-clicking on this icon will now provide access to Drive A.


 * The settings notebooks for the Drives objects are now operational when displayed from the object's pop-up menu.
 * Actions performed on fonts no longer produce inconsistent results.
 * The time needed to shut down the system has been reduced.

Windows Support

 * The following items are now described in the OS/2 2.0 online or hard copy documentation:
 * Follow the manufacturer's instructions to install Windows applications under the OS/2 2.0 product. If the installation is unsuccessful, start a full-screen DOS session and try again. Another alternative is to choose Run from the File menu of the WIN-OS/2 Program Manager.
 * To start Windows applications, do one of the following:
 * Install them as separate objects on your desktop.
 * Select Run from the WIN-OS/2 Program Manager.
 * Type WINOS2 followed by the program name in a full-screen DOS or OS/2 session.
 * Note that you cannot run DOS applications using Run from the File menu of the Program Manager. They must be run from the (OS/2) desktop.
 * OS/2's Dynamic Data Exchange (DDE) feature allows you to dynamically update and change data in one running program and effect those changes in another running program.

Note that before performing DDE between an OS/2 and a Windows application, you must start the Data Update object in the Productivity folder.


 * Not all clipboard and DDE data formats are transferable to the public clipboard or shared between Windows and PM applications.


 * You must run Windows applications in a single WIN-OS/2 session if you are using private Windows data formats.


 * A set of WIN-OS/2 printer drivers is included with this product. When you create an OS/2 printer, you will be asked if you want a Windows-equivalent configuration, if one is available. You also will be asked to install a WIN-OS/2 printer driver.

If a WIN-OS/2 printer is not automatically installed during OS/2 installation, you can install WIN-OS/2 printer drivers from the WIN-OS/2 Control Panel. WIN-OS/2 printer drivers are located on the Printer Driver Diskettes 1-6. If you want to use a Windows printer driver that is not automatically installed by OS/2, or is not shipped with OS/2, configure the Windows printer driver to use an OS/2 port that has the IBMNULL printer driver associated with it. The IBMNULL printer driver is installed during system installation. If IBMNULL is not displayed in the list of available printer drivers, use the Install pop-up menu choice on an existing printer driver to display the Printer Driver Install dialog box. 1. Insert Printer Driver Diskette1 in your diskette drive; then select Refresh. 2. Select IBMNULL from the list; then select Install. 3. Select Cancel; then select IBMNULL for the Printer object. Note that LPT1.OS2 and LPT2.OS2 support better performance than LPT1 or LPT2 when configuring from the WIN-OS/2 Control Panel.
 * Performing DDE between two Windows applications running in separate sessions or between a Presentation Manager (PM) and a Windows application currently no longer cause the Windows application running in the background to be suspended (receive no processor time).
 * If the Windows clipboard is set to public, requests to print the screen from a Windows session (using PrintScreen) are now successful.
 * The contents of the clipboard are no longer lost if you exit from a Windows application during a cut, copy, or paste operation.
 * Bit-map files and metafiles can be converted compatibly between Windows and PM applications when operating in all video modes.
 * To install your Windows LAN device drivers and configure WIN-OS/2 to use these device drivers, run SETUP.EXE from the WIN-OS/2 full screen session.
 * It is not necessary to define a Windows printer if you are installing Windows multimedia extensions under this version.
 * Like Windows, the OS/2 2.0 product automatically installs corresponding Windows mouse and printer drivers when you select a Presentation Manager* mouse driver.
 * On systems with an XGA adapter connected, starting Windows from a full-screen session and then closing the session no longer causes the screen to behave inconsistently.

OS/2 Printing

 * You can now delete any printer device drivers from the Printer object. Doing so no longer causes subsequent attempts to reinstall these drivers to fail.

Peripheral Devices

 * The DOS DISKCOPY command now operates properly when used on an external 5 1/4-inch diskette drive.

Tips and Techniques Improvements

 * The OS/2 mini-application called Cat and Mouse is now operational.
 * Closing a DOS or Windows session from the Window List or from a pop-up menu, while an application is running in that session, no longer causes subsequent attempts (by these sessions) to access devices to fail.
 * HPFS performance for 2KB and 4KB I/O has been improved.
 * All networking applications may now start from the Drives objects.
 * The following items are now described in the OS/2 2.0 online documentation:
 * Adjusting these DOS settings for Windows full-screen objects or other Windows program objects, may boost the performance of applications running in Windows sessions.
 * KBD_CTRL_BYPASS = CTRL_ESC
 * This setting allows the WIN-OS/2 Program Manager to recognize a Ctrl+Esc and then display the Task List.
 * MOUSE_EXCLUSIVE_ACCESS = ON
 * This setting allows WIN-OS/2 (in place of the PM) to control the Mouse pointer if you run a WIN-OS/2 session in a window.
 * VIDEO_SWITCH_NOTIFICATION = ON
 * This setting notifies a DOS program to do its own save and restore of the video state.
 * VIDEO_8514A_XGA_IOTRAP = OFF
 * This setting must be set so that DOS and WIN-OS/2 sessions can continue to run when in the background (for systems with 8514/A and XGA adapters only).
 * The performance of DOS applications is optimal when running in full-screen sessions. You can press the Alt+Home keys to run your DOS applications in full-screen DOS sessions.
 * If you are running Windows and have an 8514 Windows video adapter (8514.DRV) installed, do not change the default settings for VIDEO_SWITCH_NOTIFICATION and VIDEO_8514_XGA_IOTRAP.

Applications Considerations Improvements
The following applications, restricted in the LA version of this product, are now supported:
 * Borland C++ 3.0
 * Chipchat
 * Control Room 1.0
 * Crosstalk IV
 * Dynacomm
 * Framework III Version 1.1
 * IBM Current*
 * MS Flight Simulator
 * MS Word for OS/2
 * New Wave 3.0
 * PC3270
 * PC Paintbrush IV
 * PFS First Choice 3.1
 * Superprint 2.0
 * Terminator
 * Winfax Pro 2.0