LabWindows/CVI 2010 SP1 Patch Win32Eng LabWindows/CVI2010SP1补丁下载

石鑫华视觉

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

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

LabWindows/CVI 2010 SP1 Patch Win32Eng LabWindows/CVI2010SP1补丁下载

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

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

2010SP1 Patch
文件大小: 48592945 字节 (46.34 MB)
修改日期: 2019-06-25 03:00
MD5: 9d52a0ce527e7850546a7a3b374ae8c9
SHA1: abca2c8667b94517bcfc28939eb41dd4104f935e
SHA256: 872462b71005e8b3529c47ad92df4d9f40679e09910aefe1ef4e199dea4df83e
CRC32: 6f657e0b

百度和NI官方下载地址：
CVI2010SP1Patch.txt (596 Bytes, 下载次数: 0, 售价: 5 元)

2020-12-9 23:35 上传

点击文件名下载附件

LabWindows/CVI for Windows, Version 2010 Service Pack 1Readme File

This file contains installation information, programming considerations, and changes that are too recent to be included in the LabWindows/CVI Help for LabWindows/CVI 2010 Service Pack 1. Refer to the LabWindows/CVI Release Notes for more information about new features.

Note  Installing LabWindows/CVI 2010 SP1 replaces any previous version of the LabWindows/CVI Run-Time Engine with the LabWindows/CVI 2010 SP1 Run-Time Engine. To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2010 SP1 and any previous versions of LabWindows/CVI on the computer. Then reinstall the LabWindows/CVI version you want to use, along with any additional National Instruments software you might have installed.

Contents

Minimum System Requirements
Installing LabWindows/CVI
Activating LabWindows/CVI
After Installation
Upgrading from LabWindows/CVI 2010 or Earlier
Upgrading from LabWindows/CVI 2009 or Earlier
Upgrading from LabWindows/CVI 9.0 or Earlier
Upgrading from LabWindows/CVI 8.5 or Earlier
Known Issues
Bug Fixes

Minimum System Requirements

To run LabWindows/CVI 2010 SP1, you must have the following:

• Personal computer using a Pentium 1 GHz or higher microprocessor
• Microsoft operating systems:
  
  • Windows 7, including Starter Edition (32-bit and 64-bit)
  • Windows Vista (32-bit and 64-bit)
  • Windows XP Service Pack 2 (32-bit)
  • Windows Server 2008 R2 (64-bit)
  • Windows Server 2003 R2 (32-bit)
    
• 1024 × 768 resolution (or higher) video adapter
• Minimum of 128 MB of RAM, 512 MB recommended
• 1.1 GB free hard disk space for full installation, which includes the Interface to Win32 Application Programmatic Interface (API)
• Microsoft-compatible mouse
  

Notes

LabWindows/CVI supports only R2 editions of Windows Server National Instruments software supports Windows 7 Starter Edition; however, NI software does not support Windows Vista Starter Edition

Installing LabWindows/CVI

National Instruments recommends that you install the complete LabWindows/CVI program to take full advantage of all LabWindows/CVI 2010 SP1 functionality. If you choose to install with options, select the options you want and follow the on-screen directions. If necessary, you can run the setup program again to install or remove additional files.

Before Installation

• 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.
• When you install LabWindows/CVI, your user account must have administrator privileges.
• The complete Interface to Win32 API is available with the LabWindows/CVI Full Development System. Some Win32 API header and import library files are included when you install the LabWindows/CVI Base Package.
• The LabWindows/CVI installation includes the LabWindows/CVI 2010 SP1 Run-Time Engine. This version replaces any previous version of the LabWindows/CVI Run-Time Engine. After you install LabWindows/CVI 2010 SP1, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2010 SP1 Run-Time Engine.
  
  To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2010 SP1 and any previous versions of LabWindows/CVI on the computer. Then reinstall the LabWindows/CVI version you want to use, along with any additional National Instruments software you might have installed.
• 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.
• You can install the Visual Studio 2005 Wizards and Visual Studio 2008 Wizards features only if you have installed Visual Studio 2005 and Visual Studio 2008, respectively.
  

Running the Installation

The LabWindows/CVI Platform DVD includes LabWindows/CVI and the following modules and toolkits.

Modules

• Real-Time Module
• Vision Development Module
  

Toolkits

