Stoping a DLL from running
This is a discussion about Stoping a DLL from running in the Windows Software category; I'm running a Point Of Sale system that loads a DLL program into memory. In order to perform system updates the DLL has to be unloaded. The only way to achieve this is by rebooting the machine. Is there a command line i can use to manually stop and unload the dll? I'm using win2k server.
I'm running a Point Of Sale system that loads a DLL program into memory. In order to perform system updates the DLL has to be unloaded. The only way to achieve this is by rebooting the machine. Is there a command line i can use to manually stop and unload the dll?
I'm using win2k server.
I'm using win2k server.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Aug 10
Aug 31
0
1 minute
Responses to this topic
This is not supposed to happen to 32bit windows applications.
A Win16 program that loaded a DLL with LoadLibrary and crashed or didn’t call FreeLibrary later would leave the DLL in memory even after the program exited. Matt Pietrek wrote a famous NukeDLL utility for dealing with this problem, and there are still several versions of it floating around. I am not sure if it will work in your case. Here is a link where you can get one of the versions:
http://www.openinformationsystems.com/provalov/freeware/nukedll.zip
Hope this helps.
A Win16 program that loaded a DLL with LoadLibrary and crashed or didn’t call FreeLibrary later would leave the DLL in memory even after the program exited. Matt Pietrek wrote a famous NukeDLL utility for dealing with this problem, and there are still several versions of it floating around. I am not sure if it will work in your case. Here is a link where you can get one of the versions:
http://www.openinformationsystems.com/provalov/freeware/nukedll.zip
Hope this helps.
