🚀 go-pugleaf

In article <146@apr.UUCP> las@apr.UUCP (Larry Shurr) writes:
> ...
>I haven't tried to bring up 3.6 yet, but I have brought up 3.5.  The
>D model works great iiiiiiffffffff..... you also use the -s switch
>(or use -mds if you compile with lc).  This tells the compiler that
>you don't want him to "normalize" all pointers and all results of
>pointer arithmetic.  A normalized pointer is one in which the offset
>is always in the range 0x0 - 0xF and the segment is pointing at the
>appropriate paragraph.  For example:
>
>	0900:1237	is converted to		0A23:0007
>
>The advantages include: comparisons between arbitrary pointers are
>meaningful and addressing (using pointers) > 64k of data.  Disadvantage
>is significant CPU time consumed normalizing pointers.
> ...

... and if you ever plan on writing programs for the i80286, don't
"normalize" pointers.  To paraphrase some Microsoft documentation:

	When a program loads a segment register on an 8086, it is
	actually loading a displacement value.  On the 80286, what
	is loaded is actually a segment number indexing to an entry
	in the master segment table.  The actual displacement value
	is loaded from that table.  There is NO relation between
	segment N and segment N+1 (ie N+1:0 != N:10h).

I assume that they're talking about the protected mode of the 286.  Since
DOS presently doesn't use the protected mode, you're OK for now.  Still,
any programming practice which counts on two segment:offset pairs pointing
to the same place in memory will need to be changed before DOS 5.0.
If segment:offset pairs are used properly, normalization is not needed.

-- Skip Addison
   {lll-crg, decwrl, ihnp4}!amdcad!cae780!ubvax!skip