Print
PDFOverview
This document explains how a Win32 GPIB application works on the different Windows platforms.
Table of Contents
Windows 2000
The GPIB software for Windows 2000 includes a Dynamic Link Library (DLL) that runs in user mode and a multi-layered device driver that runs in kernel mode. The multi-layered device driver consists of three drivers: a device class driver that handles device-level calls, a board class driver that handles board-level calls, and a GPIB port driver that uses the Hardware Abstraction Layer (HAL) to communicate with the GPIB hardware. User applications access this device driver from user mode through gpib-32.dll, a 32-bit Windows 2000 DLL.
All of these files are included with the GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example C:\Windows\System32).
A Win32 application can either link with the language interface or directly access the functions exported by the gpib-32.dll. Figure 1 below shows the interaction between a GPIB application using direct entry (the shaded Win32 Application on the left) or a GPIB application using the language interface and the GPIB software components.
The GPIB software for Windows NT includes a Dynamic Link Library (DLL) that runs in user mode and a multi-layered device driver that runs in kernel mode. The multi-layered device driver consists of three drivers: a device class driver that handles device-level calls, a board class driver that handles board-level calls, and a GPIB port driver that uses the Hardware Abstraction Layer (HAL) to communicate with the GPIB hardware. User applications access this device driver from user mode through gpib-32.dll, a 32-bit Windows NT DLL.
All of these files are included with the GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example C:\Windows\System32).
A Win32 application can either link with the language interface or directly access the functions exported by the gpib-32.dll. Figure 1 shows the interaction between a GPIB application using direct entry (the shaded Win32 Application on the left) or a GPIB application using the language interface and the GPIB software components.
Windows 98
The GPIB software for Windows 98 includes a multi-layered device driver that consists of Dynamic Link Library (DLL) pieces that run in user mode and VxD pieces that run in kernel mode. User applications access this device driver from user mode through
gpib-32.dll, a 32-bit Windows 98 DLL.
All of these files are included with the GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example, C:\Windows\System).
A Win32 application can either link with the language interface or directly access the functions exported by the gpib-32.dll. Figure 2 below shows the interaction between a GPIB application using direct entry (the shaded Win32 Application on the left) or a GPIB application using the language interface and the GPIB software components.
The GPIB software for Windows 95 includes a multi-layered device driver that consists of Dynamic Link Library (DLL) pieces that run in user mode and VxD pieces that run in kernel mode. User applications access this device driver from user mode through
gpib-32.dll, a 32-bit Windows 95 DLL.
All of these files are included with the GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example, C:\Windows\System).
A Win32 application can either link with the language interface or directly access the functions exported by the gpib-32.dll. Figure 2 shows the interaction between a GPIB application using direct entry (the shaded Win32 Application on the left) or a GPIB application using the language interface and the GPIB software components.
Reader Comments | Submit a comment »
Pls update article to include WinXP and
Win7 (both look like NT when enabling
DOS support for NI-488.2)
- Jul 11, 2010
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).