Date: Wed, 23 Apr 1997 11:10:40 +0800 (GMT)
From: Orlando Andico <orly AT gibson DOT eee DOT upd DOT edu DOT ph>
To: Mark Habersack <grendel AT hoth DOT amu DOT edu DOT pl>
cc: opendos AT delorie DOT com, djgpp AT delorie DOT com, opendos-developer AT delorie DOT com
Subject: Re: DOSemu again
In-Reply-To: <199704220938.LAA28533@math.amu.edu.pl>
Message-ID: <Pine.SGI.3.93.970423110748.998A-100000@gibson.eee.upd.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Tue, 22 Apr 1997, Mark Habersack wrote:

> Hi All,
> 
>   I haven't used DOSemu for DJGPP development so far, but recently I started 
> a project which uses several DOS utils compiled with DJGPP and I *do* need to 
> run it from DOSemu. I run DOSemu v0.63.1.6 with OpenDOS and everything seems 
> to work fine except for DJGPP applications (DPMI and XMS configured for 
> 16MB, no EMS and no other drivers) ;-(( Anyway, the situation is somewhat 
> strange:
[...]
> 
> Does anyone with longer DOSemu experience have any idea what might be wrong? 
> 
> P.S. I run Linux kernel v2.0.30

If you have kernel 2.0.30, why not upgrade to DOSemu 0.66.1? DOSemu
versions less than 0.66.1 use a kernel patch (or alternatively, a loadable
module) called VM86PLUS in order to support "full feature DOSemu," e.g. 
DPMI and company. kernel 2.0.28 (and up) also _have_ an upgraded vm86() 
call, so this f*cks up the vm86() code in DOSemu versions that expect the
VM86PLUS version. If you use 0.66.1 however, it is _aware_ of the kernel
enhanced vm86() syscall and uses that; in fact the kernel vm86() call was
integrated from the VM86PLUS supplied with older DOSemu releases. 


-----------------------------------------------------------------------
Orlando Andico                               IRC Lab/EE Dept/UP Diliman
email: orly AT gibson DOT eee DOT upd DOT edu DOT ph          http://gibson.eee.upd.edu.ph
   "There's an obvious attraction to the path of least resistance.."