Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!oliveb!stratus!gbs
From: gbs@stratus.UUCP (George B. Smith)
Newsgroups: comp.sys.ibm.pc
Subject: Re: device drivers
Message-ID: <1611@stratus.UUCP>
Date: 7 Feb 89 16:40:52 GMT
References: <6858@fluke.COM> <509@rpi.edu> <20044@agate.BERKELEY.EDU>
Reply-To: gbs@stratus.UUCP (George B. Smith)
Distribution: na
Organization: Stratus Computer, Inc. Western Development Center
Lines: 27

In article <20044@agate.BERKELEY.EDU> izumi@violet.berkeley.edu (Izumi Ohzawa) writes:
>In article <509@rpi.edu> fargo@pawl.rpi.edu (Ethan M. Young) writes:
>>I too am interested in writing device drivers in either Turbo C...
>I don't think you can write DOS Installable device drivers
>(those you install with DEVICE= ...  line in CONFIG.SYS) using
>Turbo C or Turbo Pascal or MSC.  I wouln't say never, but
>it sounds awfully difficult.
>...
>Izumi Ohzawa

Sorry to counterdict you, Izumi, but the latest issue of "The C Users
Journal", Feb. 1989 has an article by a Robert Allen titled "Writing
Device Drivers With Turbo C."  The first paragraph goes like this:

"I read with interest the article "Writing MS-DOS Device Drivers" by
Phipip J. Erdelsky in the V6/N7 of "The C Users Journal."  In the last
few years I have written three different device drivers for MS-DOS,
each to perform fully buffered serail communications.  The first driver
was written in assembly, the second was attempted in Lattice C v3.0, 
but it became so cumbersome I reverted to assembly.  Finally, on my
third attempt I found a compiler, Borland's Turbo-C, that makes the
writing of device drivers in C very simple."

George B. Smith
Stratus Computer, Inc
gbs@stratus.stratus.com
{amdahl,oliveb,uunet}!stratus!gbs