From: dwarren@ghgcorp.com ("Douglas R. Warren") Subject: Re: B16 - Building NT device drivers 9 Nov 1996 09:40:01 -0800 Sender: daemon@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <3284BB52.251E.cygnus.gnu-win32@ghgcorp.com> References: <01BBCD86.020563C0@ppp258.enterprise.net> Reply-To: dwarren@ghgcorp.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01Gold (Macintosh; I; PPC) Original-To: "John D. Haughton" Original-CC: "'gnu-win32@cygnus.com'" Original-Sender: owner-gnu-win32@cygnus.com John D. Haughton wrote: > > Is it possible ? > > Has anyone done it ? > > Is it just a case of linking with the entry point set to _DriverEntry ? <...> John -- there's more to it than that for NT drivers. You need MS's DDK (driver dev kit) for all of the symbols. Drivers are a special 'kind' of thing, like a DLL only worse (special headers, req'd routines, etc.). They have a number of entry points, have several layers, and are expected to be thread-safe and portable between CPUs (they live on top of NTs Hardware Abstraction Layer). Also MS is making noises about changing NT and W95 driver models so they are the same -- the result will likely be closer to NT. I'm sure it can be done. And to those who will do it -- "you're a better than I, Gunga Dinn!". --Doug-- - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".