Moxa Technologies RS-422, RS-485 user manual Windows NT system panic blue scr een

Troubleshooting

d.The board(s) is not plugged properly. Please make sure the board is seated firmly in the expansion slot.

e.The slot for plugging the board is defective.

In this case, please try other slots until you find a good one.

f.The board might be defective.

3.The COM number of the Industio CI-134 Ser ies conflicts with other s.

The COM numbers of different boards happen to be the same. Try to change the COM number mappings.

4.Windows NT system panic (blue scr een).

The possible reason is an IRQ or memory conflict with other ISA Bus adapters, like LAN and SCSI boards, or the system BIOS. Please refer to the corresponding problem in the previous section, “General Troubleshooting”, for solutions.

Windows 95/98

This section is specific for troubleshooting under Windows 95/98. For general problems and solutions, please see the previous section, “General Troubleshooting”.

1. The system fails to find the Industio CI-134 Ser ies boar d! After system r eboot, er r or message " CI-134 Ser ies (CAP=0x0180, por t 1=COM3): Boar d is not found" appear s.

a.Some partial decoded network board may interfere with our board. Please avoid from using 0x300 as I/O address for those network boards.

b.Check hardware configuration of CI-134 Series board by IO-IRQ.EXE. Then make sure the hardware configuration, including I/O addresses for each port, Interrupt Vector, IRQ, is identical to that of the driver.

c.The I/O addresses may conflict with other devices, please change another set of I/O address such as I/O:0x280, Interrupt Vector:0x2C0.

d.The board(s) is not plugged properly. Please make sure the board is seated firmly in the expansion slot.

e.The slot for plugging the board is defective.

In this case, please try other slots until you find a good one.

f.The board might be defective.

Industio CI-134 Series User’s Manual 6-5