You right.. Unless somehow it is someplace also loading that other DLL.
Shield wrote:Edit: hm, nvm, it shouldn't have any effect as it's a separate process.
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
Forget about testing with both. If you have .DLL named the same but serves different function, found in the executable location. You want to load up the system .DLL, you require to specify complete path.
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
Last edited by Thunder93 on Mon Nov 17, 2014 7:56 pm, edited 1 time in total.
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
Probably.. but shouldn't matter as InitNetwork() wouldn't load the .DLL found in the application location.
skywalk wrote:Not sure if PB loads wsock32 with calls to InitNetwork()?
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
skywalk wrote:Not sure if PB loads wsock32 with calls to InitNetwork()?
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
That's what's happening! InitNetwork() is using the dll found in the application directory.
...Could be potential security issue.
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
Well, I could not find a solution to change the behaviour of the DLL loading order, but some other guy gave me the idea to hack the compiled executable that uses the "wrong" DLL, and to change the reference of DLL there it wants to load. Now it is looking for wsocipx.dll rather than wsock32.dll and does not conflict with my updater program any longer.
In the end it appears that it is not that easy to alter WinAPI functions, I suppose. As my problem now is fixed unconventionally/differently than expected, I don't think there is much sense anymore in struggling with the enigmatic logic of Windows.
Thanks everyone for trying to help out and giving ideas!
Romk