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

Similar Messages

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

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

I can not open Excel (97, 2000, or 2003) spreadsheet in Win98 OS PC using LabVIEW 7.0 Runtime Engine

Hi,
I have a problem opening an Excel spreadsheet by a LabVIEW application that is using Runtime Engine 7.0 in a Windows 98 OS environment .
I tried LabVIEW 7.1, it will not install on Win98. Meanwhile, I installed Excel 97 and 2000 (Excel 2003 does not install on Win98) and tried to open the spreadsheet, no luck with any combination.
Same code can open the spreadsheet in a WinXP OS, RTE 7.0, Excel 2000/2003 environment.
What can I do? Any advise?
Regards,
LVLV

Hi,
I did some experiment, I found out that Run-Time Engine 7.0 running executable generated at LabVIEW 7.0 environment (code written in LabVIEW 7.1 but save as 7.0) cannot open Excel 2000 files. If I replace Excel 2000 with Excel 2003 application on my pc, the executable code will open the Excel file (Run-Time Engine 7.0 works with Excel 2003).
Is the Excel 2003 and higher versions will only work with Run-Time Engine 7.0 and higher code?
How can I make executables using Run-Time Engine 7.0 work with Excel 2000 (Windows 98 operating system)??? (I cannot change Excel and Run-Time Engine and OS versions due to limitations, how can I work with what I have?).
Thanks for your help.
Regards,
LVLV

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.

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 .

CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

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

Computer with labview runtime engine (v8.2) cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What do I have to do?

I am trying to run an exectutable on a computer that has the labview v8.2 runtime engine. The error I am getting is: Cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What is the easiest solution?

the matrix,
I would try reinstalling the LabVIEW 8.2 Run-Time Engine. You may also want to try creating a very simple project in your development environment that has a VI with just the Mean.vi, try building an executable and then running it on the machine that just has the 8.2 RTE.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Labview runtime engine in VBS erkennen

Hallo,
das Dataplugin eines Kunden setzt auf die Labview-Runtime-engine auf. Um ein VBS-Makro "anwenderfest" zu machen würde ich gern im Makro abfragen können, ob die Engine in einer bestimmten Version oder höher installiert ist.
Frage: wie kann man in VBS abfragen, ob Labview oder eine Runtime-Engine in einer bestimmten Version installiert ist?
Danke für alle Antworten und Tips
Udo

Hallo Udo, Hallo Winfried,
Winfried's erste Beispiel wird nicht in einem DataPlugin funktionieren. Auch der zweite wird mit "MsgBox" ab DIAdem 10.0 Probleme bekommen. Vermütlich ist das Ziel ein sinnvollen Fehlermeldung auszugeben wenn der Version nicht passt. Dafür eignet sich die Funktion RaiseError.
Das Aufruf zu "CreateObject" sollte besser nach einem Aufruf zu "On Error Resume Next" kommen. Das ist weil, wenn LabVIEW nicht installiert ist, diesen Aufruf ein Fehler werfen kann. "On Error Resume Next" gibt einem dann die Möglichkeit diesen Fehler zu behandeln anstatt direkt aus dem Skript mit diesem Fehler rauszufliegen. Zurückschalten kann man dann mit "On Error Goto 0".
Registry auslesen ist möglich, aber nur wenn bestimmte Komponenten auf der Machine installiert sind. Bei viele Firmen sind diese Komponenten verboten da sie eine Sicherheitsrisiko darstellen.
Viele Grüsse,
Myrle
For tips and tricks on creating VBScript DataPlugins go to http://dataplugins.blogspot.com.

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

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

LabVIEW 8.6 Runtime and MAX installation

Can I install the LabVIEW 8.6 runtime engine and MAX on any computer without violating the license agreement for a single seat developer package? When I install this on a lab machine running XP and I go to launch MAX from the installed desktop icon, it does nothing... What am I doing wrong? Thanks, Keith

KC
You can try installing MAX from a download, MAX is included in many NI drivers, of which the smallest of which is the NI VISA driver. You can download and install VISA and it will automatically install the most update version of MAX as well. The VISA driver, MAX, and the runtime engine are total free and you can install them on any computer without any licenses.
Hunter
Message Edited by Huter on 02-23-2009 01:03 PM

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.

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

Similar Messages

Maybe you are looking for