this section is specific for troubleshooting under windows nt. for general problems and solutions, please 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 conflicts 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 smartio cp-168u board (bus no=x, dev no=x, port1=comx), with device number xx, conflicts with others.

    the com numbers for different boards are in conflict. change the com number mappings for the moxa boards.

    4. windows nt system panics (blue screen).

    the possible reason is an irq or i/o address conflict with other isa bus adapters, such as lan or scsi boards, or with the system bios. refer to the corresponding problem in the previous section, “general troubleshooting,” for solutions.