
Windows 95/98
In Windows 95 and Windows 98, you can use the 16-bit or the 32-bit driver: it is also possible to access the
ADC-100 directly.
It is necessary to use the driver that matches the application. The following applications require 16-bit driver:
Visual Basic 3
Excel 5
Delphi 1
Microsoft C version 1.5
Borland C 4
The following applications require 32-bit driver:
Visual Basic 4 and above
Excel 7 and above
Delphi 2 and above
Borland C 5
Microsoft C version 2 and above.
LabVIEW version 4 and above
The 16-bit and 32-bit drivers do not interfere with each other, so it is possible to install both drivers on the
same system, as long as, for any given unit, only one driver is using it at once.
The Borland C 4 and above the Watcom C 10 and above compilers can produce either 16-bit or 32-bit
applications.
When running under Windows 95, an application is not in complete control- Windows can interrupt at any time.
Interruptions occur every 55 milliseconds, and are also caused by mouse and keyboard input. As a
consequence, the driver cannot always take readings at fixed time intervals. To deal with this, the driver
returns the time at which each reading was taken. Generally speaking, the 16-bit driver gives higher sampling
rates, but the 32-bit driver is less prone to large gaps in the data.
The Windows 95 32-bit driver, PICO.VXD, is installed in windows\system,
It is loaded using a reference in
system.ini:
[386enh]
......
.....
device=pico.VXD
The Windows 95 32-bit driver is accessed using the file
ADC10032.DLL
: it is installed in
drivers\win32
.
The
DLL uses STDCALL linkage conventions, and undecorated names.
The 32-bit DLLs for Windows 95 and Windows NT use the same calling conventions, so a 32-bit application will
run without modifications on either system. Note, however, that the two operating systems require different
versions of the DLL file.