Questions and Answers about LabWindows/CVI for Microsoft Windows and
LabWindows/CVI for Sun Solaris 

Market Impact

1. In what market areas will LabWindows/CVI have the greatest impact? 

LabWindows/CVI for Windows and LabWindows/CVI for Sun will have an
immediate impact on all scientific and engineering-related market areas.
LabWindows/CVI extends the National Instruments multiplatform application
software strategy, which caters to ANSI C programmers with LabWindows/CVI,
and to graphical programmers with LabVIEW for Windows/Sun/Macintosh.
Scientists and engineers can match their programming experience to the
application software package that is best for them - LabWindows/CVI or
LabVIEW. These application areas include test and measurement, ATE,
process control, data acquisition, and analysis and signal processing.

LabWindows/CVI for Windows eliminates the need for programmers to become
familiar with the low-level Windows operating system details to build
Windows applications, providing a higher-level development environment for
creating and controlling graphical user interfaces (GUIs) quickly and
easily. LabWindows/CVI for Windows brings the power and flexibility of
ANSI C programming to Windows, while hiding the cumbersome details of
traditional Windows development from the user. The incredible growth and
success of Windows has driven many scientists and engineers to the Windows
environment, only to find a lack of sufficient test and measurement-based
development tools for C programmers. LabWindows/CVI delivers easy-to-use
Windows development tools for C programmers.

LabWindows/CVI for Sun unleashes the processing power of a Sun workstation
to scientists and engineers, delivering a user-friendly programming
interface and high-level GUI development tools to Sun workstation users.
Traditionally strong in C programming, UNIX users can acquire data and
control instruments from the same workstations they use for high-powered
product design and data analysis. LabWindows/CVI for Sun bridges the gap
between data acquisition and instrument control and the processing power
of a Sun workstation, serving both the non-UNIX user who needs the power
of a workstation as well as the experienced UNIX user who needs to acquire
data or control instruments.

2 . What impact will LabWindows/CVI have on National Instruments
revenue/market share? 

LabWindows/CVI for Windows/Sun will add significantly to the already strong
position of the National Instruments application software packages -
LabWindows for DOS and LabVIEW for Windows/Sun/Macintosh. This assumption
is based on several factors, including the large installed base of DOS
users of LabWindows seeking a migration path to Windows or Sun, the
overwhelming success of the Windows operating system, the huge installed
base of 386 and 486 PCs, and the wide acceptance of ANSI C as a
programming standard. Because of the tight coupling between LabWindows/CVI
and all of National Instruments instrument control and data acquisition
(DAQ) hardware for PC/AT/EISA and PS/2 computers, LabWindows/CVI will have
a significant impact on a broad spectrum of markets and application
areas.

3 . How will LabWindows/CVI affect alliances between National Instruments
and third-party strategic partners? 

LabWindows/CVI provides a standard platform for developing large scale data
acquisition and instrument control applications. Significant development
effort was invested in making LabWindows/CVI an open system, able to
communicate with Windows DLLs or external object modules. Providing an
open system that is based upon the worldwide ANSI C programming language
standard makes LabWindows/CVI very attractive to all system integrators,
including ATE and process control system developers. LabWindows/CVI
delivers standard software tools in a simplified application programming
interface (API) for building windowing applications. Because of these
features, LabWindows/CVI will quickly become popular with system
integrators and developers.

Language Issues

4 . Why was ANSI C chosen as the programming language for LabWindows/CVI? 

In recent years, the instrumentation market has shown a steady shift toward
C as the language of choice. The instrumentation market has been
historically dominated by BASIC, due mainly to the prevalence of
Hewlett-Packard instruments controlled by HP BASIC. However, recent
surveys have shown C outpacing BASIC as the language of choice for
scientists and engineers. Recent engineering graduates schooled in C
programming are replacing many long-time BASIC users. In addition, C
provides the power and flexibility needed to take advantage of the Windows
and UNIX operating systems. For these reasons, it was obvious that C was
the best choice for LabWindows/CVI.

5. Why was BASIC not chosen as the programming language for LabWindows/CVI?


