NI-488 doesn't install for GPIB-USB-B....

[fphart]

After the spectacular go-around on getting Matlab R2006 to work with LabView 7.1 (thread here: http://forums.ni.com/ni/board/message?board.id=170&message.id=209977&query.id=100502#M209977), I'm back.  One of the steps in investigating that problem (but not what ultimately solved it) was to have LabView 7.1 completely re-installed on the pc.  That installation was under the control of our IT folks (site license), but the installation of the NI 488 drivers was left to me.  I have attempted to install, uninstall, and re-install the NI-488.2 (version 2.4) drivers (with VISA 3.2) twice now with no luck. 

The problem occurs after reboot at the time of detection of the GPIB-USB-B device, where I am getting error code 37 from the Windows New Hardware Plug-N-Play dialog.  Short of the wholesale removal of registry keys -- which I believe would force yet another a re-install of LabView that I wish to avoid since it involves the IT folks -- I have followed all of the advice in this thread to no avail:
http://forums.ni.com/ni/board/message?board.id=140&message.id=18898&view=by_date_ascending&page=1

Does anybody have any ideas here?

One of the annoying parts of this for me is that I did have the NI-488 drivers working with LabView 7.1.1 (the prior LabView installation) before I ran into the Matlab R2006a interoperability buzzsaw.  Talk about one step forward and two back!

[fphart]

Update: I applied the updates to bring LabView up to version 7.1.1 (and the Matlab scriptnodes still work!).  Then I tried installing the NI-488.2 (v 2.4) drivers again, and got the same result I reported above:  At the time of initialization of the hardware, the "Found New Hardware Wizard" reports that "Windows cannot initialize the device driver for this hardware. (Code 37)" 

Any suggestions -- short of a LabView re-install -- will be appreciated.  If I have to go back to another re-installation for this, I think I'll find an alternative way to control my instruments that doesn't involve LabView...

[fphart]

More info, FWIW:  After the failed initialization message, if I click on the NI-488.2 troubleshooting wizard, I get the following message:
"
The NI-488.2 Software for Windows is not correctly installed on your system.  Please follow these steps:

1. Restart your system.
2. Reinstall the NI-488.2 Software for Windows
3. Run the Troubleshooting Wizard again.
"
Of course, I've done all that once already....

[Angela M]

Hello fphart,

I do not think that the problem you are seeing has anything to do with LabVIEW, so re-installing LabVIEW should not be necessary.  As I am sure you have noticed, once an installation has been corrupted it becomes increasingly difficult to uninstall/re-install properly.  When uninstalling, we would hope that all corrupt files have been removed, but the corruption can prevent this from happening.  I see from your other threads that this is a Windows XP system and you do have administrator rights, I will restate that here for reference.

When uninstalling the driver, there are some dlls that may remain in the \Windows\System32 folder.  They will be labeled as GPIB and the author will be National Instruments.  After uninstalling, make sure to remove these dlls before attempting a reinstall.  If it is not clearly a GPIB related dll from National Instruments, do not delete the file.  Between each step reboot the computer and make sure that the hardware is not connected.  I hope this helps!  Let us know if you continue to have trouble.

Regards,
Angela
Applications Engineer

[Ray.R]

Actually, I had a similar problem back in 2002.

The problem was not directly related to LV, which was LV6.1 at the time. 

We used a USB-GPIB  adapter, which was not-so-easy to get going.   The solution was to obtain newer drivers from NI and it solved the issues.

It's been a long while... but once we got the GPIB-driver & USB adapter matched up, it worked.

And yes, we had to completely uninstall (full delete) of earlier USB-GPIB drivers.  Anything residual was a headache...

RayR 

Message Edited by JoeLabView on 10-24-2006 02:47 PM

[Ray.R]

One thing I forgot to mention is that it was USB-1 back in those days.  I think we were running Win-2K.