Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活，以下链接可下载：
NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本
http://pcmv.cn/thread-490-1-1.html

视觉论坛的各种资源，除了视觉相关的模块有使用外，大部分的都不会使用，所以仅提供资源不能提供技术支持。资源的下载地址一般会同时提供NI官方地址和百度网盘的下载地址。某些工具包NI的地址失效或没有NI的下载地址，那视觉论坛也没有办法，只能尝试使用百度网盘地址下载；如果百度网盘的下载地址失效过期，可联系论坛客服更新。现在NI的下载服务器对我国IP地址不是很友好，有些时候速度很慢或大的资源下载很容易出错，这样会造成安装过程各种类型报错而无法安装。建议在下载完成后，对下载资源做校验和验证（NI一般会提供MD5或SHA256等），与官方或视觉论坛提供的校验和对比，一致就可以安装，如果不一致，则需要重新下载。视觉论坛早期下载的资源，那时候NI没有这么多限制，基本上都是正常下载的资源；后期下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘，所以百度网盘的资源基本上是正确的。校验和工具下载地址：
文件Hash计算器FHash,文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/thread-26524-1-1.html

LabWindows/CVI 2015 Full Win32Eng LabWindows/CVI2015完整版下载

LabWindows/CVI是一个ANSI C软件开发环境，提供一套用于开发测试和测量应用程序的完整编程工具。
LabWindows/CVI ANSI C集成编程环境可帮助您创建自定义工程应用程序。该环境可用于管理项目、编辑和调试源代码和构建用户界面，并提供一个简化的选项卡式工作区来测试代码输出和性能。LabWindow/CVI提供了高级调试、代码文档描述和系统部署所需的工具，可帮助您集成源代码控制、需求和数据管理系统。该软件还可具有内置仪器I/O库、内置仪器驱动程序或两个交互式测量辅助工具，帮助您更轻松、快速地采集GPIB、USB、串行、以太网、PXI、VXI和FPGA仪器的数据。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。

自2009版LabWindows开始，NI仅提供完整版和运行版，不再提供基本版。

2015，提供了EXE和ZIP两个版本：
官方的大小69.26MB，几十M的感觉像是补丁，可能有异常，校验码：
(MD5)c942269c92616fcab1a34aff40894d60
(SHA256)3b397b218e3c9ebb9a44eef39b10f9beaa580e3cd46f9f785487770d2a3ae3c4）
无资源

exe
文件大小: 1340474144 字节 (1.25 GB)
修改日期: 2015-06-19 16:33
MD5: b7b5c08f4d4a5e42b9aef33212e37533
SHA1: 840fda09b3f04a0e01c0e6cc9dfe3e376cdef2b2
SHA256: 6825a419ef50ef0d42338659350d68350e0ec84449c3266a2a48dc7832e68f04
CRC32: ed31052e

zip
文件大小: 1340369771 字节 (1.25 GB)
修改日期: 2019-06-25 02:59
MD5: 638d6c8b6b000c138fd345ce8ef0445e
SHA1: 684170480fd2ac3738fecf7e637bc746aca079b3
SHA256: 4aa8dc664ad241234e588a0c39f04018e261ae2818a18115ba7304891220bf78
CRC32: e50d8065

百度和NI官方下载地址：

LabWindows/CVI 2015 Full Win32Eng LabWindows/CVI2015完整版下载

http://pcmv.cn/thread-25932-1-1.html?fromuid=9

(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)

LabWindows/CVI for Windows, Version 2015 Readme

Contents

System Requirements

• Personal computer using a Pentium 4/M or equivalent microprocessor

• Microsoft operating systems:
  Note LabWindows/CVI supports only R2 editions of Windows Server

• Windows 8.1 (32-bit and 64-bit)

• Windows 8.0 (32-bit and 64-bit)

• Windows 7 (32-bit and 64-bit), including Starter Edition

• Windows Server 2012 R2 (64-bit)

• Windows Server 2008 R2 Service Pack 2 (64-bit)
  

• 1024 × 768 resolution (or higher) video adapter

• Minimum of 512 MB of RAM, 2 GB recommended

• 7 GB free hard disk space for full installation, which includes the Windows SDK 8.1 and the Microsoft .NET Framework 4.5.2; additional space needed for National Instruments Device Drivers

• Microsoft-compatible mouse
  

Installation Instructions

• LabWindows/CVI Real-Time Module

• NI Vision Development Module
  

