Hiding the runtime engine

I have seen postings about this issue before but still...
I'm trying to hide the LabView Runtime Engine (RTE). Basically I would like to have the whole app in one directory.
When I put the lvrt.dll and additional files in the same dir (as suggested in this forum), starting the EXE calls the Windows installer and the RTE is extracted to the usual path (c:\program Files\National Instruments\shared...).
When I abort the Installer it pops up again 3 times. After aborting 3 times the app launches and runs correctly without having installed the RTE on the system.
Is there an option to prevent the RTE installer to kick in?
(Currently running LV 7.0)
If someone can help I'll buy you a beer at your next trip to Germany!
-DB

Just having lvrt.dll and the resource files (rsc) isn't enough: copy the following files & folders into the folder containing the exe:
..\National Instruments\shared\nicontdt.dll
..\National Instruments\shared\nicont.dll
..\National Instruments\shared\LabVIEW Run-Time\ver\* (including all sub-directories)
There are a few things that, depending on whether used by your app, may not need to be included. For example:
..\National Instruments\Shared\LabVIEW Run-Time\ver\Errors
Converts and displays LabVIEW errors to the user. If you don't have this directory, errors may be displayed in a non-sensical format, or even not at all. Note: if you have custom error files (like xml onesyou've created, then put them in here).
..\National Instruments\Shared\LabVIEW Run-Time\ver\models
These are the control/indicator models - have alook through the directory, and remove those that you don't need.
..\National Instruments\Shared\LabVIEW Run-Time\ver\PlugInControls
Remove anything out of here that you don't need (eg: image control/indicators, etc)
..\National Instruments\Shared\LabVIEW Run-Time\ver\script
This is where interfaces to Matlab, HiQ and the like are kept - delete them if you don't need them
..\National Instruments\Shared\LabVIEW Run-Time\ver\lvjpeg.dll
..\National Instruments\Shared\LabVIEW Run-Time\ver\lvpng.dll
If you're not doing anything with jpegs or pngs, then you don't need these either.
That said, if you're using 7.1, then there's a whole bunch of other files in the ..\National Instruments\Shared\LabVIEW Run-Time\ver\ folder - just have a look at the names and experiment a little
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Similar Messages

How do I determine if a VI is running in the runtime engine or LabView Development Environment?

Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment? I am using LabView 8.5.
I have a menu item, File/Exit, and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected. However, in development, I don't want to shut down LabVIEW when I select that menu item.
Maybe there is a more appropriate way to exit the program. However, I am looking for something elegant. I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
Thanks

Here is a small VI with this exact function.
Attachments:
Is EXE.vi ‏9 KB

Front panel class objects are missing their icons in the runtime engine

I have this project that contain some class objects. When run in the developer environment, the icons appear fine.
However when I build as an executable and run it in the runtime engine, the icons are missing.
These missing icons are purely cosmetic and the underlying logic works without a problem. Is there anyway to get these icons to display when built as an executable?

Known issue, see http://lavag.org/topic/12980-class-control-icon-not-shown-in-run-time/
EDIT: have you considered just making that control invisible? Takes a bit of manipulation of property nodes and references but you can do it as shown:

How do I build an executable w/o installing the runtime engine in the OS?

Hello everyone
I have developped an application with LabView 8.01 and build an executable for a customer, this works great, if I have administrator rights. But my customer don't have full administrator rights and they are not able to install the software (Runtime Engine). In LabView 6.0.1, to solve this problem we added the lvrt.dll and some support files directly to the application builder as support files and it worked without to install the runtime engine in the operating system.
How can this be done in LabView 8.0.1 and which files are needed?
I am thankfull for any advice.

hi,
you always need admin rights to install software.
I think it's not possible in labVIEW 8.01 to install the runtime without admin rights.
The costumer only has to the runtime one time, so he should try to contact his system administrator.
I've found no workaround for it.
Best regards.
Christoph Strasser
AE/NIG

