Multiple additional installers?

Can LabVIEW run more than one additional installer? I can only get one to run.
Attachments:
installers.PNG ‏25 KB

Hello slipstick,
It looks like creating a batch file is your best option. Here are a couple of links to look at.
Running a Batch File Automatically After an Installation to Access Installed Files
Creating a Batch File
Regards,
Jon S.
National Instruments
LabVIEW R&D

Similar Messages

Installing NI-RIO with Additional Installers in Applicaion Builder

Is it possible to install NI-RIO device drivers in a stand-alone
installer created from the application builder in Labview 8.2? I can't
seem to find NI-RIO as an option in the Additional Installers page when
building an installer. My target systems is a PC running Windows XP
SP2 with a PCI-7833R.
What are the steps to installing a built Labview 8.2 application that
uses a PCI-7833R with the application builder? Do I have to run the
NI-RIO installer separately from my application installer? Can I
install NI-RIO from the command line with the option of a silent
install like NI-DAQ (see this link)?

I installed NI-RIO v2.1 with the /q option from a command prompt like this:
setup.exe /q /AcceptLicenses yes
It took a while but it worked. NI-RIO v2.1 spans 2 CDs. The silent install never asked for CD 2 of 2.
My build application that accesses the PCI-7833R card works fine installing NI-RIO with the /q option.
Heres a list of NI software that was installed:
NI CompactRIO 2.1.0
NI LabVIEW Run-Time Engine 7.1.1
NI LabWindows/CVI 8.0.1 Run-Time Engine
NI Measurement & Automation Explorer 4.1
NI PXI Platform Services for Windows 2.1.0
NI-RIO FCF 2.2.0
NI-Serial 3.1
NI-VISA 4.0
NI-VISA Runtime 4.0
NI-VISA Server 4.0
The following can be included as additional installers with the Labview 8.2 application builder:
NI LabVIEW Run-Time Engine 7.1.1
NI LabWindows/CVI 8.0.1 Run-Time Engine
NI Measurement & Automation Explorer 4.1
NI-Serial 3.1
NI-VISA Runtime 4.0
NI-VISA Server 4.0
By including the above list of additional installers, can I create an
installer (and application) that uses the PCI-7833R card not having a
separately install NI-RIO first? I haven't tried yet but I will and
report back my findings.
The following NI software would be missing (i.e. not available as an additional installer from the application builder):
NI CompactRIO 2.1.0 (not using any cRIO)
NI PXI Platform Services for Windows 2.1.0 (not using any PXI stuff)
NI-RIO FCF 2.2.0 (this sounds like something I will need NI-RIO FPGA Communications Framework)
NI-VISA 4.0 (this might be something thats needed too)
Message Edited by dwisti on 10-24-2006 02:55 PM

Additional Installers List empty

Hi there
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"
Solved!
Go to Solution.

You're right!
What happened to the text .....?
Here it is:
Once again the list of "Additional Installers" at my installer build specification is empty (has been discussed here several times). I'd like to try the reg files mentioned here:
http://digital.ni.com/public.nsf/allkb/1B53A6FDFC20B8058625752400687F42
mdffix.reg
mdffix_vista.reg
My IT won't let me open or download these file. Can someone please post their content here?
Thanks in advance
Chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

How to design interactive pdf. for multiple additions and saves???

Using LiveCycle designer - Can anyone clarify how we can let others make multiple additions and saves to an interactive pdf. I created in Live Cycle Designer 8.2.1...
I have created an interactive pdf. with LiveCycle designer and sent to client.
Is there any way I can give them ability to save the pdf. make multiple additions and saves and send back when they have completed it?
or even pull up the file make changes and resend at some point in the future without having to fill in all form field again?
Thxz much,
JR

Sorry but this is the wrong forum (this is for the Collaboration Services). You may want to try the LiveCycle Designer forum:
http://forums.adobe.com/community/livecycle/livecycle_es/livecycle_designer_es

NI-VISA does not appear in the addition installers window

