OSMKCM04 - COMMON PROBLEMS AND SOLUTUIONS 10/13/94 ================================================================ COMMON PROBLEMS AND SOLUTUIONS ================================================================ Please Read Entire Document for Full Explanation of Procedures ---------------------------------------------------------------- NOTE: Make sure you have the latest COM.SYS and VCOM.SYS installed. SYMPTOMS: 1. SYS1201 driver not installed 2. "COM port not available" or "IRQ not available" 3. Can not open a DOS or Windows application. 4. SYS3175 and SYS3176 5. SYS0049 6. SYS0099 or SYS1798 7. Application does not recognize COM port 8. Mode command causes session to hang RESOLUTIONS: 1. Path statements & physical devices 2. IRQ conflict or incorrect hardware configuration 3. Check path commands 4. DOS settings and APARS. 5. An attached device problem 6. The port is being used by another application 7. Application settings, configuration 8. IRQ conflict or APAR RESOLUTION: 1. SYS1201 driver not installed error can be caused by a number of problems. - The path statement for the driver in the CONFIG.SYS file may be incorrect. A. When COM.SYS does not install: - Physical ports may not exist. - Physical ports are not configured correctly in bios (reference configuration for MCA) . - Physical ports may be defective or incorrectly setup. - The driver specified is defective or non existant. 2. IRQ conflict or incorrect hardware configuration 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 rows represent each slot of the machine and columns that columns represent the "Card Type" "IRQ Level" "I/O Address" "DMA Address" "Manufacturer Info". Change this information as the configuration changes to save time and ensures 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 address' should also be unique. 3. Can not open a DOS or Windows application. - Make sure that the latest communications drivers are installed. - Make sure the application is installed correctly. A. Path commands may be incorrect. B. Applications installed under real DOS may need to be reinstalled under OS/2. 4. SYS3175 and SYS3176 - If the application is an OS/2 application, contact the vendor of the application. - Sometimes adjusting the DOS_HIGH and DOS_UMB adjustments remedy this problem. - Running the application in full screen helps. - Slowing down the processor and disabling external cache on faster machines also helps. - XR6200 includes fixes for computers with Pentium, DX, processors with this problem. Check for current APARS listed for specific applications and the error message. 5. SYS0049 Usually indicates a non-functioning attached device. Use the MODE command to check if the port is installed correctly. If the mode command functions correctly, use the use the "spurious interrupt" that is passed on the command line of the COM.SYS device driver in the CONFIG.SYS. Make sure the hardware is configured correctly and functioning optimally. 6. SYS0099 or SYS1798 Usually means 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, use 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 the specific port being used; for example, COM_SELECT = COM1. 7. Application does not recognize COM port - Check for an IRQ conflict. - Make sure the application port and line settings are configured correctly. - If using COM3 and COM4 or COM1 and COM2 with non- default configuration settings on an ISA machine, check the following: A. Verify the command line parameters on the COM.SYS device driver in the CONFIG.SYS file are correct. - For MS Windows applications make sure the Windows port setup is correct. 8. Mode command causes session to hang - Can be caused by IRQ conflicts (see sections on IRQ conflict and resolution). - Check the APAR data base. There may be situations where defective hardware had in similar results. ---------------------------------------------------------------- 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.