What does the RunTime engine support?

Hello,
Does anyone know what functions the RunTime engine supports? Or is there a
NI link I can follow. Some goodies like the VI server don't seem to be
supported in RTE 5.1.
6i any different?
Thanks
Martin

I know about the paths, but I had problems with getting the username with
the Open application reference, an error came up 'function not supported'
and a pointer to the VI that caused it.
It's my mistake to say the VI server was not included. But are the
Application properties (web etc) included ?
Thanks
Martin
"Dennis Knutson" wrote in message
news:[email protected]..
>
> I use VI server with the run time engine all the time. When you build an
app,
> you have to specify which vi's are called dynamically so that they are
included.
> Paths parse out a little differently too when you've got a built app.
Sometimes,
> all it takes is an extra Strip Path.
>
> "Martin E" wrote:
> >Hello,>>Does
anyone know what functions the RunTime engine supports? Or
> is there a>NI link I can follow. Some goodies like the VI server don't
> seem to be>supported in RTE 5.1.>6i any different?>>>Thanks>Martin>>

I give up where are they hiding the LabView runtime engine downloads?

When I deploy en EXE I find it much easier to just plug the target machine into the network and download VISA and the Runtime Engine.
VISA is easy to find but I always end up spending 45 minutes to an hour looking around for the LV runtime download.
It's been 45 minutes now and the closest I have come is finding the Web Browser runtime plugin.

2012 32bit
2012 64bit
2012 SP1 32bit
2012 SP1 64bit
2011 32bit
2011 64bit
2011 SP1 32bit
2011 SP1 64bit
2010 32bit
2010 64bit
2010 SP1 32bit
2010 SP1 64bit
2009 32bit
2009 64bit
2009 SP1 32bit
2009 SP1 64bit

Runtime engine 8.6.1 on Labview 11

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

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

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

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

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

Installing LabView 8.2 runtime engine on Windows 7 64-bit

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

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

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

How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

hp7550,
I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
I hope that helps.
Best Regards,
Matt P.
Applications Engineer
National Instruments

Can the runtine engine and an application be run directly from a CD?

Can an application be run directly from a CD without installing the runtime engine and application onto the computer?

It depends on what library functions the application is using and what version of LabVIEW it was built in. In LV 7 and earlier you could just put the run-time files (the ones in Program Files\National Instruments\Shared\LabVIEW Run-Time...(lvrt.dll is the most crucial of the files, a full list can be found here on the developer zone)) in the same folder as the application and it would run without any problems in most cases.
In 7.1/7.1.1 math functions had to be installed as well if you had used any of those and could be a problem, otherwise it still worked (we do this still with apps that use serpdrv instead of VISA).
With LV8 it is still possible, but the chance of the application depending on some function that you do not get included this way is much higher, I would just test it and see how it goes.
MTO

Runtime engine files 8.2

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

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

Runtime engine can't load vi with lvdatetimerec.ctl

Hello everybody,
i have trouble with TS 3.5 / LV 11.0
I programmed a small vi that calculates the time difference between now and a time stamp. To pass the timestamp from Teststand i use a Control (lvdatetimerec.ctl) and the matching VIs to do the task.
Unfortunally i can't load the vi into Teststand using the Runtime Engine. I get the message "Unable to load VI "xx.vi" with the Run-Time Engine. It is possible that the version of the VI or one of its subVIs is not the same as the ..."
It is certainly the same and there is no problem until i include a constant or control of that type.
Do anybody have an idea?
Best regards
Thomas
Attachments:
TimeDiff.vi ‏7 KB

Try to recompile your vi hierarchy in LabVIEW (hold Ctrl and click Run), then save it, then try again in TestStand with LabVIEW runtime.
Runtime engine does not support dynamic compiling, this vi may looks fine in LabVIEW, but TestStand will complain that it is broken.
Sergey Kolbunov
CLA, CTD

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

Hiding the runtime engine

Similar Messages

Maybe you are looking for