I'm using Novell DOS LAN Workplace TCP/IP with Telemate INT14 support. Works well enough to post this message via Synchronet online editor. Yay.

I also have a linux PERL reverse proxy that answers inbound TELNET calls and cross connects them to a DOS box via serial ports. Works well enough to run a node or two of PCBoard.

It would be better to cross connect over the LAN via TCP/IP but then I need a FOSSIL layer between PCBoard and Novell TCP/IP. I have the Novell development kit docs and libraries so writing the code is doable. PCBoard is huge though and leaves little room for neighbors. The FOSSIL layer needs to be small, no more than 10-15k or so. Not a problem for the FOSSIL code but minimal TCP/IP socket connect code is around 40k. Too big. Only need it once per connection though, so it should be separated from the FOSSIL code and the socket number somehow passed in. It's an integer, like a file descriptor.

FOSSIL functions 1 and 2 wait indefinitely for RECV data or avaialble SEND buffer space. X00 times out after 30 seconds and sets an error bit. That's better than hanging forever but I still don't like it. Checking function 3 first should be mandatory, though the FOSSIL spec does not say so.

In my own code, I can do what I want. I'll treat delay as invalid usage and return immediately with the error bit set. Any software not respecting that rule, I won't use.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net