General information, Using labwindows/cvi utility library in the borlan, Using netdde on windows – National Instruments Window User Manual

Page 38: Special instructions to labwindows/cvi 5.0 beta te, No support for multiple monitor systems, Dynamically loading dll created in third-party com, Might lose handles

Advertising
background image

LabWindows/CVI Release Notes for Windows

38

©

National Instruments Corporation

General Information

Using LabWindows/CVI Utility Library in the Borland Compiler

When you use the LabWindows/CVI libraries with the Borland compiler, the

utility.h

header file in the Borland

include

subdirectory might be referenced incorrectly instead of

the LabWindows/CVI

utility.h

header file. You can control the search order for the header

files through one of the following methods:

Place the LabWindows/CVI include directory before the Borland include directory in the
Borland Project Options directory search paths.

In your source code, refer to the explicit path to the header file, for example,

#include

"c:\cvi\include\utility.h"

.

Rename the Borland

utility.h

file.

Using NetDDE on Windows

Refer to the LabWindows/CVI

readme.cvi

file for information on using NetDDE on

Windows 3.1, Windows 95, and Windows NT.

Special Instructions to LabWindows/CVI 5.0 Beta Testers

A debuggable DLL built with LabWindows/CVI 5.0 Beta 1 is not compatible with the final
release of LabWindows/CVI 5.0. You must rebuild the DLL before you try to debug the DLL
inside the LabWindows/CVI development environment.

No Support for Multiple Monitor Systems

LabWindows/CVI 5.0 does not support systems with multiple monitors, including
Windows 98, Windows NT 5.0, and third-party solutions for Windows 95/NT 4.0.

Dynamically Loading DLL Created in Third-Party Compiler
Might Lose Handles

If a DLL created in a third-party compiler/linker is dynamically loaded and unloaded from a
process and if that DLL uses the hardware static libraries located in the LabWindows/CVI

\extlib

subdirectory, the process loses Windows handles. The external compiler support

libraries that exhibit this behavior are

dataacq.lib

,

easyio.lib

,

gpib.lib

,

nivxi.lib

,

and

visa.lib

. The loss of Windows handles occurs when the hardware static libraries of the

calling DLL do not release the internal handles used to load the hardware libraries. A
workaround is to use the import libraries that come with the DAQ, GPIB, VXI, and VISA
software instead of using the static libraries from the LabWindows

\extlib

directory. A

drawback to this solution is that some additional functions unique to the LabWindows/CVI
versions of these libraries are not available.

Advertising