How to trace how a dll gets loaded

[PradeepM]

I have this problem of certain dlls being loaded at the
start up time (Win XP Pro on PIII). I would like to find
out how to stop them from getting loaded. I have tried
using registry cleaner and msconfig. Is there any other
way to find out how dlls loaded or which application is
calling ?

 

[S.Sengupta]

Hi Pradeep!
Try this:-
Start> Run > Regedit > ok
Now navigate to:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer

Create a new sub-key named 'AlwaysUnloadDLL' and set the default value
to equal '1' to disable Windows caching the DLL in memory. Resrat your
computer.

with regards/
ssg/pronetworks.org

 

[John Dingley]

When an application needs/uses dlls they get loaded. An application can load
several dlls which may or may not be SHARED by other applications.

Killing off/unloading dlls is NOT a good idea, you are better off trying to
identify the applications that you do not need and stop them from running.

What you are asking is far too complex for an answer as no one knows what
applications you are using at start up and even if it were known you would
have to gather together loads of dlls id's for each application, then
identify which were not shared, and then you may be in a position to do what
you want. This is a mamoth task full of potential for PC failure.

 

[Alex Nichol]

Hi Pradeep!
Try this:-
Start> Run > Regedit > ok
Now navigate to:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer

That will not stop them getting loaded when needed - which is what the
question is. ANd it is not generally a good idea - it prevents them
staying around in the expectation that they will be re-used. The only
time it is useful is where you have two programs that you know to use
conflicting versions: you can put the two dlls in the related program's
folder and use that trick so when one program exits that dll unloads to
leave a clear field for the other. But in general it will slow things
down.