Appendix A - Troubleshooting
PMS8232 / PMS4232 Page
8
Appendix A - Troubleshooting
A Serial Utility Diskette is supplied with the PANACOM Technology adapter and will be used in the
troubleshooting procedures. By using this diskette and following these simple steps, most common
problems can be eliminated without the need to call Technical Support.
1.
Identify all I/O adapters currently installed in your system. This includes your on-board serial ports,
controller cards, sound cards etc. The I/O addresses used by these adapters, as well as the IRQ (if any)
should be identified.
2.
Configure your PANACOM Technology adapter so that there is no conflict with currently installed
adapters. No two adapters can occupy the same I/O address.
3.
Make sure the PANACOM Technology adapter is using a unique IRQ. While the PANACOM
Technology adapter does allow the sharing of IRQs, many other adapters (i.e. SCSI adapters & on-board
serial ports) do not. The IRQ is typically selected via an on-board header block. Refer to the section on
Card Setup for help in choosing an I/O address and IRQ.
4.
Make sure the PANACOM Technology adapter is securely installed in a motherboard slot.
5.
When running DOS, Windows 3.x or other operating systems refer to the Serial Utilities Disk 1 and the
User Manual to verify that the PANACOM Technology adapter is configured correctly. The supplied
software contains a diagnostic program 'SDOS' that runs under DOS and will verify if an adapter is
configured properly. This diagnostic program is written with the user in mind and is easy to use. Refer to
the README.txt file on the supplied diskette for detailed instructions on using 'SDOS'.
6.
For Windows 95/98 and Windows NT, the diagnostic tool 'WinSSD' is installed in the PANACOM
folder on the Start Menu during the setup process. First find the ports using the Device Manager, then use
'WinSSD' to verify that the ports are functional.
Always use the PANACOM Technology diagnostic software when troubleshooting a problem. This will
help eliminate any software issues and identify any hardware conflicts