Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!usc!apple!well!brent
From: brent@well.UUCP (Brent Southard)
Newsgroups: comp.windows.ms
Subject: Re: Memory, more memory!
Message-ID: <14260@well.UUCP>
Date: 24 Oct 89 21:49:57 GMT
References: <246400030@uxa.cso.uiuc.edu>
Reply-To: brent@well.UUCP (Brent Southard)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 30

In article <246400030@uxa.cso.uiuc.edu> mms00786@uxa.cso.uiuc.edu writes:
>
>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? 

Yes, you do.

Your application may make calls to the EMS driver which concern the SMALL
page frame only.  Messing with large frame EMS will screw with Windows'
memory management.  The functions you may call are numbered 1-15, and 18.
Unfortunately, Microsoft did not include a function interface in their
libraries.  I've written one, but I don't think my company would appreciate
me distributing it. :(

>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!!

Hmm.  The function may not be prototyped in windows.h.  Be sure you declare
it as a FAR PASCAL function in your prototype.

Hope this helps.
-brent

-- 
brent southard  (313) 656-8349   |   usenet:  ...!well!brent
ImageTech Corp  (313) 362-3141   |   

"When frog licking is outlawed, only outlaws will lick frogs."