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.

Similar Messages

Run-Time Engine Installation ?

I currently have LabVIEW Developer Suite 6.0 for both PC (Windows NT/2000) and the Mac OS . We are developping a number of executables that will be run on Windows NT 4.0 hosts . I have a few questions.
1.) Is there an installer for the run-time engine that I can use to place the run-time engie on the image of the target machines. I have stumbled on the back-door method of including the run-time installation in the installer for an application. but I would prefer to install the run-time engine once on all of the target machines (there are about 60 of them).
2.) Are executables cross-platform ? Will an executable that is built on a PC/MAC run on a MAC/PC ?
3.) Does anything change when we get LabVIEW 6.1 ?

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.

What is "LabVIEW Run Time Engine"?

I'm trying to find the differences between two computers that I'm troubleshooting. One of them is my development system which has the whole Development Suite installed, and the other is a test station which has LabVIEW 8.0 Evaluation Version installed. When I was looking through the list of programs in my development system (in Add/Remove Programs), I found a program named "LabVIEW Run Time Engine" and the size is 0.11 MB that is not in my test station. I thought all the NI components are installed under "National Instruments Software" including the Run Time Engine...
Does anyone knows what this is?
See-Ming

The Run Time Engine is a library of routines that a compiled Labview program needs to run on a system that doesn't have the development environment. It is similar to Visual Basic's vbrun.dll, which compiled VB programs need to run.
As far as I know, the run time engine gets installed whenever you install any Labview development environment. This engine is usually only necessary when running a Labview program compiled to an exe format. Both the exe and the run time engine can be installed on another computer so that the program can run without having to buy another development package for that computer.
The runtime engine is called LVRT.DLL. Search for it. For version 7.1, the run time engine is in C:\Program Files\National Instruments\shared\LabVIEW Run-Time\7.1\lvrt.dll
- tbob
Inventor of the WORM Global

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.

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Run time engine download disabled?

Hi, I am trying to download the lates LV run time engine. There are pages for 8.0 and 8.2, no 8.2.1. However, when I click on the links to download either version, the files are not there. What's going on?

Thanks for the responses. I followed Yi's links and they do work. However, I happen to have the URIs from my original attempt, and they still don't work. Here is an example, and proof
ftp://ftp.ni.com/support/labview/windows/runtime/8.2/LabVIEW_8.2_Runtime_Engine.exe
Mon Sep 17 17:28:04 2007 Connecting ftp.ni.com:21
Mon Sep 17 17:28:04 2007 Connecting ftp.ni.com [IP=130.164.140.175:21]
Mon Sep 17 17:28:04 2007 Socket connected, Waiting for welcome message.
Mon Sep 17 17:28:04 2007 220 ftp.ni.com NcFTPd Server (licensed copy) ready.
Mon Sep 17 17:28:04 2007 USER anonymous
Mon Sep 17 17:28:04 2007 331 Guest login ok, send your complete e-mail address as password.
Mon Sep 17 17:28:04 2007 PASS ********
Mon Sep 17 17:28:04 2007 230-You are user #33 of 750 simultaneous users allowed.
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230- *** Welcome to the National Instruments FTP Site ***
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-              ftp.ni.com
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-Important changes!
Mon Sep 17 17:28:04 2007 230------------------
Mon Sep 17 17:28:04 2007 230-As of January 23, 2004, /incoming will allow only uploads. Downloads from /incoming are not allowed.
Mon Sep 17 17:28:04 2007 230-You can download temporary files from /outgoing. Uploads to /outgoing are not allowed.
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-Compression Formats:
Mon Sep 17 17:28:04 2007 230--------------------
Mon Sep 17 17:28:04 2007 230-.hqx files are compressed using Binhex Mac and PC utilities.
Mon Sep 17 17:28:04 2007 230-.zip files are compressed using PKZip version 2.04g PC Utility.
Mon Sep 17 17:28:04 2007 230-.tar files are compressed using the UNIX "tar" command.
Mon Sep 17 17:28:04 2007 230-.Z files are compressed using the UNIX "compress" command.
Mon Sep 17 17:28:04 2007 230-.sea files are Macintosh Self-Extracting Archives.
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-      - National Instruments World-Wide Web Site:
Mon Sep 17 17:28:04 2007 230-                 http://www.ni.com
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-      - National Instruments FTP Site:
Mon Sep 17 17:28:04 2007 230-                 ftp.ni.com
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-      - Developer Exchange Discussion Forums:
Mon Sep 17 17:28:04 2007 230-                 http://www.ni.com/exchange
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230-
Mon Sep 17 17:28:04 2007 230 Logged in anonymously.
Mon Sep 17 17:28:04 2007 Login Successful
Mon Sep 17 17:28:04 2007 REST 100
Mon Sep 17 17:28:05 2007 350 Will attempt to restart at position 100.
Mon Sep 17 17:28:05 2007 This site can resume broken downloads.
Mon Sep 17 17:28:05 2007 REST 0
Mon Sep 17 17:28:05 2007 350 Will attempt to restart at position 0.
Mon Sep 17 17:28:05 2007 TYPE A
Mon Sep 17 17:28:05 2007 200 Type okay.
Mon Sep 17 17:28:05 2007 PASV
Mon Sep 17 17:28:05 2007 227 Entering Passive Mode (130,164,140,175,228,74)
Mon Sep 17 17:28:05 2007 LIST /support/labview/windows/runtime/8.2/LabVIEW_8.2_Runtime_Engine.exe
Mon Sep 17 17:28:05 2007 550 No such file or directory.
Mon Sep 17 17:28:05 2007 TYPE I
Mon Sep 17 17:28:05 2007 200 Type okay.
Mon Sep 17 17:28:05 2007 SIZE /support/labview/windows/runtime/8.2/LabVIEW_8.2_Runtime_Engine.exe
Mon Sep 17 17:28:05 2007 550 No such file.
Mon Sep 17 17:28:05 2007 TYPE I
Mon Sep 17 17:28:05 2007 200 Type okay.
Mon Sep 17 17:28:05 2007 PASV
Mon Sep 17 17:28:08 2007 227 Entering Passive Mode (130,164,140,175,228,76)
Mon Sep 17 17:28:08 2007 RETR /support/labview/windows/runtime/8.2/LabVIEW_8.2_Runtime_Engine.exe
Mon Sep 17 17:28:08 2007 550 No such file.
Mon Sep 17 17:28:08 2007 RETR support/labview/windows/runtime/8.2/LabVIEW_8.2_Runtime_Engine.exe
Mon Sep 17 17:28:08 2007 550 No such file.
Mon Sep 17 17:28:08 2007 Error occured!

