Why does the installer require CDs that are not related?

[Ozfarmboy]

Hi there,

I have experienced this problem a few times now.

I have installed LabVIEW 8.5.1, as well as LabVIEW 8.5.1 RT, LabVIEW 8.5.1 FPGA , and NI-RIO 2.4.0, NI-DAQmx 8.7, etc.

For this particular issue, I am trying to create an installation kit for a simple application that only uses LabVIEW, and NI-DAQmx.  I would like to include NI-MAX as part of my installation.  I go through all the steps to create my installation, and then I click BUILD, and away we go.

For some reason, half way through the build, the process prompts me to insert the NI-RIO 2.4.0 disk 1 into the D drive?  Now why on earth does the Builder need my RIO disk for an application that has no connection to NI-RIO?

I have had similar problems with the TestStand Deployment Utility in the past too.

Can anybody shed some light on this one?

Thanks!

[Ozfarmboy]

Extra notes:  The problem appears to go away when I unselect NI-DAQmx 8.7.  However I would prefer to have the installation include DAQmx.

[Soundar]

On Jun 3, 11:40 pm, Chris_Farmer <x...@no.email> wrote:
> Hi there,
> &nbsp;
> I have experienced this problem a few times now.
> &nbsp;
> I have installed LabVIEW 8.5.1, as well as LabVIEW 8.5.1 RT, LabVIEW 8.5.1 FPGA , and NI-RIO 2.4.0, NI-DAQmx 8.7, etc.
> &nbsp;
> For this particular issue, I am trying to create an installation kit for a simple application that only uses LabVIEW, and NI-DAQmx.&nbsp; I would like to include NI-MAX as part of my installation.&nbsp; I go through all the steps to create my installation, and then I click BUILD, and away we go.
> &nbsp;
> For some reason, half way through the build, the process prompts me to insert the NI-RIO 2.4.0 disk 1 into the D drive?&nbsp; Now why on earth does the Builder need my RIO disk for an application that has no connection to NI-RIO?
> &nbsp;
> I have had similar problems with the TestStand Deployment Utility in the past too.
> &nbsp;
> Can anybody shed some light on this one?
> &nbsp;
> Thanks!

Hi,
If your installer requires some files from the LabVIEW/NI Drivers
setup, it searches for that file and loads during building. In your
case, since you installed with CD, it is prompting. Check the
dependencies for the installer, while building the installation setup.

Soundar.

[MSATLAB]

Hello,

     Another thing to consider is that if you have your RIO installed on the building machine, it may assume that you will need those drivers on the computer you are building the application for.  DAQmx would then require those drivers if you plugged it in. 

Michael

[Sorooshster]

Hi Chris,

This problem happens because NI-RIO updated some component of your system that is being included in your installer.  For instance, if DAQmx installed MAX 1.0 (the numbers are arbitrary) and later you installed NI-RIO which installed a later version of MAX, say 2.0, when you go to build your installer and you include DAQmx (which includes MAX) it sees that NI-RIO updated MAX last so it asks for that CD so it can install the updated version of MAX on the installer.  There is a good Knowledgebase on our website that explains this; it is linked here.  Hope this helps, thanks and have a great day!

[Ozfarmboy]

Thanks Stephen,

That makes sense, however if I unselect DAQmx, but still have NI-MAX and LabVIEW runtime Enginer selected, I do not experience this problem!  So if NI-RIO was the last thing to install MAX, then how come it doesn't need it? 

[TroyK]

Hi Chris,
When you installed NI-RIO it must have updated your DAQmx drivers (which would be included on the NI-RIO disk).
The Application Builder always looks for the "nidist.id" file to tell it what distribution was used to install the drivers you are trying to distribute. It keeps track of where it came from too (drive & directory).

You may be able to specify a different distribution in the "additional Installers" category by changing the "Installer Source Location" if the distribution ids are compatible.



Other wise you need to reinstall the DAQmx drivers from a location (CD) you are expecting them to come from, then that is what the Application Builder will ask for.

PS. I thought you could only install the Measurement and Automation Explorer as part of a DAQmx distribution (runtimes Full to 4, Runtime 5 doesn't include it.)


Message Edited by Troy K on 06-06-2008 01:17 PM

[Sorooshster]

Sorry guys,

I was just using MAX as an arbitrary example.  Troy is right, the NI-RIO driver updated something within your DAQmx driver.  The way to avoid this is to keep your drivers current and save them to your C driver and install them from there.  I know this method can take up a lot of hard drive space but if you make installers often, you will want to make it as easy as possible. 

[WesW]

Hi Chris,

Just to further clarify - NI's software is very modular, and is often composed of multiple underlying components, which are often shared between different products.  When multiple drivers and componenents have been installed over time, it's very likely that both visible products (such as MAX) and hidden support components have been updated.  So, though it may not at all be obvious why it's prompting for a given CD/DVD, it legitimately needs something from it.

The easiest solution for this is to let LV cache these products for you to the hard drive, then you'll never be asked again (for that product). This way, you don't have to manually copy the CD to the hard drive, it will only cache the products it needs (so you don't waste space copying the whole CD), and the cache will be automatically cleaned up when those products are uninstalled or upgraded.  In LabVIEW (8.5), you can do this by:

• removing all NI CDs from the drive
• picking the "Additional Installers" and drivers that you want
• when it prompts you to locate the missing distribution, ensure that the checkbox "Cache components from this distribution" is checked, then insert the appropriate CD
• repeating for each CD as necessary

After this, for the given set of products you selected - it shouldn't prompt you for the CDs any longer.

Regards,
- WesW / NI

[Qianlong]

I realize this thread is quite old, but I am experiencing a similar issue, and I am wondering if it is possible to redirect the installer builder (LV 2013) from the device driver distribution it thinks it needs to a more up-to-date distribution (for which I actually have the CD). I have not yet been able to figure this out.

I have previously had LV2012 installed on this computer. At the time I installed with the Aug 2012 distribution of the device drivers which came with the 2013 Developer Suite DS1.

Now I have LV2013 installed, with the Aug2013 distribution of device drivers that came with 2013 Developer Suite DS2. I suppose that there may have been automatic updates (or updates that I was prompted for) in between that could have updated some of my files.

When I try to build the installer, it want the Feb 2013 distribution of device drivers, which I do not have. I can download it from the NI website, but I would prefer to be running building off of the version that I have on CD, and which I believe should also all be compatible. Is there a way that I can point it to the updated device drivers? I have already installed them, so from this thread it would appear that somehow not all of the files were updated (not too surprising, I suppose).

Help?

-Mitch