Labview hangs on start, Matlab 6.5.1 doesn't load after update to NI-IMAQ313.

[Daniel_78]

An update to NI-IMAQ313 was necessary because of a problem with the camera file for a DALSA2M30. I got the message "camera file is damaged".
After installing this update Labview hangs on start up of a Labview 6.1 VI using Matlab script.  The Matlab application doesn't start as well. Matlab 6.5.1 is installed on a Windows 2000 machine.

[ThSa]

I think it's not a problem with Matlab or the Matlab script.

Have you read the readme of the IMAQ 3.1.3 before?

Here is a short excerpt:

WINDOWS 2000 ISSUES

If you are using Windows 2000, installing an IMAQ device prior to installing the NI-IMAQ driver software causes the IMAQ device to appear in the Device Manager as a PCI Multimedia Video Device.  This situation prevents the driver software from working properly.

Complete the following steps to correct this situation:

1) If you have not already installed the NI-IMAQ driver software, install it now.

2) Select System from the Control Panel, select the Hardware tab, and then click the Device Manager button.

3) In the Other Devices section of the Device Manager, right-click the PCI Multimedia Video Device and select Uninstall.

4) In the Device Manager, select Action»Scan for hardware changes. The system now recognizes the IMAQ device.

5) Restart the computer before using the IMAQ device.

Which driver version have you installed before?

redards,

Thomas Sandrisser

[Daniel_78]

I checked all the hardware in the device manager before and after the update. The camera runs on a PCI-1428 NI Framegrabber card and everything works fine. I can run all other vis, use the camera, etc. after the update, except running or saving vis that contain a Matlab script field.
I've also created a new vi and only put in one Matlab script. When I tried to save it Labview didn't respond any more and I had to kill the process with the task manager.

[ThSa]

It seems that the ActiveX IDs of Matlab aren't the correct ones, but it sounds crazy that this is happen after the installation of the IMAQ driver.

I think, there is one relevant KB for this problem. If this fails i'll ask the colleagues in USA for further investigations

http://digital.ni.com/public.nsf/websearch/4475BC3CEB062C9586256D750058F14B?OpenDocument

(change the files)

regards,

ThSa