LV 2013 Runtime Install wants 2012 disk ?

[dacad]

I am using a blank project to create an installer to install just the LV 2013 runtime along with a few additional drivers, all listed on the device drivers disk.  See list:

NI IVI Compliance Package 4.6.0

NI LabView Runtime Engine 2013 F2 (minus Realtime support and non-english language support)

NI MAX 5.5

NI System Configuration Runtime 5.5.0

NI-DAQmx Core Runtime 9.7.5

NIDAQmx MAX Configuration Support 9.7.5

When I highlight each one in the Additional Installers section of the Installer Properties dialog box , it shows location as either being on my system already or on one of the 2013 disks.

When I goto build however, it is asking for one of the LV 2012 disks.  I never even installed version 2012 on my machine, just 2011 and 2013.  Here is the dialog box I get and again when I uncheck the Dev Suite 2012 DS1 DVD 1  disk selection.

 

If I check the February 2012 Device Drivers selection, the error message goes away but since I am just creating an install for 2013 and support for that version only, why would it ask me for a 2012 disk at all ?   shouldn't all the files be on the 2013 disks ?

Checking the 2012 DVD 3 selection does not make the error message go away.

I tried unselecting the additional drivers one by one.  Unchecking the NIDAQmx MAX Configuration Support 9.7.5  option got rid of the error and the requirement for a 2012 disk.   Is this inherently included in one of the other selections ? 

Description is that it is used for configuring NI hardware in MAX.  Kinda think I would need that.  My system has this version installed and it came from the 2013 disks.  It is listed in the software section of MAX as a separate component.

Any thoughts?

Thanks

[BobRodge]

Hi Doug,

I believe I could have an explanation to why the Installer is asking for LabVIEW 2012 DS1 DVD 1. 

The Developer Suite editions of LabVIEW are named based on when they are released. For example, LabVIEW 2012 DS1 is released in early 2012, but is actually LabVIEW 2011 SP1, since LabVIEW 2012 is not released until later in 2012, which is named LabVIEW 2012 DS2.

The same naming convention applies to the LabVIEW 2013 Developer Suites.

Below I have attached links that describe the components of each Developer Suite listed in your screenshots.

NI Developer Suite 2012 DS1:

http://www.ni.com/pdf/manuals/373293c.pdf

NI Developer Suite 2013 DS2:

http://www.ni.com/white-paper/14629/en/

Hope this helps!

[dacad]

I understand what you are referring to but I am trying to create a runtime installer for LV 2013 specifically (Yes, I am working with Dev Suite).  The disks are all referenced as 2013 DS2 DVD 1, 2 or 3 and then the DCD_August13 Drivers Disk.

All the required installers should be on these disks to make the runtime installer for 2013 support only.

Am going to try and make an installer where only 2013 is installed on the computer (mine has 2011 installed as well but I am trying to make the installer in the 2013 environment)

The element that is causing the issue appears to be   NIDAQmx MAX Configuration Support 9.7.5.

Will post what the results are of trying on alternate machine.

Thanks....

[dacad]

I have completed crating the 2013 runtime installer on another maching that has only LV 2013 installed from the 2013 DS2 disks.

As I pretty much expected, it was able to find all of the required installers from these install disks and did not require any previous version disks.

My guess is that since I have 2011 installed on my machine and it appears that the version of NIDAQmx MAX Configuration Support 9.7.5 did not change between the two versions [of LV] that it automatically pointed to where it was originally installed from [the 2012 DS 1 disks].  I did use the 2012 DS1 disks to install LV 2011 which is what it asked for on my machine.

What doesn't make sense to me is that if I am making the installer for 2013, it should, by default, look to include the most recent version of all the components and use the individual installers from the disks used for that version [2013] to create the runtime installer that I have configured.

Got it worked out but I think this needs a bit of attention on future versions.

[BobRodge]

Hi Doug,

I am happy to hear you were able to resolve your issue! This is definitely a strange behavior, and I will see if I can find some more information about this on our end. 

If any other problem arises with this, please update this forum.