🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.msdos.programmer
Article #350

Re: Trapping 386 IO port accesses

#350
From: DAVID SCOTT PASCHAL
Date: Tue, 01 Sep 1992 14:33
18 lines
1454 bytes
Hi.  The 386 and better can be set up to generate a general protection fault
when a process does an IN or OUT to a specific I/O port based on an I/O
permission bitmap in the Task State Segment, but this only works in protected
mode where there are TSS's, not in real mode in which MS-DOS operates.  I
guess you could write a little (not!) DOS extender that runs DOS in V86 mode
(which is really a real mode process running within protected mode which is how
Windows multitasks DOS applications in 386-Enhanced mode), but this would be
extremely difficult to design properly to handle BIOS interrupts and DMA.

Simulating interrupts would be pretty easy to do in real mode -- in your
"custom" interrupt handler, just call any interrupt handler you want.

Since this is your "own custom hardware", why don't you just simulate these I/O
ports in your adapter?

Tschuess,
David Paschal
Technical Details
Message-ID: <1992Sep1.143350.10587@ncsu.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rock!taco!dspascha
References: <1992Aug31.191659.672@Schultz.ON.CA>

Show Full Headers
Complete Article Headers
Newsgroups: alt.msdos.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rock!taco!dspascha
From: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Subject: Re: Trapping 386 IO port accesses
Message-ID: <1992Sep1.143350.10587@ncsu.edu>
Originator: dspascha@c00075-100lez.eos.ncsu.edu
Lines: 18
Sender: news@ncsu.edu (USENET News System)
Reply-To: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Organization: North Carolina State University, Project Eos
References:  <1992Aug31.191659.672@Schultz.ON.CA>
Distribution: na
Date: Tue, 1 Sep 1992 14:33:50 GMT