additional installer wants too many addons

[falkpl]

I am having some difficulty making installers for my applications in LV 8.5.  I have several applications which I want to use the additional installers feature.  When I add a few installers LV8.5 Runtime engine, daqMX Visa the install process starts but the installer asks for disks which my project does not use.  I have many addons such as DSC and Vision on my system but the curentproject are not using them.  When I start the installer I some times get asked for the vision or DSC disk.  This should not be needed since I do not use components from vision or DSC the disks should not be needed for the installer?  How can I prevent the installer from wanting to reference these addons.

Paul

[Eugen_Graf]

I have this problem too. I did a copy of CD to my HDD and reinstall my hardware drivers from there. Now I have not to insert a disc, the installer takes all what it needs from HDD. But I know it's a bad solution.

[falkpl]

yes after the first install all installers are cached which speeds up the problem of having to insert disks.  I bigger problem is why additional NI packages are being referenced by applications ehich dont use them.  These addons will require runtime liscence which I dont need since the application is not using them.

Paul

[TMC-NI]

Hi Paul and Eugen,

This is a question we get a lot, and although Eugen's method is recommended by NI to speed up the installer build, here is the reason why you may be getting this behavior.

From How Do I Stop the "Missing Distribution" Notification Each Time I Build An Installer?

"Some of these shared installer dependencies may have had a new version installed by another NI product and that product will be required in order to build the installer.

For example, say you install NI-DAQmx 8.0 which also installs Measurement and Automation Explorer (MAX) 4.0. As a result, MAX 4.0 will be installed on your computer.

But two months later you decide to install Measurement Studio 8.0 which installs an newer version of MAX (4.1) and overwrites the previous version of MAX (4.0) (note: the version numbers of MAX are just an example and don't reflect real revisions shipped with various products). Now, NI-DAQmx 8.0 depends on Measurement Studio and when you build an installer that includes NI-DAQmx 8.0 it will need to copy the Measurement Studio installer from the distribution that installed it. So while you aren’t directly including Measurement Studio you are including a shared dependency that it updated, and the Application Builder needs to copy the installer of that dependency. "

To clarify, if you have upgraded your software, often times individual components come with several applications already included.  Example is DAQmx and MAX.  Measurement and Automation Explorer will often come with a variety of other software and once it is updated, everytime you try to build an installer, your application will ask you to include the latest version that a particular module/toolkit is referring to. 

A possible solution would be to perform a repair on your version of LabView, by repairing, your copy of LabView should relink the version information to the latest versions of the ones found in your computer.  Lets try that for now and let me know of your results.