Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!nickel
From: nickel@cs.utexas.edu (Jody P. Nickel)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Windows 3 segment/selector problems (Tech. Quest.)
Keywords: windows-3 selectors 80286 80386
Message-ID: <588@rodan.cs.utexas.edu>
Date: 19 Dec 90 03:28:36 GMT
References: <2564@wn1.sci.kun.nl>
Distribution: comp
Organization: U. Texas CS Dept., Austin, Texas
Lines: 9

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. The far pointer you receive
is a selector:0 pointer. The selector is valid as long as the memory stays
allocted. i.e. Don't free the memory and expect the pointer to be valid. 
The indirection from the selector to the physical address is handled by
the 386. This indirection is very fast, but the loading of a new selector
into a segment register is expensive, minimize the number of times you 
load a segment register and your performance should be acceptable.