Installing run-time engine 7.0 on windows NT

I attempted to Install Labview run-time engine 7.0 (LVRunTimeEng), on windows NT with workgroups 4, but got the message wrong OS. I am sure I downloaded the correct version (which is supposed to support Windows NT). Anyone have the same problem ? Anyone know how to fix it?
Thanks in advance
Jonny

This message comes from the MSI installer engine. The engine requires Service Pack 6 to be installed on NT 4.0 systems. Can you verify that you have this service pack.
Naren

Similar Messages

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • Error 1722 when installing Run-Time Engine 6.0

    I am unable to install the necessary LabView Run-Time Engine 6.0 required to run my VitalView Software.  I have reviewed the message boards and attempted all possible solutions: disabling anti-virus programs, following the NI support links: http://digital.ni.com/public.nsf/websearch/334E91287EDEA75286256D9B003A947A?OpenDocument.
    None of these methods will allow for the Run-Time engine to be installed.  What can I do?
    Help very much appreciated, thank you! 

    My OS is Windows XP.  
    I am trying to install an older LabView run-time engine since my application VitalView asks for a LabView 6.0 Run-time engine (or something compatible). 
    I have attached the jpg of the error message that I receive whenever I attempt to install the LabView engine.  
    Thank you so much for your help!
    Attachments:
    Error1722.jpg ‏57 KB

  • Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

    Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly).  I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine.  Is this a bug in the installer, or is there something else I need?

    LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular).  However, many people have had success installing to various flavors of Ubuntu.  You can search these forums using the key Ubuntu and find the problems they had and how they solved them.  If you cannot find an answer to your problem, let us know.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Installing Run Time engine question

    Hi,
    I am new to this and I am looking for information on how to set up a test system PC.
    I have the 2014 developer software and one test seat but need to know how to install the labview 2014
    runtime engine and anything else that I need in order to use this test system PC to run Labview and teststand
    applications that I create with my development system PC...
    Is there any tutorials or instructions out there that I can download that will tell me everything that I need to install and how on my target test system?
    Thanks

    the Installation instructions are on the Download Page
    Installation Instructions
    Close all NI software.
    Run the LVRTE2014_f1Patchstd.exe self-extracting executable and follow the prompts.
    Repeat these steps for all development systems where you want to install the LabVIEW 2014 Run-Time Engine (32-bit).
    The installation files for the Run-Time Engine are automatically extracted to a directory on disk. The installer does not remove the files after installing, if you want to remove these files from disk, be sure to note their location during the unzipping process.
    Jeff

  • LabVIEW Run-Time Engine 8.2.1 - Windows XP 32-bit

    Hi,
    Which version of the LABView runtime should i donload to work on 32bit ?
    there is only 64bit .....
    Kobi Kalif
    Software Engineer
    Solved!
    Go to Solution.

    Kobi_K wrote:
    Hi,
    Which version of the LABView runtime should i donload to work on 32bit ?
    there is only 64bit .....
    The naming of that download mentioned by Eduard may have somehow mislead you, but LabVIEW 8.2.1 was only available as 32 bit version ever. The download says that it works for Windows 2000/XP/Vista 32 Bit and also the Windows Vista 64 Bit platform, but no tests have been made on Windows XP 64 Bit for instance and you would be on your own trying to run it on there. As Vista and Windows 7 are mostly the same it should also work for Windows 7 32 and 64 Bit although since Windows 7 was not available when LabVIEW 8.2.1 was released it was never tested and might have minor issues.
    32 Bit applications will usually install just fine under 64 Bit Windows versions.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installati​on package for Run-Time Engine 7.0

    I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit).  The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading.  I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013.  Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0.  If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
    I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected).  How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0?  Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    Are you running your VI from a Project?  If so, you can look at Dependencies and get an idea what "dependent" VIs you might have.  There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
    If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it.  If all of your relevant VIs are in a single folder, add the entire folder.  Now look in Dependencies.
    BS
    Yes I am running the VI from within a LV Project.  After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
    1.  Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
    2.  Restart the PC
    3.  Open the project, close the project choosing to "save all"
    4.  Restart the PC
    5.  Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
    6.  Restart the PC
    7.  Open the project, close the project choosing to "save all"
    8.  Open the project and run the VI.  No more messages about LabVIEW trying to find Run-Time Engine 7.0.

  • How can I uninstall Labview run time engine from the machine?

    I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
    If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
    from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
    Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
    Can anyone suggest solution to my problem?
    Thanks,
    Chander

    J-Tek,
    I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Error 63 run-time engine

    Hi, I'm trying to communicate with an instrument through TCP/IP using AK protocol. I've created a VI that works fine on my PC where I have installed Labview 2011.
    When I create an executable from this VI to use it on a PC without Labview, it does not work and I receive the error 63.
    Of course, I've have installed run-time engine and also VISA run-time, and I use the same configuration on the port (same ip address and port).
    Moreover, the executable works also fine on my pc as well as the VI.
    Have you got any suggestion?

    Error 63 is "LabVIEW:  The network connection was refused by the server.". 
    Is the target machine on the same subnet as the instrument?
    No routers/firewalls between the two devices?
    Net nanny/web filtering/firewall turned off on the target PC?
    Instrument doesn't have to be configured to allow connections from the target machine's IP?
    My guess is network configuration.  Try pinging the instrument's IP from the target machine, see if that goes through.
    First thought was missing drivers/modules, but since you've got VISA and RTE installed, I think you're covered there.

  • Client view vi webpage without needing run time engine

    I am trying to create a environmental webpage attached to a Labview vi where end user can browse the web page from their home computer internet.  Problem is I read that the end user need to have the Run Time Engine installed in their computers, now this sucks. If the end users need to remember to install run time engine to every computer their visit, there will no business.  Is there someway to bypass this? 
    http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_html_documents_an/
    "If you want clients who do not have LabVIEW installed to view and control a front panel remotely, they must install the LabVIEW Run-Time Engine, then view the front panel remotely."
    Solved!
    Go to Solution.

    Hi sunflower2772,
    if you want to use the NI function of webserver, then you have to install the runtime engine (there is also a smaller one), the same as using some JAVA code.
    If you don't want to do this, then you have to write your own webserver.
    Mike

  • Can labview export shared libaray use in C++ without run-time engine?

    Hi, everyone
    Now, I write a VI for a algorithm and export it as a dll.  I use the dll in my C++ apps. It is good. But I want to know how my apps can run without labview run-time engine or I must  install run-time engine?

    you can install run time engine or include dll which will be used by your application.

  • Does Labview run-time engine 6.0 application created by Window NT can install & run on other OS?

    I created a Run-Time engine 6.0 application from my Vi and it is working fine! I wonder that this application can install and run on other OS system? What I have heard is "Yes" ... but I am not sure!
    Any one know for sure? Thanks.

    > I am sorry that I did not clarify my question enough, I meant other
    > kind of OS 's that are not from Microsoft Windows!
    >
    Across multiple OSes, you will most likely be able to load the VIs and
    execute them in the LV environment or rebuild the executable with no
    problem. But, you will not be able to run executables built for Windows
    on Mac, Solaris, or Linux. The reason is that executables have to meet
    binary standards, and those standards differ between the OSes. It
    really doesn't matter what language/tool the executable is built with,
    if it is the OS that is loading it, it will be specific to the OS.
    It would be great of someone like ISO or ANSI declared an executable
    standard that all OSes could load and execute, but since t
    he goal of
    executables is maximum flexibility and maximum performance, it is
    unlikely that this new standard would win out over the existing ones.
    If this comes about, the LV team will definitely be looking to take
    advantage of it.
    Greg McKaskle

  • LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

    I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs.  This happens near the beginning.  Is there a compatibility issue?  The window does not have any error messages.  It says: "Updating System, The features you selected are currently being installed."  The progress indicator blinks periodically, but does not move forward.  Please help.  Thanks!

    I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
    Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
    Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

  • Install labview 6.1 (or compatible) run-time engine with labview 2011

    I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new  equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
    Solved!
    Go to Solution.

    Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
    So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Maybe you are looking for