12
© Sealevel Systems, Inc. 7104 Manual | SL9051 7/2021
Appendix A
–
Troubleshooting
Sealevel Software is supplied with the Sealevel Systems adapter and may be used in the troubleshooting
procedures. Using this software and following these simple steps can eliminate most common problems
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 Sealevel Systems 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 Sealevel Systems adapter is using a unique IRQ. While the Sealevel Systems 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 by the BIOS or Operating system. Some BIOS setup software
will allow changing the IRQ, but others do not. Another method of changing assigned resources is
to try changing PCI slots. This will typically cause the BIOS or OS to reassign the resources.
4.
Make sure the Sealevel Systems adapter is securely installed in a motherboard slot.
5.
When running DOS or Windows 3.x refer to the Sealevel Software and this User Manual to verify
that the Sealevel Systems adapter is configured correctly. This software contains a diagnostic
program ‘SSD’
that will verify if an adapter is configured properly. This diagnostic program is written
with the user in mind and is easy to use. Make sure that if available, the ‘Use Plug
-n-
Play” option is
turned
‘OFF’
in your BIOS. Having this option set to
‘ON
’ in DOS or Windows 3.x will cause erratic
operations.
6.
WinSSD is available as a standalone utility and is included with Sealevel’s SeaCOM, SeaLINK and
SeaMAC software suites
7.
Remember that a loopback test is not
possible with the ‘NE’ switch turned on.
8.
Always use the Sealevel Systems diagnostic software when troubleshooting a problem. This will
eliminate any software issues from the equation.
