様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様
Changes for TSDoor version 1.6
様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様

   *  Fixed a bug in the communication routines that, after several
      thousands of characters were sent through the com port, could cause
      the TSDoor program to slow down to a crawl.

   *  Changed the interpretation of the "Hayes V-Series Modem" flag in
      PCBOARD.DAT (set via the PCBSETUP program) to match the latest
      usage in PCBoard 14.5a.

   *  Changed the door to always start out in NON-Expert mode.  Callers will
      be notified that the menus can be toggled off/on via the X)pert command.

様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様
Changes for TSDoor version 1.5
様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様

   *  Modified the com port initialization routine (per Phil "Pib" Burns ...
      many thanks, Phil) to compensate for a problem causing gibberish to
      be sent out of the comm port on certain AMI bios (and perhaps others)
      machines when running LanTastic v3.0.

   *  Modifications for PCBoard 14.5:
      -  TSDoor REQUIRES a PCBoard.Sys file AND a Users.Sys file.  You MUST
         modify your DOORS.LST file (via PCBSetup) so that this file gets
         created when a caller enters the door!
      -  Start/Stop times for sysop paging are now supported
      -  Removed the code used to insure that a sliding event would not be
         missed ... the new fields in the PCBoard.Sys file make special
         handling of this situation unnecessary.
      -  Upgraded the asynch communication routines to handle com ports
         other than COM1: and COM2:

   *  Keywords found in text are highlighted with inverse video rather
      than bright white

様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様
Changes for TSDoor version 1.4
様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様

   *  & is now a synonym for the boolean AND operator and is accepted
      along with + in the search string expressions.

   *  The search engine has been enhanced to allow parenthesized search
      expressions.   This allows the user to override the default precedence
      of the boolean operators & and |.

   *  Removed code that checks for a CNAMES file (this door really doesn't
      need it anyway) so that systems that attempt to run PCBoard doors on
      non-PCBoard systems will have a better chance of succeeding with TSDoor

   *  Callers who use ANSI graphics mode will have search keywords highlighted
      in the found text.

   *  Fixed the Boyer-Moore search routine which would occasionally fail to
      match when it should.

   *  Modified the multi-line search routine to scan each entry in its
      entirety rather than one line at a time.  This means that searching
      for 'xxx + yyy' will now match an entry even if xxx is found on
      one line and yyy on some other line within the same entry.

   *  The above change has introduced some limits into the program.  To wit:
         -  No list entry can be larger than 10K in length
         -  No single line in any entry can exceed 255 characters
      a 'line' is defined in the usual sense as some string of characters
      followed by a carriage return and line feed.

様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様
Changes for TSDoor version 1.3
様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様

   *  Have added some functionality to the search engine.  A '?' character
      in the search string will now match any character in the target
      database file (ie. it's a wildcard character).  At this time, there is
      no way to quote the question mark to actually search for it (I'll work
      on that).  I also think I've found a bug in my 2 year old Boyer-Moore
      search algorithm that would occasionaly (very rarely) miss a match
      that should've been caught.

   *  Have changed the way sliding events are handled by TSDoor.  Callers
      will no longer have their time reduced due to a pending event IF that
      event is defined as sliding (in the PCBSetup program). This means that
      a caller may remain logged on past the event time. If that caller then
      logs off within the door, PCBoard would miss running the event.  To
      alleviate this, IF the caller remains on past the event time and IF
      that caller logs off from within the door, TSDoor will rename the
      event.sys file to event.bat.  This allows you to run the event from
      within the TSDoor door batch file.  The batch file for TSDoor should
      be changed to look something like the following

            Rem *** TSDoor Batch File ***
            If Exist Event.Bat Rename Event.Bat Event.Sys
            CD \TSDoor
            TSDoor Node1.Cfg
            CD \PCB1
            If Exist Event.Bat Event
            Board1

      This will insure that the event always gets run. Again, this change
      affects only those sysop who run a sliding event. For normal (ie.
      non-sliding) event systems, nothing has changed.

   *  Program was not properly handling time adjustments for upcoming events
      when extra time was added by entering a conference (before entering
      TSDoor).  Extra time granted in a conference is now properly accounted
      for.

   *  A "Press ENTER to continue" prompt has been added after display of the
      initial welcome screen(s), but only for non-Xpert callers.  This is to
      prevent the subsequent menu display from scrolling the info off the
      screen.

   *  Recompiled TSDoor using Turbo Pascal v5.5


   *  Modified the comm routine initialization code to properly enable
      RTS/CTS handshaking.

   *  Found dynamic memory that was not being deallocated after repeated
      searches.  Have taken steps to see that this memory is properly
      returned to the OS free memory pool.