Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdahl!pyramid!prls!philabs!ttidca!quad1!few
From: few@quad1.quad.com (Frank Whaley)
Newsgroups: comp.sys.ibm.pc
Subject: Re: device drivers
Message-ID: <1634@quad1.quad.com>
Date: 8 Feb 89 19:12:16 GMT
References: <6858@fluke.COM> <509@rpi.edu> <20044@agate.BERKELEY.EDU>
Reply-To: few@quad1.quad.com (Frank Whaley)
Distribution: na
Organization: Quadratron Systems, Westlake Village, CA
Lines: 36

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 am interested in writing device drivers in either Turbo C or Turbo Pascal
>>I have IBM's DOS Technical Reference Manual for DOS v3.00, but they only give
>>examples in assembly language.
>
>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.

Normally I just respond through the mail, but since this might be of
marginal net interest...

I wrote a package that allows you to develop Installable Device Drivers with
Turbo C (1.5 or 2.0).  It is available (as source) in a 30K 'shar' file
free for the asking.  I'll even add your name to my mailing list for future
updates, should I actually have any.

I used to support Lattice C and MSC, but now I'm a 'Turbo Guy'.  The C
Users Group in Kansas is still shipping the original version, I think.

I used to think this was difficult, but now it's not very impressive.  It
helps to understand the '86 architectures and the way DOS interacts with
Device Drivers.  A sample driver is included in the package (MONO.SYS, which
creates a device named MONO that controls a monochrome video adapter).

-- 
Frank Whaley
Senior Development Engineer
Quadratron Systems Incorporated
few@quad1.quad.com
uunet!ccicpg!quad1!few

Water separates the people of the world;
Wine unites them.