Additional installers

Similar Questions

• Blank Page for people with disabilities and additional installers

  Hello friends,

  First of all, I would like to thank NOR & veterans on the maintenance of this vast and useful forum where we can find solutions to almost all of our problems.

  I recently faced a problem when creating Setup program for my application (first time use). I found that page additional installers required to add the runtime and Daqmx drivers was empty and even the disabled (see the image attached). I tried to repair my Installation of Labview 8.2.1 (I also have Labview 8.0 installed on the system) but cannot correct the problem.

  Can someone offer please soultions or advice for my problem?

  Thank you

  Magalie

  
  

• Additional installers do I need to use the web server?

  I am building an application in LabVIEW 8.6 and want it includes the Web of LabVIEW server and eventually Web Services.  Should additional installers I include?  In addition to the runtime, the following options are: 'LV Web Services', "NI LabVIEW Run-Time Engine Web Server", "NI LabVIEW Web Server."  I can find no documentation explaining the differences between these - especially the last two.

  Hello Nathan,.

  From 8.6 web server is a separate component. Just as LabVIEW desktop is a separate installation program since the runtime if there is a web server for each component. In addition, Web Services is a component that is generated on the web server.

  So, if you need web server in the Office two, LabVIEW and RTE and you eventually will need to deploy web services, as well, then you'll need to install these components.

  Here's our FAQ to get Web services work - you might be useful.

  FAQ Web services

