Article View: comp.os.msdos.programmer
Article #2464Re: Communicating With Resident Programs
From: Edward John Kalenda
Date: Tue, 02 Oct 1990 01:53
Date: Tue, 02 Oct 1990 01:53
12 lines
996 bytes
996 bytes
Gordon W. 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 > with three ideas, both with advantages and disadvantages: The best way is to use the generic ioctl function. INT 21h, function 44h, sub-function 0Dh allows your application to send and receive driver specific messages. Page 466 of the MS-DOS Encyclodedia talks about it. Ed ekalenda@cup.portal.com
Technical Details
Message-ID:
<34438@cup.portal.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!julius.cs.uiuc.edu!apple!portal!cup.portal.com!ekalendaReferences:
<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!wuarchive!julius.cs.uiuc.edu!apple!portal!cup.portal.com!ekalenda From: ekalenda@cup.portal.com (Edward John Kalenda) Newsgroups: comp.os.msdos.programmer Subject: Re: Communicating With Resident Programs Message-ID: <34438@cup.portal.com> Date: 2 Oct 90 01:53:09 GMT References: <679@digigw.digital.co.jp> Organization: The Portal System (TM) Lines: 12