OS/2 2.0 README (03/1992)

OS/2 2.0 README (03/92) In OS/2 Version 2.0, IBM performed the most comprehensive testing ever done on any version of the OS/2 operating system. This included extensive DOS, Windows, and OS/2 application compatibility validation in addition to stress, usability, and performance testing. While most users will not require the information in this README, it contains unique application compatibility information and other useful tips and techniques that might be helpful in specific situations. Some of the information is intended for the more advanced user or for the user already familiar with various functions provided with OS/2 2.0. The information was largely collected during the final comprehensive system and compatibility testing phases, which involved over 30,000 users of early versions. It was not finalized before the publications were printed and we want to share this information with you. If you want to search for a specific topic, click on EDIT in the menu bar above, then on FIND in the menu. For more information about searching, and for other help related to the System Editor, click mouse button 1 on HELP, then click on HELP INDEX. The scope of this information includes:
 * Service and Support Information
 * Installation
 * OS/2 Workplace Shell
 * Application Compatibility
 * Performance
 * Windows Version 3.0 Programs Support
 * Video/Graphic Support
 * Hardware Considerations

SERVICE AND SUPPORT INFORMATION
OS/2 2.0 users can access electronic support for current technical information and exchange messages with other OS/2 users, 24 hours a day. If you run into problems or simply need a question answered about OS/2 2.0, there are two ways to get help electronically: the new IBM BBS (Bulletin Board System) and CompuServe. For information about registering for and accessing the IBM OS/2 BBS, call 1-800-547-1283. For CompuServe membership information, call 1-800-848-8199, and ask for representative 239. If you already are a CompuServe member, simply type "GO IBMOS2" at the ! prompt to access the IBMOS2 forum.

INSTALLATION
IBM2*.ADD *O2.SYS BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2SCSI.ADD If you are installing OS/2 2.0 in a Micro Channel computer: IBM1*.ADD *01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD To change a touch device to a different pointing device, select "Mouse" on the System Configuration window, and then select the pointing device you want to use. Finally, select the OK push button.
 * After installation, and before you run any DOS or Windows program, we recommend you shut down your system.
 * Support for the High Performance File System (HPFS) was not added to your system if you installed OS/2 2.0 using either "Install all features" or "Install preselected features," and your system:
 * Has 6MB or less of memory, and
 * Did not previously have HPFS support.
 * To install HPFS support, use the Selective Install object in the System Setup folder.
 * If you select "Automatically update CONFIG.SYS and AUTOEXEC.BAT," some device-driver statements might not be copied to your new CONFIG.SYS file with a REM statement as stated in the "Installation Guide." Select instead, "User edit CONFIG.SYS and AUTOEXEC.BAT" to copy these device drivers to your new CONFIG.SYS file.
 * The Setboot utility program supports an immediate-restart function that will restart the system to the specified drive without going through the Boot Manager Menu. The parameter is /IBD:DRIVE, where "DRIVE" is the letter of a startable partition (for example, SETBOOT /IBD:E). This example would start the logical drive E without displaying the Boot Manager Menu.  If the Boot Manager is not present, then only drive C can be specified.
 * If you are using Boot Manager, and one of your partitions contains OS/2 Version 1.3 with Dual Boot, copy BOOT.COM from the OS/2 2.0 \OS2 subdirectory to the OS/2 1.3 \OS2 subdirectory.
 * To enable the UNDELETE command, delete "REM" from the beginning of the following statement in the CONFIG.SYS file: REM SET DELDIR=
 * To use the ACDI support provided by PM Terminal, delete "REM" from the beginning of the following statement in the CONFIG.SYS file: REM DEVICE=d:\OS2\APPS\SASYNCDx.SYS where "d:" is the drive and "x" is either A or B. Then restart your system. If you selected the PM Terminal program with either "Select features and install" or the Selective Install object in the System Setup folder, the ACDI support is activated and you do not need to change the CONFIG.SYS file.
 * Following is additional information for the "Copying the Response File to a 5-1/4 Diskette" section of Chapter 5 in the "OS/2 2.0 Installation Guide." If you are installing OS/2 2.0 in a non-Micro Channel computer:
 * Delete the following additional files from Installation Diskette 1:
 * Delete the following from the CONFIG.SYS file:
 * Delete the following additional files from Installation Diskette 1:
 * Delete the following from the CONFIG.SYS file:
 * IBM's testing of a beta Windows Version 3.1 environment indicates that the OS/2 2.0 Installation program will not configure your WIN-OS/2 desktop. If the Windows directory that is found is from a Windows Version 3.1 environment, either change the DOS PATH to point to a Windows Version 3.0 environment, or select the default environment.
 * If you have configured your system for a touch device, the System Configuration window in the Selective Install program will incorrectly show "PS/2 Style Pointing Device" as the default mouse selection.
 * Occasionally, the Migrate Applications program might not find all applications. In this case, retry the Find Programs operation.

