🚀 go-pugleaf

In article <tgreen.715550500@pv0547.vincent.iastate.edu> tgreen@iastate.edu (Todd Greenfield) writes:
>In <1992Sep03.153802.688@Schultz.ON.CA> peter@Schultz.ON.CA (Peter Roeser) writes:
>
>>In article <tgreen.715391992@vincent2.iastate.edu> tgreen@iastate.edu
>(Todd Greenfield) writes:
>[ original discussion of need to trap access to IO port deleted ]
>>>
>>>what about doing this under windows?  I know nothing of windows
>>>programming,  but wouldn't it be possible to write a windows
>>>driver (for 386 enh mode of course) to do something like this?
>
>>  I have been told that although Windows uses protected mode to do
>>  memory management( ie. traps when you talk to non-available mem.)
>>  it does not trap IO references.
>
.
.
.
>>  Let's keep the discussion going
>
OK,

You can write what is called a virtual device driver, which will allow
you to trap references to a given port from a DOS session. I'm not sure
if you can trap references from windows apps. Anybody know what IOPL is
for 386 Enhanced mode, and what privilege level windows apps run at?

Documentation can be found in the windows DDK. (Which I don't have
handy, or I'd look it up myself) and in Daniel Norton's Writing
Device Drivers for Windows.

Tom Hill

A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Windows Device Drivers.