• Upgrade to LabVIEW caused 2012 issue additional installers

  Hello again all you lovers forum useful!

  I've been using LabVIEW 2010 (SP1) for awhile on my Windows XP computer, but I recently bought and installed LabVIEW 2012 for a future project.  In the meantime, my previous projects should always use LabVIEW 2010 until I use the tracking system of formal changes to my company to upgrade.  However, when I opened recently one of my old projects in 2010 to update and rebuild the installer, I saw in the tab other installers a bunch of empty lines at the end of the list (see screenshot).  This is not directly the hurt, but I think it's a symptom of the root problem.

  Most directly concerned, the NI VISA Run-Time 5.0.3 which had been checked before was now gone and the NI-VISA Run-Time 5.2 driver which had replaced it has NOT been verified.  That seems like an upgrade oops on part of National Instruments for me.  I decided that it was just a thing, and that the installer of 2012 had replaced my 5.0.3 version with version 5.2 (removal of the old version), so I checked the version 5.2 to build my Installer, and after having demanded that my DVD to copy the software on my computer, which seemed to work ok.

  Now the immediate problem: when I distributed the project file to a colleague that has LabVIEW 2010, she was not able to build my software installation, because he asked her to drive "FADEC_Emulator".  "FADEC_Emulator" is the name of my software.  Expansion of the error dialog box showed that he wanted the drive for access to NI VISA Run-Time 5.0.3.  Open the properties of the installer in the project file in LabVIEW showed NEITHER VISA Run-Time checked 5.0.3.  However, the project of opening with Wordpad file showed that NEITHER VISA Run-Time 5.2 has been listed as an extra Installer (and NOT 5.0.3  Maybe its system because I wanted NEITHER VISA Run-Time 5.2 and replaced it automatically with the latest version, he had, 5.0.3?  Confusing!  And if he did it, why he had that version already practicing?  And versions of switching as it seems it would be a bad idea to do it silently, in case I was counting on a specific feature of the new version.

  I'm afraid that since installing LabVIEW 2012 my system got in an unstable state, and now I possibly corrupted my LV project project file.  I need to have in 2010 and 2012 on my computer at the moment.

  Does anyone have an idea of what's going on with my system, or how to fix it?

  Thank you very much in advance for your suggestions and time!

  -Joe

  Hey Joe,

  I tried to reproduce your problems and met with mixed results. Please check with what I have provided below that we test in the same conditions

  jmorris wrote:

  Most directly concerned, the NI VISA Run-Time 5.0.3 which had been checked before was now gone and the NI-VISA Run-Time 5.2 driver which had replaced it has NOT been verified.  That seems like an upgrade oops on part of National Instruments for me.  I decided that it was just a thing, and that the installer of 2012 had replaced my 5.0.3 version with version 5.2 (removal of the old version), so I checked the version 5.2 to build my Installer, and after having demanded that my DVD to copy the software on my computer, which 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 above configuration. When I opened the project from 2010 to 2012, VISA Run-Time 5.2 has been verified (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install correctly.

  jmorris wrote:

  Now the immediate problem: when I distributed the project file to a colleague that has LabVIEW 2010, she was not able to build my software installation, because he asked her to drive "FADEC_Emulator".  "FADEC_Emulator" is the name of my software.  Expansion of the error dialog box showed that he wanted the drive for access to NI VISA Run-Time 5.0.3.  Open the properties of the installer in the project file in LabVIEW showed NEITHER VISA Run-Time checked 5.0.3.  However, the project of opening with Wordpad file showed that NEITHER VISA Run-Time 5.2 has been listed as an extra Installer (and NOT 5.0.3  Maybe its system because I wanted NEITHER VISA Run-Time 5.2 and replaced it automatically with the latest version, he had, 5.0.3?  Confusing!  And if he did it, why he had that version already practicing?  And versions of switching as it seems it would be a bad idea to do it silently, in case I was counting on a specific feature of the new version.

  In this case, I built the installation program on LabVIEW 2012 with VISA RT 5.2.0 then saved for LabVIEW 2010 compatibility. When I open the installer in a LabVIEW with VISA 5.0.3 2010 environment, VISA 5.0.3 has been verified (as planned since LabVIEW by default to the latest version of VISA on the PC, no matter what the original installer referenced). I did, however, see three additional empty lines in the additional installers (see below) tab. I also tried to build the Setup program that you have indicated, but did not get all the guests for the discs and was able to successfully build.

  One thing to keep in mind is that default LabVIEW uses the version of the driver that is installed on the PC version, whether it is newer or older than the installer references. If you feel that this has a negative impact on your success as a developer, please do not hesitate to post a feature request (for example, a guest at changes of the version of the driver) in our forum for the exchange of idea (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).

  Finally, regarding empty lines in the additional installation specifications, this problem seems to be fixed in LabVIEW 2012 and manifests itself only in 2010. During my trial class, this does not affect installers of construction and is a minor inconvenience that has been fixed in later versions.

  Please let me know if you have other questions/comments on these issues.

  Concerning

  Doug W

• NOR-DAQmx run options under additional installers are not displayed

  At halfway in this FAQ (http://zone.ni.com/devzone/cda/tut/p/id/3021) talks about the various Runtime options available when you include the NOR-DAQmx driver in a LabVIEW Installer - they are full and 5 different options of operation. I have 2011 LabVIEW and NOR-DAQmx 9.3.5; the only installation type I see is complete. No idea what I may have missed to install or configure correctly?

  Thank you

  Jorge

  Hi Jorge -.

  You make an excellent point raise this question.  The reality is that the documentation is a bit a type-o.  The latest version of DAQmx which allowed this ability multiple-install type was 8.7.1 that allowed full, TERM 3 and 5.  Version 8.6.1 allowed all full of Runtime and RT 2-5 selectable options.

  This was changed in the development of the installer because features such as Measurement & Automation explore (MAX) by omitting makes it much more difficult to program source files that use the DAQmx driver.  Limited choice DAQmx Installer problems in future development. SignalExpress is also omitted in some versions.   This change was made in order to avoid questions that were considered to be a problem when the installers have been created with these minimalist installs.  So I'll make this change to the Developer Zone confusion invites future readers.

  I really appreciate your message and bring it to our attention.

• Additional installers list empty

  Hello

  In mdffix.reg

  Windows Registry Editor Version 5.00
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MDF]
  "CommonAppDataBin"="C:\\Documents and Settings\\All Users\\Application Data\\National Instruments\\MDF\\Bin\\"
  "CommonAppDataProductCache"="C:\\Documents and Settings\\All Users\\Application Data\\National Instruments\\MDF\\ProductCache\\"
  

  In mdffix_vista.reg

  Windows Registry Editor Version 5.00
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MDF]
  "Path"="C:\\Program Files\\National Instruments\\Shared\\MDF\\"
  "CommonAppDataBin"="C:\\ProgramData\\National Instruments\\MDF\\Bin\\"
  "CommonAppDataProductCache"="C:\\ProgramData\\National Instruments\\MDF\\ProductCache\\"
  "Version"="2.7.1.128"
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MDF\Bin]
  "Path"="C:\\Program Files\\National Instruments\\Shared\\MDF\\Bin\\"
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MDF\EULAs]
  "Path"="C:\\Program Files\\National Instruments\\Shared\\MDF\\EULAs\\"
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MDF\Manifests]
  "Path"="C:\\Program Files\\National Instruments\\Shared\\MDF\\Manifests\\"
  

