8.2 runtime engine install

Hi All,
I am currently attempting to install the full LabView 8.2 RTE on a Windows 2000 SP2 machine. I downloaded the RTE from NI's site (LabVIEW_8.2_Runtime_Engine.exe, http://digital.ni.com/softlib.nsf/websearch/9BCED01B8F69F8A0862571BF0078FF96?opendocument&node=13206...), and was able to extract it into a temporary directory on the target machine. However when I try to run Setup.exe I get an error that the RTE is not compatable with my OS.
I looked around and was unable to determine if there was a specific service pack of windows 2000 that is needed to use setup.exe, but I'm guessing that there is, so if anyone knows it I would be grateful for the information.
Also, I was able to drill down into a couple directories and run the .msi for just the RTE with no errors, but I didn't know if I would need some of the other stuff that was unpacked to run my custom labview executable. Things such as the license manager, etc. Anyone know if I can just install the RTE and not any of the other stuff and still be OK?

You need at minimum Service Pack 3 for Windows 2000. You can read all the gory details in the LabVIEW Release Notes.

Similar Messages

Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
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

Will labview 6.1 runtime engine install on a win NT 3.5.1 system??

I got an error when I tried to run the .exe file for the runtime install. The .exe file was downloaded from the software update section.

Similar to the development versions of LabVIEW, the run-time engine is only supported on NT 4.0. You would need to update your system before installing this software.
J.R. Allen

Installing Labview runtime engine 2011

Hi,
Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ?
Thanks.

No, you should actutally keep the older runtime engine installed in case you still have applications that depend on it. The 2011 run time will only support applications built with LabVIEW 2011.
LabVIEW Champion . Do more with less code and in less time .

Runtime engine 8.0.1 does not install because higher version is installed

Hello,
I am trying to install Runtime Engine 8.0.1.
This is the message I get when installing Runtime Engine 8.0.1:
"A higher version of this product is already installed."
Yet I do not have another Runtime Engine version installed. According to the NI Add/Remove program, I have the following installed:
NI LabWindows/CVI 8.1 Run-Time Engine
NI Measurement & Automation Explorer 4.2.1
NI-488.2.2.5
NI-485x Software 1.0.1
NI-VISA Runtime 4.0
At some point, I un-installed:
NI LabWindows/CVI 8.1 Run-Time Engine
NI-488.2.2.5
but I ended up with the same results:
"A higher version of this product is already installed."
I checked my folders and deleted any trace of Runtime Engine folders. I therefore deleted:
C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\
but I am still unable to install Runtime Engine 8.0.1.
Any idea?
Thanks,
Francois

Hi Francois,
If you have a newer version of the runtime engine installed, then it should be listed in MAX. However, you've already deleted that directory, so it may not be there anymore. The only way now to uninstall those versions of the runtime engine is to use a utility we have that I cannot post on the forum. If you can create a service request via email or phone then we would be able to help you get the newer versions fully uninstalled. You can create a service request at www.ni.com/ask.
If you do not have a support contract and cannot create a service request, then let me know and I will create one for you so you can call in.
Nick R
NI

LabVIEW85 Runtime Engine

Hola a todos,
Necesito vuestra ayuda!... Desarrollé una aplicación hace tiempo con LabVIEW 8.5 y ahora necesito instalarla en un PC que trabaja con Windows 7. He vuelto a crear la aplicación en un PC con Windows 7. Cuando ejecuto la aplicación en un PC con Windows 7 y labVIEW 8.5 instalado no da problemas. En cambio en un PC con Windows 7 pero sin LabVIEW instalado mi aplicación ya no reconoce los puertos COM. Creo que tiene que ver con la version de LabVIEW Runtime Engine instalada en el PC. He buscado en la Web y no encuentro ninguna version para LabVIEW 8.5.1 que sea compatible con Windows 7. Se os ocurre alguna solución?
Espero vuestra respuesta!... Saludos.

English translation:
I need your help! ... An application developed with LabVIEW 8.5 for some time and now need to install on a PC running Windows 7. I re-created the application on a PC with Windows 7. When I run the application on a PC with Windows 7 and LabVIEW 8.5 installed gives no problems. However on a PC with Windows 7 but without LabVIEW installed my application and does not recognize the COM ports. I think it has to do with the version of LabVIEW Runtime Engine installed on your PC. I searched the Web and I find no LabVIEW 8.5.1 version that is compatible with Windows 7. Can you think of a solution?
You need to install NI-VISA on the target machine. This has been asked many times before. And yes, LabVIEW 8.5.1 is not officially compatible with Windows 7. It may work fine. It may not.

Linux VI with Runtime Engine Only

