From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Underwood Subject: Re: App database, libsynth Date: Sat, 12 Jul 2003 19:56:26 -0500 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <20030713005626.GR1031@dbz.icequake.net> References: <3F10A5F0.1030103@aknet.ru> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <3F10A5F0.1030103@aknet.ru> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-msdos@vger.kernel.org Hi Stas, On Sun, Jul 13, 2003 at 04:21:04AM +0400, Stas Sergeev wrote: > Hello. > > Ryan Underwood wrote: > >>That means that a potential future DOSEMU for it has to > >> run "real mode" 16bit apps emulated but can execute > >>DPMI apps natively. > >Are you certain about emulation necessary for 16bit apps? > Note the "real mode" in the quote above. > > >It goes on to say: "compatibility mode is enabled by the > >operating system on an individual code-segment basis. > >From the application's viewpoint, compatibility mode > >looks like a legacy x86 protected-mode environment." > Note the "protected-mode" in the quote above. > See? :) Okay, I gathered from "protected-mode environment" that it would be like a DOS box running under Win95, a protected mode environment. But they are saying that in this example, it would be Win95's view of the system, not the DOS program's view. So under longmode there will be no more vm86() and we will definitely need to use QEMU. So the "compatibility mode" is only good for running the 32-bit applications while in longmode. Correct? -- Ryan Underwood, , icq=10317253