Measurement Computing PCI-COM422/485 - Manual (Page 21)

17
6. TROUBLESHOOTING Q/A:
1) The system was working before I rebooted and now no longer works.
The main issue with detecting the PCI-COM hardware involves the system-assigned base address. The PCI-
COM board relies on the Plug-and-Play capabilities of the system BIOS to assign the base address for the COM
ports. When new hardware is added to the machine, the entire system is reconfigured. This might affect the
addresses assigned to the PCI-COM board and hence where the system detects the board. The easiest way to
deal with this issue is to go into the Device Manager and delete the “PCI-COM…” entry under the “Multi-
Function” node and reboot the system. This will force the system to reconfigure the PCI-COM board. After the
machine has rebooted, go back into the Ports entry under the Device Manager and configure the Advanced
settings. This forces the system to write the new settings to the registry. If you installed the ComSet32.exe
application in the Startup folder, the new configuration is restored after each reboot.
2) I cannot configure an internal modem under Windows NT.
The PCI-COM installation replaces the standard Windows NT Serial.sys device driver with a modified driver
that supports the PCI-COM family of boards. The modified driver will work for any of the boards in the PCI-
COM family as well as the internal COM1 and COM2 ports. However, there is an issue with the system being
able to detect internal modems. This appears to be a resource-related issue with the current implementation of
the modified serial device driver. Until this issue is resolved, internal modems are not supported on machines
with PCI-COM boards.