Date: Tue, 21 Jan 1997 21:48:32 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: "Mike A. Harris" <mharris AT sympatico DOT ca>
cc: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] Re: OpenDOS to be released next week! (fwd)
In-Reply-To: <Pine.LNX.3.95.970120204703.10523G-100000@capslock.com>
Message-ID: <Pine.GSO.3.95.970121214426.19563C-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Mon, 20 Jan 1997, Mike A. Harris wrote:
> On Mon, 20 Jan 1997, Gene Buckle wrote:
> Well, I've got 634k with QEMM and I've got all my drivers (a lot of them)
> loaded into UMB's and I've got the HMA reserved for DESQview so DOS loads
> into UMB's instead of high.  It gives me more mem that way.  But after I
> got the CD-ROM, and UniVBE, and a couple other new drivers that are
> needed, my memory has shrunk down again.  I loaded into the HMA now, cause
> I don't really use DV anymore, but MSCDEX REFUSES to load HIGH!!!!!!!!
> I've got 64k of contiguous UMB memory and MSCDEX is only using 12k!  It
> WONT load into UMB's!  However if I unload a few other drivers, then
> MSCDEX will load HIGH. I guess it needs like a meg of startup memory or
> something before it shrinks to 12k.  Also QEMM has the VIDRAM program

Change the driver loading order, sometimes a driver requires more space to
set itself up before loading, I think MSCDEX is one of them.  It's got
several "overlay's" embedded into it, when it loads, it reads it command
lines, checks out the hardware, then sets the driver up.  A lot of
'generic application' drivers are like that.

(generic application:  A driver which will support several different types
of hardware configurations.)