Troubleshooting |
Windows NT
This section is specifically for troubleshooting problems for Windows NT. For general problems and solutions, see the previous section, “General Troubleshooting.”
1.After the system reboots, the error message “Another driver in the system, which did not report its resources, has already claimed the interrupt used by xxx.” appears in the Event Log.
This indicates the MOXA board was found, but the IRQ is conflicting with another adapter. Check the PCI BIOS IRQ settings first and then select an IRQ that is available.
2.After the system reboots, the error message “Cannot find any configured MOXA Smartio/Industio Series board!” appears in the Event Log.
Make sure the PCI board is seated firmly in the expansion slot.
3.The COM number of the CP-102U/UL Series conflicts with others.
The COM numbers of different boards happen to be the same. Try changing the COM number mappings.
4.Windows NT system panic (blue screen).
This could be caused by an IRQ or memory conflict with other ISA Bus adapters, such as LAN and SCSI boards, or the system BIOS. Refer to the corresponding problem in the previous section, “General Troubleshooting,” for possible solutions.
Windows 95/98
This section is specifically for troubleshooting under Windows 95/98. For general problems and solutions, see the previous section, “General Troubleshooting.”
1.The system fails to find the
2.The slot the boards are plugged into is defective. Try another slot until you find one that works.
The board might be defective.
3. After the system reboots, the error message
This indicates that the MOXA board was found, but the IRQ conflicts with another adapter. Make sure the MOXA board’s IRQ does not conflict with other adapters’ IRQ. Check the PCI BIOS IRQ settings and select an available IRQ for MOXA boards.