Grabbing Problems - Matrox Meteor-II /Digital Installation And Hardware Reference

Table of Contents

Advertisement

46
Appendix A: Troubleshooting
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
Not enough memory to allocate buffer under
Windows NT 4.0
This is the message that you will receive if you try to allocate
a grab buffer that is greater than the amount of DMA memory
specified during software installation. This problem can be
addressed by changing the amount of DMA memory on your
computer. Re-allocate DMA memory using the included
milconfig.exe utility. Alternatively, uninstall and reinstall MIL
and specify the appropriate amount of DMA memory.

Grabbing Problems

The trigger pulse is not being sent
This happens when the opto-isolated trigger pulse is not
connected. When using the opto-isolated trigger, both
OPTOTRIG- and OPTOTRIG+ signals must be connected.
OPTOTRIG- is usually connected to the ground of the trigger
source.
IRQ conflicts
In general, PCI devices can share an interrupt line (IRQ).
However, sometimes this might not be possible. One type of
difficulty that you might run into is as follows:
IRQ conflict under Windows NT 4.0
In the event that your Matrox Imaging board(s) cannot share
an IRQ line with other devices, allocate a different IRQ to
each device in the IRQ Configuration Setup section of the
BIOS Setup Program (accessible on bootup), if possible.
IRQ conflict under Windows 2000
To resolve this problem, re-assign a different IRQ line to the
PCI slot in which the Matrox Meteor-II board is installed.
Note that PCI devices cannot share interrupt lines with EISA
or ISA devices.
Other possible solutions to the above problem:
Move the Matrox Meteor-II board to another (free) PCI slot.
Swap Matrox Meteor-II with another board, by switching PCI
slots.

Advertisement

Table of Contents
loading

Table of Contents