Although BASIC has been popular in the instrumentation marketplace in the
past, we chose not to use the BASIC programming language in LabWindows/CVI
for the following reasons: 

(1) The market has shown a clear shift toward C Programming in recent
years. 

(2) If two languages were incorporated, tradeoffs would have to be made
that would hinder the functionality of the product. 

(3) Visual Basic already provides a solution for BASIC users under Windows.
National Instruments endorses the use of Visual Basic for those customers
who need to acquire data or control instruments from a Windows application
and prefer to program in BASIC. All of the company's hardware products
include DLLs that developers can use with Visual Basic. Therefore, using
BASIC in LabWindows/CVI would only duplicate a certain amount of the
development effort already exerted by Microsoft with Visual Basic.
However, until LabWindows/CVI, C programmers have not had a development
tool for quickly and easily building Windows applications. 

(4) ANSI C is an established standard, whereas BASIC has many different
adaptations available on the market.

6. How can C programmers incorporate existing C code into LabWindows/CVI? 

Because LabWindows/CVI provides an open foundation for building Windows and
UNIX applications quickly, many C programmers will want to incorporate
their existing code into LabWindows/CVI. Users can incorporate existing C
code into LabWindows/CVI via the following methods: 

(1) Because LabWindows/CVI complies with the full ANSI C language
specification, users can load and run any C code that follows the ANSI C
specification within the LabWindows/CVI environment. 

(2) Users can convert their code into DLLs or use existing DLLs with
LabWindows/CVI. 

(3) Users can compile any existing source code with the WATCOM C compiler
and load the object module into LabWindows/CVI. Because it is a 32-bit
environment, the initial version of LabWindows/CVI works only with the
WATCOM 32-bit C compiler for external object modules. LabWindows/CVI for
Sun users can compile external code with the Sun Microsystems ANSI C
compiler (acc) or the public domain GNU C compiler (gcc) to load into the
LabWindows/CVI environment.

7. Does LabWindows/CVI accommodate C++ language extensions? 

The initial version of LabWindows/CVI incorporates only the ANSI C language
specification; users cannot use any C++ language extensions or structures
within LabWindows/CVI. C++ was originally developed to provide guidelines
for creating structured, reusable code within an application. C++, or
object-oriented techniques, are valuable for large-scale, professional
software development projects. Although the initial investment in C++ may
be lengthy, it can pay off farther down the development cycle as more and
more reusable code segments are created. Because the emphasis of
LabWindows/CVI is to provide tools to quickly build Windows and UNIX
applications, C++ was not considered for the first release of
LabWindows/CVI. Scientists and engineers creating small to medium scale
test and measurement or DAQ systems with LabWindows/CVI do not need the
additional classes, structures, and overhead associated with C++. In
addition, scientists and engineers generally have not embraced C++ to the
same extent they have accepted the standard C language. As a whole, it is
not yet obvious within the instrumentation industry if the time and effort
required to learn C++ is worth the gains for scientific or engineering
applications. If the instrumentation industry demands C++ in the future,
National Instruments will take the appropriate measures to meet this
demand.

Comparing LabWindows/CVI to LabWindows

8. What enhancements does LabWindows/CVI offer the DOS user of LabWindows?


LabWindows/CVI is a new product - it is much more than a simple port of the
LabWindows for DOS product to the Windows and Sun operating systems.
LabWindows/CVI is an entire rewrite of the product, with many new features
and enhancements. Not only is LabWindows/CVI a full ANSI C development
tool (BASIC capability is left to LabWindows for DOS), but every major
development tool in LabWindows/CVI was advanced an order of magnitude in
sophistication and functionality over those found in the DOS version,
including the User Interface Editor and Library, the Source Code Editor,
variable display, compiler, and debugger. LabWindows/CVI is a significant
extension of the baseline programming tools and methodology introduced in
LabWindows for DOS.

9. What level of compatibility will DOS users of LabWindows have when they
migrate from DOS to LabWindows/CVI? 