• Execution Profiler Toolkit
• PID Toolkit
• Real-Time Execution Trace Toolkit
• Signal Processing Toolkit
• SQL Toolkit
  

If you purchased any of these modules or toolkits, you can install them using the LabWindows/CVI Platform DVD. If you want to evaluate any of these modules or toolkits before purchasing them, you can install these add-ons from the LabWindows/CVI Platform DVD and try them for free for 30 days. Refer to each toolkit or module Readme for more information about installing with media other than the LabWindows/CVI Platform DVD.

Complete the following steps to install LabWindows/CVI:

Notes

If you already have a different version of LabWindows/CVI installed on your computer, be sure to install version 2010 SP1 in a different directory. If you have LabWindows/CVI 2010 installed on your computer, the LabWindows/CVI installer replaces LabWindows/CVI 2010 with LabWindows/CVI 2010 SP1. If you want to install to an existing directory, uninstall the other version before installing LabWindows/CVI 2010 SP1. When you install LabWindows/CVI, your user account must have administrator privileges.

• 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 2010 screen appears. Click Install LabWindows/CVI, Modules, and Toolkits.
• Continue to follow the instructions on the screen.
• 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.
• To activate a National Instruments product, refer to the Activating LabWindows/CVI section.
  

Activating LabWindows/CVI

You can activate LabWindows/CVI during installation or when you launch LabWindows/CVI for the first time. To activate during installation, enter a serial number when you are prompted by the installer. If you entered a serial number during installation, LabWindows/CVI prompts you to confirm the activation when you launch LabWindows/CVI for the first time. If you do not activate during installation, you can launch the NI Activation Wizard by selecting Activate Products in the License Status dialog box, which displays when you start LabWindows/CVI for the first time.

For more information about activation, refer to the Activating Your Software topic in the LabWindows/CVI Help.

Note  If you are unable to activate LabWindows/CVI, refer to the NI License Activation Web page at ni.com/activate.

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 2010 SP1 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 on Windows 7/Vista/Server 2008: \Users\Public\Documents\National Instruments\CVI2010\samples. On Windows XP/Server 2003, example programs are located in the following location: \Documents and Settings\All Users\Documents\National Instruments\CVI2010\samples.
• Working with Project and File Templates—Save user-defined project and file templates in the LabWindows/CVI public documents directory (\Documents and Settings\All Users\Documents\National Instruments\CVI on Windows XP/Server 2003 and \Users\Public\Documents\National Instruments\CVI on Windows 7/Vista/Server 2008). LabWindows/CVI 8.5 and later does not search previous locations, \Documents and Settings\All Users\Application Data\CVI and \Documents and Settings\\Application Data\CVI, for project and file templates.
  

Upgrading from LabWindows/CVI 2010 or Earlier

• 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 2010SP1, 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 2010SP1 includes the GaussHypergeometric function, which you should use instead of the GaussHG function.
  

Upgrading from LabWindows/CVI 2009 or Earlier

• 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.
  

Upgrading from LabWindows/CVI 9.0 or Earlier

• 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 2010. You can find installed files in the CVI2010 folder in the various locations where LabWindows/CVI installs files. The registry keys corresponding to this version of LabWindows/CVI are located in CVI\10.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.
  

Upgrading from LabWindows/CVI 8.5 or 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

• 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.
  

Known Issues

This version of LabWindows/CVI has the following known issues. For a complete list of known issues, refer to ni.com.

• Using EVENT_INTERACTIVE_LEGEND for Strip Chart Controls—Although trace indices for strip charts are 1-based, the values for trace indices returned by eventData1 are 0-based. For example, for an event that refers to trace 3, the value returned by eventData1 is 2.
  
  For backwards-compatibility purposes, National Instruments is not correcting this behavior.
