🚀 go-pugleaf

"David" <davids@unite.com.au> wrote in message
news:443a4e43$1@newsgroups.borland.com...
> I wish to know if a DLL which is loaded from another process is still
loaded
> and running. I don't call the DLL myself but just wish to know if it is
> still loaded in memory.
>
> Is this possible ??
>
> thanks in advance
> David
>
 try to rename/delete the file.

Boba wrote:

>"David"  wrote in message
>> I wish to know if a DLL which is loaded from another process is still
>loaded
>> and running. I don't call the DLL myself but just wish to know if it is
>> still loaded in memory.
>>

> try to rename/delete the file.

Might be nicer to use 
	if( 0 == access(filename,2) )
	{	//DLL is free
	}else{
		//DLL in use or read-only
	}

"David" <davids@unite.com.au> wrote in message
news:443a4e43$1@newsgroups.borland.com...
> I wish to know if a DLL which is loaded from another process is still
loaded
> and running. I don't call the DLL myself but just wish to know if it is
> still loaded in memory.
>
> Is this possible ??
>

There's probably an easier way, but the first thing that comes to mind is to
enumerate the modules loaded by each process currently running on the
system, looking for the one you're interested in.  If you don't find it, it
isn't loaded.

See the following link for how to enumerate all of the processes and modules
in the system:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/perfmon/bas
e/taking_a_snapshot_and_viewing_processes.asp

- Dennis

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443aac3c$1@newsgroups.borland.com...
>
> There's probably an easier way, but the first thing that comes to mind is
to
> enumerate the modules loaded by each process currently running on the
> system, looking for the one you're interested in.  If you don't find it,
it
> isn't loaded.

Here's a quick and dirty implementation:

bool IsDLLLoaded( const AnsiString &DLLName )
{
   bool bIsDLLLoaded = false;

   HANDLE hProcessSnapshot = CreateToolhelp32Snapshot( TH32CS_SNAPPROCESS,
0 );

   if ( INVALID_HANDLE_VALUE != hProcessSnapshot )
   {
      PROCESSENTRY32 ProcessEntry;
      ProcessEntry.dwSize = sizeof( ProcessEntry );

      for ( bool bProcessFound = Process32First( hProcessSnapshot,
&ProcessEntry );
            bProcessFound;
            bProcessFound = Process32Next( hProcessSnapshot,
&ProcessEntry ) )
      {
         HANDLE hModuleSnapshot = CreateToolhelp32Snapshot(
TH32CS_SNAPMODULE, ProcessEntry.th32ProcessID );

         if ( INVALID_HANDLE_VALUE != hModuleSnapshot )
         {
            MODULEENTRY32 ModuleEntry;
            ModuleEntry.dwSize = sizeof( ModuleEntry );

            for ( bool bModuleFound = Module32First( hModuleSnapshot,
&ModuleEntry );
                  bModuleFound;
                  bModuleFound = Module32Next( hModuleSnapshot,
&ModuleEntry ) )
            {
               if ( DLLName == ModuleEntry.szModule )
               {
                  bIsDLLLoaded = true;
                  break;
               }
            }
         }

         CloseHandle( hModuleSnapshot );

         if ( bIsDLLLoaded )
         {
            break;
         }
      }

      CloseHandle( hProcessSnapshot );
   }

   return bIsDLLLoaded;
}

- Dennis

I think that worked under 16 bit Windows but under Win32 I don't think 
access will tell if the file is loaded.

It calls GetFileAttribues and massages the result to decide what to return. 
Nothing in the result tells if the file is loaded.

.  Ed

> Bob Gonder wrote in message
> news:tf3l32phnths5uo1u53tbh73rsl42315mr@4ax.com...
>
>>> I wish to know if a DLL which is loaded from another process is
>>> still loaded and running. I don't call the DLL myself but just wish
>>> to know if it is still loaded in memory.
>
>> try to rename/delete the file.
>
> Might be nicer to use
> if( 0 == access(filename,2) )
> { //DLL is free
> }else{
> //DLL in use or read-only
> }

Ed Mulroy wrote:

>I think that worked under 16 bit Windows but under Win32 I don't think 
>access will tell if the file is loaded.
>
>It calls GetFileAttribues and massages the result to decide what to return. 
>Nothing in the result tells if the file is loaded.

Ok, then open file with write access will fail if in use, and doesn't
mess with the file if it isn't in use, as rename or delete would.

> I still don't understand what David (the op) is trying to achieve.

The DLL sends messages to my app but I don't send messages back. If the user 
exits the app then I would like to warn the user that there is still a DLL 
trying to communicate with it before the user exits. Therefore I need to 
know if the DLL is still in use.

Actually I do have access to source code for the DLL so maybe I could do 
something from the DLL end. I asked here once whether or not you could send 
messages to a DLL and it wasn't a simple proposition either.

regards
david




"Boba" <Boba@somewhere.world> wrote in message 
news:443bd8e0$1@newsgroups.borland.com...
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:443aac3c$1@newsgroups.borland.com...
>> ...
>> There's probably an easier way, but the first thing that comes to mind is
> to
>> enumerate the modules loaded by each process currently running on the
>> system, looking for the one you're interested in.  If you don't find it,
> it
>> isn't loaded.
>>
> been there, done that...
> if a module is not curremtly beeing used by any of the software visible to
> UI via what you're talking about, there are still tons of software running
> in below UI level that may still need those modules in which case you may
> think the module is not in use: try to delete... if it fails - keep 
> digging
> deeper.
> I still don't understand what David (the op) is trying to achieve.
>
> 

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443aac3c$1@newsgroups.borland.com...
> ...
> There's probably an easier way, but the first thing that comes to mind is
to
> enumerate the modules loaded by each process currently running on the
> system, looking for the one you're interested in.  If you don't find it,
it
> isn't loaded.
>
been there, done that...
if a module is not curremtly beeing used by any of the software visible to
UI via what you're talking about, there are still tons of software running
in below UI level that may still need those modules in which case you may
think the module is not in use: try to delete... if it fails - keep digging
deeper.
I still don't understand what David (the op) is trying to achieve.

"Boba" <Boba@somewhere.world> wrote in message
news:443bd8e0$1@newsgroups.borland.com...

> been there, done that...
> if a module is not curremtly beeing used by any of the software visible to
> UI via what you're talking about, there are still tons of software running
> in below UI level that may still need those modules in which case you may
> think the module is not in use: try to delete... if it fails - keep
digging
> deeper.

Can you explain what you mean by, "visible to the UI" and "below UI level"?

CreateToolhelp32Snapshot has no notion of what's "visible to the UI" or
"below UI level."  According to MSDN, using the TH32CS_SNAPPROCESS flag
results in a list of "...all processes in the system."  Can you provide an
example of a process that would not be in the list of "all processes in the
system?"

- Dennis

Hello Boba

So how do you tap into the message que of a DLL ??

Do you have any examples ??

Regards
David


"Boba" <Boba@somewhere.world> wrote in message 
news:443d2e58$1@newsgroups.borland.com...
> "David" <davids@unite.com.au> wrote in message
> news:443c5e6a@newsgroups.borland.com...
>> ...
>> Actually I do have access to source code for the DLL ...
>
> that always helps.
>
>> I asked here once whether or not you could send
>> messages to a DLL and it wasn't a simple proposition either.
>
> a dll is no different from any other application with an msg pump.
>
> 

"David" <davids@unite.com.au> wrote in message
news:443c5e6a@newsgroups.borland.com...
> ...
> Actually I do have access to source code for the DLL ...

that always helps.

> I asked here once whether or not you could send
> messages to a DLL and it wasn't a simple proposition either.

a dll is no different from any other application with an msg pump.

Hello

The DLL is loaded after the exceutable is run. I don't have access to the 
source code of the calling app, only the DLL.

regards
david


"Boba" <Boba@somewhere.world> wrote in message 
news:443e5780$1@newsgroups.borland.com...
> "David" <davids@unite.com.au> wrote in message
> news:443de373@newsgroups.borland.com...
>> Hello Boba
>>
>> So how do you tap into the message que of a DLL ??
>>
>> Do you have any examples ??
>>
>> Regards
>> David
>>
>>
> Hello David;
> are you talking about a dll loaded prio your code starts?
> is it a library you attach? is it something you coded?
>
> 