Although 90 to 95 percent of existing LabWindows for DOS features will be
portable to LabWindows/CVI, a certain percentage of the DOS product's
functionality cannot exist under Windows. An example is the color palette
functions found in LabWindows Version 2.3 for DOS. Because Windows and
UNIX have a totally different color palette scheme than DOS, these
functions will not be portable to LabWindows/CVI. The company will provide
suggested work-around solutions for these problem areas and will document
them in the LabWindows/CVI translators and user manuals.

10. Can users port existing DOS LabWindows applications to LabWindows/CVI?


LabWindows/CVI is built upon the programming tools and methodology
introduced in the LabWindows for DOS product. LabWindows/CVI provides a
relatively smooth migration path for DOS users to port their applications
to the Windows or UNIX operating systems. LabWindows/CVI will include
translators to convert existing DOS-based LabWindows GUIs and C source
files into LabWindows/CVI-compatible files to run under Microsoft Windows
or Sun Solaris. The converter utilities will automatically map any
obsolete LabWindows for DOS functions into LabWindows/CVI functions and
bring source code files up to date.

11. Will LabWindows/CVI use the same instrument drivers as the DOS version?


LabWindows for DOS currently has over 300 GPIB, RS-232, VXI, and CAMAC
instrument drivers. National Instruments is taking steps to ensure that
LabWindows/CVI and the DOS version of LabWindows can share the same
Instrument Driver Library, thereby making the current DOS LabWindows
instrument drivers available on Windows and the X Window System on the Sun
with LabWindows/CVI.

12. How do DOS users of LabWindows upgrade to LabWindows/CVI?

Existing DOS users of LabWindows can upgrade to LabWindows/CVI for Windows
for $495 or LabWindows/CVI for Sun for $2,495.

Differentiating LabWindows/CVI from Other Software Packages

13. Why introduce LabWindows/CVI for Windows/Sun when National Instruments
already has LabVIEW for Windows/Sun? 

National Instruments is committed to leading the market in application
software technology for instrumentation. LabWindows/CVI and LabVIEW are
functionally equivalent - both are general-purpose tools that acquire,
analyze, and present data from GPIB, RS-232, VXI, and plug-in DAQ
instrumentation. However, the programming methodology is significantly
different between LabWindows/CVI and LabVIEW. LabVIEW is extremely
successful in delivering a graphical programming solution to novice
programmers or nonprogrammers. However, LabVIEW does not address the
growing base of experienced C programmers. LabWindows/CVI provides
professional-level tools that the experienced C programmer expects, at a
level that a scientist or engineer can use.

Clearly, one software package cannot address the preferences of the entire
market. In order to maintain this leadership in software technology, the
company must provide solutions that cater to customer programming
experience levels and preferences, as well as the different needs to
acquire, analyze, and present data.

14. How is LabWindows/CVI different from LabVIEW for Windows/Sun?

Programming methodology is the primary differentiating characteristic
between LabWindows/CVI and LabVIEW. LabWindows/CVI is an ANSI C
development environment and LabVIEW is a graphical programming development
environment. LabWindows/CVI is targeted at the growing number of C
programmers, and in that sense is very different from LabVIEW.
Functionally, both packages provide the same tools for acquiring,
analyzing, and presenting data and controlling GPIB, RS-232, VXI, and
plug-in DAQ instrumentation hardware. Because the GUI design capabilities
of LabWindows/CVI and LabVIEW are virtually the same, it is possible to
build an application in LabWindows/CVI that looks identical to one built
in LabVIEW.

15. How is LabWindows/CVI different from Microsoft Visual C++?

Microsoft Visual C++ (VC++) is an object-oriented C++ development system
for professional Windows application development. VC++ is targeted at
companies building Windows applications for resale, such as a spreadsheet
or word processing package. VC++ makes it easy to develop large
applications quickly with a multiple document interface (MDI) having the
standard Windows "File," "Edit," and "Window" pull-down menus. Because
major commercial software projects can involve years of development from
many different programmers, companies can afford to invest in learning
C++. C++ is geared for code modularity and reusability (see question
number 7 for more C++ information).

