
Windows NT/2000
The Windows NT/2000 driver, PICO.SYS, is installed in windows\system32\drivers. The operating system
must be told that the driver is available: this is normally done automatically by the setup program, but can
also be done manually using the the regdrive.exe program which is copied into the PICO directory. Type in
regdrive pico
The Windows NT 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.
C
DOS
To link the driver into you program, you should take the following steps:
#include
the header file
adc100.h
into your program
If you are using an IDE, include the file
adc100drv.obj
in you project.
If you are using a command-line compiler, include the file
adc100drv.obj
in you linkfile.
See
adc100b.c
for an example of a simple DOS program which uses the driver.
C / C++ (Windows)
C
The C example program is a generic windows application- ie it does not use Borland AppExpert or Microsoft
AppWizard. To compile the program, create a new project for an Application containing the following files:
a100test.c
a100test.rc
either adc10016.lib (All 16-bit applications)
or
adc10032.lib (Borland 32-bit applications)
or
adc100ms.lib (Microsoft Visual C 32-bit applications)
The following files must be in the same directory:
a100test.rch
adc100w.h
either adc10016.dll (All 16-bit applications)
or
adc10032.dll (All 32-bit applications)
C++
C++ programs can access all versions of the driver. If adc100.h or adc100w.h are included in a C++ program,
the PREF1 macro expands to
extern “C”
: this disables name-mangling (or decoration, as Microsoft call it),
and enables C++ routines to make calls to the driver routines using C headers.