Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!news.cs.indiana.edu!cs.widener.edu!netnews.upenn.edu!rm105serve.sas.upenn.edu!theall From: theall@rm105serve.sas.upenn.edu (George A. Theall) Newsgroups: comp.os.msdos.apps Subject: Re: QEMM, etc Recommendation Sought Summary: what QEMM uses Keywords: loadhi, qemm, extended, expanded Message-ID: <39661@netnews.upenn.edu> Date: 23 Mar 91 02:05:30 GMT References: <1991Mar21.173016.27609@ssd.kodak.com> Sender: news@netnews.upenn.edu Organization: University of Pennsylvania Lines: 26 Nntp-Posting-Host: rm105serve.sas.upenn.edu In article ersys!davem@nro.cs.athabascau.ca (Dave McCrady) writes: >wieser@bissun.kodak.com (Jim Wieser) writes: >> I have a 386 machine and use PC-NFS over ethernet to > Having said all that .. I guess the short answer to your question is >yes ... IF your machine has expanded memory. Extended memory can't be >mapped to high ram. For those with 386s (386SX and 486s too) QEMM lets users convert extended memory to expanded memory. A portion of this expanded memory can then be mapped into unused areas between 640K and 1MB with LOADHI, distributed along with QEMM-386. When QEMM does this it forces the CPU into V86 mode. In sum, physical extended memory --> simulated expanded memory --> high memory. George --- theall@rm105serve.sas.upenn.edu Dept. of Economics theall@ssctemp.sas.upenn.edu Univ. of Pennsylvania gtheall@penndrls.upenn.edu Philadelphia, PA 19104