WORKPLACE SHELL
System or Shredder), there is a function that will allow you to reset the desktop to its default configuration. To perform this function, do the following:
 * Because of device-resource limitations, when too many applications are open, or when too many bit maps are visible on the screen, new icons, tabs, or other bit maps might not be drawn. You can fix this situation by closing unused folders and applications so their device resources can be used by other processes.
 * In certain low resource situations, the final shutdown message might not appear after a shutdown is performed. To ensure that shutdown has completed, wait until all disk activity stops before powering down or restarting your computer.
 * If you change the title of an object from within the Find Results folder, the name of the original object will be changed.
 * If you formatted your installation drive with HPFS, you might not be able to access files in the Desktop folder from DOS or Windows applications.
 * In the Help information for Find, disregard any references to page 2.
 * If you encounter a situation in which you cannot restart the operating system, press and hold the left Ctrl, left Shift, and F1 keys. This disables the automatic program startup feature of the desktop. Press and hold the keys when the white screen first appears and hold them down until the icons appear on the desktop.
 * If you start the operating system and you do not see some of the system icons (such as OS/2
 * WARNING: USING THIS FUNCTION WILL REMOVE ANY DESKTOP CUSTOMIZATION YOU HAVE DONE SINCE YOU INSTALLED THE OPERATING SYSTEM.

1. Restart the computer. 2. Before the first OS/2 Logo panel appears, hold down Alt+F1 for 20 seconds. When the operating system was installed, certain system files (CONFIG.SYS, OS2.INI, and OS2SYS.INI) were placed in the \OS2\INSTALL subdirectory. When you perform the recovery function described above, the current versions of those files are automatically renamed and are replaced by the default installation versions. If you have a STARTUP.CMD file, that file is also renamed, causing the startup feature to be deactivated.
 * If you were previously using the OS/2 2.0 Limited Availability version and you installed OS/2 2.0 without reformatting, you might not be able to delete existing associations. If this occurs, make a copy of the program object and discard the original.
 * If you were previously using the OS/2 2.0 Limited Availability version and you installed OS/2 2.0 without reformatting, you must update the path and file name of
 * OS/2 System Editor to \OS2\APPS\E.EXE
 * Clipboard Viewer to \OS2\APPS\CLIPOS2.EXE

PRINTING

 * If you plan on using an HP PaintJet printer to print bit maps, make sure you set the printer-specific format check box in the queues option of the printer object.
 * If you are going to install the HP LaserJet printer driver over an existing driver, be sure to delete all the old *.FNT files FIRST. You can do this by deleting the printer driver from the Workplace Shell printer object and responding "Yes" when asked if the driver files should be deleted from the hard disk.
 * If you use the "print while spooling" printer-object setting, and your printer stops printing, close the job that was printing.
 * To improve the performance of viewing a network printer object, use a long refresh interval or set the interval to 0 (no refresh).
 * If you move the network object from the desktop to another folder, the network printer object template will not appear the next time you start the system. To make it reappear, move the network object back to the desktop and restart the system.
 * If you delete a printer definition, use the Delete option of the pop-up menu.

APPLICATION CONSIDERATIONS
Most DOS, Windows, and OS/2 programs run under OS/2 2.0 without any modification. A few need specific attention, such as changes to DOS settings, for optimum performance. Some categories of programs, however, do not work correctly with OS/2 2.0 because of their design, or because they use undocumented interfaces, or because they perform restricted activities. The following list identifies these categories of programs. 1. DOS extenders that require exclusive access to the 80386 control registers, such as the Virtual Control Program Interface (VCPI), are not supported because they would violate the integrity of the system. The DOS Protect-Mode Interface (DPMI 0.9), the Expanded Memory Specification (EMS), and the Extended Memory Specification (XMS) are supported.

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

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

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

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

6. The following fax boards and programs contain timing sensitivities that might prevent reliable operation: 7. For more reliable DOS communications performance on slower systems, the combined baud rate should not exceed 9600 bps for one or more concurrent DOS applications.
 * ATI ETC
 * Cardinal FAX
 * Practical Peripherals
 * Smart Fax
 * Twincomm 24/96

Our testing has identified the following programs that perform one or more of the activities described above. In addition to the restricted activities described previously, some general conditions you should be aware of are in the following list: The following list provides information about the compatibility of specific programs with OS/2 2.0. This information is version-specific; later versions of the same program might operate correctly. Some program manufacturers already have resolved incompatibility issues and have fixes available; these are noted.
 * Ansel for Windows
 * Bound Checker (DOS)
 * Central Point Backup for Windows
 * Close-Up (Windows)
 * Desert Storm CD-ROM (Windows)
 * Distinct Back-Up (Windows)
 * DoDot 3.0 (Windows)
 * Fax Concentrator (DOS)
 * Magic-CV (DOS)
 * Mathematica 2.0 (Windows)
 * MusicPrinter Plus 4.0 (DOS)
 * OmniPage Professional 1.0 (Windows)
 * Oracle (DOS) (There is an OS/2 version of this program.)
 * Perceive for Windows
 * Realizer 1.0 (Windows)
 * Sherlock Holmes CD-ROM (DOS)
 * Smart Fax (DOS)
 * Soft-ICE (DOS)
 * Splash 1.01 (DOS)
 * Some DOS and Windows programs run correctly only in full-screen sessions. Any Windows program that does not use the Windows API to change the video mode should be run in a WIN-OS/2 full-screen session.
 * Some DOS and Windows programs must be installed or run in a "Specific-DOS" session; that is, in a session that was started by booting from an actual version of DOS.
 * Some programs run in OS/2 DOS or WIN-OS/2 sessions, but require that you install the program under DOS.
 * Windows programs cannot start DOS sessions or DOS programs.
 * DOS programs that use low-level file system calls cannot access HPFS disks.
 * Code-page switching support is not available for graphics mode in DOS sessions.
 * Some DOS and Windows programs use security keys as protection against copyright infringement. The security key is a 25 pin connector that is connected to the parallel port of the computer on which the program is executing. The program checks to see if the connector is attached and, if the connector is not present, the program is assumed to be an illegal copy. When more than one DOS session is running one of these programs, a SYS1799 error can result.  This occurs because the programs that use these security keys do not de-allocate the parallel port if a second session is started for a program that also requires the security key.  This error is the result of a direct I/O parallel port contention mechanism that protects the user from possible data corruption.  To disable this mechanism press Ctrl-Alt-PrtSc while the DOS session that first performed direct I/O to the parallel port has the keyboard focus.
 * If your Windows Multimedia Extension programs do not work correctly after being migrated to OS/2 2.0, re-install them under WIN-OS/2.
 * Action! Sampler 1.0 (Windows)
 * The DPMI_MEMORY_LIMIT WIN-OS/2 setting must be set to 5 or greater.
 * Adobe Type Manager (Windows)
 * When using an IBM 4029* printer in PPDS mode with Adobe Type Manager, some Windows programs may not function correctly. If this occurs, do not use the printer resident fonts. To disable printer resident fonts, bring up the control panel of the Windows Adobe Type Manager and ensure that the selection "Use Pre-built or Resident Fonts" is disabled.

o  After Dark (Windows) -  To run in a WIN-OS/2 window, change the object's settings to hide or minimize the icon to the desktop. o  Aldus Pagemaker 4.0 (Windows) -  The spelling checker cannot locate the dictionary. -  Deselect the public setting to use the clipboard. -  If you experience incorrect output when spooling Standard format files to the printer, set the printing to RAW mode. To       do this, take the following actions: 1. Go to the Printer icon on the desktop 2. Select Open, then Settings, then Queue Options. 3. Ensure that Printer Specific Format is            checked. o  Aldus Persuasion 2.0 (Windows) -  Use the parallel ports to print. -  Deselect the public setting to use the clipboard. o  Arts & Letters Graphics Editor 3.1 (Windows) -  The DECIPHS utility program requires that a DOS session be started from the Windows environment; this is not supported. -  To run in a WIN-OS/2 window, change the object's settings to minimize to the desktop. -  The directory created by Arts & Letters is        named A&L. The "&" character is a       reserved character of the command shell, CMD.EXE; it is used for conjugated command lines. To change to the A&L directory with the CD command you must use one of       two methods of quoting the directory name. The first method is to prefix the "&" in       A&L with a ^ (caret, shift 6): CD A^&L The second method is to surround the entire directory name with quotation marks ("):       CD "A&L"    -   If you are running Arts & Letters and you        get a system error (a GDI trap), you must        restart the operating system before        running the program again.  This is        because the program left a portion of        itself running when it ended and will not        start a new copy of itself while that        portion is running.  This also means that        when you restart the computer, Arts &        Letters will start again automatically.        It is recommended that you close the copy        that is launched on system startup and        start the program from its icon when you        intend to run it in a window. o   AutoCAD Version 10 (DOS)    -   Close the program from the desktop. o   AutoCAD (OS/2)    -   Some of the background colors are set to        an unusually pale color that does not show        up well on XGA monitors. o   AutoManager 4.0 (DOS) -  The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the real-mode version. -  The program expects COMMAND.COM to be in        the root directory of drive C:\. Copy COMMAND.COM from the C:\OS2\MDOS directory to C:\. o  Borland C++ 2.0 (DOS) -  Set the DPMI_DOS_API DOS setting to        ENABLED. o  Central Point Backup for DOS 7.1 (DOS) -  Displays meaningless characters when running in a DOS window session. Run this program only in a DOS full-screen session. o  Central Point PC Tools Deluxe 7.1 (Windows) -  Many of the utility programs require starting a DOS session from Windows; this is not supported. Start these programs from a separate DOS session. -  The backup feature of this program performs in a manner similar to Central Point Backup for Windows, which is in the list of programs that perform restricted activities. If you experience difficulty backing up on a diskette, back up on an       alternate device, such as a network drive or a tape drive. o  Commander Keen (DOS) -  Set the VIDEO_RETRACE_EMULATION DOS setting to OFF. o  Control Room 1.0 (DOS) -  You must run this program in a DOS full-screen session for the screen blanking feature to work correctly. o  CorelDRAW 2.0 (OS/2) -  If you do a large amount of printing while in this program, it is possible that you might run out of system resources. To       avoid this, you should periodically save your work and exit CorelDRAW, then restart the program and continue your work. o  CorelDRAW 2.0 (Windows) -  Install the program in a DOS session. -  Run the program in a WIN-OS/2 full-screen session. o  CorelDRAW 2.1 (Windows) -  To install this program: -- Start a DOS session. -- Run FFIX /date (Note that "date" must            be lowercase). -- Run WINOS2 (from the command line). -- Install the program. -- Exit WIN-OS/2. -- Run FFIX /u. -  Run the program in a WIN-OS/2 full-screen session. o  dBase IV 1.1 (DOS) -  Set the DOS_FILES DOS setting to 30. Set the DOS_VERSION DOS setting to       DBASE.EXE,5,0,255. With Hyperdisk, set DOS_VERSION to DBASE1.EXE,5,0,255. -  When using Hyperdisk, you might have to        adjust the EMS and XMS memory limits. -  With the multi-user version, the program must be run in a Specific-DOS session. o  Designer (OS/2) -  The MIRRORS.DLL that comes with this program must be installed in the program directory, as opposed to the C:\OS2\DLL directory, and the program must be started from this directory. This is because OS/2 2.0 comes with its own dynamic link library named MIRRORS.DLL. o  Drafix CAD Version 1.11 (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Drafix CAD Version 3.0 (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Dynacomm Asynchronous OS/2 (OS/2) -  The DLL's included with this product must not be in the same directory as the executable file. Put them in a separate directory and add that directory to the end of the LIBPATH. o  Enhanced Editor (OS/2) -  The OS/2 Enhanced Editor supports up to 99 fonts. If additional fonts are installed, unpredictable results might occur. o  F19 (DOS) -  Set the HW_ROM_TO_RAM DOS setting to ON        and the VIDEO_RETRACE_EMULATION DOS setting to OFF. o  F-117A Stealth Fighter 2.0 (DOS) -  Set the VIDEO_RETRACE_EMULATION DOS setting to OFF. -  If the program appears to stop at a blank screen soon after you start it, press ESC and the program will continue. Once you are past the opening screens, the program runs correctly. o  Fastback Plus 2.1 and 3.04 (DOS) -  If you experience difficulty backing up on        a diskette, back up on an alternate device, such as a network drive or a tape drive. o  FastLynx 1.1 (DOS) -  To use the serial port with this program, remove the DEVICE=C:\OS2\MDOS\VCOM.SYS statement from CONFIG.SYS. Using the parallel port works correctly. -  Due to its high speed, the program sometimes fails. If this occurs, simply end the program; system integrity is not compromised. To minimize the possibility of this error condition, set the following DOS settings: HW_TIMER = ON       IDLE_SENSITIVITY = 100 IDLE_SECONDS = 10 o  FormBase 1.2 (Windows) -  The SHARE statement is automatically added to AUTOEXEC.BAT during program installation. Use an editor to remove the SHARE command from AUTOEXEC.BAT. -  When running this program and Lotus 123 in        the same Windows session, this program must be started first. o  Form Publisher (Windows) -  Ensure that the program's printer driver is installed before running the program. o  FotoMan (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Framework III 1.1 (DOS) -  The program expects COMMAND.COM to be in        the root directory of C:\. Copy COMMAND.COM from the C:\OS2\MDOS directory to C:\. -  Disable the program's print spooler; using it might cause an error. o  Harvard Graphics (Windows) -  When installing this program under WIN-OS/2, you will receive an error dialog box. Select OK in the dialog box and installation will complete successfully. -  When running in a window, the Color Selection windows are missing the Color Selection grid. Run the program in a       WIN-OS/2 full-screen session. o  Harvard Draw (Windows) -  When installing this program under WIN-OS/2, you will receive an error dialog box. Select OK in the dialog box and installation will complete successfully. o  hDC FileApps 1.0 (Windows) -  Uses the Windows Notepad for a README text file during installation. Indicate that you do not wish to read the file and installation will continue. o  HP New Wave 3.0 (Windows) -  Install the program under DOS. If you experience problems with program or       session termination, set UseOS2shield=0 in        SYSTEM.INI (in the \OS2\MDOS\WINOS2        directory on your start-up drive). If       that does not help, run the program in a        full screen WIN-OS/2 session. o  IBM 3363 Optical Disk Drive* -  The software for this product must be run in a Specific-DOS session that is started from your A: drive. -  You should run only a small number of        other processes, when using this product. o  IBM PC/3270 V2.0* (DOS) -  First, the program must be migrated using the OS/2 Migration utility program. Then, set the VIDEO_MODE_RESTRICTION DOS setting to CGA and add "D:\[path]DXMA0MOD.SYS" and "D:\[path]DXMC0MOD.SYS" to the DOS_DEVICE DOS setting. o  IBM PC/3270 V2.0* (Windows) -  First, the program must be migrated using the OS/2 Migration utility program. Then add " /C PC3270WO.BAT" to the DOS_SHELL WIN-OS/2 setting and add "D:\[path]DXMA0MOD.SYS", "D:\[path]DXMC0MOD.SYS", and "D:\[path]PCS802.SYS V=N" to the DOS_DEVICE WIN-OS/2 setting. Then on the WIN-OS/2 Session settings page, set the "Separate session" setting to ON (by       clicking on the box until a check-mark        appears). o  Intel SatisFAXtion -  The installation program displays the message "You have inserted the wrong       diskette" when changing from disk one to        disk two. After the error message is       displayed, press Enter and the program will continue with installation. -  At the end of installation of the Intel SatisFAXtion you are told to remove the diskette and press any key to reboot your machine. Instead, shut down the operating system and restart your computer. -  If SatisFAXtion software is loaded into each DOS session, it might cause the fax to stop if another DOS session is started. Set up one DOS session to be used for faxing, and load the device driver and executable files only into that DOS session. To do this, take the following steps: 1. Edit AUTOEXEC.BAT. 2. Cut the last two lines referring to            the Intel SatisFAXtion board to the clipboard and save the file (using DOS           Command File for the file type). 3. Open a New file. 4. Paste the last two lines into the new file. 5. Save the new file as FAX.BAT, using DOS Command File as the file type. 6. Edit CONFIG.SYS and cut the last two lines relating to the Intel SatisFAXtion board to the clipboard (cut only the last line if you do not           have a scanner installed). 7. Save the file using Plain Text as the file type. 8. In the Command Prompts folder, select a DOS Full Screen icon, press the Ctrl key and mouse button two at the same time, move the mouse pointer to an           empty area in the folder, and release the mouse button and the Ctrl key. This creates a copy of DOS Full Screen. 9. Put the mouse pointer over your new icon and press button two. 10. Click on the arrow next to Open, and select Settings. 11. Go to the Session page and select the DOS settings push button. 12. Go to DOS_DEVICE and press mouse button one. Move the mouse to the dialog area and press button one (there should be a blinking cursor           now). 13. Paste the text that you cut from the CONFIG.SYS file and select Save. 14. Go to the General page and replace the contents of the Title box with FAX (or           whatever other title you choose). 15. If you want to edit the new session's           icon, go to the General page and select the Edit push button. 16. If you want to have this session start each time your system starts, move the icon to the Start Up folder. 17. Whenever you start this session, type FAX to run the FAX.BAT file before using the SatisFAXtion board. Use the fax board in only one session at a       time. -  If you install using this procedure and you receive error messages, install the program under DOS. o  King's Quest (DOS) -  Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or from the DOS_DEVICE DOS setting. o  LAN Support Program Device Drivers (DOS) -  If you opened a DOS session with the DOS LAN Support Program (LSP) device drivers, and subsequently closed the session, you must ensure that the Token-Ring Adapter is       reset before using the LAN from another DOS session. To ensure that the Token-Ring Adapter is reset, use RESETOKN.EXE or RESETOKN.SYS. These files can be retrieved from CompuServe by       issuing GO IBMOS2 and downloading RESTKN.ZIP from SECTION 17, IBMFILES, or       they can be retrieved from the IBM National Support Center Bulletin Board System by downloading RESTKN.ZIP. -  The IBM Token-Ring Adapter should be used by only one session at a time. o  LANtastic 4.1 (DOS) -  Run this program in a Specific-DOS session. Set DOS_STARTUP_DRIVE DOS setting to the location of a DOS kernel to       boot from. -  If you are using Artisoft AE-2 or AE-3 adapter cards, set your cards to 8-bit mode, as described in the adapter documentation. o  LapLink III 3.0 (DOS) -  We recommend using the parallel port. To       use the serial port with this program, comment out the VCOM.SYS and COM.SYS statements from CONFIG.SYS (by putting       "REM " at the beginning of the line) and restart the computer. To use the serial port for other purposes, uncomment the lines in CONFIG.SYS and restart the computer. o  Linkway Mammals (DOS) -  Photomotion programs might exhibit some audio breakup and video hesitation during periods of CD ROM access. o  Linkway Presidents (DOS) -  Photomotion programs might exhibit some audio breakup and video hesitation during periods of CD ROM access. o  Lotus 123 for Windows 1.0 (Windows) -  Set the DPMI_MEMORY_LIMIT DOS setting to a        minimum of 3MB. -  After migrating the program to the workplace shell, copy the file 123W.INI to       the \OS2\MDOS\WINOS2 directory (from the        directory previously containing Windows        3.0). o  Lotus Freelance Graphics for OS/2 (OS/2) -  If you experience installation problems, contact the Lotus Development Corporation. Lotus will provide a fix. -  If you experience problems with the color, change the palette from the Freelance menus. Instructions on how to do this can be found in the Lotus Freelance Graphics for OS/2 User's Guide. A set of new default palettes for Freelance Graphics is       available. These can be retrieved from CompuServe by issuing GO IBMOS2 and downloading PALETT.ZIP from SECTION 17, IBMFILES, or they can be retrieved from the IBM National Support Center Bulletin Board System by downloading PALETT.ZIP. o  Lotus Freelance Graphics for Windows (Windows) -  The pointer to printer objects points to        Screen Show instead of to the printer. o  Lotus Magellan 2.0 (DOS) -  The UNDELETE function in the program uses physical sector addressing, which is not supported. Use the OS/2 UNDELETE command. o  Lotus Notes (OS/2) -  To use Notes 2.x, you must delete the file QWC.EXE from the Notes program directory. This file is used only for support in the field, and, therefore, its removal will not affect program execution. o  MagiCorp (Windows) -  Running this program with other programs in the same WIN-OS/2 session might cause a       system halt. Run this program by itself in a WIN-OS/2 full-screen session. o  Mathcad 3.0 (Windows) -  To install this program: -- Start a DOS session. -- Run FFIX /date (Note that "date" must            be lowercase). -- Install the program (the installation            program is a DOS program). -- Run FFIX /u. o  MicroProse Civilization (DOS) -  Set the VIDEO_RETRACE_EMUL setting to OFF and the HW_TIMER setting to ON. o  Microsoft Bookshelf - CD-ROM Reference Library** (DOS/Multimedia) -  Requires version 6.14 of the mouse device driver, MOUSE.COM, which comes with the product. -  Animation programs might exhibit some audio breakup and video hesitation during periods of CD ROM access. o  Microsoft Chart 3.0** (DOS) -  Install the program's mouse driver, and set MOUSE_EXCLUSIVE_ACCESS to ON. o  Microsoft Codeview** (DOS/OS/2) -  When using the protect mode version, CVP 2.2 (for OS/2), trace through the source code, rather than through the assembler language. -  In order for the program to work correctly, delete the PWBHLP.PXT help file. o  Microsoft Codeview for Windows Version 3.0** (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Microsoft Excel for DOS 2.1** (DOS) -  Set the XMS_MEMORY_LIMIT DOS setting to 0. o  Microsoft Excel for OS/2 3.0** (OS/2) -  The Help index and the Keyboard Help windows operate incorrectly. Avoid using these functions. o  Microsoft Excel for Windows 3.0** (Windows) -  Deselect the public setting to use the clipboard. -  When using dynamic data exchange (DDE), run in the same WIN-OS/2 session as the Windows program it is communicating with. o  Microsoft Money 1.0** (Windows) -  Calls the Windows Calculator accessory program. Use the OS/2 Calculator mini-application program in the Productivity folder. o  Microsoft QuickC** (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Microsoft Project for Windows 1.0** (Windows) -  Must be installed in a DOS session. o  Microsoft Windows 3.0** (DOS) -  We recommend that you run Windows programs under WIN-OS/2, which supports both Standard and Real mode Windows programs. If, however, you choose to run this program, run it in Real mode only. o  More Windows (Windows) -  If you use the Full-Page Paper White mode or Full Screen Color mode the screen might be disrupted. Avoid using these modes. o  National Geographics Mammals (DOS) -  Photomotion programs might exhibit some audio breakup and video hesitation during periods of CD ROM access. o  The Norton Backup 1.2 (DOS) -  You might experience diminished performance when backing up to diskette. o  The Norton Desktop (Windows) -  This program assumes that, if it is not the first program loaded, another desktop is running. Include the UseOS2shield=0 statement in SYSTEM.INI (in the       \OS2\MDOS\WINOS2 directory on your        start-up drive). -  If you experience difficulty formatting a        diskette, use the OS/2 FORMAT command. If       you experience difficulty backing up on a        diskette, back up on an alternate device, such as a network drive or a tape drive. -  Run the program in a WIN-OS/2 full-screen session. o  The Norton Utilities 5.0 (DOS) -  The UNDELETE functions require physical sector addressing, which is not supported. Use the OS/2 UNDELETE command. -  The utility programs that manipulate the hard disk (for example, UNDELETE,       UNFORMAT, DISKTOOL, CALIBRATE, the Disk        Doctor, and the Disk Editor) can cause a        system halt. Some of these programs can be used on floppy diskettes. o  PaintShow Plus 2.21 (DOS) -  Load the version of MOUSE.COM that comes with the program, before starting the program. o  Paradox 3.5 (DOS) -  The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard version of the program. o  Peachtree Complete III 5.0 (DOS) -  Set the DOS_FILES DOS setting to 60. -  The program's Lookup function does not list all the companies that have been entered into the program's list of       companies; it displays meaningless characters. o  Perform Pro 1.0 (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  PFS: First Choice (DOS) -  When the program is run in a DOS window the mouse pointer does not reflect tool selection. -  Set the baud rate to 2400 or lower when using the communication feature. o  PFS: WindowWorks 1.75 (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Photostyler (Windows) -  Run the program in a WIN-OS/2 full-screen session. o  Publisher's PowerPak  2.1 (Windows) -  Create the directory C:\OS2\MDOS\WINOS2\POWERPAK, before running the installation batch file. o  Quattro Pro 3.0 (DOS) -  Install printers from within the program, rather than during program installation. o  Quicken (DOS) -  Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or from the DOS_DEVICE DOS setting. o  Quicken for Windows (Windows) -  Calls the Windows Calculator accessory program. Use the Calculator mini-application program in the Productivity folder. o  Risk (DOS) -  Do not use the program's shutdown function. o  SantaFe Media Manager (DOS) -  To install this program: -- Start a DOS session. -- Run FFIX /find (Note that "find" must            be lowercase). -- Install the program. -- Run FFIX /u. o  SideKick (OS/2) -  A printer must be installed and present on        the desktop to use the Notepad. o  Signmaster 5.11 (DOS) -  The plot/preview feature causes an illegal instruction to be issued. o  Soft Term (OS/2) -  In the Send File and Receive File windows, the first time the drive is changed the Directory window updates incompletely. After the first time, the Directory window works normally. o  SoundBlaster (DOS) -  The SBTEST utility program reports an        incorrect DMA level during installation. Disregard the error message and continue with installation. The program will be       installed correctly. -  The PARROT program does not run in a DOS session. o  Space Quest IV (DOS) -  Set DOS_BACKGROUND_EXECUTION to OFF so        that the program is suspended when it is        placed in the background. -  Set up the program so that it does not use extended memory. -  For best performance, run this program in        a DOS full-screen session. -  For computers with a SoundBlaster card, change to the drive and directory which contains Space Quest IV and enter SQ4FIX on the command line. o  SQLWindows 3.0 (Windows) -  The program accesses drive A: at        intermittent intervals. Keeping a scratch diskette or an empty diskette in drive A:       will save you from having to respond to        "The A: device is not ready" error windows. o  Turbo C++ 2.0 (DOS) -  The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard version of the program. o  Turbo Debugger 2.01 (DOS) -  The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard version of the program. -  TD386, the 386 version of Turbo Debugger, manipulates the 80386 control registers; this is not supported. o  Turbo Debugger for Windows (Windows) -  Run the program in a WIN-OS/2 full-screen session. -  The screen is temporarily corrupted when this program is called from Turbo C++. The screen is restored on the first repaint (a repaint can be forced by       clicking the mouse on several different        windows). o  Turbo Pascal 6.0 (DOS) -  The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard version of the program. o  The Way You Work (DOS/Windows) -  Install this program under DOS. Once installed, the program can be run in a DOS or WIN-OS/2 session. o  Windows Multimedia Extensions (Windows) -  If you are running this program and another program that uses the audio adapter at the same time, unpredictable results might occur. -  The OS/2 Multimedia Presentation Manager avoids this problem. o  WINFAX PRO (Windows) -  Run this program only in a WIN-OS/2 full-screen session. -  If you are using Dynamic Data Exchange (DDE), avoid switching away from the WIN-OS/2 full-screen session in which you are running; switching from the WIN-OS/2 session to another session might break the DDE link. o  Wing Commander II (DOS) -  If you are running on a slower computer, turn the sound option off. o  WordPerfect for Windows (Windows) -  Change to the directory that contains WPWINFIL.EXE and run: FIXWP WPWINFIL.EXE. (To enable WordPerfect for Windows to run       under DOS and Windows 3.0 again, run        UNFIXWP in a similar manner.) o  WordPerfect Office 3.0 (DOS) -  Install the keyboard-enhancement utility program manually after program installation, by adding it to CONFIG.SYS. o  Xtree Pro Gold 2.0 (DOS) -  The Zip Manager feature cannot find the zip file it is to act upon. Avoid using this feature.

PERFORMANCE
Following are some performance considerations that you should be aware of. For more performance guidelines, see the "Information and Planning Guide" document that can be obtained through your point of purchase or retrieved through CompuServe. The minimum memory requirement for OS/2 2.0 is 4MB. (This includes up to 128KB that is used on some machines for ROM to RAM remapping). Some systems use more than 128KB for other purposes, so less than the minimum required memory is available. On these systems, you might need another 512KB to 1MB to satisfy the minimum requirements. Check your system to see if it offers a way to return the memory so that you can return to the minimum requirement. Users concerned with response times when using some system functions, such as loading programs, starting sessions, and switching between sessions, can improve performance by increasing system memory. If you are running on a constrained system (small hard disk, 16-MHz or less processor, 4MB of memory), an additional 2MB of memory will improve performance. In the entry memory system (4MB), the recommended file system is the FAT file system.

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

FILE SYSTEMS
Many performance changes have been incorporated into OS/2 2.0 File Systems. Both file systems read ahead (for sequential I/O), lazy write to disk, and accept threshold parameters. A disk cache size is preselected by the system based on installed memory, disk size, and file systems installed. The default for the entry memory system (4MB) is a cache size of 128KB. To tune the size of the disk cache, see the information about DISKCACHE in the "Command Reference."

DOS APPLICATIONS
You can improve the performance of some DOS applications by adjusting the DOS settings. If the application does not require extended or expanded memory, these values can be set to zero. This will provide maximum performance. Some DOS applications use polling techniques to poll the system for work. An example is an application that appears to be idle at an input prompt, but is in fact polling the keyboard looking for keystrokes. Use the IDLE SENSITIVITY choice to detect this occurrence and put the application to sleep when it is polling.

WINDOWS APPLICATIONS
Windows applications are generally started in one WIN-OS/2 session, unless specifically set to run in their own WIN-OS/2 session. If you use several applications simultaneously, you might want to increase the DPMI memory limit before starting the first application. The first application started determines the DPMI memory available for all subsequent Windows applications that are used. In low memory configurations, you can run multiple Windows applications in one WIN-OS/2 session. This reduces both memory and swapper-file requirements. With a WIN-OS/2 window session, a new session is created every time you double-click on an active object. To restore the currently active object: If you choose to migrate your Windows applications (at installation time or later using MIGRATE), most Windows applications will execute in one WIN-OS/2 session. If you set up a Windows application and do not use MIGRATE, each program executes in its own WIN-OS/2 session. If you are running Windows applications in a single WIN-OS/2 session, the Windows clipboard can be changed from PUBLIC to PRIVATE for increased performance. Setting it to PRIVATE means that it can be used in the single Windows environment only. When a large volume of data is being sent to the clipboard in a WIN-OS/2 Window session, you might receive the message: Data not saved, possible memory or disk space error This data not available in clipboard followed by the message: Do you want to exit clipboard? Selecting OK to the second message will make the clipboard private to that WIN-OS/2 session. Data that was previously sent to the public clipboard might have remained private. You might want to use the private clipboard for applications seeing these messages. When you exit from a WIN-OS/2 session, the system leaves the clipboard and DDE loaded. If you will not be returning to a WIN-OS/2 session, close both the clipboard and DDE. Use the PM Window List to see if they are active. To permanently disable public DDE and clipboard interchange between Windows applications and PM applications, and between Windows applications in separate WIN-OS/2 sessions, edit the \OS2\MDOS\WINOS2\SYSTEM.INI file. In the [boot] section you will find the names of these two programs in the SAVDMApps= line, the MAVDMApps= line, and the WOS2VDMApps= line. By removing the names of the programs from these lines, the programs will not be automatically started. Adding them back will cause them to be started the next time a WIN-OS/2 session starts up.
 * Double-click on the minimized application object, or
 * Display the OS/2 Window List and double-click on the application name.

APPLICATION USAGE
If you have an application that you always use, you can set up the application in the Startup folder to load when the system is started. To avoid reloading frequently used applications, minimize the application after use and simply maximize it to use it again. You can find the application in the window manager. If you use several different applications, the icons (objects) can be placed on the desktop or in a folder. The folder can be set to open when the system is restarted.

FREEING MEMORY
Close opened applications when you are not going to use them again. Close folders that you do not need. Also move commonly used functions out of folders and onto your desktop, and close the folders that contained the icons.

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

WINDOWS VERSION 3.0 PROGRAMS SUPPORT

 * If you are running WIN-OS/2 window sessions, you cannot have any statement in the AUTOEXEC.BAT file that prompts the user for input.

If your printer is connected to LPTx or LPTx.OS2, be sure that the OS/2 spooler is active and the Windows spooler is disabled. When the OS/2 spooler is active, Windows applications print jobs from Windows applications spool directly to the OS/2 spooler. Therefore, multiple print jobs can be spooled asynchronously from the same WIN-OS/2 session or multiple WIN-OS/2 sessions. This does not apply for printing to COMx devices, as there is no spooling for COM devices.
 * If you are running a WIN-OS/2 full-screen session and you have an 8514 display, use DOS Settings to set VIDEO_8514A_XGA_IOTRAP to OFF and VIDEO_SWITCH_NOTIFICATION to ON.
 * Current information for WIN-OS/2* window sessions in high-resolution video modes will be available from CompuServe, the IBM National Support Center Bulletin Board System, the OS/2 Bulletin Board System, and IBMLINK.
 * Do not use the SETUP.EXE shipped with Windows 3.0. Instead, use the SETUP.EXE shipped with WIN-OS/2 to ensure your environment will be properly maintained for use in OS/2 2.0.  Use the Selective Install choice (in OS/2 2.0) to change video drivers for VGA, 8514, XGA*, EGA, and CGA, and for mouse drivers.
 * If you are running a WIN-OS/2 full-screen session with an XGA video device driver and your Windows icons are not clear, use the Control Panel to choose another color scheme for the WIN-OS/2 desktop.
 * Do not change mouse buttons from the WIN-OS/2 Control Panel if you are using WIN-OS/2 window sessions. Change mouse buttons from the Workplace Shell to change the WIN-OS/2 mouse buttons in the WIN-OS/2 environment. The WIN-OS/2 Control Panel can still be used for changing mouse buttons in WIN-OS/2 full-screen sessions.
 * If the VIDEO_SWITCH_NOTIFICATION setting is ON, wait until you see your WIN-OS/2 desktop in a full-screen session before switching back to the Workplace Shell desktop. If the session does not start successfully, close it then restart it.
 * The value for VIDEO_SWITCH_NOTIFICATION should not be changed for an active WIN-OS/2 session.
 * Clipboard and DDE default to PRIVATE in real-mode WIN-OS/2 sessions.
 * If you install the USA (English) version of OS/2 2.0, and you want to change the system configuration to another country or language, run Selective Install to make the changes effective for PM. To make the changes effective for WIN-OS/2, start WIN-OS/2 in full-screen mode, open the Control Panel, and use the international option to make your changes.
 * The EXPAND.EXE utility program for WIN-OS/2 is located on OS/2 2.0 diskette 9. This program is required to expand Windows device drivers supplied by equipment manufacturers.
 * PRINTING

VIDEO/GRAPHIC SUPPORT
OS/2 2.0 fully supports EGA and VGA. Because of the highly graphical user interface provided by the Workplace Shell, use of OS/2 2.0 in CGA mode will be difficult and is not recommended. Applications designed for CGA mode are supported and can be run even when OS/2 2.0 is running in EGA, VGA, or SVGA mode. Resolutions above VGA (640x480x16 colors) are referred to as Super VGA (SVGA). However, the implementation of SVGA varies widely and requires different device drivers for different resolutions, as well as different adapters and systems. The OS/2 Installation program will correctly configure Presentation Manager* and WIN-OS/2 drivers for 8514 and XGA. All SVGA adapters are supported in VGA mode with the VGA driver provided with OS/2 2.0. The base video system and virtual display device driver in OS/2 2.0 have been enabled for some of the most popular SVGA chips and boards. This support is required to switch between PM and DOS or WIN-OS/2 applications. Because of the many implementations and video modes, a limited number of video boards have been tested. The following Super VGA boards have been tested and found to work with OS/2 2.0 for DOS applications that make use of SVGA modes: The 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. Please contact the manufacturer of your PC or SVGA video adapter to obtain device drivers and installation instructions if you want to run Windows or OS/2 applications in SVGA modes. Information about SVGA support will be available on CompuServe, the National Support Center ulletin Board System, the OS/2 Bulletin Board System, as well as many video-board and system manufacturers' bulletin boards. We recommend you do NOT run the video-adapter test utility programs in OS/2 2.0 unless the manufacturer has explicitly verified that they run in OS/2 2.0. Some video adapters require that the computer's DOS BIOS initialize the video adapter correctly. If you have one of these adapters, screen text might appear distorted in an OS/2 full-screen command prompt. To remedy this, start a DOS full-screen command prompt, type EXIT, and then switch back to the OS/2 full-screen session; the text should appear normal. To automate this process, you can create a DOS batch file to run when you start your computer. Add the following statement to STARTUP.CMD: START /FS /DOS DOSFS.BAT Create the file, DOSFS.BAT, and place the following statement in it: EXIT If you have one of the above video adapters and want to run DOS or Windows applications that make use of SVGA, you must turn on OS/2 2.0 SVGA support. The OS/2 Installation program detects the type of video chip in the system; it cannot detect the type of adapter or system board that the video chip has been implemented on. You must determine that you have a supported configuration, and then explicitly enable SVGA. To enable SVGA, type the following at an OS/2 command prompt or DOS full-screen command prompt: SVGA ON Then restart the system. When the Installation program detects a supported SVGA video chip (other than 8514 or XGA), it will add the following line to the CONFIG.SYS file: DEVICE=(OS/2 drive):\OS2\MDOS\VSVGA.SYS Execution of SVGA ON creates the configuration file, SVGADATA.PMI, in the \OS2 directory. This file is used by VSVGA.SYS to save and restore the correct video registers when switching between DOS or Windows programs and Presentation Manager. Failure to enable SVGA will cause display errors when switching between applications that use SVGA. NOTES: 1. Over time, more display adapters and PC systems that offer SVGA, will be tested. Refer to the bulletin boards mentioned previously, or to the manufacturers for the latest support information. 2. To make use of SVGA modes, you also must install Windows and Presentation Manager video display drivers. 3. If you experience display errors on an SVGA-enabled system, try disabling SVGA support by typing SVGA OFF at a command line. This will delete the SVGADATA.PMI file. Then restart your system. 4. In some SVGA displays, if you switch to the PM desktop while the screen is still drawing, you might experience display errors on the PM desktop. Switch back to the SVGA screen, allowing the drawing to complete, and then switch back to the PM desktop. In multiple XGA configurations, when you switch from DOS to the PM desktop, your system will not save and restore the hardware registers. If your machine has an 8514 Ultra adapter and an OS/2 2.0 supported SVGA adapter, you will need to change the DEVICE= statement in your CONFIG.SYS file from VVGA.SYS to VSVGA.SYS. To change the color schemes for OS/2 system windows and create a more readable display image, change the Scheme Palette as follows: 1. Use your Reference Diskette or hardware Setup program to set your hardware to VGA color, if possible. 2. Open the System folder. 3. Select System Setup. 4. Select Scheme Palette. 5. Select the right-hand monochrome scheme. This procedure will optimize the color scheme for gray-scale usage, and also provide a good set of colors for a VGA desktop presentation. Several fonts have been enhanced in OS/2 2.0. Some existing applications use inappropriate font metrics to scale their text. In some cases, the text becomes clipped because it no longer fits the available space. When running a full-screen WIN-OS/2 session with an 8514 adapter in high resolution (8514.DRV mode), do not switch away to a different session while an application is updating the screen or displaying the hourglass. The following is a procedure for enabling WIN-OS/2 full-screen sessions to run in high-resolution mode while the Workplace Shell Desktop and WIN-OS/2 window sessions run in medium-resolution (VGA) mode. The procedure assumes you are not familiar with the SYSTEM.INI and WIN.INI files. Follow the instructions very carefully. Otherwise, you could cause your WIN-OS/2 sessions, both window and full-screen, to become inoperable. 1. Install OS/2 for medium resolution VGA.
 * SVGA
 * Orchid ProDesigner IIs by Orchid Technology (ISA and MCA versions)
 * Trident TVGA by Trident Microsystems, Inc. (8900b and c levels)
 * STB PowerGraph VGA by STB Systems, Inc.
 * Video Seven VRAM II, by Video Seven
 * Boca Super VGA by Boca Research Inc.
 * VGA Wonder XL Series by ATI Technologies, Inc.
 * SVGA ON UTILITY
 * DUAL DISPLAYS
 * LAPTOP LCD OR MONOCHROME PLASMA DISPLAYS
 * GRAPHICS
 * RUNNING VGA PM AND WIN-OS/2 WINDOW SESSIONS IN VGA AND WINDOWS FULL-SCREEN SESSIONS IN HIGH RESOLUTION MODE
 * The next step requires you to make backup copies of your SYSTEM.INI and WIN.INI files.
 * DO NOT SKIP THIS STEP. It is assumed that you have a diskette or tape backup copy of your system; instructions follow for a backup in the directory only.

2. Back up the SYSTEM.INI and WIN.INI files.
 * Open an OS/2 Window from the Command Prompts folder in the OS/2 System folder. At the C:\] prompt, type the following and press Enter:

CD\OS2\MDOS\WINOS2 COPY WIN.INI WIN.BAK COPY SYSTEM.INI SYSTEM.BAK
 * Before making changes to the files, be sure the desired high-resolution Windows device drivers and fonts are loaded in the system.

3. Check the \os2\mdos\winos2\system directory for the desired high-resolution display device driver. In this example, the XGA.DRV device driver is used. Checking this directory reveals that this device driver is not loaded. (The device driver might be loaded already, if the system was installed in high-resolution mode and then Selective Install was run to return to VGA mode.)
 * For XGA, the diskettes need to be searched for WINXGA and *G.FON. The following shows the sequence of entries.

DIR A:WINXGA DIR A:*G.FON No XGA drivers were on this diskette, but one of the font files was. Although the font file is not in a bundle of files, it is still in packed format and must be unpacked. The files are packed with their standard target directory coded into the packed file. To copy the file to the system disk in the proper directory, just run the Unpack utility program. UNPACK A:SYMBOLG.FON This procedure continues until all of the scalable fonts are unpacked. These fonts are: Eventually the WINXGA file is found by the dir a:WINXGA search. It contains the WIN-OS/2 XGA. DRV and three XGA fonts. UNPACK A:WINXGA With all of the required driver and font files on the system disks, the next step is to modify the SYSTEM.INI file. 4. Edit the SYSTEM.INI file and find the following line: display.drv=vga.drv 5. This line specifies what device driver WIN-OS/2 is to use in full-screen sessions. Change this line to point to the high-resolution device driver that was unloaded in the steps above. In this example, the device driver is XGA.DRV. The modified line should look like the following: display.drv=xga.drv Both SYSTEM.INI and WIN.INI have font entries that must be changed. In SYSTEM.INI, these entries are: fixedfor.fon=vgafix.fon oemfonts.fon=vgaoem.fon fonts.fon=vgasys.fon For XGA, these entries must be changed to: fixedfor.fon=xgafix.fon oemfonts.fon=xgaoem.fon fonts.fon=xgasys.fon In WIN.INI, the entries: Symbol 8,10,12,14,18,24 (VGA res)=SYMBOLE.FON Helv 8,10,12,14,18,24 (VGA res)=HELVE.FON Tms Rmn 8,10,12,14,18,24 (VGA res)=TMSRE.FON Courier 10,12,15 (VGA res)=COURE.FON Must be changed to: Symbol 8,10,12,14,18,24 (XGA res)=SYMBOLG.FON Helv 8,10,12,14,18,24 (XGA res)=HELVG.FON Tms Rmn 8,10,12,14,18,24 (XGA res)=TMSRG.FON Courier 10,12,15 (XGA res)=COURG.FON When these changes have been made and the INI files saved, the system is ready for running Windows applications in WIN-OS/2 window sessions (VGA mode) and WIN-OS/2 full-screen sessions (high-resolution mode). For 8514 displays, you must delete the following line from CONFIG.SYS: DEVICE=C:\OS2\MDOS\V8514A.SYS For 8514 displays, the files to find are: Windows developers should note that their debuggers work in full-screen only. If you have a dual-monitor setup (8514+VGA), install OS/2 2.0 for the 8514 as primary display with no secondary display. This will allow your Turbo Debugger for Windows (TDW) or CodeView for Windows (CVW) session to run full-screen on the VGA display while the WIN-OS/2 session runs full-screen on the 8514. For CVW, make sure to use the /8 option. Quick C runs on the same display as WIN-OS/2. If you use Quick-C, you don't need a special video configuration. Installing OS/2 2.0 in this way will allow PM to run on the 8514, and your full-screen debugger to run on the VGA. It also will provide a "stereo" effect for all full screen sessions; both the 8514 and VGA will show the same picture, unless a full-screen application takes advantage of video-specific features.
 * SYMBOLG.FON
 * TMSRG.FON
 * COURG.FON
 * HELVG.FON
 * WIN8514 (contains 8514.DRV, 8514SYS.FON, 8514OEM.FON, and 8514FIX.FON)
 * COURF.FON
 * TMSRF.FON
 * HELVF.FON
 * SYMBOLF.FON.
 * NOTES:

PERSONAL COMPUTER MANUFACTURERS - SYSTEMS
OS/2 2.0 is supported on personal computers with an 80386 SX (or compatible) or higher processor, with at least 4MB of memory and a 60MB hard disk with 15MB to 30MB of free space. IBM is currently testing personal-computer manufacturers (PCM) systems for compatibility with OS/2 2.0. The compatibility test verifies 18 key functions of OS/2 2.0. Test results are based on selected model configurations provided by the manufacturers. While testing is continuing, current compatibility information about tested systems is available through your dealer or Marketing Representative, as well as through the following:
 * Prodigy (call the appropriate phone number for your area, or Membership Service at (914) 962-0310).
 * CompuServe (call the appropriate phone numbers for your area, or Membership Service at 1-800-848-8199).
 * IBM National Support Center Bulletin Board System (NSC BBS). This service is available 24 hours a day, on a toll-call basis, with no access charge, to anyone in the world who has a modem, asynchronous-communication software, and a switched telephone line. (The modem should be set for 8 data bits, 1 stop bit, no parity, and the standard transmission speed from 1200 to 9600 baud.)
 * To access the NSC BBS, call (404) 835-6600.


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

NOTE: The compatibility test information is provided for information purposes only.

IBM MAKES NO WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE OPERATION OF THE PERSONAL COMPUTERS LISTED THROUGH THE ABOVE SOURCES

ADAPTEC AND FUTURE DOMAIN SCSI SUPPORT
Device support for the following Adaptec and Future Domain SCSI adapters is shipped with OS/2 2.0. When any of the following adapters is installed in a workstation, its presence is normally detected automatically, and the appropriate device support is subsequently installed. For reference, the names of the device drivers that support each adapter are provided here: The TMC-850/860/875/885 and TMC-850IBM adapters will not be detected when the adapter's BIOS is disabled. You can manually install this support in your system by following the steps below. NOTE: "xxxxxxxx.ADD" should be replaced with the file name of the device-driver file you want to install. 1. Locate Installation Diskette 8, which contains the file, DASDDRVS. 2. Insert the diskette in drive A. 3.  Change the current directory to the root directory of the startup drive. 4. Type:  UNPACK A:DASDDRVS \OS2 /N:xxxxxxxx.ADD 5. Add the following line to the CONFIG.SYS file: BASEDEV=xxxxxxxx.ADD 6. Restart the system. OS2SCSI.SYS Replaces SCSI.SYS The device driver, SCSI.SYS, has been replaced by OS2SCSI.SYS. OS2SCSI.SYS is provided in the \OS2 directory of the boot partition. Any CONFIG.SYS entries of the form "DEVICE=SCSI.SYS" should be replaced by the entry "BASEDEV=OS2SCSI.SYS." Normally, this is done automatically. The OS2SCSI.SYS device driver is required for a number of SCSI CD-ROM devices, SCSI Read/Write Optical devices, and SCSI Tape devices.

The SCSI CD-ROM support built into OS/2 2.0 has some manufacturer-specific dependencies at this time. Support has been verified for IBM and Toshiba SCSI CD-ROM drives. Information about the support and verification of additional manufacturers' drives will be made available at a later date.
 * SCSI CD-ROM Support


 * SCSI Removable Media Support

Full function support is not yet available for SCSI hard disk drives that support removable media. Examples of this class of device include the "Bernoulli" drives manufactured by IOMEGA, and the removable-media drives manufactured by SyQuest Technology. Although OS/2 2.0 recognizes these drives, it will treat media as large diskettes. You will be able to format for the FAT file system only. You will not be able to partition or start up from the media, and partitioned media will not be recognized. If the IBMINT13.I13 driver is used to control these units, the drive will be treated as a fixed drive. In this case, the cartridge must be in the drive at startup time, and you will need to use the Shutdown procedure to remove the cartridge from the drive. Following are a number of notes about usage, and about potential compatibility problems with the microcode levels on various adapters and devices. Adapter: All Adaptec adapters Note:    SCSI hard disks must be configured as           SCSI target ID 0 or 1 to be able to           start up from that hard disk. Adapter: Adaptec AHA-154x Drive:   IBM 0661 - 320MB SCSI Note:    Adapter BIOS will not recognize the drive as Target 0 or 1 (Drives 80, 81). For OS/2 2.0, the drive can be used as a          non-startup drive. Adapter: Adaptec AHA-174x Drive:   IBM WDS-3180 - 80MB SCSI, IBM WDS-3160 - 160MB SCSI Note:    Adapter will not recognize these drives when configured in 'STANDARD MODE' (AHA-154x emulation). Instead, the AHA-174x adapter should be configured in          'ENHANCED MODE'. This mode is supported by the OS/2 2.0 drivers, and the problem does not occur when the adapter is          operating in enhanced mode. Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0. System:  IBM Models 35 and 40 when the Future Domain adapter is controlling the startup diskette. Note:    Will produce the message, "Disk read error           has occurred" when you attempt to start the Installation diskette. Contact Future Domain for a free BIOS upgrade. AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters. If you have one of these adapters in your system, do the following:
 * SCSI Usage Notes
 * AMI SCSI Adapters
 * At the final restart after the installation is complete, delete from the CONFIG.SYS file, any line with "BASEDEV=AHA1xxx.ADD" (where "x" can be any character).
 * Ensure the line, "BASEDEV=IBMINT13.I13," appears in the CONFIG.SYS file.


 * FORMATTING DISKETTES

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

CD-ROM SELECTIVE INSTALL When installing CD-ROM using "Selective Install", do not install other options at the same time.

TRADEMARKS AND SERVICE MARKS
Terms denoted by a single asterisk in this file (*) are trademarks of the IBM Corporation in the United States and/or other countries. These terms include:
 * IBM
 * Operating System/2
 * OS/2
 * Presentation Manager
 * WIN-OS/2
 * XGA

Terms denoted by a double asterisk in this file (**) are trademarks of other companies. Other trademarks appearing in this file are owned by their respective companies. Microsoft, Microsoft Bookshelf, Microsoft Excel, Microsoft Flight Simulator, Microsoft Money, and Windows are trademarks of Microsoft Corporation. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.

Copyright IBM Corporation, 1992, all rights reserved.