Perhaps the Appnote also mentions that unless the BBS does it's flow
control correctly the Portmaster will blow itself right to hell as soon as
somebody starts a large download? We were frustrated enough to commit
physical violence against something/one last year and Livingston Support
didn't have a clue as to how to make it stop. Best we can figure,
PC-Board had some condition where it would not stop sending when the
Portmaster asserted flow control, and the Portmaster would try to continue
receiving all the way until it exhausted available memory. (At least this
theory fits all of the available evidence.) We were running PC-Board 15.21
and various multiport serial cards (in a vain effort to find a one that
worked) and finally gave up and switched to Wildcat 5.0 so we could just
telnet into it. The day Kitty1 went up and the PC-Board box went down we
stopped having blowups at the Portmaster. Of course since kitty1 is an NT
box, IT commits suicide on a pretty regular basis, but that is a problem
which will have to wait for the BSDI port of Wildcat. :)
John M. This post is 100% M$ Free!
Geek code 3.0:GCS d- C+++ UL++++$ P+ L+++ W+ N++ w--- Y+>+ 5+++ R tv- b++ e*
============================================================================
The views expressed may not reflect those of DataExchange Internet Services,
so don't bother flaming them. I'm the postmaster anyway, so just flame ME!