Does Labview run-time engine 6.0 application created by Windows NT/2000 can install & run on UNIX

LabVIEW exe created in Windows and running in UNIX

LabVIEW source code from one OS can be ported to another OS (except for OS specific things like ActiveX) but executables cannot. You would need the unix version of LabVIEW and it's app builder to create an new exe.

Similar Messages

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

NI Vision Run-Time Engine 8.2 - Error user is now getting when attempting install of built software

I've built an installer for an application using LabVIEW 8.2 and Vision8.2. I have sent this installer to someone for 6 months and they have had no problems completing the install.
Now the last time that I sent the installer, the user is getting the attached error during install.
"NI Vision Run-Time Engine 8.2
Error: Another installer or uninstaller is running.
Finish that installer or uninstaller and try again."
When the user clicks OK to this error, the user is then told to restart or finish uninstall. Since we do not know what uninstall is being asked for, the user restarted the computer and attempted running the software - to which he was prompted for LVWA.dll file and he did not know what to do from there.
I gave the installer to a second beta-tester - the same thing occurred.
The only thing 'of significance' that has changed in my software that I can think of that is Vision related is the inclusion in the software of the ability to read/write .TIF files. I have no clue whether that might have anything to do with the error.
Any help is appreciated. NI - I can post the installer ZIP to your ftp site if you want.
Sincerely,
Don
Attachments:
error.jpg ‏30 KB

Hello Don,
Have you tried uninstalling the previous Vision run-time
engine on the deployed computer before running the new installer? You
might also want to try running the Vision RTE separately from the installer to
see if you are able to manually run it on the target. Here is a document which explains the
procedure for both manually installing the RTE as well as how to include it in
the LabVIEW installer:How do I
Deploy LabVIEW 8.0 and 8.20 Applications with NI Vision 8.0 and 8.2?
I also found
a Knowledge Base that may be helpful addressing the error you mention in your
first post. I hope this helps.
How Do I
Correct the "Another Installer Is Already Running" Error Message?
Regards,
Vu D

Problem to install the Run-Time Engine 6.0.2 on a Windows XP

Hi,
A client tried to install our application on a new computer with Windows XP Pro. The application was developped on LabVIEW 6i, so he has to install the RTE 6.0.2, like it was on the old Windows 2000 computer.
The installation of this RTE is OK, but it disturbs completely the "Add/Remove Application" windows of the Control Panel (See attachment).
And then our application is very very slow !!!
Our client installed then the Service Pack 2 for XP, that didn't change anything.
Is there a possibility to use correctly a LabVIEW 6i-application on a Windows XP SP1 or SP2 ?
Now the client is thinking to transfer directly this application on a Windows 2003 server, is it possible ? Is there a already known problem to do it ?
The application is used to do the monitoring of geological movements and is therefore very sensitive and should run fine, without any trouble !!! We can't be unsure !
Many thanks in advance for any help.
Best regards,
Gerald Monin
Attachments:
RTE_XP_prob.gif ‏26 KB

Hi,
Regarding the blank space in the add/remove programs list, please look at the following link
http://digital.ni.com/public.nsf/websearch/9D43413E0F8289B586256DD50072EDFB?OpenDocument
Regarding the slow execution, I would suggest to upgrade the LV environment to 6.0.2 as well and create an installer with the RTE included to be sure to have the right version installed on the target machine. If not, then please give more info's about what is executing slower (the hole application, acessing HW,ports...).
Porting the application to windows server 2003 is not the best idea, because LV in general is not supporting it and lv 6i is released a long time before windows 2003 server was. But i know a lot of people which are using lv 7.1 on windows server 2003 successfuly.
I hope it helps!
Regards,
Evrem

What creates a windows error 126 when installing/running iTunes and how do you fix it?

My install and reinstall keep failing with the above message. It also states MSVCR80.dll is missing. How do I resolve this issue? thank you.

Try the following user tip:
Troubleshooting issues with iTunes for Windows updates

Distribute application without labview run-time engine

I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
Solved!
Go to Solution.

Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
Attachments:
NI software.jpg ‏98 KB
Installer.jpg ‏216 KB

Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
Attachments:
windows.jpg ‏26 KB

Hi,
There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
Zvezdana S.
NAtional Instruments

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

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.

Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE

What's going on here? I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer. When I open VB6, I always get what looks like a Windows Installer error:
First, it asked me for the location of "lvruntimeeng.msi", which I located for it. The next progress-window says:
NI LabVIEW Run-Time Engine 7.11
Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
Finally it fails with this error-message window:
NI LabVIEW Run-Time Engine 7.11
Error 1334. The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
[OK]
The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay. What can I do to prevent this error?
Message Edited by citizenDAK on 04-23-2008 01:34 PM

Yes it occurrs every time I launch VB6.
For a long time now, at least many months. It's not every day that I need to open good old VB6. I was hoping it'd just 'go away' but it hasn't.
I don't know what changes lead up to it. LOTS of things have been updated, security-patched, etc... (It is XP.) I've even un-installed the runtime, then re-installed it when I kept getting the same prompt. Don't have any idea why, I was hoping you could tell me from the specific file named in the error. (Google didn't find it for me, and neither did searching ni.com)
p.s., Sorry I left out a decimal and copy/pasted it several times... should've said "NI LabVIEW Run-Time Engine 7.1.1"

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation 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.

System Error 31 while loading the LabVIEW Run-Time Engine

I'm getting the following error message. I've attached a screen shot of it as well.
System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
I'm trying to update an instrument running Windows95. What is system error 31? I can't find anything on it using Google or the forum's search function.
The instrument is a Romulus-IIIA from Quad Group. I'm pursuing assistance from them as well.
Solved!
Go to Solution.
Attachments:
Winzeta Error LabVIEW.JPG ‏17 KB

Howdy Szandstra,
Check out this KnowledgeBase article describing what you are seeing. Follow the steps there to correct the problem. Have a great day, and let me know if that solution doesn't work for you!
Sincerely,
Chris G in AE

Minimizing LV Run-Time Engine installation size?

Hi!
Is there any approach how RTE installation size could be minimized by selecting only the components that are really needed in a certain application? This would be very useful because:
1) Currently, if you select to install "NI LabVIEW Run-Time Engine" in RTE setup, you will get 160MB of components installed.
There are relatively much extra stuff that is definitely not needed in most of the applications (like NI-Reports, TDMS etc). Where is the option to deselect these?
2) Installation takes quite much time, even several minutes. If the installation is run silently and as an external part of the application installation itself, it is quite hard to estimate RTE installation progress.
3) There may be a bug in component installation
(see http://forums.ni.com/ni/board/message?board.id=170&message.id=239662&query.id=187629#M239662),
which could be avoided if that component were excluded from install.
Is it possible to customize the installation by editing Setup.ini or lv82runtime.msi's LabVIEW 8.2 RTE PDF.xml? Because NI does not seem to instruct how to do it, any 'hacker' solutions would be useful!
Thanks,
Wirer
Message Edited by Wirer on 04-10-2007 07:54 AM

The installer for the LabVIEW run-time engine can be found at \..\National Instruments\LabVIEW 6\AppLibs\installs. You will need separate run-time engines for the PC and Mac as executables are not cross-platform. To run an executable on a PC, you will need to use the PC version of the application builder and to run an executable on a Mac, you will need the Mac application builder. When you get 6.1, if you build an application with it, you will need to install a 6.1 run-time engine.

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

Does Labview run-time engine 6.0 application created by Windows NT/2000 can install & run on UNIX

Similar Messages

Maybe you are looking for