LabWindows/CVI 2010 Full Win32Eng LabWindows/CVI2010完整版下载

石鑫华视觉

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 Full Win32Eng LabWindows/CVI2010完整版下载

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

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

2010，提供了EXE和ZIP两个版本：
zip
文件大小: 409038139 字节 (390.09 MB)
修改日期: 2019-06-25 02:59
MD5: d2590c9afa2439a3596b1a7df7a9cf1d（官方正确）
SHA1: f06371ba710cddbf97d53e34191e770bb9dbc74e
SHA256: 35d0cbe2d1198c64c9f887ad1eb0cb89c36228e98f5c1f0c38817915a8ddd5d1
CRC32: febb730d

exe
文件大小: 407804512 字节 (388.91 MB)
修改日期: 2010-11-09 08:01
MD5: 5ee08e174e48fc89a1f1b8b2c563f6f5
SHA1: e8b6fd519a647fd5f8e8cf3a9480442e2b637017
SHA256: 2ba0141c495037fcadbd978484436244ae91421ee925f2cd89d1ab602e7b9a7e
CRC32: de70b85b

百度和NI官方下载地址：
CVI2010.txt (1.04 KB, 下载次数: 0, 售价: 15 元)

2020-12-9 23:25 上传

点击文件名下载附件

LabWindows/CVI for Windows, Version 2010Readme 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. Refer to the LabWindows/CVI Release Notes for more information about new features.

Note  Installing LabWindows/CVI 2010 replaces any previous version of the LabWindows/CVI Run-Time Engine with the LabWindows/CVI 2010 Run-Time Engine. To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2010 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 2009
Upgrading from LabWindows/CVI 9.0
Upgrading from LabWindows/CVI 8.5 or earlier
Known Issues
Bug Fixes

Minimum System Requirements

