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
> 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
Assuming this function is used to accept connections in Wsocket, it's
certainly not causing any problem here in W2K3 SP1.
I've been using t
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;
