Ok, so it is working, but still remains the question wy the dynamically loading of winsock should not work as it should on some machines ?
Arno, you mention a virus, but should it then work with the ForceLoadWinsock ? I recall virusses that did some things with the TCP stack, but it was more the service and proto files in registry I think. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Thursday, December 14, 2006, 15:49, Henrik wrote: > Hi! > YES! Now we are getting somewhere. > When I manually load/unload winsock as Wilfried suggested, the error does > not show. So it has something to do with the loading of the dll. > I'm sending You the files Wilfried :-) > // Henrik -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be