Re: Communicating With Resident Programs

Article View: comp.os.msdos.programmer

Article #2512

Back to comp.os.msdos.programmer Previous Next

#2512

From: Ned Snow
Date: Wed, 03 Oct 1990 06:32

14 lines
1185 bytes

In article <679@digigw.digital.co.jp> gday@digigw.digital.co.jp (Gordon Day) writes:
>Could somebody suggest the best way to communicate with a driver?  I have 
>successfully implemented a block device driver, but I am at a loss as to the
>best way to communicate with it from a transient program.  I have come up 
>
When I implemented a device driver ( to deal with serial input in a C program)
I used the ioctl functions to communicate with it. To do this, you must set
the ioctl bit in the device header, and provide code for the ioctl input
and output functions ( 3 for input, 12 for output ). The transient program
can then use dos function 44h to send/receive strings to/from the driver.

>Gordon W. Day

Ned

Technical Details

Message-ID: <2337@runxtsa.runx.oz.au>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!metro!ipso!runxtsa!snow

References: <679@digigw.digital.co.jp>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!metro!ipso!runxtsa!snow
From: snow@runxtsa.runx.oz.au (Ned Snow)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Communicating With Resident Programs
Keywords: driver, TSR, interrupt vectors
Message-ID: <2337@runxtsa.runx.oz.au>
Date: 3 Oct 90 06:32:03 GMT
References: <679@digigw.digital.co.jp>
Organization: RUNX Unix Timeshare.  Sydney, Australia.
Lines: 14

Reply to Parent Message