Mario Semo wrote in a message to Mike Bilow:

 MS>> For example, for a DosAllocMem call with a size of 1, the 
 MS>> following occurs:

 MS>>       On OS/2 Warp Connect, the system allocates a
 MS>> 4096-byte block of committed memory.
 MS>>       On OS/2 Warp, the system allocates a 4096-byte 
 MS>> block of committed memory plus 61440 bytes without 
 MS>> attributes.

 MB> That's not just wrong, but absurd.  With FixPack 5 or later 
 MB> applied, OS/2 Warp and OS/2 Warp Connect are running 
 MB> exactly identical kernels.

 MS> then you should write an error report to IBM. they changed
 MS> to DosAllocMem docu AFTER devcon 8 to read as above. (the
 MS> above is a cut&paste from the OS/2 WARP toolkit from DevCon9
 MS> / DevCon10). The docu from OS/2 toolkit 2.0 till WARP
 MS> toolkit on DevCon8 says somewthing else (that 4K pages are
 MS> allocated). 

I didn't mean that by way of picking a fight with you, but I can assure you
that OS/2 does not even allocate address space when such allocations are
requested.  You can watch this inside a device driver, and you see that the
segment limits are set to the actual allocated amount in the descriptor
table. I have never seen different behavior under any version of OS/2.
 
-- Mike


---