Its seems that i cannot add any NI-VISA packages to my "additional installers" window.
The dev system has VISA 4.0 and LV 8.0 and even after downloading and installing the VISA runtime especially to fix this problem, i still cannot see it in the list!!! There also seems to be lots more missing from what i have seen in screenshots on previous posts. Why oh why is this happening!
Alex.
:. LV2010 SP1 ... W7 .:

Thanks for your reply! It seems to have worked a treat!
I did the following steps:
1. uninstalled VISA 4.0 and DAQmx 8.x
2. installed DAQmx 8.6 (i wanted to upgrade to this a some point anyway)
3. installed VISA 4.2
I can now open the Installer Properties => Additional Installers window and have the following options:
and now that i can select the Measurement and Automation Explorer it has solved a second issue for me that i posted on this forum (see:
Problems with building and installer - hardware config). An error used to occur when i tried to include the "Hardware Configuration from MAX" but there are no errors now. Im sure it has something to do with also including the MAX in your installer. See Below:
Happy days for a monday
Message Edited by ali66b on 11-19-2007 11:21 AM
:. LV2010 SP1 ... W7 .:

How to add NI-VISA Configuration Support to list of additional installers

I recently changed computers and now I am trying to use an installer that I made with the old computer, but one of the additional installers I had selected was the NI-VISA Configuration Support. How do get that installed to my new computer so it will available in the list of additional installers?

if it's not in your 'old' installer then you did not include it in the build.
You will have to download the correct version from NI ... this is the link for the 5.4
http://www.ni.com/download/ni-visa-run-time-engine-5.4/4231/en/
There is a good chance if you install the latest NI VISA your program will run again!

Outlook 2010 to save multiple additional account password

Hi,
How save multiple additional email account passwords in Outlook 2010 in win xp machine?
Because, everytime these accounts are prompting passwords after we clicked even save password.
MD

Hi,
What does additional email accounts refer to? Is it an additional mailbox added to your Exchange account or it's just another email account configured in your Outlook?
Please try to add the users credentials to Credential Manager to check the result. We can open the credential manager by clicking Control Panel > All Control Panel Items > Credential Manager. Add credentials under Generic Credentials.
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support

Require additional installers?

Hey,
I am looking for advice on the following, I am attempting to build a stand alone application, i am unsure as to how to go about achieving this as its the first time i have attempted it. I have built an application with my main vi as the start up vi and all the dependencies are attached so there are no vis to choose from for the source files for the always included window.
My next step was to build an installer, i assume the source files to attach to this is the one i selected for the start up in building the stand alone application. Now within my vi i use NI-IMAQdx 4.0 aquisition software i was wondering what additional installers i require or will my code execute? Do i need to add drivers etc.
Regards,
Damien

Hi guys,
I have added the NI-IMAQ 4.7.0, NI-IMAQdx 4.0.0, the chroma driver, NI-Serial and the NI-VISA Configuration support 5.2, NI-VISA Runtime 5.2 and NI-VISA Server 5.2. Do i install Vision Run-Time Engine 2012 also?
I have a serial number for the labview professional development licence and it contained the vision acquisition module along with the vision builder and toolkits etc. I also have a different serial number this is the vision development module run time licence which is the vision acquisition product. So this is the one i activate on the deployed computers? Thanks for the help i am just a bit cautious as to what i can activate.
Thanks
Damien

Additional Installers

Spoiler (Highlight to read)
We purchased a PXI8101 w Windows 7 and using Labview 2012. In the other PXI slots we have PXI6230, PXI2564, 2503 and 4065. From the Knowledge Base I understand I must include DAQmx for the 6230 in the additional installations tab of the application builder. I'm going to port to a target machine.
1) What drivers do I need for the other PXI cards to include ( additional installations tab) or does the daqmx support those? The 2564, 2530 and 4065??
2) do I need to include the MAX config.nce file?? I've given my DMM and relay cards "names" in MAX but I thought that was just for my interaction. In other words when I call up a vi that uses the DMM the id is DMM. When you create the exe the front panel goes away so does it still need MAX??
3) There are links on some discussion grp pages that are suppose to take you to the latest RT engine for LV but they're blank. Is that only if you need to purchase?? We have the full developemnt sys. Is the RTE included?
Thanks
Solved!
Go to Solution.

