
Log of work done on ORACOMM

The main command menu files are MENU and AMENU.  If the account is a sysop
    account, send MENUSYS and AMENUSYS instead which can have the sysop
    commands.

+f new option C will allow changing the msg llo.  This is useful for node
    accounts to reset the echo msgs transmitted.
3/5/90
Even if Oracomm detects caller at 7e1, allow him to download but send warning
    msg in case noisy lines leads to a false 7e1 detection.

In miniterm mode, send out the +++ and ATZ automatically after baud rate.

Permanent Oralink:  Two or MORE nodes (up to 16 nodes for 240 users) can be
   connected in permanent Oralink.  Just set the IL command for the line
   to be permanently connected to modem type D and Network call C (continuous).
   Baudrate is normally 9600 baud.  In the cable connecting the two systems,
   be sure that carrier detect, pin 8, is high such as jumping it to pin 4.
   This will allow the users on one node to chat with users on the other node
   at all times.  It is useful if one sysop is running a straight and a gay
   bbs on separate computers at the same location.  If necessary to terminate
   Oralink, you can use X to shut down that line from the control window.

If a echo msg comes in which does match an echo board, check to see if the
    msgno on that echo board already exists.  If it does not, add the msg 
    but do not change the msg number.  If it does, read the header and see 
    if the source nodes match.  If they do, do not save the msg in an attempt 
    to remove duplicates.   If the source nodes do not match, add the msg but 
    do not change the msgno. 

CHAT /acct:  In chat, only the first character of the command is recognized.
    This caused problems if a user entered "/bobc howdy" to account bobc
    since if bobc logged off, Oracomm would assume it was a bring command.
    To clarify the command to send a private line to a specific user, now
    there is a /TO command (or just /T(space)) to send it to that account
    specifically.  The above command would then be "/to bobc howdy".
    The /account will no longer work.  It must be /TO ACCOUNT and there
    must be a space between /TO or /T and the account.
    Be sure to change menuc and helpc for this change.

Disabled echo board feature except for those systems specifically requesting
   it and who are aware of the ramifications of it.

8-n-1: Since so many users do not know how to switch their software to 8-n-1,
    Oracomm will now detect 7e1, put out a message warning users to us 8n1,
    but allow users to use MOST features even with 7e1.  It will NOT allow
    the U or D commands since crc checks require 8 bits and the protocol
    transfer will not work with 7 bits.  A separate version will be available
    for European systems requiring the full 8 bits.

Add the following 2 lines to PROMPT4 in the utility help file:
491 \nPlease reset your modem program to 8 data bits, 1 stop bit, NO parity.
492 \nProtocol transfers will not work with 7 data bits.

RTS/CTS:  Since the Practical Peripheral modems appear to hang the system
    when rts/cts flow control is used with them, there is now a new modem
    type (as entered with IL command) of P.  P is similar to H and C except
    rts/cts flow control will NOT be turned on.  This occurs not only
    during normal user logon, but also if a PP modem is used on Outside Feat.

Network Echo Boards and SIGS:  In an effort to limit what network nodes
    get an echo board without forcing the board to be a sig and have each
    user account set to that sig, the following change was made.  An echo
    board does NOT have to be defined as a sig, but the echo board must be
    listed in the sig list of the network node to be able to access it.  That
    way the board abbreviation only needs to be put in the node account and
    not every user account.  The ? wild cards DO apply and can be used to
    give a node access to all echo boards.

Oracomm 5.0 does a DOS call to open more than 20 files.  DOS3.3 apparently
    takes more space than is needed creating an out of memory condition for
    10 and 17 user systems.  An interim solution was to not have Oracomm do
    the call automatically, but only do it if a parameter of FILES was used
    when Oracomm was called.  This created problems since it was inconsistent
    with the documentation.  For this reason, Oracomm will do the file
    expansion DOS call unless you add a parameter of NOFILES on the line
    when starting Oracomm.  If you use NOFILES, you can then the files3x.com
    or files33.com program to allow DOS to open more than 20 files.

Greenleaf Comm 3.0 used on all 5.0 systems compiled after this date.