"Boba" <Boba@somewhere.world> wrote in message
news:443e58c4$1@newsgroups.borland.com...
>
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:443bf6f6$1@newsgroups.borland.com...
> > ...
> > Can you provide an example of a process that would not be
> in the list of "all processes in the system?"
>
> if you have an nt handy, look to see if the Client Server Runtime
> Process
> is running; if so - is the module loaded? what do you use to list 'all'
> the modules curently loaded?

I do have NT handy, and I'm not sure where you were suggesting I look, but I
do not see that particular process in task manager.

The code I posted earlier is what I used (see the message I posted on 4/10).
That code, however, will not run on NT because NT does not provide
imeplementations of the CreateToolhelp32Snapshot-related functions.

If you must use NT, there are functions in PSAPI.DLL that will allow you to
enumerate processes and modules in a fashion similar to how I did it in my
example.

- Dennis

"David" <davids@unite.com.au> wrote in message
news:443de373@newsgroups.borland.com...
> Hello Boba
>
> So how do you tap into the message que of a DLL ??
>
> Do you have any examples ??
>
> Regards
> David
>
>
Hello David;
are you talking about a dll loaded prio your code starts?
is it a library you attach? is it something you coded?

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443bf6f6$1@newsgroups.borland.com...
> ...
> Can you provide an example of a process that would not be
in the list of "all processes in the system?"

if you have an nt handy, look to see if the Client Server Runtime
Process
is running; if so - is the module loaded? what do you use to list 'all'
the modules curently loaded?

"David" <davids@unite.com.au> wrote in message
news:443e5b4d@newsgroups.borland.com...
> Hello
>
> The DLL is loaded after the exceutable is run. I don't have access to the
> source code of the calling app, only the DLL.
>
if you have access tro that dll's source code you are the one
who knows if the dll has a message queue and if it's got its
pump plugged in and switched on.

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443e698b$1@newsgroups.borland.com...
>
> I do have NT handy, and I'm not sure where you were suggesting I look, but
I
> do not see that particular process in task manager.

run System Information from the Start/Programs/Accessories/System
Tools/System Information
(mssysinfo32.exe) Look@the Running Tasks branch of Software Environment.

> ... because NT does not provide
> imeplementations of the CreateToolhelp32Snapshot-related functions.

sure it does.
It doesn't matter what you call those functions: most of the useful ones
don't have names anyway.

> It doesn't matter what you call those functions: most of the useful ones
> don't have names anyway.
I mean the end user versions of Windows.

"Boba" <Boba@somewhere.world> wrote in message
news:443e8465$1@newsgroups.borland.com...

> > ... because NT does not provide
> > imeplementations of the CreateToolhelp32Snapshot-related functions.
>
> sure it does.

Try compiling and executing a program that uses CreateToolhelp32Snapshot in
Windows NT (NT 4 workstation).  You'll get an error that says, in effect,
"CreateToolhelp32Snapshot not found in kernel32.dll."

- Dennis

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443eaef2$1@newsgroups.borland.com...
>
> "Boba" <Boba@somewhere.world> wrote in message
> news:443e8465$1@newsgroups.borland.com...
>
> > > ... because NT does not provide
> > > imeplementations of the CreateToolhelp32Snapshot-related functions.
> >
> > sure it does.
>
> Try compiling and executing a program that uses CreateToolhelp32Snapshot
in
> Windows NT (NT 4 workstation).  You'll get an error that says, in effect,
> "CreateToolhelp32Snapshot not found in kernel32.dll."

I can provide such a program, if you want to try it without writing one of
your own.

- Dennis

"Boba" <Boba@somewhere.world> wrote in message
news:443e8465$1@newsgroups.borland.com...

> run System Information from the Start/Programs/Accessories/System
> Tools/System Information
> (mssysinfo32.exe) Look@the Running Tasks branch of Software Environment.

I think you mean msinfo32 (not mssysinfo32).  And if so, we are not talking
about the same OS.  You keep saying "NT", but you are referring to things
that are in XP but are not in NT (like CreateToolhelp32Snapshot).