Wow lots of questions, sorry if I miss any.
Lets start with the Run-Time Engine (RTE). LabVIEW's RTE is free for deployment EXEs. If you build a EXE, then you build an installer, under the Additional Installers you'll want to select the RTE for the EXE you built. This is selected by default so no worries there. Then when you install this on a fresh normal Windows machine, a basic normal LabVIEW EXE should run. Your EXE may use other toolkits and need more additional installers. Which ones is an educated guess if you are unfamiliar with it. In 2013 NI made a way for the installers needed to be automatically selected. I haven't tried this but bet it is prone to issues. It can be partially a trial an error process. Build the EXE, build the installer, run the installer on a fresh machine and see if it runs without error. If the EXE is broken it will try to suggest the component needed. Then you'll need to figure out what is needed in the additional installers to make it work.
In your case you will need DAQmx that is a given and you mentioned it. You will probably only need the DAQmx Core Runtime, and DAQmx MAX Configuration Support. Do you use a serial port? Then you'll also need the VISA Runtime. Do you use XNET? Then you'll need to include that. This will make your installers baloon in size, but it will include all the needed drivers for all DAQ hardware/VISA/XNET based on what is selected. The goal is to make a single installer that you run and a fresh machine can run the EXE with.
As for the MAX config. In your code if you reference a physical channel, virtual channel, task, scale, or hardware by the alias made in MAX then you will need this same alias on your deployed system. The easiest way to do this is probably to make an Export in MAX of your config, then in your installer settings there is a page for Hardware Configuration and you can provide a NCE file to get imported after the install is done. For this to work properly you'll want the hardware in the system before the install, otherwise you'll need to import the NCE again after the hardware is installed.
EDIT: Here is a link to the LabVIEW 2012 SP1 RTE. You don't need to download this, checking the RTE from the additional installers is all that is needed, but I wanted to show you the link where you can get the RTE for free.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Upgrade to LabVIEW 2012 caused Additional Installers issue

Hello again all you helpful forum-goers!
I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project. In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them. However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot). This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file. I need to have both 2010 and 2012 on my computer for the time being.
Does anyone have any idea what is going on with my system, and/or how to fix it?
Thank you very much in advance for your suggestions and time!
-Joe
Solved!
Go to Solution.
Attachments:
Additional Installers Blank Lines.png ‏45 KB

Hi Joe,
I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
jmorris wrote:
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
jmorris wrote:
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully.
One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
Please let me know if you have any additional questions/comments regarding these issues.
Regards
Doug W
Applications Engineer
National Instruments

Application Builder: Additional Installers Source Location

I am having trouble creating an installer for my application. I can build the installer when I only inculde the NI LabVIEW Run-Time Engine, but I also need NI-FieldPoint for LabVIEW Real-Time and NI-VISA Runtime. When I try to include these I run into problems.
I think the problem is that I installed some of these from the discs, but now my company has an installer on the network that I have used as well, so now I don't have the discs. Is there a way to change the Installer Source Location in the Installer Properties? When I try to build the installer I am asked if I have the discs, but I do not. I want to be able to get the installers from my company's network or maybe I can download them from ni.com and have them on my computer, but I need to know how to change the Installer Source Location.
I reinstalled NI-VISA Runtime from my company's network and the Installer Source Location changed to the network location (which is what I thought I wanted), but it still asks for CDs and if I click throught I get the following errors:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.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
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** End Error Report
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-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment

Hi Bob,
My most recent attempt gave me this error immediately after clicking Yes on the Distribution Needed window. I was never prompter for anything after clicking Yes:
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:MDFDistCopyList_CopyItem.vi
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
*** Abort requested.
Done building deployment
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 'FieldPoint 6.0.1' from: C:\Documents and Settings\Administrator\Desktop\FIELDPOINT_601_20080201_final\ to: C:\PPG\installer\PPG\
Copying distribution 'NI-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment
When I build the application, I get a lvapp.lib.tmp file in the temp directory, but I get no new temp files when I try to build the installer.
I would also like to point out that if if I uncheck FieldPoint 6.0.1 from the Additional Installers, and select either FieldPoint 6.0 or FieldPoint 6.0.3 (which are other optiions that show up in the list), I still get the same error as above that references 6.0.1
-Chris

