Programmer 7500/MAX_PROGRAMMERS.iso/PROGRAMS/UTILS/COMMUNIC/K9X88D_1.ZIP/WHATSNEW.88

Text File | 1990-04-17 | 20.3 KB | 395 lines

           B E    S U R E    T O    R E A D    T H I S    F I L E

  This file contains information concerning each of the new versions of  K9X.
  All  changes  up  to  and  including  version  8.50 are now included in the
  various DOC files.

  All newer than v8.7c changes/additions covered in  this  file  replace  any
  information  contained  in K9X.DOC dealing with the same subject(s).  Since
  new features are added and old features  are  changing,  this  entire  file
  should  be  reviewed  (along with the K9X.DOC file(s)) before attempting to
  use K9X.  Most of the problems encountered are due to users not reading the
  documentation  before  "diving  in".  K9X is an intricate piece of software
  with many features other comm programs only "dream of having"!  Even if you
  are  fortunate  enough to get it up and running,  you will more than likely
  miss out on alot of features  that  would  make  your  modeming  life  alot
  easier! Please take the time to read the documentation!

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
K9X      v8.80   Dated  Dec01, 1989

   Let's see... where do I begin?! This version is a prelude to the switch to
   Turbo  Pascal v5.5 so there are a batch of changes!  To this end,  much of
   the code has been reworked and optimized...  resulting  in  fewer  overlay
   modules and a net decrease in total file size even with the new features!

   First and foremost,  the old K9X Configuration Utility has  been  rendered
   obsolete as it is now incorporated within K9X itself and,  since there are
   several new parameters saved within the K9X.CNF file,  DO NOT use the  old
   K9XCNF  utility  on the new K9X.CNF file!

   Please note:

      K9X will reset the  port  if  modifications  are  made  to  the  comm
      parameters  while  in  the  K9X  configuration section.  It WILL ALSO
      close the current port and open the new  one  if  the  comm  port  is
      changed (be careful)!

      K9X will not automatically save your default changes when exiting the
      configuration  section.  You  MUST save them via the manually via the
      menu selection.

      Since K9X saves all changes when it writes out a new K9X.CNF file,  I
      would suggest you only make/save your changes upon initial startup of
      the program rather than after several calls have been made.

   Consolodated  main  color  and  SuperK colors into one menu within the K9X
   configuration section.

   Added full color to all displays including incoming text!  Note: the color
   selection menu includes a Zmodem color.  Although this color scheme is not
   used in the current version,  it will be used when K9X makes  its  way  to
   Turbo Pascal v5.5 and internal Zmodem support is added.

   Added both Online and Offline Border color settings.

   Added  code  to auto-detect the existance of an EGA or VGA card - in which
   case,  K9X will NOT allow the use of the Line 26 status line.  This should
   eliminate  all  of  the  confusion that existed in earlier versions of K9X
   when started up in an EGA/VGA environment with Line 26 active.

   Added another text editor.  User may now select between the old  BBS  type
   editor  contained  in  earlier  versions  of  K9X  or the new full screen,
   PC-Write type editor.  Please note that there are several commands  within
   the new editor that have not been implemented yet.  The new editor has its
   own, built in help screens so I will not go into detail on its use.

   Added Zmodem autostart option.  Since K9X uses the external DSZ module, in
   Zmodem autostart mode,  there may be  times  when  the  transfer  must  be
   aborted.   The   results  of  a  premature  abort  may  send  K9X  into  a
   non-breakable loop as the sender continues  to  send  the  Zmodem  opening
   codes  and  K9X  interprets  each  opening  code as a signal to commence a
   Zmodem transfer!  To this end, I have added a "hidden" expert mode command
   key which will purge the incoming buffer and return control to  the  user.
   The  command  key is Ctrl-PgUp (NOTE:  This command key may be used at any
   time to clear the incoming buffer).

   Earlier versions of K9X sent an opening  D; and a final c/r when using the
   download buffers in single file mode.  Version 8.80 adds a user configured
   "add D;" flag.  When set to Yes, K9X acts as it did in earlier versions...
   when set to No,  K9X  acts  identically  to  the  Batch  mode  in  earlier
   versions... that is, it only sends the filename.

   Modified the processing of incoming characters.  All  incoming  characters
   are now passed to DOS for processing.

   Added  new  "Bells and Whistles" flag.  This flag setting effects only the
   internal menu bells and whistles and NOT any incoming sound control  codes
   sent by the host.  The "Quiet mode" flag controls the incoming sound.

   Modified many of the internal screen write routines for faster display.

   Added 38400 and 57600 bps modem speed support for you "Speed Demons"!

   In an effort to correct Comm 3 and 4  configurations,  I've  modified  the
   communications init routines so that K9X is more "Comm Port Aware".  These
   modifications  should also correct the "Mouse on Comm1 and Modem on Comm2"
   problem. (I NEED FEED BACK on this please).

   Modified the menu routines to include 3 dimensional shadowing.

   Modified the "Configure drives" section of the  configuration  section  so
   that  K9X  will create the K9X Drive table when only a default upload path
   is specified.

   Corrected  the  dialing  directory  input  problems  which  resulted  in a
   run-time error when you backspaced a number input  and  changed  it  to  a
   letter command.

   Modified the dialer "Connection Made" routines in an effort  to  eliminate
   the sporatic run-time errors present in earlier versions (still don't know
   what was causing them!).

   Modified the dial directory entry editor. Use the arrow keys to select the
   entry field you wish to edit.  You may also press the field  number...  in
   which  case,  K9X  will  automatically jump to that field and commence its
   edit mode.  Please note that K9X will not save any changes  automatically.
   You  will have to select the save option to write the changes to the K9X.P
   directory file. Pressing Escape at any time will return you to the dialing
   directory WITHOUT SAVE.

   Oh yes,  when things get too hectic for you and you need a break,  take  a
   stroll in the "Forest of Kalajan" via the Alt-0 key set or Command Gateway
   Info section!

                         Merry Christmas  and  Enjoy-


