Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!uunet!indetech!hsv3!jls
From: jls@hsv3.UUCP (James Seidman)
Newsgroups: comp.windows.ms.programmer
Subject: Finding the module name for a window
Message-ID: <8888@hsv3.UUCP>
Date: 30 May 91 16:59:55 GMT
Reply-To: jseidman@jarthur.claremont.edu
Organization: Video Seven / Headland Technology
Lines: 15

Given the handle to a window, is there any sequence of calls I can make
to find out the name of the module which owns it?  I'd settle for either
just the short name or the full path.

(The reason I want to know is that I'm trying to detect if the foreground
session is a DOS box.  I was going to do this by testing if the module
was WINOLDAP.  If anyone has an alternate way to do this, I'd love to hear
it.)


-- 
Jim Seidman (Drax), the accidental engineer.
"It doesn't have to work... they'll be paralyzed just from laughing at me."
							- Dr. Who, _Shada_
UUCP: ames!vsi1!hsv3!jls	         INTERNET: hsv3.UUCP!jls@apple.com