Path: utzoo!utgpu!jarvis.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!maccs!cs4g6ag
From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: weakness in the LIM EMS 4.0 spec
Message-ID: <25CB80EC.26768@maccs.dcss.mcmaster.ca>
Date: 4 Feb 90 01:10:03 GMT
References: <28980@amdcad.AMD.COM> <25C87DEC.22918@maccs.dcss.mcmaster.ca> <1570@mipos3.intel.com>
Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Organization: McMaster University, Hamilton, Ontario
Lines: 27

In article <1570@mipos3.intel.com> mwilcox@pcocd2.UUCP (Mike Wilcox ) writes:
$What it doesn't explain is why paradox 3.0 won't load with ems40.sys
$loaded. I have a 10Mhz 286 with 1 meg on the Motherboard and 2 3Megs add
$in cards as exTENded memory. Can't set them for expanded. Anyway Paradox
$3.0 just freezes the whole system (have to hard reset) if ems40.sys id
$loaded. Doesn't even show the opening screen.

   EMS40.SYS seems to be incompatible with some software or combinations
of software.  Last summer, I tried using it on a couple of machines on
a network.  We were using a special network printing utility (Network
Assistant Plus) which would use 64K of EMS, if you had it, to store its
overlays; otherwise, it would have to load them from the server every
time you wanted them.

   Anyway, EMS40.SYS and NAP worked fine together; EMS40.SYS and Symphony
worked fine (though rather slowly) together.  However, if we tried
using both at the same time, the machine would hang.

   I never found out what the problem was; NAP and Symphony coexisted
beautifully on other machines with proper EMS 3.2 or 4.0, and I
never found anything else that we used that would not run with
EMS40.SYS.
-- 
Stephen M. Dunn                               cs4g6ag@maccs.dcss.mcmaster.ca
          <std_disclaimer.h> = "\nI'm only an undergraduate!!!\n";
****************************************************************************
       "I want to look at life - In the available light" - Neil Peart