🚀 go-pugleaf

In article <1992Sep03.153802.688@Schultz.ON.CA>, peter@Schultz.ON.CA (Peter Roeser) writes:
|> Newsgroups: alt.msdos.programmer
|> Path: taco!rock!stanford.edu!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!torn!watserv2.uwaterloo.ca!watserv1!Schultz.ON.CA!peter
|> From: peter@Schultz.ON.CA (Peter Roeser)
|> Subject: Re: Trapping 386 IO port accesses
|> Message-ID: <1992Sep03.153802.688@Schultz.ON.CA>
|> Organization: S-S Technologies, Kitchener, ON
|> References: <1992Aug31.191659.672@Schultz.ON.CA> <1992Sep1.143350.10587@ncsu.edu> <tgreen.715391992@vincent2.iastate.edu>
|> Distribution: na
|> Date: Thu, 3 Sep 92 11:38:02 GMT+5:00
|> Lines: 22
|> 
|> In article <tgreen.715391992@vincent2.iastate.edu> tgreen@iastate.edu (Todd Greenfield) writes:
|> >
|> >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.
|> 
|> >
|> >I'd be interested in seeing what others think, and how one 
|> >would go about doing it, as I have a similar need.
|> 
|>   Let's keep the discussion going
|> 
|> 
|> -- 
|> Peter Roeser                 | peter@Schultz.ON.CA
|> S-S Technologies Inc.        | uunet.uu.net!watserv1.uwaterloo.ca!schultz!peter
|> 88 Ardelt Avenue             | voice: (519) 571-1434 x227
|> Kitchener, ON Canada N2C 2C9 | FAX:   (519) 743-3610
|> 

Hi.  Windows DOES trap I/O port accesses -- that's what *.386 virtual device
drivers are for.

Tschuess,
David Paschal