LabWindows/CVI 2009 Run-Time Engine update

I wanted to let everyone know that NI has released an udpated CVI 2009 Run-Time Engine. Information on what bug(s) this update fixes can be found here. If you are currently not using the CVI 2009 Run-Time Engine, you do not need to install this update.
This is an updated installation of the CVI Run-Time Engine, not a patch. If you download and install this update it will upgrade whichever version of the CVI Run-Time Engine you currently have to version 9.1.0.428 (CVI 2009 released with version 9.1.0.427). One way to find out which version of the CVI Run-Time Engine you have installed is to view the version number of c:\windows\system32\cvirte.dll. If you install version 9.1.0.428, any installer distributions that you create from any version of the CVI ADE will include version 9.1.0.428.
If you have not yet installed LabWindows/CVI 2009, it's recommended that you install this update, either before or after you install CVI 2009.
Luis

To be clear, the original problem that you reported ("Attempt to free pointer to memory not allocated by malloc() or calloc()") might very have been the problem that this patch fixed, which was in fact new to 2009. But that problem only happens if there were actual plots in the graph.
However, after looking at the "dynamic memory is corrupt" isse some more, it turns out that it is actually expected behavior, believe it or not. This is a limitation of easytab controls, caused by how they use callback chaining in their implementation. Whenever a panel or a control has its callback chained, you cannot change the callback, or make a copy of it after the chaining takes place. This is described in the EasyTab_ConvertFromCanvas function help ("...For the same reasons, do not call DuplicatePanel or DuplicateCtrl on any of these panels or controls after the Easy Tab control has been created.").
As you probably have read elsewhere, easytab controls are quite obsolete. They were a stopgap "solution" to the problem of there not being a native tab control in the CVI user interface library. Native tab controls were finally added in CVI 8.0, and so we recommend that, if possible, users update their code to use these instead.
Luis

Similar Messages

Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
National Instruments
Product Support Engineer

The correct link should be this one
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

I've created an application installer using LabVIEW's application builder and use it to install NI MAX. However, after running the installer, the VISA interactive control is disabled in NI MAX.
The installer installs the following NI components: NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX. But, the installer created with the application builder does not seem to install the necessary components.
What needs to be added to the installer to enable the VISA interactive control (VISAIC)?
Thanks.
Solved!
Go to Solution.

From Pedro Munoz, Applications Engineer, National Instruments
Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
Here is the download link:
http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
And in here you can find instructions on how to get started with it:
http://zone.ni.com/reference/en-XX/help/374206A-01/
Let me know if you have any question.
Regards
Pedro Munoz
Applications Engineer
National Instruments
http://www.ni.com/support

CVI Run time engine installation

Hi,
We are using TestStand extensively and in our installation package will be
installing the CVI RTE (run-time engine). Where can I find exactly which
files (DLL's especially) are installed by the CVI RTE setup.exe?
Iain

Iain,
The CVI RTE installer installs CVIRT.dll and CVIRTE.dll in your Windows\System
directory (Win98/95) or Windows\System32 directory (Win2000/NT). It also
creates a CVIRTE directory in the same.
You can get the latest CVI RTE installer from ftp://ftp.ni.com/support/labwindows/
It consists of 2 floppy disks.
By default, the TestStand 1.0.x engine installer utility will install the
CVI 5.0.1 RTE. You can have the TS engine installer install the latest CVI
RTE by replacing the CVIRTE directory in your TestStand\Setup\Engine\ directory
*before* running the TS Engine Installation Wizard.
Hope this helps,
Paul
"Iain Simpson" wrote:
>>Hi,>>We are using TestStand extensively and in our installation package
will be>installing the CVI RTE (run-ti
me engine). Where can I find exactly
which>files (DLL's especially) are installed by the CVI RTE setup.exe?>>Iain

Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC? I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
Thanks!
Solved!
Go to Solution.

I'm guessing this is a bug that NI needs to fix. I see no reason you shouldn't be able to install the run-time engine of an older version. I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine. There are some command line switches for NI installers as mentioned here:
http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
I wonder if there is a force install option.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Run time engine and NI-DAQmx installation order

Greetings Fellow Developers:
I'm looking at a product manual that contains instructions to install NI-DAQmx, a product software installer created with LabVIEW 2009 SP1 Full and then the LabVIEW 2009 Run Time Engine in that order.
This does not seem correct--particularly if a LabVIEW 8 (or previous) Run Time Engine is already installed.
Since I need to test installation of my builds before distribution I'll need to install them on machines that have never had any NI products and also on machines that may have previous Run Time Engines.
I feel the correct order is to install the Run Time Engine, NI-DAQmx and THEN the application. Prior to running the application the USB device should be plugged in so the 'add hardware wizard' can install the USB driver(s).
What is the consensus on this?
Warm Regards,
Saturn
Solved!
Go to Solution.

Hello Saturn,
Could you point out the location of the product manual that explains this order? Typically, when installing National Instruments products, in particular LabVIEW, we recommend installing LabVIEW, drivers, and toolkits in that order. So, installing the LabVIEW 2009 Run-Time Engine, DAQmx, and then your application should be the proper installation process.
Regards,
Roman Sandoval | National Instruments | RF Systems Engineer

What's the cost of Labwindows run time engine

Dear Sir,
I have some questions about CVI and hope you can help me figure it out as usual.
1st, what's the advantage of labwindows against Labview? I know one is C programing environment and the other graphical environment. But the Labview seems more user-friendly.
2nd, What is run-time engine according to your definition? I know Matlab has similar component and is free of charge. Does the run time engine in Labwindows charge? If so, how much?
3rd, Previously, I thought labwindows is used to convert Labview program into C source code which is faster (how fast, compared with labview) and very popular in the industries, so companies do not have to buy labview and run it for just simple application in the field. But if the run time engine costs a lot, I can find no reason to use labwindows.
Thank you very much!

1) LabVIEW is a graphical based programming environment and
LabWindows/CVI is a C based programming environment. Both can be used
for similar tasks. Users familiar with C may prefer CVI. LabVIEW is
typically easier to learn if you are unfamiliar with both.
2)
The Run-Time Engine is a separate component that can be installed to
execute LabWindows/CVI programs and LabVIEW programs. It is free of
charge for both LabVIEW and LabWindows/CVI.
3)
LabWindows/CVI does not convert any LabVIEW programs into C code.
LabVIEW programs are already compiled as you write them, so you won't
need to convert them to C to use them. You should see similar
performance in similar LabVIEW and CVI code.
Allen P.
NI

