> Area : (fido) Telegard Support
> Date : Mon 28 Aug 1995  10:16p             Msg # : 255/281
> From : Michael Yadron                      Reply : None
> To   : All                                Status : None
> Subj : PRESS RELEASE:  UPDATED FEATURES LISTING

TELEGARD 3.0 UPDATED FEATURES LISTING

KINGSTON, ONTARIO - August 28th, 1995 - Over the past 16 months, we have
been developing what has become known as "Telegard 3.0".  The following
information is an update to the features announcement that we made in
November, 1994.  NOTE ALL UPDATES TO THIS FILE HAVE BEEN MARKED WITH "|" IN
THE FAR LEFT-HAND COLUMN.

For the development of 3.0, our goal and priority has been to move the
software into the future.  Many of the features in 3.0 are new to the
software and have been written from ground up.  And while some of the
features are available in other BBS packages, 3.0 marks the first version
that they will be coming to Telegard.  We are attempting to enrich the
usefulness of Telegard without changing the interface which has made
Telegard a popular and user-friendly bulletin board system.

What follows is a brief synopsis of what the Telegard 3.0 release contains.
Any item marked with "2" will not be available until Gamma-2 has been
released, at least a couple of weeks after the initial Gamma-1 release.

     _____________
     MESSAGE BASES

     The message bases have been redesigned from ground up.  They
     incorporate many of the powerful mailing features that are now
     expected by mosy bulletin board systems operators and users.

|    * Support for two standard message base formats; JAM and Squish.
|      These message base formats replace the proprietary format which
       Telegard users have come to hate (and some love, but I don't think
       there are many of them).  With these standard base formats, there
       will be many more options available for utilities and message bases.
       Programmers will even be able to use one of the various toolkits and
       interfaces to program for Telegard and the new message base formats.
|      Fido *.MSG support was slated for release in TG 3.0, but since the
|      format is extensive (ie, not very standard) it was decided that
|      JAM and Squish could fulfill the message base needs for TG 3.0.

|    * Support for messages up to 64K (65535 bytes) in length - eclipsing
|      the old maximum of 32K.  The message writing buffer is also 64K,
|      over 800 lines at 80 characters per line (nearly four times as large
|      as the previous buffer of 200 lines).

     * Support for a maximum of 32000 message bases - a combination of any
       type of the message base formats (JAM/Squish).

     * Support for internal QWK mail.  QWK functions include uploading and
       downloading of mail, separate base selection lists, network mail
       uploads (QWK mail network hubs) and offline user configurations.

    2* Support file attaches (between users and in public conferences by
       security).  File attaches will be available for optional download
       and will be removed after being downloaded from any private area.

    2* Support for carbon copying (multiple messages) by security, and
       allows a user to forward messages to various users after the message
       has been received.

|    * Support for full-alias messages, including anonymous messages
|      and alias messages.  Telegard still fully supports all the formats:
       realname, alias, optional anonymous, forced anonymous, anyname
|      (selection) and dear "abby".  Both Squish and JAM formats support
|      these extended types in different ways.

     * Support for external editors was expanded to provide all dropfile
       formats and the external information file MSGINF which contains
       posting/message base information.

     * Support for multiple netmail bases was built in based first on exact
       address matches; second on zone matches, and as a tertiary method,
       the first netmail base encountered.

|    * Support was completed for full UUCP interaction via gateway
|      programs.  UUCP support includes different prompts for netmail
|      gateways, automated "ALL" posting and UUCP message formatting.

    2* Support for subject scans.  Text body scans will be implemented for
       Telegard 3.0 to be used in larger areas where subjects are often
       wrong or misleading.

     __________
     FILE BASES

     The file section was redesigned from ground up.  While the look and
     feel of the previous Telegard was maintained as much as possible, many
     of the features that have been missing from Telegard for a long time
     have been added to the file areas for this release.

     * Support for a maximum of 32000 file bases.

     * Support for CD-ROM drives.  All files from CD-ROM drives will be
       stored in a temporary directory before the download begins so that
       file protocols will not struggle trying to get the file from the
       CD-ROM in intervals.  CD-ROM support also includes automated
       detection of the CD so that files are automatically 'unavailable' if
       the correct CD is not in the drive.

     * Support for global file downloading (optionally toggled off).

     * Support for extended descriptions of up to 26 lines in length.

     * Support for automated importation of FILE_ID.DIZ/DESC.SDI
       descriptions so that the author-intended description is correctly
|      imported into the file bases.  Telegard will also attempt to
|      reformat the files if the files are not of the correct format.
|      NOTE: THE _CORRECT_ FORMAT IS 10 LINES @ 45 CHARACTERS PER LINE.

     * Support for upload/download queues in batch/single file protocol
       modes.  Upload/download queues can be used to store files and
       download in blocks at a given point in time.  Downloading in blocks
       also allows the download of descriptions of files that are
       transferred.

     * Support for file tagging from the menu prompt or during file
       lists/searches.  Tagged files will be added to the download queue
|      for downloading.  File tagging can be done by filename, or by
|      file number, allowing multiple files to be tagged at once.