Multiple additional SIP domains - certificate and DNS requirements

We've setup Lync 2010 Enterprise in our organisation and have successfully enabled a couple of thousand users.
This is working successfully internally, externally and through Lync Mobile.
However, we've only enabled users who are using the main company domain for SMTP and SIP addresses aaaaa_group.com (so all nice and easy so far!)
In other words, user A has a primary SMTP and SIP address of
UserA@aaaaa_group.com
However, due to numerous mergers and acquisitions over the years, we have quite a lot of users who have other primary SMTP addresses e.g. bbbbb_co.uk, ccccc_company.com, ddddd_ltd.co.uk, de.ccccc_company.com etc etc
There must be in excess of 40 to 50
of these other domains in use as primary SMTP addresses.
(Nearly all
these users have secondary SMTP addresses of aaaaa_group.com).
I have been told to approach this from a best practices point of view and give all users a SIP address that matches their primary SMTP address and calculate how much it will cost to buy certificates to cover enabling every user for Lync on all these domains.
I know from reading that wilcard certificates are considered to be a bad thing generally with Lync, especially if using Lync Mobility as the phone Lync clients don't accept them.
Wilcard certificates aside, what are the names that will I need to add to my SAN certificates? Presumably sip.domain.com, access.domain.com, meet.domain.com, dialin.domain.com, edge.domain.com, autodiscover.domain.com, lyncdiscover.domain.com
The potential cost of all these names is frankly getting pretty scary considering we currently use Verisign for all our cert requirements, and they charge like a wounded bull. However, I still need to report back with a cost of doing this, no matter
what it is.
Any thoughts/comments would be very welcome. :-)

Actually the Mobility clients for mobile devices (cell phones, tablets) DO support wildcard entries in the certificates, it's the Lync Phone Edition client (desktop handset devices) which does not work with wildcards. So you may be able to use wildcards,
but do plenty of research on how to approach this. Here are some articles to get started:
http://blog.schertz.name/2011/02/wildcard-certificates-in-lync-server/
http://blog.schertz.name/2011/02/lync-phone-edition-incompatible-wildcard-certificates/
That said, if you decide to skip the wildcard approach then you do NOT need to add additional entries for ALL FQDN types, only some.
For both the Edge Server external certificate and any internal Front End certificate you'll need to add the 'sip' FQDN for every domain to the SAN field.
sip.domain1.com, sip.domain2.com, sip.domain3.com, etc
The Front End certificate will also need the lyncdiscover and lyncdiscoverinternal
FQDNs, and the Reverse Proxy certificate will require the lyncdiscover
FQDNs.
For Exchange Server you'll need to an autodiscover.domainX.com record as well, although this can also be covered by the wildcard entry. The remainder of names (web conferencing, external web services, dialin, meet, etc.) can all remain in the primary
SIP domain only as these FQDNs will be passed in-band to the clients after they have successfully signed-in to Lync. Unless you need users to all user their own domain names for the SimpleURLs (which it doesn't not sound like in your scenario) then you'd
have to add all those as well.
So if you are not supporting any Lync Phone Edition devices I would try going with the wildcard route first to see how well things work. And even if you do have some of those devices you could simply add the 40-50
sip.domain.com FQDNs to both the FE and Edge certificate but still use a wildcard entry for the mobility clients, SimpleURls, etc. Just make sure that the certificates Common Name (e.g. Subject Name) is NOT the wildcard entry, use the primary
domain name entry in the CN and then place the wildcard entries in the SAN field. It is also best practice to duplicate the CN as a SAN field entry for the widest range of support by all clients.
For example:
Edge Server external certificate
Common Name: sip.domain1.com
Subject Alternative Name: sip.domain1.com, *.domain1.com, *.domain2.com, *.domain3.com, *.domain4.com,
etc...
Jeff Schertz | Microsoft Solutions Architect - Polycom | Lync MVP

How to include DAQmx device drivers in installer (LV 7.1)

Hi,
We would like to build an installer that packages all required device drivers and does NOT require a separate installation from the DAQmx device driver CD.
How can we do this?
LV : 7.1 with Application Builder
H/W : USB-6009
DAQmx : 8.0
Presently, we use the DAQmx device driver CD (that accompanied the USB-6009) to install the drivers. We do not want to do it this way because:
1) It makes the installation a two-step process - (a) install DAQmx from device driver CD (b) install our application
2) It installs a lot of drivers which are not required by our application.
Thanks,
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