How do I create installer that checks the available Run Time Engine on the target system

Hi,
I am looking for a soultion on custom Installer where this Installer once done with the Installation should be capable of checking the presence of Runtime Engine on the target system. I amaware of including/checking the LV RTE checkbox for such options and we are working on some other concept. The thing is we would like to give the user a pop-up or any message that shows the presence of Runtime engine on the target system after finishing the installation. In case the runtime engine is not already installed on the target system, this time the message will be for the link to get the .exe and close the installation.
Overall we would like to minimize the size of our Installer that in case will get increased if we include Run Time Engine along with the Installer.
I am also assuming that such checking can be done through Advanced Tab in the Installer properties by including any such .exe for performing those things but looking for more options if possible to get it done.
Please do let me know if someone has any idea about it.
Thnaks in Advance,
Vivek

Hi teststand,
you can start another program which checks if the rte is available. It should also be possible with only a batch file.
Mike

LabVIEW Run-Time Engine

Hi ,I have used Application Builder to make EXE file from my source files but I have noticed it is not possible to use this EXE file in another PC without LabVIEW because LabVIEW run-time engine is needed so I tryed Installer
but I have few questions and I would really appreciate if u help me
1- What kind of source files should be added to the installer? I would like to install an EXE file and Data folder so do I need to first use the application builder to make the application then add all the application files(EXE and Data folder) one by one to the installer or Do I need to add my LV files to the installer and LV make exe and data folder again for me?
2- I am using LV2010 and I would like to add run time engine for 2010 so I checked the box for LV2010 run time engine but many options are included to this engine like NI TDM,NI SSL etc ... and after making the installer I noticed the size of my file was so big (109MB) while I want to make a small size installer for email .Is there any chance to reduce the size of installer by unchecking some of the options?
Many thanks

You build an executable first, then you build an installer for the executable. When building the installer, simply add the executable and LabVIEW will figure out what else is needed in the typical case.
If you want a small installer, don't include the run time engine. Instruct your customers to donwload and install the free runtime engine from here.
Make sure they install the "standard", not "minimum" version. Also make sure they install the 32 bit version if your LabVIEW 32 bit, even if they install it under a 64 bit OS.
LabVIEW Champion . Do more with less code and in less time .

Why do different versions of the LabVIEW Run-Time Engine not compatible?

LabVIEW Run-Time Engine to become more and more big
Why do different versions of the LabVIEW Run-Time Engine not compatible?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview
Solved!
Go to Solution.

jwdz wrote:
LabVIEW2020 ....... ，it look like?
You need to express your ideas more clearly. We cannot fill in the blanks and read between the lines if the post has no substance.
jwdz wrote:
It will affect the future development of LabVIEW, right?
What is "it"?
There are many things that affect the future development of LabVIEW, starting with NI management, all the smart people in LabVIEW development, the economy, the LabVIEW users, etc.
If you are worried about the increasing size of the distribution, the good news is that the cost of data storage and data transmission has dropped much more dramatically. Even though newer versions are bigger due to great and welcome new features, the improvements in infrastructure have actually made the distribution and storage significantly easier over the years and will continue to do so. Trust me!
Nobody wants to go back to a LabVIEW version that fits on a floppy disk!
LabVIEW Champion . Do more with less code and in less time .

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

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

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

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

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Unable to run vi with labview run time engine

Hi All,
I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
When I make a call to it from Test Stand 4.1 it works lovely.
When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
I don't really understand! And am tearing my hair out.
The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
I have attached the problemVI.lvproj.
Thanks for any advice or help.
Matt
Attachments:
problem VI.lvproj ‏41 KB
teststand.JPG ‏43 KB

Matt,
it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Run-Time Engine error

I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
Thanks
Chirs
Solved!
Go to Solution.

Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

VISA Write differs between TS Development System and LV Run-Time Engine

Hi all
I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
Everything works fine using just LabVIEW.
Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
Any solutions for this?
Thanks in advance
Joao
Solved!
Go to Solution.

Joao,
you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
So i am pondering: Does this refer to TS at all?
Please check the following:
Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
What about loading/unloading options of the modules?
How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
Could you provide a simple example sequence+modules showing this behavior?
What versions of LV and TS are you using?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Minimizing LV Run-Time Engine installati​on size?

Similar Messages

Maybe you are looking for

Minimizing LV Run-Time Engine installation size?