LabWindows/CVI 9.0 Full Win32Eng LabWindows/CVI9.0完整版下载
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 9.0 Full Win32Eng LabWindows/CVI9.0完整版下载
LabWindows/CVI是一个ANSI C软件开发环境，提供一套用于开发测试和测量应用程序的完整编程工具。
LabWindows/CVI ANSI C集成编程环境可帮助您创建自定义工程应用程序。该环境可用于管理项目、编辑和调试源代码和构建用户界面，并提供一个简化的选项卡式工作区来测试代码输出和性能。LabWindow/CVI提供了高级调试、代码文档描述和系统部署所需的工具，可帮助您集成源代码控制、需求和数据管理系统。该软件还可具有内置仪器I/O库、内置仪器驱动程序或两个交互式测量辅助工具，帮助您更轻松、快速地采集GPIB、USB、串行、以太网、PXI、VXI和FPGA仪器的数据。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。
9.0完整版：有ZIP和EXE两个版本，ZIP版为现在提供下载版本，但是视觉论坛未找到资源，仅提供EXE版本：
(MD5)
0a3a0181263d95afd3f98ca4cac04cfb
(SHA256)
d060fc8ecfdc05d14dd042672a663123336e37230a3b4bd2ca8ee17bbc476ea6
ZIP无资源
EXE版：
文件大小: 293191200 字节 (279.61 MB)
修改日期: 2008-10-11 01:38
MD5: b17231e02edd1eea1e9de3dc0f45cea5
SHA1: c6957dfbf653a19fc5274dd089fe6db15031270f
SHA256: 2ce39a4213227c3696886590705e13c022c9ee2f811d66201d45dec88f925778
CRC32: 48ba9ee1
百度和NI官方下载地址：
LabWindows/CVI for Windows Vista/XP/2000, Version 9.0Readme 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 9.0
Known Issues
Bug Fixes
Minimum System RequirementsTo run LabWindows/CVI 9.0, 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 program to take full advantage of all LabWindows/CVI 9.0 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 9.0, you must install these products in the following order:
[*]LabWindows/CVI 9.0
[*]LabWindows/CVI 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 9.0 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 from the LabWindows/CVI Full Development System (FDS). Some Win32 API header and import library files are included when you install the LabWindows/CVI Base package.
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.
[*]The LabWindows/CVI installation includes the LabWindows/CVI 9.0 Run-Time Engine. This version overwrites previous versions of the run-time engine. After you install LabWindows/CVI 9.0, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 9.0 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.
[*]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 InstallationComplete the following steps to install LabWindows/CVI 9.0:NoteIf you already have a different version of LabWindows/CVI installed on your computer, be sure to install version 9.0 in a different directory or uninstall the other version before installing LabWindows/CVI 9.0.
[*]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 9.0 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.
[*]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 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 LabWindows/CVI 8.1.1 or earlier and you install LabWindows/CVI 9.0 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 Vista: \Users\Public\Documents\National Instruments\CVI90\samples. On Windows 2000/XP, example programs are located in the following location: \Documents and Settings\All Users\Documents\National Instruments\CVI90\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 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 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.
[*]Starting with LabWindows/CVI 9.0, the Auto Size and Scroll (when loaded) option of table controls and tree controls is also enforced when printing the control, and when the control resizes as a result of the Scale Contents On Resize option of panels.
Known Issues
[*]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.
[*]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 9.0, 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 9.0 in LabWindows/CVI 8.1.1 or earlier.
You can save .uir files you create or load in LabWindows/CVI 9.0 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 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.5.1 and LabWindows/CVI 9.0. For a list of bug fixes in previous releases, refer to ni.com.User Interface
IDFixed IssueHas Run-Time Impact?
127846ClipboardGetBitmap can cause a general protection fault for images with color depths lower than 32-bitYes
125025User Interface Editor changes made with the Text Tool do might not persistNo
124788Out of range warning in the User Interface Editor when editing a numeric control with Range Checking set to CoerceNo
123692Splitters with Span Panel enabled do not draw correctly when scrolling the panelYes
121776A timer control event can be sent unexpectedly if the previous event was delayedYes
121405Some printing operations can block other threads from executingYes
121207Graph and strip chart legend cannot be made transparentYes
120414Strip chart scrolling is very slow when many points are plotted and y-axis autoscaling is disabledYes
120197Inc/dec arrows sometimes disappear when editing the numeric cell of a tableYes
119695Minimized window reports an incorrect value for the ATTR_WINDOW_ZOOM attributeYes
119315When editing table cells and Caps Lock is on, tabbing does not advance to the next cellYes
119314Double-clicking to autosize table row does not take into account multiple lines when table cell is in word wrap or character wrap modesYes
124400InsertPanelAsTabPage can cause a general protection faultYes
116671Inconsistent cut/copy/paste behavior in cells of tables with Auto Edit enabledYes
114873Unable to change the tab order of an ActiveX control in the User Interface EditorNo
113973Internal metafonts are visible in the font selection dialog boxNo
113568A general protection fault can occur when modal panels are created in a secondary threadYes
112287In Vista Aero,燾hild panels do not draw correctly after minimizing the parent panelYes
110020Rotated labels of strip chart axes can draw outside the control boundariesYes
107830When calling DirSelectPopup with Allow Cancel set to 0, the Done button does not respondYes
104340The highlighting of the active tab of a tab control overlaps images and tab label selection boxYes
104055Scale Contents On Resize option does not resize the center part of a lab-style gauge controlYes
102989With ATTR_MINIMIZE_OTHER_PANELS enabled, right-clicking the taskbar button of a minimized panel restores the panel unexpectedlyYes
99880A general protection fault can occur when simultaneously creating/destroying panels from one thread and showing/hiding them from a different thread.Yes
98435Incorrect event data sent to callback for graph cursor eventsYes
95092In some fonts, Chinese characters do not display properlyYes
93835Some changes made in the Quick Edit Window of the Edit Tree dialog box do not persistNo
59589Sample menu bar insertion causes items on UIR to move when the file is reopenedNo
59440DataSocket binding does not work in the User Interface Editor for controls within a tab pageNo
58808Scaling table controls with the Scale Contents On Resize option can introduce cumulative inaccuracies in the size of the textYes
58796PointPinnedToRect pins to 1-pixel outside the rectangle on the right and bottom edgesYes
58749CanvasSetClipRect is ignored while a canvas batch is activeYes
58584Interactive strip chart legend operations in the User Interface Editor persist after leaving operate modeNo
58568The initial position of the line thickness slide in an interactive graph legend is not set properlyYes
58508Plotting to a paused strip chart does not always update the gridlines correctlyYes
58499Cannot use the interactive爈egend to rename strip chart traces in the Quick Edit Window of the Edit Strip Chart dialog boxNo
58429Changing the color of a tab panel in the User Interface Editor does not change the color of the corresponding tabNo
57849Strip chart control does not redraw traces correctly after calling RecallPanelStateYes
56777Password custom control does not handle clipboard operations correctlyYes
55872Cannot use non-powers of 10 as the min and max of a graph axis in logarithmic modeYes
44569Sizing a table row or column interactively can introduce scaling errors if the panel has the Scale Contents On Resize option enabledYes
44530Tree controls with the Full Row Select attribute enabled have extra gaps surrounding each gridline, if the tree has more than one columnYes
44131Attempting to edit a table control cell containing the specified maximum number of characters causes the contents of the cell to disappear if Auto Edit is enabledYes
42949Tooltips of child panel controls can appear in the wrong location if the panel is scrolledYes
42619Canvas control contents appear on the panel when the canvas is not visible, if the canvas does not have Mark for Update enabledYes
42523Resizing panels can cause controls on the panel to flash repeatedlyYes
41845Strip chart updates inconsistently when it is dimmedYes
41762Rotated strip chart axis labels can overwrite axis names or draw outside the control boundariesYes
41422Plotting a large number of points at once to the strip chart causes the x-scale range to be incorrectly updatedYes
40882Horizontal scrolling of touchpads not supportedYes
36547Knob needles can snap directly from the max value to the min value or vice-versaYes
34909Message Dialogs with buttons do not respond to arrow keysYes
Development Environment
IDFixed IssueHas Run-Time Impact?
127879Removing a project from a workspace while a function tree is open can cause a general protection faultNo
124951Intermittent problems with license activation in LabWindows/CVI 8.5.1 FDSNo
124577Selecting Project from Template on the Welcome Page and not adding the project to the current workspace can cause a general protectionNo
121917Launching the Select Attribute Constant dialog box from a function panel can cause a general protection faultNo
120872Checking out a file from source code control, after having made changes to it, and discarding the changes, can cause a general protection faultNo
58038Cannot select a custom path for the Where to Copy DLL option in the Target Settings dialog box for DLLsNo
117394Changing the version of a .fp file from 8.5 and later to an earlier version might cause an internal errorNo
112735The error message displayed when using a read-only workspace cannot be movedNo
107394Sometimes, when exiting LabWindows/CVI with the workspace window maximized, the next time LabWindows/CVI starts up, an Attribute passed is not valid error is displayedNo
10459464-bit numeric controls do not load correctly from an FPX fileNo
104402Borland DLLs are not properly named in Loaded Modules windowNo
99478Accessing the <<Running>> menu when the focus is on the error window can cause a general protection faultNo
98681LabWindows/CVI includes temporary auto-backup files in multi-file searchesNo
96692Dotted line for a collapsed source code region is not removed when deleting the regionNo
96354Creating a new DAQ task from the Welcome Page can cause a general protection fault if the current project includes a .fp file that requires compilationNo
95889The Source window does not receive focus when a build error occurs and Classic View is enabledNo
60017Source window color customizations are lost when the system color depth changes while LabWindows/CVI is runningNo
59735Multi-file searches include non-project filesNo
58743Show Completions option is not available for struct members that are used as array indicesNo
58639When generating a function tree from a header file enums without labels are not processed correctlyNo
58638Long file names cause results to be clipped in the Find Results windowNo
58430Syntax coloring for parts of a comment can be incorrect燼fter new lines not created using the <Enter> keyNo
58407Some header files created from a template are put under the wrong folder in the project treeNo
57001Cannot generate function panels from header files containing unsigned char * parametersNo
44752Close button on tabbed workspace bar is not correctly positioned for very narrow windowsNo
42013Dragging a file that is excluded from the build from one project to another leaves the file excluded in the new projectNo
38382Line continuation character causes the Balance command to work incorrectlyNo
Compiler
IDFixed IssueHas Run-Time Impact?
124569Pre-build build steps occur only if LabWindows/CVI compiles filesNo
123149Redeclaration error for StrToIntA when including toolbox.h and shlwapi.hNo
122509Type library generation errors and resource embedding errors are not reported as build errorsNo
115846cviauto.lib does not link in Microsoft Visual Studio 8No
108285Errors in release builds are not reported in a batch buildNo
98829typedefs based on 64-bit integers are not included in type libraries embedded in DLLsNo
96261Compilation conflict between the analysis library and the Word Report instrument driverNo
66600Valid structure pointers passed into a function can trigger a user protection error inside the functionYes
58998Compiling with an external compiler resets build dependencies in the debug configurationNo
58889LabWindows/CVI does not detect that a NaN value is unequal to itself (x != x)Yes
58540Unexpected wait cursor is displayed when compiling a single file with unsaved changes using an external compilerNo
58483Automatically inserted include statements are always added to the top of the source fileNo
57356The mscorlib2.c file compiled in Microsoft Visual Studio 6 does not load in LabWindows/CVINo
120676With the iso_9899_1999 pragma enabled, LabWindows/CVI does not allow variable declarations immediately following a case statementNo
117592With the iso_9899_1999 pragma enabled, LabWindows/CVI does not allow variable declarations of custom types in the middle of a blockNo
60413Documentation tags for source code are not skipped inside blocks excluded from compilation by the preprocessorNo
Debugging
IDFixed IssueHas Run-Time Impact?
125405Selecting Original Type for the Interpret As command does not update the Variables or Watch windowsNo
125207LabWindows/CVI can crash when writing the contents of the Variables window to a file if large string buffers are presentNo
124741LabWindows/CVI can display the value of the wrong variable in a data tooltip, if a different variable at a different scope has the same nameNo
119223String Display window does not display control characters correctlyNo
120710Changing an enum variable in the Variables Window does not update the variable抯 value in the Watch Window, and vice-versaNo
120520Cannot edit characters in non-ASCII mode in String Display windowNo
64228ListInsertItems function in Programmer抯 Toolbox can incorrectly return a dynamic memory corruption errorYes
41714User protection of PlotStripChart function does not take into account the startingIndex and skipCount parametersYes
41700Loading or unloading instrument drivers is possible while execution is suspendedNo
41436Project switching is possible while execution is suspendedNo
58956Global debug break key does not break execution consistentlyNo
Performance
IDFixed IssueHas Run-Time Impact?
116827LabWindows/CVI applications can have a noticeable delay at startup if the ISA Firewall client is installedYes
115124Memory is lost when calling some Advanced Analysis Measurement functionsYes
114644Application stops responding when unregistering a DDE server with active connectionsYes
96027Source window editing is not as responsive when using LabWindows/CVI via Windows Remote DesktopNo
55487The performance of matrix by vector multiplication is inadequate in some casesNo
35750When debugging a multithreaded program, continuing execution after hitting a breakpoint can sometimes cause LabWindows/CVI to pause for a long timeNo
Stand-Alone Applications and Distributions
IDFixed IssueHas Run-Time Impact?
111051Distribution of an ActiveX server application includes unnecessary project files by defaultNo
110454Default LabWindows/CVI EXE icon does not include images with the appropriate resolution for displaying in larger sizesYes
106816Trailing space at end of distribution output path causes build failuresNo
38153It is not possible to specify pre/post-build steps for building a distributionNo
36322Distribution of an ActiveX server application does not include associated help fileNo
.NET and ActiveX
IDFixed IssueHas Run-Time Impact?
59856Invalid user protection error reported in .NET wrapper codeYes
58458Unknown Language COM error when calling LabWindows/CVI ActiveX Server from a .NET application if the system locale is not English.Yes
98641LabWindows/CVI application can stop responding if it is closed while it is accessed at the same time through ActiveX automationYes
125416Using ActiveX automation to build a project in release mode will result in a failed build if the File Version property of the project includes a + character.Yes
Analysis
IDFixed IssueHas Run-Time Impact?
54563The Sort Function returns 0 when the input array contains one elementYes
Miscellaneous
IDFixed IssueHas Run-Time Impact?
128323Network variables created programmatically do not configure the single-writer restriction correctlyYes
126669The RegEnumerateValue function cannot retrieve empty values from the registryYes
122632DiscardAsyncTimer can return an error if timers are not discarded in the order in which they were createdYes
114623Some CVIXML functions do not return an error when invalid inputs are passed to themYes
114291Toolbox registry API lacks the ability to delete keys/valuesNo
104648Toolbox registry API lacks the ability to enumerate subkeysNo
104576The OPT_PROCESS_EVENTS_WHILE_WAITING flag for the CmtWaitForThreadPoolFunctionCompletion function does not process all eventsYes
98433Variable Manager does not handle the buffer size of programmatically configured network variables properlyNo
59197InstallWinMsgCallback is not thread safeYes
59181Wildcards used in the new name of the RenameFile and CopyFile functions are not always processed correctlyYes
Copyright© 1993–2008 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, 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.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.For copyright notices, conditions, and disclaimers regarding certain components used in USI (Xerces C++, ICU, HDF5, Citadel 5, b64 library, and Stingray), refer to the USICopyrights.chm.Other product and company names mentioned herein are trademarks or trade names of their respective companies.PatentsFor 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]