LabWindows/CVI is targeted at scientists and engineers who need to build
applications quickly under Windows or UNIX. Because these users are not
professional software engineers, in many cases it doesn't make sense for
them to spend the time and effort to learn C++. LabWindows/CVI also has
tools targeted specifically for instrumentation applications, such as
instrument drivers, technical analysis functions, and user interface
controls for meters, knobs, graphs, strip charts, gauges, and tanks.

In addition, LabWindows/CVI provides a multiplatform solution to the C
programmer for building portable applications for Windows and the Sun.

16. How is LabWindows/CVI different from Microsoft Visual Basic?

Microsoft Visual Basic offers a development environment for building
Windows applications quickly and easily using the BASIC programming
language. Visual Basic is an excellent tool for quickly creating simple
Windows applications. In fact, National Instruments promotes the use of
Visual Basic with DLLs for users who want to program in BASIC and use
Windows.

However, LabWindows/CVI offers some unique advantages over Visual Basic for
the engineer or scientist. First, Visual Basic is not a standard language.
It is yet another adaptation of the BASIC language available with no real
migration path for DOS developers. LabWindows/CVI is based on ANSI C, an
established standard.

Second, Visual Basic is not a viable solution for C programmers whereas
LabWindows/CVI caters directly to the C programmer. Third, Visual Basic is
only available on Windows, and therefore cannot provide a multiplatform
development solution like LabWindows/CVI. And finally, unlike
LabWindows/CVI, Visual Basic does not have built-in, instrumentation
focused tools, such as instrument drivers, analysis functions, and GUI
instrumentation controls. In our experience with both LabVIEW and
LabWindows, the integrated software tools for data acquisition and
analysis give our users the greatest productivity gains.

17. How will LabWindows/CVI for Windows take advantage of the Windows DLLs
previously introduced for National Instruments hardware? 

National Instruments has developed and maintained a portable development
strategy for all of its driver software (NI-488.2, NI-VXI, NI-DAQ, and
NI-DSP) for years. This strategy gives users the ability to move their
application programs developed with industry standard languages, like C
and BASIC, to new operating systems and new platforms. The Windows DLLs
introduced by National Instruments over the last three years represent the
implementation of this portable software strategy for Microsoft Windows.

Both the LabWindows/CVI and LabVIEW application software packages build on
standardized driver software. In the case of Windows, LabWindows/CVI
accesses the National Instruments hardware through Windows DLLs. Thus, the
massive development effort to make a portable LabWindows/CVI is a logical
Progression in the company's portable software strategy. Now,
LabWindows/CVI programs will work with the National Instruments hardware
regardless of the platform.

National Instruments will continue to develop, support, and supply Windows
DLLs for customers who wish to use LabWindows/CVI, LabVIEW, or other
general-purpose programming environments, such as Borland C++ for Windows,
Microsoft Visual Basic, and Microsoft Visual C++.

Portability and Networking

18. Define the level of portability between Windows and Sun applications
built into LabWindows/CVI. 

Portability means two things. Most importantly, it means that users can run
a LabWindows/CVI project developed on the Windows version without
modification on the Sun. This feature is crucial to the National
Instruments software strategy. It is unclear how many users will take
advantage of this portability, but if nothing else, it gives them security
in knowing they are not tied to a particular computing platform. This
strategy is not new to National Instruments - its entire NI-488.2, NI-VXI,
and NI -DAQ driver strategy is based upon operating system and computing
platform portability. LabWindows/CVI is structured so that much of the
code internal to LabWindows/CVI is identical on all platforms (80 percent
of the LabWindows/CVI code is platform independent). The only variance in
code between LabWindows/CVI versions is in the code that interacts with
computer hardware and the operating system. For users, this level of
portability ensures a common look and feel as well as identical operation
on all platforms. For National Instruments, it means the company can
easily port to other operating systems with minimal development effort as
market demands change in the future.

19. Can users pass data between LabWindows/CVI applications on both
platforms? 

Both LabWindows/CVI products can store and retrieve data in ASCII and
binary formats. Consequently, LabWindows/CVI users can acquire and store
data on one platform and retrieve and analyze it on another platform.

20. Will LabWindows/CVI for Windows have dynamic data exchange (DDE) or
object linking and embedding (OLE) capabilities? 

