Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!apple!agate!ucbvax!hplabs!hpl-opus!hpnmdla!hpsad!sdw
From: sdw@hpsad.HP.COM (Steve Warwick)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Windows 3 segment/selector problems (Tech. Quest.)
Message-ID: <22150004@hpsad.HP.COM>
Date: 9 Jan 91 17:00:11 GMT
References: <2564@wn1.sci.kun.nl>
Organization: HP Signal Analysis Division - Rohnert Park, CA
Lines: 30


Both the SDK and Petzold's book seem to avoid detailing how 
windows deals with movable code and data segments in protected
mode programs. They instead concentrate on the software-assisted
fixup methods which are required in real mode. Assuming you are willing
to write applications which are restricted to protected mode, is there a
clean description of the assumptions you can make about segments i.e.

1) can you assume that program code and segments are fixed 
 (since they are segment selectors)

2) won't  large model programs work fine, since data segments are also
  segment selectors..

3) same for DLL code and data?

more generally,

4) How does windows protected mode differ from OS/2 protected mode 
     in terms of segment fixups,  relocation and virtual memory?

5) Arn't much simpler methods of dealing with code and data movement 
	available when your in protected mode, removing the need for 
	windows prolog/epilogs and thunks? Will future versions of windows
	support such simpler models?


References to articles/technical publications dealing with these
issues will be appreciated. Please avoid the "I Think That ..."
(Unless you wrote it...)