PDF1. 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 your GPIB software. When you install the GPIB software, these files are copied into the windows\system32 directory, where windows is your Windows 2000 directory (for example C:\Windows).
A Win16 application uses the 16-bit DLL, gpib.dll, to access the GPIB virtual device driver, gpib-vdd.dll. Figure 1 shows the interaction between a Win16 application 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 your GPIB software. When you install the GPIB software, these files are copied into the winnt\system32 directory, where winnt is your Windows NT directory (for example C:\Windows).
A Win16 application uses the 16-bit DLL, gpib.dll, to access the GPIB virtual device driver, gpib-vdd.dll. Figure 1 shows the interaction between a Win16 application and the GPIB software components.
3. Windows 98
Using the Native 32-bit GPIB Driver for 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 your GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example C:\Windows\System).
A Win16 application uses the 16-bit thunking DLL, gpib.dll, and the 32-bit thunking DLL, gpib32ft.dll, to access the GPIB driver. Figure 2 shows the interaction between a Win16 application and the GPIB software components.
Figure 2
Using the 16-bit GPIB Driver for Windows 3.x
The GPIB software for Windows 3.x is a standard 16-bit Windows Dynamic Link Library (DLL). This file is included with the GPIB software. When you install the GPIB software, it is copied into the Windows system directory (for example C:\Windows\System).
A Win16 application uses the 16-bit DLL, gpib.dll to access the GPIB driver. Figure 3 shows the interaction between a Win16 application and the GPIB software components.
Using the Native 32-bit GPIB Driver for Windows 95
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 your GPIB software. When you install the GPIB software, these files are copied into the Windows system directory (for example C:\Windows\System).
A Win16 application uses the 16-bit thunking DLL, gpib.dll, and the 32-bit thunking DLL, gpib32ft.dll, to access the GPIB driver. Figure 2 shows the interaction between a Win16 application and the GPIB software components.
Using the 16-bit GPIB Driver for Windows 3.x
The GPIB software for Windows 3.x is a standard 16-bit Windows Dynamic Link Library (DLL). This file is included with the GPIB software. When you install the GPIB software, it is copied into the Windows system directory (for example C:\Windows\System).
A Win16 application uses the 16-bit DLL, gpib.dll to access the GPIB driver. Figure 3 shows the interaction between a Win16 application and the GPIB software components.
5. Windows 3.x
The GPIB software for Windows 3.x is a standard 16-bit Windows Dynamic Link Library (DLL). This file is included with the GPIB software. When you install the GPIB software, it is copied into the Windows system directory (for example C:\Windows\System).
A Win16 application uses the 16-bit DLL, gpib.dll to access the GPIB driver. Figure 3 shows the interaction between a Win16 application and the GPIB software components.