The initial release of LabWindows/CVI for Windows will have DDE capability.
The initial version of LabWindows/CVI will not have OLE capability.
Although National Instruments has definite plans to include OLE capability
in the future, it is not clear exactly how or when the company will
implement OLE capabilities in LabWindows/CVI.

21. Will LabWindows/CVI for Sun have networking capabilities?

LabWindows/CVI for Sun includes a TCP/IP library, a set of standard
protocols for communicating across a single network or interconnected set
of networks. LabWindows/CVI accommodates the three basic suites of
protocols - the Internet Protocol (IP) for the low-level service of taking
data and packaging of components, the Transmission Control Protocol (TCP)
for high-reliability data transmissions, and the User Datagram Protocol
(UDP) for low-overhead transmissions. The TCP/IP functions handle
conversion between 32-bit Internet addresses, dotted notation Internet
addresses, and domain name addresses. The TCP and UDP functions use 32-bit
Internet addresses to specify destinations.

LabWindows/CVI for Sun Issues

22. Why did National Instruments choose the Sun SPARCstation as the first
workstation platform for LabWindows/CVI?

As the leading manufacturer in the workstation market, the Sun platform has
a large installed base of technical users. Because Sun is already a
dominant player in the Engineering Design Automation (EDA) market as well
as in research and experimentation labs, Sun workstations are widely used
by the same companies that also need high-performance test and measurement
systems. This natural fit will result in the long-awaited goal of the
scientist or engineer performing research or design and testing on the
same platform. For commercial applications, using the same platform for
design and test will result in faster time-to-market cycles and improved
quality.

Sun has the built-in connectivity and networking capabilities that are
required for integrated test systems in applications such as Computer
Integrated Manufacturing. Another attractive feature of the Sun platform
is the openness of the platform, which has resulted in widespread
availability of the SPARC technology. The price/performance ratio of the
SPARCstations also matches the requirements of the test industry, where
the majority of users need controllers priced under $10,000.

The Open Measurement Solutions (OMS) alliance, announced in September 1992
between National Instruments, Sun, and Tektronix, is also a factor. This
alliance has proved very successful for all three parties. Through OMS,
LabVIEW has been introduced at companies like Integrated Measurement
Systems (IMS, Beaverton, OR), which selected LabVIEW for its complex
device testing systems. LabWindows/CVI is a good fit for OMS.

23. Under which Sun operating systems will LabWindows/CVI run?

LabWindows/CVI runs under the Sun Solaris operating system, Version 1.x
(also known as Sun OS 4.1.2) or under Sun Solaris 2.x.

24. Under which UNIX windowing systems will LabWindows/CVI for Sun run?

LabWindows/CVI for Sun was developed with the X Window System, the popular
low-level UNIX window building tools developed by MIT. Because users can
control X Window applications through either the Open Windows or the Motif
window managers under UNIX, LabWindows/CVI for Sun is compatible with both
of these window managers.

Future Plans

25. How will future operating system developments, such as NT, OS/2, and
Pink, affect LabWindows/CVI?

National Instruments is committed to delivering both standard programming
and graphical programming solutions on the most popular platforms as
defined by its users. Tremendous efforts have gone into building a
portable foundation of software managers under LabWindows/CVI. These
managers will make future ports to new operating systems possible for
LabWindows/CVI. In general, customers will make the decision as to which
operating systems and computer platforms LabWindows/CVI must work with.

At this time, Microsoft Windows is clearly the operating system of choice
by a large percentage of the market. The company is anxiously awaiting the
release of Windows NT. LabWindows/CVI is actually a 32-bit application
with a 16-bit interface to Windows 3.x. With NT, LabWindows/CVI will run
much faster. Because of the true multitasking, multi-threaded kernel in
NT, many new applications and opportunities will arise on the PC platform.
Once National Instruments has released and stabilized the initial version
of LabWindows/CVI for Windows, it will make a Microsoft Windows NT version
available. The company expects the Windows NT version of LabWindows/CVI to
be available in early 1994.

26. What are the future plans for the DOS-based LabWindows?

LabWindows will continue to be sold and supported by National Instruments
for the following reasons: 

