This one should be getting close.  The second release candidate
version of EMM386 with VCPI support is available at
ftp://ftp.devoresoftware.com/downloads in the files EMM386.ZIP and
EMM386SR.ZIP, as executable and ASM+C source.  They are dated March
27, 2004.

This version of EMM386 corrects incompatibilities with: NIOS; the
latest version of PC Config; the most recent release of SLOWDOWN; and
Lemmings 3d.

The above corrections were all different and doubtless affect other
programs as well, so if you've had past problems with EMM386, please
try this version and post if and where any problems remain.  A good
tip for testing with a problem is to try the failing application both
with and without EMM386 loaded to see if the problem only occurs under
EMM386 and not in a pure HIMEM environment.  Otherwise something else
in software or hardware might be causing the error.

Details, details, details:

NIOS should now successfully load, without any of previously
documented EMS setting restrictions.  It may even work.  Prior
versions of EMM386 used the 24-bit mode of LGDT and LIDT when V86->PM
switching so that a program such as NIOS which used linear addresses
above the 4M range for a new GDT or LDT would misbehave quite badly.

SLOWDOWN used the WBINVD instruction which is illegal in V86 mode.
Emulation for that instruction has been added to EMM386.

PC Config used the mov dr7,eax instruction which is illegal in V86
mode.  Emulation for that instruction has been added to EMM386.

There was a nasty bug in the EMM386's support for EMS 4.0 function
50h, map multiple pages, where it looked in the wrong memory location
for the pages to map.  Oops.  The fix allows Lemmings 3D to run
properly on my machine.


--

At 05:16 PM 3/27/2004 -0600, Michael Devore wrote:

>>NIOS should now successfully load, without any of previously documented EMS
>>setting restrictions.  It may even work.  Prior versions of EMM386 used the
>>24-bit mode of LGDT and LIDT when V86->PM switching so that a program such
>>as NIOS which used linear addresses above the 4M range for a new GDT or LDT
>>would misbehave quite badly.


Hmm, that's supposed to be above the 16M range not 4M, I'm betting, what
24-bit being 16M and with 80286's supporting up to 16M in protected mode.