Application Builder Includes Older Runtimes in the Installer

Lately, I'm noticing that built installers take an eternity to install, compared to some that I built in 2010 (the year, not the LV version).
As I look as what is being included in the installer, I can see that LV Runtimes 2010, 2011, 2012, and 2013 are all being installed. While I do have the other versions of LabVIEW installed on the same system, the software is written purely in 2013. Even if I am manually selecting additional installers, the other runtimes are still being included.
Any ideas?
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

Hi MoviJOHN,
Do you still have other LabVIEW versions installed in your computer? If so, do you need them?
Warmest regards,
Lennard.C
Learning new things everyday...

Similar Messages

Can I include raw files into the installer folder with LV application builder?

Hello,
I have created a batch file that will run at the end of the installer, which will copy over some raw configuration files into the source destination so that the configuration files can be customized for each end user without rebuilding the installer with application builder. I also have an autorun.inf so the installer will automatically run when the user installs the CD.
However I would like to have some default configuration files and an autorun.inf file that will be automatically added to the installer "volume" folder using the application builder.
However I don't see a way to include raw files in the "volume" folder. It appears all source files in the application builder are embedded into the binary files.
Please let me know if this is possible with the current application builder.
Regards,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor

Russel,
i think this link might give you some good hints....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to include hardware configuration in the installer?

I have a VI developed with LabVIEW 2009 V9.0f2 using a USB-6009 and two of its analog inputs. The VI uses the DAQ Assistant to configure the USB-6009. I include the DAQmx Core Runtime 9.0.2 with the LabVIEW Runtime Engine 2009 in the installer build. I spent most of the past week trying to get the application to run after installation.
If I leave out the Hardware Configuration from MAX (no configData.nce file) and run the installer on another machine the application produces an Error-200378 Custom Scale Specified Does Not Exist when it runs (I searched the 200378 error code - no help).
If I include the Hardware Configuration from MAX to produce a configData.nce file, and select Perform the Import Silently to Merge the Import Data when the installer is built, I get this message during the install to another computer:
.\Distribution.cpp(1902): IInstallerError 11004Developer Error. Distribution contains invalid dependencies:1. Product NI Remote Provider for MAX 4.6.1 ({FBD23528-31AC-412A-9DEE-6CEA814A7430}) depends on product with upgrade code {B5171839-26E3-48D9-9FD6-AF7F39055146}, version [8.2.379.0,), language in {} which is not in the distibution.2. Product NI LabVIEW Real-Time Error Dialog ({297FA251-FF30-4F16-978C-4A65EA804EFF}) depends on product with upgrade code {B5171839-26E3-48D9-9FD6-AF7F39055146}, version [8.2.379.0,), language in {} which is not in the distibution.3. Product NI LVBrokerAux 8.2.1 ({0FB31DF8-38DF-4C9D-B313-AFAFC3FBA02B}) depends on product with upgrade code {B5171839-26E3-48D9-9FD6-AF7F39055146}, version [8.2.379.0,), language in {} which is not in the distibution.Correct the distribution and try again. I’m not really sure that the installer even uses the configData.nce file during the build.
Another error I have seen (I have done several other builds using various installer settings) is that the app appears to run fine except it is unable to find the USB-6009, even though the operating system picks it up and installs it in the device manager seemingly without error.
I am a novice LabVIEW user. Any help you could give would be greatly appreciated.
Bill
Solved!
Go to Solution.

Hi Willygene,
Give the steps listed in KnowledgeBase 52GH9OW5: Why Do I Get Error 200378 When Running a Stand Alone Application? a shot, does this help with the 200378 error?
Do you have DAQmx installed on the other machine? Are you unbundling it with your installer? If so, what Run-Time Level are you buiding into your installer? Can you post screenshots of the errors that you are getting?
Joshua B.
National Instruments
NI Services
NI Support Resources
NI Training Resources

How to include a font in the installer?

Hi all!
My program uses a custom font (namely popular NI7seg font) that I would like to include in my installation distribution.
I am using LabView 8.5 and I have tried force the installer (normally through the options window) to copy the font into [WindowsFolder]\Fonts folder and to add a registry key.
After installation I have noticed that the font actually is added into the registry however it has not be copied to the fonts directory.
Any ideas?
Regards,
Michal
Solved!
Go to Solution.

