Article View: comp.sys.ibm.pc.programmer
Article #845Re: .SYS (device drivers) that are actually .EXEs?
From: Michael A. Shiels
Date: Wed, 04 Jul 1990 02:04
Date: Wed, 04 Jul 1990 02:04
13 lines
1189 bytes
1189 bytes
>It is also possible to create a plain old .EXE file program that can be >invoked from the command line that can install itself as a device driver. >To do this, it must find the device driver chain (via an undocumented >function call) and link a device driver header into it. The initialization >call will not be made, of course. If you need to write a device driver >in a high-level language (even <GASP> turdo pascal or <NOOOO!> basic), >this is your best bet. Most if not all of my drivers can use this technique already. What I had not even thought about was the ability to use a.EXE driver in the normal DEVICE= line. Most of not all the drivers I write are C with a small .ASM stub to get things going.
Technical Details
Message-ID:
<j92jl5cor@tmsoft.uucp>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!tmsoft!mshielsReferences:
<j8t1seef8@tmsoft.uucp> <141@qmsseq.imagen.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!tmsoft!mshiels From: mshiels@tmsoft.uucp (Michael A. Shiels) Newsgroups: comp.sys.ibm.pc.programmer Subject: Re: .SYS (device drivers) that are actually .EXEs? Message-ID: <j92jl5cor@tmsoft.uucp> Date: 4 Jul 90 02:04:19 GMT References: <j8t1seef8@tmsoft.uucp> <141@qmsseq.imagen.com> Reply-To: mshiels@tmsoft.UUCP (Michael A. Shiels) Organization: MaS Network Software and Consulting Lines: 13