Re: Matching window handles and open file handles
- From: "Peter" <peterguy -at- hotmail -dot- com>
- Date: Tue, 19 Jul 2005 20:54:59 -0700
"Sam Hobbs" <samuel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23ZC4VFMjFHA.3448@xxxxxxxxxxxxxxxxxxxxxxx
> "mr_unreliable" <kindlyReplyToNewsgroup@xxxxxxxxxxx> wrote in message
> news:uVreh7XiFHA.3716@xxxxxxxxxxxxxxxxxxxxxxx
> >
> > This CAN be done.
>
> That depends on what you mean by "CAN". Yes, it can be done by someone as
> knowledgeable as the people at SysInternals.com. However I have seen
> questions such as this asked many times, and the SysInternals.com utility is
> the only sample I have seen suggested as something that can do it. And as
> you say, they do not provide source code. If they do, however, provide a
> documented interface to their software, then that is good.
>
> > However, they are not saying how they do it, and it's not readily
> > apparent to me.
>
> It uses undocumented parts of Windows and obviously they don't want us to
> know how it works. Obviously Microsoft does not want to tell us either.
Sysinternals also has a product called "Handle" that does pretty much what I was trying to do.
I have since abandoned that approach in favor of examining the running processes' CommandLines, then matching PIDs to Windows Handles, which is easier and more reliable than matching open file handles to windows handles because a process can open a file, read all of it into memory, then close the physical (notepad, for example).
-Peter
.
- References:
- Matching window handles and open file handles
- From: Peter
- Re: Matching window handles and open file handles
- From: mr_unreliable
- Re: Matching window handles and open file handles
- From: Sam Hobbs
- Matching window handles and open file handles
- Prev by Date: Re: .ini .dat or registry question
- Next by Date: Re: copy object
- Previous by thread: Re: Matching window handles and open file handles
- Next by thread: gdi32.dll question
- Index(es):
Relevant Pages
|