Hi Michal,
At first, you should add the font file to LabVIEW project.
Then create a Source Distribution from build specification. In the source distribution setting, you can specify where to distribute the font file.
When you build your installation, you add the source distribution as source file to installer.
I'm not sure if you can skip step 2 to add the font file as source file to installer, but source distribution could work correctly.

Labview 8.5 application builder .exe does not run.The same source code runs ok.

Hi,
I have an application built in labview 8.5 application builder using windows XP. I have one instrument connected in gpib and one connected to a serial port. The source code runs ok but when I build an executable of teh same code and try to run it, it doesnt run the instrument connected to the serial port. It does communicate with the gpib port. Any ideas why this would be happening?
Steven

Additional to Britoa's reply: Did you add the serial commuication (drivers) when you built the application?

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How do I insure that the VISA driver is installed when I insatll my application using the application builder?

One some PC's , when I sniatll my applciation build with teh applicaio buider, it apperas that the VISA drivers are missing. In other cases it install them fine.

Hi Juand,
I have included some screenshots of where you would be able to see the VISA runtime in both MAX and in the installer page if you have it installed.
If you do not have it installed, it can be downloaded at www.ni.com/downloads. Although the runtime should have been installed with the full version of the driver.
Scott G.
AE Specialist
National Instruments
Attachments:
VISAinINSTALLER.jpg ‏541 KB
VISAinMAX.jpg ‏461 KB

I use iBookAuthor to make a textbook for my students; I revised it, including title page, but when I export it and upload it to my iPad, the old title page appears, even though I've deleted the older version of the text before I upload the new one.

Last year I produced a textbook using iBookAuthor for my students. I exported it as an iBook and they uploaded it to their iPads. This year, I revised it, including revising the title page. However, when I upload the new version, the old title page is shown, not the new one. I deleted the older version of the textbook before I did this. I've been told that I can cut and paste each revised chapter into a new template and that will work; however, title page and glossary can't be cut and pasted. Any thoughts for getting the entire new version on the iPad? I'm also told that if it is uploaded to an iPad that never had a previous version of this textbook, it will upload correctly. But my iPad has had several older versions, now deleted.

I had a similar issue when trying to create an iBook file to submit for course credit for one of the Apple Learning Essentials classes I took. I had a book I'd started previously which I updated and submitted, and then had to make some edits to for the course evaluator. I made the edits, and when I previewed the book in iBooks Author, it looked correct, but whatever I sent to him only showed some of the edits - for example a new page I created was there, but some edits I made to image captions and the title page image were not.
What worked for me was to do a "Save as" of the actual Author file to a totally new location (I used the Desktop), and then submit that file - which seemed to work in terms of the changes sticking. I even used the same file name.
I'm not sure if some similar action might help you (maybe change the file name slightly?) or if you've already tried something like this.
Still doesn't change the fact that this is a pretty irritating bug.

LabView 2010 Application Builder for EXE Always Included files are not Included

In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
Why does the Application Builder ignore these files specifications?

Dennis Knutson wrote:
The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
The Build Directory.jpg file shows the file in the Build directory that were built.
The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
Attachments:
Build Source Files.jpg ‏151 KB
Build Directory.jpg ‏125 KB
Data Directory.jpg ‏131 KB

LV Application Builder: solving "The system cannot find the file specified." error?

