02-28-2009 11:03 AM
03-02-2009 03:53 PM
Thanks for the info and the solution! I'll try to relay this information to the appropriate people so that we can include this information somewhere.
08-13-2009 10:02 PM
Thanks for the info. I think this is what is happening to my laptop and USB-GPIB-HS. We have totally wiped out NI's software (cleaned with msiblast and msicuu and deleted all NI Registry and folders). We didn't look to see what files were left with in the System32 file. Also we wer getting the Software error from the NI-488.2 Troubleshooting Wizard and no indication from the installers that is a problem. Initially our issue was caused by (I think) iTunes version 8 having the Bonjour Service's mDNS Responder running during the install of a LV Built Custom Installer that carried NI-488.2 2.6. We got the error (see attached picture) "The NI mDNSResponder 1.0.0 installation failed with the following error: Internal Error 2753. nimdnsNSPTool.exe.MDNS01 Continue?" We think was the cause of the original corruption.
After we uninstalled iTunes and the Bonjour service we were able to install with NO ERRORS. But MAX couldn't see the device (found by Device Manager alright). This was all after several "cleanings" as directed by NI. But we will check to delete the GPIB-32.dll after a clean uninstall. The NI Installer should really overwrite this.
I will post if this is solved our issue.
08-18-2009 01:32 AM
SOLVED IT!! Had to delete the GPIB*.dlls from the system32. There were about 6 dlls that I had to delete. I don't if they had been left behind during the original installer crash or not. But a uinstall/re-install (even with NI's cleanup information) didn't resolve the issue. I HAD to delete the Dlls manually after a complete clean up (registry folders,etc) after a normal uninstall.
05-10-2012 03:25 AM
You save my day.
I've installed the NI-488.2 GPIB Drivers packet 3.0.2 for Windows 7 64-bit. With the Measurement & Automation application I've could connect to the GPIB-PCI board and also to my instrument (an electric loads in my case). Then I've started the GPIB Troubleshooting Utility but the tests had failed.
So I've reinstalled the software, use an older version and an other board with the same result.
After one day with blood, sweat and tears I've read your post. And yes and GPIB-32.dll from an other company reside in the system32 folder.
Delete file, reinstall NI-488.2 GPIB Drivers packet, run GPIB Troubleshooting Utility, be happy.
And so I repeat Jojis statement three years later: "The NI Installer should really overwrite this."