Multiple installs of runtime engine?

Are there any problems with multiple installs of LabVIEW 7.0 runtime engine.
That is, if I create an executable application with the runtime engine installer present and distribute it to a person who already has the 7.0 runtime engine installed, does this present any problems? Will the runtime engine actually be installed the second time? Will there be multiple entries in the Windows add/remove list?

The installer is designed to work that way. Multiple installs of the same version of the runtime engine should only increment the reference count on the files. When you install your built application you will not see an entry for the runtime engine in the Add/Remove Programs (ARP) list.
If you are familiar with MSI terminology, this behaviour is because the LV RTE that is included in your installer is just the merge module not the MSI. When you install the LV development environment, the RTE is installed from a separate MSI. Because your built app installer will use the merge module, the only way to uninstall the RTE will be by uninstalling your app.
Naren

Similar Messages

  • Run labview exe in other way than runtime engine?

    Hi guys
    This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
    -AA-

    If the runtime is only one out of 40 components, it should not make a big difference for you.
    I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
    There is also an idea to simplify all this. Please support it.
    (It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
    Message Edited by altenbach on 12-16-2009 11:42 AM
    LabVIEW Champion . Do more with less code and in less time .

  • Customizable Runtime Engine

    Hi,
    I am using LabVIEW 8.6 and I am interested to understand how to customize the LabVIEWRun time engine. Basically to shrink its size.
    I just create a sample program and installer with and without Runtime Engine.
    The VI and the projec is attached.
    The Sizes are,
    VI                                               ->      6.9 KB ( Just a UI with a loop)
    EXE                                            ->  151.0 KB 
    Installer without Runtime Engine    ->   10.4  MB  
    Installer with Runtime Engine         ->   74.7  MB
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Thanks,
    Pandiarajan R
    Certified LabVIEW Architect
    Attachments:
    RTE.zip ‏122 KB

    Pandiarajan wrote:
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Besides the options then you create the installer no. I think NI could have done it, but they do not dare. If the installer was more modular it would have resulted in a lot of extra support work for NI. As people hate to read read documentation. It is much more convenient to phone NI support and yell at them. So NI has taken the all or nothing approach. As a self defense. And I can not blame them. But I have to admit a modular RT setup would have been nice.
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • 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

  • Distribute CVI runtime engine without the installer ?

    Customer wants to distribute CVI runtime engine with their application in VB.net.
    They don't want 2 installer (one for VB.net, one for CVI).  They want to extract the files out of CVI installer, and included in VB installer.
    Any one did this before?
    For CVI 2013.
    TIA.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

    I use CVI and deliver CVI dll to customer.
    I don't create installer.
    Customer don't want installer.
    They use VB.net, they create their own installer.
    And they don't want to call CVI Run Time Engine installer.  That's the problem.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

  • Installer build wants wrong runtime engine

    LabVIEW 8.6
    Windows XP Pro
    When I build the installer for my application, it wants me to have available the install disk from November 2007.
    Expanding the list for that disk, I find that it wants the runtime engine for version 7.1.1.
    If I remove NI-DMM 2.9 from the 'National Instruments Installers to Include' list in the Installer Properties, the error goes away.  The description for that installer indicates it comes from the August 2008 device drivers disk.
    At one time I had other versions of LV on the computer.  I have removed all other versions, including the directories in c:\Program Files.
    My application uses the DMM device driver, so I assume that I need to check the box for the additional installer.  I've looked for more documentation on when and why I should select different items in the list, but couldn't find anything useful.  Would it be possible for the installer to automatically select those items required and perhaps let me direct it otherwise by choosing fewer or more items?
    Bottom line, do I need to select the DMM driver to ensure that my application will run on a computer that doesn't have LV installed?
     - les

    Hello all,
    I couldn't really understand what was doing on in the above questions and answers but from the forum topic I believe I am in right place. I have an issue similar to those desscribed above. I have LabView 8.6.0 installed on my computer but when I run LabView it starts asking for 'NI LabView Runtime 7.1.1'. I tried feeding in the labview 8.6.0 but it doesn't accept it and keeps asking for 7.1.1.
    The program used to run fine couple of months back and I then didn't use it for a while and I had other prgrams installed durig this time. And when this month I tried to use LabView it started giving me this trouble. I don't know what went wrong. I installed some ftdi chip drivers also. So, I am thinking if that kind of messed things up.
    Also, I have this windows installer message come up sometimes which is not when I open LabView but some other programs. I don't know if this windows installer has to do anything with it.
    Whatever the case it is could someone please help me figure out how I can get the right runtime work for my LabView 8.6 and if also possible how i can get rid of this windows installer message. I don't remember the error code right now because it comes up randomly. Next time I see it I am going to save that number. But in the meantime if anyone can help me with LabView 8.6. runtime engine problem.
    Thanks,
    Lovepreet

  • 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

  • Installer Build Error using LV Runtime Engine 2010

    I had an executable and installer working that were built in LV2009.  Since then I modified my source code and saved as LV version 2010.  I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed.  So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer.  However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
    Thanks in advance.
    Solved!
    Go to Solution.
    Attachments:
    Installer Build Error Message.docx ‏13 KB

    Hello,
    I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error 
    ------------------ERROR MESSAGE-----------------------------------
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    *** Error: Windows SDK function returned an error. (Error code -12)
    The system cannot find the path specified.
    *** Error Details:
    Error in MDF API function: _MDFDistCopyList_CopyItem
    Windows function FindFirstFile returned an error. Error code: 3
    *** End Error Report
    Done building deployment
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\ ***************** Error: Windows SDK function returned an error. (Error code -12)The system cannot find the path specified.
    ***************** Error Details:Error in MDF API function: _MDFDistCopyList_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
    --------------------MESSAGE END------------------
    In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
    Attachments:
    Additional.jpg ‏174 KB

  • Runtime Engine installer spawns from unrelated software

    Hello all,
    When I run a completely unrelated app (Quickbooks timer, in case you're wondering), Windows Installer launches and attempts to install LabVIEW 7.1 runtime engine. Has anyone else encountered this, and why would it occur? Is there an easy solution besides installing the runtime engine?
    Thanks

    Hello CT_JIM,
    We are probably seeing this behavior because your application (Quickbooks Timer) is querying Windows to confirm that all MSI installers are installed properly. In this case some part of the LabVIEW RTE must not have been installed completely and Windows is trying to correct it.
    This can typically be resolved by reinstalling or repairing the RTE to fix the install.
    Please let me know if you have any questions.
    Regards,
    Matt F
    LabVIEW Run-time Engine Version 7.1 for Windows 2000/NT/XP
    Keep up to date on the latest PXI news at twitter.com/pxi

  • Runtime engine 8.6.1 on Labview 11

    Hello,
    I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it? 
    And if I downgrade to Labview 10, will i solve this issue??
    Thanks in advance!!

    This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
    What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
    Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
    Sergey Kolbunov
    CLA, CTD

  • Several question s about runtime Engine, application builder and labview player

    I am a little confused by all the options to distribute a program.
    Please help bij answering (one of) the following questions:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    3. What is the advantage of the labview player above the runtime Engine?
    All questions refer to the latest software versions of NI software
    Thanks in advance,
    Regards,
    Ferry

    ferry1979 wrote:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
    If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
    The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
    (In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
    (Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    No. See above.
    3. What is the advantage of the labview player above the runtime Engine?
    The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
    Message Edited by altenbach on 08-21-2005 10:05 AM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    runtime.png ‏24 KB

  • Installing LabView 8.2 runtime engine on Windows 7 64-bit

    We have a product built on LabView 8.2
    For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
    Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
    Our verification team has confirmed this to be true.
    Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
    How is this possible?
    Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
    We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
    Any thoughts would be extremely appreciated.
    Attachments:
    lv_install_error.jpg ‏22 KB

    No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • Runtime engine files 8.2

    Hi,
    Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
    "Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
    Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
    Thanks in advance,

    I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
    If somebody know, please tell us......
    Benoit Séguin
    Software Designer

  • Runtime engine installatiion aborted

    HI,
    I am trying to install LV runtime engine 7.1 on a user's machine and
    see the error "Installation aborted, A higher version of this product
    is already installed". I checked the registry, C:\Program Files and
    Control Panle --> Add remove programs for any traces of already
    installed versions but couldn't find any. To the best of my knowledge,
    I can say that this machine does not have any other versions of LV. I
    attached a picture with the error messages. I am using windows 2000 and
    was logged in as administrator, when this problem occured.
    My question is does anyone know if the runtime engine installation
    checks any particular registry settings for information about 
    previously installed versions and hence does not allow the user to
    proceed with the installation.
    Deepak

    The Run-Time Engine installer shouldn't check to see if any previous or future versions have been installed. The reason is that multiple versions of the RTE can be installed on a given computer. This is actually necessary in many cases, since applications built with a certain version of LabVIEW require that version of the RTE to run.
    I haven't heard of this specific error occurring. I would recommend downloading the following site and downloading a utility called msiblast.exe. This should detect any hidden installers for NI software on your machine. Remove any that you find. You might also check out this Microsoft knowledge base on the msicuu.exe utility that helps clean up installers. This utility could help clean up configuration settings for any Windows installers as well as registry information that might be left behind.
    Let me know if either of these utilities helps out.
    Jarrod S.
    National Instruments

  • Labview trying to find runtime engine when opening up VB6

    This is bizarre. I'm not even trying to open a labview program, and I get this error.
    when I go to open up VB6 from Visual Studio (Visual Studio 6, Enterprise Edition), I get a pop-up saying that the Labview runtime engine 7.1.1 is going to be configured. A new window then pops up, because it can't find the lvruntimeeng.msi file.
    Problem is, I'm using Labview 8.2.
    Worse, now my VB6 programs are hanging if I close out of all the installer boxes (it does this multiple times).
    UPDATE-4:42PM EST-
    I noticed when I went into Add/Remove Programs in the control panel, when I clicked on Change for National Instruments, it says that only the 7.1.1 Runtime Engine is installed. However, I can not uninstall it because another product relied on it. I also downloaded the 7.1.1 runtime engine, but it doesn't install because it says a higher version is already installed. (?)Message Edited by Dauntless on 12-26-2006 03:46 PM

    There are some NI programs which were written in LabVIEW and so need the LV RTE in order to run.
    Theoretically, the RTE should be properly installed when these programs are installed, but for some reason maybe it wasn't. Maybe one of the NI services running on your machine tries to do something when you're opening VB or maybe your code calls some NI component?
    I used to have something similar where for some reason going into certain websites prompted me to insert the LV 7.1 CD so that I can configure the RTE. I think it stopped after doing it one time.
    You can try downloading the 7.1 RTE and installing it to see if it will stop. If not, you can try pointing the dialog at the MSI once to see if that will stop it.
    Try to take over the world!

Maybe you are looking for