Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!bu.edu!bu-cs!lectroid!cloud9!jjmhome!m2c!umvlsi!umaecs!amh!tgoldin
From: TGOLDIN@amherst.bitnet
Newsgroups: comp.sys.ibm.pc
Subject: Re: 640K limit
Message-ID: <8940@amherst.bitnet>
Date: 16 Jan 90 23:49:05 GMT
References: <13346@garnet.BBN.COM> <580@watserv1.waterloo.edu> <948@philmtl.philips.ca>
Followup-To: comp.sys.ibm.pc
Lines: 15

In article <948@philmtl.philips.ca>, ray@philmtl.philips.ca (Ray Dunn) writes:
> In a recent article:
>>passed the 640K limit of DOS
> 
> I see this over and over again, and would like to try to put it to bed...
> 
> MSDos does *not* have a 640K limit, it has a 1Meg limit in its addressing.
> 
> 640K is only an artifact of the architecture of the PC which *normally* uses
> the memory map above 640K for RAM and ROM on option cards and BIOS.  

There is a software product called 386 MAX that will allow you to map extended
or expanded memory into the 640K to 1Meg range.  This is especially useful when
you have memory resident programs and drivers that are taking up too much of
the 640K conventional memory.