TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Bob Jones
from: Bo Simonsen
date: 2003-05-28 18:09:22
subject: Maximus at UNIX

Hello Bob!

May 27 18:59 03, Bob Jones wrote to Bo Simonsen:

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

 BJ> Ah.....  maximus has I believe two mecca files that are shown to a 
 BJ> user on the first few calls.  There is a new user (initial login 
 BJ> sequence) and then a thanks for comming back / here's some more 
 BJ> startup info sequence....  Maybe Max is getting hung up on processing 
 BJ> this second set of files?

Hmm.. can you remember the filenames of those scripts?

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

 BS>> I guess it's not 8bit, because things like filetransfer 
 BS>> doesn't work.. but i don't know mutch about the telnet module.

 BJ> Ok.  File transfers can get killed from either 7 bit or because of 
 BJ> control character interpretation.....  Concerning file transfers not 
 BJ> working, the standard telnet does not support maximus's file transfer 
 BJ> protocols.  But if you know what you are doing (or use a differnet 
 BJ> terminal package) things should work.....

Yes that was what i believed.

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

 BJ> I figured some of that was hard coded.  Not nice in a unix 
 BJ> enviornment where a TERMCAP or CURSES library should be used instead 
 BJ> (old school Unix thoughts).  Now, with almost all folks emulating the 
 BJ> terminal as a VT-100 work-alike, it is less of a problem......  
 BJ> Hmmm....  I wonder if the exchange sequence includes a control-s from 
 BJ> either end?  I recognize the \033 as escape, and the (U is one of the 
 BJ> functions (following an escape character)....

Well you need \033(U to see the normal .ans files graphic.

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

 BJ> I've only run the BBS with hardware flow control due to the software 
 BJ> flow control issues.  But I have needed flow control with my setup 
 BJ> using modems.

Ok.

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

 BJ> Then you are probably defaulting parameters on opening up the TCP 
 BJ> socket.  I thought the default was 8 bit clean, and doesn't inturpet 
 BJ> control characters, so I'm probably barking up the wrong tree on this 
 BJ> one.   [On the other hand, if one option for opening the socket is to 
 BJ> setup for telnet, then 7-bit / flow control issues may be the 
 BJ> problem.]

Well i have not coded the telnet module, so i really don't know about it.

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

 BJ> I think eventually max needs to be able to take a hand-off from 
 BJ> either mgetty or inetd.  

Well i don't think.. If i run the BBS, i've no chance to run a mailer too..
I don't know how mutch you know about mgetty..

But then it's get a "RING" from the DTE, i would answer the call,
and then figure out what the call is..

If you set it up it can figure out, if it's a PPP connect, or a mailer and
at last a human call..

 BJ> Max will need to be able to test (using the 
 BJ> IOCTL functions) for handling modem hardware flow control and to 
 BJ> control DTR (to hang up the phone) if it is to replace my existing 
 BJ> setup.  The hooks should already be in Max.  It's just a matter of 
 BJ> figuring out (a) the IOCTL functions to use and (b) wether they 
 BJ> should be called....  Another item is that Carrier detect from the 
 BJ> modem should be tied to the TCP socket disconnect for TCP based 
 BJ> connections.

I see your point..

BTW max is getting better day for day.. i've been making several changes in
the MSGAPI, so squish is working very good, except for it has some problems
about dupechecking, but it has them too with *.MSG, and i can't figure out
the problem, maybe wesley can..

BTW it's only if dupechecking should be out from msgid or msgid and
header... i run only specified header there is no problem..

Regards,
Bo

--- Msged/LNX 6.1.2
* Origin: Downlink BBS * Roennede, Dk * telnet geekworld.dk (2:236/100)
SEEN-BY: 633/267 270
@PATH: 236/100 237/9 20/11 106/1 2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.