Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!zaphod.mps.ohio-state.edu!samsung!uunet!saxony!dgil
From: dgil@pa.reuter.COM (Dave Gillett)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: In praise of QEMM-386
Message-ID: <691@saxony.pa.reuter.COM>
Date: 29 Jan 91 18:46:19 GMT
References: <3981@stl.stc.co.uk> <valley.665103177@gsbsun>
Distribution: na
Organization: Reuter:file Inc  (A Reuter Company) Palo Alto, CA
Lines: 26

In <valley.665103177@gsbsun> valley@uchicago (Doug Dougherty) writes:

|	Given that programs often need much more space to load than they
|	leave resident, it should be possible to load them in such a way
|	that even though there isn't enough High Ram available for their
|	load image, if there is enough available for their TSR image,
|	all is well.  I.e., 386MAX supposedly (haven't seen it up close
|	and personal) allows you to temporarily deactivate the EMS page
|	frame, so that a TSR can load part of its run time image there.
|	I.e., suppose your TSR requires 40K to load, but only 17K resident.
|	Further, suppose that the only remaining slot of High Ram starts
|	at D800:0 and the EMS page frame is at E000:0.

|	Would QEMM allow you to load your TSR high?  If so, how?

|ndh@stl.stc.co.uk (Neale D Hind ) writes:

|>o   When trying to maximise the number of Devices/TSR's in high memory,
|>    try swapping around the order in which they are loaded in your
|>    config.sys and autoexec.bat files.


     It seems to me that the "easy" solution is to load TSRs that need big
load areas but small resident areas *first*, so that TSRs with smaller load
areas don't produce this problem.
                                                Dave