• Using the IVI Specific Driver Test Suite—To use the IVI Specific Driver Test Suite in LabWindows/CVI 2010 SP1 or later, you must have ICP 4.4 installed on your computer.
• Incorrect Reference in LabWindows/CVI Release Notes—The LabWindows/CVI Release Notes references the DetachDebugger ActiveX Server Interface function. However, this function is not included in LabWindows/CVI 2010.
• Selecting Files Using Libraries Shortcut—In Windows 7, the Libraries shortcut item in file dialog boxes does not work correctly.
• Zooming Graph Axis—Zooming a graph axis can skew a plot when the magnification becomes too large.
• Using Perforce with LabWindows/CVI—LabWindows/CVI crashes when using the Perforce 2009.1 source code control plug-in.
• Displaying Popups—Second popup can appear behind another popup if the application is not in the foreground when the second popup is displayed.
• Displaying Panels and Windows in Windows 7—LabWindows/CVI panels and windows do not support Aero Shake.
• Availability of Example Programs for Base Package—Examples that only work in FDS are listed in Example Finder when Base version is activated.
• Displaying PNG Images—PNG images with alpha-channel transparency lose their transparency when displayed on transparent classic-style picture controls.
• Numerical Differences in Analysis Function Results—LabWindows/CVI 2010 uses the latest version of the Intel® Math Kernel Library (MKL). Some of the functions in the Intel MKL return different results compared to previous versions of MKL due to optimization, causing slight numerical differences between results from Vector and Matrix Algebra, Statistics, and Curve Fitting functions in LabWindows/CVI 2010 and previous versions of LabWindows/CVI.
• 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.
• Flushing Internal Buffers in a Network Variable Write Operation—Starting with LabWindows/CVI 8.5.1, 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.
• Flushing Internal Buffers in a Network Variable Read Operation—During a read operation, the Network Variable Library flushes all network variable connections in your program, including data in writer connections, for better performance.
• Debugging Executables on Windows Vista—On Windows Vista, 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.
• Performing DAQmx USB Buffered Operations on Windows Vista—On Windows Vista x64 Edition, running a program that uses NI-DAQmx 8.5 and terminating the program while it is performing DAQmx USB buffered operations can cause the machine to reboot or to display a Windows kernel bugcheck.
  
  The following may cause a process to terminate unexpectedly:
  
  • Selecting the End Process option in the Task Manager to kill the process.
  • Using a utility such as pskill to request process termination.
  • Shutting down the computer from the command line using shutdown -r -t 0 while the task is still running.
  • The process encountering an access violation, breakpoint, or other unhandled exception.
  • Attempting to log off, restart, or shutdown and clicking Cancel when the process prompts you to quit or cancel.
  • Choosing to stop the process from the LabWindows/CVI debugger while it is running or suspended.
    
• Using Functions Requiring the Low-Level Driver—The LabWindows/CVI low-level driver is not supported on Windows Vista x64 Edition. The following functions are affected: inp, inpd, inpw, MapPhysicalMemory, outp, outpd, outpw, ReadFromPhysicalMemory, ReadFromPhysicalMemoryEx, StartPCSound, StopPCSound, UnMapPhysicalMemory, WriteToPhysicalMemory, WriteToPhysicalMemoryEx.
• Registering ActiveX Servers—When you build ActiveX servers in LabWindows/CVI 8.1.1 and later on Windows Vista and XP, the ActiveX servers are registered in your user profile. This registration is not visible to other users on your system. On previous versions of Windows, 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.
• Registering LabWindows/CVI as an ActiveX Server—Installing LabWindows/CVI registers it for all users. Launching LabWindows/CVI registers LabWindows/CVI as an ActiveX server. LabWindows/CVI is registered in your user profile on all versions of Windows.
• 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.
• Creating and Deleting Network Variables and Processes—You may notice that about 50 bytes of memory are lost when you create and delete a network variable or process.
• Using the LabWindows/CVI Conversion Wizard in Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008—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.
• Using the NI Instrument I/O Assistant—The Instrument I/O Assistant 2.0 generates LabWindows/CVI code that is not backward compatible with code that previous versions of the Instrument I/O Assistant generated. If you run code generated with the Instrument I/O Assistant 2.0 with an existing application, the code in that application might not compile.
• 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.
• 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 2010, 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 2010 in LabWindows/CVI 8.1.1 or earlier.
  
  You can save .uir files you create or load in LabWindows/CVI 2010 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.
• Using Microsoft Excel as an ActiveX Control—If you develop an application that uses Excel as an ActiveX control on a LabWindows/CVI user interface panel, make sure that a separate instance of Excel is not running simultaneously. Otherwise, programmatic calls to the Excel control might not work as expected after the separate Excel application terminates.
• Navigating Toolkit Topics in the LabWindows/CVI Help—If you click a link from a topic in a toolkit section of the LabWindows/CVI Help or from the toolslib function panel help, you cannot use the Back button in the help viewer toolbar to return to the original topic.
• Using the Advanced Analysis Library—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.
• 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.
    
