Hello Jerry ...
 JC> The majority of NT device drivers are written in C or C++,
 JC> and doing so is no major problem.  All the NT drivers I've
 JC> written were in C++. However, I've never attempted to use
 JC> Watcom for the purpose - nearly the only documentation on
 JC> the subject comes directly from Microsoft, so it assumes
 JC> that you'll use Microsoft's compiler as well.  Offhand I
 JC> can't think of any reason you couldn't use a different
 JC> compiler, but doing so may make your life more difficult.
Ok, the only reason why I like to use the Watcom is because its my main 
compiler and I know how it work and what kind of code it generate.
What kind og EXE format dos these drivers use ???
 JC> Nearly the only documentation on NT device drivers is in
 JC> MSDN
 JC> Professional (or above.)  All you have to do is install the DDK and
 JC> spend the next three months or so reading the online
 JC> documentation. 
Thanks, in the meantime I have found a book written by Art Baker "The Windows 
NT device driver book (a guide for programmers", I hope this will create a 
shortcut for my driver writting, so i hope you are wrong :-)
 JC> With a little luck your driver will be extremely similar to
 JC> one of the samples MS provides so you can simply modify what
 JC> they send, and make it do the job for you.
Its a kind of a parallel port, spesial modifyed for a EProm emulator.
 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.
Thanks for the hint, where can i find this Wizard ?
/BL
---
---------------