home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!news.univie.ac.at!chx400!bernina!almesber
- From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
- Subject: Re: DOS emulation
- Message-ID: <1993Jan7.184329.8050@bernina.ethz.ch>
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
- References: <79132@hydra.gatech.EDU> <1993Jan5.174435.3669@wam.umd.edu>
- Date: Thu, 7 Jan 1993 18:43:29 GMT
- Lines: 25
-
- In article <1993Jan5.174435.3669@wam.umd.edu> joel@wam.umd.edu (Joel M. Hoffman) writes:
- > I see two possibilities: One, giving the DOS program full control of
- > the screen, for SVGA graphics. The program could do whatever it
- > wanted, and so the VC code would have to be augmented to save/restore
- > the complete state of the video card. This would be a good thing,
- [...]
- > The only problem with this approach is that I don't think
- > graphics programs could run in the background.
-
- If you mean "detaching from a display", why not ? It's not necessarily
- different from switching a VC. VCs aren't things that really exist in
- hardware either.
-
- If you mean "switching to a different VC", why not ? The display memory
- could be mapped to the physical frame buffer while the respective VC is
- in the "foreground" which is copied to a buffer in user space when
- switching to a different VC. Now, that buffer memory could be mapped to
- the display memory and the DOS program could happily continue to
- scribble to what it thinks is its screen. It would even run faster ;-)
-
- - Werner
- --
- _________________________________________________________________________
- / Werner Almesberger, ETH Zuerich, CH almesber@nessie.cs.id.ethz.ch /
- /_IFW_A44__Tel._+41_1_254_7213___________________________________________/
-