Although it is always recommended to use the Run-time Engine Installer, it is not always necessary to do so. Strictly the only file required for a LabVIEW executable to run is the lvrt.dll. Other files are needed depending on what front panel controls and VIs are used by the executable. It is possible to create an executable that only requires the lvrt.dll, however a specific executable (even a simple one) will most likely require additional files from the Run-time Engine. The Run-time engine can be installed on one machine and then the necessary parts can be copied to another machine. For example in the case of a customer not wanting to install the Run-time engine, the entire sub-directory structure of the Run-time engine can be copied to the CD.
Note: If you choose to copy only part of the Run-time engine, the executable may start running but it may not work correctly. That is if an essential part is missing controls may be missing from the front panel, it may report errors, the application may crash, or it may not function as expected.
The built executable will look for the Run-time engine in the following locations:
The path named in the DLLPath key under the LVRT section. Create an .ini file for the executable by copying the labview.ini file to the directoy of the executable and renaming it name.ini where name is the name of the executable. If it is not present add a section for LVRT, and add a key for DLLPath.
[LVRT]
DLLPath= path to run-time engine
Next the executable will look in it's own directory.
Then it will look in the directory specified by the registry key "HKEY Local Machine \Software\National Instruments\LabVIEW Run-Time\X.X." Where "X.X" is the LabVIEW version.
Finally it will look in the default install location, which is Program Files\National Instruments\Shared\LabVIEW Run-Time\X.X.
Note: 3D graph, Report Generation and DataSocket components still need to be installed if the executable uses them.
In the case where you do not have administrative privileges to install the Run-time engine on a computer, follow these steps:
Install the Run-time engine on a computer where you do have the necessary privileges.
Copy the contents of Program Files\National Instruments\Shared\LabVIEW Run-Time\X.X to a disk. Where X.X is the version of the Run-time engine. The contents should be a several directories and .dll files.
Transfer the files you just copied to the computer where you want to install the Run-time engine, but do not have the ability to do so. Be sure to put these files in the same directory path, Program Files\National Instruments\Shared\LabVIEW Run-Time\X.X.
If you have privileges to modify the Windows Registry, continue with these steps:
Copy the file LVActiveXControl.dll located in Program Files\Internet Explorer\Plugins from the first computer to the second computer.
Add the registry keys for this ActiveX plug-in by downloading and running the attached file Run-time Engine 6.1 ActiveX Registry Entries.reg. These keys are necessary in order to use the Remote Front Panels feature of LabVIEW. Be advised that these registry keys are for LabVIEW Run-time engine version 6.1 and have not been tested with version 6.0 or 6.0.2. This has been tested on Windows 9x and Windows 2000.
As mentioned previously, Program Files\National Instruments\Shared\LabVIEW Run-Time\X.X is the default install directory for the Run-time engine. No registry keys are necessary for the Run-time engine to function, with the exception of the Internet Explorer ActiveX plug-in. Internet Explorer, as a Microsoft product, uses Microsoft Windows registry keys to register browser plug-ins, such as LVActiveXControl.dll. Without administrative privileges to add these keys manually or properly install the Run-time engine the user will be unable to use the Remote Front Panels feature of LabVIEW.
J.R. Allen
