🚀 go-pugleaf

In <4sejl4$pua@su3.in.net>, daniel@in.net (Daniel J. Casey Jr.) writes:
>In message <o9q6xoHpvyFd091yn@skypoint.com> - rsteiner@skypoint.com (Richard
>Steiner)15 Jul 1996 16:26:07 -0500 writes:
>:>The 512MB limit in VDMs was (as I understand it) an intentional design
>:>decision on IBM's part to make addressing more efficient for 16-bit apps,
>:>but the method Microsoft used to implement that API call just happens to
>:>be incompatible with the 512MB limit.

It's not a matter of efficiency - the thunking algorithm used to map
16-bit selectors to 32-bit flat addresses has to have a 512 MB limit: 
8192 segments x 64KBytes each for tiled address space = 512 MB.

From a programmer's perspective, when my app needs memory allocated, I
don't care where it is - the API returns a pointer, and I use it.I can
only think of one reason why Microsoft would implement an API to 
return Win32s/DPMI memory above 512MB. . . They're becoming a massive 
blight on the industry.

Best,

--- Les

+--------------------------------------------------------+
| Les Bell                          Tel: +61 2 451 1144  |
| lesbell@ibm.net                   Fax: +61 2 451 1122  |
| lesbell@syd.interconnect.com.au   PO Box 297           |
| lesbell@acslink.net.au            Neutral Bay NSW 2089 |
| CIS: 71210,104                    Australia            |
+--------------------------------------------------------+