From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julius Schwartzenberg Subject: Re: DPMI errors on amd64, but not on i386 Date: Fri, 06 Feb 2009 22:10:27 +0100 Message-ID: <498CA743.3070604@zgod.cjb.net> References: <498C712B.1010203@zgod.cjb.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-msdos-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org Javier wrote: > Julius Schwartzenberg wrote: >> I'm getting similar results with DPMI on AMD64. According to dosemu.conf >> DMPI on AMD64 is experimental, so I guess this is to be expected. I have >> the same problem when CPUEMU is set to full though, so I guess the CPU >> emulation is also still experimental. > > Please note that I am using the 32-bit binary on both the x86_32 and 64 > kernel -- I've no knowledge about how dosemu works, but does it follow a > diferent code path on amd64 even if compiled for i386? (apart from > x86_64's missing vm86plus syscall). > Because of this, I initially believed I had misconfigured my kernel > build, but since I am also having problems with the default 64-bit Debian > kernel I guess not. I suspect the experimental limitation doesn't come from the 32 or 64 bit binary, but from the 64-bits kernel. I understand certain 16-bit mode things aren't possible when the system runs in 64-bit mode, so that's why the emulation is necessary for certain parts then. This emulation feature is still experimental.