🚀 go-pugleaf

I did one with a DDK kit for Borland compilers that I 'think' came 
from NuMega.

I did a couple with the MS DDK but had to alter the headers so that 
they at least approximated legal C language.

For another I used the MS tools that come with the DDK.

Other than the drivers I used to climb the learning curve, the drivers 
were for a custom board I designed.  It contained three systems, data 
acquisition, computation and output.  I cannot expand further without 
violating a non-disclosure agreement.

The command line linker has an option to create a device driver. 
However I do not remember offhand what the option is and cannot find 
it in the BCB6 help on the linker.

I no longer have the DDK for Borland tools package so If I had to do a 
device driver today I probably use the MS tools that come with the 
DDK.  However I object to those people who make the all-encompasing 
statement that BCB cannot create a device driver.

Do not expect to create your first device driver in a day or two 
unless it is a 'toy' one that you create for the purpose of learning. 
The DDK documentation is obscure - typical MS docs, what they say is 
correct, but the way the information is organized and how things are 
worded seems to be arranged more to obfuscate than to enlighten.

.  Ed

> Gustav wrote in message
> news:42679c46@newsgroups.borland.com...
>
> You do not need to give us the whole code. Just give some hints;
>    * For what kind of device did you develop the driver ?
>    * Did you use MS's DDK with BCB?