LabWindows/CVI 2009 Runtime Win32Eng LabWindows/CVI2009运行版下载
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 2009 Runtime Win32Eng LabWindows/CVI2009运行版下载
LabWindows/CVI是一个ANSI C软件开发环境，提供一套用于开发测试和测量应用程序的完整编程工具。
LabWindows/CVI ANSI C集成编程环境可帮助您创建自定义工程应用程序。该环境可用于管理项目、编辑和调试源代码和构建用户界面，并提供一个简化的选项卡式工作区来测试代码输出和性能。LabWindow/CVI提供了高级调试、代码文档描述和系统部署所需的工具，可帮助您集成源代码控制、需求和数据管理系统。该软件还可具有内置仪器I/O库、内置仪器驱动程序或两个交互式测量辅助工具，帮助您更轻松、快速地采集GPIB、USB、串行、以太网、PXI、VXI和FPGA仪器的数据。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。
自2009版LabWindows开始，NI仅提供完整版和运行版，不再提供基本版。
2009RT
文件大小: 125323298 字节 (119.52 MB)
修改日期: 2019-06-25 03:00
MD5: a4aa787bc26a9827eb61f9761c3f8e04
SHA1: 8fd29b136068fde6ed7735bcbb571b2db5511177
SHA256: 5b0cd37b2a35c7768476c6a9cb9bf03380adabee24a56cb008a9b90a120a97ef
CRC32: 4ec02d13
百度和NI官方下载地址：
LabWindows/CVI for Windows 7/Vista/XP/2000, Version 2009Readme FileThis file contains installation information, programming considerations, and changes that are too recent to be included in the LabWindows/CVI Help. Refer to the LabWindows/CVI Release Notes for more information about new features.ContentsMinimum System Requirements
Installing LabWindows/CVI
Activating LabWindows/CVI
After Installation
Updating to LabWindows/CVI 2009
Updating to LabWindows/CVI 9.0
Known Issues
Bug FixesMinimum System RequirementsTo run LabWindows/CVI 2009, you must have the following items:
[*]Personal computer using a Pentium 1GHz or higher microprocessor
[*]Microsoft operating systems:
[*]Windows 7 (32-bit and 64-bit)
[*]Windows Vista (32-bit and 64-bit)
[*]Windows XP (32-bit)
[*]Windows 2000 Service Pack 3 or later
NoteLabWindows/CVI 2009 is the last major release to support Windows 2000.[*]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
NoteInstalling the Documentation from MSDN Library requires additional disk space.
[*]Microsoft-compatible mouse
Installing LabWindows/CVINational Instruments recommends that you install the complete LabWindows/CVI program to take full advantage of all LabWindows/CVI 2009 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
[*]If you install the LabWindows/CVI Real-Time Module and device drivers with LabWindows/CVI 2009, you must install these products in the following order:
[*]LabWindows/CVI 2009
[*]LabWindows/CVI 2009 Real-Time Module
[*]Device driver software, using NI Device Drivers media
The LabWindows/CVI package includes the device driver software on a DVD. If you require device driver software on CDs, refer to the National Instruments Web site at ni.com/info and enter the info code drivercd.
If you are installing the LabWindows/CVI Real-Time Module, do not install the device driver software when you are prompted to do so during the LabWindows/CVI 2009 installation. Instead, install the device driver software when you are prompted during the LabWindows/CVI Real-Time Module installation.[*]When you install LabWindows/CVI, your user account must have administrator privileges.
[*]You must explicitly select the Interface to Win32 API feature of the LabWindows/CVI installer to install the complete Interface to Win32 API.
The Interface to Win32 API is based on the Windows Server 2003 R2 Platform SDK. The Windows Server 2003 R2 Platform SDK was released in March 2006 and does not include tools or functionality added in later versions of the SDK, such as support for functionality specific to Windows Vista.
NoteThe 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 2009 Run-Time Engine. This version replaces any previous version of the LabWindows/CVI Run-Time Engine. After you install LabWindows/CVI 2009, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2009 Run-Time Engine.
To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2009 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 InstallationThe 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
NoteThe LabWindows/CVI Platform DVD also includes the Documentation from MSDN Library.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 2009:NoteIf you already have a different version of LabWindows/CVI installed on your computer, be sure to install version 2009 in a different directory. If you want to install to an existing directory, uninstall the other version before installing LabWindows/CVI 2009.
[*]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 2009 screen appears. Click Install LabWindows/CVI, Modules, and Toolkits.
[*]In the Product List panel, select all the products you want to install. Select Install to install products using default options. Selecting Install with customization opens additional dialog boxes that require your input.
[*]In the Product Information panel, determine whether to allow the installer to contact National Instruments to search for new notifications, such as critical updates, on the products you are installing. The checkbox is enabled by default.
[*]In the User Information panel, enter your name and organization.
[*]Enter the serial number, from the Certificate of Ownership card in the software kit, in the appropriate field for each product you install. LabWindows/CVI uses this serial number when you run the NI Activation Wizard. Leave the Serial Number field blank to evaluate the product.
NoteTo activate a National Instruments product after you evaluate it, refer to the Activation Instructions.
[*]Continue to follow the instructions on the screen.
NoteIf you selected Device Drivers in the Product List, after installing LabWindows/CVI and any selected modules and toolkits, the LabWindows/CVI installer prompts you to insert the National Instruments Device Drivers DVD. Follow the instructions on the screen to install the device drivers.Activating LabWindows/CVIYou can activate licenses you have purchased for LabWindows/CVI, modules, and toolkits during installation. If you do not activate a valid license for LabWindows/CVI or any modules and toolkits that you install, the unlicensed product operates in evaluation mode. After you install the product, the evaluation begins the first time you launch the product and lasts 30 consecutive days. When the evaluation period expires, you must activate a valid license to continue using the product.You can activate LabWindows/CVI, module, or toolkit in the following ways:
[*]During installation, as described in the Installation Instructions.
[*]After installation, by enabling the Run License Manager to activate the product(s) checkbox on the Installation Summary panel of the LabWindows/CVI Platform DVD installer.
[*]After you launch LabWindows/CVI for the first time with any product in evaluation mode, click the Activate Products button in the LabWindows/CVI Message dialog box.
[*]Select Help»Activate LabWindows/CVI while LabWindows/CVI is running in evaluation mode or select Start»All Programs»National Instruments»NI License Manager to launch the NI License Manager.
If you do not activate LabWindows/CVI or any modules and toolkits during installation, LabWindows/CVI prompts you to activate when you launch LabWindows/CVI. After you activate the licenses for all LabWindows/CVI products you installed, you no longer see this prompt. Once you choose your activation method and launch the NI Activation Wizard, complete the following steps to activate LabWindows/CVI and any modules or toolkits:
[*]Select the Automatically activate through a secure Internet connection option and click Next.
Your computer must be connected to the Internet for this option to work.
[*]Enter the serial numbers for the products you want to activate. Click Next.
[*]Fill in the necessary information and click Next.
[*]Check the option and enter an email address if you would like to receive a confirmation email of your activation and click Next.
[*]After a brief moment, a message appears, indicating whether LabWindows/CVI has been activated. Click Next.
[*]Continue to follow the instructions on the screen.
[*]When you successfully activate LabWindows/CVI and any modules or toolkits, click Finish. LabWindows/CVI displays a window indicating when your license expires.
For more information about activation, refer to the LabWindows/CVI Release Notes.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 2009 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: \Users\Public\Documents\National Instruments\CVI2009\samples. On Windows 2000/XP, example programs are located in the following location: \Documents and Settings\All Users\Documents\National Instruments\CVI2009\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/2000 and \Users\Public\Documents\National Instruments\CVI on Windows 7/Vista). LabWindows/CVI 8.5 and later does not search previous locations, \Documents and Settings\All Users\Application Data\CVI and \Documents and Settings\<User ID>\Application Data\CVI, for project and file templates.
Updating to LabWindows/CVI 2009
[*]Borland is no longer supported as a compatible compiler or as a third-party compiler in LabWindows/CVI.
[*]Starting with this 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 2009. You can find installed files in the CVI2009 folder in the various locations where LabWindows/CVI installs files. The registry keys corresponding to this version of LabWindows/CVI are located in CVI\9.1 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.
Updating to LabWindows/CVI 9.0
[*]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:
LibraryPrevious Macro NameNew Macro Name
WordReport.fp Instrument DriverNONEWR_NONE
Analysis LibrarySORT_ASCENDINGANALYSIS_SORT_ASCENDING
Analysis LibrarySORT_DESCENDINGANALYSIS_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
[*]Microsoft Windows 7 Support—National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. While most NI products work with Windows 7, NI has become aware of some compatibility issues regarding Windows 7. To learn more about Windows 7 and NI products, visit ni.com/info and enter the Info Code windows7.
[*]User Interface Controls in 64-bit Mode—Some drawing artifacts (black dots) can appear in the top-left parts of some user interface controls when running in 64-bit mode.
[*]Linking Import Libraries for .NET—LabWindows/CVI cannot link in the import library for a .NET mixed mode DLL.
[*]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.
[*]Resizing Slide Controls—Numeric markers do not always adjust correctly to the resizing of a slide control.
[*]Setting Inc/Dec Arrow Width—ATTR_INCDEC_WIDTH has no effect if the inc/dec arrows are not visible.
[*]Using Perforce with LabWindows/CVI—LabWindows/CVI crashes when using the Perforce 2009.1 source code control plug-in.
[*]Specifying ATTR_MOVABLE Attribute—ATTR_MOVABLE does not work in Windows 7 with Aero enabled.
[*]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 2009 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 2009 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.
[*]Editing Controls Using the Attribute Browser—The control you are currently editing loses focus as you update values in the Property Browser.
[*]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.
[*]Using Compressed Icons—To use an icon featuring PNG compression, you must replace the resource compiler shipped with LabWindows/CVI with the one included in the Windows SDK released with Windows Vista. Install the SDK and copy the rc.exe and rcdll.dll files from C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin to CVIversion\sdk\bin.
[*]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.
[*]Setting the Compatibility Mode for Real-Time DLLs—When you create a DLL to run on a real-time target, you must use the Visual C/C++ compatibility mode. The Borland C/C++ compatibility mode is not supported for real-time DLLs.
[*]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 KnowlegeBase article for more information.
[*]Updating an Existing Distribution—The LabWindows/CVI distribution creation feature does not provide the option to include .obj files for both compatible compilers. If you convert an existing distribution that has this option enabled, LabWindows/CVI includes the .obj files only for the current compatible compiler in the updated distribution.
[*]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 2009, 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 2009 in LabWindows/CVI 8.1.1 or earlier.
You can save .uir files you create or load in LabWindows/CVI 2009 in the following formats:
[*]LabWindows/CVI 7.1
[*]LabWindows/CVI 8.0-8.1
[*]LabWindows/CVI 8.5-9.0
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 7.1 or 8.0-8.1 format.[*]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 the Tools Library and Toolkit Topics in the LabWindows/CVI Help—If you click a link from a topic in the Tools Library or 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 FixesThe following items are the IDs and titles of the bugs fixed between LabWindows/CVI 9.0.1 and LabWindows/CVI 2009. For a list of bug fixes in previous releases, refer to ni.com.User Interface
IDFixed IssueHas Run-Time Impact?
190831ATTR_NO_EDIT_TEXT does not prevent tab spaces from being entered into a text box controlYes
189400Loading a very wide .bmp or .pcx file can fail with an Out of Memory errorYes
189247Drag and drop operation on the title bar or window frame does not workYes
184792String control sends EVENT_VAL_CHANGED with <Ctrl+F>No
183301Splitter controls with no range limit do not draw shadow when operatedYes
182743Editing a panel that has a control with a label of exactly 50 characters can cause a crashNo
177284Table and tree scroll bars are not always clipped to a child panel's boundsYes
101593Strip chart scroll bar overlaps the plot areaYes
101591Phantom arrow buttons can appear when a strip chart is scrolledYes
173952Truncating tree item strings can cause user applications to crash under some circumstancesYes
175118Minor gridlines of graphs and minor ticks of numeric slides can disappearYes
139151Debugger does not always catch incorrect use of ATTR_COPY_ORIGINAL_DATAYes
134165Menu bar does not resize when using Scale Contents On Resize or Resolution AdjustmentYes
134049User Interface Editor does not retain the awareness that it should save the .uir in an older formatNo
133845Table row labels cannot be sized when the column labels are not visible, and vice-versaYes
139269Hidden tab panels of a nested tab control can be made activeYes
60017LabWindows/CVI loses some color customizations when color depth changesNo
147609Setting ATTR_COLOR_RAMP_WIDTH can leave the control apparently unchangedYes
149350The cursor position of a text box can be incorrect when typing Thai charactersYes
177493Plotting to a hidden strip chart can cause the application to hangYes
152088ATTR_XMARK_ORIGIN and ATTR_YMARK_ORIGIN can change the wrong axisYes
191757ActiveX controls might not appear if a panel is displayed in a thread other than the thread that created the panelYes
Development Environment
IDFixed IssueHas Run-Time Impact?
194053There can be multiple prompts to check out a project file from source code controlNo
185942Cannot add empty function panel file to a projectNo
156166Cut Line does not work correctly with a collapsed block of codeNo
127036Repeated save prompts can be shown if a project file path is made invalidNo
167925LabWindows/CVI can crash when browsing the set of values for an attributeNo
172750UI Localizer preview does not work correctly with non-native character setsNo
136293LabWindows/CVI can crash after removing from the workspace a project that uses an external release compilerNo
136341LabWindows/CVI Welcome Page cannot be minimizedNo
130204Multi-file search does not ignore invalid paths, even when searching only a specific set of filesNo
126050tmpdir registry value is not used when backing up filesNo
154794Web links in Help menu do not work when .html files are not associated with a Web browserNo
135900LabWindows/CVI Workspace window title bar does not show Aero transparencyNo
166027Cannot launch Icon Editor from Tools menuNo
137735Browse window does not retain all its settings when a file is recompiledNo
157568Go to Next Reference does not cycle through all references of a variable or a function in other filesNo
156975User Interface Editor asks to assign constant names when backing up filesNo
162197Help tooltip for the Run button in the toolbar is incorrect after running the Interactive Execution windowNo
Compiler
IDFixed IssueHas Run-Time Impact?
179613_declspec in function pointer typedef causes compile error.No
160327LabWindows/CVI can crash when compiling designated initializers for array of structs/unionsNo
132689LabWindows/CVI Show Completions does not work for nested struct array fieldsNo
145895struct auto completion does not handle arrays of structs inside other structs correctlyNo
129546Cannot use the Utility or Formatting and I/O Libraries and some Interface to Win32 API functions at the same timeNo
131351Some Interface to Win32 API header files that use EXTERN_C can cause compile errorsNo
157216Batch building with auto-increment leaves version numbers for debug and release builds offset by oneNo
168621Using an object file built with precompiled headers can lead to link errorsNo
177794LabWindows/CVI can crash when compiling a complex mathematical computation that is not assigned to a variableNo
130056Compiler does not define NDEBUG in release configurationNo
127909Instrument drivers are marked for compilation with each configuration switchNo
158055Cannot include windows.h in the Interactive Execution windowNo
186965Command line compiler crashes when building project with Add type library resource to DLL optionNo
Debugging
IDFixed IssueHas Run-Time Impact?
193526Adding a watch expression that already exists fails silentlyNo
184979Breakpoint pass counts are off by oneNo
127318Calling some inifile.fp functions while the Programmer's Toolbox is compiled from source code can result in a false report of leaked resourcesNo
179034Obtaining a non-existant attribute with CVIXMLGetAttributeByName results in a false report of leaked resourcesNo
162554Some source code constructs can cause incorrect Local was referenced before being initialized runtime errorsYes
155604Adding a watch expression that references a variable declared in block scope can hang the program when it is debuggedNo
139139Viewing memory as HEX longs (64 bit) in the Memory Display causes all values to turn redNo
177188LabWindows/CVI debugger can crash when using memcpy to copy data from a const struct arrayNo
189661Variables window does not always show variable declared in for-loop scopeNo
Performance
IDFixed IssueHas Run-Time Impact?
184428LabWindows/CVI can crash when calling the Delay function from multiple threadsYes
175150LabWindows/CVI can crash when opening a .c file containing lines with approximately 1020 charactersNo
167239LabWindows/CVI can hang while editing a large non-source-code data fileNo
157141Memory leak in the thread-safe queueYes
Stand-Alone Applications and Distributions
IDFixed IssueHas Run-Time Impact?
192040LabWindows/CVI can crash after changing a registry key name in the Edit Distribution dialog boxNo
179863Error dialog boxes can appear when editing a distribution before and after discarding a User Interface Editor windowNo
177971Creating an installer spec file fails if a Visual Studio 2008 wizard is explicitly includedNo
148892The Files tab of the Edit Distribution dialog box is too smallNo
141648Auto-incrementing the distribution is marking the project for recompilationNo
182036CreateUDPChannelConfig fails if ws2_32.dll is installed to the application directoryYes
165495Installing an application that uses ActiveX controls to a clean machine might result in a runtime errorYes
165285Subdirectories of application directory are all lowercase in an installed distributionNo
141444Creating a distribution for a DLL that installs the support files to the application directory might fail if the DLL is loaded from a different folderNo
130286Cannot install TDMS support or RT Utility support to application directoryNo
130423.NET library cannot be included in a distribution without also including the full run-time engineYes
.NET and ActiveX
IDFixed IssueHas Run-Time Impact?
174102Hidden LabWindows/CVI ActiveX Automation interface is visible in function panel treeNo
168302Cannot create a numeric floating-point function panel control via ActiveX AutomationNo
39122Intrusive registration message when building ActiveX server projectNo
Analysis
IDFixed IssueHas Run-Time Impact?
183434NonLinearFitWithMaxIters function does not return best fit array when max interations is exceededYes
156791Several Analysis Library function panels incorrectly relying on AnalysisLibPowerOfTwo enumNo
140249NonLinearFitWithMaxIters does not return an error when maximum iterations is 1Yes
140913ThresholdPeakDetector has unexpected results when width > 1Yes
Miscellaneous
IDFixed IssueHas Run-Time Impact?
191778The application crashes when passing NULL data length to RegEnumerateValueYes
178655GetDrive returns an incorrect total number of drives if there are non-contiguous drives presentYes
173689LoadLocalizedPanel fails for trees with more than 7 column translationsYes
162814Cannot embed type library in DLL when function panel has a custom type based on a character arrayNo
162398Toolbox lists can grow by amounts greater than the allocation policy specifiesYes
142035LabWindows/CVI ibdev function returns positive value if GPIB driver is not installedYes
139658GetFileSize can crash if you pass in a path that is too longYes
129812Calling a LabVIEW-built DLL causes printf to format a double to a string incorrectlyYes
129094Asynchronous timer limited to intervals no greater than approximately 429 secondsYes
128060Visual Studio cannot find Interface to Win32 API libraries in LabWindows/CVI projects converted to Visual Studio using the project wizardNo
60948A file path sometimes appears in printed Microsoft Word reportsYes
Copyright© 1993–2009 National Instruments Corporation. All rights reserved.Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.TrademarksCVI, National Instruments, NI, ni.com, LabVIEW, and NI TestStand are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about 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.
页:
[1]