home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!connor.Berkeley.EDU!rstanton
- From: rstanton@garnet.berkeley.edu (Richard Stanton)
- Newsgroups: comp.os.os2.misc
- Subject: Re: specific dos and mem
- Date: 24 Jul 1992 22:07:54 GMT
- Organization: Haas School of Business, U.C. Berkeley
- Lines: 15
- Distribution: world
- Message-ID: <rstanton.407.0@garnet.berkeley.edu>
- References: <2178347@overmind.citadel>
- NNTP-Posting-Host: connor.berkeley.edu
-
- >In article <1992Jul21.1480.22689@dosgate> "kenneth tam"
- ><kenneth.tam@canrem.com> writes:
- >>Both claim that replacing HIMEM.SYS and EMM386.EXE or their equivalents
- >>with OS2\MDOS\HIMEM.SYS and EMM.SYS will work.
- >>
- >>They don't, at least for me. This is off a DOS 5.00 VMDISK image,
-
- Another possibility. I don't know if this applies with specific DOS
- sessions, but I had trouble for a long time seeing any EMS memory, even
- though I had specified 2 MB in my DOS settings. It turned out that I had
- too many claimants on the memory between C0000-DFFFF to allow a 64k vlock
- for the EMS page frame. Rearranging memory, and using INCLUDE and
- EXCLUDE_REGION settings helped in the end.
-
- Richard Stanton
-