BJ> With maximus there are TWO terminals 
 BJ> involved, the user's (which they control, but 
 MK> needs to be a VT-100 or 
 BJ> better)

 MK> Yep.  I need to set a few things up.  I tried logging 
 MK> in via telnet but it punted me after the login.  So I 
 MK> never got to the point where I could see if the linux 
 MK> term works.  Getting there.

Ah....  The last I knew, the telnet was broken in the CVS archives.  Bo has
a workaround to get the telnet stuff working, but the last I knew we hadn't
gotten the CVS archives "fixed" for this.  Wes was working on the
serial port stuff and I believe something fixed there "broke" the
telnet stuff....  And then Wes got real busy with work and family.....  So,
this is on our list to fix, but....  Ask Bo for the library that needs to
be replaced with an older version (from the original Linux/Unix port of
Max)....

 BJ> and the terminal window that is the console for Maximus.  It 
 BJ> is the console window for maximus (especially when run with 'bin/max 
 BJ> -k') that needs the ANSI setting to get color working.

 MK> Yeah.  Very DOSie or OS/2ie except the keyboard and 
 MK> colours.  Strange seeing that on a linux console after 
 MK> all these years.  Getting old and spoiled.  What can I 
 MK> say?  I think I need to look at that aspect of the code.

 Well, I think you might also consider it slighly unixy if you
were used to using Unix befor X-Windows.....

 MK> However, I am making headway on the message areas and 
 MK> was wondering if there is some info on sqafix 
 MK> configuration.  Once that is done then I am seriously 
 MK> thinking that the menuing etc needs a hard look at as 
 MK> far as terminals go.  I know you want this to be 
 MK> portable but to get it running efficently on Linux I am 
 MK> thinking ncurses.  What do you think?

For SqqFix.Cfg, see the documentation in the last DOS / OS/2 release of
SqaFix (99b8) and then add the info from my sample SqaFix.Cfg file and
related log documentation.....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01