How to prevent prompt to install CVI Run-Time Engine?

The LabVIEW laptop for my client got messed up, so I spent several hours making it forget everything it ever knew about NI software. I started by uninstalling all NI applications, then manually deleted all the folders that the uninstaller leaves behind, then ran a couple of registry cleaners to sweep out as much NI as possible, and finally ran regedit to see what was left. In the end there were only some legacy drivers that regedit would not let me delete.
Then I installed 8.6.1 from DVD, carefully selecting only the options we needed; LabVIEW core, cRIO, FPGA, PID, and the minimum set of drivers the installer would let me get away with. Note that no Labwindows/CVI option boxes were checked. When the installation was complete, I rebooted the machine and launched LabVIEW, which immediately prompted me to install the LabWindows/CVI 8.5.1 (not 8.6.1) Run-Time Engine. I dutifully fed it my 8.6.1 DVD, which caused LabVIEW to crash. After 3 reboot/retry cycles with the same result, I decided to appeal to the forum for help.
What is causing LabVIEW to think I need the CVI Run-Time Engine (and a down-rev version, at that), and how do I convince LabVIEW that I do not?
Jeff

Thanks for the reply! OK, so LabVIEW needs the CVI RTE even though I'm not using any CVI features. I can live with that. I downloaded LabWindows/CVI Run-Time Engine 8.5 from the NI web site and tried to install it. After I confirmed that I accepted whatever that license agreement says, the installer told me that "No software will be installed or removed."
Then I opened LabVIEW, and it went through the same "The feature you are trying to use..." popup and tried to install the CVI RTE. The installation failed as usual, and LabVIEW crashed.
A few minutes ago I found and ran CVTRTE.msi on the 8.6.1 distribution DVD. I selected the "repair" option, which completed successfully. After rebooting, I launched LabVIEW only to be greeted with the now-hated NI LabWindows/CVI 8.5.1 Run-Time Engine installer.
The part of this that is so infuriating is that there appears to be no way for anyone to make a computer forget everything NI so you can start with a clean slate.
Jeff
Attachments:
NoCanDo.jpg ‏28 KB

Does CVI install the LabVIEW Run-Time Engine?

Hello,
running the NI Update Service suggests to download a 226 MB patch for the LabVIEW 2012 Run-Time Engine... (all I installed knowingly was CVI2012)
--> How can I check if the computer has this engine installed, what is the file name to search for (and is it needed by CVI)?
Thanks!
Solved!
Go to Solution.

Hello,
1) You can use Measurement And Automation Explorer (MAX) to see the National Instruments Softwares installed:
2) Some CVI softwares use the Labview runtime.
By example, when you use the CVI Menu: Help / Find Examples... , you launch NIExampleFinder.exe which uses the labview runtime:
3) When you install the NI-VISA library, the software C:\VXIPNP\WinNT\NIvisa\NIvisaic.exe is also installed. This utility is a Labview Software.
I think it's difficult to avoid the Labview runtime on a computer with NI softwares installed...

Has NI plans to develop CVI for WinCE run time engine?

Has NI plans to develop CVI for WinCE run time engine?

At this point, LabWindows/CVI does not have plans to support Windows CE. There are many reasons we do not have plans for support, but two main reasons are:
Windows CE uses a different kernel from other Windows operatings systems.
Windows CE does not support the full WinAPI.
National Instruments
Product Support Engineer

LabView Run-Time Engine 2009 installation failure

Hi,
I have problem to install Labview Run-Time Engine 2009.
This error occur:
Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
(The installation of NI is VC2008MSMs x86 failed due to the following error.
The Windows Installer Service could not be accessed. That can occur when you run
Windows in Safe mode or Windows Installer is not installed correctly.
Contact your support personnel for assistance.)
I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
I've installed Microsoft Visual C++ 2008 Redistributable x86.
Im runing Windows XP Service Pack 3
(Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
So my question is:
How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
Best regards
Simon
Solved!
Go to Solution.

Hi,
I have already looked at that forum issue.
So I have already tried to delete all keys in regedit.
The problem is, if I continue with my installation, about 10 other new issues will appear.
And my installation will not complete, it will fail.
The installer does not install, it will tell me that the installation failed, and it will only install a few things.
Not all the things that I need to run my program.
See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
Best regards Simon
Attachments:
Pictures.zip ‏414 KB

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

Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS. From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP. Does anyone have any experience using Runtime 2009 on Windows 8?

Hi Awhite144,
The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

When I try to run a VI that is reentrant in parallel execution, I receive this error. The details of the error is: LabVIEW: The property or method is not supported in this version of LabVIEW.
This is run under the Simple Operator Interface in LV 2010. The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
Can anyone reproduce this error (bug?) ?
Solved!
Go to Solution.

have you got the latest updates for TestStand using LabVIEW 2010?
http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
Regards
Ray Farmer

LabWindows/CVI 2009 Run-Time Engine update

Similar Messages

Maybe you are looking for