Hi,
We're trying to start a VI on a Linux system, with only the runtime engine installed. But we're having a few problems...
First, if the runtime engine installed without errors ("rpm --install labview71-rte......i386.rpm" and "rpm --install labview-rte-aal......i386.rpm") how can I know for sure that it's working? I can't find any file that indicates that it is installed...
Is it possible (just like under windows) to start a VI with only the runtime engine? What should I call on the shell to start a VI?
Is it possible to run a windows VI under Linux, with only the runtime engine? I read somewhere on www.ni.com that to run a VI a rte of the LabVIEW version used to build the VI is needed. But is LV7.1 for Linux the same version as LV7.1 for windows? Is the Linux runtime engine capable of running the windows VI?
In short, what we like to do is: Use windows to develop some VI's with serial communication. Copy the VI's to a Linux system. Start the VI's.
Any ideas are greatly appreciated.
Wiebe.

"shoneill" <[email protected]> wrote in message news:[email protected]...
Wiebe,I wrote that the binary code is OS dependent, not independent.  Please re-check my post (and your reference to my post to rule out cheeky editing.... )Regarding running a linux VI on linux without the development
You're right. Let's blame it on the language barier (on my side), and today being fryday. Still I don't see why assembler code can't be the same on two exactly the same i386 processors. The OS stuff should be handled in the runtime engine, and the add's mul's, call's etc. are the same. But I haven't given in much thought, and never tried anything like that. I'm sure their will be some problems.
environment, I wouldn't know since I've never used LV on linux (yet).  I thought the original duscussion was about running a VI from one platform on another without requiring the development environment to re-compile. 
It was about running a VI on Linux with only the rte. And what's needed to make this happen.
Can't you just build a wrapper VI to call the VI from a built application (provide path and hey presto, it can be called dynamincally.....no?)I also agree that a bit more multi-platform support would ultimately help NI, but I can understand
Yes, if we had an application builder for Linux, we could make a wrapper. It would solve the licensing problem. Perhaps someone can make a Linux application wrapper/vi starter for LV8.2 (we'd be happy with any version though)?
About the support.. Somehow someone forget to put all the Linux documentation on ni.com.
the thinking behind it.  Not that I agree, I just understand Further, I believe the run-time is required to prevent each and every LV application being huge.  But sometimes I wish we could distribute without theis run-time Stigma (or better - have the choice).You've raised an interesting point by questioning the existance of the run-time engine......Shane.Message Edited by shoneill on 02-09-2007 04:01 PM
Someone ought to make a virtual machine that can execute LabVIEW's executable code inside a vi, and simulate the runtime engine at the same time : ) It will take some time though...
Regards, Wiebe.

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

Labview runtime engine [SOLVED]

Hi, I'm a new Arch user having migrated from Ubuntu a few weeks ago. I've been stuck for several days trying to get the National Instruments Labview runtime engine installed. It is an easy process on Ubuntu so it must be possible with Arch. I'd prefer not to operate outside of pacman (ie. installing with rpm or dpkg) based on what I've read in the forums.
The Labview runtime engine is a free download from National Instruments and allows programs that are generated by the Labview developer package (expensive) to be run on any box without having the licensed Labview software installed. This is handled with two .rpm files that one downloads from the NI website after registering there. You must download the .rpm files appropriate for the version of Labview that generated your executable. (Note that executables generated by Windows Labview and Linux Labview are not interchangeable) For reference, those files can be found here:
http://joule.ni.com/nidu/cds/view/p/id/1103/lang/en
For Ubuntu, I converted the .rpm files to .deb using alien and installed them with dpkg. The Labview executables can then be run by opening them in the file manager. As a first step in Arch, I unbundled the .rpm files using rpmextract and found that they are just a bunch of library files placed in usr sub-directories. I then wrote the following naive PKGBUILD followed by makepkg -s.
pkgname=lvtest
pkgver=1
pkgrel=1
arch=('i686' 'x86_64')
license=('GPL')
makedepends=('rpmextract')
source=("labview86-rte-8.6.0-1.i386.rpm"
"labview-rte-aal-1.1-1.i386.rpm")
md5sums=('37b43da794fd9c61d0c5e3c9cfa56628'
'a2110e5b5677351095bd93e5b1aa5bea')
build() {
cd ${srcdir}
rpmextract.sh labview-rte-aal-1.1-1.i386.rpm
rpmextract.sh labview86-rte-8.6.0-1.i386.rpm
cp -ra ${srcdir}/usr $pkgdir/
This generates a pkg.tar.xz that I install with pacman -U. My problem is that the Labview executables are not being recognized, ie. I don't know how to open them. I suspect this has something to do with permissions or perhaps linking that I sometimes see in other PKGBUILD files, but I don't know how to proceed. I am brand new at this, but have spent a lot of time searching the wiki and forums looking for hints and guidance.
Last edited by sportscliche (2011-01-02 23:58:49)

Thanks for the fast reply! Output of pacman -Ql lvtest follows:
lvtest /usr/
lvtest /usr/local/
lvtest /usr/local/lib/
lvtest /usr/local/lib/LabVIEW-8.6/
lvtest /usr/local/lib/LabVIEW-8.6/.data/
lvtest /usr/local/lib/LabVIEW-8.6/.data/Analysis-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/IAK_SHARED-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/LV_RemotePanelConnection.lic
lvtest /usr/local/lib/LabVIEW-8.6/.data/LabVIEW Simulation Module-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/LabVIEW-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/Measure-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/NI-488-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/NI-Reports-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/.data/VISA-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/English/
lvtest /usr/local/lib/LabVIEW-8.6/English/lvapp.rsc
lvtest /usr/local/lib/LabVIEW-8.6/English/vidialogs.rsc
lvtest /usr/local/lib/LabVIEW-8.6/LV86NPlugin.so
lvtest /usr/local/lib/LabVIEW-8.6/copyright.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/Analysis-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/IAK_SHARED-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/LabVIEW Simulation Module-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/LabVIEW-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/Measure-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/errors/English/NI-Reports-errors.txt
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so.2
lvtest /usr/local/lib/LabVIEW-8.6/libappweb.so.2.3.0
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblkdynam.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblkrealt.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblksec.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so.5
lvtest /usr/local/lib/LabVIEW-8.6/liblksock.so.5.0.0
lvtest /usr/local/lib/LabVIEW-8.6/liblvrt.so.8.6.0
lvtest /usr/local/lib/LabVIEW-8.6/liblvrtdark.so.8.6.0
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so.4
lvtest /usr/local/lib/LabVIEW-8.6/libnids.so.4.5.4
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so.1
lvtest /usr/local/lib/LabVIEW-8.6/libnitaglv.so.1.5.0
lvtest /usr/local/lib/LabVIEW-8.6/libniwebsrv.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so.2
lvtest /usr/local/lib/LabVIEW-8.6/libnixerces.so.2.7.0
lvtest /usr/local/lib/LabVIEW-8.6/linux/
lvtest /usr/local/lib/LabVIEW-8.6/linux/README.libs
lvtest /usr/local/lib/LabVIEW-8.6/linux/libstdc++.so.5
lvtest /usr/local/lib/LabVIEW-8.6/linux/libstdc++.so.5.0.3
lvtest /usr/local/lib/LabVIEW-8.6/lvanlys.so
lvtest /usr/local/lib/LabVIEW-8.6/lvdark
lvtest /usr/local/lib/LabVIEW-8.6/models/
lvtest /usr/local/lib/LabVIEW-8.6/models/arrow.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/attank.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/bowvalve.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/box_inc.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/box_incp.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/boxshadow.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/frame_i.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/frame_o.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/gauge_f.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/inc.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/knob_t.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_f.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_g.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/meter_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pb_l.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pro_bar.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/pro_bar_in.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rectvalve.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rocker.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rockerl.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/rockerr.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slided.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slideh.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_b.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_d.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_f.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/slider_t.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/slidet.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/squreled.3ds
lvtest /usr/local/lib/LabVIEW-8.6/models/tab.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tank.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tb_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/tb_h_in.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/therm_e.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/therm_h.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_b.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_s.ptc
lvtest /usr/local/lib/LabVIEW-8.6/models/toggle_su.ptc
lvtest /usr/local/lib/LabVIEW-8.6/nids.so
lvtest /usr/local/lib/LabVIEW-8.6/niwebsrv.so
lvtest /usr/local/lib/LabVIEW-8.6/patchlib/
lvtest /usr/local/lib/LabVIEW-8.6/rtapp.rsc
lvtest /usr/local/lib/LabVIEW-8.6/webserver/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvauthmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvrfpmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/liblvsnapshotmodule.so.1.0.0
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvauthmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvrfpmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/LVModules/lvsnapshotmodule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/access.log
lvtest /usr/local/lib/LabVIEW-8.6/webserver/logs/error.log
lvtest /usr/local/lib/LabVIEW-8.6/webserver/mime.types
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libcopyModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libdirModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/modules/libespModule.so
lvtest /usr/local/lib/LabVIEW-8.6/webserver/niwebserver.conf.defaults
lvtest /usr/local/lib/libguide.so
lvtest /usr/local/lib/libmkl.so
lvtest /usr/local/lib/libmkl_def.so
lvtest /usr/local/lib/libmkl_lapack64.so
lvtest /usr/local/lib/libmkl_p3.so
lvtest /usr/local/lib/libmkl_p4.so
lvtest /usr/local/lib/libmkl_p4p.so

Utility to switch TestStand runtime engines

The development version of TestStand 2.0 comes with a version switch utility to change versions of TestStand between TestStand 1.x and TestStand 2.x. If a machine only has runtime engines installed, is there a utility to switch runtime engines between TestStand 1.x and 2.x?

The problem now is that the run-time installer will not allow a different TestStand run-time engine to be installed on the target machine since it already has a TestStand run-time engine. Unlike the full development installer, the run-time installer will not allow the TestStand directory to be changed so that more than one version of the run-time engine can be used. So, the version switch utility cannot be used unless there is a way to have two different TestStand run-time engines on the same machine (without any TestStand development software installed). Is there any way to get around this ? Am I misunderstanding something here ?

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

Cannot Install LV Runtime Engine 7.1

HI,
Some of our users are having unusual installatiion problems while
installing the LV runtime Engine 7.1.1 on win2k. Our users have
installed another application recently and in that process the LV
runtime engine was removed from their computer. So, they tried to
install the runtime engine(downloaded it from NI website) again but couldn't becuase they keep getting
the message that they are not logged in as administrator. We logged in
as admnistrator and tried installing the runtime engine again,
but the error keeps occuring and is not allowing us to install. I
searched the NI discussion forums and the Knowledge base to find
answers but did not see any that match our problem. From some of the
posts I suspect it has got something to do with Microsoft hotfixes and
windows upgrades etc.
If anyone else had seen this kind of behavior and has found a fix,
please share it with us. Any help will be greatly appreciated.
Thanks Ahead
Deepak K

Hello!
This is an unusual problem. I would first go through the add/remove
programs through control panel. Loate the "National Instruments
Software" item and select "change". See if any LabVIEW
components are there and slect to remove them. This will completely remove the
LabVIEW components. Then attempt a reinstall of the runtime engine.
If this still causes problems, you may have deleted the old LabVIEW runtime
engine in an unusual way which is interfering with later installs. If this
is the case, there are some other methods that we might be able to use to
uninstall fragments of NI software. Removing the software does not fix
the problem post back and let us know!
-thanks-
Travis M
LabVIEW R&D
National Instruments

Unable to install LV Runtime Engine 7.1.1 with LabVIEW Professional 8.5.1

I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
"Installation aborted. Newer version already installed."
Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.

Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.

App won't install with the prerequisite SAP Crystal Reports Runtime Engine

On installing with the following prerequisite checked:
SAP Crystal Reports Runtime Engine for .NET Framework 4.0
.. received this error:
Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0.msi
has changed since it was initially published.
Should I NOT use the prerequisite, and instead, use a merge module?

I ran a program with the exact same name, 2 weeks ago, on my VS 2010 Dev machine:
CRforVS_13_0.exe. (284 Meg)
Today, I followed your link, and downloaded the file with the same name, but different size: (1.5 Meg). I mean, a really major difference in size!
Because creating and testing installation packages is very time consuming, I want to verify what you have stated so that I completely understand before I change what currently works, which is for the client machine to separately install the CR runtime, to what you're proposing in including a prerequisite to my install package.
-> I should run this latest exe. It will add a prerequisite to the prerequisite list in Visual Studio 2010. The installation of this prerequisite will work, as the earlier one did not. And it will work for both 32- and 64-bit client machines.
Therefore, I can eliminate the need for the client machine to install the CR run time separately.
Please confirm, and then I will make the necessary changes, and do the install tests on client machines.
(Also, FYI the merge module did not work for me on a 32-bit client machine. So I removed it.)
Thanks, Peg

What is minimum runtime engine size when installed on XP embedded OS

I hope to build move an existing Labview 8.6 application to a Windows XP embedded machine and would like to know if their are any tools available to help minimize the hard disk memory requirement, specifically can the runtime engine installation be micro managed so that absolutely nothing that is not required by the application is installed?
If not, is their some way to install the runtime engine and then remove unused items, for instance one .dll file at a time?
I would appreciate any guidance.
Thanks,
Bernie

I believe NI does not officially support running LV apps on XPe, but if you search, you should find some references to it. In any case, I doubt you will find anything relating to the size of the RTE. You can probably safely remove some of the support files (e.g. language files, which take up some space), but I've never done it and it isn't necessarily safe.
In older versions, you could simply use all the files from the RTE folder if you didn't require any drivers, but I believe that doesn't work since ~8.0.
Try to take over the world!

8.2 runtime engine install

Similar Messages

Maybe you are looking for