"DOS Guy" <D...@Guy.com> wrote in message news:50AE315B...@Guy.com...
> Microsoft has issued some updates recently (KB2724197) that prohibit
> the use of EMS memory for 16-bit applications in Windows XP SP3.
There is a thread on the issue here:
It's not all that informative, IMO.
This link to EMS Magic was posted in a response by Rugxulo:
> I was wondering if there's a way to know if any given
> 16-bit app uses EMS.
Do you mean uses *only* EMS?
Personally, I'd be a bit surprised if you find an EMS-only application
anymore. For RM MS-DOS, I haven't had an EMS provider installed for many
years ... It's likely that any EMS applications that are still in use, are
still in use because they can also use XMS, DPMI, or VCPI instead of EMS.
Will MS-DOS warn that no EMS is available if starting an
EMS-only application? Anyone know? Or, is it the application that
warns if it needs EMS and can't get any?
I'd think that you'd want an EMS host that can be directed to emit
diagnostic messages ... or a TSR that detects EMS calls and displays
> What are the distinguishing characteristics of such apps?
> Lots of memory use?
Most likely they were written for the 286 ... I doubt that helps any.
Japheth's Jemm readme says it includes his EMSSTAT.
I doubt that helps much either. It can be used to tell you if EMS is
available. I.e., REM out your EMS provider in config.sys or autoexec.bat.
Re-boot. Use EMSSTAT to tell you that no EMS is available. Then, execute
or run your application. If it truly is EMS-only, then hopefully either the
application or DOS will warn that there is no EMS.