• Help File Font Size—Starting with LabWindows/CVI 2009, the LabWindows/CVI Help includes a Font button that you can use to increase or decrease the font size in the help file. The Font button might not update the font size in help files that merge into the LabWindows/CVI Help.
  
  In addition, the smallest font size setting of the Font button is the standard font size for National Instruments help files. The text size settings in Internet Explorer might cause the font to appear larger than typical National Instruments help files. If you resize the font, the help file retains the font size the next time you open the product help.
  

Bug Fixes

The following items are the IDs and titles of the bugs fixed between LabWindows/CVI 2010 and LabWindows/CVI 2010 SP1. For a list of bug fixes in previous releases, refer to ni.com.

Development Environment

ID	Fixed Issue	Has Run-Time Impact?
299976	LabWindows/CVI can corrupt files on some network shares when saving a file after deleting some of its contents.	No
299674	Pasting unicode data copied from the clipboard can cause a crash.	No
295529	Changing only the type of a custom configuration does not trigger a rebuild of your project.	No
295228	Add Watch Expression context menu item incorrectly dimmed in watch window.	No
294443	"Index out of range" error in Edit Columns/Cells dialog.	No
294960	Switching execution target and starting to debug project crashes LabWindows/CVI when a watchpoint exists.	No
293875	Debugging a project in an unnamed workspace results in duplicate save dialog boxes.	No
292892	The LabWindows/CVI Visual Studio wizards add the version-specific ProgramData include path incorrectly.	No
291368	Line numbers are missing from Standard I/O window.	Yes
290057	Copying a control from one panel to the other in the User Interface Editor can cause the Attribute Browser to display incorrectly.	No
289945	Selecting a .lib instead of a .dll from the Generate DLL Import Library file dialog box causes LabWindows/CVI to crash.	No
288104	Changing any environment option while in an untitled workspace results in an error.	No
283634	The LabWindows/CVI Visual Studio Conversion Wizard fails for some projects that reference National Instruments modular instruments drivers.	No
282844	LabWindows/CVI does not allow users to save files following an exception.	No
282612	Editing a menu associated with a panel on an unsaved UIR can cause LabWindows/CVI to crash.	No
279028	Enabling or disabling profiling does not trigger a rebuild of your project.	No
277640	The User Interface Browser may not update when Find UI Object is selected from a source file.	No
258506	The Attribute Browser Find text box might incorrectly filter attributes when double-clicking a control in the User Interface Browser.	No
258505	Selecting Create New File on a project folder results in an invalid file.	No

Performance

ID	Fixed Issue	Has Run-Time Impact?
285633	LabWindows/CVI might crash if you create a panel with a very long title.	No
302494	Memory leak when using ATTR_COPY_ORIGINAL_DATA=0 and getting a scaled bitmap of a graph control.	Yes
290737	InetSendMail can crash if the To: field exceeds 250 bytes.	Yes
283981	Performance of many TDMS functions deteriorates more quickly than expected as total group and channel counts become very large.	Yes
253304	TDMS Files with very high channel counts might be slow to open.	Yes

User Interface

ID	Fixed Issue	Has Run-Time Impact?
284842	The GetTableCellRangeVals and SetTableCellRangeVals functions do not work for string cell types in a 64-bit application.	Yes
294725	Adding or removing an item from a tree that is not in edit mode might, in rare circumstances, cause a crash.	Yes
286688	The menu text for a menu using a non-metafont rotates when a panel with Scale Contents on Resize enabled is resized.	Yes
282946	Right justified numeric controls can draw their text incorrectly.	No
281083	The y-axis name of a strip chart control might be drawn incorrectly when the y-axis autoscales.	Yes
281082	A strip chart legend may not be drawn correctly if it overlaps the strip chart plot area.	Yes
280705	You cannot enter numbers in scientific notation into numeric controls holding 64-bit integers.	Yes
280320	Table scroll bars do not redraw when scrolling a table with the keyboard.	Yes
279916	Scroll bar thumbs of table controls do not redraw when scrolling the table with the keyboard.	Yes
276443	A tab inserted anywhere but the end of the list will use the wrong image.	Yes
276442	Displaying a file select popup panel from a panel with a tab control might disrupt the panel z-plane order.	Yes
258827	Block and sweep strip chart modes do not scroll properly.	Yes
303247	Strip chart x-axis divisions do not maintain proper spacing during scrolling.	Yes
302870	UI Localizer can crash when clicking Next on the last item of a tree control.	No