K9X      v8.8a   Dated  Dec06, 1989

   This is the first of the maintenance releases after "the big crunch"  code
   optimization performed in v8.8! It's purpose was to correct a oversight in
   the handling of the new 38400 and 57600 baud rates (sorry bout that)!


K9X      v8.8b   Dated  Dec21, 1989

   This version is dedicated to Matt Kyle who has  requested  the  option  to
   Link  scripts  and  load  the  PASSWORD.BBS information created by the PCP
   Dialer ADIAL! I have added a couple of new options here...

   <L>Filespec

      If  this  code  is encountered within a macro file,  K9X will close the
      current macro file and open (link) the new macro file designated by the
      Filespec.  Macro operation will continue using the macro lines found in
      the new macro file.

      NOTES:  The linked macro file must have the default .K9X extension  and
              must  reside in the K9X\SUPP directory.

              DO NOT include the .K9X extension or path in your Filespec...

              The   `<L>Filespec   MUST appear on a line by itself (without a
              "lookfor" portion) and MUST begin with the ` delimiter.

      Example: You wish to link to a new macro file called  MACRO2.K9X  which
               resides in your   K9X\SUPP   directory. The initial macro line
               would look like this:   `<L>MACRO2

      If  this  code  is encountered within a Function Key definition string,
      K9X will open the specified file, read in and send out all lines within
      the file NON STOP.  When used as a Function Key string, you may specify
      a full DRIVE:\PATH\ along with the filename.  The file itself may be of
      any size.

      Example: You wish to read in and send the contents of the  PASSWORD.BBS
               file  created  by  ADIAL  and  resides  in  your  C:\K9X\ADIAL
               directory. The Function Key string would look like this:

                       <L>C:\K9X\ADIAL\PASSWORD.BBS

      Since the file may be of any size, you may also use the Function Key
      link code to read in and send message replies:     <L>C:\REPLY.MSG

      Note here that the ` delimiter is NOT used...

   <ADIAL>

      This control code is to be  used  in  conjunction  with  the  <L>  link
      control code.  If K9X encounters this code as a link Filespec,  it will
      look for,  open and read in the file SCRIPT.BBS  which  is  created  by
      ADIAL and contains the true macro file name which K9X is to execute.

      Now this is a little tricky so read carefully!

      If  the  <ADIAL>  code is used,  K9X sets a Repeat SCRIPT.BBS flag that
      will repeat the reading of SCRIPT.BBS each  time  you  exit  back  from
      ADIAL  to K9X.  If the SCRIPT.BBS file does not exist (ADIAL erases the
      old one each time you re-enter ADIAL),  no  action  is  taken.  If  the
      SCRIPT.BBS  file  exists,  K9X will re-read the SCRIPT.BBS contents and
      re-execute the new,  true macro file.  Now...  K9X  automatically  adds
      the  SUPP\ path and .K9X extension to all macro files.  So no extension
      should be included (nor is one required) within your ADIAL Script field
      specification...  The Repeat SCRIPT.BBS flag will remain set until  the
      PCP Host carrier is dropped.

      HOWEVER,  this  "un-needed"  extension  space  turns  out  to be a very
      convenient place to let K9X know what default protocol and  optionally,
      what SuperK Resume mode you would like to use! Here's how this works...

      When K9X reads the contents of SCRIPT.BBS, it looks for a period (.) in
      the  true  macro  filename.  If  one exists,  K9X splits the true macro
      filename into 2 parts...  the filename and the extension.  The filename
      portion  is  of course,  intact and the ACTUAL true macro filename less
      the .K9X extension.

      The extension portion is where we will store the protocol # and  SuperK
      Resume Mode...  K9X checks the length of the extension portion and will
      interpret up to the first 2 characters (digits) as the default protocol
      number.  If the extension is 3 characters (digits) in length,  K9X will
      interpret the last character (digit) as the SuperK  Resume  Mode!  What
      this  means  of  course,  is  that if you wish to set the SuperK Resume
      mode,  you MUST specify the default protocol as a 2 digit  number  (01,
      02,  08, 23, 33, etc.) and, if a SuperK Resume Mode is to be specified,
      you MUST ALSO include a protocol number.  The SuperK Resume mode  codes
      are:   0 = disabled    1 = Auto    2 = Prompt

      Example:  Your True Macro filename is called MININET.K9X.  You wish  to
                set  your  default  protocol to Super8K Batch (protocol # 20)
                and  you  wish  to set the SuperK Resume mode to Auto (number
                1).  You would specify: MININET.201 as the ADIAL Script Name.
                K9X  uses  MININET as the Macro Filename,  20 as the Protocol
                number and 1 (Auto) as the SuperK Resume Mode


      Example:  Your True Macro filename is called MININET.K9X.  You wish  to
                set your default protocol to Jmodem Single (protocol # 8) and
                the SuperK Resume is not supported in  Jmodem  so  you  would
                specify:  MININET.8  or  MININET.08 as the ADIAL Script Name.
                K9X  uses  MININET  as the Macro Filename,  8 as the Protocol
                number and (who cares?) as the SuperK Resume Mode.

                If no SuperK Resume Mode is specified,  K9X will use the last
                Resume Mode Setting.  You MAY specify a  SuperK  Resume  Mode
                even though the specified protocol does not use/support it.

      NOTES:  Your ACTUAL  defined  macro  filename  must  contain  the  .K9X
              extension and must reside within your K9X\SUPP directory.

              K9X  will look for the SCRIPT.BBS file within the K9X directory
              NOT the ADIAL subdirectory

              The   `<L><ADIAL>   MUST appear on  a line by itself (without a
              "lookfor" portion.

              If you are not specifying a default protocol (and SuperK Resume
              Mode)  then  the  same  rules  apply here as do to the standard
              <L>Filespec  definition  above...   DO  NOT  include  the  .K9X
              extension or a path in the Filespec...

      Example: You wish to link to a new macro file called  MACRO2.K9X  which
               resides  in  your  K9X\SUPP  directory - no protocol or SuperK
               Resume mode specified. The ADIAL Script field definition would
               look like this:   MACRO2

   I've also modified the macro execution code to allow the specification  of
   the  <P>  (PCPursuit  Module  Execution  code)  to  be  used  as  a  "send
   immediately" type of  code...  That  is,  the  <P>  may  now  be  used  in
   conjunction  with a "lookfor" portion or by itself to facilitate immediate
   execution of the PCP Module upon connection to the PCP host.

     Examples: If the macro line reads @`<P> K9X will wait for the appearance
               of the @ before shelling out to the PCP Module.

               If the macro line reads `<P> K9X will do an immediate shell to
               the  PCP  Module  as soon as a Connect is established with the
               PCP Host.

   These modifications/enhancements should make control  of  the  PCP  Module
   execution alot easier... for instance...

   Define  a  dialing  directory  entry to hold your PCP Host information and
   include the filename PCP as the macro filename.

   Now create a macro file called PCP.K9X which contains the following lines:

             `<P>
             `<L><ADIAL>

   You may now create a standard logon macro for the particular BBS...  let's
   say for logging on to MiniNet. Your MININET.K9X macro would contain:

             T, G, C or F`TSal Manaro;mypassword|

   Place both  macro files,   PCP.K9X   and   MININET.K9X   in your  K9X\SUPP
   directory.

   Within the ADIAL module define the  SCRIPT field as  MININET  (without the
   SUPP\ path or the .K9X extension) or MININET.201 (as discussed above).

   When K9X connects with your PCP Host,  it will automatically  execute  the
   PCP  macro  file  you  defined.  The  first line will immediately shell to
   ADIAL.  Upon connection to MiniNet,  ADIAL will create the file SCRIPT.BBS
   (which  will  contain the true macro filename MININET) and then return you
   to K9X.  Upon return,  K9X will execute the second line in the  PCP  macro
   file (the `<L><ADIAL> line), read in the true script filename contained in
   the  SCRIPT.BBS file,  close the current PCP macro file,  open and execute
   the contents of the MININET macro file thus  logging  you  onto  the  bbs.
   After  disconnecting  from the BBS,  simply hit the Alt-9 key to return to
   ADIAL!

                           Enjoy and Merry Christmas!
                                 Sal Manaro


K9X      v8.8c   Dated  Jan07, 1990

   There have been reports that K9X hangs if it cannot address the modem upon
   initial startup.  This version modifies that code so that K9X will make  2
   attempts  at addressing the modem before automatically exiting to DOS with
   an errorlevel 1.  Upon notification of the failure to address  the  modem,
   K9X now gives the user the option to perform an immediate exit to  DOS  by
   pressing the  Escape key or resetting the modem and hitting any other key.
   If, after resetting the modem and pressing a key, K9X still cannot address
   the  modem,  you will be notified of this condition and K9X will then exit
   to DOS.

   There have also been some (minor) complaints about  the  "Press  any  key"
   prompt  prior  to  executing  the PCP or CIS/B module...  Please note that
   this is a timed prompt and K9X will automatically executed the appropriate
   module  upon  timeout.  In any  case,  for  you impatient types, the timer
   length has been shortened (it was about 10 seconds before and is  about  5
   seconds now)!

   Since the Configuration routines are now built into K9X,  I've added a new
   command line parameter. Starting  K9X  as   K9X P   will set K9X in a pure
   configuration  mode...   that  is,   K9X  will  go  directly  to  the  K9X
   Configuration section and will return to DOS immediately  upon  exit  from
   that section. So.... if you make changes, be sure to save `em via the  K9X
   defaults "Save Current Setup" option!

   A couple of other internal changes have been made,  but nothing  major  or
   "visible"!

   For those of you who have been waiting patiently for a K9X  Host  mode,  I
   haven't  forgotten  you!  K9X  is  about  at its code size limit under the
   current Pascal compiler so, rather than shortchange the Dog's users with a
   host mode that leaves alot to be desired, I've decided to put it off until
   K9X makes its transition to Turbo Pascal v5.5 at which time,  K9X will  be
   offered  in  several  "flavors"  (you'll  have  to  wait  to find out what
   "flavors" will be offered)!

                           Enjoy and Happy New Year!
                                 Sal Manaro


K9X      v8.8d   Dated  Apr20, 1990

   This  release  marks the first major upgrade of the old Shareware v8.6e to
   bring it in line with the current status of the  registered  version.  The
   new  Shareware  version  has  the v8.6e screens in place but the execution
   delays have been shortened quite a bit  (20  seconds  on  startup  and  10
   seconds on exit).

   There have been some minor changes to this version...

   There was a problem in opening the port at or above 38400bps. This was an
   oversight when I added the 38400 and 57600 bps support.

   I've added some additional code to drop the RTS line when performing  disk
   writes in Super8K and Super8K-G and operating with a locked port. Although
   this will help some of you "speed demons",  I'm afraid the I/O routines in
   the current K9X are just too slow to satisfy all conditions and are  being
   reworked  for  the next version.  If you find you are having problems with
   your locked port/Super8K/Super8K-G  transfers,  please  use  the  external
   SuperK driver until I can get the K9X routines reworked.

   I've corrected the Auto Zmodem problems... As of this version, Auto Zmodem
   requires  your protocol be either the internally supported Zmodem Batch or
   an external which has the word   Zmodem   somewhere in its name... and you
   have used the download   cut and paste buffers  to  mark  and  supply  K9X
   and the Host with the filename(s) requested for download.

   For those users who have been patiently awaiting the new Turbo Pascal v5.5
   version...  I offer my apologies for the delay.  Due to a serious  illness
   and  subsequent  death  in  our  family,  our attentions have been focused
   elsewhere.  In the past couple of months, I've been working frantically to
   get  cought  up  with my programming and will commence work on the new K9X
   and SuperK programs ASAP. The sequence of events will be ...

      1) The release of the all new SuperK HST v1.0 protocol driver
      2) The release of the all new K9X HST v1.0 program
      3) The conversion of SuperK HST to Turbo Pascal v5.5
      4) The conversion of K9X HST to Turbo Pascal v5.5

   * Somehwere within steps 1 through 4 above, a stand alone (not a funky
     script type) host mode will be released.

   Again, my apologies for the delay...

                           Enjoy and Happy Easter!
                                 Sal Manaro