home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.msdos.programmer:10605 comp.sys.ibm.pc.programmer:583
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!zaphod.mps.ohio-state.edu!caen!uflorida!reef.cis.ufl.edu!ggh
- From: ggh@reef.cis.ufl.edu (Greg Huey - Aymer deGregory)
- Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.programmer
- Subject: MS-DOS in 386 protected mode
- Message-ID: <37619@uflorida.cis.ufl.edu>
- Date: 14 Nov 92 01:48:44 GMT
- Sender: news@uflorida.cis.ufl.edu
- Followup-To: comp.os.msdos.programmer
- Organization: Univ. of Florida CIS Dept.
- Lines: 23
- Nntp-Posting-Host: reef.cis.ufl.edu
-
-
- Im trying to write a 'bare-bones' multi-processing os for the 386.
- I dont wont to create my own dos, obviously I want to use MS-DOS...
- Question is, how do I do this in protected mode?
- Presumably, I create the GDT, LDTs, TSSs, IDTs, and the viarious gates...
- But no matter HOW I map virtual memory with the GDT, LDTs, I cannot make
- the virtual memory transparent, due to the priv bits and table indicator
- bit. I need to put the 386 in protected mode, but it has to look the
- same to MS-DOS, otherwise MS-DOS will fail, wont it? For instance, MS-DOS
- knows one of its buffer is at seg:offs -- when I put the 386 into protected
- mode, seg, rather than being a simple address, will now be treated as a
- selection index into the GDT or LDT.
-
- Is there some way (and how?) that I can get MS-DOS to work in the new
- protected mode once I make the switch from real mode to protected mode?
-
- Does anyone know of a ftp site or the like w/ detailed information on
- MS-DOS that might help me here?
-
- Many thanks
- Greg Huey
- ggh@reef.cis.ufl.edu
-
-