Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!bloom-beacon!deccrl!news.crl.dec.com!shlump.nac.dec.com!ashok.dec.com!nadkarni
From: nadkarni@ashok.dec.com (Ashok P. Nadkarni)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Windows 3 segment/selector problems (Tech. Quest.)
Message-ID: <18388@shlump.nac.dec.com>
Date: 20 Dec 90 14:30:26 GMT
Sender: newsdaemon@shlump.nac.dec.com
Distribution: comp
Organization: Digital Equipment Corporation
Lines: 11


In article <588@rodan.cs.utexas.edu>, nickel@cs.utexas.edu (Jody P. Nickel) writes...
>If you are only going to run in 386 enhanced mode the this will simplify
>your task immensely. After a GlobalAlloc, you can lock this memory and
>leave it locked until it is no longer needed.

As far as I know, this is also true in standard mode. It's only real mode that
you need to worry about being a good citizen in terms of unlocking global
memory.

/Ashok Nadkarni