• Need to find installers DAQmx and LabVIEW. Lost installation CD.

  I have LabVIEW full edition and the Application Builder.  I am trying to build a stand-alone application with the application builder and I need the following additional installers:

  OR LabVIEW Run-Time Engine 2010

  NOR-DAQmx Base Runtime 9.1.5

  I lost my CD to install LabVIEW 2010.  These installers are available on the Web?  I tried without success.  Thank you for your help.

  RogerK wrote:

  I have LabVIEW full edition and the Application Builder.  I am trying to build a stand-alone application with the application builder and I need the following additional installers:

  OR LabVIEW Run-Time Engine 2010

  NOR-DAQmx Base Runtime 9.1.5

  I lost my CD to install LabVIEW 2010.  These installers are available on the Web?  I tried without success.  Thank you for your help.

  Hello

  You can download the run time of the website NOR, as also the DAQmx

  LabVIEW:

  2010SP1

  http://Joule.NI.com/nidu/CDs/view/p/ID/2292/lang/en

  2010 min 32 bits

  http://Joule.NI.com/nidu/CDs/view/p/ID/2088/lang/en

  2010 standard

  http://Joule.NI.com/nidu/CDs/view/p/ID/2087/lang/en

  DAQmx Base:

  9.5.1

  http://Joule.NI.com/nidu/CDs/view/p/ID/2934/lang/en

  9.1.7

  http://Joule.NI.com/nidu/CDs/view/p/ID/2206/lang/en

  Just search in blogs or any time of the performance you need.

  You can even download drivers daqmx if needed

  http://Joule.NI.com/nidu/CDs/view/p/ID/2934/lang/en

• Inclusion of additional installation

  Hello.

  for one of my application, I create Installer and it asks additional installers such as lv DURATION, dacmx, nor-usi 15.0 but I can not able to locate the path of these additional setup programs, I want to know where are these additional installers and how to add these installers to my application installer

  Note: I use labview 2015 in my development system, I have two DVDs would be driver suite and or developer.

  Yes I'm pointing my path to disk when the request path Installer but still it is showing dialogue this installer not found

• NOR-RIO as not installed additional Installer 4.0

  I have converted my LabView 8.6.1 project 2011 SP1. The output of the project is a Setup program that includes the additional installers as 4.0 OR RIO. This avoids to install these drivers manually on the test PC. Test PC has a card of the R series FPGA. Only when I install the Setup program generated on the PC NOR-RIO of test driver is not installed. Everything seems to work fine (after installing this driver manually). Anyone have an idea what may be wrong?

  Hi Thierry,.

  Thanks for your reply. I managed to fix it myself. I added the extra 'NI R Series 4.0' installation program probably is not part of NOR-RIO 4.0 more when add you it as an additional installer (but it is part of RIO OR when you install from a DVD). I looked before, but I forgot the first time (prior to the announcement of my problem). .

  Kind regards

  Biker