Compiler

ID	Fixed Issue	Has Run-Time Impact?
257782	The Resource Tracking window does not track thread local variable handles.	No
298184	Non-Fatal UP errors can sometimes display with only the message %%s.	Yes
275934	Including the http.h Win32 API header file can result in missing function prototype compile errors.	No
295530	Watch points created for custom configurations might not work without modifications.	No
258835	Using clang 1.0 as your active release compiler might result in link errors if you include windows.h from more than one source file.	No

Stand-Alone Applications and Distributions

ID	Fixed Issue	Has Run-Time Impact?
292539	Opening a distribution that was created in LabWindows/CVI 7.1 and earlier can cause a crash during conversion.	No
292805	An application whose installer includes only the Network Variable Support sub-item might not run correctly in a minimally configured target computer.	Yes
292521	An application whose installer includes only the Network Variable Support sub-item might run slower than expected in a minimally configured target computer.	Yes
291813	Distributions with .inf files fail to install after checking module dependencies.	Yes
291452	An application whose installer includes only the Standard Run-Time sub-item might run with a Mesa.dll could not be found error in a minimally configured target computer.	Yes
290986	A 32-bit application whose installer includes only the ActiveX Container Support sub-item might not run correctly in a minimally configured target computer.	Yes
290386	Uninstalling LabWindows/CVI distributions from some non-English operating systems fails.	No
286606	In a multi-project workspace, when editing a distribution, the output files of a project might incorrectly refer to the output files of a different project.	No
278742	In a distribution, the path to the CHM help file for an ActiveX server file is incorrect.	No

.NET and ActiveX

ID	Fixed Issue	Has Run-Time Impact?
296663	DIAdem automation example reports ActiveX error.	Yes
296660	ActiveX Iedemo example does not work with newer versions of IE.	Yes
283042	A LabWindows/CVI ActiveX server can crash while shutting down if there are open client connections to the server.	Yes

Analysis

ID	Fixed Issue	Has Run-Time Impact?
248829	The function GaussHG returns NaN for X values less than 0.	Yes
280209	Calling IIRCascadeFiltering in a loop produces erroneous results.	Yes

Miscellaneous

ID	Fixed Issue	Has Run-Time Impact?
287394	HTML and XML files generated from source code contain an extra asterisk for output parameters in function prototype.	No
277253	Non-void pointer types in function prototypes have an extra asterisk in the LabWindows/CVI help.	No
258354	CNVProcessIsRunning may incorrectly report that the process is running if the program is run as a startup program.	Yes

Notice Regarding Microsoft Silverlight Installation and RedistributionInstalling Microsoft Silverlight

Some NI components require Microsoft Silverlight. If you do not have Silverlight installed on your computer, but you do have Internet access, you can download the installer from Microsoft at http://www.microsoft.com/silverlight/. If you do not have Internet access, you can install Silverlight from this NI distribution media.

Using Microsoft Silverlight

You may not use any H.264/MPEG-4 AVC and/or VC-1 technology or codecs included in or with Microsoft Silverlight software which may be provided by NI as Third Party Software, including for the purpose of encoding or decoding video in compliance with, or making use of, the H.264/AVC visual standard or the VC-1 video standard.

Redistribution of Microsoft Silverlight

If you create and distribute software applications that contain NI components that also use Microsoft Silverlight, you may be authorized to include Silverlight in installers or on physical media as long as you comply with certain requirements. Refer to the notice.txt file in the \_Legal Information\Microsoft Silverlight 4.0 directory or the NI standard End User License Agreement (EULA) located in the \Common\MDF\EULADepot\NIReleased directory for more information.

---

Copyright

© 1993–2011 National Instruments Corporation. All rights reserved.

For copyright notices, conditions, and disclaimers, including information regarding certain third-party components used in LabWindows/CVI, refer to the Copyright topic of the LabWindows/CVI Help.

Trademarks

CVI, LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.

The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.

Other product and company names mentioned herein are trademarks or trade names of their respective companies.

Patents

For patents covering the National Instruments products, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or ni.com/patents.