|    * Support for advanced index system making file downloading and
|      searching faster when using full filenames/file tagging, providing
|      almost immediate reaction to file requests.

     * Support for default protocols so that protocol selection need not be
       done every time a file is downloaded.

     * Support for bi-directional protocols to allow uploading and
       downloading at the same time while in the file bases.

     * Support for daily download limits (KB and number of files) so that
       restrictions can be created by security level to limit the number of
       files that can be taken daily.

|    * Extended graphical specification support for BMP and JFIF (JPG)
|      files.  Resolution and colour (as well as version header)
|      information will be optionally added to file descriptions.  This
|      adds to the support already existing for GIF (87A/89A) files.

|    * Support for TESTINFO.DAT external tester data file - for automated
|      importation of conversion and description information, as well as
|      file status after testing with upload tester which creates
|      TESTINFO.DAT data file.

|    * Support for internal (TG) RAR file viewing, adding to the already
|      supported ARC/PAK, ARJ, LHZ, ZIP and ZOO viewing.

|    * Internal file maintenance including updating of file sizes, dates,
|      offline status, file points, importing FILE_ID.DIZ files and adding
|      graphical specifications (see above for formats supported).

     _____
     DOORS

|    * Support for the two standard drop file formats: DOOR.SYS and
|      DORINFO1.DEF.  Additional support for PCBOARD drop file format
|      (PCBOARD.SYS) and WWIV dropfile format (CHAIN.TXT).  External
|      support provided via scripts includes Solar Realms dropfile
|      format (DOORFILE.SR), the Wildcat! dropfile format (CALLINFO.BBS),
|      and the Spitfire dropfile format (SFDOORS.DAT).

|    * Support for advanced swapping for doors (turn door swapping off
|      for certain doors).

|    * Support for advanced door timing (turn door timing off for certain
|      doors).

     * Support for script language for quick-drop file programming (see
       later section for further information on script files).

     * Support for file updates to all Telegard data files.

     _________
     MULTINODE

     While these hooks have been added for Telegard 3.0 and have been
     tested fairly extensively, this does not make the system multinode
     compatible.  When the release is made, it will be as close to
     multinode ready as possible - those that wish to try it, however, are
     still doing so at their own risk.

     Complete multinode support will be added in a subsequent release --
     including who's-online lists and node-to-node messages and chatting.

     * Support hooks for multinode.  While multinode isn't officially a
       part of Telegard 3.0 (it will be in a subsequent update), the hooks
       for multinode have been completed.

     * Support for file sharing so that all files will be opened in the
       correct mode.  Files will be opened, updated and closed.  Files
       which are open for greater periods of time will have their first
       byte locked, meaning that the file shouldn't be updated until after
       it is unlocked.

     * Support for multiple modem setups and command line switches to
       segregate the node information (i.e. node 1 will store it's vital
|      information in \TEMP1\ and node 2 in \TEMP2\).  These important
|      files include door drop files, message base temporary files and
|      several new files including transfer queues, base tables and iemsi
       information files and sysop logs.

     _________
     LANGUAGES

|    * Support for multiple languages.  Complete definitions of all strings
|      for any number of languages.  Well over 1500 strings are available
|      for definition - with string lengths being unlimited.  With the
|      script and display file extension, the power of the language support
|      is still unrealized.

     * Support for alternate menu/text paths for each language, so that
       each language can have it's own set of menus and text files.
       Alternatively, the language set can use a default menu/text set.

     * Support for customizable date formats for international users - date
       formats include MM/DD/YY, YY/MM/DD and DD/MM/YY.  The formats are
       used for all date displays and date input fields.

     * Optional support for extended characters in all user information
       fields to support languages which commonly user characters found in
       the eighth bit (characters 128 to 256, including accented and
       special characters).

     _____________
     MISCELLANEOUS

     * Support for modem speeds of 300 to 115200 bps.  Support includes
       complete customization of VERBOSE result codes (no more messy
       numbers) and ARQ connections (for modems which support this feature).
