🚀 go-pugleaf

I have an application that I'm porting to Windows 3.0 that monitors and
analyzes incoming data.  The data is not gathered via RS-232 and requires
special hardware and a device driver.  I've been through the Microsoft SDK
documentation and there appears to be no documentation on this, directly.
There are references to the communications functions which probably don't
fit the bill.  I saw a neat $500 price tag for a device driver SDK, but
I was hoping this applied to DC-type device drivers.

My question is: How do I interface my application to a real MS-DOS device
driver.  If this is hard or wrong I could port the driver to a Windows
driver, but then, what is it supposed to look like, etc?  What is the
environmental relationship between the application and the driver?
In other words, what context is the driver called in, how many I/Os can
go on concurrently, etc?

I'm willing to buy a book to answer these questions if one exists that
deals with these kinds of issues.

	Thanks, Dave