(1) DOS will continue to be a major OS platform for several years to come.


(2) DOS requires a less powerful computer to run than Windows, and may
therefore still be a better solution for certain customers or
applications. 

(3) We can more easily distribute DOS applications than Windows
applications for the same resource issues. 

(4) LabWindows for DOS is the most widely installed PC instrumentation
software package. LabWindows will continue to control all of the National
Instruments GPIB, VXI, and DAQ hardware for DOS users.

Instrumentation Hardware

27. Which National Instruments hardware works with LabWindows/CVI for
Windows?

The Windows version of LabWindows/CVI can control the National Instruments
hardware for PC/XT/AT/EISA and PS/2 computers, including interfaces for
GPIB and VXI instrument control, plug-in DAQ boards for real-world signal
acquisition, and SCXI signal conditioning hardware.

See the National Instruments 1994 catalog for more details on PC-compatible
hardware products.

28. Which National Instruments hardware works with LabWindows/CVI for Sun?

LabWindows/CVI will control all National Instruments instrumentation
hardware available for the Sun SPARCstation. Hardware available for the
SPARCstation includes a plug-in SBus GPIB interface board, an external
GPIB-to-SCSI interface, a plug-in MXIbus interface for controlling
MXI-equipped VXI and VME systems, and the GPIB-ENET/Sun for communicating
with and controlling IEEE 488 devices from anywhere on an Ethernet-based
TCP/IP network. The company is currently developing SBus DAQ hardware for
the SPARCstation, and expects the first products to be available by the
end of the year.

See the National Instruments 1994 catalog for more details on
SPARCstation-compatible hardware products.

Computer Configuration Information

29. What computer configurations are necessary to run the Windows and Sun
versions of LabWindows/CVI?

The minimum configuration for LabWindows/CVI running on Windows is a 386/33
with 387 coprocessor, 8 MB RAM, 20 MB hard disk space and DOS 5.0 and
Windows 3.1. For most applications, National Instruments recommends using
a 486/33 with Super VGA display.

The minimum Sun configuration is a SPARCstation with 24 MB main memory, 32
MB disk swap space, 20 MB disk space for the application and associated
files, Solaris 1.x or 2.x, and MIT's X Window System Version 11 Release 5.
LabWindows/CVI will run under Motif or Open Look.

Price and Availability

30. When will LabWindows/CVI for Windows and LabWindows/CVI for Sun be
available and how much will they cost? 

The LabWindows/CVI Full Development System for Windows will be available in
November for $1,995. It includes the Data Acquisition Library, GPIB
Library, Instrument Library, Analysis libraries, User Interface Library,
Utility libraries, and the standard ANSI C libraries. A base package
configuration, priced at $995, includes all of the libraries except the
Advanced Analysis Library. A special LabWindows/CVI VXI Development System
for Windows, which includes all of the LabWindows/CVI instrument drivers
and VXI controller libraries, will sell separately for $3,995.

LabWindows/CVI for Sun will be available in December for $3,995 for a
single-user, floating license. It includes the GPIB Library, Instrument
Library, Analysis libraries, User Interface Library, Utility libraries,
and the standard ANSI C libraries. The LabWindows/CVI VXI Development
System, which includes all of the LabWindows/CVI instrument drivers and
VXI controller libraries, will be available separately in December for
$4,995. Multi-user site licensing will also be available.

A Windows NT version of LabWindows/CVI will be available in the first
quarter of 1994.

For More Information For more information, please contact National
Instruments at 6504 Bridge Point Parkway, Austin, TX 78730-5039, (512)
794-0100. Call toll free at (800) 433-3488. Fax: (512) 794-8411.

 ==========================================================
 From the 'New Product Information' Electronic News Service
 ==========================================================
 This information was processed from data provided by the
 above mentioned company. For additional details, contact 
 the company at the address or telephone number indicated.
 ==========================================================
 All submissions for this service should be addressed to:
 BAKER ENTERPRISES,  20 Ferro Dr,  Sewell, NJ 08080  U.S.A.
 Email:  RBakerPC (AOL/Delphi), rbakerpc@aol.com (Internet)
 ==========================================================
