Re: Mechanism for this oddity?
Vincent Fatica wrote:
On XP SP3, I start WinWord (Office 07) and minimize it. Using =
ProcessExplorer
(SysInternals v 11.04) I "suspend" WinWord (I figure ProcessExplorer =
suspends
each thread of WinWord). Then I open an Explorer window and navigate =
to my
profile dir ... Favorites ... double-click on a link ... nothing =
happens,
Explorer's caption includes "not responding". If I try to close the =
Explorer
window, I'm prompted to terminate Explorer (cancel that). If I go =
back to
ProcessExplorer and "resume" WinWord, all's well; the link opens and =
Explorer's
OK.
While I don't think it's a good idea to suspend an app like that, I'm =
curious
about the mechanism by which this peculiar interaction takes place ... =
any
speculation?
See SendMessage, read aboud DDE.
In a another related incident, if I try (in WinDBg) to start a certain =
3rd-party
GUI app while WinWord is so suspended, WinDbg tells me "debugee is =
running"
right in the middle of loading DLLs. Resuming WinWord causes this app =
to resume
loading DLLs, with UXTheme.dll being the first one loaded after the =
hang. Only
then does the app actually appear. ... any speculation?
See SendMessage. For whatever reason, the app is broadcasting a message.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not =
necessarily a good idea. It is hard to be sure where they are going to =
land, and it could be dangerous sitting under them as they fly overhead. =
-- RFC 1925