Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!bionet!agate!sunkist.berkeley.edu!raymond
From: raymond@math.berkeley.edu (Raymond Chen)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Device Drivers in "C"
Keywords: device drivers
Message-ID: <1991Apr21.164027.9564@agate.berkeley.edu>
Date: 21 Apr 91 16:40:27 GMT
References: <702@toshais.UUCP>
Sender: root@agate.berkeley.edu (Charlie Root)
Reply-To: raymond@math.berkeley.edu (Raymond Chen)
Distribution: usa
Organization: U.C. Berkeley
Lines: 55
In-Reply-To: swonk@toshais.UUCP (Glen Swonk)
Originator: raymond@sunkist.berkeley.edu

In article <702@toshais.UUCP>, swonk@toshais (Glen Swonk) writes:
>Does anyone have references to or source for
>writing a MSDOS device driver in "C"?

The `books' file on the comp.sys.ibm.pc.misc archive contains a
rather long list of IBM PC reference books (and mini-reviews from
net.people).  Selected extracts:

@book{td:dos,
    author = "Terry R. Dettman",
    title = "{DOS} Programmer's Reference"
    publisher = "Que",
    address = {Carmel, IN},
    year = 1988,
    price = "$23",
    ISBN = "0-88022-327-8"
}
   "Lists almost any interrupt a guy could want."

   [In response to a question about writing a device driver]
   "I recommend reading chapter 12." -- Neal A. Belair (nab@sppy00.UUCP)

@book{rd:dos,
    author = "Ray Duncan",
    title = "Advanced {MS-DOS} Programming",
    publisher = {Microsoft Press}
    price = "$25",
}
   "I strongly recommend the Advanced DOS guide from Microsoft Press.  It's
    very informative."

   "... very good if you are either writing in C or Assembly language.
    In section one, he covers many areas such as keyboard/mouse input,
    video display, printer and serial ports, file management, disk
    directories, memory management, interrupt handlers, device drivers,
    filters and compatibility. He discribes the concepts and gives source
    code (C and assembler) to be used as an example.  In sections 2, 3 and
    4 describes all the DOS function calls. He gives all inputs and outputs,
    and gives examples. There are also notes. These give you an idea of what
    and how DOS does things as well as things to watch out for. His second
    edition is current through DOS version 4.0."
                -- Mark Kallas (mkallas@digi.lonestar.org)

@book{rl:device,
    author = "Robert S. Lai",
    title = "Writing {MS-DOS} Device Drivers",
    publisher = {Addison-Wesley},
    ISBN = "0-201-13185-4",
}
   "Lots of examples in assembly language."
   "Recommended highly."

   "Examples include Console, Printer, Clock, RAM Disk, and 
    a `Complete Full-function Device Driver'.  Chapter on debugging.
    Diskette available."