Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!hub.ucsb.edu!amadeus!grosen
From: grosen@amadeus.ucsb.edu (Mark D. Grosen)
Newsgroups: comp.windows.ms
Subject: Re: Device Driver Development
Keywords: SDK,DDDK
Message-ID: <5941@hub.ucsb.edu>
Date: 12 Jul 90 03:37:28 GMT
References: <34@sgtech.UUCP> <55766@microsoft.UUCP>
Sender: news@hub.ucsb.edu
Reply-To: grosen@amadeus.UUCP (Mark D. Grosen)
Distribution: usa
Organization: University of California, Santa Barbara
Lines: 30

In article <55766@microsoft.UUCP> bobt@microsoft.UUCP (Bob TANIGUCHI) writes:
>In the past, the DDK and win/386 kits dependant upon tools not contained
>in the SDK, i.e. special linker versions, etc.  However, today this is 
>not the case.  Contained in the Windows 3.0 SDK is a fulfillment card for
>the DDK, and for the OS/2 SMK (Software Migration Kit).  
>
>The new DDK contains all you'll need to do either Win 3.0 drivers and
>VDD's as well.
>
>Bob Taniguchi
>Advanced Operating Systems Group
>Microsoft


How much device driver development can you do without the DDK?  I would like
to do a very simple interrupt routine that simply PostMessage()'s a message
to the (one and only one) application that will be using the driver.  I know
that PostMessage() is ok, as described in the DLL chapter of the "Guide to
Programming".  What are things do I need to watch out for/be careful of?  Is
there a function in the SPI to install an interrupt handler?

Thanks for any info.

Mark

Mark D. Grosen		ARPA: grosen@amadeus.ucsb.edu
Signal Processing Lab / Communications Research Lab
ECE Dept.
University of California
Santa Barbara, CA  93106