|      Also built in was a hardware extension platform which allows some
|      measurable portability between releases to upgrade the connection
|      rates for various modems with just a simple data file.

     * Support for extended HISTORY.DAT files and LASTON.DAT files which
       record more information and store the information so that can be
       displayed online.  New commands include caller listings (which can
       be customized by the number of days to go back - for instance, a
       yesterday's caller listing) and various HISTORY.DAT graphing
       functions.

     * Completely updated sysop controls.  A new sysop window system which
       displays all vital information in various sysop windows (all under 4
       lines in total used space).  The SysOp control keys were all redone
       to be ALT-KEY activated, replacing the often confusing and misleading
       series of ALT, CTRL and FUNC keys which the previous versions have
       used.

     * Support for extended security measures, including random passwords
       and automated password replacements (after specified period of
       days).

     * Support for multiple colour system - two varying colour systems
       which support up to 256 colour combinations - foreground, background
       and blinking attributes.  One colour system is easier to understand,
       while the other one is more compact and allows SysOps to add more
       colour into tight string spaces.

     * Support for Remote Imaging Protocol (RIP) and full support for
       Avatar graphics protocol.  Advanced fallback also includes ANSI or
       text modes.  Support includes the sending of .RIP/.AVT files along
       with the standard .ANS and .MSG files.

     * Support for extended MCI sequence.  The MCI sequence has been
       expanded from 26 combinations to nearly 100, including all required
       user and system information.

     * Support for IEMSI logon sequences allowing users with IEMSI to
       automatically login as users and new users (both optional toggles).

     * Support for definable newuser and logon sequences, including
       information collected and forced values, etc.

     * Support for a completely indexed user system, removing user numbers
       from use within Telegard.  The indexed system allows the userbase to
       be packed, sorted and manipulated without the loss of data elsewhere
       in the system.

     * Completely new user editor includes all information in the userbase,
       down to the last statistics and fields stored for each user.

     * Support for a programming-like script language.  The script language
       is capable of getting and storing information, comparing
       information, writing text files, counting loops, etc.  The script
       language is fully integrated into the system and can be used to
       customize various parts of the BBS.

     * Support for external definition files - *.ADF, *.PDF and *.MDF,
       which contain information on archivers, protocols and modems for
       easy installation into Telegard.  Default definition files have been
       included for most popular archivers, protocols and modems.  This
       also allows the easy distribution of working setups and
       configurations through network mail and file distribution systems.

     * Support for external sysop paging files/programs.  Paging files can
       be customized and programmed with various tones (to create tunes of
       course), or an external chat program can be used in place of the
       internal one.

     * Support for numerous validation levels, which allow for quick
       upgrading to predefined flag and access settings.

     * Support for user subscription system, including automated expiry
       dates and expiry levels.  Subscription system is based on
       subscription date, length of membership, and level of membership
       (based on validation levels).

     * Support for timebank storage system based on security level includes
       daily deposit and withdrawal limits, and maximum account limits.

     * Support for special logoff sequences - including exiting without
       hanging up, and logoff cycling (logging the user off and returning
       back to the logon name prompt).

     * Support for automated rebuilding of damaged/missing files.  No more
       messy installation programs or external update utilities required.

     __________
     STRUCTURES

     * Every telegard structure has changed since the previous version (if
       there are any left standing, it is a real surprise to me and you'll
       have to tell me so I can take care of that as soon as possible. ;)

|    * The final structures for Telegard 3.0 are available as TGDEV300.ZIP.
|      There will be a follow-up release (the first Telegard Programming
|      Reference file), which will have sample access source code, as well
|      as sample data files as created by Telegard.

|      The TGDEV300.ZIP file is available from any of the development sites
|      which are listed at the end of this announcement.  The file size is
|      ~60k, the file date is 07-03-1995.  The file contains C/Pascal
|      structure files as well as complete development document.

     _____________________
     PROPOSED RELEASE DATE

     Telegard 3.0 will be released in gamma versions first.  These gamma
     versions will be public betas which can be run by systems as we move
     toward the final 3.0 release.  We have planned about two or three
     gamma versions before the final release.

     Since these versions will be gamma versions, there may still be minor
     bugs and problems that need to be worked out.  Some planned features
     may not be fully implemented in the first gammas, but will be added
     as the development and testing move forward.  The gamma versions are
     nothing more than relatively tested beta versions -- they are still
     test versions and should not be considered "complete".

     Any SysOp can run the gamma versions when they are released.  However,
     no guarantees are made about the quality of the software in gamma form
     and SysOps are asked to use their own judgement -- the responsibility
     is in the hands of those who choose to run the gamma versions.

     The first gamma release has been scheduled for SEPTEMBER 9, 1995.
     Barring any unforeseen problems, the gamma will be released on this
     date and sent out as TG_299G1.ZIP.  As we move closer to this date, we
     will naturally verify this information and also announce the
     distribution sites where the gamma will be found.

     _____________
     DOCUMENTATION

     Telegard 3.0 will be completely documented at the time of release.
     Gamma documentation will be provided with all gammas and will be
     completed as we move toward the final release.

     _________
     PLATFORMS

     At this time, Telegard is only being programmed for DOS.  The reason
     for this is that we would prefer to have a stable product before we
     attempt to cross over to OS/2 or Windows platforms.

Although this list is fairly comprehensive, only highlights were chosen to
represent each area.  There are countless other changes which have not been
included in this feature listing -- the changes from 2.7 are fairly
phenomenal and will take some adjustments to get used to.  I do hope that
this information will provide insight into the direction that development
has taken.  Many of these features should be welcome additions to your
system.

Thanks for your interest in Telegard 3.0.

                                                                Tim Strike
                                                            Michael Yadron

                                                       TELEGARD BETA TEAM:
                   Michael Bogden, Paul Dyer, Ernest Evert, Hugo Ferreira,
                 Lars Hellsten, Derek Hessman, Brent Johnson, Don Johnson,
                  Jeffrey Johnson, Peter Laur, Perry Lowell, David Luckie,
                  Deanna Luke, Scott Malin, Lucas Nealan, Clint O'Donnell,
     Michael Randolph, Jack Schofield, Steve Shapiro, Carol Shenkenberger,
      Michael Smith, Gary Stewart, John Tabler, Dave Turner, Kevin Watkins

