Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

unable to access ni-488.2m driver for windows 95 (gpibmngr.dll)

I wrote software to control an HP scalar network analyzer in windows 95, and it works fine. However, in trying to get the same software to run in windows 2000, I get an error: "unable to access ni-488.2m driver for windows 95 (gpibmngr.dll)" whenever I perform an action involving the GPIB interface (programming the SNA/grabbing data -- for example, when using the "Send()" proceedure in vbib-32.bas). The error box is titled "gpib-32.dll" I cannot determine why the drivers are having these problems in windows 2000.
0 Kudos
Message 1 of 4
(3,804 Views)
Hello-

Be sure to use an ibonl(ud,0) to take all unit descriptors offline before closing a program. Also be sure the GPIB card is functioning. After making sure you have the latest driver from (http://www.ni.com/support/gpib/versions.htm), the first step in determining the functionality of your GPIB card is to run the "Getting Started Wizard" found in Start/Programs/National Instruments/NI-488.2.

If the Getting Started Wizard Fails:
-Read the instructions on that utility.
-If you are using a PCI card, try switching slots.
-In Windows NT, you may want to verify your setup in Control Panel/GPIB. In this dialog, click GPIB0 and click "Board Type". Be sure that the board matches what is installed in your system. If you can't see the serial number see K
B#1N88Q5RM (http://digital.ni.com/public.nsf/websearch?SearchView&Query=1N88Q5RM)
-In other versions of Windows, you should be able to see the GPIB interface in the "Device Manager".

The next step is to communicate with the instrument in the Measurement & Automation Explorer (MAX). In MAX under "Devices and Interfaces" you should be able to find your card. Right-click and do a "Scan for Instruments".

If the scan fails:
-Be sure the instrument is powered on and online.
-Be sure the cable is connected tight and screwed on.
-Try switching cables. Shorter cables are preferred.
-If using multiple instruments, try communicating to one instrument at a time.

Randy Solomonson
Application Engineer
National Instruments
0 Kudos
Message 2 of 4
(3,804 Views)
Your answer was ineffective. My problem does not arise when I close the program, but when I am using it and attempt to communicate with the instrument. I will attach a picture of the error message, and you can see it arises after I press the "Initialize" button which attempts to send information to the instrument my GPIB card is connected to. This software DOES work in Windows 95, why not in Windows 2000?
0 Kudos
Message 3 of 4
(3,804 Views)
I found an issue very similar to this. Another customer had this problem when gpibmngr.dll somehow was deleted from his system folder. Reinstalling the latest driver from here solved the problem:

http://www.ni.com/support/gpib/versions.htm
0 Kudos
Message 4 of 4
(3,804 Views)