• When I run the exe file, it should load the niscope_32.dll why?

  Hello:

  I used scope in my program functions,

  and then I did it in the exe file and the installation file,

  but when I make them to another computer,

  To load the niscope_32.dll, what should I do?

  Hi ylongwu,

  You will need to install the driver OR-Scope on the deployment computer so that the code you can call the driver. You can download the driver from our Web site at drivers and updates the link below by searching our driver OR-Scope and choosing the appropriate version. I also recommend that you include the NOR-Scope driver as an extra Installer for your executable. In the setup of window construction there is a category called additional installers where you can choose the drivers and execution engines to install with your executable file. I've included a screenshot to show what it will look like for LabVIEW 8.x.

  Drivers and updates
  http://Joule.NI.com/nidu/CDs/fn/p/lang/en

  

• Serial communication does not work in an executable file.

  I created a vi that communicates with a serial device. It works fine on the computer on which it was created on. I then created an application and then built an installer to put it on another machine. The second machine doesn't have a LV 2009 on it. Once installed on the machine the vi does not work. When it is running on the computer with LV 2009 the com port control is a pull down, and it lists all agrees on the computer, and then you select the one you want to connect with. The vi is installed on the computer does not list the available com ports. This leads me to believe that there is no support Comms series in the installable version. What should I do now? I noticed that you can add "Additional installers" when you build the installer and one of them is NEITHER Serial 3.4. I'm trying to add this and a message says that he had to get, so I used it thinking it was more that I needed and this standard com port driver would be included. Am I mistaken or did I miss something? Any help is greatly appreciated.

  [email protected]

  I'm sure that NEITHER Serial is the driver for COM port cards of NEITHER, and that very probably that you have to install NI-VISA.  You can add the VISA installer as an extra Installer for your application.  It may ask you a DVD during the build process, because even if the software is already on your computer, the installer so it probably isn't.

• NOR-MAX for VISA DURATION 4.2

  Hello

  I posted this on the Narcotics Control Instrument, but maybe it's not in the right place since I didn't get all the answers. Here's my question:

  I have been looking for more than an hour and have not led to what. Is there a version of the NOT-MAX runtime? I have deployed executables LabVIEW on many other PCs and I encounter a problem on one of them where the resource VISA vi does not return the exact list of the COM ports even as drop-down list of the vi box VISA set up a Serial Port. For example, the list box might show COM1 and COM4 COM10, but VISA resource find vi shows ASRL1::INSTR, ASRL4::INSTR, and ASRL12::INSTR (should be ASRL10::INSTR). So I need a program such as NOR-MAX to change the alias on the PC with the execution of VISA 4.2 engine so that it corresponds to what shows the VISA configure Serial Port vi, incidentially, that matches what is shown in Device Manager.

  The PC in question does NOT the LabVIEW development environment installed, so it has NEITHER-MAX. is there a stand-alone exe OR-MAX I can install it on other PCs without the IDE LV? Manual change of visaconf.ini will do the trick? If so, is that what I should remove all aliases, uninstall all external (VCP) ports in the Device Manager, restart the PC (or not) and start again, reconnect the devices?

  Thank you for any help or advice.

  Ed

  James,

  Thank you for your response. Yes, I use the Application Builder and no, I chose not install NOR-MAX, but I see there in my file of project under "additional installers. I will consult the installer to run from the Web site of NOR.

  After that I posted this question, I have experienced yet. I have manually edited visaconf.ini so that numbers ASRL agreed with Device Manager of / ' Windows port assignment and low and behold, it worked! If this happens on the PC client, installation of MAX would probably be best solultion, however.

  Now I'm wondering if the VISA resource find vi is just read this file? I guess that Yes.

  Thanks again,

  Ed

• Need HELP! -The installer and excutable issues

  Hello

  I created a Labview installation program to install an executable file (.exe) on a clean machine, who has no any product of Labveiw, so the executable can run by itself without the evoriment of development. Given that the program needs to use sub - VI DAQmx so I include the engine runtime and DAQmx and everything that makes setup > 1.2 GB. At first everything went well.

  Now, we have to make some minor changes in the source code. My question is, what do I have to redo the installer every time for minor changes? I've seen the system creates several files when I build an executable:

  An .exe file

  A single file .aliases

  A configuration file

  A "Data" folder

  Can I just copy these files to a place so new version of the executable file can run without HAVING to build a new installer which exceeds 1 GB?

  Any help or suggestion is greatly appreciated!

  This is the same process as the regular creation of an installer.

  Way the easiest is probably to copy your existing full installer and then removed the additional installers of the copy and rename your copy as a hotfix.

  (i.e. make sure you just deselect the additional installers of the page indicated on the attached screenshot)

  

