On (31 May 97) Bo Lorentsen wrote to Jerry Coffin...
 BL> Hello Jerry ...
Hello,
 BL> Ok, the only reason why I like to use the Watcom is because its my
 BL> main compiler and I know how it work and what kind of code it
 BL> generate.
Sounds reasonable.
 BL> What kind og EXE format dos these drivers use ???
Basically a normal PE file, the same as any other executable for NT.
However, it doesn't export its functions in the usual way - if you use a
PE file dumper on a device driver, with most device drivers you'll get
told that there are no functions exported at all.
 BL> Thanks, in the meantime I have found a book written by Art Baker "The
 BL> Windows NT device driver book (a guide for programmers", I hope this
 BL> will create a shortcut for my driver writting, so i hope you are wrong
 BL> :-)
Ah, good.  I'd heard rumors of a book being written, but hadn't actually
seen it in any stores yet.  I'll be interested in hearing how things go
with it.
[ talking about the type of device involved ]
 BL> Its a kind of a parallel port, spesial modifyed for a EProm emulator.
Hmm...that should be a fairly easy one - there's definitely code for
driving a normal parallel port in the DDK.
 JC> If you decide to use the MS compiler, you _might_ also want
 JC> to check out a device driver Wizard somebody wrote a while
 JC> back.  Basically it will automatically create the skeleton
 JC> of a driver for you, which does help out considerably at
 JC> getting started at things.
 BL> Thanks for the hint, where can i find this Wizard ?
It's definitely on MSDN, and should be on MS' web/ftp sites, though I
don't know the filename offhand.  It was written up late last year (or
thereabouts) in MSJ, so it should be with the code from other MSJ
articles...
    Later,
    Jerry.
... The Universe is a figment of its own imagination.
--- PPoint 1.90
---------------