OSMKCM04 - COMMON PROBLEMS AND SOLUTIONS FOR OS/2 2.1 AND OS/2 2.11 01/30/96 ======================================================================= Common Problems and Solutions for OS/2 2.1 and OS/2 2.11 ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION * SYS1201 driver not installed. * An IRQ conflict exists or hardware is set up incorrectly. * Cannot open a DOS or Windows application. * Error messages received: - SYS3175 and SYS3176 - SYS0049 - SYS0099 or SYS1798 * Application does not recognize COM port. * MODE command causes session to lock up. RESOLUTION Note: Make sure you have the latest COM.SYS and VCOM.SYS installed. SYS1201 Driver Not Installed ---------------------------- This error can be caused by a number of problems: * The PATH statement for the driver in the CONFIG.SYS file might be incorrect. * When COM.SYS can't be installed: - Physical ports might not exist. - Physical ports are not configured correctly in BIOS (check configuration for Micro Channel architecture). - Physical ports might be defective or incorrectly set up. - The driver specified is defective or does not exist. IRQ Conflict or Incorrect Hardware Setup ---------------------------------------- IRQ conflicts can cause many problems. They can result in problems unrelated to the immediate point of conflict. You can eliminate IRQ conflicts by creating a table with rows that represent each slot of the system, and columns that represent the "Card Type," "IRQ Level," "I/O Address," "DMA Address," and "Mfgr. Info." Change this information as the configuration changes to save time and ensure configuration integrity. Use the documentation that came with the adapter for the switch settings. Each adapter must be assigned to a unique IRQ level and I/O port address. DMA addresses also should be unique. Cannot Open a DOS or Windows Application ---------------------------------------- 1. Make sure the latest communications drivers are installed. 2. Make sure the application is installed correctly: * Path commands might be incorrect. * Applications installed under real DOS might need to be reinstalled under OS/2. SYS3175 and SYS3176 ------------------- * If the application is an OS/2 application, contact the vendor of the application. * Sometimes adjusting DOS_HIGH and DOS_UMB fixes the problem. * Running the application in full-screen helps. * Slowing down the processor and disabling external cache on faster computers also helps. * Check the databases for problems reported for specific applications and these error messages. SYS0049 ------- This message usually indicates a non-functioning attached device. Use the MODE command to check if the port is installed correctly. If the MODE command works correctly, use the spurious interrupt that is passed on the command line of the COM.SYS device driver in the CONFIG.SYS file. Make sure the hardware is set up correctly and functioning optimally. SYS0099 or SYS1798 ------------------ These messages usually mean the port requested is being accessed by another application. Some applications automatically take all available system resources. If the problem occurs, view the task list and note applications that are running. Verify that these applications are not, or should not be, using the port. OS/2 provides a DOS property in the DOS settings to hide COM ports from applications. Set the COM_SELECT property to None or to the specific port being used; for example, COM_SELECT = COM1. Application Does Not Recognize COM Port --------------------------------------- * Check for an IRQ conflict. * Make sure the application port and line settings are set up correctly. * If using COM3 and COM4, or COM1 and COM2, with other than default settings on an ISA system, check the following: - Verify the command-line parameters of the COM.SYS device driver in the CONFIG.SYS file are correct. - For Microsoft Windows applications, make sure the Windows port setup is correct. MODE Command Causes Session to Lock Up -------------------------------------- This problem can be caused by IRQ conflicts. See "IRQ Conflict or incorrect Hardware Setup." Also, check other databases for similar problems reported. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.