Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!usc!julius.cs.uiuc.edu!rpi!uwm.edu!linac!midway!valley From: valley@uchicago (Doug Dougherty) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: In praise of QEMM-386 Message-ID: Date: 30 Jan 91 23:38:28 GMT References: <3981@stl.stc.co.uk> <691@saxony.pa.reuter.COM> Sender: news@midway.uchicago.edu (News Administrator) Distribution: na Organization: University of Chicago Lines: 31 dgil@pa.reuter.COM (Dave Gillett) writes: >In 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 Yes. Unfortunately, all of my TSRs exhibit the pathology (of taking up much more space to load than to be resident)