CompuServe Thread

memory limits WIN32/NT

1 messages in this thread
#50483From: Lee Hart [Microsoft]Aug 3, 1993 1:17 AM
>>>James, I have further questions along these lines. Does memory allocated by a Win32s app count against the 8K selector limit in win 3.1 ? Since memory allocated by Win32s via any Win32 API other than GlobalAlloc is not allocated via Windows 3.1, and therefore does not have any related selector(s) allocated, Win32s does not neccesarily have the same 8192 selector limits. However, there is still a system limit on the number of selectors, so when you start translating pointers and eating selectos with these translations you could till run afoul of it. >>>If it does, that wouls seem to indicate that Win32s allocated memory from the same address space, using the same local descriptor table as Win 3.1. Is this the case, or does 32s use a different address space, and if this latter is the case, does each 32s app have its own, or do all 32s apps share the same one ? Thanx. How about both? Win32s runs the Win32 apps in the same address space as the Win16 apps but since most Windows 3.1 apps are only looking at 16:16 addresses (and not 16:32), you can think of the Win32 apps as running in different address spaces than the Win16 apps. Lee