Hello Gurdas,
This question of yours brings up an issue we addressed when we released LabVIEW 8.0. In LabVIEW 8.x and later, you have the option to package multiple additional installers with your application installer.
The issue you are having is limited by LabVIEW 7.1, as it is capable of including only one additional installer. However, if you would like to create an installer in LabVIEW 7.1 and have it launch multiple additional installers, your only option is to create a batch file and have the LabVIEW 7.1 installer call this batch file.
We have KnowledgeBases available to explain this issue and the topic of creating batch files. Here are a few of these documents:
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E?OpenDocument
http://digital.ni.com/public.nsf/websearch/B2640E34C4654F7B86256D07006D843D
Let me know if you have any further questions. Cheers!
Bob
Applications Engineering Specialist | National Instruments
-Bob

Create additional installer error code -12 file not found from device driver cd

I'm trying to build an installer for a project that includes several NI drivers - specifically NI-DMM. NI-SCOPE, NI-SWITCH, NI-845x, and a few others (MAX, DAQ, etc). When I build the software standalone (and only include the run-time engine), it works fine. However, when I try to build the installer with the additional installers (mentioned above), the build prompts me for device driver cds, and then fails. Specifically, it fails on the February 2006 Device Driver cd. The error is attached below.
I have tried
- repairing all the installations of the software mentioned
- using a new project and re-adding the files
- building the additional installers seperately (no source code installed)
- copying the driver cds to the harddrive and referencing them there when needed
The next step will be to reinstall all of those drivers from scratch, but I really would prefer not to. Does anyone have any ideas (or solutions) regarding this problem?
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> CDK_Engine_PromptForMissingDist.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
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-845x Software 1.0.1' from: C:\National Instruments Downloads\NI-845x\1.0.1\ to: C:\PTF\Builds\**********************<edited out>
Copying distribution 'National Instruments Device Drivers - February 2006, Disk 1' from: C:\National Instruments Downloads\DCD-Feb06-1\ to: C:\Program Files\National Instruments\Shared\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the file specified.
*** End Error Report
Done building deployment

I have had this happen a lot espescially with LV 8.0 -8.20. What I had to do was take the device drivers CD and copy it to the and run the installation of the software from the copy on the hard disk.
When you build an exe with additional installers it looks at the last place that you installed the drivers from. Anyway it worked for me so it might work for you.
Joe.
"NOTHING IS EVER EASY"

Additional installer issue - NI system component missing - DVD

Hi,
I have trouble building my installer... when I try to add DAQ and Measeurement & automation explorer, the setup is asking me to provide file (that in my head are supose to be already in my PC). It says to find NI system component on DVD 1 of develloper suite.
When I insert DVD1 of the labview DVD I received to install Develloper suite on my PC, it tells me wrong DVD!!!!! I understand nothing... see pictures... what is the problem???
Thank you for helping.
ET
Attachments:
images.docx ‏172 KB

I assume that the additional installers you are refering to are programs you are installing from the Developer Suite DVDs, and not something you are installing from an installer you built - right?
The NI Device Driver 2014 DVD does not include "all" drivers - but rather the most recent version of each. If you would like to see which versions are included, take a look at the following link, in the Description section:
http://www.ni.com/download/ni-device-drivers-2014.02/4634/en/
Your 2014 DVD is asking you to provide the 2012 DVD?
Regards,
Shane C
Applications Engineer
National Instruments

Multiple additional installers?

Similar Messages

Maybe you are looking for