• LabWindows/CVI Database Connectivity (SQL) Toolkit

• LabWindows/CVI Signal Processing Toolkit

• LabWindows/CVI PID Control Toolkit

• LabWindows/CVI Execution Profiler Toolkit

• NI ECU Measurement and Calibration Toolkit

• NI Automotive Diagnostic Command Set
  

• Activating LabWindows/CVI Base Package also activates the LabWindows/CVI PID Control Toolkit

• Activating LabWindows/CVI Full Development System also activates the following toolkits:
  
  

• LabWindows/CVI Database Connectivity (SQL) Toolkit

• LabWindows/CVI PID Control Toolkit

• LabWindows/CVI Execution Profiler Toolkit
  

Installation Considerations

• When installing LabWindows/CVI, the LabWindows/CVI Real-Time Module, and NI Device Drivers, install device drivers after the LabWindows/CVI Real-Time Module. If you install all of these products at the same time using the LabWindows/CVI Platform DVD, the products are installed in the correct order. If you install the LabWindows/CVI Real-Time Module on a computer that already has device drivers installed, reinstall the device driver software to ensure that real-time support is installed for the device drivers you selected.

• The LabWindows/CVI installation includes the LabWindows/CVI 2015 Runtime. This version replaces any previous version of the LabWindows/CVI Runtime. After you install LabWindows/CVI 2015, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2015 Runtime.
  
  To restore the previous runtime, uninstall LabWindows/CVI 2015 and any previous versions of LabWindows/CVI on the computer. Then reinstall the LabWindows/CVI version you want to use.

• If you install LabWindows/CVI onto a network drive, you might encounter an error during installation that prevents files that the IVI Instrument Driver Wizard requires from being installed. This issue does not affect other functionality in LabWindows/CVI.

• If you have installed Microsoft Security Update 896358, you might not be able to view topics within the LabWindows/CVI Help if the file is on a network drive. To solve this issue, copy the .chm files that LabWindows/CVI installs to your local hard drive and launch them as normal.

• The IVI Installer Creator and IVI Specific Driver Test Suite items are selected by default in the installer feature tree only if the IVI Compliance Package is installed. You can select these items if the IVI Compliance Package is not installed, but you must then install the IVI Compliance Package, which you can download from ni.com. The IVI Compliance Package is also available on the NI Device Drivers media.

• You can install the Visual Studio Wizards feature only if you have installed the version of Visual Studio corresponding to the Visual Studio Wizard you select.

• If your software is part of a Volume License Agreement (VLA), contact your VLA administrator for installation instructions.
  

Running the Installation

• Insert the LabWindows/CVI media into the disk drive. If the media does not run automatically, open Windows Explorer, right-click the disk drive icon, and select AutoPlay.

• On installation startup, the National Instruments LabWindows/CVI screen appears. Click Install LabWindows/CVI, Modules, and Toolkits.

• Continue to follow the instructions on the screen.
  
  Note  If you have a serial number for the product you want to install, enter the number during installation when you are prompted. You also can activate the product after installation. For more information about finding serial numbers, refer to ni.com/info and enter SerialNumbers_en as the Info Code.

• If you selected Device Drivers in the Product List, the LabWindows/CVI installer prompts you to insert the National Instruments Device Drivers DVD after you install LabWindows/CVI and any selected modules and toolkits. Follow the instructions on the screen to install the device drivers.

• If you have an active Internet connection, the installer prompts you to select Windows SDK components to install. The components you select are downloaded and installed from the Microsoft website. For more information about the components, refer to ni.com/info and enter the Info Code CVI2015_WindowsSDK.
  
  If you do not have an active Internet connection, LabWindows/CVI installs all Windows SDK components, which might not be the latest components available on the Microsoft website.
  
  Note  If you cancel the Windows SDK installation, LabWindows/CVI will not function properly. You can download the Windows SDK from one of the following places:
  

• The Microsoft website

• ni.com—Visit ni.com/info and enter the Info Code DownloadMSDTWindowsSDK
  

• Install hardware. Refer to your device documentation, such as printed manuals or PDFs, for information about installing your NI hardware.

• To activate a National Instruments product, refer to the Activating LabWindows/CVI section.
  

Activating LabWindows/CVI

After Installation

• Installing LabWindows/CVI in a New Directory—If you installed driver or toolkit software for LabWindows/CVI 8.1.1 or earlier and you install LabWindows/CVI 2015 in a new directory, you must uninstall and reinstall the LabWindows/CVI portion of the driver or toolkit software.