Hello everyone,
I don't mind banging my head off of something that feels complex but it's always frustrating to be stumped by something that seems simple... I have LabVIEW 2014 and Application Builder. I've built an program that runs flawlessly as a VI, then compiles and runs flawlessly as a .exe. But I can't seem to get the installer to work. I get the following error:
Per the suggestions in this thread and this KB article, I created a new installer build spec, then a new application build spec, then a new project with all my VIs in it, building and testing the installer at each step. None of that seemed to make a difference.
I ran the installer as admin, I created the install directories ahead of time (in case it didn't have the privileges to create folders), and built an installer without the Run-Time in it. None of that worked either. Lastly, I played around with putting all my subVIs in a library.
So since the tutorial worked I'm assuming that it's some quirk in my program. Does anyone have any experience or advice as to what specific aspects of a program play nice with the AB installers? It's one primary VI, less than a dozen subVIs, a few Type Defs, and no hardware integration. Seems like a pretty straightforward and simple program but maybe something in there is persona non grata with Application Builder?
Xander Cesari
Automotive/Internal Combustion Test Engineer
CLAD certified, mainly focused on data acquisition
Been LabVIEWing for a few years, still a lot to learn
Solved!
Go to Solution.

Hello,
Thanks for the response. Nope, I'm running it from a regular directory, in the same folder as the rest of my project. Here's the project window showing the folder directory:
Xander Cesari
Automotive/Internal Combustion Test Engineer
CLAD certified, mainly focused on data acquisition
Been LabVIEWing for a few years, still a lot to learn

Build an application installer and include files referenced in the code

I want to make an application installer of my project, and I need to include a picture that I'm using in the code.
This picture is used both in the vision assistant and in a low level color pattern match.
What I need is some way to reference this picture in my code, so that when I create the installer and the project is installed on another computer, this file will always get referenced.
Can someone please tell me how to do this?
Thanks in advance!

Your installer should be putting everything in the data folder you need. So it should be fine.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Application builder error coder 21

I get this error code when trying to build an application and include the visa runtime install files
What can i do to fix this error
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'LabVIEW 2009, Media 1' from: \\dtads2\it_software$\Labview 2009\DVD 1 of 2\Distributions\LabVIEW\LabVIEW2009\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Copying distribution 'National Instruments Device Drivers - February 2010' from: C:\National Instruments Downloads\NI Device Drivers\Feb10\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
While validating input parts.
and so on

Hi brockmaa,
It seems that the files it needs to include the VISA runtime are not being found on your system. Try re-installing the correct version of VISA you need from:
http://www.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:3.25.123.1640,ssna...
and try to build the installer again and it should be able to find the correct files.
DylanC

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

LabVIEW cannot locate some components necessary to build the installer - looking for "Setup" installer

Hi,
I have an application that has been upgraded to LabVIEW 8. I have previously been able to build the exe and installer but recently the installer part of the build has been failing with the following error message:
Unable to locate the installer source for "Setup" distribution.
Locate the distribution and try again
The dialog includes a file path prompt that is pointing at the Installer\Volume directory where Installer is the target directory for the build. The installer build is configured to span CD-sized volumes (650MB)
There are no sources or support files named anything like Setup that I can see.
The installer includes DaqMX and the LabVIEW 8 runtime engine as additional installers
The build works ok If I turn off the DaqMX driver installer
Cheers,
Brett Percy
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion

Hi Andy,
I've upgraded DAQmx to 8.0.1 and the installer build now works....sometimes.
And sometimes it gives me a different error:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI-DAQ 8.0.1' from: C:\Documents and Settings\brettper\Desktop\NIDAQ801\8.0.1\ to: C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\
Copying distribution 'Setup' from: C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\ to: C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input directory 'C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\bin\p2' not found for part 'palSetupLVRT.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL for Phar Lap ETS {3263845B-95F2-43C0-817E-B7BF25BCB742}.xml'.
Input directory 'C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\bin\p3' not found for part 'infInstaller.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-DAQ INF Files {2146CF1A-5ACD-4A50-8B36-6A7DD095B08C}.xml'.
-- SNIP --
Input directory 'C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\bin\p43\nilm' not found for part 'nilm.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI License Manager {FB6DF036-C3A7-4A89-92DA-B4364A8E9373}.xml'.
Input directory 'C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\bin\p44\LVRealTimeErrorDialog' not found for part 'LVRealTimeErrorDialog.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI LabVIEW RT Error Dialog {3DFF45F7-C12C-4A3A-BA9E-1946A4E92424}.xml'.
Input directory 'C:\Documents and Settings\brettper\My Documents\Work\Deakin University\433 VuPlate Software Upgrade\builds\VUPlate\VuPlate Installer\Volume\bin\p45\LVBrokerAux800' not found for part 'LVBrokerAux80.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\Broker Aux 8.0 {88BBB9A9-C034-466E-BB83-8197AFD1669C}.xml'.
*** End Error Report
Done building deployment
And underneath all this (in the Details of the Build Errors dialog) I get
"Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:"
followed by nothing...
So it's sort of working but not entirely reliable. I think I've seen the path to the DAQmx installer in the Additional Installers tab replaced with the path into the installer build directory I was being prompted with earlier but I haven't been able to replicate this.
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion
Attachments:
Full error listing.txt ‏16 KB

Applicatio​n Builder Includes Older Runtimes in the Installer

Similar Messages

Maybe you are looking for

Application Builder Includes Older Runtimes in the Installer