To run LabWindows/CVI 2010, 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 (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 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 Run-Time Engine. This version replaces any previous version of the LabWindows/CVI Run-Time Engine. After you install LabWindows/CVI 2010, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2010 Run-Time Engine.
  
  To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2010 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.
• Some National Instruments components require Microsoft Silverlight 4.0. If you use a component that requires Silverlight, a dialog box prompts you to install Silverlight from the Internet. Microsoft Silverlight 4.0 is available from the Microsoft Web site at http://www.microsoft.com/silverlight.
  

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 in a different directory. If you want to install to an existing directory, uninstall the other version before installing LabWindows/CVI 2010. 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 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 2009

• 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

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

• 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 2009 SP1 and LabWindows/CVI 2010. For a list of bug fixes in previous releases, refer to ni.com.

Development Environment

ID	Fixed Issue	Has Run-Time Impact?
242690	"A custom control callback..." exception dialog box displays when removing a distribution from the Manage Distributions dialog box.	No
240876	Pressing spacebar in the Edit Menu Bar dialog box can result in an internal error.	No
252825	Variables window can flicker with some types of applications.	No
127953	Closing a workspace may not remove all the files associated with a workspace.	No
222105	Using XCOPY in a build step to copy a file over an existing file can break subsequent builds.	No
239694	Viewing a ViSession variable with extended displays enabled can cause LabWindows/CVI to crash.	No
240603	LabWindows/CVI copies 64-bit DLLs to the SysWOW64 folder after compilation.	No
239396	LabWindows/CVI may close unexpectedly when launching.	No
237878	Deleting a key from the tree in the Registry Keys tab of the Edit Installer dialog box doesn't update the table on the right.	No
237395	Dragging a file from the Open File dialog box to the LabWindows/CVI Project Tree can cause LabWindows/CVI to crash.	No
236151	Creating a new project from a template from the Welcome Page can crash LabWindows/CVI.	No
218979	If the Auto hide Project Tree and Library Tree environment option is enabled, clicking the User Interface Editor will not hide the Project Tree.	No
214519	Changing the default cell value settings for a table column overwrites the default settings of other columns.	No
207820	Modifying a menu bar font can hide elements of the Edit Menu Bar dialog box.	No
211865	Edit»Insert Construct»Function Documentation Tags may crash LabWindows/CVI under some circumstances.	No
211495	LabWindows/CVI function panel help is missing stylesheets and images in multibyte operating systems.	No
205243	Memory leaks will not be displayed in the Resource Tracking window if CNVFinish is not called in network variable applications on Windows 7.	No
206858	Changes made through the Attribute Browser cannot be saved while the Attribute Browser has focus.	No
170375	Batch Build dialog box does not offer 64-bit configurations.	No
190179	LabWindows/CVI can crash after evaluating a watchpoint that runs for a very long time.	No
203164	The Auto-center vertically and Auto-center horizontally panel options are missing from the Attribute Browser.	No
202713	Stale selection boxes can be left in the User Interface Editor after making changes with the Attribute Browser.	No
197984	Source code comment tags for static functions are not exported to .xml or .html files when generating help from source.	No
198012	Dragging binary files, such as a static library, between projects may result in an exception.	No
200395	Example link buttons in the LabWindows/CVI Help do not work on 64-bit operating systems.	No
201055	Type library generation may fail if FP control names contain ODL keywords.	No
202313	The Attribute Browser allows invalid panel constant names.	No
256525	Program can crash in 64-bit after suspending and then editing a watchpoint that updates continuously.	No
256485	Releasing Variables and Watch windows results in the smallest possible window.	No
256194	Viewing a very large comment block can result in a crash.	No
251687	LabWindows/CVI crashes when browsing for RT targets and ethernet to GPIB controller is found.	No
256578	LabWindows/CVI can crash while debugging a 64-bit program, with extended variable displays enabled.	No

Performance

ID	Fixed Issue	Has Run-Time Impact?
251440	RS-232 Library can crash when flushing output queue while another thread is writing.	Yes
241552	LabWindows/CVI does not support offline files in Windows Vista and Windows 7.	Yes
238953	The GenericList .NET example program does not dispose the mscorlib library.	No
217094	EVENT_MOUSE_POINTER_MOVE can nest until the stack overflows if ProcessSystemEvents is called from the event callback.	Yes
215744	Calling CNVData functions in network variable callbacks can cause hangs.	Yes
207856	If errors are encountered when generating an FP from a header file, LabWindows/CVI may get into a bad state.	No
171624	CPU usage can spike when using ComRdTerm.	Yes
195469	Using the Intel C++ 11.1 compiler as a release compiler and optimizing for speed can cause crashes in user applications.	Yes
197427	NIReport_GetPrinters has a small memory leak.	Yes

User Interface

ID	Fixed Issue	Has Run-Time Impact?
253193	DuplicatePanel can fail if active control is dimmed.	Yes
250654	Strip chart prints unscrolled	Yes
248368	When table row/column labels are hidden, they can still be clicked on, making them reappear temporarily.	Yes
247402	File dialog cannot filter to an exact file extension.	Yes
240139	Menu bars may not resize correctly on panels with the Scale Contents On Resize option enabled.	Yes
237405	The event EVENT_LEFT_CLICK_UP can be sent to a panel behind a modal dialog box.	Yes
238634	ActiveX controls aren't dimmed when ATTR_DIMMED is set to True.	Yes
238038	Copying Japanese characters into text box control on Japanese OS doesn't work with native character set	Yes
147737	Numeric markers do not always adjust correctly to the resizing of a slide control.	Yes
226289	Batch drawing does not work for a canvas with a transparent background.	Yes
225134	Bitmaps obtained with the GetCtrlDisplayBitmap function cannot be used as menu images.	Yes
220236	The type returned from the function GetMonitorAttribute for the attribute ATTR_SYSTEM_MONITOR_HANDLE should be intptr_t and not int.	No
215429	Tab control panels do not generate size or move events when tab controls are sized or moved by a splitter.	Yes
151308	Passing "." or ".." to the DefaultFileSpec parameter of FileSelectPopup causes a legacy file dialog box to be shown.	Yes
154911	Setting ATTR_INCDEC_WIDTH on numeric controls has no effect if the inc/dec arrows are not visible.	Yes
194970	Using string controls with right or center justification causes the cursor to appear in the wrong position when there are trailing spaces.	Yes
194174	Bitmaps with alpha channels, such as .PNG images, do not print correctly.	Yes
193639	The panel attribute ATTR_MOVABLE does not work when Aero is enabled.	Yes
256142	Copying collapsed tree items with images in the User Interface Editor can result in a crash.	No
256056	Deleting or editing a menu from the User Interface Browser in the User Interface Editor doesn't mark the file as modified.	No
255934	Controls in LabWindows/CVI might not scale properly when panel is scaled to a different aspect ratio.	Yes
255807	A text box with non-default ATTR_EXTRA_LINES may cause an error when the panel is scaled.	Yes
256628	In some cases, a ring control can display a menu that doesn't completely fit on the screen.	Yes

Compiler

ID	Fixed Issue	Has Run-Time Impact?
247337	Watchpoints report incorrect values for some anonymous unions.	No
232258	You cannot use word "defined" in a macro definition.	No
232196	LabWindows/CVI does not consider "$" to be a valid character in a symbol identifier.	No
232194	LabWindows/CVI ignores invalid symbols in macro names.	No
237630	Debugger may invalidate stored return values of gmtime and asctime.	No
229071	While suspended at a breakpoint, running a function panel or the Interactive Execution window or executing the Refresh User Interface command prevents future breakpoints from being hit.	No
217295	AppendString might work incorrectly when debugging a LabWindows/CVI program.	Yes
250204	Command line compiler attempts to link the project after compilation errors when using a third-party compiler.	No
243809	Erroneous "Unexpected trailing tokens on directive line ignored" warning.	No
203337	The DirectShow API in the full Interface to the Win32 SDK is unusable.	No
240722	Including strsafe.h causes compilation errors.	No
237175	Some LabWindows/CVI examples generate warnings when built with compile.exe in the 64-bit release configuration.	No
204719	Wrappers generated for the Microsoft.JScript .NET assembly will not compile.	No
203051	Some constant array size expressions may be incorrectly reported as variable-length in C99 mode.	No
232139	LabWindows/CVI can recompile a source file if the timestamp of a .obj file changes, but there has been no change to the corresponding source file.	No

Stand-Alone Applications and Distributions

ID	Fixed Issue	Has Run-Time Impact?
216375	64-bit debug applications are signed even if the Sign debug build option is disabled in the Target Settings dialog box.	No
150213	Absolute drive letters cannot be specified as the base install location for LabWindows/CVI distributions.	No
250518	cvintdrv.sys causes a security warning in Event Viewer on Windows 7 32-bit.	No

.NET and ActiveX

ID	Fixed Issue	Has Run-Time Impact?
217093	LabWindows/CVI .NET components do not get installed if .NET 2.0 is installed.	No
215062	The LabWindows/CVI .NET Controller dialog box does not recognize default parameters for assemblies created with C++.	No
169037	Linking against mixed-mode .NET DLLs may cause LabWindows/CVI applications to crash.	Yes

Analysis

ID	Fixed Issue	Has Run-Time Impact?
231459	Analysis library might not be functional after uninstalling DIAdem.	Yes

Miscellaneous

ID	Fixed Issue	Has Run-Time Impact?
252846	GetModuleDir cannot be called in a 64-bit application.	No
251801	CVI GUI Localization Utility duplicates items in the dictionary when exporting translations to existing dictionary.	No
246218	numElements parameter of the DefineThreadSafeArrayVar macro is not expression-tolerant.	Yes
119213	Exception can occur when inserting an image into a report created with WordReport.fp.	Yes
233510	Ini_GetInt64 doesn't return –5021 (Invalid integer) for numbers greater than LLONG_MAX.	Yes
202380	PasswordCtrl_ConvertFromString does not return an error if a non-string control is passed as the control to convert.	Yes
192713	TDMS_ConvertFileFormat may fail intermittently.	Yes
227697	Writing TDMS data and setting TDMS properties in a specific sequence can cause TDMS data corruption.	Yes
215992	LabWindows/CVI DLLs that link against the Programmer's Toolbox export the function _crt_debugger_hook.	No
202274	The LabWindows/CVI debug deployment license will not activate previous versions of LabWindows/CVI.	No

---

Copyright

© 1993–2010 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.