What security feature disallows applications from loading DLLs from their own directory?
I have two DLLs named ws2_32.dll and wsock32.dll. I also have an application that i want to utilize these two dlls rather then the ones in system32 but it apears that it doesn't. I ran a dependency scanner and found that in fact the application does load these two DLLs rather then the ones in system32 folder.
How i know its not working: the dlls are suppose to make a log file. It succeeded in making the log file on winXP but not Win7.
I found some one else having same problem but with vista but that could be fixed by doing the following:
'set the registry key "HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Image File Execution Options\DevOverrideEnable" to 1" '
However, i can't find the DevOverrideEnable field in my win7 registry. so upon the suggestions of some friends i added the field in manually and set the value that didnt work either.
What i have tried:
On Admin account
Run as Admin
Set compatibility to xp
take ownership
turn off all security features that i could get my hands on
does the registry entry " HKLM\ SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs" have any thing to do with this problem? i tried taking off the dll with the same name off the list but it denied my permission.
does the registry entry " HKLM\ SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs" have any thing to do with this problem? i tried taking off the dll with the same name off the list but it denied my permission.
Those DLLs are bassicaly pointer DLLs which i am using to make a tool for an application that is widly used but no longer supported. they are ws2_32.dll and wsock32.dll. the program is suppose to call these DLLs instead of the one in the system32 folder (which it does on my xp machine) and these DLLs create a packet log. basically recording the communication data between the application and a remote node. well that part is irrelevant, only telling because you asked.
I even ran 2 different dependency scanners on the applications and they tell me that the program will call the DLLs in the same directory which it apparently isn't, because if it did i would have the logs generated too.
they were made IN windows xp but they are designed to work with all versions of windows. there is nothing in the code that would stop it from working with windows 7. as long as bot operating systems operate on the same bit number it doesn't really matter.
