LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Add IVI driver to exe / installer

Hello,

 

i created VI which is used for control TTi CPX400DP power source.

VI use IVI driver.

Question is, isit possible to build installer from project manager, which contain IVI driver, so when user install this VI, IVI driver will install automatically?

If possible, please advice how to do this...

 

Thanks

 

0 Kudos
Message 1 of 8
(1,260 Views)

Yes! It is possible. 

 

In your installer build specification there is an additional installers option.  I forgot exactly where it is so...look in the Help File 😀 then, just follow those instructions. 


"Should be" isn't "Is" -Jay
0 Kudos
Message 2 of 8
(1,250 Views)

Thanks i found it.

 😄

if somebody else is looking for these, here you go...

milan87_0-1687519978440.png

 

Message 3 of 8
(1,230 Views)

@milan87 wrote:

Thanks i found it.

 😄

if somebody else is looking for these, here you go...

milan87_0-1687519978440.png

 


And, under the advanced section you can run an executable as either a pre or post installation operation if you have an IVI installer.exe.


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 8
(1,220 Views)

I, too, am having trouble adding an IVI installer (or ten) to the installer spec of my project.  When I open the installer spec (created by someone else on a different computer), it says it's missing ten products: 

PghFool_0-1688767190847.png

 

I downloaded the offline installation package for NI IVI Compliance Package 19.5, unpacked it, and put it in a folder (which I named NI IVI Compliance Package 19.5) in C:\ProgramData\National Instruments\MDF\ProductCache, where all the other installers seem to be, but it still doesn’t show up in the list of installers available when I open the install spec. The inside of the folder looks like:

PghFool_1-1688767438538.png

 

so I can see it has an exe file instead of the .msi files that the other folders have.  It's also much bigger (500+MB), so I'm pretty sure I'm going down the wrong path.  Where do I find the right installers for all these errors?

0 Kudos
Message 5 of 8
(1,147 Views)

@PghFool wrote:

I, too, am having trouble adding an IVI installer (or ten) to the installer spec of my project.  When I open the installer spec (created by someone else on a different computer), it says it's missing ten products: 

PghFool_0-1688767190847.png

 

I downloaded the offline installation package for NI IVI Compliance Package 19.5, unpacked it, and put it in a folder (which I named NI IVI Compliance Package 19.5) in C:\ProgramData\National Instruments\MDF\ProductCache, where all the other installers seem to be, but it still doesn’t show up in the list of installers available when I open the install spec. The inside of the folder looks like:

PghFool_1-1688767438538.png

 

so I can see it has an exe file instead of the .msi files that the other folders have.  It's also much bigger (500+MB), so I'm pretty sure I'm going down the wrong path.  Where do I find the right installers for all these errors?


I hate to ask the obvious question but....Did you read the last paragraph on the Build Errors dialog output string?  What did you find at Ni.com/info under the packagebuilder code? 


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 8
(1,137 Views)

Thanks for the reply!  I don't mind obvious questions. 

 

The info page describes how to build packages, which I kind of dismissed because I was trying to build an installer.  I was focused more on the "installers are missing" phrase, and annoyed that NI couldn't distinguish between the potential issues.  I haven't tried building packages before, and am not familiar with the vocabulary. 

 

Now that I've learned a bit more, I'm going to try that path instead of building an installer.  So far, I successfully built both the package and the package installer .exe.  I'll release it to my customer and see how it goes.

0 Kudos
Message 7 of 8
(1,124 Views)

Just copying the installer files to the cache folder unfortunately won't work. The reason is that the installer builder can only include components that are actually installed on that system. As such, install the missing components first, then try to build that deployment installer again.

0 Kudos
Message 8 of 8
(1,084 Views)