Do you use HookCode or HookAPI? Try using HookAPI if you used HookCode.
That bot hooking code uses plain and simple import table patching. It might work in this specific case. But it hooks only the executable module, it doesn't hook any dlls.
If that is good enough for you you can use it yourself. But it's not really the best API hooking technique available. Anyway, it seems that it works around the WinSock double hooking problems...
Hook Winsock2.....
Ya ya!!!!!madshi wrote:nildo, the problem you're talking about might be that with WinSock1 vs WinSock2. In win9x WinSock1 calls end up in the same WinSock2 calls. So if you call WinSock1.recv, this goes through WinSock2.recv. IIRC, in XP when you call WinSock1.recv this ends up in WinSock2.WSARecv. Probably that's what you mean, nildo?
Thats what I mean, and what I was trying to find out.
Mathias, is that a True information or just an assumption?