At 05:44 AM 01/10/02, you wrote:

> > > ----------------------------------------
> > > And of course, the infamous;
> > >
> > > Tue Jan 8 10:08:18 2002
> > > INET/inet_error: send errno = 104
> > >
> > > ( i have lots of this...)
> > > ----------------------------------------
>
>Check in your Windows Event Viewer(I know this exists under NT/2000/XP
>platforms). It should if there was an error and could tell you a bit more
>about it. Don't bother looking on Microsoft's website, the only error
>listed as 104 is related to Visual FoxPro. The error related to Windows
>start at 600. Winsock, I'm not sure, they might be listed in the SDK.

Yeah, that sounds par for Windows. We run Delphi front ends to a Linux
FB-IB server and the Windoze are always getting winsock errors. I've made
some adjustments to the TCP time-outs in Linux, it seemed to help a bit,
but I don't see how to do that with Windows. I got that error message down
from 30-40 times per occurrence to 3-4 times, still get the WinCrash though.

Linux never complains about network responses, it just keeps waiting until
it times out, then you have a choice to try again, but Windoze seams to
need to have the power cycled every time.

Here is a good how-to for Linux TCP/IP resources:
http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap6sec75.html#AEN4895

Scott.