Path: utzoo!utgpu!watmath!clyde!att!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!se-sd!dennis
From: dennis@se-sd.sandiego.ncr.com (Dennis Foster)
Newsgroups: comp.windows.ms
Subject: Re: Does DialogBox preserve Data Segment Address?
Message-ID: <1781@se-sd.sandiego.ncr.com>
Date: 16 Feb 89 00:45:44 GMT
References: <460@msn005.misemi> <1366@agora.UUCP> <3816@metavax.UUCP> <433@dev386.UUCP>
Reply-To: dennis@se-sd.sandiego.NCR.COM (Dennis Foster(AEP))
Organization: NCR Corp. Systems Engineering, San Diego
Lines: 14

In article <433@dev386.UUCP> beckman@dev386.UUCP (Zacharias Beckman) writes:
> ... stuff deleted ...
>You can use the 'heapwalk' routine under windows/286 to see what is locked
>at any given point (it doesn't work too well under windows/386 because of the
>complex addressing).  Run your program, get the dialog box on screen, and
> ... stuff deleted ...

You can much more information out of heapwalk in windows/386 if you execute
windows/386 to not provide expanded memory.  You do this by including a /n
on the execution of windows.

E.g.,          WIN386/N

From this point, heapwalk shows about all there is to see!