Here in my Windows XP x64 build 2003, the current code works fine. Regards,
SZ On 9/27/06, Francois PIETTE <[EMAIL PROTECTED]> wrote: > > A user reported to me that winsock.accept generate an access violation at > address 7C8224B2 in ntdll.dll when is program runs on a w2K3 SP1 computer, > and only one such computer. He found that changing the lines: > > FSelectEvent := FD_READ or FD_WRITE or > FD_ACCEPT or FD_CLOSE; > iStatus := WSocket_WSAASyncSelect(FHSocket, Handle, > WM_ASYNCSELECT, FSelectEvent); > > into: > FSelectEvent := FD_ACCEPT; // Not all events, other wise Access > violation 7C8224B2 in NtDll in Window 2003 sp1. > iStatus := WSocket_WSAASyncSelect(FHSocket, Handle, > WM_ASYNCSELECT, FSelectEvent); > > solved the problem. > Any one else noticed similar problem ? > Removing FD_READ and FD_WRITE has probably no impact on a listening > socket. > But removing FD_CLOSE probably has (I have yet to do some testing). > > Any tought ? > > > -- > Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html > -- > [EMAIL PROTECTED] > http://www.overbyte.be > > > -- > 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 > -- Fastream Technologies Software IQ: Innovation & Quality www.fastream.com | Email: [EMAIL PROTECTED] | Tel: +90-312-223-2830 -- 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
