why does my installer want Realtime?

[falkpl]

I am using labview 8.51.  I  have many addons on my machine including DSC Vision FPGA and RT.  I have an application which usis daq mx, and imaq and imaq-dx (not vision vis though.  I added the 8.51 runtime engine, NI Imaq, NI Imaq-dx, Max 4.1 and Daqmx8.7.  I start the installer but it always wants the real-time disk.  This application uses no RT vis and should not waqnt this disk.  What triggers this action and how can I avoid it.  I have had this problem many times and cant seem to find a solution other than shipping my installers seperate (I hate this solution).

[Hillman]

Hi Paul.

Thanks for your post and I hope your well today.

I would take a look at the following KBs - there are some options to check in your installer.. Also, remember that some share installer dependencies.

Why Do I Get A "Missing Distribution" Error When Trying to Build an Installer from LabVIEW 8.0?

http://digital.ni.com/public.nsf/websearch/C3666BA408F81E59862570D20056E692?OpenDocument

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

http://digital.ni.com/public.nsf/allkb/5C55288F366FC5CA862570F500680F7C?OpenDocument

One assumes your install works fine as your not including it anyways? To remove the warning you could do a silent install.

Another option would be to take a look at the setup.ini file which should be in the installer volume directory. 

Hope this helps,

[falkpl]

Thanks for the links I will look them over.  The issue is not durring instalation but during my build of the executable.  How do i prevent the installer from asking for CDs from addons that are not used for the application I am writing the installer.  I am afraid that if i just feed the installer the disks parts of addons which require liscencing such as the realtime runtime will be required by the final application which is a problem.

[Chris G in AE]

Paul,

I'm not 100% sure of how the files are stored on the CDs, but I am 100% sure that your customers will not need a license for anything you give them in your executable.  This is the reason why we have runtime engines for everything and free drivers for the rest.  My feeling on why the installer is asking for multiple CDs is because some files are spread out across multiple CDs.  

One way to get around feeding LabVIEW the CDs while you're building the installer is to copy all of them to your hard drive.  Then you point LabVIEW to the folder that they're saved in and it will run seamlessly.   Happy Holidays!

[falkpl]

Thanks I am playing it safe and just sending the free installers and a simple installer which will install my application and the lv runtime engine.  I have never had much suscess with the additional installer but it is on my list of things to master

[WesW · Accepted solution]

Hi Paul,

Just to clarify, you don't need to manually copy the CDs to the hard drive, as the LV application builder will automatically only save what it needs if you check the "cache" option during the installer build. Please see this thread for further information on why app builder works this way: link

Regards,

- Wes / NI

Message Edited by WesW on 12-29-2008 02:28 PM

Message Edited by WesW on 12-29-2008 02:29 PM

[falkpl]

Thanks The reference did clairify some of my confusion.  I have been struggling with additional installers since they were introduced.  Will there be any issues with running the installer build on different machines with different toolkits (IE# ON a client machine which doesnt have Realtime module on it)?

[WesW]

Paul,

I wasn't quite clear on your question, so I'll answer it both ways. About running the installer that App Builder created - you can install it on any machine regardless of what other software is already installed on that machine, and it will work properly. 

Regarding building the installer on another machine - as long as that machine has the same version of daq mx, imaq, imaq-dx, and max (what you mentioned that your application uses), then it will build fine (and not ask for RT). If the other machine has different versions of those components, it still should work properly, but you might get a warning the first time you open that project, but you can just reselect those products and continue.

Regards,

- Wes / NI