> YOU SAID
> Just recalled - Named Pipes allowed only 255 instance of pipe. I.e. you
> will
> have limitation in 255 simultaneous Named Pipes connections. And, of course,
> client OS can't create Named Pipe instance, i.e. you can't run Firebird at
> Win9x
> and use Named Pipe's connections.
>
> I SAY
> I don´t understand what do you mean. In this network there is a user with
> Windows 95 and he is using the application with \\host\alias and it is
> working good.

Do you run Firebird at Win95 ? Re-read what i wrote, read some MSDN at last,
i can't be your scool teacher, sorry.

> YOU SAID
> Its not about files, its about sockets. To handle N TCP\IP connections,
> Firebird
> call select() and put N+1 socket's into it. Obviously, NOD32 intercept TCP
> stack and
> somewhere calls WaitForMultiplyObjects with this socket's. This API have
> limitation
> in 64 handles, therefore the issue. Is it clear now ?
>
> I SAY
> This means that with NOD32, in any Windows version it´s impossible to use
> more than 63 TCP/IP connections?

It looks so. Any software have its bugs, and NOD32 is a software. Probably
FB3 will work another way with sockets and this issue gone, but no promise yet.
Current way of Firebird listener works is pretty legal.

Regards,
Vlad