I installed the latest PCI-GPIB driver for Windows Server 2003 and now the card is no longer detected.

[Mike@ClariPhy]

As a result of installing the latest driver we've not only lost visibility to the card but now the NI software will not launch either. We went from PCI-GPIB driver ver 2.5.2.1 to 2.8.1 (for Windows Server 2003) and now have lost the ability to communicate with our programmable hardware.

History:

The driver update was ptompted by the card not being "fully" recognized at system startup (a new system BTW), i.e. the card was listed in device manager w/o any conflicts (!)  but was not seen by any software using the card including the NI Troubleshooting Utility (if the test for the card was run it would FAIL);

Current Device Manager Status:

Shows Conflict (because it cant load the driver)

Next Troubleshooting Steps:

I next will try falling back to the driver version we had originally. However, I am surprised the software is now none functional.

Questions:

Has anyone run into this problem? Is Windows Server 2003 an odd combination to be running with an NI PCI-GPIB card?

The system:

DEll: Inspiron Desktop 570, Pentium 4 Prescott DT, 3.8GHZ, 1 MEGB, 800FSB

OS: Windows Server 2003, SP2

NI card: PCI-GPIB

[Julianne_K]

Hello, 

1) Uninstall and reinstall the 488.2 driver, ensure that the computer is restarted. 

2) Download the most recent version of NI-VISA. The download can be found here.

Unfortunately, error code 39 is often related to either driver conflicts (in the past, there have been conflicts with Agilent drivers), or is related to a registry corruption. Let me know if the above two suggestions, or downgrading your drivers, correct the issue. Thanks,