Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!pasteur!ames!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!uunet!mcrware!pgthor!dev386!beckman
From: beckman@dev386.UUCP (Zacharias Beckman)
Newsgroups: comp.windows.ms
Subject: Re: Does DialogBox preserve Data Segment Address?
Summary: How to see what's locked
Message-ID: <433@dev386.UUCP>
Date: 14 Feb 89 00:39:10 GMT
References: <460@msn005.misemi> <1366@agora.UUCP> <3816@metavax.UUCP>
Organization: University of Iowa, Iowa City
Lines: 17

In article <3816@metavax.UUCP>, adam@metavax.UUCP (- Mr. Engineering) writes:
> Does anyone know if Windows locks the data segment while a DialogBox
> is active?

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
select the 'walk heap' option from the 'heapwalk' program; this will show you
precisely what data/tasks/code/tdb's are owned by your application, what the
lock levels are, etc.  As for a direct answer to your question: "I'm not
sure".

Zacharias J. Beckman   ...   gatech!mdt!pgthor!dev386!beckman
                       ...   uunet!mcrware!pgthor!dev386!beckman
(319) 354-5116               (319) 351-1993

The answer is 42.