Failing to detect NI PCI 1422

[GavinV]

I have been experiencing a unique problem with the NI PCI 1422 board. After the first install, everything runs fine. However, after some period of operation, errors appear. Then if the board is ever physically removed from the PC, it will never be detected again.

I am running Windows 2000 Pro, on a AMD XP2100+ with 512Mb PC2700 DDR, and have tried several different motherboards. When you replace the motherboard, the card will be detected but only the first time the system is booted up. From then on it is non-existent. I have tried reinstalling everything, flashing the bios, reinstalling from a drive image where it works etc.

I have built an identical system that works fine. I am fairly sure the framegrabber is not faulty, as I have tr
ied replacing that also (to no avail).

Anyone got any suggestions?

[nestor-sg]

What do you mean not detected? Is it not detected in the Windows Device Manager or in MAX? If it is not detected in Device Manager then you should check that computer BIOS and make sure PnP is enabled and PCI Bus Mastering as well. If it is not detected in MAX try hitting F5 (refresh).

What version of the driver do you have? I suggest you have the latest one, 2.5.5.

If Device Manager does recognizes the board you may want to uninstall it from there and then click the refresh button inside Device Manager as well. And see if that recognizes the hardware.

Nestor.

[GavinV]

It is not detected in Device Manager. PnP is enabled, as is PCI Bus Mastering. I can plug any other board I have into the PC without any problems. The NI board works fine in other machines.

I have driver version 2.5.3

My company is now seeing this problem in a number of our customers PCs. They are all using AMD XP processors, and I think the same chipsets (although there are a range of m'boards being used, from Asus to Gigabyte to Epox). The problem starts with an IMG ERR being reported, and then the framegrabber does it's disappearing trick.

We are not doing anything special with the hardware, so I'm surprised that this problem has not been previously reported.