LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

dependencies error CVI 2010

Yes. the error caused by the .inf files also affects a distribution created with the reduced runtime. We're still looking into that issue and I'll let one know once we have a workaround or a fix.

 

But, just to clarify... are you saying that you did not see the "installation has failed" error when you created a distribution with the reduced runtime that did not include those two merge modules (but that include .inf files)?

 

Luis

0 Kudos
Message 11 of 14
(1,550 Views)

You are right.

 

Without changing anything others in the distribution kit editor (.inf files always included) I got the following behaviour:

  • With the reduced runtime and without adding the 2 merge modules the installation completed without an error but when I launched the application I got the Mesa.dll error.
  • With the reduced runtime and WITH the 2 merge modules the installation failes (exactly the same behaviour as with the full runtime and without the merge modules)

I hope this clarifies the situation

 

Bertrand

0 Kudos
Message 12 of 14
(1,542 Views)

Okay, I think we've finally figured it out. This is actually a bug that has been in CVI since 2009, but that only becomes apparent if you happen to click on the Check Module Dependencies button. I'm fairly sure that this is really the only factor that impacts whether the installation fails or not. It's probably the case that, because of the mesa.dll problem, you had to start checking dependencies and, if you happened to build a distribution after clicking on this button, then the installation that you build will fail to install if you have .inf files in your distribution.

 

This is being tracked with bug ID 291813 and it will be fixed soon. In the meanwhile, there are two possible workarounds you can use:

 

1. Any time that you check module dependencies you should restart CVI before building your distribution.

2. If you never need to build 64-bit distributions, another workaround is to remove DIFxApp_x64.msm from C:\Program Files\Common Files\Merge Modules to some other location. It's not sufficient to rename it. The file must be physically moved elsewhere.

 

Please let me know if this fixes your problem.

 

Also, because of the earlier issues, if you want to build a 32-bit distribution with the reduced run-time, you should manually add these 4 merge modules to your distribution:

 

    C:\Program Files\Common Files\Merge Modules\Microsoft_VC90_CRT_x86.msm

    C:\Program Files\Common Files\Merge Modules\policy_9_0_Microsoft_VC90_CRT_x86.msm

    C:\Program Files\Common Files\Merge Modules\Microsoft_VC90_ATL_x86.msm

    C:\Program Files\Common Files\Merge Modules\policy_9_0_Microsoft_VC90_ATL_x86.msm

 

I'm really sorry about all these problems. You managed to find three independent problems with a single distribution! Thank you so much for your patience in helping us investigate this.

 

Luis

0 Kudos
Message 13 of 14
(1,533 Views)

With the 4 merge modules now everything is working.

 

Thank you for your support

Bertrand

0 Kudos
Message 14 of 14
(1,524 Views)