home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.misc
- Path: sparky!uunet!microsoft!hexnut!jenk
- From: jenk@microsoft.com (Jen Kilmer)
- Subject: Re: Is dos 6.0 gonna multitask? Or have no memory barrier????
- Message-ID: <1992Nov13.065801.22564@microsoft.com>
- Date: 13 Nov 92 06:58:01 GMT
- Organization: Microsoft Corporation
- References: <1992Nov10.174211.1@csc.canterbury.ac.nz> <1992Nov10.060504.10390@netcom.com> <BxKoEC.JC8@news.cso.uiuc.edu>
- Lines: 43
-
- In article <BxKoEC.JC8@news.cso.uiuc.edu> walk@mrcnext.cso.uiuc.edu (Todd Walk) writes:
- >DOS doesn't have a 640K barrier. DOS will use as much CONTINOUS memory it
- >can find. Since the upper 384K of the 1st meg. is reserved for hardware,
- >(and bios) DOS can only "see" 640K. One thing that may be possible is
- >to use to 386 memory mapping to fool DOS into thinking that more memory
- >is availiable, and then having a device driver handle the mem. swaps.
-
- Technically, Todd, this is quite true. A friend of mine with a 386
- that has a hercules monitor gets 700K conventional memory this way
- with MS-DOS 5.
-
- (Namely, in config.sys he includes:
-
- device=c:\dos\himem.sys
- device=c:\dos\emm386.exe i=a000-afff
- dos=umb
-
- Emm386 gets xms memory from himem, which it maps into unused areas
- in the uma - including the A000 segment - which emm386 makes available
- via the xms umb calls. DOS=UMB instructs MSDOS.SYS to request any & all
- xms umbs and add them to the MS-DOS memory pool. Since the A000 segment
- is contiguous with the rest of 'conventional' memory, it gets folded
- into it. Nice, eh?)
-
- However...it is amazing the number of commercial applications that
- do not run properly in this configuration. They complain about too
- little memory, or a memory error, or a memory allocation error, or
- simply hang. If my friend does not include the A000 segment, or only
- includes A400-AFFF (separating that memory from the conventional
- pool, making it a "normal" umb) these same applications work.
-
- This may be more of what Ralf was talking about when he said that
- a DOS which breaks the 640k limit would not be DOS. It won't run
- the existing DOS machine base applications (still more DOS platforms
- out there than Mac, Windows, and OS/2 platforms combined).
-
- And, of course, breaking the the 1M limit imposed by the 8086 (and
- the 1M + 64K - 16 bytes imposed by real mode on 80x86s) would be
- even tougher to break. Current solutions include Windows [either
- native Windows apps or DOS-mode apps using DPMI] or OS/2 apps.
-
- -jen
- no, not speaking for microsoft....
-