🚀 go-pugleaf

"Martin C" <martinc@aol.com> wrote in message
news:3f4d3a81@newsgroups.borland.com...
> well if GetWindowLong is NULL, then why it is returning library
> path for the exe (c:\windows\VCL50.bpl) of the newly create
> program window??

Because global hooks are executed in the context of all running processes
and threads.  When you spawn a new process, your hook will be injected into
that process and executed within the context of that new process.  Passing
NULL to GetModuleFileName() retreives the filename for the calling process.
If your hook is inside the context of another process at the time of calling
GetModuleFileName() and you are passing NULL, you get the filename of that
process.

> and do you suggest any other solution where I can get exe
> path of the newly created windows ??

Rather than using GetModuleFileName(), you could try using
GetWindowThreadProcessId() instead.  Once you have the process ID of the
window, you can then enumerate through all of the currently running
processes until you find a match, at which time you will know the executable
filename as well.  For information on enumerating processes, have a look at
this article:

    HOWTO: Enumerate Applications Using Win32 APIs
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;q175030


Gambit


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/03