LabWindows/CVI 8.5 Base Win32Eng LabWindows/CVI8.5基本版下载
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 8.5 Base Win32Eng LabWindows/CVI8.5基本版下载
LabWindows/CVI是一个ANSI C软件开发环境，提供一套用于开发测试和测量应用程序的完整编程工具。
LabWindows/CVI ANSI C集成编程环境可帮助您创建自定义工程应用程序。该环境可用于管理项目、编辑和调试源代码和构建用户界面，并提供一个简化的选项卡式工作区来测试代码输出和性能。LabWindow/CVI提供了高级调试、代码文档描述和系统部署所需的工具，可帮助您集成源代码控制、需求和数据管理系统。该软件还可具有内置仪器I/O库、内置仪器驱动程序或两个交互式测量辅助工具，帮助您更轻松、快速地采集GPIB、USB、串行、以太网、PXI、VXI和FPGA仪器的数据。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。
8.5基本版
文件大小: 198307328 字节 (189.12 MB)
修改日期: 2007-12-17 23:35
MD5: a50f694b6478fcf762bcb375351036d3
SHA1: 5d615c99573d6d7000ef9628949d3c03e33dfb26
SHA256: 78fc065b0fd1ebc135fce99e1416eff76bab3ed4031d1bbba8f7072005437efd
CRC32: 3df8971f
百度和NI官方下载地址：
LabWindows/CVI for Windows Vista/XP/2000, Version 8.5Readme 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
Known Issues
Bug FixesMinimum System RequirementsTo run LabWindows/CVI 8.5, you must have the following items:
[*]Personal computer using a Pentium 1GHz or higher microprocessor
[*]Windows Vista/XP/2000 Service Pack 3 or later
[*]1024 × 768 resolution (or higher) video adapter
[*]Minimum of 128 MB of RAM, 512 MB recommended
[*]200 MB free hard disk space
[*]Microsoft-compatible mouse
Installing LabWindows/CVINational Instruments recommends that you install the complete LabWindows/CVI 8.5 program to take full advantage of all LabWindows/CVI 8.5 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 8.5, you must install these products in the following order:
[*]LabWindows/CVI 8.5
[*]LabWindows/CVI Real-Time Module
[*]Device driver software from the NI Device Drivers CD set
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 8.5 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 Win32 SDK feature of the LabWindows/CVI installer to install the complete Windows SDK from the LabWindows/CVI Full Development System (FDS). Some Windows SDK header and import library files are included when you install the LabWindows/CVI Base Package. The Windows SDK help file is available only with the LabWindows/CVI FDS.
[*]The LabWindows/CVI installation includes the LabWindows/CVI 8.5 Run-Time Engine. This version overwrites previous versions of the run-time engine. After you install LabWindows/CVI 8.5, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 8.5 Run-Time Engine.
[*]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.
Running the InstallationComplete the following steps to install LabWindows/CVI 8.5:NoteIf you already have a different version of LabWindows/CVI installed on your computer, be sure to install version 8.5 in a different directory or uninstall the other version before installing LabWindows/CVI 8.5.
[*]Insert the LabWindows/CVI CD into the CD drive. If the CD does not run automatically, open Windows Explorer, right-click the CD drive icon, and select AutoPlay.
[*]On installation startup, the National Instruments LabWindows/CVI 8.5 screen appears. Click Install LabWindows/CVI.
[*]In the User Information panel, enter your name and organization. Select one of the following options:
[*]Install this product using the following serial number
[*]Install this product for evaluation
If you choose to enter a serial number, enter the serial number found on your Certificate of Ownership card. LabWindows/CVI uses this serial number when you run the NI Activation Wizard.[*]Continue to follow the instructions on the screen.
Activating LabWindows/CVIComplete the following steps to activate LabWindows/CVI 8.5.
[*]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. If you do not have Internet access on your computer, refer to the LabWindows/CVI Release Notes.
[*]The Serial Number option is populated with the number you entered during installation. Click Next.
[*]Fill in the necessary information and click Next.
[*]Check the option if you would like to receive a confirmation email of your activation and click Next.
[*]After a brief moment, you should receive a message indicating whether LabWindows/CVI has been activated or not. Enter or verify your serial number. Click Next.
[*]Continue to follow the instructions on the screen.
[*]When you successfully activate LabWindows/CVI, click Finish. LabWindows/CVI will then display a window indicating when this license will expire.
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 a previous version of LabWindows/CVI and you install LabWindows/CVI 8.5 in a new directory, you must uninstall and reinstall the LabWindows/CVI portion of the driver or toolkit software.
[*]New Example Program Location—You can find example programs in the following location on Windows Vista: C:\Users\Public\Documents\National Instruments\CVI85\samples. On Windows 2000/XP, example programs are located in the following location: C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples. You can find a link to these locations from the previously used location (C:\Program Files\National Instruments\CVI85\samples).
Known Issues
[*]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.
[*]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.
[*]Using Compressed Icons—To use a Windows Vista compliant icon (featuring very large icons or 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 CVI85\sdk\bin.
[*]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 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 Visual Studio .NET 2005—Microsoft Visual Studio 2005 removed support for the single-threaded version of its 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.
[*]Running the LabWindows/CVI Project and Conversion Wizards in Visual Studio .NET 2003—If you use the LabWindows/CVI Project and Conversion Wizards in Visual Studio .NET 2003 and try to build a project that was created by one of these wizards, you will receive linker errors. With LabWindows/CVI 8.5 and later, the LabWindows/CVI libraries can be installed to various locations. The LabWindows/CVI wizards are not aware of these changes and therefore cannot find the needed libraries. These linker errors will only occur if you are using the LabWindows/CVI wizards in Visual Studio .NET 2003. Refer to National Instruments KnowledgeBase Article 4BIHC800 for steps to work around this issue.
[*]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—If you have been using LabWindows/CVI 8.1.1 or earlier, make backup copies of your .uir files. Once you save .uir files in LabWindows/CVI 8.5, 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 8.5 in LabWindows/CVI 8.1.1 or earlier.
You can save .uir files you create or load in LabWindows/CVI 8.5 in LabWindows/CVI 7.1 or LabWindows/CVI 8.0/8.1 format. Select File»Save .uir As and specify the version 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 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. 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.
Bug FixesThe following items are the IDs and titles of the bugs fixed between LabWindows/CVI 8.1.1 and LabWindows/CVI 8.5. For a list of bug fixes in previous releases, refer to ni.com.User Interface
IDFixed IssueHas Run-Time Impact?
431CB7OFPlotPackedDigitalLines does not display data if ATTR_DIGWAVEFORM_SHOW_STATE_LABEL is re-enabled before calling SetAxisScalingModeYes
43LAC80SPlotIntensity does not interpolate colors in a deterministic fashion when plotting integer dataYes
46D9Q734Installing a child panel as a popup changes its appearance after uninstalling the popupYes
46BGGNABUndo fails with Panel, pop-up, or menu bar hande is invalid error after repeatedly copying and pasting a panel in User Interface EditorNo
46FFIDNMTwo consecutive underscore characters become a single underline in a ring control menuYes
47KC3F03ATTR_SIZE_TO_TEXT is not automatically disabled when a text message is sized with a splitter controlYes
4669HV34Canvas sometimes scales its contents incorrectly then the Scale Contents On Resize option is enabledYes
47SDHEZWCell edits are lost when the value of another cell changes programmaticallyYes
482EKLZWEdit Table Control dialog box does not always update correctly when coercing cell valuesNo
485DMN03The Windows XP-style menu arrows and scroll bars can stop drawing if a table control has several thousand cellsYes
493HLPZWThe user interface of a LabWindows/CVI application becomes unresponsive after running for 49.7 daysYes
49UCRKIODataSocket binding of user interface controls cannot be enabled or disabled after the panel is loadedYes
4A5817OFControl tooltips appear on the primary monitor, even though the panel is displayed on the second monitorYes
4ALBTK3QThe menu item ID parameter of a control menu item callback function is incorrectYes
4AOCPUZWThe User Interface Editor does not allow a listbox control to be converted into a treeNo
4AQIK8ZWThe Find UI Object command can crash LabWindows/CVI if the corresponding .uir file has several nested menus, each containing long menu item constant namesNo
4B28DHOFPerforming an undo after changing the control coordinates of a control on a tab control causes an unrecoverable internal errorNo
4C8AACZWEvents sent to the graph control callback that result from moving annotations do not include event dataYes
4C8EJJZWIn a graph control that contains both cursors and annotations, moving an annotation fails to restore the active cursorYes
4CDAAJZWMinimized panels are drawn on the desktopYes
4CMAO600Hovering over toolbar images display incorrect shadowing when TOOLBAR_ATTR_BUTTON_IMAGE_SIZE attribute is usedYes
4CMACC00When changing the font of a menu bar using SetMenuBarAttribute, underlined accelerators are drawn in the wrong locationYes
4D4ATV0SSetting the tab order of a panel that contains a tab control without any tab pages causes a crashNo
4DBGFQZWAn application can crash when the mouse hovers over a specific location within the top-left corner of a table control if row or column sizing is disabledYes
4DCGDPIQThe presence of both cursors and annotations in a graph control cause the position of one or more annotations to be incorrect when the panel is loadedYes
4DDDKJ9PChanging the data type of any numeric slide in the User Interface Editor causes the maximum and minimum values to be resetNo
4DJEIH34Installing the panel that corresponds to a tab control page as a popup causes a general protection faultYes
Development Environment
IDFixed IssueHas Run-Time Impact?
43QAL8ZWLoadPanel returns an error with projects built in an external compiler if the .uir file specifies multiple callbacks that differ by case only or if a control inside a tab control specifies a callbackNo
466BE3IQThe Microsoft Vista Aero Glass features disappear from the window borders after the LabWindows/CVI environment is minimizedNo
4ACATO34The Microsoft Vista Aero Glass features can cause LabWindows/CVI fonts to appear distorted in 120-dpi modeNo
4D69FAVQThe Close All command does not consistently close all types of windows in the workspaceNo
489AR8ZWIf released, the Build Output window moves to the primary monitor whenever a build error occursNo
4B1ENO34Change Shortcut Keys dialog box does not always show all available shortcut keys when assigning a new keyNo
4B9AJN9PWhen printing source code using a proportional font, the inter-character spacing can vary within the fileNo
485A8D3QCannot use a custom stylesheet for the HTML documentation of a function panelNo
4BABJE03Output from the post-build actions appears before the pre-build actions output in the Build Output windowNo
4BP9SIZWThe Function Panel Editor snaps controls to the panel grid lines when performing an undo actionNo
4C2GO0ZWLabWindows/CVI does not use the instrument directory list to find missing instrument drivers when loading a projectNo
4CRCHNZWPressing <Ctrl-Tab> in the Function Panel Editor does not work if the .fp file has the read-only option setNo
4D3A3EZWDeleting the last recorded source code macro in the Manage Macros dialog box can sometimes also delete other macrosNo
4DD8HLOZThe Source Code Browser can display an error if the files are added to the project without rebuilding the projectNo
4CQFHJ9PGenerating HTML documentation after generating the instrument from the header file can cause a crash if there is a .sub file for the instrumentNo
Compiler
IDFixed IssueHas Run-Time Impact?
4C18BNIOIf a function returns a structure, in some rare combination of local variables, an access violation may occurNo
4839K3ZWCannot use the Intel 10.0 compiler to compile release executables in LabWindows/CVINo
4ASB9MZWThe scanf function ignores the default locale if the default locale is not EnglishYes
47EA4L1AIncluding NIDAQmx.h after Bussacc.h causes redefinition errors for the INT8 data typeNo
4BB9KTOFMultiplying a 64-bit integer variable by a numeric constant in the parameter list of a compound function call can result in the wrong value being passed to the functionNo
4ARAS49PThe post-increment operator behaves identically to the pre-increment operator when applied to 64-bit integersNo
Debugging
IDFixed IssueHas Run-Time Impact?
43E9QT34Misleading user protection run-time error message when passing a function pointer by valueNo
461C7P34Array argument too small user protection error is incorrectly returned in some rare circumstancesNo
47QDPSIODebugging a project when the Variables window is open, and with a particular combination of DLLs, can cause the application to hangNo
47RB29ZWCannot debug two DLLs with the same base nameNo
4AAELDIOGetLastError might incorrectly return 0 when single-stepping through a LabWindows/CVI programNo
4B59HB9PLabWindows/CVI does not highlight the watch point that triggered a breakpoint when running the Interactive Execution WindowNo
4CSMO9ZWLabWindows/CVI cannot debug applications located in a path with multibyte charactersNo
4D634ZWCreating a source file from a template can result in multiple files with the same name being debugged simultaneously, which can cause LabWindows/CVI to ignore breakpointsNo
Performance
IDFixed IssueHas Run-Time Impact?
44I3FU07Cannot check if a thread lock is availableNo
44AF8QBUMemory is lost when calling SavePanelDisplayToFileYes
489DSQOFThe InetFTPGetDirList function loses memory when used with some FTP serversYes
4APAKMNMMemory is lost gradually when one or more controls in a child panel have tooltipsYes
4D6G4334Memory is lost each time that the font of a menu bar is set using SetMenuBarAttributeYes
4DHDSRZWIn Windows Vista, if the FileSelectPopup function is called the with the Restrict Directory option enabled, and the user attempts to switch directories, the application hangsYes
Stand-Alone Applications and Distributions
IDFixed IssueHas Run-Time Impact?
467B8GZWEdit Distribution dialog box is too smallNo
49N9LJ18Unable to display more than one merge module in Edit Installer dialog boxNo
.NET and ActiveX
IDFixed IssueHas Run-Time Impact?
435H1O0SLabWindows/CVI ActiveX server function (AppCreateDistributionKit) hangs if there is no distribution in the workspaceYes
3U0B9OKFSome Excel examples and the Excel Reports library do not work properly with Excel 2007No
49MCM154Missing prototype error when calling the WordRpt_SetMargins functionNo
4A0DKSNMCalling a LabWindows/CVI ActiveX Server function from a compiler build step causes LabWindows/CVI to hangNo
4CREBOZWIn the ActiveX Controller Wizard, returning to the original screen by clicking the Back button, and then clicking the Next button, causes an error to be displayedNo
43E9FUBUMatlab shipping example does not work with Matlab 7 or laterNo
Hardware
IDFixed IssueHas Run-Time Impact?
44H9IK0SComFromFile behaves incorrectly when count = 0Yes
4A78TS0SClosing and then reopening a COM port can cause events from the first session to be sent to the COM callback of the second sessionYes
4AAB6N0SA race condition in the RS-232 library can cause a crash if the output queue is enabledYes
4CUC39I0Applications that use the GPIB library report a link error when building the debug configuration if the run-time support is Instrument driver onlyNo
Analysis
IDFixed IssueHas Run-Time Impact?
3L8MCTQQIncorrect HarmonicAnalyzer results for THD+NOISEYes
44CFCSJWN_Dist and InvN_Dist do not return correct values for some inputsYes
4DADRH00Some Analysis Library error codes are not recognized by the GetAnalysisErrorString functionYes
Help
IDFixed IssueHas Run-Time Impact?
464E54ZWMissing documentation in MatrixMul functionNo
Miscellaneous
IDFixed IssueHas Run-Time Impact?
4B9CKNOFThe ListInsertItems function can return a dynamic memory corruption error, depending on the number of items insertedNo
44JCHT00INI library (inifile.fp) does not support commentsYes
48477TBUHost name resolution missing from the Internet LibraryYes
Copyright© 1993–2007 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.TrademarksNational Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks. For a listing of the copyrights, conditions, and disclaimers regarding components used in USI (Xerces C++, HDF5, Citadel 5, b64 library, and Stingray), refer to the USICopyrights.chm.The mark LabWindows is used under a license from Microsoft Corporation.PatentsFor patents covering the National Instruments products, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your CD, or ni.com/patents.
页:
[1]