this is a manually forwared message that I sent to Bo via netmail.
Having problems getting the actual netmail out  as his computer isn't
answering the phone. (its not busy either.)


===========================================================================
  BBS: Planet Maca's Opus
 Area: MUFFIN (Reply)
 Date: 05-11-04 18:22
 From: B'ichela
   To: Bo Simonsen
 Subj: Max? serial ports
 Stat: Pvt 
---------------------------------------------------------------------------
-=> Bo Simonsen{at}2:236/100 wrote to Michele Marie Dalene <=-


 BS> To: Michele Marie Dalene{at}1:142/7176
 BS> I saw you did have problems with Max/UNIX.
 BS> 
 BS> 1. To get telnet running, you need to read README.2ST really carefully.
 BS> I changed a bit, so I'll still have the availbility to spy on my users, 
 BS> but 
 BS> you'll require the thirdparty program screen.
        I figured that out after I posted but I do got a serial port
question. when Max is waitng for a call (in this case on /dev/ttyS2
why does it do this in the logs endlessly?
+ 11 May 17:47:03 MAX  Begin, v3.03 (task=1)
: 11 May 17:47:04 MAX  Waiting for caller (event in 1440 mins)
! 11 May 17:47:05 MAX  Carrier lost
! 11 May 17:47:06 MAX  Carrier lost
! 11 May 17:47:07 MAX  Carrier lost
! 11 May 17:47:08 MAX  Carrier lost
! 11 May 17:47:09 MAX  Carrier lost
! 11 May 17:47:10 MAX  Carrier lost
! 11 May 17:47:12 MAX  Carrier lost
! 11 May 17:47:13 MAX  Carrier lost
! 11 May 17:47:14 MAX  Carrier lost
! 11 May 17:47:15 MAX  Carrier lost
! 11 May 17:47:16 MAX  Carrier lost
! 11 May 17:47:17 MAX  Carrier lost
: 11 May 17:47:18 MAX  Exit by keyboard request
! 11 May 17:47:18 MAX  Carrier lost
: 11 May 17:47:18 MAX  End, v3.03 (1)

        Now obviously ONE carrier lost would be fine but why an
endless loop of them? Because its busy with carrier lost reports it
never answers the modem! what do you need to put in my max.ctl file to
have it work right? I remember from my Opus days you need to turn Echo
off with ATE0 anything else? Max would be answering the phone by
itself.
Also when the software exits. why does it not erase its
/var/lock/lck..ttyS2 file? I am talking about during a normal Alt-X
exit.
        The modem is initted fine. then the carrier lost loop starts.

Heres my equipment section of my max.ctl file

Equipment Section

        % The 'Output' keyword tells Maximus where to send its output,
        % whether that is the local monitor, or a COM port.
        % Specifying 'Local' for local output is generally
        % unnecessary, because the '-k' (keyboard) command-line parameter
        % does exactly the same thing.  Only COM ports from one through
        % eight are supported -- also note that your FOSSIL must support
        % the COM port you wish to use.  Please consult your FOSSIL
        % documentation if you're using a port other than COM1: or
        % COM2:.  By default, Maximus will use COM1: if no 'Output'
        % statements are given.
  
%        Output  Com1
% the binkleyterm sets on /dev/ttyS1 (com2) my test was on that modem
% when binkleyterm was shut down.
       Output  Com2
% I also have fax/modem on ttyS2  which I also tried with the same
% results
%       Output  Com3
%       Output  Com4
%       Output  Com5
%       Output  Com6
%       Output  Com7
%       Output  Com8

%       Output  Local

        % The following statement specifies the highest baud rate that
        % your system can support.

        Baud Maximum    38400

        % This is the command that Maximus will send to the modem when a
        % user logs off.  Everything in this string is sent as-is to
        % the modem, with the exception of the following special characters:
        %
        %   v : Sets DTR low
        %   ^ : Sets DTR high
        %   ~ : This pauses for one second
        %   ` : This pauses for 1/20th of a second
        %

        % The following default string is a bit lengthy, but it seems to
        % work for all of the modems it has been tried on.

        Busy  v~~^~~|~ATZ|~ATM0H1|

        % The following strings are only required for the internal 
        % Wait-For-Caller command.  These strings use the same command
        % chracters as the "Busy" string.

        % This string is sent to the modem when the Maximus WFC 
        % (Waiting For Caller) subsystem starts up.  This should
        % initialize your modem and set the appropriate defaults.
        %
        % If you are running a high-speed modem (9600 or above),
        % the following init statement should include the &B1
        % option (to specify a locked com port).

        % For 9600 bps (or faster) modems:

        Init    ~v~````|~^``AT&B1E0H0S0=0|

        % For 2400 bps (or slower) modems:
        %
        %Init    ~v~````|~^``ATH0S0=0|

        % For a modem-controlled answering sequence, use the following
        % string, and COMMENT OUT the 'Ring' and 'Answer' strings.  Only
        % use this if your modem won't properly answer the phone.

%       Init    ~v~````|~^``ATH0S0=1|

        % This string is what your modem sends to the computer when
        % your telephone rings.

        Ring    Ring

        % This string is sent to the modem in response to a ring.
        % Normally, this command should tell the modem to take the
        % phone off-hook and to start the answer sequence.
        %
        % WARNING!  This command may not work for semi-Hayes-
        % compatible modems.  If Max isn't answering the phone at
        % all (and you're seeing a bunch of "Ring" messages in
        % the status window), try commenting out this statement
        % and using the "Init" statement (above) with an "S0=1".

        Answer  ATA|

        % This string should be returned by your modem when a connection
        % is established.  The link rate (300, 1200, 2400, and so on)
        % should follow the string you specify.  The following will
        % work for most Hayes-compatible modems.

        Connect Connect

        % This is the carrier mask to use for your modem.  If you
        % don't know what this does, then please leave it alone.  If
        % you *do* need to change it, then please remember that the
        % value is in decimal, not hexadecimal.

        Mask Carrier    128

        % The following three lines specify what type of handshaking
        % to use with your modem.  If you want your users to be able
        % to use ^S and ^Q to pause and re-start their screen display,
        % then you must use the 'XON' keyword.

        % Also, if you are running a high-speed modem (9600 or above),
        % CTS handshaking should be enabled.
        %
        % NOTE:  These statements have no effect when running under
        % OS/2.  Maximus directly inherits the port characteristics
        % from the calling process.  See the installation instructions
        % for information on setting up the port using the 'MODE'
        % command.

        Mask Handshaking        XON
        Mask Handshaking        CTS
%       Mask Handshaking        DSR

        % Use this if your modem requires a BREAK to clear its internal
        % buffer.  This is only necessary with modems that *do* have
        % an internal buffer -- generally, modems which are 2400 baud
        % or lower do not have an internal buffer and do not need this
        % keyword.  If you are not sure if you have an internal
        % buffer or not, check your modem manual for details.
        %
        % !!!!!!!!!!! WARNING !!!!!!!!!!!!
        %
        % Do not enable this option unless you are POSITIVE that your
        % modem supports this feature.  At present, only the HST
        % supports this function, and even then, the HST must be
        % set to AT&Y0 for it to function correctly.  If your
        % HST is not configured for AT&Y0, or your modem does
        % not support a "destructive, nonexpedited" break,
        % do NOT enable this feature.

%       Send Break to Clear Buffer

        % The "No Critical Handler" keyword tells Max to turn off the
        % internal critical error handler.  Normally, Max will fail
        % all critical errors, and continue with the BBS's operation.
        % If this behaviour is not desired, the following keyword can
        % be used to turn off the critical error handler so that
        % an external handler can be installed.

%       No Critical Handler
End Equipment Section

                                Michele Marie Dalene


... BREAKFAST.COM error: Cereal port not responding
-!- blueMail/Linux 0.11

--- blueMail/Linux 0.11
--- SBBSecho 2.00-Linux