Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!manuel!csc.canberra.edu.au!news From: act@softserver.canberra.edu.au (Andrew Turner) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: DOS 5 and memory management Message-ID: <1991Jun18.013604.22276@csc.canberra.edu.au> Date: 18 Jun 91 01:36:04 GMT References: Sender: news@csc.canberra.edu.au Organization: University of Canberra Lines: 24 In article cb@tamarack12.timbuk (Chris Brewster) writes: > >Since the new DOS has paging and task switching, I'm unclear on what is still >needed from a memory manager. Is QEMM or MAX still useful? > At a pre-release presentation a Microsoft type stated that QEMM is viable and useful under DOS 5, MAX not mentioned. He said that although DOS 5 had the ability to load stuff high that the features of QEMM were more sophisticated. QEMM's optimise does all the hard work of figuring out the best fit for stuff to load high. It seems that you have to do a little of your own figuring out with DOS 5 - the MEM command helps with this and has new features since DOS 4. NB That you can only load one thing into each vacant spot in upper memory. So don't stick a 5k device driver into a 64k hole. Another opinion given by a more-than-happy beta tester was that he preferred to use DOS 5's memory management features as they were all part of DOS 5 - if you get my drift. I suppose if you,ve paid for QEMM certainly use it, but if you don't own a copy then certainly give DOS 5's memory management a good shake. -- Andrew Turner act@csc.canberra.edu.au Die, v: To stop sinning suddenly. -- Elbert Hubbard