
Appendix B
Troubleshooting
© National Instruments Corporation
B-5
VXI-AT2000/NI-VXI MS-DOS Getting Started
Note:
If you have changed your Master Window address range, use it instead of the
default range (D000 to DFFF) in the following examples.
If you are using EMM386, which is included with MS-DOS, prevent it from using the default
Master Window address range by editing the
CONFIG.SYS
file and appending the flag
X=D000-DFFF
to the line
DEVICE=EMM386.EXE
.
If you are using QEMM386 from Quarterdeck, prevent it from using the default Master Window
address range by editing the
CONFIG.SYS
file and appending the flag
X=D000-DFFF
to the
line
DEVICE=QEMM386.SYS
.
If you are using 386MAX from Qualitas, prevent it from using the default Master Window
address range by editing the
386MAX.PRO
file located in the
386MAX
directory, and inserting
the line
RAM=D000-DFFF
.
If you are using any other expanded-memory manager, refer to its documentation to learn how to
prevent it from using the default Master Window address range of D000h to DFFFh.
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,
VXIEDIT
or
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, save the changes, and
run
VXIINIT
.
Problems with MXIbus Cable
If you have verified that you do not have a conflict with any of the AT-MXI configuration
settings, your problem might be with the MXIbus cables in your system.
The following symptoms can indicate a problem with the MXIbus cable.
•
RESMAN
finds the AT-MXI board at Logical Address 0 but does not detect the VXI/VME
chassis.
•
RESMAN
previously worked, but now produces errors.