faq	Windows driver

The message was:
I'd like to get updated on what exactly is required to get the PCL board running.

If you want to support all Windows plattforms, you need:

AvPcl32.dll
pcl-pci.inf
Setup.exe
wd_virtual.inf
windrvr.sys

Setup.exe is only needed with Windows NT 4.0

We have an installation package that installs the drivers. We currently include

avpcl32.dll
windrvr.sys
wdusb.sys

and in registry we write in parameters in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\windrvr

Starting with version 3.20 of the PCL-PCI driver, wdusb.sys (and the later added wdpnp.sys) are no longer needed.

Why do you modify the registry manually? This is not needed. Everything what has to be done to install the driver is managed by Windows, plug-and-play and our pcl-pci.inf. Only Windows NT 4.0, what is not PnP capable, needs the help of Setup.exe, but the work is managed by pcl-pci.inf, too. The source code of Setup.exe is included with the SDK. You may integrate it to your own setup program.

What about driver for the ISA board, is it the same driver?

No, the ISA driver is completely different. It doesn't use WinDriver, and it doesn't suppert PnP (of course, the PCL-ISA doesn't support PnP as well). With Windows 95/98/ME only avplc32.dll (that one from the win32 directory of the ISA driver disk) is needed, there is no Registry entry. With Windows NT/2000 (and probably XP, but it's not tested), avpcl32.dll, avpclnt.sys and Setup.exe are needed (all files (this time from the winnt directory), and there is a registry entry to set the I/O base address.