Path: utzoo!utgpu!watmath!iuvax!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!mms00786
From: mms00786@uxa.cso.uiuc.edu
Newsgroups: comp.windows.ms
Subject: Memory, more memory!
Message-ID: <246400030@uxa.cso.uiuc.edu>
Date: 23 Oct 89 00:24:00 GMT
Lines: 27
Nf-ID: #N:uxa.cso.uiuc.edu:246400030:000:1045
Nf-From: uxa.cso.uiuc.edu!mms00786    Oct 22 19:24:00 1989


Hello. I just ran into a memory roadblock (Sorry if thirty three solutions have
been discussed in the past, I missed them!)

I am writing a dedicated MS Windows application, to be run on one machine in
our lab. It has gobs of memory, about 4Meg I think, most of it EMS. The 
problem is that if I try to GlobalAlloc 384K of memory, I get a out of
memory error!

I therefore conclude only one thing - that GlobalAlloc does not know about
EMS memory. Is that true? Do I have to resort to assembly calls to EMS
functions? (BTW, I need to allocate 384K in 16K chunks at most, so I know
its not running into problems trying to allocate across segment boundaries).

So is this EMS memory accessible to my program without resorting to assembly?
I also tried using the function LimitEMSPages (wKbytes) as described in the
readme file provided with the SDK - this however gave me a unresolved external
error!!

Any information on how to allocate the requisite memory will be very much 
appreciated.

Thanks in advance,

Milan
mms00786@uxa.cso.uiuc.edu
.