Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!unmvax!ariel.unm.edu!triton.unm.edu!keirje
From: keirje@triton.unm.edu (Keirje Aldranske)
Newsgroups: comp.os.msdos.apps
Subject: 4DOS memory problem, XMS
Message-ID: <1990Oct10.030914.27139@ariel.unm.edu>
Date: 10 Oct 90 03:09:14 GMT
Sender: news@ariel.unm.edu (USENET News System)
Organization: University of New Mexico, Albuquerque NM
Lines: 26

From keirje Tue Oct  9 18:22:38 1990
Subject: Re: 4DOS memory problem, XMS
To: toma%tekgvs.labs.tek.com@relay.cs.net
Date: Tue, 9 Oct 90 18:22:38 MDT
In-Reply-To: <9010091916.AA11681@tekgvs.LABS.TEK.COM>; from "toma%tekgvs.labs.tek.com@relay.cs.net" at Oct 9, 90 12:16 pm
X-Mailer: ELM [version 2.3 PL6]
Status: OR

> 
> Try running 4DOS telling it either not to swap or to swap to a disk file. Then
> It shouldn't be using any extended memory. I started using 4DOS before I got
> the new XMS driver, so I don't know how it works with command.com.
> 
> TOm
> 




   The problem is now understood :)  the XMS driver takes over all extended
 memory (almost just like EMS)  MSDOS (although I can't understand why) does
 not properly use the XMS driver.  It will not report the extended memory as
 being managed by XMS...  4DOS, however, does.  I am glad.  I do wish that
 the programs coming out today would use the standard thought (dang frustrating)

      thanks... Kay