• Cannot create an installer containing IMAQdx in 2014 of LabVIEW

  I have a strange question in the generation of installers with a function IMAQdx in LV Application Builder 2014.

  When I was building an installer for an executable file using IMAQdx in 2013 LV, Application Builder automatically selected additional installers needed and IMAQdx drivers (Vision Acquisition) were one of them. Now I'm trying to build the project even in 2014, but in the additional installers, I see only NOR-IMAQdx DURATION 14.0. When I build the installer in 2014 LV, the size of the file is about 300MB opposed to 900MB of the installer which has been built in 2013 of LV.

  When I run the installation program from 2014 on a 'clean' Windows, install and run any application that uses IMAQdx, I do not see the cameras connected. This problem is fixed after manual installation Vision Acquisition software of DVD drivers for the device OR. After that, I can see all the cameras in the application and in MAX.

  I tried to manually add additional installers in 2014 LV, but nothing helped. It seems to me that there is no way drivers IMAQdx bundle in LV Application Builder.

  I found a post related to this and I wonder if someone can reproduce this behavior before dropping off a CAR. I have attached a simple project with a simple VI and installers of the sample in for testing. The VI allows you to select a camera (e.g. a webcam) and video image.

  Hi martin.zmrhal,

  What you see with only the Vision Acquisition Software runtimes (VAS) available in the list of installers extra is expected with the latest behavior.

  Before Vision Acquisition Software (VAS) August 2014, programs additional installation to after-sales Service, namely OR-IMAQ, e/s NOR-IMAQ and NOR-IMAQdx not only includes the runtime components but also for LabVIEW application development support. GO August 2014 and later, now only allow us the deployment of runtime components. This gives the advantage of a substantially reduced Installer size, but you can include more support development (ADE) LabVIEW applications is in the installation program.

  This change aligns Vision with LabVIEW behavior and most of the other products OR you cannot deploy generally support the complete development of a product, but rather only the runtime components. If you need to install GO with ADE on your deployment machine, you will need to distribute the complete Installer GOING on this machine in addition to LabVIEW (to make use of the SAV ADE support). To do this automatically, you will need to write a batch file to run the installer for LabVIEW, then IMAQdx.

  With respect to the second issue of not being able to see the camera, I think that what you are experiencing is that the drop of the control Session is dimmed and you cannot click on it to see a list of the cameras on the system. It is also the expected behavior for the runtimes are going TO. This does not mean that the driver is not well that discovery of cameras, and you can test this by typing the name of the camera in the Session control (for example "cam0" for the first discovery of camera on the system).

  What we are looking for with this behavior, is for vision applications deployed to abstract the end-users camera selection process. Ideally, your code must list programmatically cameras with IMAQdx list Cameras.VI and then determine what device (based on the type of bus, serial number, model number, etc.) to the target. We are working on an application note paper that clearly explain with some examples, but the idea is similar to this example of community for NI-DAQmx devices: https://decibel.ni.com/content/docs/DOC-10014.

  I'm sorry for the current lack of documentation on these features, but without a doubt, we are working to provide examples useful and other items in the knowledge base at this address. I'll post a link to the content as soon as it is available.

  In addition, Vision Acquisition Software August 2014 f1 went live yesterday: http://www.ni.com/download/ni-vision-acquisition-software-august-2014-f1/4974/en/. The patch is also available through the Update Service, and it is strongly recommended that you upgrade if you still use drivers of August 2014.

  Kind regards

  Joseph

• build specification missing properties

  I created a build specification for my project, but the tabs for the information in the dialog box, shortcuts and additional installers are missing.  See attached screenshot. How can I make it appear?

  David

  You will create two specifications: (1) build the exe. (2) create an installer for the exe. One you have both in your project, you can do a "build together" when right-clicking on the header section of specifications of generation.