LabVIEW Base Development System 8.2.1 - Windows/2000/Vista x64/Vista x86/XP - 8.2.1f4 Patch

14 calificación | 3.00 fuera de 5

Imprimir Documento

Descripción

The LabVIEW 8.2.1f4 patch resolves five distinct issues:

1. This patch fixes an issue that prevented saving to an existing VI on some shared network drives. When this occurred, LabVIEW returned the following error: "Generic file I/O error. Cannot save VI." The fix involves saving the VI to the temp directory and then instructing the OS to move it to the correct destination. This is how LabVIEW saved VIs prior to version 8.2, which was changed in 8.2 for performance reasons. To enable this fix, install this patch and set saveToTempFileFirst=True in Labview.ini.



2. This patch fixes an issue in the LabVIEW Run-Time Engine that prevented custom steps in LabVIEW SignalExpress from properly loading .NET controls. If you create two custom LabVIEW SignalExpress steps that each use the same .NET control, opening the second step does not correctly load the .NET control. This change fixes this issue. Note, "custom steps" are not the same as "user steps", which are simply VIs prepared in LabVIEW to be used as steps in LabVIEW SignalExpress. Creating custom LabVIEW SignalExpress steps requires additional technology.



3. This patch fixes a DataSocket function that was not threadsafe. When controls or indicators are bound to a DataSocket connection through the front panel, this non-threadsafe function performed an unprotected memory opperation which can result in a LabVIEW or LabVIEW Runtime Engine crash. This fix is recommended for anybody using DataSocket control or indicator bindings.



4. The LabVIEW 8.2 and 8.2.1 run-time engine requires specific registry entries to be present to load properly. These keys are set during a normal install of the LabVIEW run-time engine. This patch includes a modification to the LabVIEW run-time engine to disable this check. Users will notice no change in functionality unless they were attempting to load the LabVIEW run-time engine DLL without it being installed normally.



5. When a VI is loaded into memory, a check is performed for any ActiveX type library to determine if the library has changed. If the library has changed, the VI relinks references to the new version of the type library and recompiles the code. In LabVIEW 8.0 and prior, the check to determine if a relink/recompile only looked at the version of the type library. In LabVIEW 8.2.x, the on-disk timestamp of the type library is also checked. This means that, in LabVIEW 8.2.x, if a type library differs in timestamp only, it will still need to be relinked and recompiled. This causes many problems for customers using source code control systems since it they are not able to tell which VIs have been changed due to these recompile issues, and which are compiled due to changes in the program. LabVIEW 8.2.1 was patched to disable the timestamp check if ignoreTypeLibraryTimeStamps=true is set in Labview.ini

Notas de Instalación

This patch does not have an installer. See readme_lv821f4.txt for installation instructions and system requirements.

Comentarios

Califique este documento: Seleccione una calificación 1 2 3 4 5
¿Se Resolvieron Sus Preguntas? Sí No