BJ> Interesting....  I was wondering if Maximus's built in 
 BJ> ANSI (superset of VT-100 video) escape sequences would 
 BJ> cause any problems....

Maybe.. But after i set it to disable checking of ANSI, there might be no
problem by my self. But i see i got a german caller thru, but i can see he
didn't made it longer than the joining of the BBS.

I notice, if calledbefore is set, there is no problem..

 BJ> Are the TCP/IP ports set up for 8 bit clear or using 7 bit with various 
 BJ> terminal control codes interpreted?

I guess it's not 8bit, because things like filetransfer doesn't work.. but
i don't know mutch about the telnet module.
  
 BJ> If the you run the 
 BJ> TCP/IP ports as the telnet standard with only 7 bits 
 BJ> and interpretation, then there are some VT-100 escape 
 BJ> sequences that *will* lock up the communication path.  Gets back to the 
 BJ> old flow control issues, among other things.  

Well let me say it.. it look like a old school bbs in dos, after a printf
"\033(U".. I'm running ANSI, else i won't be able to write this
message in MaxEd.

 BJ> From 
 BJ> memory, control-s stops traffic while control-q starts 
 BJ> traffic.  Also (from memory), since Max is setup to 
 BJ> handle various modems, including flow control issues, you may need to 
 BJ> look at the "modem" or "serial port" settings, or with 
 BJ> how you are openinging up the TCP/IP socket.  

Hmm.. ok. That's quite smart.. i used to run RemoteAccess, there i didn't
got those options as far as i remember.

 BJ> For 
 BJ> TCP/IP connections we should be able to turn off the 
 BJ> software and probably also turn off the hardware flow control stuff in 
 BJ> Maximus.  For the TCP/IP socket, I believe you will 
 BJ> want an 8 bit clear channel, not the telnet interpreted 
 BJ> channel.  

I doubt that the telnet module is using the options, remember it's at alpha state.

 BJ> There may be some additional IO CTL functions 
 BJ> also needing to be called after opening the TCP/IP socket to get this 
 BJ> working smoothly.  [I assume we are running TCP and not 
 BJ> UDP over IP.]  

Correct.

 BJ> Is max being run as a shell under a version of getty?  

Maximus is listening (personally.. hah, couldn't find a better word) at a
port number you tell it by the -p option, and after a user has login and he
log out it quit, but then i've inittab to respawn the problem.

Maybe max should have some options, so i could be called from
mgetty/inetd.conf, i really don't see the point of writing a serial IO
interface, for modem connectivity... on unix..

Just my 2 cents :)

Regards,
Bo


--- Maximus/UNIX 3.03