Table of Contents
Advertisement
Appendix C
Troubleshooting and Common Questions
I installed or uninstalled NI-Serial software for Windows NT, and
NI Ports no longer supports the serial device server devices or is
missing. What should I do?
NI Ports is a shared utility with both NI-Serial (PCI, AT,
(Windows NT only)
and PCMCIA products) and NI-Serial server (serial device server
products). The most current version of NI Ports must be installed to support
both product lines. To restore NI Ports, reinstall the NI-Serial device server
software as described in Chapter 2, Installation. You do not need to
reinstall the serial device server devices, as their configuration information
should be intact.
Can I use the serial device server with older Win16 serial applications?
Yes, if the application uses standard Win16 API function calls. While the
serial device server uses the Win32 API, Windows automatically translates
the Win16 API calls into Win32 API calls with Windows On Windows
(WOW). As a result, Win16 applications running in a Win32 environment
can use the serial device server.
Can I use the serial device server with DOS serial applications?
No. Because the serial device server driver uses the Windows API, DOS
serial applications will not work. DOS understands only that COM1 is
mapped to base address 3f8, COM2 is mapped to 2f8, and so on. Because
no physical memory addresses are associated with serial device server
ports, DOS serial applications are unable to access the serial device server.
I powered off my serial device server before recording the flashing
PWD/RDY LED pattern. What should I do?
Try to duplicate the error before calling National Instruments for
assistance. Recording the PWR/RDY LED pattern is not critical to the
operation of your serial device server, but it saves you time and helps
National Instruments to diagnose the problem quickly and accurately.
Why does NI Ethernet device configuration list my box as
*BUSY*
when I know my network uses DHCP?
For up to one minute, the serial device server attempts to retrieve network
parameters from a DHCP server. During this time,
appears in the
*BUSY*
utility display. If this status does not change, there are several reasons why
DHCP may fail to respond. One of the most likely reasons is that your
subnet has no more available addresses to assign using DHCP. Please
consult your network administrator to determine the specific reason for the
problem.
© National Instruments Corporation
C-13
ENET-232 and ENET-485 Series User Manual
Advertisement
Table of Contents
