Arawak OS/2 Shareware

home *** CD-ROM | disk | FTP | other *** search

/ Arawak OS/2 Shareware / PAKLED.ISO / docs / os2tnd.txt < prev next >

Wrap

Text File | 1992-09-15 | 269.2 KB | 8,353 lines

OS/2 2.0 TIPS AND TECHNIQUES Document Number 53G1930 +---------------------------------------------------------------------------+ | | | CONSULT THIS BOOK PRIOR TO CALLING THE OS/2 SUPPORT LINE. It contains | | important information that might be helpful in specific situations. | | | +---------------------------------------------------------------------------+ +--- NOTE -----------------------------------------------------------+ | | | Before using this information and the product it supports, be sure | | to read the general information under "Notices" on page v. | | | +--------------------------------------------------------------------+ FIRST EDITION (SEPTEMBER 1992) THE FOLLOWING PARAGRAPH DOES NOT APPLY TO THE UNITED KINGDOM OR ANY COUNTRY WHERE SUCH PROVISIONS ARE INCONSISTENT WITH LOCAL LAW: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Requests for technical information about IBM products should be made to your IBM Authorized Dealer or your IBM Marketing Representative. (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1992. ALL RIGHTS RESERVED. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. CONTENTS ________ NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V ABOUT THIS BOOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . IX Who Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . ix CHAPTER 1. SERVICE AND SUPPORT . . . . . . . . . . . . . . . . . . . . 1-1 CHAPTER 2. INSTALLATION CONSIDERATIONS . . . . . . . . . . . . . . . . 2-1 Upgrade Version of OS/2 2.0 . . . . . . . . . . . . . . . . . . . . . . 2-1 Limited Availability Version of OS/2 2.0 . . . . . . . . . . . . . . . 2-2 Reformatting the Hard Disk . . . . . . . . . . . . . . . . . . . . . . 2-2 During Installation . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 After Successful Installation . . . . . . . . . . . . . . . . . . . . 2-3 Partitioning the Hard Disk . . . . . . . . . . . . . . . . . . . . . . 2-3 High Performance File System . . . . . . . . . . . . . . . . . . . . . 2-3 Considerations When Deciding to Use HPFS . . . . . . . . . . . . . . 2-3 Adding the HPFS After Installation . . . . . . . . . . . . . . . . . 2-3 Adding Device Driver Statements to a CONFIG.SYS File . . . . . . . . . 2-4 Getting Your Mouse to Work . . . . . . . . . . . . . . . . . . . . . . 2-4 Changing the Default Mouse Driver . . . . . . . . . . . . . . . . . . 2-4 HP Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Logitech Mouse Not Working after Installation . . . . . . . . . . . . 2-5 Logitech Mouse Not Working after Dual-Boot Switch from DOS . . . . . 2-5 Other Mouse Not Working after Dual-Boot Switch from DOS . . . . . . . 2-5 Problems with Installation . . . . . . . . . . . . . . . . . . . . . . 2-6 LOGO Screen Problems . . . . . . . . . . . . . . . . . . . . . . . . 2-6 With OAK Video Adapter . . . . . . . . . . . . . . . . . . . . . . 2-6 With Future Domain SCSI Controller . . . . . . . . . . . . . . . . 2-7 Diskette Problems by Number . . . . . . . . . . . . . . . . . . . . . 2-8 Messages on Screen . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 C0000005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 COUNTRY.SYS File Cannot Be Found . . . . . . . . . . . . . . . . . 2-9 SYS1200 and EC=00BF . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Computer Beeps Constantly . . . . . . . . . . . . . . . . . . . . . . 2-9 White Screen Problems . . . . . . . . . . . . . . . . . . . . . . . . 2-9 With Disk Light On Constantly . . . . . . . . . . . . . . . . . . 2-10 After Installation . . . . . . . . . . . . . . . . . . . . . . . 2-10 With an ATI Video Adapter . . . . . . . . . . . . . . . . . . . . 2-10 BIOS Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Phoenix BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 AMI BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Micronics System Board . . . . . . . . . . . . . . . . . . . . . 2-12 Gateway 2000 Computer . . . . . . . . . . . . . . . . . . . . . . 2-12 Gateway 486 Computers . . . . . . . . . . . . . . . . . . . . . . 2-12 Gateway Computers and Trap 2 Errors on Boot or Installation . . . 2-12 Gateway Nomad Notebook . . . . . . . . . . . . . . . . . . . . . 2-13 ZEOS Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Short Cut If Your Installation Procedure Stops . . . . . . . . . . . 2-14 (C) Copyright IBM Corp. 1992 iii Using DOS and Windows Applications . . . . . . . . . . . . . . . . . 2-15 Installing a Local Area Network . . . . . . . . . . . . . . . . . . . 2-15 Installing a Response File . . . . . . . . . . . . . . . . . . . . . 2-15 Installing CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Enabling UNDELETE . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Dual Boot Does Not Work . . . . . . . . . . . . . . . . . . . . . . . 2-16 Using Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Boot Manager Menu Bypass . . . . . . . . . . . . . . . . . . . . . 2-17 OS/2 Version 1.3 in a Partition with Dual Boot . . . . . . . . . . 2-17 Using Non-IBM Computer with Two Drives . . . . . . . . . . . . . . . 2-17 CHAPTER 3. SYSTEM PERFORMANCE CONSIDERATIONS . . . . . . . . . . . . . 3-1 Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Swapper File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 DOS Application Programs . . . . . . . . . . . . . . . . . . . . . . . 3-2 Windows Application Programs . . . . . . . . . . . . . . . . . . . . . 3-2 Application Program Usage . . . . . . . . . . . . . . . . . . . . . . . 3-3 Hard Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 CHAPTER 4. OS/2 WORKPLACE SHELL . . . . . . . . . . . . . . . . . . . 4-1 Starting Up Your System . . . . . . . . . . . . . . . . . . . . . . . . 4-1 File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 The Startup Folder . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Preventing Automatic Startup . . . . . . . . . . . . . . . . . . . . 4-2 STARTUP.CMD File . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Customized Startup . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Using Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Redrawing Icons, Tabs, or Bit Maps . . . . . . . . . . . . . . . . . 4-3 Changing Icon Positions . . . . . . . . . . . . . . . . . . . . . . . 4-4 Changing the Color of Icon Title Text . . . . . . . . . . . . . . . . 4-4 Recovering Icons . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Creating an Icon for an Application . . . . . . . . . . . . . . . . . 4-5 Restoring the Desktop . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Updating the .INI Files . . . . . . . . . . . . . . . . . . . . . . . 4-5 Re-creating the .INI Files . . . . . . . . . . . . . . . . . . . . . 4-6 Adding an OS/2 Window to the Desktop Menu . . . . . . . . . . . . . . . 4-7 Using Executable Files . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Changing a Default Folder View . . . . . . . . . . . . . . . . . . . . 4-8 Using the Minimized Window Viewer . . . . . . . . . . . . . . . . . . . 4-8 Using Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Avoiding an "Incorrect DOS Version" Message . . . . . . . . . . . . . . 4-9 Using ANSI Colors and Characters in DOS Sessions . . . . . . . . . . . 4-9 Using the High Performance File System . . . . . . . . . . . . . . . . 4-9 Shutting Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 CHAPTER 5. APPLICATION PROGRAMS . . . . . . . . . . . . . . . . . . . 5-1 Incompatible Programs . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Improving Program Compatibility . . . . . . . . . . . . . . . . . . . . 5-2 Specific Program Compatibility . . . . . . . . . . . . . . . . . . . . 5-4 CHAPTER 6. WIN-OS/2 APPLICATION PROGRAMS . . . . . . . . . . . . . . . 6-1 Optimizing WIN-OS/2 . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Using Clipboard and Dynamic Data Exchange . . . . . . . . . . . . . . . 6-2 iv Tips and Techniques CHAPTER 7. PRINTING CONSIDERATIONS . . . . . . . . . . . . . . . . . . 7-1 Configuring Your Computer for Printing . . . . . . . . . . . . . . . . 7-1 Hardware Adapters and IRQ Conflicts . . . . . . . . . . . . . . . . . 7-2 PS/2 Direct-Memory-Access Parallel Ports . . . . . . . . . . . . . . 7-2 Selecting Printer Drivers . . . . . . . . . . . . . . . . . . . . . . . 7-2 Canon Bubble-Jet Printer . . . . . . . . . . . . . . . . . . . . . . 7-2 DeskJet, DeskJet+, DeskJet 500, and DeskJet 500C Printers . . . . . . 7-3 HP LaserJet Printer . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 HP PaintJet and PaintJet XL Printers . . . . . . . . . . . . . . . . 7-3 HP PaintJet Printer Driver for WIN-OS/2 . . . . . . . . . . . . . . . 7-3 IBM 3812, 3852, 5152, 5182, 5201-1, and 5216 Printers . . . . . . . . 7-4 IBM 4019 and IBM 4029 Printers . . . . . . . . . . . . . . . . . . . 7-4 IBM 4072 Execjet Printer . . . . . . . . . . . . . . . . . . . . . . 7-4 NEC P3200 Printer . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 NEC P6200 Printer . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Star NX-1000 Printer . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Non-Supported Printer . . . . . . . . . . . . . . . . . . . . . . . . 7-5 OS/2 1.3 Printer Drivers . . . . . . . . . . . . . . . . . . . . . . 7-6 Accessing Lexmark International Bulletin Board Service . . . . . . . . 7-6 Diagnosing Printing Problems . . . . . . . . . . . . . . . . . . . . . 7-7 Printing Is Slow . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Unable to Print . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Printer Stops Printing . . . . . . . . . . . . . . . . . . . . . . . 7-8 Print Job Damaged on Retry . . . . . . . . . . . . . . . . . . . . . 7-8 Printer Worked under DOS, but Not under OS/2 2.0 . . . . . . . . . . 7-8 Print Job Spooled but Does Not Print . . . . . . . . . . . . . . . . 7-8 Printing Starts Only When DOS Application Ends . . . . . . . . . . . 7-8 Print Job Split into Several Spool Files . . . . . . . . . . . . . . 7-9 Can Print from DOS Application, but Cannot Print Elsewhere . . . . . 7-9 Printer Worked under Windows, but Not under OS/2 2.0 . . . . . . . . 7-9 Printing from a WIN-OS/2 Session . . . . . . . . . . . . . . . . . . . 7-9 LPTx and LPTx.OS2 Port Considerations . . . . . . . . . . . . . . . . 7-9 Configuring an LPT3.OS2 Destination . . . . . . . . . . . . . . . . 7-10 Installing the IBM 4029 Laser Printer . . . . . . . . . . . . . . . 7-10 Network Printing . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 CHAPTER 8. VIDEO GRAPHICS SUPPORT . . . . . . . . . . . . . . . . . . 8-1 Super VGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 SVGA ON Utility Program . . . . . . . . . . . . . . . . . . . . . . . 8-2 OS/2 SVGA Video Files . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Additional SVGA Support Information . . . . . . . . . . . . . . . . . 8-4 Dual Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Laptop LCD or Monochrome Plasma Displays . . . . . . . . . . . . . . . 8-6 Inappropriate Font Metrics . . . . . . . . . . . . . . . . . . . . . . 8-6 WIN-OS/2 Window and Full-Screen Sessions . . . . . . . . . . . . . . . 8-7 CHAPTER 9. HARDWARE SUPPORT . . . . . . . . . . . . . . . . . . . . . 9-1 Personal Computer Manufacturer Systems . . . . . . . . . . . . . . . . 9-1 SCSI Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Adaptec and Future Domain SCSI Device Drivers . . . . . . . . . . . . 9-2 OS2SCSI.DMD Device Driver . . . . . . . . . . . . . . . . . . . . . . 9-3 SCSI CD-ROM Support . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 SCSI Removable Media Support . . . . . . . . . . . . . . . . . . . . 9-4 SCSI Usage Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Contents v AMI and CEI SCSI Adapters . . . . . . . . . . . . . . . . . . . . . . 9-6 Always Technology SCSI . . . . . . . . . . . . . . . . . . . . . . . 9-6 Additional Device Support Information . . . . . . . . . . . . . . . . . 9-6 Bernoulli Device Drivers . . . . . . . . . . . . . . . . . . . . . . 9-6 HP Scanjet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Adapter or SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Diskette Based . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Colorado Jumbo . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Mountain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 IBM PS/2 Model 30-286 Upgrades . . . . . . . . . . . . . . . . . . . 9-8 50 MHz Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Logitech 3-Button Mouse . . . . . . . . . . . . . . . . . . . . . . . 9-8 Aox Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 PerStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Interrupt Problems on an ISA System . . . . . . . . . . . . . . . . . 9-8 Communication Ports Accessed by DOS Application Programs . . . . . . 9-9 Communication Port Is Not Recognized or Does Not Work . . . . . . . . 9-9 COM3 or COM4 Support on an ISA System . . . . . . . . . . . . . . . 9-11 Setting the Interrupt Request (IRQ) Level on an ISA System . . . . 9-12 Parallel-Port-Attached Device . . . . . . . . . . . . . . . . . . . 9-13 Fax Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14 PS/2 External 5.25-Inch 1.2MB Diskette Drive . . . . . . . . . . . 9-15 IBM PS/2 Model 90 or 95 . . . . . . . . . . . . . . . . . . . . . . 9-15 Formatting Diskettes . . . . . . . . . . . . . . . . . . . . . . . . 9-15 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1 vi Tips and Techniques NOTICES _______ References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights or other legally protectable rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577. The following terms, denoted by an asterisk (*), used in this publication, are trademarks or service marks of the IBM Corporation in the United States or other countries: AT ExecJet IBM IBMLINK Micro Channel Operating System/2 OS/2 PCAT PC/XT Personal System/2 Presentation Manager Proprinter PS/2 WIN-OS/2 Workplace Shell XGA XT (C) Copyright IBM Corp. 1992 vii The following terms, denoted by a double asterisk (**), used in this publication, are trademarks of other companies as follows: TRADEMARK OWNER Boca Research Boca Research, Inc. Adobe Adobe Systems Inc. Adobe Type Manager Adobe Systems Inc.' Aox Aox Corporation AutoCAD AutoDesk, Inc. Borland C++ Borland International,Inc. Bubble-Jet Canon, Inc. Canon Canon Kabushiki Kaisha Central Point Backup Central Point Software, Inc. CodeView Microsoft Corporation Commute Central Point Software CompuServe CompuServe Inc. Control Room Ashton-Tate Corporation Corel Corel Systems CorelDRAW Corel Systems Crosstalk Digital Communications Associates, Inc. dBase Ashton-Tate Corporation Distinct Distinct Corporation DynaComm Future Soft Engineering, Inc. Epson Seiko Epson Kabushiki Kaisha Everex Everex Systems Excel Microsoft Corporation Fastback Plus Fifth Generation Systems, Inc. FastLynx Rupp Corporation FotoMan Logitech International Framework III Aston-Tate Corporation Freelance Graphics Lotus Development Corporation Harvard Graphics Software Publishing Corporation Hewlett-Packard Hewlett-Packard Company HP Hewlett-Packard Company Intel Intel Corporation Iomega Iomega Corporation LANtastic Artisoft, Inc. LapLink Traveling Software, Inc. LaserJet Hewlett-Packard Company Logitech Logitech, Inc. TRADEMARK OWNER Lotus Lotus Development Corporation Lotus Magellan Lotus Development Corporation MAGICorp MAGICorp Ltd. Mathcad MathSoft, Inc. Micrografx Micrografx Inc. Microsoft Microsoft Corporation Microsoft Windows Microsoft Corporation Mirrors Micrografx Incorporated More Windows Aristosoft, Inc. MS Microsoft Corporation MS Bookshelf Microsoft Corporation MS Excel Microsoft Corporation viii Tips and Techniques MS Flight Simulator Microsoft Corporation MS Money Microsoft Corporation MS Word Microsoft Corporation MusicPrinter Plus Temporal Acuity Products, Inc. National Geographic National Geographic Society NEC NEC Corporation Norton Backup Peter Norton Computing, Inc. Norton Utilities Peter Norton Computing, Inc. Omnipage Professional Caere Corporation Orchid Orchid Technology Inc. PageMaker Aldus Corporation PaintJet Hewlett-Packard Company Paradox Borland International, Inc. Peachtree Peachtree Software, Inc. Peachtree Complete Peachtree Software, Inc. Persuasion Aldus Corporation PFS Software Publishing Corporation PFS First Choice Software Publishing Corporation Phar Lap Phar Lap Software, Inc. PostScript Adobe Systems Inc. Powergraph STB Systems Inc. Prodigy Prodigy Services Company Publishers PowerPak Atech Software Quattro Pro Borland International, Inc. Quicken Intuit Company Quicken for Windows Intuit Company Realizer Within Technologies, Inc. SideKick Borland International, Inc. TRADEMARK OWNER SmartFax American Data Technology, Inc. Stacker Stac Electronics TI Texas Instruments Inc. Tseng Tseng Laboratories Inc. Turbo C++ Borland International, Inc. Turbo Pascal Borland International, Inc. VGAWONDER XL ATI TECHNOLOGIES INC. Windows Microsoft Corporation Windows 3.0 Microsoft Corporation Winfax Pro Delrina Technology Systems, Inc. Wing Commander Origins Systems, Inc. WordPerfect WordPerfect Corporation 8514/ULTRA ATI Technologies, Inc. Notices ix x Tips and Techniques ABOUT THIS BOOK _______________ During product development of OS/2(*) 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. The information in this book was largely collected during the final comprehensive system and compatibility testing phases, and the first few months of support line calls. While most users will not require the information in this book, it contains unique application compatibility information and other useful tips and techniques that might be helpful in specific situations. +--- IMPORTANT NOTE --------------------------------------------------------+ | | | This publication is an update to the information in the 03/92 README that | | is located in the Information folder on the desktop. It provides | | corrections to the 03/92 README as well as additional information to help | | you run your OS/2 2.0 operating system. | | | +---------------------------------------------------------------------------+ WHO SHOULD READ THIS BOOK _________________________ This book is provided as an information source for the people installing and using OS/2 2.0. Some of the information in this book is intended for the more advanced user or for the user already familiar with various functions provided with OS/2 2.0. --------------- (*) Trademark of the IBM Corporation. (C) Copyright IBM Corp. 1992 xi xii Tips and Techniques CHAPTER 1. SERVICE AND SUPPORT _______________________________ OS/2 2.0 users can access electronic support for current technical information and exchange messages with other OS/2 users, 24 hours a day. If you run into problems or simply need a question answered about OS/2 2.0, there are two ways to get help electronically: the new IBM BBS (Bulletin Board System) and CompuServe**. o For information about registering for and accessing the IBM OS/2 BBS, call 1-800-547-1283. o For CompuServe membership information, call 1-800-848-8199, and ask for representative 239. If you already are a CompuServe member, simply type "GO IBMOS2" at the ! prompt to access the IBMOS2 forum. To locate an OS/2 bulletin board system in your geographical area, call 1-609-596-1267. This locator service allows you to enter an area code, and the voice unit responds with phone numbers of bulletin boards in your area. The OS/2 Support Line provides toll-free voice support for questions related to installing or using OS/2 2.0. The voice support is available for a no-charge, no-obligation, 60-day trial. To take advantage of this special offer, and receive additional details about the OS/2 Support Line, call 1-800-237-5511. NOTE: The OS/2 Support Line is NOT available for the Extended Services OS/2 product or the Local Area Network Server Version 2.0 product. For these products, contact your place of purchase. For general IBM OS/2 product information and availability, call 1-800-3IBMOS2. IF YOU SHOULD ENCOUNTER A PROBLEM WITH THE OPERATING SYSTEM, PLEASE CONSULT THIS DOCUMENT PRIOR TO CALLING THE OS/2 SUPPORT LINE. (C) Copyright IBM Corp. 1992 1-1 1-2 Tips and Techniques CHAPTER 2. INSTALLATION CONSIDERATIONS _______________________________________ This chapter describes installation information you might need to consider before, during, or immediately after installation; including: o Upgrading from another operating system o Reformatting and partitioning the hard disk o Using non-IBM devices, such as a Logitech** mouse o Handling problems during installation. UPGRADE VERSION OF OS/2 2.0 ___________________________ The upgrade version of OS/2 2.0 (for DOS, Windows,** and OS/2 1.x) is _ slightly different from the full-purchase-price version of OS/2 2.0. You must have an operating system installed on your hard disk before you can install the upgrade version. If you formatted your hard disk before you attempted to install the upgrade version, you must put an operating system on the hard disk. If your previous operating system was DOS, start your computer with a DOS diskette, and then type the following at the DOS command prompt: FORMAT C: /S Then proceed with the installation of the upgrade version of OS/2 2.0. If installation Diskette 1 in your upgrade package is write protected, turn __________ the diskette over and locate the black tab at the bottom-right corner. Slide the black tab up so the tab covers the square hole. If the tab is missing, place a piece of tape over the hole. Covering the hole enables information to be written to the diskette during installation. (C) Copyright IBM Corp. 1992 2-1 LIMITED AVAILABILITY VERSION OF OS/2 2.0 ________________________________________ If you previously installed the OS/2 2.0 Limited Availability version of OS/2 2.0 and installed OS/2 2.0 without reformatting, you must update the OS/2 System Editor and Clipboard Viewer PATH statements in the CONFIG.SYS file. Change them so they read as follows: \OS2\APPS\E.EXE \OS2\APPS\CLIPOS2.EXE Also, you might not be able to delete existing program associations. If this occurs, make a copy of the program object that has the associations; then discard the original. REFORMATTING THE HARD DISK __________________________ Following is information about when you should and should not reformat the hard disk while you are installing OS/2 2.0. DURING INSTALLATION Consider the following when deciding whether or not to reformat the hard disk: o If you are installing over any beta version 2.0 except for OS/2 2.0 ___ ______ Limited Availability (6.177H), you must reformat. o If you formatted during installation, and the installation failed, reformat. o If you did not format during installation and the installation failed, try to install again without formatting. If the installation fails again, reformat. ( Back up any data files you need from the drive on which you want to install.) 2-2 Tips and Techniques AFTER SUCCESSFUL INSTALLATION After successfully installing OS/2 2.0, you might want to add or change some features. You do not have to reformat your hard disk and reinstall OS/2 2.0 to do this, unless you are advised to do so by your IBM dealer or representative. You can add any feature you want by selecting OS/2 SYSTEM, SYSTEM SETUP, and then SELECTIVE INSTALL. PARTITIONING THE HARD DISK __________________________ It is desirable for OS/2 2.0 to be in a partition by itself, unless you are installing Dual Boot. Then you must have both the DOS and OS/2 operating systems on the same partition. NOTE: If you are installing Dual Boot, you must have DOS on the system before you install OS/2 2.0. The OS/2 partition should be approximately 40 -- 50MB if you want the default installation and the swap drive on the same partition. Because the swapper file is based on the size of installed memory, the less memory you have, the larger the swapper file, thus you will need a larger partition. If you partition the hard disk, you should have at least 2 partitions -- one for OS/2 2.0 and one for your data. HIGH PERFORMANCE FILE SYSTEM ____________________________ Following is information about the memory requirement for the High Performance File System (HPFS) and how to install it. CONSIDERATIONS WHEN DECIDING TO USE HPFS If you are trying to decide whether to use the HPFS, consider that it takes approximately 500KB of system memory. If your computer has 6MB or less of memory, your system performance will be affected adversely. ADDING THE HPFS AFTER INSTALLATION If you selected either INSTALL ALL FEATURES or INSTALL PRESELECTED FEATURES and your computer had 6MB or less of memory, and no partitions formatted for HPFS, your computer will not have HPFS support. To install HPFS after installation of OS/2 2.0, select SELECTIVE INSTALL in the System Setup folder. In order to use the HPFS, you must format a hard disk partition with the following options: /FS:HPFS Chapter 2. Installation Considerations 2-3 ADDING DEVICE DRIVER STATEMENTS TO A CONFIG.SYS FILE ____________________________________________________ Some device driver statements might not be copied to your new CONFIG.SYS file with a REM statement if you select AUTOMATICALLY UPDATE CONFIG.SYS AND AUTOEXEC.BAT during installation. Instead, select USER EDIT CONFIG.SYS AND AUTOEXEC.BAT so you can copy your device driver statements to your new CONFIG.SYS file. GETTING YOUR MOUSE TO WORK __________________________ Following is information about getting a mouse to work. CHANGING THE DEFAULT MOUSE DRIVER During installation, do NOT make changes in the Mouse window unless it is displayed while Diskette 2 is in the installation drive. If the Mouse panel __________ is not displayed for you, OS/2 2.0 has been able to determine the correct device driver for your mouse. For example, if you have a Logitech PS/2 mouse or serial mouse, series M, the installation program will correctly select the PS/2 Style Pointing Device driver, not the Logitech Serial Mouse driver. ___ HP MOUSE To install an HP** mouse, do the following: 1. Accept the default mouse driver during the installation of OS/2 2.0. 2. Copy HILMOU.SYS and NOEXBIOS.SYS to the OS2 directory. (These files are supplied by Hewlett-Packard**.) 3. Modify your CONFIG.SYS file so it contains the following lines in the order shown: DEVICE=C:\OS2\NOEXBIOS.SYS DEVICE=C:\OS2\HILMOU.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$ If you do not have the diskette that contains the required files, contact the dealer from whom you purchased the mouse. Or, you can contact Hewlett-Packard Company customer service. 2-4 Tips and Techniques LOGITECH MOUSE NOT WORKING AFTER INSTALLATION If you have a Logitech PS/2 mouse or a Logitech serial mouse, series M, and it does not work after installation, you might have installed the Logitech Serial Mouse driver, which is NOT the correct driver. To select the correct mouse driver, use the keyboard to select OS/2 SYSTEM, SYSTEM SETUP, SELECTIVE INSTALL, MOUSE in the System Configuration window, and then OK. These steps install the default mouse driver, the PS/2 Style Pointing Device driver, that is required for a Logitech mouse. LOGITECH MOUSE NOT WORKING AFTER DUAL-BOOT SWITCH FROM DOS If your Logitech mouse is not working on a Dual-Boot system after you run DOS and switch to OS/2 2.0, your mouse might be running in a mode set by a DOS-based mouse device driver. To correct the problem, type the following at the DOS command prompt: MOUSE PC or MOUSE 1200 5B This will reset the mouse to a mode that is recognized by OS/2 2.0. Then type the following: BOOT /OS2 OS/2 2.0 should start and your mouse should work. You can perform this procedure automatically by creating a batch file for the commands you would type: MOUSE PC BOOT /OS2 or MOUSE 1200 5B BOOT /OS2 For information about creating a batch file, refer to the online Master Help Index. OTHER MOUSE NOT WORKING AFTER DUAL-BOOT SWITCH FROM DOS If your mouse works when you first turn on your computer, but it does not work when you switch from DOS to OS/2, your mouse might be emulating (acting _________ like) another kind of mouse. For example, your mouse might be emulating a Logitech mouse. Refer to the documentation that came with your mouse to see if it has a command for changing the mode. If so, try to reset the mouse to a mode that is recognized by OS/2 2.0. Chapter 2. Installation Considerations 2-5 PROBLEMS WITH INSTALLATION __________________________ The following information provides solutions for problems you might encounter during or after installation. They are: o Problems at the LOGO screen o Problems while using specific installation diskettes (they are referenced by number) o Messages that are displayed on the screen o Constant beeping while changing diskettes o White screen during or after installation o Early version of BIOS o Patch needed for ZEOS** notebook LOGO SCREEN PROBLEMS Following are problems that can occur at the LOGO screen during or after installation. With OAK Video Adapter If the installation procedure stops immediately after the LOGO screen is displayed, and you have an OAK video adapter, change the video adapter to 8-bit mode and place it into an 8-bit adapter slot. If the problem continues, you can change the OS2LDR file using the DOS DEBUG command. You must have a version of DOS on a DOS diskette or on your hard disk. To change the OS2LDR file, do the following: 1. Make a backup copy of installation Diskette 1. (You can use the DOS __________ DISKCOPY command to make the backup.) Do not change the file on your ______ original OS/2 2.0 installation Diskette 1. __________ 2. Start DOS from diskette or your hard disk. NOTE: Make sure that DEBUG.COM is on your hard disk. Change to the directory that contains the DEBUG.COM file. 3. Insert the backup copy of Diskette 1 in drive A. Type the following at __________ the DOS command prompt: DEBUG A:\OS2LDR and press Enter. 4. Type: 4f7c and press Enter. "CD." appears. 2-6 Tips and Techniques 5. Type: 90 and press the Spacebar. "10." appears. 6. Type: 90 and press Enter. 7. To write changes to the file, type: W and press Enter. 8. To end the debug procedure, type: Q and press Enter. (If you started DOS from a diskette in drive A, remove the backup copy of Diskette 1 from drive A and insert your DOS diskette __________ and press Enter. You will see the DOS prompt.) 9. Restart the installation of OS/2 2.0 using your modified backup copy of Diskette 1. __________ With Future Domain SCSI Controller If you have a Future Domain 16xx SCSI controller, you might have installed __ OS/2 2.0 successfully, but then found a problem the next time you started OS/2 2.0. If the system stopped running with the LOGO screen displayed, there might be a conflict with the interrupt settings of your hardware devices. Check all interrupt-request (IRQ) settings on all your hardware _________________ devices and make sure that each one is using a unique IRQ. Future Domain controllers are shipped from the factory preset to use IRQ5. However, IRQ5 is the interrupt that is normally assigned to LPT2. Also, it is common for IRQ5 to be used by sound or communications adapters. You might not see a problem immediately because of interrupt conflicts, but eventually a problem can occur. Refer to Chapter 9, "Hardware Support" on page 9-1, for more information about setting IRQ levels. Chapter 2. Installation Considerations 2-7 DISKETTE PROBLEMS BY NUMBER Following are solutions for problems that might occur while you are using specific installation diskettes during installation (for example, Diskette ________ 1). _ o DISKETTE 1 PROBLEM If the installation procedure stops while Diskette 1 is in the diskette __________ drive of a non-IBM computer, there might be a problem with the features of the hard disk drive controller. If the controller has on-board disk caching, disable the caching. If the controller can do asynchronous memory refreshes, turn off that feature. o DISKETTE 3 PROBLEM If the installation program keeps prompting you to insert Diskette 3, you __________ have a 1.44MB diskette drive that can work in either IBM PC/XT(*). mode or IBM PCAT* mode. You need to change the mode from XT(*) to AT(*) by changing the jumper for pin 34 on your 1.44MB diskette drive. Refer to the information that came with your computer or diskette drive to find out how to make the change. o DISKETTE 6 If the installation procedure stops after Diskette 6, the adapter for a __________ VGA display might be causing the problem. If you have a VGA display, refer to the Guide to Operations for your VGA adapter. If the adapter has autosense capability, find out how to turn off this feature. If the adapter has a resolution available other than 640x480, make sure the mode on the adapter is set to 640 x 480 mode. o NO DISKETTE 16 (3.5-INCH INSTALLATION) If you are installing the 3.5-inch version of OS/2 2.0, and the installation prompts you to insert Diskette 16, your drive A is not being ___________ recognized as a 1.44MB drive. You must set the Basic Input/Output System (BIOS) to recognize drive A as 1.44MB. Refer to the documentation that came with your computer to find out how to do this. MESSAGES ON SCREEN Following are solutions you can try when you see specific information displayed on the screen during installation. For example, there is something you can do if "C0000005" appears when the installation procedure stops. --------------- (*) Trademark of the IBM Corporation 2-8 Tips and Techniques C0000005 If "C0000005" appears on the screen the first time you start the system after installation, call the OS/2 Technical Support Center at 800-237-5511 and request a corrected version of the BVHSVGA.DLL file. COUNTRY.SYS File Cannot Be Found Following are solutions to try when OS/2 2.0 displays a message that it cannot find the COUNTRY.SYS file: o If you have a PS/2(*) P70, contact your IBM customer engineer or computer dealer and request the engineering change announcement "ECA068". o Find out if a diskette drive or a hard disk drive controller has an additional device attached to it, such as a tape backup. Disconnect the device, if possible. o Make sure the diskette drive or hard disk drive controller resides at its own IRQ level. Refer to the operations manual that came with your computer for information about the IRQ setting. Refer to Chapter 9, "Hardware Support," for more information about setting IRQ levels. SYS1200 and EC=00BF If you see the error message "SYS1200" while attempting to use the Dual Boot feature to change to DOS, and you also see error code "EC=00BF" (meaning that the DOS environment cannot be created), check your CONFIG.SYS file. Make sure your virtual DOS device drivers are listed correctly in your CONFIG.SYS file. COMPUTER BEEPS CONSTANTLY If your computer beeps constantly while you are changing diskettes during installation, you might have a defective-diskette drive controller or cable. Check the controller and cable for damage, and also check all their connections. WHITE SCREEN PROBLEMS The following sections provide problem determinations if you encounter a white screen during or after installation. --------------- (*) Trademark of the IBM Corporation Chapter 2. Installation Considerations 2-9 With Disk Light On Constantly If you are installing OS/2 2.0 on a fast 486 ISA-bus computer, you might see a white screen and the disk light constantly on. If so, try switching the system board out of turbo mode, to reduce the speed of the computer. Refer to the documentation that came with your computer to find out how to change the mode. After Installation If the display screen is white after installation and there is no system activity, set the video adapter to 8 bits and move the adapter to an 8-bit slot. If possible, disable the auto-switching capability of the video adapter. Refer to the documentation that came with your video adapter. With an ATI Video Adapter If the display screen is white after installation, and you have an ATI 8514/ULTRA or Graphics Ultra video adapter, you might have an early version of a video ROM chip on the adapter. Contact ATI at 416-756-0711 to request an update. BIOS PROBLEMS Following is information about systems and system boards that do not support OS/2 2.0 because of an earlier version of the BIOS. Information is provided about how to upgrade the BIOS. Phoenix BIOS You must have a level 1.02.05D, or later, BIOS from Phoenix to run OS/2 2.0. AMI BIOS The later BIOS versions from American Megatrends, Inc. (AMI) provide a screen ID code, which is visible at the lower-left corner of the screen during the initial random-access-memory (RAM) count. The code can be made to reappear if you restart the system by pressing Ctrl+Alt+Del, or it can be frozen on-screen by holding down the Ins key during system startup. This creates a keyboard error, which will stop the screen for the error message: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If the screen ID code is in a form other than the above, the BIOS is either (1) a very early version, or (2) it was produced by a company with source-code license. In the first case, contact Washburn & Co. at 716-248-3627. In the second case only, the system board manufacturer will be 2-10 Tips and Techniques able to provide further information or updates. All Everex** 368 BIOS versions are in the second category. GENERAL RULES: 1. If an IDE-type hard drive is installed, the date mmddyy should be 040990 ______ or later for use with any operating system, including DOS. This is because of the special timing requirements of IDE drives, which were accommodated on the date noted. 2. With any other drive type, such as MFM, RLL, ESDI, or SCSI, the OS/2 operating system might install and operate correctly if mmddyy is 092588 ______ or later, provided that the Keyboard Controller revision level is suitable for the OS/2 version being used. Also, in the case of SCSI hard drives, a driver compatible with the version of OS/2 operating system being installed might be provided by the controller manufacturer, and if so, a special installation procedure might apply. 3. The Keyboard Controller revision levels ("c" in the previous screen ID code examples) expected to produce proper installation and operation of the various OS/2 operating system versions are as follows: OS/2 1.0 or 1.1: 8, B, D, or F OS/2 1.2x: D or F OS/2 1.3x or 2.0: F 4. If the Keyboard Controller revision level shows as 0 or M, the Keyboard Controller chip is not an AMI chip, even if an AMI license sticker was ___ applied to it by the system board of original equipment manufacturer (OEM). This means that its performance under the OS/2 operating system is unknown. It might or might not work correctly. In some cases, (usually "M"), an AMI chip can successfully replace a non-AMI chip, but this is not a general rule. Sometimes the nonstandard Keyboard Controller (usually "0") was used to combine system board functions not normally part of the controller. Substituting a standard chip causes the board to not function at all. In this case, there is no solution other than to replace the board. A revision level of 9 accompanied by a nonstandard ID code, also indicates a nonstandard controller (and BIOS). The system board manufacturer should be contacted for further information. BIOS UPDATES: If a BIOS prior to the previously noted dates requires replacement, note the following: 1. AMI BIOS and BIOS Plus series BIOS (16 character ID code) for cached system boards are customized for individual system board designs. They can only be obtained from the system board OEM, with only three common exceptions: a. BIOS's with "aaaa" = E307 can often be replaced with a standard type. b. BIOS's for Northgate or Motherboard Factory system boards, except the Northgate Slimline, can be replaced by a standard type. Slimline BIOS's have the VGA BIOS in the same chips. They can be updated to the 040990 release, provided they are identified as Slimline, and the speed is specified (20, 25, or 33 MHz). The speed must be specified because different VGA code is required for the various speeds. Chapter 2. Installation Considerations 2-11 c. BIOS's with "aaaa" = DAMI, DAMX, or EDAMI are usually for cached boards designed or built by AMI, and if so, can be updated. Mylex or Leading Technology boards with these prefixes can only be updated by the board manufacturer. 2. The complete screen ID code is necessary to determine whether a BIOS update for other system boards can be provided. In the case of the Hi-Flex BIOS, the complete second and third lines of the ID code are also necessary. If not immediately visible on the screen, they can be viewed by pressing the Ins key during system startup. 3. If you have a hard disk drive from another manufacturer, it must be dated 092588 or later. If your hard disk drive is an early version, contact the dealer at your place of purchase, or the manufacturer, for information about upgrading the drive. Micronics System Board If your computer does not work properly, (for example, you receive a "divide underflow" message), you might have revision E of a Micronics system board. This board contains an early version of BIOS. If you purchased the board from Gateway, contact Gateway 2000, Inc. at 800-523-2000 and request an upgrade to revision F. Gateway 2000 Computer If you have an early version of a Gateway 2000 computer that does not work properly, your BIOS might be an early version. The company suggests that you replace the system board. Contact Gateway 2000, Inc. at 800-523-2000 for information about upgrading your computer. Gateway 486 Computers If you have a Gateway 486 computer with a Rev E system board, there is potential for a DIVIDE UNDERFLOW error. The error is caused when running software that takes advantage of the 486 math coprocessor. If this error occurs, you can upgrade to a Rev F system board by contacting Gateway. Gateway Computers and Trap 2 Errors on Boot or Installation Gateway computers that cause a Trap 2 error are caused by one of the following: o A bad Read Ahead Cache on the system board o Bad memory When the problem is a bad Read Ahead Cache on the system board, press Ctrl+Alt+Esc to disable the external caching. Contact Gateway when this problem is encountered. 2-12 Tips and Techniques When the problem is bad memory, try moving the memory sims. If the problem is not corrected, locate the memory sim that is bad and replace it. Gateway Nomad Notebook If you receive a "COUNTRY.SYS not found" message, your computer needs a BIOS upgrade. NOTE: If a trap error appears when the system is started, or during installation, disable caching on the system board. If the problem persists, contact Gateway 2000, Inc. at 800-523-2000. ZEOS NOTEBOOK If you have a ZEOS notebook and the installation of OS/2 2.0 fails, you can correct the installation problem by adding a patch to your Installation ____________ Diskette. ________ NOTE: To do this, use another computer that has OS/2 2.0 installed on it. You also will need the OS/2 2.0 Installation Diskette and a blank, _____________________ formatted, high-density 3.5-inch diskette. If you are unable to find a computer to use, call the OS/2 Technical Support Center at 800-237-5511 and request that a patched Installation Diskette be _____________________ sent to you. To install the patch using a computer that has OS/2 2.0 running on it, do the following: 1. Select OS/2 SYSTEM on the OS/2 desktop. 2. Select COMMAND PROMPTS. 3. Select OS/2 WINDOW. You will see an OS/2 command prompt. 4. Back up your Installation Diskette to the blank 3.5-inch diskette you _____________________ brought with you by typing the following: DISKCOPY A: A: Then press Enter and follow the prompts. 5. Place the newly created backup Installation Diskette in drive A. _____________________ 6. Type: PATCH SYSINSTX.COM Then press Enter. 7. When asked for the offset address, type: 96AF Then press Enter. 8. Change "44" to "45"; then press Enter. The following message is displayed: Chapter 2. Installation Considerations 2-13 Do you wish to continue patching sysinstx.com? 9. Type: N Then press Enter. 10. When asked if you want to apply patches, type: Y Then press Enter. 11. At the OS/2 command prompt, type: SYSINSTX A: The patch is complete. 12. Install OS/2 on your ZEOS notebook computer using the patched backup Installation Diskette that you just created. _____________________ SHORT CUT IF YOUR INSTALLATION PROCEDURE STOPS ______________________________________________ If the installation procedure stops before completion, you might be able to complete the installation without reusing all the installation diskettes. You do not have to use all diskettes again if the installation stopped after you were prompted to put the Installation Diskette in the drive the second _____________________ time (after you are in the graphical installation). For example, if you were _________ copying files from Diskette 9 on a 3.5-inch-diskette system, you could resume __________ the installation at Diskette 9 after doing the following: __________ 1. Identify which diskette was being "unpacked" when the installation procedure stopped. 2. Subtract the number of that diskette from 15 and add one to the result if you have 3.5-inch installation diskettes. (Subtract the number from 18 if you have 5.25-inch installation diskettes.) For example, if you were on Diskette 9 on a 3.5-inch system, the result would be 7. __________ _ 3. Start the computer with the Installation Diskette, and then insert _____________________ Diskette 1 when prompted. __________ 4. When you are asked to press Esc to cancel, press Esc. You will see a command prompt. 5. Use a text editor to edit the CONFIG.SYS file on your hard disk. 6. In the line that starts with FIRSTDISK, change the number to the number of the diskette that was in the diskette drive when the installation procedure stopped. In the example, this is 9. _ FIRSTDISK=9 2-14 Tips and Techniques 7. In the line that starts with NUMDISKS, change the number to the one you reached in step 2. In the example, this is 7. _ NUMDISKS=7 8. Remove the diskette and press Ctrl+Alt+Del. You will see the graphical install panel. Select OK, then INSTALL, and select all defaults. 9. When you are prompted, insert the diskette named in the prompt. In the example, this would be Diskette 9, the diskette that was being loaded __________ when the installation procedure stopped. All the Selective Install choices that you selected when you first tried to install OS/2 2.0 are preserved. USING DOS AND WINDOWS APPLICATIONS __________________________________ Following is information about running DOS or Windows applications: NEWLY INSTALLED DOS OR WINDOWS APPLICATIONS: After installation, and before you run any DOS or Windows applications, shut down your system and restart it. You only have to do this once, immediately after you finish installing OS/2 2.0. EXISTING APPLICATION NOT MIGRATED: Occasionally, the Migrate Applications program might not find all applications. In this case, retry the Find Programs operation. WINDOWS VERSION 3.1: IBM's testing of Windows Version 3.1 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. INSTALLING A LOCAL AREA NETWORK _______________________________ To install OS/2 2.0 across a local area network (LAN), purchase IBM LAN _______ Installation Utility/2 (LIU/2), program package number 5799-PTC. To order ______________________ the package, contact your IBM representative or an IBM dealer. INSTALLING A RESPONSE FILE __________________________ Following is additional information for the "Copying the Response File to a 5.25-Inch Diskette" section of Chapter 5 in the OS/2 2.0 Installation Guide. ___________________________ If you are installing OS/2 2.0 in a non-Micro Channel(*) computer: --------------- (*) Trademark of the IBM Corporation Chapter 2. Installation Considerations 2-15 o Delete the following additional files from your copy of Diskette 1: __________ IBM2*.ADD *O2.SYS o Delete the following additional statements from the CONFIG.SYS file on your copy of Diskette 1: __________ BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2SCSI.ADD If you are installing OS/2 2.0 in a Micro Channel computer: o Delete the following additional files from your copy of Diskette 1: __________ IBM1*.ADD *01.SYS o Delete the following additional statements from the CONFIG.SYS file on your copy of Diskette 1: __________ BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD INSTALLING CD-ROM _________________ After you have installed the operating system, if you install CD-ROM using the SELECTIVE INSTALL program, do not install any other options at the same time. ENABLING UNDELETE _________________ To enable the UNDELETE command, delete "REM" from the beginning of the following statement in the CONFIG.SYS file: REM SET DELDIR= DUAL BOOT DOES NOT WORK _______________________ If you cannot switch from DOS to OS/2 by typing BOOT /OS2, you might have one or more active terminate and stay resident (TSR) or DOS cache programs. If so, end the programs before you switch to DOS. USING BOOT MANAGER __________________ Following is information about using the Boot Manager. 2-16 Tips and Techniques BOOT MANAGER MENU BYPASS The Setboot utility program supports an immediate-restart function that will restart the system to the specified drive without going through the Boot Manager Menu. The parameter is /IBD:DRIVE, where DRIVE is the letter of a _____ _____ startable partition. For example, from the OS/2 command prompt, you can type SETBOOT /IBD:E to start the logical drive E without displaying the Boot Manager Menu. (If the Boot Manager is not present, then only drive C can be specified.) OS/2 VERSION 1.3 IN A PARTITION WITH DUAL BOOT If you are using Boot Manager, and one of your partitions contains OS/2 Version 1.3 with Dual Boot, copy BOOT.COM from the OS/2 2.0 \OS2 subdirectory to the OS/2 Version 1.3 \OS2 subdirectory. USING NON-IBM COMPUTER WITH TWO DRIVES ______________________________________ If you have a non-IBM computer with two hard disk drives, the second drive might not work properly after you install OS/2 2.0. If so, reformat that drive with DOS or OS/2 2.0. Chapter 2. Installation Considerations 2-17 2-18 Tips and Techniques CHAPTER 3. SYSTEM PERFORMANCE CONSIDERATIONS _____________________________________________ Following are some performance considerations that you should be aware of. For more performance guidelines, see the Information and Planning Guide ______________________________ document (G326-0160) that can be obtained from your place of purchase or retrieved through CompuServe. MEMORY REQUIREMENTS ___________________ The minimum memory requirement for OS/2 2.0 is 4MB. (This includes up to 128KB that is used on some systems for ROM to RAM remapping.) Some systems use more than 128KB for other purposes, so less than the minimum required memory is available. On these systems, you might need another 512KB to 1MB to satisfy the minimum requirements. Check your system to see if it offers a way to recapture the memory so that you can regain 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 preallocates the SWAPPER.DAT file based on the size of installed memory. This is done to optimize performance and reduce disk fragmentation. To tune the size of the swapper file, see the information about SWAPPATH in the Command Reference. _________________ In OS/2 2.0, the SWAPPER.DAT file is designed to shrink in size when the data segments are no longer needed, but does not shrink as expected. This problem has been fixed by IBM APAR PJ03686, available from CompuServe or the IBM BBS. Ignore any CHKDSK errors that might be reported on the SWAPPER.DAT file. These error indications are normal. FILE SYSTEMS ____________ Many performance changes have been incorporated into OS/2 2.0 file systems. They are the file allocation table (FAT) and the high performance file system (HPFS). 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, (C) Copyright IBM Corp. 1992 3-1 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 APPLICATION PROGRAMS ________________________ You can improve the performance of some DOS application programs by adjusting the DOS settings. If the program does not require extended or expanded memory, these values can be set to zero. This will provide maximum performance. Some DOS programs use polling techniques to poll the system for work. An example is a program 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 suspend the program while it is polling. WINDOWS APPLICATION PROGRAMS ____________________________ Windows application programs 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 programs simultaneously, you might want to increase the DPMI memory limit before starting the first program. The first program that is started determines the DPMI memory available for all subsequent Windows programs that are used. In low-memory configurations, you can run multiple Windows programs 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: o Double-click on the minimized program object, or o Display the OS/2 Window List and double-click on the program name. If you choose to migrate your Windows programs (at installation time or later using MIGRATE), most Windows programs will run in one WIN-OS/2 session. If you set up a Windows program and do not use MIGRATE, each program runs in its own WIN-OS/2 session. If you are running Windows programs 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: 3-2 Tips and Techniques 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 programs receiving 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 exchange between Windows programs and Presentation Manager programs, and between Windows programs in separate WIN-OS/2 sessions, edit the OS2\MDOS\WINOS2\SYSTEM.INI file. Under 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. APPLICATION PROGRAM USAGE _________________________ If you have an application program that you always use, you can set up the program in the Startup folder to load when the system is started. To avoid reloading frequently used programs, minimize the program after use and simply maximize it to use it again. You can find the program in the Window List or the Minimized Window Viewer. If you use several different programs, 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. TIP: Close opened programs 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. 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. Chapter 3. System Performance Considerations 3-3 3-4 Tips and Techniques CHAPTER 4. OS/2 WORKPLACE SHELL ________________________________ This chapter describes tasks associated with using the OS/2 Workplace Shell(*). For WIN-OS/2-specific topics, refer to Chapter 6, "WIN-OS/2 Application Programs." STARTING UP YOUR SYSTEM _______________________ This section describes information that controls the operation of your system at startup time. FILE SYSTEMS If you are using the file allocation table (FAT) file system, update your CONFIG.SYS file with the following statement to autocheck drive C (or your startable partition) to ensure disk data is verified prior to using the hard disk: DISKCACHE=64,LW AC:C If you are using the High Performance File System (HPFS), this function is done automatically. THE STARTUP FOLDER The Startup folder is the OS/2 Workplace Shell equivalent of the STARTUP.CMD file. Objects placed in a Startup folder are started when the Desktop folder is opened. You cannot specify the order in which the objects are started. NOTE: Place program objects in this folder instead of the executable program-file objects. --------------- (*) Trademark of the IBM Corporation (C) Copyright IBM Corp. 1992 4-1 PREVENTING AUTOMATIC STARTUP If you want to prevent programs from automatically starting when the computer is restarted (for example, programs located in the Startup folder or programs that were running at the time the computer was shut down), do the following: 1. Press Ctrl+Alt+Del to restart the computer. 2. When the mouse pointer appears, press Ctrl+Shift+F1. 3. Hold the keys for approximately 15 seconds, or until the desktop icons appear. (If the hard disk light stops during this time, your computer might be suspended. Release the keys quickly, and then resume holding the keys until the desktop icons appear.) STARTUP.CMD FILE The STARTUP.CMD file is started before the OS/2 Workplace Shell is started; therefore, you cannot start applications using this file if they require an initialized shell. CUSTOMIZED STARTUP If you want a customized system startup, you can update your CONFIG.SYS file with the following statements: SET RESTARTOBJECTS = YES Default. Start all objects that were running at time of shutdown. NO Do not start any applications that were running at time of shutdown. STARTUPFOLDERSONLY Start objects only in the Startup folder. REBOOTONLY Start objects only if the OS/2 Workplace Shell is starting after resetting with Ctrl+Alt+Del or turning on the computer. This parameter can be used with one of the other parameters (for example, YES). 4-2 Tips and Techniques SET AUTOSTART = FOLDERS Folders are opened, including the Desktop folder. TASKLIST The Window List is opened. PROGRAMS Programs are opened. CONNECTIONS Re-creates the network connections established when you last logged on. NOTE: The SET AUTOSTART statement is used to start parts of the OS/2 Workplace Shell. Eliminating any of the options in the list restricts users from accessing portions of the shell (for example, limiting a user to only a few applications). USING ICONS ___________ The following sections describe some of the tasks associated with using Icons. Icons are miniature pictures that represent an object. For example, ______ if you install a printer, your printer object appears as a miniature picture of a printer. REDRAWING ICONS, TABS, OR BIT MAPS o Because of system (memory) resource limitations, when too many applications are open, or when too many bit maps are visible on the screen, new icons, tabs, or other bit maps might not be drawn. To remedy this, close unused folders and applications so the resources can be used by other processes. o If some system icons (such as OS/2 System or Shredder) do not appear when you start the operating system, you can reset the desktop to its default configuration by doing the following: WARNING: THIS PROCEDURE REMOVES ANY DESKTOP CUSTOMIZATION DONE SINCE INSTALLING THE OPERATING SYSTEM. 1. Press Ctrl+Alt+Del to restart the computer. 2. Before the OS/2 Logo panel appears, hold down Alt+F1 for 20 seconds. The current versions of the CONFIG.SYS, OS2.INI, and OS2SYS.INI files are renamed and replaced by the default installation versions in the \OS2\INSTALL subdirectory. If you have a STARTUP.CMD file, it also is renamed. This deactivates the startup feature. Chapter 4. OS/2 Workplace Shell 4-3 CHANGING ICON POSITIONS If you install IBM LAN Server 2.0, the positions of the icons on your screen might change. To rearrange the icons: 1. Display the pop-up menu for the Desktop folder by clicking mouse button 2 on an area not covered by any objects or windows. 2. Click on Arrange. CHANGING THE COLOR OF ICON TITLE TEXT If you want to change the color of the title text of all the icons in a ___ folder, do the following: 1. Select OS/2 SYSTEM. 2. Select SYSTEM SETUP. 3. Select COLOR PALETTE. 4. Press and hold Ctrl; then, pressing and holding mouse button 2, drag a color to an icon. Drop the color; then release Ctrl. NOTE: You cannot change the color of individual icon-title text. RECOVERING ICONS o If you lose a folder by moving it to a folder you are unable to access, you can recover the folder. From an OS/2 Window, use the MOVE command to relocate the folder (for example, the OS/2 System folder, "OS!2_SYS"), to the proper location. WARNING: THE FOLLOWING PROCEDURE SHOULD BE USED ONLY IF A FOLDER IS INACCESSIBLE TO THE OS/2 WORKPLACE SHELL. To move a folder (for example, the "OS!2_SYS" folder): 1. Change to the directory where the "OS!2_SYS" folder is located. 2. Type the following to move the folder back to the Desktop folder. For FAT, type: MOVE OS!2_SYS \OS!2_2.0_D For HPFS, type: MOVE "OS!2 SYSTEM" \"OS!2 2.0 DESKTOP" o If, intermittently, the icons on your desktop open normally but appear black, there might have been a timing problem that occurred when a new icon was saved using the General page in the settings notebook. Try correcting the appearance by re-creating or restoring the icon. 4-4 Tips and Techniques CREATING AN ICON FOR AN APPLICATION If you want to create an icon for a DOS, Windows, or OS/2 application that does not have one, but has graphics within the application, do the following: 1. Run the application in a window session. 2. When you see an icon-sized graphic that you would like to use as the icon to represent your program, size the window, making the image approximately the size of a desktop icon. 3. Click on the title-bar icon (in the upper-left corner of the window); Select MARK. 4. Mark the graphic. 5. Select COPY to move the graphic to the clipboard. 6. Display the pop-up menu for the object by moving the mouse pointer to it and clicking mouse button 2. 7. Click on the arrow to the right of OPEN. 8. Select SETTINGS; then select the GENERAL tab to display the default icon. 9. Select CREATE ANOTHER to display the Icon Editor. 10. Select FILE, NEW, ICON; then select OK. 11. Select EDIT, then PASTE to paste in your graphic. If necessary, use the Icon Editor to make any changes you want in the graphic. 12. Select FILE, then SAVE to store the program name.ICO file in the same ____________ drive and directory as the program file (.COM or .EXE file). 13. Double-click on the title-bar icon to exit the editor. 14. From the settings notebook, Select FIND; then locate the saved .ICO file. (Selecting DRIVES is the easiest search.) 15. Click on the icon; then save the file. 16. Exit the settings notebook. The original icon is replaced with the graphic from the application. RESTORING THE DESKTOP _____________________ If your desktop becomes damaged (for example, you started a specific version of DOS and rearranged your hard disk, damaging .INI files or extended attributes), you must restore the initial .INI and CONFIG.SYS files to restore the desktop. However, any modifications (such as shadows and associations created after installation) are lost and must be re-created. UPDATING THE .INI FILES To restore the desktop, do the following to update your existing .INI files: 1. Restart your computer using the OS/2 Installation Diskette; then insert __________________________ Diskette 1. __________ 2. Press Esc to access an OS/2 full screen; then change to the \OS2 directory. 3. Type: MAKEINI OS2.INI INI.RC (and press Enter) MAKEINI OS2SYS.INI INISYS.RC (and press Enter) Chapter 4. OS/2 Workplace Shell 4-5 4. Delete the hidden file WP ROOT. SF in the startable partition. For HPFS, type: ATTRIB -h -s -r "WP ROOT. SF" (and press Enter) For FAT, type: ATTRIB -h -s -r WP_ROOT._SF (and press Enter) Next, for HPFS type: DEL "WP ROOT. SF" (and press Enter) For FAT, type: DEL WP_ROOT._SF (and press Enter) If the above procedure does not fix the problem, do the following to recover the backup .INI files. You will lose all your desktop customization, but the desktop should be restored. 1. Press Ctrl+Alt+Del to restart your computer. 2. As soon as you hear a single beep, or you press Enter at the Boot Manager menu or power-on password prompt, press and hold Alt+F1. Hold these keys down until you hear rapid beeping. RE-CREATING THE .INI FILES If the preceding procedures do not fix the damaged desktop, do the following to re-create the .INI files: 1. Restart your system using the OS/2 Installation Diskette; then insert __________________________ Diskette 1. __________ 2. Press Esc to access an OS/2 full screen; then change to the OS2 directory. 3. Delete the current .INI files. Type: DEL OS2.INI (and press Enter) DEL OS2SYS.INI (and press Enter) 4. Re-create both files using the MAKEINI command. Type: MAKEINI OS2.INI INI.RC (and press Enter) MAKEINI OS2SYS.INI INISYS.RC (and press Enter) 5. Change to the desktop directory, OS!2_2.0_D (FAT) or "OS!2 2.0 DESKTOP" (HPFS). 6. Delete all subfolders (subdirectories) in this directory. 7. Change to the root directory. 4-6 Tips and Techniques 8. Delete the hidden file WP ROOT. SF in the startable partition. For HPFS, type: ATTRIB -h -s -r "WP ROOT. SF" (and press Enter) For FAT, type: ATTRIB -h -s -r WP_ROOT._SF (and press Enter) Next, for HPFS, type: DEL "WP ROOT. SF" (and press Enter) For FAT, type: DEL WP_ROOT._SF (and press Enter) 9. Press Ctrl+Alt+Del. The desktop is reinstalled to its initial installation setup. 10. Shut down the system using the SHUT DOWN choice on the desktop pop-up menu. NOTE: Use MAKEINI instead of the Alt+F1 key combination if you do not want to replace the CONFIG.SYS file and desktop. The installation process places a copy of the original OS2.INI, OS2SYS.INI, and CONFIG.SYS files in the \OS2\INSTALL subdirectory. These are the same .INI files created with MAKEINI. They will rebuild the desktop and set it to its initial installed state. Alt+F1 replaces OS2.INI, OS2SYS.INI, and the CONFIG.SYS files. ADDING AN OS/2 WINDOW TO THE DESKTOP MENU _________________________________________ If you want another method of accessing an OS/2 Window, you can add OS/2 WINDOW as a new menu choice on the desktop pop-up menu. Do the following: 1. Display the pop-up menu for the Desktop folder by clicking mouse button 2 on an area not covered by any objects or windows. 2. Click on the arrow to the right of OPEN. 3. Select SETTINGS; then select the MENU tab. 4. From the ACTIONS ON MENU choices, select CREATE ANOTHER. 5. In the MENU ITEM NAME field, type: OS/2 Window 6. In the PROGRAM NAME field, type: C:\OS2\CMD.EXE Change to a different drive, if necessary. 7. Select OK. 8. Double-click on the title-bar icon to close the notebook. Chapter 4. OS/2 Workplace Shell 4-7 9. Display the Desktop folder pop-up menu again. "OS/2 Window" is added to the available menu choices. If you select this choice, an OS/2 Window is displayed. USING EXECUTABLE FILES ______________________ Do not move program-file objects (.EXE, .COM, .CMD, and .BAT files) from their installed directories (for example, moving a program-file object from the Drives folder to a new location). Moving program-file objects might cause some program objects to not function properly. Instead, create a new object that refers to the original, either a program object or a shadow; then you can move the new object to a location of your choice. (Program-object settings and shadow settings specify the location of the original program-file object.) To create a program object or shadow: 1. Display the pop-up menu for the program-file object by moving the mouse pointer to it and clicking mouse button 2. 2. Select CREATE ANOTHER or CREATE SHADOW. 3. Select a folder for the new object; then select CREATE. NOTE: The CREATE ANOTHER choice, when used on a program-file object, creates a program object, not a program-file object. CHANGING A DEFAULT FOLDER VIEW ______________________________ If you want to change the default view for displaying the objects within a folder (for example, icon versus details view), do the following: 1. Display the pop-up menu for the folder by moving the mouse pointer to it and clicking mouse button 2. 2. Click on the arrow to the right of OPEN. 3. Select SETTINGS; then select the MENU tab. 4. Select OPEN in the AVAILABLE MENUS field. The Menu Settings window is displayed. 5. In the DEFAULT ACTION field, select the default you want. 6. Select OK. USING THE MINIMIZED WINDOW VIEWER _________________________________ o In the Minimized Window Viewer settings notebook, disregard "Page 1 of 3." Each section of the notebook contains 1 page only. o Some objects, such as WIN-OS/2 programs, online books, and programs that start other programs, do not minimize to the Minimized Window Viewer. 4-8 Tips and Techniques USING FIND __________ o In the Help information for Find, disregard any references to "page 2." Page 2 does not exist in Find operations. o If you change the title of an object from within the Find Results folder, the name of the original object is changed. AVOIDING AN "INCORRECT DOS VERSION" MESSAGE ___________________________________________ If you receive the message "Incorrect DOS version" when trying to run a DOS application under OS/2 2.0, the application is using an earlier version of DOS on your computer. To fix the problem, update the DOS setting DOS_VERSION using the Value field of the DOS Settings window. For example, PROG.EXE,5,0,255 (program, major version, minor version, count) This setting simulates the DOS 5.0 version check as opposed to the OS/2 2.0 version check. USING ANSI COLORS AND CHARACTERS IN DOS SESSIONS ________________________________________________ If you want to use ANSI colors and characters in your DOS sessions, do the following: 1. Add the following statement to your CONFIG.SYS file: DEVICE=C:\OS2\MDOS\ANSI.SYS 2. Shut down your computer. 3. Press Ctrl+Alt+Del to restart your computer and make the change active. USING THE HIGH PERFORMANCE FILE SYSTEM ______________________________________ o If you formatted your installed drive with the High Performance File System (HPFS), you might not be able to access files in the Desktop folder from DOS or WIN-OS/2 applications. DOS and WIN-OS/2 applications use the FAT file system. If you experience this problem, the partition should be reformatted with the file allocation table (FAT) file system. o If you are typing a command in the HPFS, you must include double quotation marks around the name of the subdirectory or file name if it contains blanks. For example, to change to the OS!2 2.0 DESKTOP directory, type: CD "OS!2 2.0 DESKTOP" As another example, to copy the file This is my file from the root _______________ directory to the This is my directory subdirectory, type: ____________________ Chapter 4. OS/2 Workplace Shell 4-9 COPY "THIS IS MY FILE" \"THIS IS MY DIRECTORY" NOTE: In the FAT file system, HPFS file names are shortened. Underscores represent blank spaces. SHUTTING DOWN _____________ o Sometimes when system (memory) resources are limited, the final shutdown message might not appear after a shutdown is performed. To ensure that shutdown is complete, wait until all disk activity stops before turning off or restarting your computer by pressing Ctrl+Alt+Del. o If you want to shut down your system without using a mouse, do the following: 1. Press Ctrl+Esc to display the Window List. 2. Press the Up Arrow (A) to move the cursor to "OS/2 2.0 Desktop - Icon View"; then press Enter. 3. Press Ctrl+\ to deselect any selected icons. 4. Press Shift+F10 to display the pop-up menu for the desktop. 5. Press the Down Arrow (V) to move the cursor to SHUT DOWN; then press Enter. o You should shut down your system before restarting or turning off your computer; however, there are situations where you might want to restart your system by pressing Ctrl+Alt+Del instead: - If you used the ARRANGE choice on the Desktop folder pop-up menu, it rearranged the icons you placed in specific positions on the screen. Restarting your system recovers your icon positions. - If you opened several folders containing many icons, shutdown will take a long time saving the positions of the icons. You might want to restart your system without using the SHUT DOWN choice on the desktop pop-up menu as long as you are certain that you will not lose anything else of importance. o If you shut down your system, but do not receive the message "Shutdown has completed. It is now safe to turn off your computer...", you should wait for all disk activity to stop, and then you can turn off your computer or press Ctrl+Alt+Del. 4-10 Tips and Techniques CHAPTER 5. APPLICATION PROGRAMS ________________________________ Most DOS, Windows, and OS/2 programs run under OS/2 2.0 without any modification. A few need specific attention. This chapter provides that information. INCOMPATIBLE PROGRAMS _____________________ The following identifies categories of programs that do not work correctly with OS/2 2.0. o DOS extenders that require exclusive access to the 80386 control registers, such as the Virtual Control Program Interface (VCPI), are not supported because they would conflict with OS/2 2.0 operations. The DOS Protect-Mode Interface (DPMI 0.9), the Expanded Memory Specification (EMS), and the Extended Memory Specification (XMS) are supported. o Programs that directly address the physical disk sectors to perform disk-write operations are not supported. These operations would conflict with OS/2 2.0 operations. This category includes most DOS UNDELETE programs. o Some Windows programs make use of the Windows accessory programs, like the Calculator. If you already had Windows Version 3.0 installed and you did not format your hard disk when you installed OS/2 2.0, the accessory programs are on your hard disk and are supported by OS/2 2.0. However, the accessory programs are not part of the WIN-OS/2 environment included with OS/2 2.0. o Programs (and hardware) that require the Windows Enhanced mode are not supported. This mode uses an unsupported memory-management method. Programs that run in Windows standard mode and real mode are supported. o Programs that manipulate the 80386 control registers, such as 386 DOS debuggers, are not supported; this would conflict with OS/2 2.0 operations. o Fax boards and programs that use more that 1000 interrupts per second (9600 baud or greater) are not supported. The following fax boards and programs contain timing sensitivities that might prevent reliable operation: - ATI ETC - Cardinal FAX - Practical Peripherals - Smartfax** - Twincomm 24/96 (C) Copyright IBM Corp. 1992 5-1 The programs listed here fit into one or more of the categories listed in the previous section: - 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 - PharLap** DOS extenders prior to Version 4.0 - Realizer** 1.0 (Windows) - Sherlock Holmes CD-ROM (DOS) - Smartfax (DOS) - Soft-ICE (DOS) - Splash 1.01 (DOS) - Turbo Debugger (DOS) IMPROVING PROGRAM COMPATIBILITY _______________________________ The following provides techniques that improve program compatibility: o For more reliable DOS communications performance on slower systems, the combined baud rate should not exceed 9600 bps for one or more concurrent DOS applications. o You can improve the performance of DOS communications programs by using the 16450 UART or 16550AFN UART communications chips. o If you run a bulletin board or a DOS communications application that keeps timing out, change the DOS settings as indicated below. If the first settings change does not fix the problem, change the next settings, and so forth. 1. HW_TIMER to ON 2. IDLE_SECONDS to 60, and IDLE_SENSITIVITY to 100 3. COM_HOLD to ON 4. HW_ROM_TO_RAM to ON 5. If you lose data using DOS communications software, set the PRIORITY_DISK_IO setting to NO in your CONFIG.SYS file, and the IDLE_SENSITIVITY setting to 100% in the DOS settings for the object. If the DOS-settings changes do not fix the problem, set PRIORITY_DISK_IO to NO in the CONFIG.SYS file. 5-2 Tips and Techniques o Some DOS and Windows programs run correctly only in full-screen sessions. Any Windows program that does not use the Windows application program interface (API) function to change the video mode should be run in a WIN-OS/2 full-screen session. o Some DOS and Windows programs must be installed or run in a specific DOS ____________ session. A specific DOS session is started by booting from an actual _______ version of DOS. For more information, refer to "DOS, starting specific version" in the online Master Help Index. o Some programs run in OS/2, DOS, or WIN-OS/2 sessions, but require that you install the program under DOS. o Windows programs cannot start DOS sessions or DOS programs. o DOS programs that use low-level file-system calls cannot access HPFS disks. o If you are running communications programs, set the CONFIG.SYS statement PRIORITY_DISK_IO to NO; then restart your system. o Code-page-switching support is not available for graphics mode in DOS sessions. o Some DOS and Windows programs use security keys as protection against copyright infringement. The security key is a 25-pin connector that is connected to the parallel port of the computer on which the program is executing. The program checks to see if the connector is attached and, if the connector is not present, the program is assumed to be an illegal copy. When more than one DOS session is running one of these programs, a SYS1799 error can result. This occurs because the programs that use these security keys do not de-allocate the parallel port if a second session is started for a program that also requires the security key. This error is the result of a direct I/O parallel port contention mechanism that protects the user from possible data corruption. To disable this mechanism: 1. Display the pop-up menu for the printer object by moving the mouse pointer to it and clicking mouse button 2. 2. Click on OPEN; then SETTINGS. 3. Click on the Output tab. 4. Double-click on the LPT port that has the contention problem. 5. Select Shared access to share the port between DOS sessions doing direct I/O to the parallel port. 6. Click on OK. o Some Windows Multimedia Extension programs might not work correctly after being migrated to OS/2 2.0. If this occurs, reinstall them under WIN-OS/2. o If the SYS0005 error "ACCESS DENIED" occurs when starting DOS programs, follow this procedure: 1. Shut down the system. Chapter 5. Application Programs 5-3 2. Insert the Installation Diskette into drive A. _____________________ 3. Restart the system. 4. When prompted, remove the Installation Diskette, insert Diskette 1, _____________________ __________ and press Enter. 5. At the "Welcome to OS/2" screen, press Esc. 6. Remove Diskette 1 and insert Diskette 2. __________ __________ 7. At the command prompt, type "CHKDSK C: /F:3 " and press Enter. 8. If you receive the error "cross-linked extended attribute", repeat the previous command until CHKDSK reports no errors. 9. After repeated attempts, if CHKDSK continues to report errors, note the names of the files related to the errors. Copy these files to a blank diskette and delete the files from the hard disk. Then, run CHKDSK again. 10. When CHKDSK reports no errors, copy the files back to their original location, and restart your system. NOTE: This problem usually occurs when an EADATA file is deleted from DOS. If you have DOS, copy files to another directory or name; delete the originals, and then copy back to the original location. SPECIFIC PROGRAM COMPATIBILITY ______________________________ 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. ACTION! SAMPLER 1.0 (WINDOWS) o The DPMI_MEMORY_LIMIT WIN-OS/2 setting must be set to 5 or greater. ADOBE TYPE MANAGER (WINDOWS) o When using an IBM 4029 printer in PPDS mode with Adobe** Type Manager**, some Windows programs might not function correctly. If this occurs, do not use the printer's resident fonts. To disable the printer's 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. AFTER DARK (WINDOWS) o To run this program in a WIN-OS/2 window session, change the object's settings to Hide or minimize the program object to the desktop. 5-4 Tips and Techniques o This program places a TSR (terminate and stay-resident) reference in the AUTOEXEC.BAT file when it is installed. To run in a WIN-OS/2 window session, remove this reference from AUTOEXEC.BAT. Chapter 5. Application Programs 5-5 ALDUS PAGEMAKER 4.0 (WINDOWS) o The spelling checker cannot locate the dictionary. o Deselect the Public setting to use the clipboard. o 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. ALDUS PERSUASION 2.0 (WINDOWS) o Use the parallel ports to print. o Deselect the Public setting to use the clipboard. ARTS & LETTERS GRAPHICS EDITOR 3.1 (WINDOWS) o The DECIPHS utility program requires that a DOS session be started from the Windows environment; this is not supported. o To run in a WIN-OS/2 window, change the object's settings to minimize to the desktop. o The directory created by Arts & Letters is named A&L. The ampersand 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. (caret, shift 6): CD A&caret.&L The second method is to surround the entire directory name with quotation marks (" "): CD "A&L" o 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 opened on system startup and start the program from its icon when you intend to run it in a window. AUTOCAD VERSION 10 (DOS) o Close the program from the desktop. Use an HPFS partition as a workaround. A fix is forthcoming from IBM. AUTOCAD (OS/2) 5-6 Tips and Techniques o Some of the background colors are set to a very pale color that does not show up well on XGA displays. AUTOMANAGER 4.0 (DOS) o The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the real-mode version. o 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:\. BORLAND C++** 2.0 AND 3.0 (DOS) o Set the DPMI_DOS_API DOS setting to Enabled. BORLAND TURBO C++ 2.0 (DOS) o The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard-mode version of the program. BORLAND TURBO DEBUGGER 2.01 (DOS) o The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard-mode version of the program. o TD386, the 386 version of Turbo Debugger, manipulates the 80386 control registers; this is not supported. BORLAND TURBO DEBUGGER FOR WINDOWS (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. o 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.) BORLAND TURBO PASCAL 6.0 (DOS) o The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard-mode version of the program. CENTRAL POINT BACKUP FOR DOS 7.1 (DOS) o Displays meaningless characters when running in a DOS window session. Run this program only in a DOS full-screen session. CENTRAL POINT PC TOOLS DELUXE 7.1 (WINDOWS) o Many of the utility programs require starting a DOS session from the Windows environment; this is not supported. Start these programs from a separate DOS session. o 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 do not work correctly with OS/2 2.0. If you experience Chapter 5. Application Programs 5-7 difficulty backing up on a diskette, back up on an alternate device, such as a network drive or a tape drive. TIP: You might need to install this program under a specific DOS session. COMMANDER KEEN (DOS) o Set the VIDEO_RETRACE_EMULATION DOS setting to OFF. COMMUTE (WINDOWS) o When this program is installed under WIN-OS/2, the statement keyboard.drv=commkbd.drv is added to the SYSTEM.INI file. Change this statement to keyboard.drv=keyboard.drv. CONTROL ROOM 1.0 (DOS) o You must run this program in a DOS full-screen session for the screen blanking feature to work correctly. CORELDRAW 2.0 (OS/2) o If you do a large amount of printing while in this program, it is possible that you might run out of system (memory) resources. To avoid this, you should periodically save your work and exit CorelDRAW; then restart the program and continue your work. CORELDRAW 2.0 (WINDOWS) o Install the program in a DOS session. o Run the program in a WIN-OS/2 full-screen session. CORELDRAW 2.1 (WINDOWS) o To install this program: - Start a DOS session. - Run FFIX /date (note that "date" must be lowercase). - Type A: and press Enter. - Exit WIN-OS/2. - Run FFIX /u. - Type INSTALL and press Enter. o Run the program in a WIN-OS/2 full-screen session. CROSSTALK (WINDOWS) o Type MODE COMx BUFFER=OFF at the command prompt, where x is the _ _ communications port you are using, before you run the program. DBASE IV 1.1 (DOS) o If you receive a "too many files open" error message, set the DOS_FILES DOS setting to 30. Set the DOS_VERSION DOS setting to 5-8 Tips and Techniques DBASE.EXE,5,0,255. With Hyperdisk, set DOS_VERSION to DBASE1.EXE,5,0,255. o When using Hyperdisk, you might have to adjust the EMS and XMS memory limits. o With the multi-user version, the program must be run in a specific DOS session. DESIGNER (OS/2) o The MIRRORS.DLL that comes with this program must be installed in the program directory, not in 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. DRAFIX CAD VERSION 1.11 (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. DRAFIX CAD VERSION 3.0 (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. DYNACOMM** ASYNCHRONOUS OS/2 (OS/2) o 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. Chapter 5. Application Programs 5-9 ENHANCED EDITOR (OS/2) o The OS/2 Enhanced Editor supports up to 99 fonts. If additional fonts are installed, unpredictable results might occur. o In the online help for the Enhanced Editor, it states that you should contact your IBM representative for detailed information on how to program the editor. Instead, obtain this information from the IBM bulletin boards. F-117A STEALTH FIGHTER 2.0 (DOS) o Set the VIDEO_RETRACE_EMULATION DOS setting to OFF. o 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. F19 (DOS) o Set the HW_ROM_TO_RAM DOS setting to ON and the VIDEO_RETRACE_EMULATION DOS setting to OFF. FASTBACK FOR WINDOWS (WINDOWS AND OS/2) o Use only Version 1.01, a no-charge upgrade from Fifth Generation Systems. To order, call 1-800-873-4384. o In the Options pull-down menu in the program, make sure that the Media setting is set to the system default. (The other Media settings write to DMA device drivers, which have incompatibility problems.) FASTBACK PLUS 2.1 AND 3.04 (DOS) o If you experience difficulty backing up on a diskette, back up on an alternate device, such as a network drive or a tape drive. FASTLYNX 1.1 (DOS) o To use the serial port with this program, remove the DEVICE=C:\OS2\MDOS\VCOM.SYS statement from CONFIG.SYS. The parallel port works correctly. o Due to its high speed, the program sometimes fails to function. If this occurs, simply end the program; system integrity is not compromised. To minimize the possibility of this error condition, set the following DOS settings: HW_TIMER = ON IDLE_SENSITIVITY = 100 IDLE_SECONDS = 10 FORM PUBLISHER (WINDOWS) o Ensure that the program's printer driver is installed before running the program. FORMBASE 1.2 (WINDOWS) 5-10 Tips and Techniques o The SHARE statement is automatically added to AUTOEXEC.BAT during program installation. Use an editor to remove the SHARE command from AUTOEXEC.BAT. o When running this program and Lotus 1-2-3 in the same WIN-OS/2 session, this program must be started first. FOTOMAN (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. FRAMEWORK III** 1.1 (DOS) o The program expects COMMAND.COM to be in the root directory of C:\. Copy COMMAND.COM from the C:\OS2\MDOS directory to C:\. o Disable the program's print spooler; using it might cause an error. HARVARD DRAW (WINDOWS) o 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. HARVARD GRAPHICS (WINDOWS) o When installing this program under WIN-OS/2, you will receive an error dialog box. Select OK in the dialog box and the installation will complete successfully. o When running this program in a WIN-OS/2 window session, the Color Selection windows are missing the Color Selection grid. Run this program in a WIN-OS/2 full-screen session. HDC FILEAPPS 1.0 (WINDOWS) o The program uses the Windows Notepad for a README text file during installation. Indicate that you do not wish to read the file and installation will continue. HP NEW WAVE 3.0 (WINDOWS) o Install the program under DOS. If you experience problems with program or session termination, set UseOS2shield=0 in the SYSTEM.INI file (in the OS2\MDOS\WINOS2 directory on your startup drive). If that does not help, run the program in a WIN-OS/2 full-screen session. IBM 3363 OPTICAL DISK DRIVE o The software for this product must be run in a specific DOS session that is started from drive A. o You should run only a small number of other processes when using this product. IBM PC LAN SUPPORT PROGRAM (DOS) Chapter 5. Application Programs 5-11 o If you close the DOS session that is running this program, you must first reset the token-ring adapter before you restart this session. To fix this problem, download RSTTOK.ZIP from the IBM BBS or from IBMFILES in CompuServe. IBM PC/3270 VERSION 2.0 (DOS) o First, the program must be migrated using the OS/2 MIGRATE utility program. o Then, in the Session Page of the DOS settings: - Select DOS FULL SCREEN or DOS WINDOW. - Set the VIDEO_MODE_RESTRICTION DOS setting to CGA. - Add "D:[path]DXMA0MOD.SYS" and "D:[path]DXMC0MOD.SYS" to the DOS_DEVICE DOS setting. o Then, in the Program Page of the DOS settings: - Set the Path and File Name to *. - Set the Parameters to /K d:[path]PC3270.BAT. - Set the Working directory to d:[path]. IBM PC/3270 V2.0 (WINDOWS) o First, the program must be migrated using the OS/2 Migration utility program. o Then, in the Session Page of the WIN-OS/2 settings: - Add " /C PC3270WO.BAT" to the DOS_SHELL WIN-OS/2 setting. - Add "D:[path]DXMA0MOD.SYS", "D:[path]DXMC0MOD.SYS", and "D:[path]PCS802.SYS V=N" to the DOS_DEVICE WIN-OS/2 setting. - Set the "DOS_SHELL" setting to /C PC32700WO.BAT. - Set the "WIN-OS/2 window Separate session" or "WIN-OS/2 full screen" setting to ON (click on the check box until a check mark appears). o Then, in the Program Page of the WIN-OS/2 settings: - Set the Path and File Name to d:[path]PC3270.EXE. - Set the Working directory to d:[path]. INTEL SATISFAXTION (DOS) o The program must be run in a specific DOS session. o After installing Intel SatisFAXtion, you are told to remove the diskette and press any key to reboot your computer. Instead, shut down the operating system and restart your computer. o 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. 5-12 Tips and Techniques 6. Edit CONFIG.SYS and cut the last two lines relating to the Intel SatisFAXtion board to the clipboard (cut only the last line if you do not have a scanner installed). 7. Save the file using Plain Text as the file type. 8. In the Command Prompts folder, select a DOS Full Screen icon, press the Ctrl key and mouse button 2 at the same time, move the mouse pointer to an empty area in the folder, and release the mouse button and the Ctrl key. This creates a copy of DOS Full Screen. 9. Put the mouse pointer over your new icon and click on mouse button 2. 10. Click on the arrow next to OPEN, and select SETTINGS. 11. Go to the Session page and select the DOS SETTINGS push button. 12. Go to DOS_DEVICE and click on mouse button 1. Then, move the mouse to the dialog area and click on mouse button 1 (there should be a blinking cursor now). 13. Paste the text that you cut from the CONFIG.SYS file and select SAVE. 14. Go to the General page and replace the contents of the Title box with FAX (or whatever other title you choose). 15. If you want to edit the new session's object, 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 Startup 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. o If you install the program using this procedure and you receive error messages, install the program under DOS. KING'S QUEST (DOS) o Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or from the DOS_DEVICE DOS setting. LAN SUPPORT PROGRAM DEVICE DRIVERS (DOS) o 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. o The IBM token-ring adapter should be used by only one session at a time. Chapter 5. Application Programs 5-13 LANTASTIC 4.0 (DOS) o You might experience problems with this version of LANtastic. Use Version 4.1 instead. For more information, contact the ARTISOFT BBS at 602-293-0065. LANTASTIC 4.1 (DOS) o Run this program in a specific DOS session. Set DOS_STARTUP_DRIVE DOS setting to the location of a DOS kernel to boot from. o If you are using Artisoft AE-2 or AE-3 adapters, set your adapters to 8-bit mode, as described in the adapter documentation. LAPLINK PRO (DOS) o Type MODE COMx IDSR=OFF ODSR=OFF ORTS=OFF at the command prompt, _ where x is the communications port you are using, before you run the _ program. LAPLINK III 3.0 (DOS) o It is preferable that you use the parallel port. To use the serial port with this program, comment out the VCOM.SYS statement from CONFIG.SYS (by typing 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. LOTUS 1-2-3 FOR WINDOWS 1.0 AND LOTUS 1-2-3 RELEASE 3.1 (DOS) o Set the DPMI_MEMORY_LIMIT DOS setting to a minimum of 3MB. o 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 Version 3.0). o If you plan to use this program, follow these steps: 1. Create a batch file called LOTUS.BAT which contains: @ECHO OFF CLS PROMPT $p$g PATH=X:\LOTUS SET 123MEMSIZE=2048 ... (any other lines) 123.EXE (last line in file) 2. Open the Templates folder from the desktop. Select the program object by clicking on it with the left mouse button. Drag a program template to the desktop using the right mouse button. 3. Click on the program template on the desktop with the right mouse button to reveal the Object menu. Select OPEN SETTINGS. A notebook display will be opened. 4. In the PROGRAM AND FILENAME field, enter: x:\path\lotus.bat 5-14 Tips and Techniques 5. Select the SESSION Tab and click on the DOS FULL SCREEN radio button. Select the DOS SETTINGS push button. 6. Select or add the following DOS Settings: DOS_UMB ON DOS_HIGH ON DOS_VERSION INSTALL.EXE,3,40,255 123.EXE,3,40,255 LOTUS.EXE,3,40,255 123DOS.EXE,3,40,255 ZAP.EXE,3,40,255 INS.EXE,3,40,255 DPMI_MEMORY_LIMIT 4 OR HIGHER 7. Select the GENERAL tab, and add: Title -> Lotus 123 (or whatever you choose) Close the notebook by selecting CLOSE or double-clicking on the system menu. 8. Start the DOS session by double-clicking on the DOS full-screen object. 9. From the A: prompt, type INSTALL to install the product. 10. Start the LOTUS specific DOS session by double-clicking on the LOTUS program object. LOTUS FREELANCE GRAPHICS FOR OS/2 (OS/2) o If you experience installation problems, contact the Lotus Development Corporation. Lotus will provide a fix. You can also download FLGOS2.ZIP from the IBM BBS or from IBMFILES in CompuServe, or download INSTAL.ZIP from the LOTUS section of CompuServe. o 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. LOTUS FREELANCE GRAPHICS FOR WINDOWS (WINDOWS) o The pointer to printer objects points to Screen Show instead of to the printer. LOTUS MAGELLAN** 2.0 (DOS) o The UNDELETE function in the program uses physical-sector addressing, which is not supported. Use the OS/2 UNDELETE command. LOTUS NOTES (OS/2) Chapter 5. Application Programs 5-15 o To use Notes 2.x, you must delete the file QNC.EXE from the Notes _ program directory. This file is used only for debug support in the field. Therefore, its removal will not affect program execution. MAGICORP (WINDOWS) o 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. MATHCAD 3.0 (WINDOWS) o 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. MATHCAD 3.1 (WINDOWS) o Set the DPMI_MEMORY_LIMIT DOS setting to 64 or greater. o Set the XMS_MEMORY_LIMIT DOS setting to 0. o Set the EMS_MEMORY_LIMIT DOS setting to 0. 5-16 Tips and Techniques MICROPROSE CIVILIZATION (DOS) o Set the VIDEO_RETRACE_EMUL setting to OFF and the HW_TIMER setting to ON. MORE WINDOWS (WINDOWS) o If you use the Full-Page Paper White mode or Full-Screen Color mode, the screen might be disrupted. Avoid using these modes. MS BOOKSHELF - CD-ROM REFERENCE LIBRARY (DOS/MULTIMEDIA) o The program requires version 6.14 of the mouse device driver, MOUSE.COM, which comes with the product. o Use the INT_DURING_IO setting to avoid video and audio problems. o The program will not install if the PATH statement in the AUTOEXEC.BAT file exceeds 254 characters. If this problem exists, do the following: 1. Make a backup copy of AUTOEXEC.BAT. 2. Edit the AUTOEXEC.BAT and add the directory to install the program. For example, if you want to install the program in your D drive, add D:\VIEWER to the PATH statement. 3. Save the file; then start a WIN-OS/2 session to install the program. MS CHART 3.0 (DOS) o Install the program's mouse driver, and set MOUSE_EXCLUSIVE_ACCESS to ON. MS CODEVIEW (DOS/OS/2) o When using the protect-mode version, CVP 2.2 (for OS/2), trace through the source code, rather than through the assembler language. o In order for the program to work correctly, delete the PWBHLP.PXT help file. Chapter 5. Application Programs 5-17 MS CODEVIEW FOR WINDOWS VERSION 3.0 (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. MS EXCEL FOR DOS 2.1 (DOS) o Set the XMS_MEMORY_LIMIT DOS setting to 0. MS EXCEL FOR OS/2 3.0 (OS/2) o The Help index and the Keyboard Help windows operate incorrectly. Avoid using these functions. MS EXCEL FOR WINDOWS 3.0 (WINDOWS) o Deselect the Public setting to use the clipboard. o When using dynamic data exchange (DDE), run it in the same WIN-OS/2 session as the Windows program it is communicating with. MS MONEY 1.0 (WINDOWS) o Calls the Windows Calculator accessory program. Use the OS/2 Calculator mini-application program in the Productivity folder. MS MSCDEX (DOS) o Run the program in a specific DOS session. MS PROJECT FOR WINDOWS 1.0 (WINDOWS) o Must be installed in a DOS session. MS QUICKC (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. MS WINDOWS 3.0 (DOS) o It is preferable that you run Windows programs under WIN-OS/2, which supports both standard and real mode Windows programs. However, if you choose to run this program, run it in real mode only. MS WORD (OS/2) o You might have problems selecting items from the application menu, and the application appears to freeze. Call the Microsoft** support number for their fix. 5-18 Tips and Techniques MIRRORS III o Type MODE COMx BUFFER=OFF at the command prompt, where x is the _ _ communications port you are using, before you run the program. NATIONAL GEOGRAPHICS MAMMALS (DOS) o Run the program with the DOS Setting INT_DURING_IO set to On. NATIONAL GEOGRAPHIC PRESIDENTS (DOS) o Run the program with the DOS Setting INT_DURING_IO set to On. NORTON BACKUP 1.2 (DOS) o You might experience diminished performance when backing up to diskette. NORTON DESKTOP (WINDOWS) o 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 startup drive). o 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. o Run the program in a WIN-OS/2 full-screen session. NORTON UTILITIES 5.0 (DOS) o The UNDELETE functions require physical sector addressing, which is not supported. Use the OS/2 UNDELETE command. o 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. PAINTSHOW PLUS 2.21 (DOS) o Load the version of MOUSE.COM that comes with the program before starting the program. Chapter 5. Application Programs 5-19 PARADOX 3.5 (DOS) o The version of the program that uses extended memory uses an unsupported DOS memory extender. Use the standard version of the program. PEACHTREE COMPLETE III 5.0 (DOS) o Set the DOS_FILES DOS setting to 60. o 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. PERFORM PRO 1.0 (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. PFS FIRST CHOICE** (DOS) o When the program is run in a DOS window, the mouse pointer does not reflect tool selection. o Set the baud rate to 2400 or lower when using the communication feature. PFS WINDOWWORKS 1.75 (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. PHOTOSTYLER (WINDOWS) o Run the program in a WIN-OS/2 full-screen session. PM TERMINAL PROGRAM o Make sure that the asynchronous communications driver, SASYNCDB.SYS, is not commented out on a REM statement in the CONFIG.SYS file. PUBLISHERS POWERPAK 2.1 (WINDOWS) o Create the directory C:\OS2\MDOS\WINOS2\POWERPAK before running the installation batch file. QUATTRO PRO 3.0 (DOS) o Install printers from within the program, rather than during program installation. QUICKEN (DOS) o Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or from the DOS_HIGH setting. QUICKEN FOR WINDOWS** (WINDOWS) 5-20 Tips and Techniques o The program calls the Windows Calculator accessory program. Use the Calculator mini-application program in the Productivity folder. RISK (DOS) o Do not use the program's shutdown function. SANTAFE MEDIA MANAGER (DOS) o To install this program: - Start a DOS session. - Run FFIX /find (note that "find" must be lowercase). - Install the program. - Run FFIX /u. SIDEKICK (OS/2) o A printer must be installed and present on the desktop to use the Notepad. SIGNMASTER 5.11 (DOS) o The plot/preview feature causes an illegal instruction to be issued. SOFT TERM (OS/2) o 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. SOUNDBLASTER (DOS) o 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. o The PARROT program does not run in a DOS session. SPACE QUEST IV (DOS) o Set DOS_BACKGROUND_EXECUTION to OFF so that the program is suspended when it is placed in the background. o Set up the program so that it does not use extra memory. o For best performance, run this program in a DOS full-screen session. o For computers with a SoundBlaster card, change to the drive and directory which contains Space Quest IV and enter SQ4FIX on the command line. SQLWINDOWS 3.0 (WINDOWS) Chapter 5. Application Programs 5-21 o The program accesses drive A at intermittent intervals. Keeping an empty diskette in drive A will save you from having to respond to "The A: device is not ready" error windows. STACKER 2.0 (DOS) o This program does not run under OS/2 2.0. Stac Electronics has announced an OS/2 2.0 compatible version of Stacker that will be released later in 1992. Contact Stac Electronics for more information. THE WAY YOU WORK (DOS/WINDOWS) o Install this program under DOS. Once installed, the program can run in a DOS or WIN-OS/2 session. WINDOWS MULTIMEDIA EXTENSIONS (WINDOWS) o If you are running this program and another program that uses the audio adapter at the same time, unpredictable results might occur. o The OS/2 Multimedia Presentation Manager avoids this problem. WINFAX PRO** (WINDOWS) o Run this program only in a WIN-OS/2 full-screen session. o If you are using Dynamic Data Exchange (DDE), avoid switching 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. WING COMMANDER II (DOS) o Set HW_TIMER to ON. o If you are running on a slower computer, turn the sound option off. WORDPERFECT FOR WINDOWS (WINDOWS) o Change to the directory that contains WPWINFIL.EXE and run: FIXWP WPWINFIL.EXE. (To enable WordPerfect for Windows to run under DOS and Windows Version 3.0 again, run UNFIXWP in a similar manner.) WORDPERFECT OFFICE 3.0 (DOS) o Install the keyboard-enhancement utility program manually, after program installation, by adding it to the CONFIG.SYS file. XTREE PRO GOLD 2.0 (DOS) o The Zip Manager feature cannot find the zip file it is to act upon. Avoid using this feature. 5-22 Tips and Techniques CHAPTER 6. WIN-OS/2 APPLICATION PROGRAMS _________________________________________ This chapter contains information when running a Windows application program in a WIN-OS/2 session (window and full-screen). OPTIMIZING WIN-OS/2 ___________________ The following are tips for using your computer more efficiently in WIN-OS/2 sessions: o Current information for WIN-OS/2 window sessions in high-resolution video modes is available from CompuServe, the IBM National Support Center Bulletin Board System, the OS/2 Bulletin Board System, and IBMLINK*. o If you are running Windows programs in WIN-OS/2 window sessions, you cannot have any statement in the AUTOEXEC.BAT file that prompts the user for input (for example, "Press any key to continue"). o Do not use the SETUP.EXE file shipped with Windows Version 3.0. Instead, use the SETUP.EXE file shipped with WIN-OS/2 to ensure your environment is properly configured for OS/2 2.0. Use the Selective Install program in OS/2 2.0 to change video device drivers for VGA, 8514, XGA, EGA, and CGA, and for mouse device drivers. To start Selective Install, select the icon for OS/2 SYSTEM, then SYSTEM SETUP, then SELECTIVE INSTALL. o To decompress Windows device drivers supplied by equipment manufacturers, use the EXPAND.EXE utility program for WIN-OS/2 located on OS/2 2.0 Diskette 9. __________ o Windows Version 3.1 is not compatible with OS/2 2.0, so you cannot run it in a WIN-OS/2 session. However, you can run Windows Version 3.1 in a separate partition. Install Boot Manager, and partition your hard disk so that Windows Version 3.1 is in a partition separate from OS/2 2.0. Or, if you have DOS and Windows Version 3.1 already installed before you begin OS/2 2.0 installation, consider installing OS/2 2.0 Dual Boot. With Dual Boot, you can shut down OS/2 2.0 and start up DOS/Windows to run programs that require Windows Version 3.1. o If a Windows program does not work correctly in a WIN-OS/2 session, it is likely that the program files were not all migrated properly. To fix the problem, you can reinstall the program using a WIN-OS/2 full-screen session. (Select RUN on the File menu of the Program Manager and use the command line there.) Or, if you know the specific files that are needed, you can copy them from the \WINDOWS directory to the \OS2\MDOS\WINOS2 directory. o If you are running a WIN-OS/2 full-screen session and you have an 8514 display, use DOS Settings to set VIDEO_8514A_XGA_IOTRAP to OFF and VIDEO_SWITCH_NOTIFICATION to ON. (C) Copyright IBM Corp. 1992 6-1 o If the VIDEO_SWITCH_NOTIFICATION setting is On, wait until you see your WIN-OS/2 desktop in a full-screen session before switching back to the OS/2 desktop. If the session does not start successfully, close it, and then restart it. o The value for VIDEO_SWITCH_NOTIFICATION should not be changed for an active WIN-OS/2 session. o You cannot use the WIN-OS/2 Control Panel to change mouse buttons in WIN-OS/2 window sessions. Change mouse button settings from the OS/2 desktop to affect the WIN-OS/2 mouse buttons in the WIN-OS/2 window environment. The WIN-OS/2 Control Panel can still be used for changing mouse buttons in WIN-OS/2 full-screen sessions. o If you install the US English version of OS/2 2.0, and you want to change the system configuration to another country or language, run Selective Install to make the changes effective for OS/2. To make the changes effective for WIN-OS/2, start WIN-OS/2 in a full-screen session, open the Control Panel, and use the INTERNATIONAL choice to make your changes. o If you start a program in a WIN-OS/2 session and receive the message "FATAL ERROR 0X0401", ensure that all device statements are correct in OS2\MDOS\WINOS2\SYSTEM.INI. o If you are running a WIN-OS/2 full-screen session with an XGA video device driver and your WIN-OS/2 icons are not clear, use the Control Panel to choose another color scheme for the WIN-OS/2 desktop. o To improve performance, it is preferable to have only one server or client in a WIN-OS/2 session. o If you have an XGA or 8514 display, keep the DDE server as an icon instead of opening it. Also, set the DOS setting VIDEO_SWITCH_NOTIFICATION to On. USING CLIPBOARD AND DYNAMIC DATA EXCHANGE _________________________________________ o If you use the Clipboard Viewer to display data, cut, copy, or paste from a DOS, OS/2, or WIN-OS/2 program, ensure that the Clipboard Viewer is running before marking the text; otherwise, the copy might not be successful. o The availability of Clipboard and Dynamic Data Exchange (DDE) functions can vary, depending upon the types of sessions you are running. - In standard-mode full-screen WIN-OS/2 sessions, Clipboard and DDE default to Public. - In real-mode full-screen WIN-OS/2 sessions, the default is Private. - In WIN-OS/2 window sessions, Clipboard and DDE can only be Public. o To disable Clipboard and DDE in an OS/2 session, do the following: 6-2 Tips and Techniques 1. Create a WIN-OS/2 window or full-screen session, so that Clipboard and Data Update are started. (Clipboard and Data Update are automatically started when you start a WIN-OS/2 session.) 2. On the OS/2 desktop, display the Window List. 3. Select CLIPBOARD and DATA UPDATE. 4. Display a pop-up menu by clicking mouse button 2 on CLIPBOARD or DATA UPDATE. 5. Select CLOSE. o To share data between WIN-OS/2 sessions only, close Data Update and Clipboard in the OS/2 sessions. o In a WIN-OS/2 window session, the Clipboard and DDE icons are not available. You do not have access to the clipboard features. However, if you want to use a private clipboard in WIN-OS/2 window sessions, you can remove !CLIPWOS2 from the SYSTEM.INI file (in the OS2\MDOS\WINOS2 directory). The statements involved are those that begin with: SAVDMApps= MAVDMApps= WOS2VDMapps= All three occurrences of !CLIPWOS2 must be removed. It is advisable to back up the SYSTEM.INI file before making the changes, so that you can easily restore the original SYSTEM.INI if you decide to do so in the future. WARNING: IF THE SYSTEM.INI FILE IS CHANGED INCORRECTLY, YOU MIGHT NOT BE ABLE TO USE WIN-OS/2. IF YOU ARE NOT FAMILIAR WITH WINDOWS .INI FILES, YOU MIGHT WANT TO ARRANGE FOR A PERSON WHO HAS WINDOWS TECHNICAL EXPERTISE TO MAKE ANY CHANGES IN THE SYSTEM.INI FILE. o To disable Clipboard and DDE in a full-screen WIN-OS/2 session, do the following: 1. Start WIN-OS/2. 2. Click mouse button 1 on the Clipboard icon to display the window menu. 3. Select CLOSE. 4. Respond to the confirmation message. 5. Repeat the previous steps to close the DDE Interchange Agent. o If you experience slow performance when using a Windows program to copy data to the clipboard, consider the following information on improving performance. The clipboard uses delayed rendering, which means only the format name is given to the clipboard. The actual data is rendered only when the PASTE menu choice is selected. Many Windows programs use this scheme when they copy data to the clipboard. However, to share data between WIN-OS/2 and OS/2 sessions, the WIN-OS/2 clipboard receives all data from the program that copied the data to the clipboard, and then sends the data to other Chapter 6. WIN-OS/2 Application Programs 6-3 sessions. This process is time-consuming. You can decide whether or not you want to share data between WIN-OS/2 sessions. If you do not want to share data, open the Clipboard icon in a WIN-OS/2 full-screen session and turn off the PUBLIC CLIPBOARD choice on the OPTIONS menu bar choice; however, if you want to share some of the data between sessions, use the FILE EXPORT and IMPORT menu bar choices. o If you are unable to paste data from the OS/2 clipboard to a WIN-OS/2 session, you need to open the WIN-OS/2 session before you copy data from the OS/2 clipboard. The WIN-OS/2 session starts the OS/2 clipboard, which will send the data to the WIN-OS/2 clipboard. This problem will be fixed in a future release. o If you cannot paste a bit map from the OS/2 clipboard to a WIN-OS/2 session, the bit map might be too large, or the program might not understand the device-independent bit map (DIB) format of the file. For example, icons created using the Icon Editor are not understood by some Windows programs, such as Microsoft Paintbrush. If your WIN-OS/2 session is started first, you can view the bit map in the OS/2 clipboard; however, you cannot paste it. The PASTE menu choice is grayed (unavailable). o If you are running several programs concurrently (each doing Copy and Paste), you might receive from the clipboard pasted data that was supposed to go into another program. Suppose you copy data to the clipboard using Program 1, but do not paste it into its destination right away. While Program 1 is doing other work, you copy data from Program 2 to the clipboard, and you do not paste that data either. Later, you attempt to paste the Program 1 data from the clipboard. However, the only data that is pasted is from Program 2, not Program 1. This happens because the clipboard can hold data from only one cut or copy at a time. In this example, the copied data from Program 2 replaced the data from Program 1. To avoid having this problem, always paste the cut or copied data into its destination program before you cut or copy data from another program to the clipboard. o Vertical scrolling in the OS/2 clipboard does not work. It will be fixed in a future release. In the meantime, you can use Page Down and Page Up. o When a program copies several sources of data to a public clipboard in different formats, and if one of the sources creates a rendering problem, no data is sent to other WIN-OS/2 sessions. In a future release, only the problem data will not be sent to the public clipboard. o When a metafile is copied to the OS/2 clipboard, it is converted into a bit map, and then the image is enlarged. Only the center of the image is in the clipboard viewer. This will be fixed in future release. o Metafiles in WIN-OS/2 and OS/2 are not compatible. If you copy a WIN-OS/2 metafile without bit map information to a public clipboard, it 6-4 Tips and Techniques is converted to a device-independent bit map (DIB) so that it can be exchanged with an OS/2 session. o If you want to use dynamic data exchange (DDE) using the PASTE LINK choice on the File menu of a program, consider the following information. The clipboard should be set to Public. The client and server must negotiate the data format to initiate the DDE link. If this negotiation fails, some applications do not display any error message and no further action is taken. If this happens, try another menu choice (for example, LINK), if available. Chapter 6. WIN-OS/2 Application Programs 6-5 6-6 Tips and Techniques CHAPTER 7. PRINTING CONSIDERATIONS ___________________________________ This chapter describes how to configure your printer hardware. It also provides help when diagnosing printing problems. CONFIGURING YOUR COMPUTER FOR PRINTING ______________________________________ On most Industry Standard Architecture (ISA) -- IBM refers to this architecture as AT bus -- parallel ports are configured using either dual-inline package (DIP) switches or jumpers. Most of the systems and adapters purchased have literature that explains the interrupt request (IRQ) level and port setting for each port. The following tables show standard parallel-port address and IRQ settings: +------------------+------------------+------------------+------------------+ | | AT BUS (ISA) | EISA* | MICRO CHANNEL | +------------------+------------------+------------------+------------------+ | LPT1 | 3BC/IRQ7 | 3BC/IRQ5 or IRQ7 | 3BC/IRQ7 | +------------------+------------------+------------------+------------------+ | LPT2 | 278/IRQ5 | 378/IRQ5 or IRQ7 | 378/IRQ7 | +------------------+------------------+------------------+------------------+ | OR | | | +------------------+------------------+------------------+------------------+ | LPT1 | 378/IRQ7 | 378/IRQ5 or IRQ7 | 378/IRQ7 | +------------------+------------------+------------------+------------------+ | LPT2 | 278/IRQ5 | 278/IRQ5 or IRQ7 | 278/IRQ7 | +------------------+------------------+------------------+------------------+ +------------------+------------------+------------------+------------------+ | | AT BUS (ISA) | EISA* | MICRO CHANNEL | +------------------+------------------+------------------+------------------+ | LPT1 | 3BC/IRQ7 | 3BC/IRQ5 or IRQ7 | 3BC/IRQ7 | +------------------+------------------+------------------+------------------+ | LPT2 | 378/IRQ7 | 378/IRQ5 or IRQ7 | 378/IRQ7 | +------------------+------------------+------------------+------------------+ | LPT3 | 278/IRQ5 | 278/IRQ5 or IRQ7 | 278/IRQ7 | +------------------+------------------+------------------+------------------+ * Using IRQ5 or IRQ7 depends on the hardware interrupt level your Extended Industry Standard Architecture (EISA) parallel port supports. Dip switches and jumpers reside on the system board or adapter in your computer. To change their configuration, do the following: 1. Turn off your computer. 2. Remove the parallel-port adapter. 3. Configure the system board or adapter by adjusting the DIP switches or jumpers to set the parallel port to one of the industry standard (C) Copyright IBM Corp. 1992 7-1 combinations. Ensure that other adapters are not configured to use the same IRQ level. Sound, Musical Instrument Device Interface (MIDI), LAN, and serial adapters might be sharing these same hardware-interrupt levels and creating interference. For more information, refer to "Setting the Interrupt Request (IRQ) Level on an ISA System" on page 9-12 and "Interrupt Problems on an ISA System" on page 9-8. HARDWARE ADAPTERS AND IRQ CONFLICTS AT bus computers do not allow hardware-interrupt sharing; therefore, each adapter must be configured to a separate IRQ level to be able to work properly. Some adapters, such as SoundBlaster, are factory configured to IRQ7, or their accompanying instructions recommend that you configure them to IRQ7. This might be the same hardware-interrupt level as the first parallel port. If you intend to print, this conflict must be resolved. Refer to "Unable to Print" on page 7-7. You might be able to use IRQ10 with SoundBlaster because it does not conflict with parallel ports (IRQ7 or IRQ5) or IRQ5 if LPT2 is not being used. Refer to "Configuring Your Computer for Printing" on page 7-1 and "Setting the Interrupt Request (IRQ) Level on an ISA System" on page 9-12 for more information about possible parallel port and IRQ settings. Refer to the reference manual for your adapters to configure the IRQ levels for your parallel ports and other adapters in your system. PS/2 DIRECT-MEMORY-ACCESS PARALLEL PORTS If you have a Personal System/2(*) system that supports direct-memory-access (DMA) parallel ports, OS/2 2.0 can take advantage of it. The current systems with a DMA parallel port include PS/2 models 56, 57, 80-A21, 80-A31, 90, and 95. If you have one of these systems, ensure that the parallel-port arbitration level is set to SHARED7 (enabled). OS/2 2.0 will automatically take advantage of this feature; no additional OS/2 setup is required. If you are an OS/2 Version 1.3 customer with Corrective Service Diskette 5054 (or ________________________________ later) installed, and you have disabled the parallel-port arbitration level, you need to reenable it in order for OS/2 2.0 to take advantage of the feature. Use the Reference Diskette shipped with the computer to view the system configuration, and then set the parallel-port arbitration level to SHARED7. SELECTING PRINTER DRIVERS _________________________ The following section describes suggestions for using specific printers. 7-2 Tips and Techniques CANON BUBBLE-JET PRINTER The following can help you select a driver for a a Canon** Bubble-Jet** printer to use with OS/2 2.0: o The Bubble-Jet BJ10E can emulate an IBM Proprinter(*) x24E using the _ IBM42xx driver. __ o The Bubble-Jet BJC800 can emulate an Epson** LQ2550 using the OS/2 Epson driver. o The Bubble-Jet LBP8 III+ can emulate an Epson LQ2550 or Proprinter x24E _ using the appropriate driver. DESKJET, DESKJET+, DESKJET 500, AND DESKJET 500C PRINTERS If you want to use a Deskjet, DeskJet+, DeskJet 500, or DeskJet 500C printer, install the Epson driver and then select HP DESKJET 500. NOTE: The HP DeskJet 500C will not produce color output using the HP DeskJet 500 device support in the Epson printer driver. HP LASERJET PRINTER If you are going to install the OS/2 HP LaserJet printer driver over an existing driver, be sure to delete all the old .FNT files first. Then, delete the printer driver from the OS/2 Workplace Shell printer object, and respond YES when asked if the driver files should be deleted from the hard disk. HP PAINTJET AND PAINTJET XL PRINTERS These printers should use the Micrografx** Paintjet** printer driver (SMGXPJET.DRV) shipped with OS/2 2.0 on Printer Diskette 3. __________________ Some applications, such as Aldus PageMaker, have problems printing multiple bit maps using this printer driver. If this occurs after the driver is installed, open the printer object settings notebook; then select PRINTER-SPECIFIC FORMAT on the Queues page. HP PAINTJET PRINTER DRIVER FOR WIN-OS/2 If you are using a HP Paintjet printer driver for WIN-OS/2, you might receive the following error message when printing: SoftRIP Failure: insufficient memory in SMGXPJET.DRV --------------- (*) Trademark of the IBM Corporation. Chapter 7. Printing Considerations 7-3 An updated printer driver that fixes this problem will be available shortly on IBM bulletin boards and CompuServe. IBM 3812, 3852, 5152, 5182, 5201-1, AND 5216 PRINTERS Printer drivers were not shipped with OS/2 2.0 for IBM 3812, IBM 3852, IBM 5152, IBM 5182, IBM 5201-1, or IBM 5216 printers because they have been out of service for several years. However, you can use the printer drivers shipped with OS/2 Version 1.3. Download the printer drivers from CompuServe (located in Library 17), or use the IBM Electronic Device Driver Distribution system. (Refer to the order card in the OS/2 2.0 package.) NOTE: The IBM 3812 printer can use the IBM 5152 printer driver by selecting 5152 compatibility mode in the 3812 printer. (For more information, refer to the documentation that came with your printer.) IBM 4019 AND IBM 4029 PRINTERS For the IBM 4019 and 4029 printers, the beta version of the Automatic Emulation Switching (AES) utility is available from the Lexmark International bulletin board service (BBS). The file is located in the Utilities directory and is called 40X9SU32.EXE. (For more information on the bulletin board, refer to "Accessing Lexmark International Bulletin Board Service" on page 7-6.) If you have any problems accessing the Lexmark BBS, call Lexmark at 1-800-537-2540. IBM 4072 EXECJET PRINTER If you have an IBM 4072 Execjet* printer, you might want to obtain the new beta version of the OS/2 IBM 42xx printer driver. The printer driver is __ available on the Lexmark bulletin board. The file is located in the Inkjet directory and is called OS24072.EXE. (For more information on the bulletin board, refer to "Accessing Lexmark International Bulletin Board Service" on page 7-6.) NOTE: Problems associated with this beta driver should be reported to Lexmark International through their bulletin board service. NEC P3200 PRINTER If you want to use a NEC** P3200 printer, install the EPSON LQ-850 printer driver. NEC P6200 PRINTER If you want to use a NEC P6200 printer, install the EPSON LQ-2550 printer driver 7-4 Tips and Techniques STAR NX-1000 PRINTER If you want to use a Star NX-1000 printer, install the EPSON LX-800 printer driver. NON-SUPPORTED PRINTER o If your printer is not supported by an OS/2 2.0 printer driver, determine if your printer supports a more common printer in emulation mode; then install the corresponding printer driver. o If your printer has a supported WIN-OS/2 printer driver, but no OS/2 printer driver, do the following: 1. Set up the WIN-OS/2 printer driver using the WIN-OS/2 Control Panel. 2. Set up the OS/2 print object using the IBMNULL printer driver. You should be able to print from a WIN-OS/2 session. Contact your printer manufacturer to obtain an OS/2 2.0 printer driver or to determine what other printers your printer emulates. Chapter 7. Printing Considerations 7-5 OS/2 1.3 PRINTER DRIVERS If you are using any of the following OS/2 1.3 printer drivers, you should obtain new versions from the IBM OS/2 BBS or CompuServ: IBM3852.DRV IBM4201.DRV IBM4202.DRV IBM4207.DRV IBM4208.DRV IBM5152.DRV IBM5182.DRV IBM52011.DRV IBM52012.DRV IBM5202.DRV IBM5216.DRV IBMNULL.DRV In addition, IBM will update OS/2 and Windows drivers on the bulletin board to provide the best possible printing support for our customers on an ongoing basis. ACCESSING LEXMARK INTERNATIONAL BULLETIN BOARD SERVICE ______________________________________________________ The phone number for the Lexmark bulletin board service is 1-800-453-9223. To access the BBS, select (N,8,1) for port settings, and use the XMODEM or ZMODEM protocols. Baud rates 1200 to 38 400 are supported. If you have any problems accessing the Lexmark BBS, call Lexmark at 1-800-537-2540. 7-6 Tips and Techniques DIAGNOSING PRINTING PROBLEMS ____________________________ This section describes the actions you can take to resolve some common printing problems. PRINTING IS SLOW If you have an AT bus computer and your parallel printer prints slowly under OS/2, DOS, and WIN-OS/2 sessions, your parallel-port address and hardware-interrupt levels are not configured correctly. You need to reconfigure your hardware. Refer to "Configuring Your Computer for Printing" on page 7-1. UNABLE TO PRINT If you encounter printing problems with parallel ports (for example, nothing prints), ensure that you have installed the appropriate printer driver for your model printer (see "Selecting Printer Drivers" on page 7-2). If the printer driver is correct, check the following: o Check that your parallel ports are configured properly. Refer to "Configuring Your Computer for Printing" on page 7-1 for configuration settings. o Verify that your printer cable meets parallel-port specifications. Some cables do not meet these specifications and can cause printing problems. (Cables that are longer than six feet in length are suspect. The six-foot cable-length problem is more evident on high-speed microprocessor systems.) Some cable manufacturers reduce the costs of their cables by not wiring all interface signals. This might not have been a problem under DOS, because DOS does not make use of all the signals within the parallel-port interface. However, some interface signals used to transmit data under OS/2 2.0 are not used when printing under DOS. You might need to purchase a new cable. You might want to use an "IBM approved" cable -- one which has been verified as properly wired. o If you still cannot print, and you are convinced it is not a printer-driver problem, interrupt problem, or cable problem, there might be a problem with your I/O adapter. Some older parallel-port adapters fail to generate hardware interrupts; therefore, they will not work with versions of the OS/2 operating system. These adapters usually work correctly under DOS, as DOS does not use hardware interrupts to print. The OS/2 2.0 operating system waits for the printer to send an interrupt when the printer is ready for more data. If your adapter does not generate interrupts, it must be replaced if you want to print under OS/2 2.0. If your printer-buffer light illuminates, or prints one character and then displays an error message (or otherwise behaves erratically), you might have an interrupt problem. Chapter 7. Printing Considerations 7-7 PRINTER STOPS PRINTING If your DOS application sending PostScript** output stops printing, do the following: 1. Cancel the print job that caused the printer to stop printing. 2. Open the printer-object settings notebook to the Queue page. 3. Turn off the PRINT WHILE SPOOLING check box. 4. Resend the print job. PRINT JOB DAMAGED ON RETRY If you send a print job to an offline printer, and then retry the operation when the printer is online by responding to the Retry message, your job might be damaged. To fix the problem, cancel the initial job, and resubmit it after resetting the printer. PRINTER WORKED UNDER DOS, BUT NOT UNDER OS/2 2.0 If your printer worked under DOS, but does not work under OS/2 2.0, there is probably a problem with your hardware-interrupt level or printer cable. (Refer to "Unable to Print" on page 7-7.) PRINT JOB SPOOLED BUT DOES NOT PRINT The spooler will not print a job until the application closes the print-data stream. Some DOS applications do not immediately close the print-data stream. If you see your print job as an icon with an arrow pointing to the document in the Job Icon View window, the job will not print. The arrow must point from the document to the print device. This will not occur until the application closes the data stream. If the job does not print after 15 seconds, you might need to change a DOS setting. By default, the PRINT_TIMEOUT DOS setting is turned ON and set to 15 seconds. If, after 15 seconds, your job does not print, adjust the setting. (Refer to "Printing Starts Only When DOS Application Ends" regarding the LPTDD.SYS file.) PRINTING STARTS ONLY WHEN DOS APPLICATION ENDS If your DOS print job does not begin printing until the application is ended, the application has not closed the data stream. Use the DOS_DEVICE DOS setting to load the C:\OS2\MDOS\LPTDD.SYS device driver. Then, the PRINT_TIMEOUT DOS setting can be used to close the print job without having to exit the application. 7-8 Tips and Techniques PRINT JOB SPLIT INTO SEVERAL SPOOL FILES If your DOS application print job is split into several spool files, you might need to disable the spooler to correct the problem. Some applications open and close the printer data stream for every character, line, or page. Disabling the spooler (using the Spooler object in the System Setup folder) is one way to correct this problem. Another alternative is to upgrade the application by contacting the manufacturer. If the problem occurs with complex printouts, you might increase the DOS setting PRINT_TIMEOUT value. CAN PRINT FROM DOS APPLICATION, BUT CANNOT PRINT ELSEWHERE If you are printing from a DOS application, but are unable to print elsewhere until you end the DOS application, your DOS application is accessing the parallel-port hardware directly. OS/2 2.0 prevents two or more applications from simultaneously accessing the same parallel-port hardware. The second application must wait for the first application to end, even if the second application is the OS/2 print object. PRINTER WORKED UNDER WINDOWS, BUT NOT UNDER OS/2 2.0 o If your printer worked under a Windows operation, but does not work after installing OS/2 2.0, delete the printer driver and reinstall it under WIN-OS/2 using the WIN-OS/2 Control Panel. o If printing from a WIN-OS/2 session is slow, but acceptable everywhere in the system, you might need to set the priority level higher using the Options menu in the WIN-OS/2 Print Manager. PRINTING FROM A WIN-OS/2 SESSION ________________________________ The following section describes considerations for customizing your system to print from a WIN-OS/2 session. LPTX AND LPTX.OS2 PORT CONSIDERATIONS If your printer is connected to LPTx or LPTx.OS2, be sure that the OS/2 _ _ spooler is active and the WIN-OS/2 printer does not use the Print Manager. (Disable using the Printer icon in the WIN-OS/2 Control Panel.) When the OS/2 spooler is active, WIN-OS/2 applications print directly to the OS/2 spooler. Therefore, multiple print jobs can be spooled from one WIN-OS/2 session or multiple WIN-OS/2 sessions. This does not apply to serial printers, because there is no spooling for COM devices to the OS/2 spooler (only to WIN-OS/2 Print Manager). If you are using LPTx but are unable to _ print from any other session, you must use LPTx.OS2 for WIN-OS/2 printing. _ If you are printing to a redirected port, you must use LPTx.OS2. _ Chapter 7. Printing Considerations 7-9 CONFIGURING AN LPT3.OS2 DESTINATION To enable support for LPT3.OS2, you need to configure an LPT3.OS2 destination that you can select from the ports listbox in the WIN-OS/2 Control Panel. You must shut down your WIN-OS/2 session and edit the C:\OS2\MDOS\WINOS2\WIN.INI file. You need to add a "LPT3.OS2=" line following the "LPT2.OS2=" line in the ports section of the file. After saving the file, you can start the WIN-OS/2 session and Control Panel and then select the LPT3.OS2 destination. INSTALLING THE IBM 4029 LASER PRINTER o If you are installing the IBM4029 Windows PostScript printer driver for use in WIN-OS/2 sessions, do the following to avoid an invalid entry in the WIN.INI file: 1. Select CONTROL PANEL in the WIN-OS/2 session. 2. Select PRINTERS. 3. Select ADD PRINTER. 4. Select UNLISTED PRINTER from the list of printers. 5. Insert Printer Driver Diskette 4 in drive A. _________________________ 6. In the Files and Directories window, select A. 7. Select PSCRIPT.DRV from the files list. (This installs the PostScript driver.) 8. Select CONFIGURE. 9. Select the appropriate port. 10. Select SETUP. 11. Select IBM4029 (17 font, 600 Dpi) from the list of printers. 12. Select OK several times to remove the open windows. 13. Exit the Control Panel. 14. Save any changes; then exit the WIN-OS/2 session. o If you have problems printing with a 4029 printer in a WIN-OS2 session, change the WIN.INI file in the OS2\MDOS\WINOS2 directory. Several lines in the file refer to the 4029 printer; for example: IBM 4029 v52.3 (17 Fonts, 600 Dpi) Now change the comma (,) to a colon (:) as follows: IBM 4029 v52.3 (17 Fonts: 600 Dpi) NETWORK PRINTING ________________ o To improve the performance of viewing the contents of a network printer object, use a long refresh interval or set the interval to 0 (no refresh). o If you move the network object from the desktop to another folder, the network printer-object template will not appear the next time you start the system. To make it reappear, move the network object back to the desktop and restart the system. 7-10 Tips and Techniques o If you are unable to print from a DOS session to an LPT port that is redirected to a network printer, you might need to use the LPTDD.SYS device driver. (Refer to "Printing Starts Only When DOS Application Ends" on page 7-8 for more information.) Chapter 7. Printing Considerations 7-11 7-12 Tips and Techniques CHAPTER 8. VIDEO GRAPHICS SUPPORT __________________________________ OS/2 2.0 fully supports EGA, and VGA. Because of the graphical user interface provided by the Workplace Shell, using OS/2 2.0 in CGA mode will be difficult and is not recommended. However, 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. The OS/2 installation program will correctly configure OS/2 2.0 and WIN-OS/2 drivers for the 8514 display and the XGA* mode. Resolutions above VGA (640 x 480 x 16 colors) are referred to as Super VGA (SVGA). The implementation of SVGA varies widely and requires different device drivers for different resolutions, as well as for different adapters and systems. All SVGA adapters are supported in VGA mode with the VGA driver provided with OS/2 2.0. SUPER VGA _________ 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 adapters. This support is required to switch between OS/2 Presentation Manager, 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 adapters have been tested and found to work with OS/2 2.0 for DOS applications that make use of SVGA modes: o Orchid** ProDesigner IIs by Orchid Technology (ISA and MCA versions) o Trident TVGA by Trident Microsystems, Inc. (8900b and c levels) o STB PowerGraph** VGA by STB Systems, Inc. o Video Seven VRAM II, by Video Seven o Boca Super VGA by Boca Research** Inc. o VGAWONDER XL** series by ATI Technologies, Inc. o Paradise VGA Professional by Western Digital Imaging VGA support is designed to be generic for the Trident, Tseng**, ATI, Headland, and Western Digital chipsets. It is likely that there are many more adapters which are supported that have not been tested. The 8514/ULTRA** by ATI must be installed as an 8514 and as a primary display; it will default to high-resolution mode. You need to edit the following statement in your CONFIG.SYS file: DEVICE=\OS2\MDOS\VVGA.SYS to DEVICE=\OS2\MDOS\VSVGA.SYS (C) Copyright IBM Corp. 1992 8-1 Contact the manufacturer of your computer or SVGA video adapter to obtain device drivers and installation instructions if you want to run Windows or OS/2 applications in SVGA modes. Information about SVGA support will be available on CompuServe, the National Support Center Bulletin Board System, the OS/2 Bulletin Board System, as well as many video-board and system manufacturers' bulletin boards. Do NOT run the video-adapter test utility programs in OS/2 2.0 unless the manufacturer has explicitly verified that they run in OS/2 2.0. Some video adapters require that the computer's DOS BIOS initialize the video adapter correctly. If you have one of these adapters, screen text might appear distorted in an OS/2 full-screen command prompt. To remedy this, start a DOS full-screen session, type EXIT, and then switch back to the OS/2 full-screen session; the text should appear normal. To automate this process, you can create a DOS batch file to run when you start your computer. Add the following statement to STARTUP.CMD: START /FS /DOS DOSFS.BAT Create the file DOSFS.BAT and place the following statement in it: EXIT SVGA ON UTILITY PROGRAM If you have one of the video adapters listed on the previous page and want to run DOS or Windows applications that make use of SVGA, you must turn on OS/2 2.0 SVGA support. The OS/2 Installation program detects the type of video chip in the system; it cannot detect the type of adapter or system board that the video chip has been implemented on. You must determine that you have a supported configuration, and then explicitly enable SVGA. To enable SVGA, type the following at a DOS full-screen command prompt: SVGA ON Then restart the system. NOTE: This does not apply to IBM PS/2 Micro Channel computers. OS/2 SVGA VIDEO FILES o OS2\SVGADATA.PMI This file indicates that SVGA support has been enabled with SVGA ON. The file contains data on the following: - The video chipset of your SVGA adapter. - The SVGA modes from the supported list your adapter is capable of setting. The list of supported modes is: 8-2 Tips and Techniques - 640 x 480/256 colors - 800 x 600/16 colors - 800 x 600/256 colors - 1024 x 768/16 colors - 1024 x 768/256 colors - 132 x 25 text - 132 x 43 or 44 text - The values in the video registers when the adapter is in each mode. This data is used by the OS/2 operating system to save and restore the registers to their proper state when switching between sessions with different SVGA modes set. This data file must be generated by typing SVGA ON at a DOS full-screen command prompt, because SVGA ON sets all the possible modes using the BIOS of the video adapter, and then reads out the values of the registers into the .PMI file. If SVGA ON is run from a DOS window, the video virtualization of the operating system takes over, and the BIOS does not set the SVGA modes properly. Even though two systems have the same video adapter, the same SVGADATA.PMI file does not work in both. The SVGADATA.PMI file has to be specific to each adapter/display setup. o OS2\SVGA.EXE This is the utility program that generates the .PMI file and places it in the OS2 subdirectory. The syntax is: SVGA ON|OFF|STATUS where ON creates the OS2\SVGADATA.PMI file and enables SVGA support, OFF deletes the .PMI file, and STATUS returns the chipset type that your adapter appears to be to the operating system. o OS2\DLL\DISPLAY.DLL This file determines what video resolution the desktop uses. This is the Presentation Manager display driver. The equivalent file on a Windows system is the VGA.DRV (in the case of VGA) file. For the first release, SVGA systems will have a VGA display driver installed on their system. Already, SVGA drivers are available from most of the main adapter manufacturers. o OS2\DLL\BVHSVGA.DLL This file is the Base Video Handler for the OS/2 operating system. Any OS/2 application that sets a video mode calls this DLL. In most cases, however, the only application that sets any video modes is the Presentation Manager display driver and the MODE.EXE utility program (for setting 132-column modes). The first time this DLL would be called is after the OS/2 bit-map logo appears (PM starts up then). This DLL is specified in the CONFIG.SYS file as the following: SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) Chapter 8. Video Graphics Support 8-3 BVHVGA is used to set, save, and restore VGA modes; BVHSVGA is used for SVGA modes. o OS2\MDOS\VSVGA.SYS This is the virtual video device handler for DOS sessions. All calls to change the video mode from a DOS session are handled through this driver. The job of this driver is to allow the user to set an SVGA mode, and when the user switches away, to save the current state of the video adapter (its registers and its video RAM). Then, when the user returns to the DOS session, it restores the video adapter to its previous state. When there is no .PMI file (SVGA is OFF), this driver acts like a VGA driver, except for adapter-specific code which ensures the VGA modes work correctly on the SVGA adapter. Therefore, even if you do not want SVGA, you will probably want VSVGA. o OS2\MDOS\WINOS2\SYSTEM\VGA.DRV OS2\MDOS\WINOS2\SYSTEM\SWINVGA.DRV These are the WIN-OS/2 full-screen and WIN-OS/2 window session drivers, respectively. They determine which resolution WIN-OS/2 uses. ADDITIONAL SVGA SUPPORT INFORMATION o Over time, more display adapters and PC systems that offer SVGA will be tested. Refer to the bulletin boards mentioned previously, or to the manufacturers, for the latest support information. o To make use of SVGA modes, you also must install Windows and Presentation Manager video display drivers. o If you experience display errors on an SVGA-enabled system, try disabling SVGA support by typing SVGA OFF at a command line. This will delete the SVGADATA.PMI file. Then restart your system. o In some SVGA displays, if you switch to the PM desktop while the screen is still drawing, you might experience display errors on the PM desktop. Switch back to the SVGA screen, allowing the drawing to complete, and then switch back to the PM desktop. o Some screen resynchronization problems might exist in DOS or WIN-OS/2 full-screen sessions. The problem is with how some SVGA adapters handle switching. IBM has created a new VSVGA.SYS file to correct this. Specifically, the problem occurs most frequently with Tseng chipsets. Video adapters using the Tseng ET4000 chipset with batch #TC6059AF have been identified as having this problem. The VSVGA.SYS file dated 4/8/92 or later should solve this problem. o In the event of a TRAP000E error message when opening a DOS or WIN-OS/2 session on systems with 4MB of memory and SVGA adapters, you need to obtain the VSVGA.SYS driver replacement from IBM. 8-4 Tips and Techniques o In the event of a SYS3176 message when starting a DOS or WIN-OS/2 command prompt, try setting the HW_ROM_TO_RAM setting in the session to ON or changing the DOS_RMSIZE parameter in the session to 624 from the default 640. If this does not work, the VSVGA.SYS fix from IBM might resolve the problem. o A virtual desktop is a Presentation Manager display driver that uses all of the adapter's video memory to store a desktop that is bigger than what is actually displayed. You could have 1024 x 1024 of desktop space, with only 640 x 480 being displayed on the screen. You move to other portions of the desktop by dragging the mouse to the edge of the screen, which scrolls the desktop. Because of the way OS/2 2.0 is designed, this is an extremely quick operation and will be very smooth, even on the slowest video adapters. The PM driver must be coded to support virtual desktops, and Trident is currently the only chipset to support it. o Trident supports OS/2 2.0 and has SVGA presentation drivers available for their SVGA boards. Trident's support number is 415-691-9211. They also have support bulletin boards where these drivers are available. For the West Coast, the number is 415-691-1016 and for the East Coast, the number is 203-483-0348. o Orchid is working on OS/2 drivers for their video adapters. For more information, you can reach Orchid's bulletin board service at: - 510-683-0327 for 2400 baud, parameters n,8,1 - 510-683-0555 for 9600 baud, parameters n,8,1 - ATI now has SVGA drivers for OS/2 2.0. Information is available using the ATI bulletin board service: 416-756-4591 (2400 baud, N, 8, 1) The file names are ATIOS213.ZIP and WIN31ACC.ZIP. - A WIN-OS/2 window session has the ability to run Windows Version 3.0 programs on the desktop. The way it is achieved is by making a place in the desktop that the WIN-OS/2 window session driver writes to. Special code must be put into both the window session driver and the display driver to support this. Trident has produced 800 x 600/16 WIN-OS/2 window session drivers, and has been the only one to produce SVGA support for WIN-OS/2 window sessions so far. - Questions about OS/2 support for adapters based on the S3 or TI** chipsets have been asked. Adapters which are coprocessed are the fastest, but also take the longest to develop software for. No manufacturers have announced dates yet for support of any of these adapters. You might want to contact the manufacturer for further information. - In the event of some corruption when returning to a WIN-OS/2 full-screen session, set your VIDEO_SWITCH_NOTIFICATION in the DOS Settings to ON. - Even in VGA, games in a DOS full-screen session are not optimized. Set your VIDEO_RETRACE_EMULATION in the DOS Settings to OFF. - Some DOS applications in a window have color corruption. This is a limitation of the VGA desktop. The color palette of the DOS session Chapter 8. Video Graphics Support 8-5 has to be translated to PM, and the 640 x 480/16 desktop does not offer enough colors to do a good translation. The best solution is to use a 256 color PM driver or run the application in a DOS full-screen session. - The graphics of some applications are corrupted when displayed in a window. These applications are probably using a nonstandard VGA mode that the adapter can support, but that OS/2 2.0 does not. - When you have SVGA ON, you can: - Use 132 column modes in an OS/2 full-screen session - Take a window with an SVGA image in it and paste it to the Clipboard - To enable the Windows 3.0 SVGA drivers in WIN-OS2, update the SYSTEM.INI file to point to a new Windows display driver, or just copy over the VGA.DRV in the OS2\MDOS\WINOS2\SYSTEM directory. Keep in mind, however, that a Windows session in SVGA mode will only work if you have set SVGA ON. - Many different SVGA boards have different interfaces and chipsets, each with their own characteristics. Some boards perform better with SVGA OFF. DUAL DISPLAYS _____________ In multiple XGA configurations, when you switch from DOS to the desktop, your system will not save and restore the hardware registers. If your machine has an 8514/ULTRA adapter and an OS/2 2.0 supported SVGA adapter, you will need to change the DEVICE= statement in your CONFIG.SYS file from VVGA.SYS to VSVGA.SYS. LAPTOP LCD OR MONOCHROME PLASMA DISPLAYS ________________________________________ To change the color schemes for OS/2 system windows and create a more readable display image, change the Scheme Palette as follows: 1. Use your Reference Diskette or hardware Setup program to set your hardware to VGA color, if possible. 2. Open the System folder. 3. Select SYSTEM SETUP. 4. Select SCHEME PALETTE. 5. Select the monochrome scheme in the right-hand column. This procedure will optimize the color scheme for gray-scale usage, and also provide a good set of colors for a VGA desktop presentation. INAPPROPRIATE FONT METRICS __________________________ 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 in the available space. 8-6 Tips and Techniques WIN-OS/2 WINDOW AND FULL-SCREEN SESSIONS ________________________________________ When running a WIN-OS/2 full-screen session with an 8514 adapter in high-resolution (8514.DRV) mode, do not switch to a different session while an application is updating the screen or displaying the hourglass. The following is a procedure for enabling WIN-OS/2 full-screen sessions to run in high-resolution (XGA) mode while the Workplace Shell desktop and WIN-OS/2 window sessions run in medium-resolution (VGA) mode. The procedure assumes you are not familiar with the SYSTEM.INI and WIN.INI files. Follow the instructions very carefully. Otherwise, you could cause your WIN-OS/2 sessions, both window and full-screen, to become inoperable. 1. Install OS/2 2.0 for medium-resolution VGA. The next step requires that you make backup copies of your SYSTEM.INI and WIN.INI files. DO NOT SKIP THIS STEP. It is assumed that you have a diskette or tape backup copy of your system; instructions follow for a backup of 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 mode, 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. Chapter 8. Video Graphics Support 8-7 UNPACK A:SYMBOLG.FON This procedure continues until all of the scalable fonts are unpacked. These fonts are: o SYMBOLG.FON o TMSRG.FON o COURG.FON o HELVG.FON Eventually the WINXGA file is found by the dir a:WINXGA search. It contains the WIN-OS/2 XGA.DRV and three XGA fonts. UNPACK A:WINXGA With all of the required driver and font files on the system disks, the next step is to modify the SYSTEM.INI file. 4. Edit the SYSTEM.INI file and find the following line: display.drv=vga.drv 5. This line specifies the device driver WIN-OS/2 is to use in full-screen sessions. Change this line to point to the high-resolution device driver that was unloaded in the steps above. In this example, the device driver is XGA.DRV. The modified line should look like the following: display.drv=xga.drv Both SYSTEM.INI and WIN.INI have font entries that must be changed. In SYSTEM.INI, these entries are: fixedfor.fon=vgafix.fon oemfonts.fon=vgaoem.fon fonts.fon=vgasys.fon For XGA mode, 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: 8-8 Tips and Techniques 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 the CONFIG.SYS file: DEVICE=C:\OS2\MDOS\V8514A.SYS For 8514 displays, the files to find are: WIN8514 (contains 8514.DRV, 8514SYS.FON, 8514OEM.FON, and 8514FIX.FON) COURF.FON TMSRF.FON HELVF.FON SYMBOLF.FON +--- TIP FOR PROGRAMMERS ---------------------------------------------------+ | | | Windows application program developers should note that their debuggers | | work in full-screen sessions only. If you have a dual-display setup | | (8514+VGA), install OS/2 2.0 for the 8514 as primary display with no | | secondary display. This will allow your Turbo Debugger for Windows (TDW) | | or CodeView for Windows (CVW) programs to run in a full-screen session on | | the VGA display while the WIN-OS/2 session runs full screen on the 8514. | | For CVW, make sure to use the /8 option. Quick C runs on the same | | display as WIN-OS/2. If you use Quick C, you don't need a special video | | configuration. | | | | Installing OS/2 2.0 in this way will allow PM to run on the 8514, and | | your full-screen debugger to run on the VGA. It also will provide a | | "stereo" effect for all full-screen sessions; both the 8514 and VGA | | displays will show the same picture, unless a full-screen application | | takes advantage of video-specific features. | | | +---------------------------------------------------------------------------+ Chapter 8. Video Graphics Support 8-9 8-10 Tips and Techniques CHAPTER 9. HARDWARE SUPPORT ____________________________ The following sections provide information about hardware device support in OS/2 2.0. PERSONAL COMPUTER MANUFACTURER SYSTEMS ______________________________________ OS/2 2.0 is supported on personal computers with an 80386 SX (or compatible) or later microprocessor, with at least 4MB of memory and a 60MB hard disk with 15MB -- 30MB of free space. IBM is currently testing personal computer manufacturer (PCM) systems for compatibility with OS/2 2.0. The compatibility test verifies 18 key functions of OS/2 2.0. Test results are based on selected model configurations provided by the manufacturers. While testing is continuing, current compatibility information about tested systems is available through your dealer or Marketing Representative, as well as through the following online services: o Prodigy**, Jump Computer Club, in Windows and OS/2 topic. (To join Prodigy, call 1-800-Prodigy.) o CompuServe, G IBMOS2, in Library 17, PCMTAB.TXT. (To join CompuServe, call the appropriate phone numbers for your area, or Membership Service at 1-800-848-8199, and ask for representative 239.) o IBM National Support Center Bulletin Board System (NSC BBS). This service is available 24 hours a day, on a toll-call basis, with no access charge, to anyone in the world who has a modem, asynchronous-communication programs, 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. o IBMLink. Eligible customers can obtain installation and usage assistance through IBMLink 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. (C) Copyright IBM Corp. 1992 9-1 SCSI ADAPTERS _____________ o ProCom+ SCSI disk adapters (Micro Channel) are not supported by OS/2 2.0. You should contact the manufacturer for any details on OS/2 support. o Some SCSI adapters have jumper pins which can be set to either synchronous or asynchronous mode. There have been noted problems such as no icons appearing or slow hard disk performance. This can be attributed to the SCSI adapter and hard disk not being set to the same synchronous or asynchronous settings. Either way, they must match. Be sure these are set properly. o The early versions of the IBM 16-bit SCSI adapters might experience problems and report, erroneously, that the device is not functioning. This can be corrected by replacing the SCSI adapter with an adapter with updated microcode. ADAPTEC AND FUTURE DOMAIN SCSI DEVICE DRIVERS Device support for the following Adaptec and Future Domain SCSI adapters is shipped with OS/2 2.0. When any of the following adapters is installed in a workstation, its presence is normally detected automatically, and the appropriate device support is subsequently installed. For reference, the names of the device drivers that support each adapter are provided in the following table. +-------------------------------------+-------------------------------------+ | SCSI ADAPTER OR INTERFACE | DEVICE DRIVER | +-------------------------------------+-------------------------------------+ | Adaptec A/C 6260 | AHA152X.ADD | +-------------------------------------+-------------------------------------+ | Adaptec AHA 1510 | AHA152X.ADD | +-------------------------------------+-------------------------------------+ | Adaptec AHA 1520/1522 | AHA152X.ADD | +-------------------------------------+-------------------------------------+ | Adaptec AHA 1540/1542 | AHA154X.ADD | +-------------------------------------+-------------------------------------+ | Adaptec AHA 1640 | AHA164X.ADD | +-------------------------------------+-------------------------------------+ | Adaptec AHA 1740/1742/1744 | | +-------------------------------------+-------------------------------------+ | (Standard mode operation) | AHA154X.ADD | +-------------------------------------+-------------------------------------+ | (Enhanced mode operation) | AHA174X.ADD | +-------------------------------------+-------------------------------------+ | Future Domain TMC-850/860/875/885 | FD8XX.ADD | +-------------------------------------+-------------------------------------+ | Future Domain TMC-1660/1670/1680 | FD16-700.ADD | +-------------------------------------+-------------------------------------+ | Future Domain MCS-600/700 | FD16-700.ADD | +-------------------------------------+-------------------------------------+ 9-2 Tips and Techniques +-------------------------------------+-------------------------------------+ | SCSI ADAPTER OR INTERFACE | DEVICE DRIVER | +-------------------------------------+-------------------------------------+ | Future Domain TMC-850IBM | FD850IBM.ADD | +-------------------------------------+-------------------------------------+ For the Adaptec 1542B SCSI card to run properly, set the default data rate to 5. The TMC-850/860/875/885 and TMC-850IBM adapters will not be detected when the adapter's BIOS is disabled. To install this support in your system follow these steps: 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 Where xxxxxxxx.ADD is the file name of the device-driver file you want to ____________ install. 5. Add the following line to the CONFIG.SYS file: BASEDEV=xxxxxxxx.ADD 6. Restart the system. OS2SCSI.DMD DEVICE DRIVER Earlier versions of the OS/2 operating system used the device driver SCSI.SYS. This has been replaced by OS2SCSI.DMD. OS2SCSI.DMD is provided in the OS2 directory of the startup partition. Replace the old CONFIG.SYS entry "DEVICE=SCSI.SYS" with "BASEDEV=OS2SCSI.DMD." Normally, this is done automatically, but inspect your CONFIG.SYS file if you suspect SCSI problems. The OS2SCSI.DMD device driver is required for a number of SCSI CD-ROM devices, SCSI read/write optical devices, and SCSI tape devices. SCSI CD-ROM SUPPORT The SCSI CD-ROM support built into OS/2 2.0 has some manufacturer-specific dependencies at this time. Support has been verified for IBM and Toshiba SCSI CD-ROM drives. If your CD-ROM is either SCSI with no other devices attached or is non-SCSI, you might get it to work by using an external DOS session (VMBOOT by using the DOS Program setting, DOS_STARTUP_DRIVE ). Information about the support and verification of additional manufacturers' drives will be made available at a later date. Chapter 9. Hardware Support 9-3 SCSI REMOVABLE MEDIA SUPPORT Full-function support is not yet available for SCSI hard disk drives that are 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 them 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 this medium, and partitioned removable-media drives will not be recognized. If the IBMINT13.I13 driver is used to control these units, the drive will be treated as a hard disk. In this case, the cartridge must be in the drive at startup time. Use the SHUT DOWN choice on the desktop pop-up menu to remove the cartridge from the drive. Bernoulli 44MB and 89MB drives work if connected to Adaptec, Future Domain, IBM, or any adapter other than the Bernoulli adapter. The drive will work as a large diskette but cannot be used as a startup drive. Customers should call Iomega for status on an update for their adapter. If Seagate SCSI controller model ST-01 or ST-02 is present, it must be the only drive controller present. Conflicts exist between this controller and MFM and RLL hard disk controllers. If you experience some problems with a Western Digital WD7000 SCSI adapter, contact Future Domain for assistance. SCSI USAGE TIPS The following table provides tips on usage and potential compatibility problems with the microcode levels on various adapters and devices. +-------------------------------------+-------------------------------------+ | ADAPTER | TIP | +-------------------------------------+-------------------------------------+ | All Adaptec adapters | o Might produce contention | | | problems with the | | | diskette-drive controller on | | | fast computers. | | | o Do not support drives of 1GB or | | | larger. | | | o Must have SCSI hard disks | | | configured as SCSI target ID 0 | | | or 1 to be able to start up | | | from that hard disk. | +-------------------------------------+-------------------------------------+ 9-4 Tips and Techniques +-------------------------------------+-------------------------------------+ | ADAPTER | TIP | +-------------------------------------+-------------------------------------+ | IBM SCSI | If you experience intermittent data | | | errors with earlier IBM SCSI | | | adapters, you might need to upgrade | | | them. If you have IBM SCSI FRU P/N | | | 15F6561, obtain ECA032. If you | | | have IBM SCSI with cache FRU P/N | | | 64F0124, obtain ECA027. These | | | adapters are standard in 8565 | | | models 061 and 121 and 8580 models | | | 121, 131, A21, and A31. | +-------------------------------------+-------------------------------------+ | Adaptec AHA-154x | Drive: IBM 0661 - 320MB SCSI | _ | | | | | Adapter BIOS will not recognize the | | | drive as Target 0 or 1 (Drives 80, | | | 81). For OS/2 2.0, the drive can | | | be used but not as a startup drive. | +-------------------------------------+-------------------------------------+ | Adaptec AHA-174x | Drive: IBM WDS-3180 - 80MB SCSI, | _ | | IBM WDS-3160 -160MB SCSI | | | | | | 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. | +-------------------------------------+-------------------------------------+ | Future Domain TMC-850/860/875/885 | System: IBM Models 35 and 40 | | w/BIOS revision level 7.0. Future | | | Domain TMC-1660/1670/1680 w/BIOS | When the Future Domain adapter is | | revision level 2.0. | controlling the startup diskette, | | | it will produce the message, "Disk | | | read error has occurred" when you | | | attempt to start the Installation | ____________ | | Diskette. Contact Future Domain | ________ | | for a free BIOS upgrade. | +-------------------------------------+-------------------------------------+ | Seagate ST-01, ST-02 | Causes contention with MFM and RLL | | | drives. The ST-01 or ST-02 should | | | be the only drive controller | | | installed. This problem is being | | | investigated. | +-------------------------------------+-------------------------------------+ Chapter 9. Hardware Support 9-5 +-------------------------------------+-------------------------------------+ | ADAPTER | TIP | +-------------------------------------+-------------------------------------+ | Western Digital WD7000 | Newer adapters seem to be supported | | | while earlier ones are not. | | | Western Digital is now owned by | | | Future Domain. Contact Future | | | Domain for assistance. | +-------------------------------------+-------------------------------------+ AMI AND CEI SCSI ADAPTERS AMI Fast Disk and AMI Fast Disk II SCSI adapters are incorrectly recognized as Adaptec adapters. The CEI Cumulus C5640B SCSI Micro Channel adapter has the same problem. If you have one of these adapters in your system, do the following: o At the final restart after the installation is completed, delete from the CONFIG.SYS file any line with "BASEDEV=AHA1xxx.ADD" (where x can be any ___ _ character). o Ensure the line "BASEDEV=IBMINT13.I13" appears in the CONFIG.SYS file. This line should have been placed there by system installation. ALWAYS TECHNOLOGY SCSI If you are experiencing OS/2 problems either at installation time or after, (such as a TRAP 000D error) and your system has an Always Technology IN-2000 SCSI adapter, the BIOS on the adapter might be the problem. If the BIOS revision level is 3.06A or 3.20 (as shown during the system self-test), you should get the BIOS on the adapter upgraded. The current BIOS level is VCN:1-02 and works with OS/2 2.0. If you require this upgrade, you might also need an upgrade to a companion 8-pin serial PROM chip which must have a revision level of 2.5-2.7. Always Technology support can be reached at 818-597-9595. ADDITIONAL DEVICE SUPPORT INFORMATION _____________________________________ The following contains useful information about OS/2 2.0 support for the specified devices. BERNOULLI DEVICE DRIVERS If you are experiencing a problem installing your new Bernoulli device driver, call the Iomega Corporation support group at 1-800-456-5522 and ask for an OS/2 technician. 9-6 Tips and Techniques HP SCANJET If you receive an error message saying that you cannot access your HP scanner, and you are using an ISA (AT-style) bus machine, your adapter switches need to be set to 1010. If you are using a PS/2 computer, you must use the Reference Diskette to set the adapter to ROM addresses C8000 -- CBFFF and I/O addresses 268 -- 26F. In both cases, you also need to set the DOS Setting for the DOS session for EMS_FRAME_LOCATION to Auto. TAPE DRIVES The following describes IBM and non-IBM tape drives that work in conjunction with OS/2 2.0. Adapter or SCSI The only tape drives that have been tested at this point are IBM tape drives. If no other device is connected to the SCSI bus on its adapter or the tape adapter, then you might be able to get your drive to work in an external DOS (VMBOOT) session. If the tape drive worked under OS/2 version 1.x and the device is written to _ ASPI, IBM is currently working on support for your device. IBM does not provide third-party device drivers for peripherals. Refer to your peripheral manufacturer for OS/2-specific support. Diskette Based IBM or IRWIN tape drives are supported. Programs are PMTAPE or PS2TAPE. Easy Tape from Maynard Backup Systems is scheduled for future release. Contact Maynard for information. Colorado Jumbo For Colorado Jumbo tape drives connected to a diskette-drive controller, you must set up a DOS Startup session from a diskette image and run the tape backup program from it. To do this, you need to refer to the topic "Starting DOS from an image file" in the Master Help Index. The Colorado Jumbo Tape program allows you to specify some hardware and software settings to be used when backing up files. The CONCURRENT DISK/TAPE OPERATION option must be set to No. To change the option, start the program and select the Utilities menu (F3); then select SOFTWARE SETUPS (F6). Change the option to N. The Colorado company is developing an OS/2-specific version of their program. For more information, contact Colorado. Chapter 9. Hardware Support 9-7 Mountain The Mountain company is developing an OS/2-specific version of their program. For more information, contact Mountain at 1-800-458-0300. IBM PS/2 MODEL 30-286 UPGRADES IBM PS/2 Model 30-286 upgrades to a 386 microprocessor are not supported. 50 MHZ SYSTEMS There have been some intermittent problems using 50 MHz systems with AT-style bus computers with a mouse. The mouse can get out of synchronization. Input will function through the keyboard and the mouse, but to avoid possible problems, shut down the system and restart to resynchronize the mouse. LOGITECH 3-BUTTON MOUSE The Logitech 3-button bus mouse is supported as a 2-button mouse. It is treated as a Microsoft 2-button bus mouse. A Logitech serial mouse with 3 buttons behaves as expected in DOS sessions. In a Presentation Manager session, however, there might be different and more limited functions assigned to the buttons. There are no standards for the functions of 3-button mice. AOX SYSTEMS If your computer has an Aox** add-in microprocessor adapter card and you encounter problems either installing or starting up your OS/2 system, you can call the Aox Corporation and ask for the latest "flash-prom" code upgrade. PERSTORE PerStore drive controllers are not supported. INTERRUPT PROBLEMS ON AN ISA SYSTEM On an ISA system, having a shared interrupt-request line can cause problems. ISA systems have what are called edge triggered interrupts, whereas Micro ______________ Channel and EISA systems use level sensitive interrupts. Edge triggered _______________ interrupts can only be sensed for a very short period. If a second interrupt arrives from another adapter while the first interrupt is still being processed, the second interrupt will be lost. In your computer system, this situation can lead to various difficulties, such as printers that do not seem to print smoothly or reliably, or communications sessions where some characters are getting lost. 9-8 Tips and Techniques However, with single-tasking systems such as DOS, the two adapters that are sharing the interrupt might never cause any real problems because they might never be in use at the same time. However, OS/2 2.0 presents a different set of problems. If you have multiple serial communications adapters, there is a greater probability that you might try to use two or more of them at the same time. If some of them have previously been set up using shared interrupts, problems can occur that probably didn't happen in DOS. OS/2 2.0 can detect that an interrupt line is shared and will not allow simultaneous use. Assume that COM1 and COM3 are sharing Interrupt Request line 4 (IRQ4). If you try to use both COM ports at the same time, the OS/2 operating system will not allow the second one to start. A well-written OS/2 communications program will recognize that the port cannot be opened and an error message will be displayed. However, a DOS program is unprepared to respond to this unfamiliar situation. It will probably suspend, waiting for the port that will not open. Another potential source of trouble is having multiple hardware adapters that are sharing the same I/O address. The various hardware adapters in your computer must have their own addresses. Consider what might happen, for example, if the commands that were meant for your printer were instead routed to your disk drive. The solution for all of these problems is to ensure that all your hardware adapters have their own unique I/O addresses and IRQ assignments. COMMUNICATION PORTS ACCESSED BY DOS APPLICATION PROGRAMS When COM_DIRECT_ACCESS is set to On, DOS programs use VCOM.SYS to directly access communication ports. COM_DIRECT_ACCESS enables LapLink III, FastLynx, FSDUAT, AS/400 Asynch Router, MS Word to work in a DOS session. However, because buffers in COM.SYS cannot be used, characters are sometimes lost, and some programs experience difficulties from the lack of buffering. Therefore, on most DOS programs, it is a good idea to set COM_DIRECT_ACCESS to Off as its default setting. COM_SELECT enables a DOS session to select and use one communication port. Communication ports that are not selected are hidden from the DOS session. There are some DOS programs that take over every available communication port, such as LapLink Pro. If LapLink Pro and another program that accesses a communication port are executed at the same time, it is necessary to set COM_SELECT to All as its default setting. COMMUNICATION PORT IS NOT RECOGNIZED OR DOES NOT WORK Most problems with Interrupt Request (IRQ) lines and I/O address settings occur on an AT bus (ISA) computer as a limitation of the hardware. IRQ lines can be shared on a micro channel (MCA) computer provided the adapter card is MCA compatible and is configured with the Reference Diskette. The follow provides some solutions for your communications problems: Chapter 9. Hardware Support 9-9 o Verify that all IRQ levels and I/O addresses are unique for every adapter card. The normal problem is that communication adapters, such as internal modems, FAX machines, etc., use COM3 and IRQ4, which are already in use by COM1. You MUST change the IRQ on the adapter card to one that is not in use. Refer to the documentation that came with the adapter card. o Verify that the correct parameters are being passed to the COM.SYS driver in the CONFIG.SYS file. Refer to "Communication Ports Accessed by DOS Application Programs" on page 9-9. o Obtain the latest OS/2 2.0 communication drivers. o During boot, if the message "COMx not installed because Interrupt is already in use" appears, ensure there is no IRQ conflict with other device drivers or hardware. o If the system (AT bus or MCA) boots without an error but the communication ports are not working, type the following at an OS/2 command prompt: MODE COMx Where x is the problem communication port. If a message appears _ indicating the COMx port is not installed, check for IRQ conflicts. _ NOTE: If the mouse is on a communication port, the message "SYS1620 COM port specified is not installed" appears. o If the program is a DOS communication program, set DOS_SETTINGS to the following: COM_HOLD On COM_DIRECT_ACCESS On or Off* COM_Select Specified COMx* _ DOS_DEVICE X:\OS2\MDOS\COMMDD.SYS** HW_ROM_TO_RAM On HW_TIMER On IDLE_SECONDS 60 IDLE_SENSITIVITY 100 *Requires the latest device drivers. Refer to "Communication Ports Accessed by DOS Application Programs" on page 9-9. **The DOS_DEVICE (COMMDD.SYS device driver) might require more than one device driver depending on the program. For example, Intel's SatisFAXtion requires a device driver loaded into each DOS session that 9-10 Tips and Techniques uses an adapter. The COMMDD.SYS device driver is usually required only for earlier DOS communication programs. Do not use DOS_DEVICE for every DOS communication session; use it only if it resolves the problem. o To provide a higher priority to all communication programs, edit the following in the CONFIG.SYS file: PRIORITY_DISK_IO: NO MAXWAIT: 1 o Some DOS programs open all the communication ports. If this occurs, use the COM_SELECT DOS property (see "Communication Ports Accessed by DOS Application Programs" on page 9-9) in all DOS communication sessions. COM3 OR COM4 SUPPORT ON AN ISA SYSTEM The original ISA computer (the IBM Personal Computer AT) allowed for the definition of up to four serial communication ports. However, there has never been any hardware architectural standard that defined the I/O port addresses or IRQ lines associated with communication ports 3 or 4. Over the years, a convention has developed that places the port addresses for COM3 and COM4 at 03E8 and 02E8 respectively. This is a generally accepted convention, but not a standard. Check the documentation and the settings of the adapters in your system to verify your hardware environment. After you have checked and set the I/O and IRQ values on your COM ports or internal modems, you must add this information to the communications device-driver (COM.SYS) statement in the CONFIG.SYS file. You might also need to tell your communications program where the COM ports are. ProCom software, for example, has a configuration screen that enables you to specify these settings. If the program, operating system, and hardware are not in agreement, then the program will not run. OS/2 COM ports do not need to be defined in sequence. It is acceptable to have a COM4 without having a COM3. DOS, however, might have difficulty if there is a gap in the port definition. To avoid confusion for DOS, you can define COM ports that do not have any physical adapters attached in the COM.SYS statement. These substitute definitions will serve as placeholders. COM1 and COM2 are assumed to have standard values and do not need to be explicitly set up unless you want to set some nonstandard values to accommodate your particular configuration. To enable COM3 or COM4 on an ISA system, place the following in the CONFIG.SYS file: DEVICE=X:\OS2\COM.SYS (n,a,i) (n,a,i) where: X is the drive where OS/2 is installed. N is the communication port that you are attempting to access. Chapter 9. Hardware Support 9-11 A is the communication port I/O address (for example, 03E8 and 02E8). I is the IRQ level, which is usually a jumper setting on the I/O adapter. For example, to specify that COM3 is at address 03E8 on IRQ5 and that COM4 is at address 02E8 on IRQ10, use the following statement (assuming that OS/2 is installed on drive C): DEVICE=C:\OS2\COM.SYS (3,03E8,5) (4,02E8,10) The I/O address and IRQ level should be noted in the documentation that came with your adapter. Either or both might be fixed values or can be set to a range of values via jumpers or switches. In some cases you might find that the values are fixed or that the range of settings available to you is insufficient to avoid the sharing conflict. In that case, you must purchase a different, more versatile adapter or accept that you cannot use both adapters at the same time. SETTING THE INTERRUPT REQUEST (IRQ) LEVEL ON AN ISA SYSTEM The following information will help you determine what IRQ settings you can use for COM3 or COM4 port adapters to avoid shared interrupts. On an ISA machine there are a total of 15 IRQ levels available. Many of these are already being used. Most are already in use because they are the the standard settings for the more common devices. These standard settings are as follows: IRQ LEVEL DEVICE ASSOCIATED 0 System Timer 1 Keyboard 2 Secondary Interrupt Controller (see note) 3 COM2 (Serial Communications Port 2) 4 COM1 (Serial Communications Port 1) 5 LPT2 (Parallel Port 2) 6 Diskette 7 LPT1 (Parallel Port 1) 8 Real-time Clock 9 open 10 open 11 open 9-12 Tips and Techniques 12 open 13 Math Coprocessor 14 Hard Disk 15 open NOTE: On the IBM-AT (ISA bus), the IRQ9 pin is identical with the IRQ2 pin on the original IBM-PC. If you have an earlier, 8-bit adapter whose documentation states that it uses IRQ2, be aware that this will actually be interpreted as IRQ9 when plugged into the 16-bit ISA bus. The IRQ levels shown as "Open" have no established, standardized use. When setting the IRQ values on your COM3 or COM4 ports, you are likely to find these levels available to use without conflict with some other adapter. Furthermore, if you don't have two parallel ports installed, IRQ5 might be usable for some other purpose, such as COM3 or COM4. Be cautious about doing this because it might cause a problem later if you decide to install a second parallel port. In addition, some other nonstandard device might already be using IRQ5. When trying to manage the IRQ levels of your various hardware adapters to avoid conflicts, you might find that your 8-bit adapters cause problems. Except for IRQ9, only 16-bit adapters are configurable to use IRQ levels higher than 7. Notice that IRQ table shows that the low-numbered IRQ lines already have some standard function assigned. It might be that your only alternative for avoiding some IRQ conflicts is to purchase a more versatile 16-bit adapter. If you have nonstandard 8-bit adapters, be especially careful of interrupt conflicts. For example, the SoundBlaster adapter is configured at the factory to use IRQ7. IRQ7, however, is the standard assignment for LPT1, the first printer port. This conflict might not be apparent with DOS because DOS printing typically does not use the interrupt line. OS/2 2.0, however, requires it, and the hidden conflict can become the source of printing problems. It is also fairly common to discover that the interrupt feature on your parallel-port adapter does not work. In DOS, this might not have any effect. In OS/2 2.0, however, your printer might be very erratic or not work at all. PARALLEL-PORT-ATTACHED DEVICE o If you have a parallel device (for example, a tablet system, LAN adapter, or SCSI device) that does not work in a DOS session, it might be because interrupt IRQ7 is not reflected in the session. Your device might attempt to use the parallel-port feature and is prevented from doing so. OS/2 developers are working on a solution for this limitation. o Some security devices (known as dongles) attached to a parallel port do _______ not work properly with OS/2 2.0. The DOS program that uses the device can start from one DOS session only. An error message appears when you try to start additional copies of the program. You can press Chapter 9. Hardware Support 9-13 Ctrl+Alt+Print Screen to release access to the parallel-port program prior to starting the second copy of the DOS program. o Make sure you are using cables that are properly shielded and wired. (For more information, refer to "Unable to Print" on page 7-7.) FAX ADAPTERS When certain fax adapters are operating as ordinary modems, they might operate correctly yet fail to work correctly as a fax device in a DOS session. The probable cause of the trouble is the VCOM.SYS device driver. VCOM.SYS might be introducing timing distortions into those hardware commands that are used to control the fax device but are not a part of normal asynchronous communications. Because there are no standards established for fax controls, it might be that the only solution is to acquire an OS/2-based fax device driver and program. Your fax adapter manufacturer might have information on sources and availability of OS/2-based program. Without purchasing new software, you can try removing the VCOM.SYS statement from your CONFIG.SYS file. This might allow your fax adapter to work properly but might have other undesirable side effects. One of the functions of VCOM.SYS is to provide a performance assist. Without VCOM.SYS, you might have to use a reduced baud rate. Also, some programs, such as Prodigy, will not run without it. Therefore, while removing VCOM.SYS is all right in some instances, it might not be the right action for you. If you have an ISA bus system, you might consider making changes to the fax adapter so that only part of your system detects it. Then, place all operation into a single DOS session. This is possible on an ISA system if you can set up your fax adapter as COM3 or COM4. Since there are no standards for COM3 or COM4 on an ISA system, OS/2 2.0 will not recognize the adapter unless it is defined for the system in the CONFIG.SYS file (See the section "COM3 or COM4 Support on an ISA System" found earlier in this chapter). To set up this configuration, set the hardware switches on the fax adapter to indicate either COM3 or COM4. Use a setting that is available and that does not conflict with other adapters. Leave VCOM.SYS in your CONFIG.SYS definition but do not define the fax adapter settings to the COM.SYS device driver. When OS/2 2.0 starts up, it will not recognize the fax adapter, but the normal communications ports will still get the benefit of having VCOM.SYS available. Next, set up a DOS session so that it loads the DOS programs that you use for faxing and also the DOS device driver used to control the fax adapter if it came with a special driver. Check your documentation to be sure. This single DOS session should now be able to operate your fax adapter normally. In some cases, this still might not work. If the DOS program treats the adapter as a COM port instead of directly accessing the hardware, then DOS will not recognize the adapter either. The only problem with this 9-14 Tips and Techniques configuration is that this single DOS session controls the adapter. Other DOS or OS/2 sessions will not be able to access it at all. IBM is working on a fix to alleviate this problem, but the best solution is to use OS/2-specific device drivers and programs, especially where performance is critical. PS/2 EXTERNAL 5.25-INCH 1.2MB DISKETTE DRIVE If you cannot get the external 5.25-inch 1.2MB diskette drive to work on a PS/2 computer, install the device driver that comes with the drive into the OS2 directory in the startup partition. The device driver is called EXT5DD.SYS. Change your CONFIG.SYS file statement to read \OS2\EXT5DD.SYS instead of \OS2\EXTDSKDD.SYS. IBM PS/2 MODEL 90 OR 95 If you are experiencing problems with your Model 90 or 95, ensure your system is at the latest engineering change (EC) level. Your IBM service representative can assist you. If your Model 90 or 95 is a 33 MHz system and you are having intermittent difficulty identifying memory parity errors such as TRAP 0002, forcing you to restart your system, then ECA053 might apply. If your microprocessor card has part number 84F9356, contact your IBM representative to assist you with a replacement. If your Model 90 is experiencing intermittent memory errors, ECA084 might apply if the part number of your memory riser card is N33F4905 or 84F9356. Again, your IBM representative can assist you with a replacement. For both Model 90 and 95 computers, you must ensure that you have matched pairs of single inline memory modules. This means that each pair of single inline memory modules, as described in your technical reference manual, must be matched in memory size and speed. Mixing these modules can cause some computers to report memory errors. FORMATTING DISKETTES ____________________ If you have a non Micro Channel system with a 5.25-inch drive, and its 3.5-inch drives all support media sense, your 5.25-inch drive will format diskettes at 720MB. Previously formatted 1.2MB diskettes will read and write correctly. A fix for this problem can be obtained from the electronic bulletin board described in Chapter 2 "Service and Support Information." Chapter 9. Hardware Support 9-15 9-16 Tips and Techniques INDEX _____ +--------------------+ application programs | SPECIAL CHARACTERS | Aldus PageMaker 4.0 5-6 +--------------------+ AutoCAD 5-6 automatic startup 4-1 .INI files Borland 5-7 re-creating 4-6 Central Point Backup for DOS restoring 4-5 7.1 5-7 Central Point PC Tools Deluxe 7.1 5-7 +----------+ Commander Keen 5-8 | NUMERICS | communication applications 9-11 +----------+ Commute 5-8 Control Room 1.0 5-8 38XX printers 7-4 CorelDRAW 2.0 5-8 4019 printer 7-4 CorelDRAW 2.1 5-8 4029 printer 7-4 creating an icon for 4-5 51XX printers 7-4 Crosstalk 5-8 52XX printers 7-4 dBase IV 1.1 5-8 8514 display 6-1, 8-9 Designer 5-9 8514, changing in WIN-OS/2 6-1 disabling automatic startup 4-2 DOS and Windows, shut down after installation 2-15 +---+ DOS application | A | considerations 3-2 +---+ Drafix CAD versiom 1.11 5-9 Drafix CAD version 3.0 5-9 Action! Sampler 1.0 5-4 error message 4-9 Adaptec 1542B SCSI Card 9-3 Excel for DOS 2.1 5-18 Adaptec device driver 9-2 Excel for OS/2 3.0 5-18 adapters, configuring for Excel for Windows 3.0 5-18 printing 7-1 Fastback for Windows 5-10 Adobe Type Manager 5-4 Fastback Plus 2.1 and 3.04 5-10 AES 7-4 FastLynx 1.1 5-10 After Dark 5-4 FotoMan 5-11 Aldus Freelance Graphics for OS/2 5-15 PageMaker 4.0 5-6 Freelance Graphics for PageMaker, printing bit maps 7-3 Windows 5-15 Persuasion 2.0 5-6 graphics 8-6 Always Technology adapters 9-6 Harvard Draw 5-11 AMI BIOS, old version 2-10 Harvard Graphics 5-11 AMI SCSI adapters 9-6 IBM PC/3270 V2.0 5-12 ANSI colors and characters 4-9 incompatible programs 5-1 Aox systems 9-8 Intel SatisFAXtion 5-12 LANtastic version 4.0 5-14 (C) Copyright IBM Corp. 1992 X-1 application programs (continued) AutoCAD 5-6 LANtastic version 4.1 5-14 AutoManager 4.0 5-7 Laplink Pro 5-14 automatic emulation switching 7-4 Lotus 1-2-3 for Windows 1.0 5-14 Lotus 1-2-3 Release 3.1 5-14 Lotus Notes 5-15 +---+ Magellan 2.0 5-15 | B | MAGICorp 5-16 +---+ Mathcad veriosn 3.0 5-16 Mathcad version 3.1 5-16 basic input/output system (BIOS), memory considerations 3-3 old version Microsoft Bookshelf 5-17 AMI 2-10 Microsoft Chart 3.0 5-17 Gateway 2000 2-12 Microsoft Codeview 5-17 Micronics system board 2-12 Microsoft CodeView for Windows Phoenix 2-10 Version 3.0 5-18 BBS 1-1 Microsoft Money 1.0 5-18 beeping (constant during diskette Microsoft MSCDEX 5-18 changing) 2-9 Microsoft QuickC 5-18 Bernoulli drivers, installing 9-6 Microsoft Word 5-18 Bernoulli removable drives 9-4 migration did not work 2-15 bit maps not appearing 4-3 More Windows 5-17 Boca Super VGA 8-1 National Geographic Bookshelf (Microsoft) 5-17 Presidents 5-19 Boot Manager 2-16, 6-1 National Geographics Borland Mammals 5-19 C++ 2.0 and 3.0 5-7 Norton Backup 1.2 5-19 Turbo C++ 2.0 5-7 Norton Desktop 5-19 Turbo Debugger 2.01 5-7 Norton Utilities 5.0 5-19 Turbo Debugger for Windows 5-7 PFS First Choice 5-20 Turbo Pascal 6.0 5-7 PFS WindowWorks 1.75 5-20 Bubble-Jet printer 7-3 preventing automatic startup 4-2 bulletin board systems support 1-1 Project for Windows 1.0 5-18 BVHSVGA.DLL file 8-3 SideKick 5-21 Turbo Pascal 6.0 5-7 using Windows 3.1 2-15 +---+ WIN-OS/2 6-1 | C | Windows 3.0 5-18 +---+ Windows performance considerations 3-2 C0000005 (system error message) 2-9 Windows programs 5-4 cache size 3-1 WordPerfect for Windows 5-22 CD-ROM, SCSI device support 9-3 WordPerfect Office 3.0 5-22 CD-ROM, Selective Install 2-16 application support 5-1 CEI adapters 9-6 Arts & Letters Graphics Editor Central Point 3.1 5-6 Backup for DOS 7.1 5-7 AT bus IRQ levels 7-1 PC Tools Deluxe 7.1 5-7 ATI video adapter (white screen CGA support 8-1 problem) 2-10 CGA, changing in WIN-OS/2 6-1 X-2 Tips and Techniques changing Crosstalk 5-8 country settings 6-2 customizing language 6-2 default folder view 4-8 characters in DOS sessions 4-9 system startup 4-2 CHKDSK error with swapper file 3-1 clipboard closing 6-3 +---+ DDE and Paste Link choice 6-5 | D | public or private 6-2 +---+ vertical scrolling does not work 6-4 Data Update, closing 6-3 when running Windows 3-2 dBase IV 1.1 5-8 Clipboard Viewer and OS/2 2.0 debuggers 8-9 Limited Availability 2-2 decompressing device drivers 6-1 CodeView 8-9 Designer 5-9 color DeskJet Printers 7-3 ANSI colors and characters in desktop DOS 4-9 adding an OS/2 window 4-7 changing icon title text 4-4 restoring damaged 4-5 color schemes 8-6 details view 4-8 Colorado jumbo tape drives 9-7 device driver statements in COM_DIRECT_ACCESS DOS property 9-9 CONFIG.SYS 2-4 COM_SELECT DOS property 9-9 device drivers COM3 support on an ISA system 9-11 Bernoulli 9-6 COM4 support on an ISA system 9-11 for PS/2 5.25-inch diskette 9-15 command prompt 4-7 OS2SCI.DMD 9-3 Commander Keen 5-8 problems, compatibility 9-4 commands 4-9 device support information Commute 5-8 fax adapters 9-14 CompuServe 1-1, 6-1, 9-1 Logitech mouse 9-8 CONFIG.SYS file parallel-port-attached automatic update 4-3 device 9-13 automatically updating 2-4 PS/2 external 5.25-inch 1.2MB device driver statements, diskette drive 9-15 adding 2-4 PS/2 model 30-286 9-8 restoring desktop 4-5 PS/2 model 90 or 95 9-15 when installing an HP mouse 2-4 device support, SCSI Configure program for OS/2 2.0 50MHz systems 9-8 environment 6-1 Adaptec and Future Domain 9-2 configuring Always Technology adapters 9-6 IBM 4029 Laser Printer 7-10 AMI SCSI adapters 9-6 printers 7-2 Aox systems 9-8 Control Room 1.0 5-8 ATI SVGA drivers 8-5 copying metafiles 6-4 Bernoulli 9-4 CorelDRAW Bernoulli drivers 9-6 version 2.0 5-8 CD-ROM 9-3 version 2.1 5-8 HP Scanjet 9-7 country setting configuration 6-2 Orchid video adapters 8-5 COUNTRY.SYS cannot find file ProCom and SCSI disk adapters (message) 2-9 (Micro Channel) 9-2 Index X-3 device support, SCSI (continued) DOS session, specific 5-3 removable media 9-4 DOS version message 4-9 Seagate 9-4 Drafix CAD SyQest 9-4 version 1.11 5-9 tape drives 9-7 version 3.0 5-9 Western Digital 9-4 dual boot 6-1 devices, configuring printers 7-2 does not work (no error diagnosing message) 2-16 printing problems 7-7 EC-00BF error message 2-9 workplace shell problems 4-1 in a partition with OS/2 disk controller, PerStore 9-8 1.3 2-17 disk drive not working 2-17 SYS1200 error message 2-9 disk light constant with white DynaComm Asynchronous OS/2 5-9 screen 2-10 Dynamic Data Exchange DISKCACHE command 3-2 public or private 6-2 diskette drive, PS/2 5.25-inch 9-15 public/private 3-3 diskette problems diskette 1 2-8 diskette 16 2-8 +---+ diskette 3 2-8 | E | diskette 6 2-8 +---+ diskettes, formatting 9-15 display adapter support EGA support 8-1 additional SVGA information 8-4 EGA, changing in WIN-OS/2 6-1 debuggers 8-9 EISA IRQ levels 7-1 dual displays 8-6 electronic support 1-1 laptop LCD or monochrome plasma Enhanced Editor 5-10 displays 8-6 environment for OS/2 2.0, SVGA 8-1 configured 6-1 WIN-OS/2 window and full-screen error message sessions 8-7 0X0401 error message 6-2 DISPLAY.DLL file 8-3 C00000005 (system message) 2-9 displays, dual 8-6 COUNTRY.SYS not found 2-9 DMA parallel ports 7-2 EC-00BF error message 2-9 DOS application programs SoftRIP Failure (HP COM_DIRECT_ACCESS 9-9 Paintjet) 7-4 COM_SELECT 9-9 SYS1200 error message 2-9 communication applications 9-11 Execjet Printer 7-4 DISKCACHE command 3-2 executable files 4-4 DOS property 9-9 performance considerations 3-2 DOS applications, shut down after +---+ installation 2-15 | F | DOS communication port, +---+ accessing 9-9 DOS property F-117A Stealth Fighter 2.0 5-10 COM_DIRECT_ACCESS 9-9 F19 5-10 COM_SELECT 9-9 Fastback DOS session needs to select one for Windows 5-10 communication port 9-9 Plus 2.1 and 3.04 5-10 X-4 Tips and Techniques FastLynx 1.1 5-10 +---+ FAT See file allocation table | G | fatal error 0X0401 6-2 +---+ fax adapter problems 9-14 file allocation table (FAT) file Gateway 2000 BIOS, early system version 2-12 memory considerations 3-1 graphics 8-6 typing commands 4-9 graphics support 8-1 file names 4-9 file systems fat allocation table file +---+ system 3-1 | H | high performance file system 3-1 +---+ memory considerations 3-1 performance 3-1 hard disk starting up 4-1 IDE=type is installed 2-11 swapper file 3-1 partition for HPFS 2-3 file, swapper 3-1 partitioning 2-3 files performance considerations 3-3 CONFIG.SYS file 4-3, 4-5 reformatting 2-2 executable, moving 4-8 removable Bernoulli drive 9-4 OS2.INI file 4-3, 4-5 space considerations 3-3 OS2SYS.INI file 4-3, 4-5 Harvard STARTUP.CMD file 4-1, 4-2, 4-3 Draw 5-11 Find Results folder 4-9 Graphics 5-11 finding objects 4-9 hDC FileApps 1.0 5-11 folder High Performance File System (HPFS) adding an OS/2 window 4-7 adding HPFS after changing default view 4-8 installation 2-3 changing icon title text 4-4 DOS and WIN-OS2 applications, Find Results 4-9 accessing 4-9 minimized window viewer 4-8 formatting a hard disk OS/2 System, not appearing 4-3 partition 2-3 Startup 4-1 memory requirements 2-3 fonts 8-7 partitioning 2-3 Form Publisher 5-10 support not added 2-3 formatting diskettes on non Micro HP mouse not working 2-5 Channel systems 9-15 HP mouse, installing 2-4 formatting the hard disk 2-2 HP New Wave 3.0 5-11 FormBase 1.2 5-10 HP Scanjet device support 9-7 FotoMan 5-11 HPFS See High Performance File Framework III 1.1 5-11 System Future Domain device driver 9-2 Future Domain SCSI Controller 2-7 Index X-5 +---+ installation problems (continued) | I | OAK adapter 2-6 +---+ OS/2 2.0 Limited Availability 2-2 I/O adapter 7-7 Phoenix BIOS, old version 2-10 IBM 3363 Optical Disk Drive 5-11 PS/2 P70 (COUNTRY.SYS) 2-9 IBM National Support Center Bulletin second disk drive not Board System 9-1 working 2-17 IBM PC LAN Support Program 5-11 SYS1200 (message) 2-9 IBM PC/3270 V2.0 5-12 SYS2025 (message) 2-10 IBMLink 9-1 SYS2027 (message) 2-10 icons 4-4 system error messages 2-8 changing color of title text 4-4 white screen 2-10 changing positions 4-4 ZEOS 2-13 creating for an application 4-5 installing not appearing 4-3 Bernoulli driver 9-6 recovering 4-4 CD-ROM 2-16 recovering icon positions 4-10 HP mouse 2-4 unclear 6-2 HPFS after installation 2-3 incorrect DOS version 4-9 local area network 2-15 installation problems non-IBM mouse 2-4 AMI BIOS, old version 2-10 OS/2 2.0 in a partition 2-3 applications did not response file 2-15 migrate 2-15 the upgrade version of OS/2 beeping (constant during diskette 2.0 2-1 changing) 2-9 Intel SatisFAXtion 5-12 C00000005 (system message) 2-9 interrupt levels, setting 9-12 COUNTRY.SYS not found 2-9 interrupt problems on an ISA disk light constant 2-10 system 9-8 diskette 1 2-8 Iomega support group telephone diskette 16 2-8 number 9-6 diskette 3 2-8 IRQ levels for printers 7-1 diskette 6 2-8 ISA IRQ levels 7-1 DOS and Windows, shut down after ISA systems, COM support 9-11 installation 2-15 ISA systems, interrupt problems 9-8 dual boot does not work (error message displayed) 2-9 dual boot does not work (no error +---+ message) 2-16 | K | dual boot in a partition with +---+ OS/2 1.3 2-17 EC=00BF (message) 2-9 King's Quest 5-13 Future Domain SCSI Controller 2-7 Gateway 2000, early BIOS 2-12 LAN 2-15 LOGO screen, at 2-6 Micronics system board, early BIOS 2-12 non-IBM computer with two drives 2-17 X-6 Tips and Techniques +---+ memory requirements (continued) | L | mininum 3-1 +---+ swapper file 3-1 messages LAN adapters 7-2 incorrect DOS version 4-9 LAN installation 2-15 metafiles 6-4 LAN Support Program Device Micro-Channel IRQ levels 7-1 Drivers 5-13 Micronics system board, early language configuration 6-2 BIOS 2-12 LANtastic microprocessor card, Aox add-in 9-8 version 4.0 5-14 MicroProse Civilization 5-17 version 4.1 5-14 Microsoft LapLink III 3.0 5-14 Bookshelf 5-17 Laplink Pro 5-14, 9-9 Chart 3.0 5-17 laptop displays 8-6 CodeView 5-17 LaserJet Printer 7-3 CodeView for Windows Version Limited Availability version of OS/2 3.0 5-18 2.0 2-2 Excel for DOS 2.1 5-18 local area network, installing 2-15 Excel for OS/2 3.0 5-18 Logitech mouse 9-8 Excel for Windows 3.0 5-18 Logitech mouse not working 2-5 Money 1.0 5-18 LOGO screen, installation MSCDEX 5-18 problems 2-6 Project for Windows 1.0 5-18 Lotus QuickC 5-18 1-2-3 for Windows 1.0 5-14 Windows 3.0 5-18 1-2-3 Release 3.1 5-14 Word 5-18 Freelance Graphics for OS/2 5-15 migrating applications Freelance Graphics for error following 6-2 Windows 5-15 in WIN-OS/2 full-screen 6-1 Magellan 2.0 5-15 migration did not work during Notes 5-15 installation 2-15 LPTx and LPTx.OS/2 ports 7-9 minimized objects 4-8 minimized window viewer 4-8 Mirrors III 5-19 +---+ monochrome displays 8-6 | M | More Windows 5-17 +---+ Mountain tape backup 9-8 mouse MAGICorp 5-16 changing a mouse driver 2-4 MAKEINI 4-5 installing an HP mouse 2-4 Mathcad Logitech 2-5 version 3.0 5-16 Logitech support 9-8 version 3.1 5-16 mouse button settings 6-2 memory problems on PS/2 model 90 or mouse not working 95 9-15 HP 2-5 memory requirements Logitech 2-5 application program usage 3-3 music adapters 7-2 file system recommendation 3-1 for HPFS 2-3 how to reduce usage 3-3 Index X-7 +---+ Paste Link choice and DDE 6-5 | N | pasting data from wrong program 6-4 +---+ pasting icons 6-4 PCM See personal computer National Geographics manufacturers Mammals 5-19 Peachtree Complete III 5.0 5-20 Presidents 5-19 Perform Pro 1.0 5-20 NEC printers 7-4 personal computer manufacturers Norton compatibility support 9-1 Backup 1.2 5-19 Personal System/2 Desktop 5-19 5.25-inch diskette drive 9-15 Utilities 5.0 5-19 model 90 or 95 9-15 not able to print 7-7 PerStore disk controllers 9-8 PFS First Choice 5-20 +---+ WindowWorks 1.75 5-20 | O | Phoenix BIOS, old version 2-10 +---+ Photostyler 5-20 PM Terminal Program 5-20 objects PostScript printer driver, changing icon title text 4-4 IBM4029 7-10 creating icon 4-5 preventing automatic startup for Find Results 4-9 programs 4-2 minimized window viewer 4-8 Print Manager, WIN-OS/2 session 7-9 Startup 4-1 print-data stream 7-8 offline printer, resending print printer cables 7-7 job 7-8 printer does not work properly 7-7 Orchid video adapters 8-5 printer prints slowly 7-7 OS/2 Support Line 1-1 printer stops printing 7-8 OS/2 System folder 4-3 printing OS/2 Window, adding to desktop 4029 Laser printer 7-10 menu 4-7 configuring devices 7-2 OS2.INI file 4-3 configuring your computer 7-1 OS2SYS.INI file 4-3 diagnosing printing problems 7-7 DMA parallel ports 7-2 hardware adapters 7-2 +---+ I/O adapter 7-7 | P | model considerations 7-2 +---+ network considerations 7-10 non-supported printers 7-5 PaintJet Printers 7-3 WIN-OS/2 considerations 7-9 PaintShow Plus 2.21 5-19 problem determination Paradise VGA Professional 8-1 AMI BIOS, old version 2-10 Paradox 3.5 5-20 applications did not parallel-port IRQ levels 7-1 migrate 2-15 parallel-port-attached devices 9-13 beeping (constant during diskette partitioning a hard disk for HPFS changing) 2-9 installation 2-3 C00000005 (system message) 2-9 partitioning for OS/2 2.0 2-3 COUNTRY.SYS not found 2-9 disk light constant 2-10 X-8 Tips and Techniques problem determination (continued) +---+ DOS and Windows, shut down after | R | installation 2-15 +---+ dual boot does not work (error message displayed) 2-9 real-mode WIN-OS/2 6-2 dual boot does not work (no error recovering icons 4-4 message) 2-16 reformatting the hard disk 2-2 dual boot in a partition with removable-media drives 9-4 OS/2 1.3 2-17 response file for 5.25-inch EC=00BF (message) 2-9 diskettes 2-15 Future Domain SCSI response file, installing 2-15 Controller 2-7 restoring desktop 4-5 Gateway 2000, early BIOS 2-12 Risk 5-21 LOGO screen, at 2-6 running Windows applications 6-1 Micronics system board, early BIOS 2-12 non-IBM computer with two +---+ drives 2-17 | S | OAK adapter 2-6 +---+ Phoenix BIOS, old version 2-10 PS/2 P70 (COUNTRY.SYS) 2-9 SantaFe Media Manager 5-21 second disk drive not SatisFAXtion, Intel 5-12 working 2-17 screen resynchronization 8-4 SYS1200 (message) 2-9 SCSI device support SYS2025 (message) 2-10 Adaptec and Future Domain 9-2 SYS2027 (message) 2-10 Always Technology adapters 9-6 system error messages 2-8 AMI SCSI adapters 9-6 white screen 2-10 Bernoulli 9-4 ZEOS 2-13 CD-ROM 9-3 ProCom disk adapter 9-2 problems, compatibility 9-4 Prodigy 9-1 ProCom and SCSI disk adapters program objects 4-1, 4-4, 4-8 (Micro Channel) 9-2 program-file objects 4-1, 4-4, 4-8 removable media 9-4 programs Seagate 9-4 disabling automatic startup 4-2 SyQest 9-4 error message 4-9 Western Digital 9-4 PS/2 5.25-inch diskette drive 9-15 second disk drive not working 2-17 Publishers PowerPak 2.1 5-20 serial adapters 7-2 service information 1-1 sessions, WIN-OS/2 window and full +---+ screen 8-7 | Q | Setboot (utility program for +---+ multiple operating systems) 2-17 settings view 4-8 Quattro Pro 3.0 5-20 SETUP.EXE 6-1 Quicken 5-20 sharing data Quicken for Windows 5-20 between WIN-OS/2 sessions 6-3 shell troubleshooting 4-1 Shredder 4-3 Index X-9 shutting down your computer 4-10 SVGADATA.PMI file 8-2 SideKick 5-21 SWAPPATH command 3-1 Signmaster 5.11 5-21 swapper file description 3-1 slow printing 7-7 SWAPPER.DAT file 3-1 Soft Term 5-21 SWINVGA.DRV file 8-4 sound adapters 7-2 SyQuest removable-media drives 9-4 SoundBlaster 5-21 System Editor and OS/2 2.0 Limited SoundBlaster adapter 7-2 Availability 2-2 Space Quest IV 5-21 SYSTEM.INI 6-2, 6-3 spooled job does not print 7-8 spooled job split into several files 7-9 +---+ SQLWindows 3.0 5-21 | T | Stacker 2.0 5-22 +---+ Star printer 7-5 starting applications 4-2 tabs not appearing 4-3 Startup folder 4-1 tape drives STARTUP.CMD 4-3 adapter or SCSI 9-7 STARTUP.CMD file 4-1, 4-2 Colorado jumbo 9-7 STB PowerGraph VGA 8-1 diskette based 9-7 super VGA (SVGA) 8-1 Mountain Tape Backup 9-8 support information 1-1 text clipped 8-6 Support Line, OS/2 1-1 The Way You Work 5-22 SVGA support TI chipsets 8-4 ATI 8-5 tree view 4-8 Boca Super VGA 8-1 Trident drivers 8-5 BVHSVGA.DLL file 8-3 troubleshooting description of 8-1 workplace shell problems 4-1 DISPLAY.DLL file 8-3 Tseng chipsets 8-4 list of adapters 8-1 Turbo Debugger 8-9 Orchid 8-5 turning off your computer 4-10 Orchid ProDesigner II 8-1 Paradise VGA Professional 8-1 SVGA.EXE file 8-3 +---+ SVGADATA.PMI file 8-2 | U | SWINVGA.DRV 8-4 +---+ TI chipsets 8-1, 8-4 Trident 8-5 unable to print 7-7 Trident chipsets 8-1, 8-4 UNDELETE, enabling 2-16 Trident TVGA 8-1 upgrading from DOS, Windows, and Tseng chipsets 8-1, 8-4 OS/2 2-1 utility program, SVGA on 8-2 VGA.DRV 8-4 VGAWONDER XL 8-1 video files 8-2 Video Seven VRAM II 8-1 VSVGA.SYS file 8-4 with an 8514/ULTRA adapter 8-6 SVGA.EXE 8-3 X-10 Tips and Techniques +---+ Windows (Microsoft) | V | shut down after +---+ installation 2-15 using version 3.1 2-15 VGA display, installation Windows applications problem 2-8 application considerations 3-2 VGA support 8-1 debugging 8-9 VGA Wonder XL Series 8-1 device drivers 6-1 VGA, changing in WIN-OS/2 6-1 high-resolution modes 6-1 VGA.DRV file 8-4 WIN-OS/2 windows sessions 6-1 video files, SVGA 8-2 Windows Multimedia Extensions 5-22 video graphics windows to desktop menu, adding 4-7 debugging 8-9 Windows Version 3.1 6-1 EGA support 8-1 Winfax Pro 5-22 SVGA adapters , list of 8-1 Wing Commander II 5-22 TI chipsets 8-1 WordPerfect Trident chipsets 8-1 for Windows 5-22 Tseng chipsets 8-1 Office 3.0 5-22 VGA support 8-1 Video Seven VRAM II 8-1 VIDEO_SWITCH_NOTIFICATION 6-2 +---+ mouse button settings 6-2 | X | view of folder, changing +---+ default 4-8 view, changing folder 4-8 XGA 6-2 virtual desktop 8-5 XGA, changing in WIN-OS/2 6-1 VSVGA.SYS file 8-4 Xtree Pro Gold 2.0 5-22 +---+ +---+ | W | | Z | +---+ +---+ white screen 2-10 ZEOS notebook 2-13 WIN-OS/2 bulletin boards 6-1 changing country settings 6-2 Clipboard and DDE 6-3 icons, unclear 6-2 language considerations 6-2 mouse button settings 6-2 mouse device drivers, changing 6-1 real-mode 6-2 running Windows programs 6-1 video device drivers, changing 6-1 window session 6-3 WIN-OS/2 window sessions 8-7 Index X-11 +++EDF002W DOCPROF tag found outside PROLOG. (Page 0 File: EFIQBASE SCRIPT) DSMMOM397I '.EDF#CNTX' WAS IMBEDDED AT LINE 39 OF 'EFIQBASE' DSMBEG323I STARTING PASS 2 OF 2. +++EDF002W DOCPROF tag found outside PROLOG. (Page 0 File: EFIQBASE SCRIPT) DSMMOM397I '.EDF#CNTX' WAS IMBEDDED AT LINE 39 OF 'EFIQBASE'