Memory Area Used By Another Device; Problems With Mouse - National Instruments VXI-AT2022 Getting Started

Troubleshooting
A conflict in the Master Window of the AT-MXI can cause resman to behave erratically. The
following are likely symptoms of a conflict in the Master Window configuration.
• The resman display shows multiple devices at Logical Address 0. (The AT-MXI should be
the only device at Logical Address 0.)
• resman detects nonexistent devices.
• The computer hangs when you run resman.
The following paragraphs discuss the two main causes of a Master Window Base Address
conflict.

Memory Area Used by Another Device

Your system may contain a device that already occupies all or some of the upper memory area
that is allocated for the Master Window.
To solve this problem, first determine what area of upper memory your devices use. Then move
either your device or the Master Window Base Address to an unused area of upper memory.
If you have a Super VGA monitor, your system is likely to use video RAM. Generally, any
video RAM used by your PC AT occupies all or some of the upper memory from A000h to
BFFFh. If you have Ethernet networking cards, be aware that many of them occupy upper
memory. Many Ethernet cards have an upper memory base address of D000h or E000h.

Problems with Mouse

If you notice your mouse behaving erratically after you run vxiinit, the problem is most
likely an interrupt conflict. As stated earlier, the AT-MXI requires one interrupt line that it
cannot share with another device in the system.
To correct an interrupt conflict, first verify that the AT-MXI board interrupt level (set by a
jumper) matches the software setting in the Logical Address Configuration Editor of the VXI
resource editor program, vxitedit. Then determine if any other devices are configured to use
the AT-MXI interrupt level. The default AT-MXI interrupt level is 12.
If there is a conflict, move either the conflicting device or the AT-MXI to a different interrupt
level. If you decide to change the AT-MXI interrupt level, you must change the interrupt jumper
hardware setting, enter the new interrupt level in the Configuration Editor, and save the changes.
Also, you will have to reinstall the NI-VXI driver and specify the new interrupt level in the
installation procedure to match the hardware setting. Reboot the system to make the changes
take effect. Refer to the Installing the Software section in Chapter 3 for more details.
VXI-AT2022/NI-VXI SCO UNIX Getting Started B-4 © National Instruments Corporation
Appendix B