#memory limits WIN32/NT
5 messages in this thread
Thanx for checking, James. It's trickier than it looks, isn't it ? I mean, if
a Win32s app calls GlobalAlloc(), where does the block come from ? Either it
comes from the Win 3.1 global heap, or it's mapped to somewhere else. But
which ? But where ? Stay tuned for future developments.
Dave
There are 2 Replies.
>>>Thanx for checking, James. It's trickier than it looks, isn't it ?
I mean, if a Win32s app calls GlobalAlloc(), where does the block come
from ? Either it comes from the Win 3.1 global heap, or it's mapped to
somewhere else. But which ? But where ? Stay tuned for future
developments.
Please download Win32s.Hlp and read it – it makes these sorts of issues much
clearer. If a Win32 application running under Win32s calls GlobalAlloc, that
call is thunked through to the Win16 GlobalAlloc. (This is so that global
memory handles can be shared among applications, like so many apps assume.)
Other Win32 memory allocations (such as HeapAlloc, LocalAlloc, or
VirtualAlloc) all eventually map through to the AllocPage (I believe) VxD
memory allocation API.
Please download Win32s.Hlp – it explains this much better, and wih better
diagrams.
Lee
There is 1 Reply.
Sure, I will (RTFM, no ?). When all else fails…
But seriously, thanx for the reply, I will.
Dave
There is 1 Reply.
>>>Sure, I will (RTFM, no ?). When all else fails…
I know it's somewhat of a joke, but when you work on this side of support, it
hits close to the bone. Granted, few people have read all of the Win32 &
Windows NT documentation, but an amazing amount of what is asked is already
in the manual, and usually right where you think it'd be. And with the full
text searching that is available in the final Win32 SDK for Windows NT, it's
very quick and easy to do a near-exhaustive search.
>>>But seriously, thanx for the reply, I will.
Your welcome – please pass on any feedback that you have about the
documentation, the rest of the SDK, or the support – we do value it.
Lee
David, I'm sorry I did some research but got side tracked by a few things. I'll
have to go back and look up those things again. I'll need to because my app
crunches a lot of data, its a project management tool. What happens is during
the retrieval of a medium size file, about 20min into the retrieval the screen
blackens and the pc is in what can only thought of as being in a hung state.
There are no error messages. I did not have DR. Watson running. Well, I here
the Codewrite people think Win32s is unstable, so we are waiting for the final
release, we'll continue testing what we can. I have found the MSJ to be worth
the subsciption cost.
James