• Using Example Programs—You can find example programs in the following location: UsersPublicDocumentsNational InstrumentsCVI2015samples.

• Working with Project and File Templates—Save user-defined project and file templates in the LabWindows/CVI public documents directory (UsersPublicDocumentsNational InstrumentsCVI. LabWindows/CVI 8.5 and later does not search previous locations, Documents and SettingsAll UsersApplication DataCVI and Documents and Settings<User ID>Application DataCVI, for project and file templates.

• Making Backup .uir Files—Make backup copies of your .uir files if you have been using previous versions of LabWindows/CVI. Once you save .uir files in LabWindows/CVI 2015, the .uir files are no longer compatible with versions 8.1.1 or earlier. You cannot load .uir files that you have saved in LabWindows/CVI 2015 in LabWindows/CVI 8.1.1 or earlier.
  
  You can save .uir files you create or load in LabWindows/CVI 2015 in earlier formats. Select File»Save .uir As and specify the format in the Save as type option. If you save a user interface with features that were added in later versions of LabWindows/CVI, those features are removed when you save the file in earlier formats.
  

Product Security and Critical Updates

Behavior Changes in LabWindows/CVI

Behavior Changes Introduced in LabWindows/CVI 2015

• The LabWindows/CVI installation includes the complete Windows 8.1 SDK.

• The Instrument I/O Assistant is no longer accessible by default through the LabWindows/CVI environment. The Tools»Create Instrument I/O Task is no longer available.

• The DIAdem Connectivity Library is no longer available by default. To use this library, select Library»Customize and enable the DIAdem Connectivity option. NI recommends that you use the TDM Streaming Library for new projects.

• The NI-USI component, which is necessary for applications that use the DIAdem Connectivity Library, is no longer included in the LabWindows/CVI Runtime. To deploy applications that use DIAdem Connectivity Library functions, create an installer and select the NI USI item in the Drivers & Components tab of the Edit Installer dialog box.

• The Variables and Call Stack window lists static local variables before local variables. In previous versions of LabWindows/CVI, local variables appeared before static local variables.

• You cannot use LabWindows/CVI 2013 to debug DLLs you create with LabWindows/CVI 2015.

• Files installed with the Windows SDK are in different locations than in previous versions of LabWindows/CVI:

  Files	Previous Location	Current Location
  Import libraries	<cvidir>sdklib	<;Program Files>Windows Kits8.1Libwinv6.3um� (or d)
  Include files	<cvidir>sdkinclude	<;Program Files>National InstrumentsSharedMSDTRedistributablesSDKHeaderFiles8.1

  
  

Behavior Changes Introduced in LabWindows/CVI 2013 SP2

• Activating the LabWindows/CVI Base Package also activates the LabWindows/CVI PID Control Toolkit.

• Activating the LabWindows/CVI Full Development System also activates the LabWindows/CVI PID Control Toolkit, LabWindows/CVI Database Connectivity (SQL) Toolkit, and LabWindows/CVI Execution Profiler Toolkit.
  

Behavior Changes Introduced in LabWindows/CVI 2013 SP1

• You can specify a .c file as the module to load to the LoadExternalModule and LoadExternalModuleEx functions.
  

Behavior Changes Introduced in LabWindows/CVI 2013

• The following product components no longer appear in the tree on the Driver and Components tab of the Edit Installer dialog box:
  
  If you select NI LabWindows/CVI Shared Runtime Engine from the tree, LabWindows/CVI includes these components automatically.

• Standard Runtime

• Instrument Driver Runtime

• Real-Time Runtime
  

• The minimum installer size when including the runtime engine increased by approximately 41MB compared to previous versions of LabWindows/CVI. To decrease the size of your distribution, you can include LabWindows/CVI merge modules. For more information, refer to KB 6AHC1EQW.

• The Install LabWindows/CVI Shared Runtime Engine in the application directory option on the Advanced tab of the Edit Installer dialog box is deprecated. If you need to install and preserve a specific version of the LabWindows/CVI Runtime Engine, consider installing the LabWindows/CVI Side-by-Side Runtime Engine. Refer to the Binding Executables and DLLs to Side-by-Side Runtime Engines topic in the LabWindows/CVI Help for more information about the Side-by-Side Runtime Engine.

• The Project Tree no longer displays the Status column.

• If you enable the Build with C99 extensions option, the Require function prototypes option is always implicitly enabled.

• The results of several mathematical operations performed using floating-point numbers might differ from results returned in previous versions of LabWindows/CVI. The differences are small and within acceptable error ranges for the data types.

• Function calls are no longer allowed in watch expressions or in the condition of a breakpoint.

• You must rebuild any EXEs and DLLs built in LabWindows/CVI 2012 or earlier in LabWindows/CVI 2013 before you can debug them.

• You cannot debug EXEs and DLLs built in LabWindows/CVI 2013 in LabWindows/CVI 2012 or earlier.

• Displaying extended data in the Variables and Call Stack window is available only when a program stops gracefully, for example, as a result of a breakpoint or when stepping through code. Extended data is unavailable in the following instances:
  

• If the program breaks as a result of an exception

• If you manually break execution, for example, by pressing the Stop button
  

• Expressions in the Watch window do not update continuously while a program is running.

• You can no longer choose scope in the Watch window. All variables and expressions in the Watch window are evaluated in the current context.

• Watch expressions that you save in LabWindows/CVI 2013 cannot be loaded by LabWindows/CVI 2012 or earlier.

• Some C99 features are available in C89.

• When debugging a real-time application via LabVIEW, LabWindows/CVI does not stop listening when the VI is unloaded. You must either Disconnect or Abort and reboot.

• When graphs scale, they will always scale to the thickness of their line plots. In previous versions of LabWindows/CVI, only plots whose thickness was greater than 1 scaled up or down.

• LabWindows/CVI no longer links to gpibstub.obj or vxistub.obj.

• To use the ExportStyle method in 3DGraphCtrl.fp, you must specify the directories to which you want to export files. Refer to KB 67L8L0QW for more information about using the ExportStyle method.

• LabWindows/CVI 2013 includes updated bracket and indentation styles. You can continue using bracket and indent styles available in previous versions of LabWindows/CVI by selecting the Use CVI legacy formatting option in the Editor Preferences dialog box. Some of the legacy formatting options map to the updated styles except for the following combinations:
  
  
  Note that if you select a legacy formatting option, batch auto indent support (selecting Edit»Format File and Edit»Format Selection), is unavailable.

• Function brackets set to uneven, left; statement brackets set to uneven, right

• Function brackets set to uneven, left; statement brackets set to flush, left

• Function brackets set to uneven, left; statement brackets set to flush, right

• Function brackets set to uneven, right; statement brackets set to uneven, left

• Function brackets set to uneven, right; statement brackets set to flush, left

• Function brackets set to uneven, right; statement brackets set to flush, right

• Function brackets set to flush, left; statement brackets set to uneven right

• Function brackets set to flush, left; statement brackets set to flush right

• Function brackets set to flush, right; statement brackets set to uneven, left

• Function brackets set to flush, right; statement brackets set to uneven, right

• Function brackets set to flush, right; statement brackets set to flush, left
  

• The LabWindows/CVI Help no longer includes a Font button for increasing or decreasing the font size in the help file. Refer to KB 696A8AOA for more information.

• The Options»Generate Visual Basic Include menu item is no longer available.

• LabWindows/CVI 2013 now returns 2 as the size of variables of type wchar_t, which is consistent with the ANSI C specification. You must recompile existing code in LabWindows/CVI 2013 to see the change in behavior.

• LabWindows/CVI 2012 returned certain compiler errors that are now returned as warnings. Refer to KB 6A9GOOQW for more information.

• LabWindows/CVI 2012 returned certain compiler errors that are no longer errors. Refer to KB 6A9GO5QW for more information.

• Using the token-pasting operator (##) might return compiler errors that were not returned in LabWindows/CVI 2012.

• The Conservative and Aggressive levels of unitialized local variables detection are now combined into one compiler warning. You might notice more unitialized local variables warnings because LabWindows/CVI now flags all variables that may or may not have values assigned to them. This behavior more closely matches the Aggressive level for the Uninitialized local variables detection option in previous versions of LabWindows/CVI.

• You must enable the Include project files in Interactive window or Include loaded instrument drivers in Interactive window options if you run code in a function panel or in the Interactive Execution window that has dependencies on other files in the project or on a loaded instrument driver.

• You cannot view the values of #define macros when you are debugging.

• You cannot specify a .c file as the module to load to the LoadExternalModule and LoadExternalModuleEx functions.

• The Up Call Stack menu item moves toward the callee. The Down Call Stack menu item moves toward the caller. In previous versions of LabWindows/CVI, the Up Call Stack menu item moved toward the caller, while the Down Call Stack menu moved toward the callee.

• You can separate multiple compiler defines using a comma and a space.
  

Behavior Changes Introduced in LabWindows/CVI 2012

• The Physical Memory Access functions, located in the Utility Library, are deprecated. Refer to KB 5QCCQSQW for more information.

• If your program includes any Port IO functions, located in the Utility Library, the program will require administrator privileges to run. Refer to KB 5Q5FO1QW for more information.

• The LabWindows/CVI low-level support driver can be loaded only by applications running with administrator privileges on 32-bit systems. Refer to KB 5Q5FJ4QW for more information.

• You can no longer create a reduced-size distribution that includes the low-level support driver. If your application uses the low-level support driver, you must include the full LabWindows/CVI Runtime Engine in your installer. To include the full runtime engine in your installer, complete the following:
  Refer to KB 5R6A4SQW for more information.

• Select the NI LabWindows/CVI Shared Runtime Engine item in the Drivers & Components tab of the Edit Installer dialog box.

• Ensure that you deselect the Install the LabWindows/CVI Shared Runtime Engine in the application directory option in the Advanced tab of the Edit Installer dialog box.
  

• The GetFontTypefaceName function, when used on VAL_DIALOG_FONT or VAL_DIALOG_META_FONT, now returns the actual typeface of the dialog font on your system, rather than the substitute for that font that Windows uses.

• LabWindows/CVI 2013 supports the Perforce SCC Plug-in (P4SCC) 2006.1 and later.

• For projects you save in LabWindows/CVI 2013, LabWindows/CVI attempts to resolve paths that were previously saved as absolute paths to be relative to the project. You can override this behavior by specifying the following options in the .prj file:
  
  For a target file, specify the following in the [Create Executable] section of the .prj file:
  Executable File_Configuration Force Path Absolute = True
  
  where _Configuration is the configuration of your target, such as Debug, Release, or Debug64.
  
  For a file in the project list, specify the following in the [File nnnn] section of the .prj file, where nnnn is the index of the file in the project list:
  Path Force Path Absolute = True

• You can call .NET Library functions from multiple threads simultaneously without getting blocked.

• Previous versions of LabWindows/CVI did not recognize numbers entered in scientific notation for numeric controls of type int64 or unsigned int64. Starting with LabWindows/CVI 2010 SP1, you can enter numbers in scientific notation. When you enter a number in scientific notation into numeric controls of type int64 or unsigned int64, LabWindows/CVI converts the number to a double and then to a 64-bit integer. This conversion may cause a loss of precision after 15 decimal digits.

• LabWindows/CVI 2010 SP1 includes the GaussHypergeometric function, which you should use instead of the GaussHG function.
  

Behavior Changes Introduced in LabWindows/CVI 2010

• To specify multiple compiler defines, separate each compiler define using only a space. If you separate each one with a comma and a space, LabWindows/CVI displays an error.

• Build Options and Target Settings dialog box options apply per configuration. The options on these dialog boxes are no longer global as in previous releases.

• National Instruments no longer supports Windows 2000.

• The minimum operating system version for distributions is Windows XP. If you open an existing distribution that specifies Windows 2000 as the minimum operating system, LabWindows/CVI updates the minimum operating system to Windows XP.

• If you install the Full Development System, the Interface to Win32 Application Programmatic Interface (API) is installed by default.

• The glaux.lib import library is deprecated and is no longer included with LabWindows/CVI. The glaux.prj sample program is no longer installed.

• The Save changes before debugging option in the Environment dialog box is now a global option. In previous releases, this option was workspace-specific.

• The Save changes before compiling option in the Environment dialog box is enabled by default. This global option allows LabWindows/CVI to save all modified files before compiling and debugging.

• LabWindows/CVI no longer installs the Documentation from MSDN Library. National Instruments recommends that you view the latest version of this documentation at www.msdn.com. For more information, visit ni.com.
  

Behavior Changes Introduced in LabWindows/CVI 2009

• Borland is no longer supported as a compatible compiler or as a third-party compiler in LabWindows/CVI.

• Starting with the 2009 version of LabWindows/CVI, major versions align with the year in which they release. For example, this version of LabWindows/CVI is called LabWindows/CVI 2015. You can find installed files in the CVI2015 folder in the various locations where LabWindows/CVI installs files. The registry keys corresponding to this version of LabWindows/CVI are located in CVI .0 in the registry.

• The NI Distributed System Manager replaces the NI Variable Manager. Use the System Manager to create and monitor network variables, processes, and I/O servers. For more information about the System Manager, refer to the NI Distributed System Manager Help, which you can access from the System Manager.

• The Translate LW DOS Program option is no longer available.

• The LabWindows/CVI compiler now defines the NDEBUG macro for release configuration builds.

• LabWindows/CVI no longer adds _dbg suffix to the base name of the debug target of a project.

• The data type of the targetThreadId parameter of the PostDeferredCallToThread and PostDeferredCallToThreadAndWait functions has been changed from unsigned long to unsigned int.
  

Behavior Changes Introduced in LabWindows/CVI 9.0 and Earlier

• toolbox.h now includes some LabWindows/CVI headers that must be included after including windows.h. Therefore, if your code includes toolbox.h before including windows.h, reverse the order of these includes.

• Network variable processes that begin with NI_ are disallowed. The CNVNewProcess function returns an error if the process name you specify begins with NI_.

• The following macros have been renamed:
  
  

  Library	Previous Macro Name	New Macro Name
  WordReport.fp Instrument Driver	NONE	WR_NONE
  Analysis Library	SORT_ASCENDING	ANALYSIS_SORT_ASCENDING
  Analysis Library	SORT_DESCENDING	ANALYSIS_SORT_DESCENDING

• Upgrading to LabWindows/CVI 8.5 and later may cause the Advanced Analysis or Analysis Library to produce numerical differences in floating point results and different results for exceptional inputs, such as positive or negative infinity and NaN. These differences may occur because the underlying C Analysis library has been recompiled in LabWindows/CVI 8.5 to take advantage of new processors and operating systems.

• The enum value CVIConst_CVI_FPVERSION_90 has been changed to CVIConst_CVI_FPVERSION_85 for the fpVersion parameter of the FPGenCreateFunctionTree function of the LabWindows/CVI ActiveX Server Interface Library.

• The modini utility and related source code as well as the modreg source code are deprecated and no longer installed with LabWindows/CVI.

• The LabWindows/CVI Quick Reference card is no longer published and is not installed with LabWindows/CVI.

• The option to create Microsoft Windows WinHelp files (.hlp) from LabWindows/CVI, Generate»Documentation»Windows Help, is no longer available.

• The Network Variable Library flushes all internal buffers in a write operation, which improves network variable performance.
  
  Flushing on write may cause lower throughput in some high bandwidth conditions, in which case you can set CNVFlushOnWriteAttribute to 0 (FALSE). In high bandwidth conditions, National Instruments recommends using the CNVBufferedWriter connection.

• During a read operation, the Network Variable Library flushes all network variable connections in your program, including data in writer connections, for better performance.

• Registering ActiveX Servers—When you build ActiveX servers in LabWindows/CVI 8.1.1 and later on Windows XP and later, the ActiveX servers are registered in your user profile. This registration is not visible to other users on your system. On versions of Windows prior to Windows XP, ActiveX servers are registered for all users. When you register these servers outside the LabWindows/CVI environment, they are always registered for all users; this option requires administrator privileges on Windows Vista and later.

• Analysis Function Behavior Changes—The following function behavior has changed from LabWindows/CVI 7.1 to LabWindows/CVI 8.x:
  
  

• SVD and CxSVD—The following formula defines the SVD factorization of an n-by-m matrix A: A = USVT.
  
  In LabWindows/CVI 7.1 and earlier, U is an orthogonal matrix of dimensions n-by-m. In LabWindows/CVI 8.x and later, U is an orthogonal matrix of dimensions n-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, V is an orthogonal matrix of dimensions m-by-m. In LabWindows/CVI 8.x and later, V is an orthogonal matrix of dimensions m-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, S is a diagonal matrix of dimensions m-by-m. In LabWindows/CVI 8.x and later, S is a diagonal matrix of dimensions min(n, m)-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, CxSVD has the following requirement: If numberOfRows (n) < numberOfColumns (m), you must allocate m*m*sizeof(ComplexNum) bytes of memory to the input matrix and the U orthogonal matrix. LabWindows/CVI 8.x and later no longer has this requirement.

• Lu and CxLU—In LabWindows/CVI 7.1 and earlier, if the input matrix is singular, the functions stop the decomposition and return SingularMatrixErr. In LabWindows/CVI 8.x and later, if the input matrix is singular, the functions complete the decomposition and return SingularMatrixWarn. In this case, there are one or more zero elements along the diagonal of U.

• CxTrace—CxTrace accepts only a square matrix. In LabWindows/CVI 7.1 and earlier, the function requires both the number of rows and the number of columns as input parameters. In LabWindows/CVI 8.x and later, matrixSize specifies both the number of rows and the number of columns. The numberOfColumns parameter in LabWindows/CVI 7.1 and earlier is a reserved parameter in LabWindows/CVI 8.x and later. This parameter is not referenced in the function.

• ConditionNumber and CxConditionNumber—In LabWindows/CVI 7.1 and earlier, these functions return NaN for singular input matrices. In LabWindows/CVI 8.x and later, these functions return Inf for singular input matrices.

• GenLSFit—In LabWindows/CVI 8.x and later, GenLSFit calculates the mean squared error as the weighted mean square error, which differs from the prior implementation of the function.
  

Known Issues

• Selecting Values in IviFgen Class Driver—In the IviFgen FP file, the Attribute ID and Attribute Value controls in the Get/Set/CheckAttributeViInt64 functions display an empty field instead of a list of attributes and values. For more information, refer to KnowledgeBase 5WOA752F: Issue Setting IviFgen Attribute ID Using Get/Set/CheckAttributeViInt64 Functions.

• Uninstalling LabWindows/CVI—If you have multiple versions of LabWindows/CVI installed and you uninstall one of the versions, the remaining installation will be missing its file associations, and its automation capabilities will not function properly. To fix this problem, perform a repair installation of the remaining LabWindows/CVI version.

• Error When Building a LabWindows/CVI Project in Visual Studio 2005—If you create a project in Visual Studio 2005 that uses LabWindows/CVI libraries, you will see the following error: fatal error LNK1103: debugging information corrupt; recompile module. To address this issue, install the hotfix available from Microsoft.

• Debugging Executables on Windows—On Windows Vista and later, executables that contain setup, install, or update as part of their name automatically require administrator privileges. If you run these executables as stand-alone from a user-level account, Windows will prompt you for an administrator password. However, LabWindows/CVI cannot debug these applications from a user-level account. When you try to run them, LabWindows/CVI displays a Could not run executable notification. NI recommends that you rename your executable so that it does not contain those words in its name, or that you embed a manifest into the application that marks the application as being Vista-aware. You can embed a manifest using the Target Settings dialog box.

• Viewing Help—If you open the LabWindows/CVI Help outside of LabWindows/CVI, such as launching it through the Start menu, you might not see all driver or toolkit content. Select Help»Contents to open the LabWindows/CVI Help from within LabWindows/CVI to ensure that all driver and toolkit content is available.

• Using the LabWindows/CVI Conversion Wizard in Microsoft Visual Studio—Microsoft Visual Studio 2005 and later do not support the single-threaded version of the Visual Studio C library. Therefore, you must configure your project's linker settings to ignore directives to use the single-threaded C library. In Visual Studio, select Project»Properties and expand the properties tree to the Configuration Properties»Linker»Input item. Add libc to the Ignore Specific Library option. Refer to the I Receive Linker Errors When Using LabWindows/CVI-Generated Static Libraries and Object Files in Microsoft Visual Studio 2005 KnowledgeBase article for more information.
  

Bug Fixes

Accessing the Help

Finding Examples

Automating the Installation of NI Products

• For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.

• For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate the Installation of a Suited Installer?.

• To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My National Instruments Installer?.
  

How to Use NI Software with Microsoft Windows 8.x

Using NI Launcher

Pinning Frequently Used Applications

Finding All Programs

NI LabWindows/CVI Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2015

Legal Information

• Notices are located in the <National Instruments>_Legal Information and <National Instruments> directories.

• EULAs are located in the <National Instruments>SharedMDFLegallicense directory.

• Review <National Instruments>_Legal Information.txt for information on including legal information in installers built with NI products.
  

• 上篇：LabWindows/CVI 2013 SP2 Runtime Win32Eng LabWindows/CVI2013SP2运行版下载
• 下篇：LabWindows/CVI 2015 Runtime Win32Eng LabWindows/CVI2015运行版下载
• 标签：LabWindowsCVI 2015NI CVIANSI C软件LabWindows文本编程语言LabWindows测试测量开发平台