BJ> Thanks for the fix!  When I get a chance I'll try to run a CVS
 BJ> update and try stuff on my machine here.  

 BS> Ok.

Let's see if I get it updated before the next contract work starts.
...
 BS> Ok, just take your time. :-)

I am.... 

 BS> No problem, I do enjoy the stuff, I do still have a 
 BS> comm api problem with telnet, I can't figure out how I 
 BS> tell max to stop listening on port 2000 after the 
 BS> acceptance of the connection. The super sneaky fork() 
 BS> trick don't work either.

The fork thing (under Unix), lets the original code keep listening for new
connections while the forked copy handles the established connection.  This
allows additional connections to be established using the same inbound port
number.  It has been a few years since I've played with this.  I know there
are ways to set this up.  I last played with this under a BSD style system,
while I believe Linux is a System V style setup....  And I think this is
one of the areas where the two use to be slightly different..... 
Hmmmmm....  May need to look at this some time when I am caught up with
other things....

Unfortunately, this is also a weakness with porting Max to a Unix style
system.  The DOS-think thata max started with may need a change to support
rolling the task number when waiting for the next connection on the port. 
This isn't an issue with the OS/2 VMODEM solution, because you had to start
a copy of max up for each vmodem "comm" port that was set up.....
 

Any way....

Take care....

And, hello.....

Bob Jones, 1:343/41


--- Maximus/2 3.01