
ALTAIR v1.20 Gamma
Released October 28, 1996
Expires January 1st, 1997
-------------------------

Welcome to the first ever Gamma release of ALTAIR.  We have released this
version to the general product for a number of reasons.

   1.  ALTAIR v1.20 includes some signifcant improvements and fixes from
       the lateset v1.16a release.  While v1.20 is not due to be released
       until the end of the year, we felt it necessary to provide you, the
       users of ALTAIR, with what we had accomplished so far since it does
       address a number of key issues that users are encountering.

   2.  The inclusion of Searchlight and PCBoard 15.x support has made the
       task of gathering a variety of beta testers more difficult.  So in
       order to test ALTAIR more in depth, we have released this stable,
       but still Gamma version for the public to use and provide us
       feedback on that we will use in the completion of v1.20

   3.  We want ALTAIR v1.20 to be the best release of ALTAIR to date and
       to accomplish that, we need as much feedback as possible from users.

Legal Stuff
-----------

ALTAIR is a shareware product even in its Gamma form.  It requires
registration if used past the 30 day evaluation period.  This version of
ALTAIR will not function after January 1st, 1996 and includes a time delay
upon startup.  After January 1st, either a Gamma 2 or the final version of
v1.20 will be made available.  Use of this Gamma version does not entitle
you in any way to a registered version of ALTAIR except by registering the
product as explained the the registration forms.

Installation
------------

If you are already a previous version of ALTAIR, make a backup copy of your
ALTAIR directory.  Then copy the contents of this archive into your ALTAIR
directory and run the SETUP program to configure the new settings.

If this is a new installation, create your ALTAIR directory and copy the
contents of this archive into it.  Double click on the INSTALL.REG file
using the Windows Explorer to create a default installation and the use
SETUP.EXE to configure your settings.

Documentation
-------------

With that said, here is the "documentation" for this version.  Refer to the
v1.15 documentation included with this package for most items.  This file
includes the changes that have taken place during the development of ALTAIR
and you should take care to read this and note the setup changes.

What's new in v1.20 Gamma?
--------------------------

The following is a list of improvements in ALTAIR.  They are listed from
the most newest to oldest.  To read from v1.16a->v1.20 start at the end.
Items marked with a * are the most important and often represent changes
in the operation of ALTAIR as opposed to a bug fix.

      *  Added tossing/scanning/purging support for Searchlight 4.5/5.0
         message base format.

      *  Rewrote all scanning routines to use memory mapped files.  This
         was done to speed processing and to support messages of unlimited
         size.  This beta now supports unlimited size scanning.  Unlimited
         size tossing is only limited in some formats by a 32k buffer that
         will soon be removed.

      *  Rewrote ALTAIR routing routines.  Routing now works as follows for
         ALTAIR for both Front Door and Binkley Style Mailers.

            Each node in the node manager can be configured to have
            outbound mail routed to it.  In order to route mail to
            a node, it must exist in the node manager.  Once a node
            is configured, a list of addresses is defined as being
            routed to that node.  This routing definition can be set
            as Netmail Only, Echomail Only, or Both.  

            During the compression stage, ALTAIR will first send
            any netmail packets to the destination node and route them
            accordingly.  It will also compress all echomail that is
            routed to the destination node into a single archive and
            send that archive to the destination.

         This was done to allow for "netmail packing" which is supported
         in many mail tossers.  To use netmail packing, configure a node
         in the node manager.  In the routing configuration for that node,
         list the addresses that will be routed *to* that node.  Then mark
         the routing to be netmail only.  This will cause ALTAIR to send
         any netmail destined to the configured address list to the node
         instead.  Make sure that you turn on the "Bundle netmail" option
         or ALTAIR will not process your netmail messages.

         ALTAIR no longer ignores routing when configured for FD style
         operation.

      *  Fixed major bug in ALTAIR's netmail scanning that would cause
         ALTAIR to not scan out netmail destined for a downlink that was
         received via a toss command.

      *  Changed setup program extensively including new origin (on the
         Area Manager) and AKA (General Options) entry.

      *  Fixed bugs in the auto-add feature of ALTAIR that would cause GPFs
         when it was used.

      o  Added the ability to use the ALTAIR TOSS SCAN command line option
         to perform and toss and scan in one pass.

      o  Modified setup program to allow keyboard command entry for most
         functions.

      o  Fixed problems with scanning not removing existing tear and origin
         lines.

      o  Fixed problem with *.MSG and the Bundle Netmail option being ignored

      o  Fixed some bugs with netmail tossing and zone/point recognition

      o  Fixed bug in Binkley style support for point sites.

      o  Fixed some bugs in the AREAS.BBS importing.

      *  ALTAIR now uses two separate directories for netmail and ARCmail
         attach messages used by Front Door style mailers.  This allows
         you to have a netmail base separate from your attach messages
         allowing for Squish, JAM, or any other message base format to be
         used as a netmail base.  These can be the same if they are both
         *.MSG and the sysop desires it so.

         Along with this is a new flag on the General Options screen while
         instructs ALTAIR how to bundle netmail.  By checking the box,
         ALTAIR will put your netmail in .PKTs during scanning.  By not
         checking the box, ALTAIR will not scan your netmail, leaving it
         to be handled by another piece of software.

         ALTAIR will also now delete messages scanned in the netmail
         directory marked with the "kill when sent" flag.

      o  There is now a setting on the node configuration to mark whether
         or not that node is included in the NOTIFY command.  And, as you
         can gather, typing ALTAIR NOTIFY will send a netmail message to
         each configured node about their system and the ares they are
         connected to.

      o  Fixed bugs in PCBoard 15.22 tossing and scanning that should now
         work correctly.

      o  Fixed some problems with the PowerBBS 4.5 tossing.  This should
         resolve the need for PBBS 4.5 sysops to run PowerPack after every
         toss.

      o  Fixed some bugs in the setup program that would clear information
         during setup and other minor issues.

      o  Fixed problem in AREAS.BBS importing that would not properly
         import JAM areas

      o  Fixed bugs in date/time routines on all message base formats

      o  Fixed bug in Spitfire routines that may cause some systems to
         not recognize more than 100 areas.

      o  Fixed problems in JAM tossing that was causing memory errors.
         Also fixed problems with JAM seen-by and path lines.

      o  Added support for the PCBoard 15.x message base format.

      o  Option to keep inbound area manager requests.  As of v1.16,
         ALTAIR by default deletes inbound area manager requests after
         they are processed.  This option on the General Options screen
         controls this behavior.

      o  Added support for multiple logging levels.

            Level 3 - All entries (debug mode)
            Level 2 - Standard entries plus external program information
            Level 1 - Standard entries only

      o  Areas can now be marked as mandatory so that nodes cannot
         disconnect from them using area manager commands like -<AREA>


If you have any trouble, support is provided only through myself.  Direct
all problems, suggestions, etc to KEVIN_KUPHAL@msn.com or via netmail to
Kevin Kuphal at 1:115/859

Kevin Kuphal
