home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!destroyer!news.iastate.edu!jws
- From: jws@iastate.edu (James William Shoemaker)
- Subject: Re: 1Meg limit in WinOS/2?
- Message-ID: <BzF1zy.JB8@news.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames, IA
- References: <20071@ksr.com> <1992Dec15.015233.15485@njitgw.njit.edu>
- Distribution: na
- Date: Thu, 17 Dec 1992 18:28:45 GMT
- Lines: 27
-
-
- >>Since WinOS/2 is effectively Standard Mode Windows, does
- >>that mean that the biggest contiguous memory block that can
- >>be allocated is 1Meg?
-
- >Yes, if you use HUGE model. If you use LARGE model, then the buggest
- >block is 64K. I think Windows provides some memory management
- >functions that get around this, though. But those functions might
- >only be available in ENHANCED mode.
-
- As far as I know there is no way for a 16-bit Program to allocate
- a memory region larger than 1M in Standard Mode Windows.
-
- One Caviat there is that WinOS2 is not Completely Standard mode Windows
- It is Standard Mode Windows running on a DPMI server. So a 32-Bit Windows
- program that uses DPMI to get into and out of 32-bit mode runs great and can
- allocate large buffers. I know this because the 32-Bit Windows extender from
- Watcom Does this and the programs generated by it run just fine, though you
- have to give the Win-OS2 session they are in >64 Meg Ram for some reason.
-
- Needless to say any program I write under windows that allocates Large
- buffers will be written using Watcom for the ability to run on the most
- platforms possible. I don't know if this trick works under NT, I haven't had
- a chance to try it yet.
-
-
- JWS
-