Error "Unable to Access NI-488.2 Driver for Windows 95 (gpibmngr.dll)"

Updated Jun 4, 2019

Reported In

Driver

  • NI-488.2

Operating System

  • Windows

Issue Details

I get the error "Unable to Access NI-488.2m Driver for Windows 95 (gpibmngr.dll)" when I run my application, executable or the Getting Started Wizard. I am using Windows 2000 or later, why am I getting this error?

Solution

National Instruments drivers no longer use the gpibmngr.dll.  That error message indicates one of the following:

  • A copy of the old GPIB dll from Win 95/98 that referenced gpibmgr.dll was included in a project, like Visual C++ project.  So when the app is compiled and run, it uses the wrong dll.
  • The operating system was upgraded from Win 95/98 to Windows 2000/NT/XP,
    instead of a format and install of the new operating system.
  • A copy of an old GPIB dll is on your computer and is not being deleted or replaced.

If you have the source code:

  1. If you get the error when you compile and run a project, check to see if the project or any of the project's folders contain a GPIB dll. If you find any GPIB dlls, remove them and recompile the application.
  2. In Device Manager, uninstall your GPIB card.
  3. In Add/Remove programs, delete NI-488.2. Note: Depending on the version of NI-488.2 you have installed, it may be located in the NI Software folder.
  4. If you have LabVIEW 6.02 or earlier on your machine, remove it.
  5. Go to Start»Search»For Files or Folders and type in gpib*.dll. Delete any versions you find.
  6. Reboot and cancel out any "Found New Hardware Popups."
  7. Install LabVIEW 6.02 or earlier if you previously uninstalled it. Do a custom install, click on the drivers folder, and select "This feature will not be installed."
  8. Install the Current version of NI-488.2  for your GPIB interface and operations system.
  9. Reboot

For executables:

  1. Find an older version of NI 488.2 that is compatible with your hardware and includes the gpibmngr.dll (versions prior to 2003)
  2. Install that version onto your computer
  3. Reboot