Luigi Auriemma

Reading some of the posts, it looks like I wasn't the only one to struggle with this, so I thought I'd share what it took to get this working. The DevOverrideEnable registry setting did not work for me.

I created a manifest file named processname.exe.manifest in the target program's directory. This is a simple XML file. This allows the local dll to be loaded. Here is an example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<file name="ws2_32.dll"/>
</assembly>

ws2_32.dll seems to be missing some functions that are present in win7/server 2008. Using Luigi's DLL proxy skeleton generator and his existing ws2_32.c code as a template, I was able to recompile it. Code attached. (ws2_32.def renamed to ws2_32.def.c so that it could be attached)

I will verify it, if I'm not in error I already checked for differences between the exports of win7 and winxp in the past.

the manifest seems a good idea.

Sethoiz: It's an .xml, but it has a .manifest extension. Just copy/paste from my first post and name the file as follows:
nameofprocessthatcallsdll.exe.manifest.

I did some further testing and these are my findings:

Setting DevOverrideEnable did not work, but setting it and creating the manifest file did. Another option is to set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\ExcludeFromKnownDlls to ws2_32.dll. No manifest file is required if the latter option is chosen. I'm not sure, but I think setting it in ExcludeFromKnownDlls would prevent ws2_32.dll from being cached by other apps, so DevOverrideEnable may be the better option. I don't think it's a big deal either way though.

I get the error "The procedure entry point WahDestroyHandleContextTable could not be located in the dynamic library WS2_32.dll" with the original version of the dll on Server 2008. I think this was the same error I got on Win7, but I did not re-test Win7.

The new ws2_32.dll is attached as requested.