Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!newstop!eastapps!tandoori!venkat
From: venkat@tandoori.East.Sun.COM (Desikan Venkatrangan - Sun BOS Software CONTRACTOR)
Newsgroups: comp.windows.ms.programmer
Subject: Storing far pointers in windows programs.
Message-ID: <6150@eastapps.East.Sun.COM>
Date: 15 May 91 14:20:10 GMT
Sender: news@East.Sun.COM
Reply-To: venkat@tandoori.UUCP ()
Distribution: na
Organization: Sun Microsystems, Billerica MA
Lines: 19


I have a Windows DLL and multiple applications using the DLL.  Because of
other non-technical requirements, the following is unavoidable -- storing
far pointers to near data in the applications.  Now at several places in
the SDK I came across statements that storing far pointers to near data
would not work if the data segment is marked MOVEABLE; but this statement
appears to be made only for real-mode (Windows using the Basic Memory
configuration).  Is there a problem with storing far pointers to near
data segment (which is marked MOVEABLE) when Windows is using the other
memory configurations? (The EMS4.0 configuration, the Standard Mode 
configuration and Enhanced mode configuration)  What negative side effects
result if the data segment is marked FIXED in real-mode?

Thanks.


D. Venkatrangan
(508) 671-0276
Sun Microsystems Inc.