- Dennis

"Boba" <Boba@somewhere.world> wrote in message
news:443fa386@newsgroups.borland.com...
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:443eb0bd$1@newsgroups.borland.com...
> >
> > I think you mean msinfo32 (not mssysinfo32).
>
> typo
>
> > And if so, we are not talking
> > about the same OS.  You keep saying "NT", but you are referring to
> things
> > that are in XP but are not in NT (like CreateToolhelp32Snapshot).
> >

How long have you been using Windows -- less than 5 years?  Windows NT was
introduced several years (1993) before Windows 95, so when you say "Windows
NT," you're referring to very old operating system.  There is a very
definite difference between Windows NT and Windows XP (which wasn't
introduced until 2001), so do not make the assumption that NT and XP they
are one and the same -- they are not (they're not even close).

- Dennis

"Dennis Jones" <nospam@nospam.com> wrote in message
news:443eb0bd$1@newsgroups.borland.com...
>
> I think you mean msinfo32 (not mssysinfo32).

typo

> And if so, we are not talking
> about the same OS.  You keep saying "NT", but you are referring to
things
> that are in XP but are not in NT (like CreateToolhelp32Snapshot).
>

i am not smart enough to see the difference ...

Dennis Jones wrote:
> Windows NT was introduced several years (1993) before Windows 95,
> so when you say "Windows NT," you're referring to very old operating
> system.  There is a very definite difference between Windows NT and
> Windows XP (which wasn't introduced until 2001), so do not make the
> assumption that NT and XP they are one and the same -- they are not
> (they're not even close).

Wikipedia says this:
Windows XP and Windows Server 2003 are the latest versions of Windows NT, 
though they are not branded as such for marketing purposes. AFAIK, XP is 
Windows NT 5.1

Also Windows NT went through four versions before becoming Windows 2000.

Wikipedia has a table of all the Windows NT versions here: 
http://en.wikipedia.org/wiki/Windows_NT. You just have to scroll down to the 
Releases section.

Jonathan
------------------------
TwineCompiler, blazingly fast C++ compiles:
http://www.jomitech.com/#twine
------------------------ 

My thanks go to Jonathan.
Dennis;
there are 2 (two) branches of what you call Windows marketed by MS:
Windows written by MS (the idea belongs to Apple) and NT written
outside of MS. The former has deadended with Millennium and the later is
still around in the form of 2003, xp,... On Tuesday you asked me
"Can you explain what you mean by, "visible to the UI" and "below UI
level"?"
I simply don't like to use the abbriviation GUI 'cause I know folks
who can not see as well as I can but they make much more money out of
the toy we call a PC. Speaking of levels - I am not a paperback writer -
so
just take a look at the following table (fixed font recommended):

Level         Tools        log($/hr)
-----------+-------------+-------------
GUI          Borland/MS     1
Executive    MS/Borland     2
Kernel       MS             3
HAL          MS+            4
HW           Screwdriver    priceless
-----------+-------------+-------------

This particular NG covers the top level issues only.

Boba

"Jonathan Benedicto" <invalid@nobody.com> wrote in message
news:443fc12b$1@newsgroups.borland.com...
> Dennis Jones wrote:
> > Windows NT was introduced several years (1993) before Windows 95,
> > so when you say "Windows NT," you're referring to very old operating
> > system.  There is a very definite difference between Windows NT and
> > Windows XP (which wasn't introduced until 2001), so do not make the
> > assumption that NT and XP they are one and the same -- they are not
> > (they're not even close).
>
> Wikipedia says this:
> Windows XP and Windows Server 2003 are the latest versions of Windows NT,
> though they are not branded as such for marketing purposes. AFAIK, XP is
> Windows NT 5.1

I understand that, but the fact is when people refer to Windows NT, it is
generally understood that they are referring to the "old" Windows NT, that
is, before they changed the name to Windows 2000 and eventually Windows XP.
I don't know about you, but I've never heard anyone refer to XP as "Windows
NT 5.1" -- they just call it "XP."

So, my point remains.  Windows NT (pre-2000) does NOT have the same
functionality that Windows 2000 and XP do.  So if you are going to say that
Windows NT has the CreateToolhelp32Snapshot function, you had better
indicate which version of the operating system you are talking about, either
by giving the name (NT, 2K, XP, etc) or by using the version number (which,
of course, nobody does because the mnemonic is much easier to remember),
because otherwise you're going to run into misunderstandings like this one!

- Dennis

"Boba" <Boba@somewhere.world> wrote in message
news:44401ee0$1@newsgroups.borland.com...
> My thanks go to Jonathan.
> Dennis;
> there are 2 (two) branches of what you call Windows marketed by MS:
> Windows written by MS (the idea belongs to Apple) and NT written
> outside of MS. The former has deadended with Millennium and the later is
> still around in the form of 2003, xp

Please read my reply to Jonathan.


,... On Tuesday you asked me
> "Can you explain what you mean by, "visible to the UI" and "below UI
> level"?"
> I simply don't like to use the abbriviation GUI 'cause I know folks
> who can not see as well as I can but they make much more money out of
> the toy we call a PC. Speaking of levels - I am not a paperback writer -
> so
> just take a look at the following table (fixed font recommended):

I have no idea what you are talking about!


> Level         Tools        log($/hr)
> -----------+-------------+-------------
> GUI          Borland/MS     1
> Executive    MS/Borland     2
> Kernel       MS             3
> HAL          MS+            4
> HW           Screwdriver    priceless
> -----------+-------------+-------------
>
> This particular NG covers the top level issues only.

Huh?  Where did you get *that* idea?  This newsgroup covers the Windows API
(hence the name, "nativeapi"), which is, by no means limited to GUI
functions.

This thread is going nowhere fast -- I think it has breathed its last.

- Dennis

"David" <davids@unite.com.au> wrote in message 
news:443c5e6a@newsgroups.borland.com...
>> I still don't understand what David (the op) is trying to achieve.
>
> The DLL sends messages to my app but I don't send messages back. If the 
> user exits the app then I would like to warn the user that there is still 
> a DLL trying to communicate with it before the user exits. Therefore I 
> need to know if the DLL is still in use.
>
> Actually I do have access to source code for the DLL so maybe I could do 
> something from the DLL end. I asked here once whether or not you could 
> send messages to a DLL and it wasn't a simple proposition either.
>
> regards
> david
>
Check this out:
  Since you are already considering re-writing code for the DLL, the DLLMain 
or DLL EntryPoint (Depends on whether you've selected MFC Compatability  or 
not) function takes as one of its parameters a reason code, of which one of 
the valid reason codes for the function to be called is 
"DLL_PROCESS_DETACH".  I would think you could use this to trap detach calls 
from apps and display your warning dialog from the DLL.  Correct me if I'm 
wrong, experts. 

Hello

Yes I ended up doing something like this. I even sent a message from the DLL 
to the app to tell it when the PROCESS_DETACH was called so it knew that the 
DLL was no longer in use.

It worked out OK doing this way.

regards
david


"David Pratt" <Prattaratt@sbcglobal.net> wrote in message 
news:4441d664$1@newsgroups.borland.com...
>
> "David" <davids@unite.com.au> wrote in message 
> news:443c5e6a@newsgroups.borland.com...
>>> I still don't understand what David (the op) is trying to achieve.
>>
>> The DLL sends messages to my app but I don't send messages back. If the 
>> user exits the app then I would like to warn the user that there is still 
>> a DLL trying to communicate with it before the user exits. Therefore I 
>> need to know if the DLL is still in use.
>>
>> Actually I do have access to source code for the DLL so maybe I could do 
>> something from the DLL end. I asked here once whether or not you could 
>> send messages to a DLL and it wasn't a simple proposition either.
>>
>> regards
>> david
>>
> Check this out:
>  Since you are already considering re-writing code for the DLL, the 
> DLLMain or DLL EntryPoint (Depends on whether you've selected MFC 
> Compatability  or not) function takes as one of its parameters a reason 
> code, of which one of the valid reason codes for the function to be called 
> is "DLL_PROCESS_DETACH".  I would think you could use this to trap detach 
> calls from apps and display your warning dialog from the DLL.  Correct me 
> if I'm wrong, experts.
>