Uploaded to ftp://ftp.devoresoftware.com/downloads are the files
emm386.zip (uncompressed executable) and emm386sr.zip (revised source
code) for EMM386.

This relatively minor update adds an SB option, adds silent
recognition to the bare RAM option, and restores the VDS experimental
option for those who can use it in its current skeletal condition.

The SB option can be used in conjunction with SoundBlaster drivers
which were enabled by the last EMM386 change.  The SoundBlaster
drivers hook EMM386's interrupt descriptor table, as well as its GDT
(per previous release remarks) and redirect all INT 3's (debug
interrupt) to a general protection fault with error code 1ah IF an
application is running in virtual 8086 mode.  As a result, any
attempts to run an application under a debugger with the SoundBlaster
drivers loaded will fail with a GPF.  Further, applications such as
NEWDES, which intersperse their code with normally benign INT 3's will
fail with a GPF.  To work around this problem,  the SB option
redirects GPFs with error code 1ah to INT 3.  This allows normal
debugging and NEWDES execution if the SoundBlaster drivers are
loaded.  Hopefully there are not a number of SoundBlaster versions out
there which use different GPF error codes.

Why do the SoundBlaster drivers do this?  No idea, in the absence of a
SoundBlaster developer here to interrogate, the code I traced the
problem to just looks really stupid.

In addition, by popular request, EMM386 will parse the RAM option, but
do nothing, since it already behaves as if RAM were present.  A
RAM=xxxx-xxxx option will continue to kick out a warning message.
Also, the VDS #define previously commented out was returned for those
few intrepid souls who want to use it.

Finally, I request that anyone who has a problem with any application
crashing while HIMEM or EMM386 is loaded, where the problem occurs
only when those drivers are loaded, let me know a link I can download
the application for testing, or send it to me directly.  If the
application only requires a few minutes to setup and doesn't require a
specific hardware setup not available, I will test it.  Otherwise, I
won't.  Nor will I fill out nosy detailed web forms to get a download
access code.  Because I'm a grump.

Following is my open list of applications which remain problematic:

 Lynx -- too much time and complicated for me to set up and get going
 in a reasonable amount of time.  I tried, I failed.  Maybe in the
 future.

 Microsoft Virtual PC -- no time to download, setup, and look at it
 yet.  Preliminary looks are that it's complicated and time-consuming
 to get going for lazy people like me.  Maybe later.

 GEOS Ensemble Lite -- incompatible with FreeDOS kernel, despite the
 guy posting around UseNet who says it's an EMS incompatibility.  Hey
 man, it's not.

 Microsoft Diagnostic msd.exe included with Win 3.1 distribution --
 memory-oriented options incompatible with kernel, possibly related to
 list of lists call and/or undocumented internals.

If you want to add to an application to this problem list, so I can
try to take it off the list, please let me know.


-Micheal Devore