Distribution Kit Error

[ocean]

I am using the R&S instrument driver for CVI. So, does that bypass NI-VISA?

Brenda

[cymrieg]

Sorry if you think I am hijacking this thread but.....

If I use the "Create IVI Driver Installer" does that bundle in the instrsup.dll and can I have it bundle in VISA also?

[juergenstraub]

Hi Brenda,

the FSH R&S instrument driver utilizes (NI-)Visa. No chance to run it without.

Regards Juergen

[jose.olvera@optichron.com]

Hi (all)

 My application was converted from CVI Rev 7.x to CVI rev 9.x .... and (after few minor changes) is up and runing OK

a.- The project Contains multiple c files...is a mid-large size project

b.- Contains multiple *.fp files and *.lib (or DLL files) .... developed  or built on CVI REV 7.x

 Problem: When I tried to create a 'new' DISTRIBUTION KIT ... suddenly it stops and a popup window

indicating that I have to provide 'device drivers' (etc) .....which cannot be found  ???? !!!!

NOTE: My CVI 9.x  license is FULL and all NI device drivers were installed...... any advise ?

 O I have to re-build all my dll's with rev 9.x ?   is there any other alternative ?

see below the LOG

 ==== error LOG history  =====

Adding files to installer
Warning: .NET Support module: cannot find 1 dependency with the following module ID:
  mondo.E4183BB4_18A8_11D5_A549_0090278A1BB8
Done adding files
Preparing to build deployment
Copying products from distributions

[Mert_A.]

> Problem: When I tried to create a 'new' DISTRIBUTION KIT ... suddenly it stops and a popup window

>indicating that I have to provide 'device drivers' (etc) .....which cannot be found  ???? !!!!

Now CVI has the ability to bundle device drivers and other NI component installers along with your installer to create a distribution much like the distributions that NI ships. In order to do this, CVI needs to be provided with a source to copy those driver/component installers from. In most cases, this means providing the original disc(s). If you cannot provide these discs,  you can deselect everything except the CVI Run-Time Engine (which you never need to provide the disc for) on the Drivers & Components tab of the distribution editor. Refer to the help for more details.

> O I have to re-build all my dll's with rev 9.x ?   is there any other alternative ?

You should not have to rebuild your DLLs. The 9.x runtime engine is backwards compatible with binaries built against older runtime engines. Is there some issue that makes you think you have to rebuild them with 9.x?

> Warning: .NET Support module: cannot find 1 dependency with the following module ID:
>  mondo.E4183BB4_18A8_11D5_A549_0090278A1BB8

From what I can tell, this is a merge module that was supposed to distribute the .NET framework, but was ultimately never released by Microsoft. It is a dependency that was automatically added by Visual Studio when the .NET Support module was originally built by NI. In short, you can ignore this dependency warning. The only thing to keep in mind is that if your application relies on the .NET framework, your distribution will not install it; the target will have to already have it, or it will have to be installed separately.

Mert A.

National Instruments

[JonathanN]

That warning you saw regarding the mondo dependency will be fixed in the next release of CVI.

[jose.olvera@optichron.com]

FYI

I tried to follow your advise ...see details ..... and got a similar problem for two trials

so,  PLEASE ADVISE (or confirm) if I have to get the next REV to fix these problems

Trial  1 :  Inside the EDIT (distribuiton kit window) ... selecting ONLY the CVI standard run time

Trial  2 :  Inside the EDIT (distribuiton kit window) ... using the 'default'  ( std run time + Analysys support + NIDAQmx  + NI-VISA )

a.- By 'pressing' the button named : Check Modules Depedency ...... I got a green ligth (all modules were found) for both trials

b.- When runing the BUILT DIST KIT ..... it ran about 70 percent of the 'bar' and then stops to ask to more modules (not found)

and then  I tried all my 4  DVD from the CVI rev 9.0 ...w/out success

Details FYI

1.- when runing the 'build' ..... the last modules found (as displayed) were : nidmxrtl.cab, mxs.msi,dotnetfx.exe

..... to reach 70 percent from the bar

2.- In both cases stops when failing to find the module named : PXIPlatformExpertRT_kor.mst

NOTE: I have a PC and Windows XP (not an PXI) with USB-GPIB card and  an USB-DAQmx

3.- next is the DLOG history

Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'National Instruments Device Drivers - November 2008, Disk 1' from: E:\ to: c:\dpd_ATE\C\reader\cvidistkit.DPD_ATE\
 

[Mert_A.]

Did  you try putting "National Instruments Device Drivers - November 2008, Disk 1" in drive E:\ when you get the prompt? I'm not sure if that is one of the 4 disks you mention having tried. 

If you have tried that disk and it is not accepted, follow the instructions in my first post in this thread to create a more detailed debug log which should indicate the specific problem. Post it back here, and I will take a look.

Mert A.

National Instruments

[jose.olvera@optichron.com]

short answer : YES I placed the DVD on drive E :

long answer :

 0.- After checking all modules or dependencies were found OK ( button on the DIST KIT window)

 1.- The Building start runing as normal until the bar reaches around 60 percent , and then ask for the DEVICE DRIVERS

 2.- At that moment I placed the DVD's (disk2 - dev drivers) ... and started adding modules  reaching around 70 percent of the bar

 3.- then stops ..... and indicating that a module was not found .... so, I tried then Disks 1, disk 3, disk 4  //w.out sucess

So,  I am confused why is looking for the PMX module if I am NOT using such 'box', I have a PC and windows XP

Jose

[Mert_A.]

Two things to note:

1. The "Check Module Dependencies" button attempts to locate all the merge module (.msm) dependencies only -- it does not apply to component installers that must be copied from source disks. So in your case, this does not tell you anything useful.

2.  When you select components to include in your distribution (like DAQ or VISA), the package that is included may have more features than just the ones needed to support your particular application. It's just like installing that component/driver from the original NI disk. So just because you're developing a Windows desktop app, it doesn't mean you won't be distributing some PXI, RT, or other such features as part of the DAQ support.

Please follow the logging instructions in my previous post so that I may help you further.

Mert A.

National Instruments