Path: utzoo!attcan!utgpu!watserv1!watmath!maytag!mks.com!tslwat!louk From: louk@tslwat.UUCP (Lou Kates) Newsgroups: comp.sys.ibm.pc Subject: Re: memory driver Message-ID: <135@tslwat.UUCP> Date: 8 Feb 90 06:49:31 GMT References: <862@gator.usl.edu> <2825@cunixc.cc.columbia.edu> Reply-To: louk@tslwat.UUCP (Lou Kates) Organization: Teleride Sage, Ltd., Waterloo Lines: 15 In article <2825@cunixc.cc.columbia.edu> bmh@cunixd.cc.columbia.edu (Brian M Hoffman) writes: >In article <862@gator.usl.edu> pcb@gator.usl.edu (Peter C. Bahrs) writes: >>Does anyone know of a pd or $< package that will turn extended into >>expanded and provide an EMS 4.0 interface? > >The best way to do this is to get a commercial software EMS driver. Two good >packages are 386 to the Max and Qemm. Both of these will convert your extended >memory into expanded memory. I use Qemm regularly and have no problems. We have tried 386-to-the-Max and QEMM and 386-to-the-Max is significantly easier to use since it can figure out alot that you have to tell QEMM via command line items. In particular we were never able to figure out how to get QEMM to work on a DELL 386 laptop (it may work but we could not figure it out. We have used QEMM successfully on other machines) whereas we had no problem with 386-to-the-Max.