

			            MB-KMD
			       (a User's guide)
 				      by
 			          Bob Kramer
			   Rock Island RCP/M (PBBS)
			        (309) 786-6227



       MB-KMD is  currently  the  ONLY Stand-Alone/BYEBDOS  file  transfer
    utility supporting 1k and BATCH protocol you will likely run across in
    your electronic travels.   While it is similar in general operation to
    the XMDM [sic] utility (generally  known  by the user as XMODEM) still
    used  by  many  RCP/M's,  MB-KMD  provides many interesting and useful
    extras to help you cut down on online time.

       There  are  many detailed and informative document  files  floating
    around  which  detail XMODEM protocol,  so no use in beating  this  to
    death. What you get with this protocol is a transfer rate of 128-bytes
    per block sent.  This protocol is the most widely supported and can be
    found used in the majority of communications programs today, both CP/M
    and MS-DOS...not yet antiquated.

       MB-KMD is a direct off-shoot of the XMDM series,  but with the very
    useful addition of Ymodem protocol. What you get is a transfer rate of
    1k-bytes per block sent!  This saves time when operating at speeds  of
    1200 baud and up.  Another feature of Ymodem protocol is that of batch
    transfers.  What this means is that you can specify a number of  files
    to be downloaded (from the RCP/M to you) via MB-KMD and then just tell
    your program (i.e. IMP for  CP/M users -- PROCOMM,  Pro-YAM  or  other
    MS-DOS  program which supports Ymodem batch  protocol  with  CRC error
    checking) to start receiving -- you don't  specify any  filename  more
    than once. Your program will then get all filenames from MB-KMD during
    the transfer -- a nifty feature  even  if  only  transferring a single
    file.  This also works for uploads (from you to the RCP/M) as well  --
    tell MB-KMD to start up batch receive (i.e. "KMD  R" -- no filename is
    specified), then tell your program what file(s) you wish to send batch
    mode.

       MB-KMD also automatically  detects  the  type  of  error   checking
    needed/expected  by  your  terminal program (i.e.  CRC  or  Checksum).
    Those  of you who are used to forcing the check mode may also  do  so,
    but this is unecessary.

       In  addition,   MB-KMD   will  automatically detect which  protocol
    your  terminal   program  uses during file  transfers  -- note:   this
    means   it  will  know  whether to use 128-byte block XMODEM  protocol
    or  1k-byte block Ymodem protocol.    With the Ymodem or Ymodem  batch
    mode used by MB-KMD, only  CRC error checking is used -- not checksum.
    Those of you who are used to forcing transfer protocols (i.e. MEX) may
    still do so, but this is unecessary.

       The following are descriptions of command examples displayed to you
    when MB-KMD is initiated incorrectly, or when it is entered by itself.
    While not meant to be exhaustive of the many combinations,  this guide
    should  provide   you  with enough information to get  your   transfer
    going  in short order.


                  = = = = = = = = = = = = = = = = = = = = =


    This section displays examples for DOWNLOAD.   When a file transfer is
    from an RCP/M to you, this is called a "download".

    DOWNLOADS:

          KMD S   EXAMPLE.LBR                Normal file download
          KMD S   B1:EXAMPLE.DQC             From a named drive/user area
          KMD SP  YOURFILE.EXT               Private download
          KMD SB  EXAMPLE.*                  1k batch mode
          KMD SB  EX*.* B1:PBBS*.*           1k multiple file batch request
          KMD SK  EXAMPLE.LBR		     Force 1k Ymodem protocol
          KMD SX  EXAMPLE.LBR		     Force Xmodem protocol

    Note:  When requesting a batch transfer,  wild cards may be used.  You
    are only  limited  by  the  amount  of  time a Sysop grants you online
    during  each  24-hour period,  as to how many files you may pick up in
    this manner.

       The  "SP" command informs MB-KMD to search a "private" area for the
    file specified.  This is useful when the Sysop has prearranged for you
    to download a file from the system,  but does not want it released  to
    the  general  public.  If MB-KMD fails to find the file  specified, it
    aborts with a message telling you no file exists with that name.

       MB-KMD  will compute the time required for transferring the file(s)
    to you and display this information.    You will also be told how many
    'k'  of  space  will be required (keep in mind this is based   on   2k
    block  allocations) and how many 128-byte "records" the transfer  will
    consist of.    Once it gets the "go ahead" from your terminal program,
    transfer begins.    At  any  time before/during the transfer,  you may
    abort   by  entering   a CTRL-X,   followed by a  short  pause,   then
    another  CTRL-X.  Many times, a single CTRL-X will suffice.


                  = = = = = = = = = = = = = = = = = = = = =


    This  section displays examples for UPLOAD.   When a file transfer  is
    from you to an RCP/M, this is called an "upload".

    UPLOADS:

          KMD R   EXAMPLE.OBJ                Normal file upload
          KMD R                              1k batch mode
          KMD RP  EXAMPLE.AQM                Private upload
          KMD RP                             Private BATCH upload
          KMD RC  EXAMPLE.LBR                Force checksum
          KMD RPC EXAMPLE.AQM		     Private upload (force checksum)
          KMD RM  MESSAGE.FIL		     See 'RM' section below

    Note:   As  you  can  see,  filenames are never  specified  for  batch
    uploads.   You will return to your communications program and tell  it
    which  file(s) to send via Ymodem batch protocol (i.e.  IMP,  Pro-YAM,
    PROCOMM, etc..) and everything else is automatic.

       The  "RP"  command is used  whenever you have a file(s) you wish to
    upload to the Sysop's private area -- when no filename  is  specified,
    MB-KMD is  expecting  a  batch transfer  (still goes private, though).
    Files uploaded in this manner  are not  displayed  to users  when that
    system supports the NEW utility for listing all uploads.

       Once  it gets the "go ahead" from your terminal  program,  transfer
    begins.   At  any  time before/during the transfer,  you may abort  by
    entering  a CTRL-X,  followed by a short pause,  then another  CTRL-X.
    Many times,  a single CTRL-X will suffice.  If only a partial file was
    received at that time, MB-KMD will erase it in most cases.

       When   you  have finished uploading your file(s)  to  the   system,
    MB-KMD  may then  ask  you  to assign a category to  it  -- categories
    vary according  to each Sysop. Next you may be asked if automatic line
    wrap should be turned off (default is 'N'o,  so hit <enter> to  skip).
    If  you  do a lot of uploading,   you will save time to pre-type  each
    file's descriptions.  In case you have text ready to ASCII transfer at
    this  time,  answer  'Y'es  to  turn  off line wrap and start the text
    transfer when asked for the description.  This process is repeated for
    each  file  uploaded  (if batch used).   You will only go through this
    process on systems which support the FOR utility -- this allows you to
    type FOR and see what the file is used for... (optionally, a SysOp may
    have MB-KMD set up to route upload descriptions to the  BBS's  message
    system for callers to view when they logon, this  unique  option is  a
    'first' by the MB-KMD program).


                  = = = = = = = = = = = = = = = = = = = = =


    This section is an example of a special "message file"  upload.   MBBS
    systems currently support this feature,  but it will likely turn up on
    others as well.

    MESSAGE FILE UPLOAD:

          KMD RM  UPLOAD.MSG                 Pre-formatted msg file xfr

    Note:  A pre-formatted message file may be uploaded with this command.
    It will then be placed in the system's message base without you having
    to  type  anything  while online.   MBBS systems  running  either  the
    NUBYE/MB-KMD combination,  or MBYE/MB-KMD combination may support this
    optionally  -- ask your sysop about this feature if not sure,   or you
    would like to see it supported.

       Following this type of upload (on MBBS systems),  a special message
    file handler will be run and you will be asked to verify or skip  each
    message found within your file -- you may also abort, but in any case,
    the  sysop has your message file for later reference.   If you do  not
    have  message write  access,  MB-KMD will not allow you  to  use  this
    command.


                  = = = = = = = = = = = = = = = = = = = = =


    This section displays examples for downloading individual file members
    from .LBR/.ARK/.ARC files.  .ARK files have the same structure as .ARC
    files -- the extension is different to distinguish it from the  MS-DOS
    counterpart.  .LBR  files  are found in CP/M and MS-DOS,  although the
    ARChive format is edging this type of file storage into antiquity.


          KMD L  MBKMD120 MBKMD.UZD          .LBR file
          KMD LX MBKMD120 MBKMD.HZP 	     Force Xmodem protocol

          KMD A  FLIGHT FLIGHT.EXE           .ARK/.ARC file
          KMD AK FLIGHT FLIGHT.DOC           Force 1k Ymodem protocol

    Note: The "L" and "A" options are used to download single file members
    from within .LBR/.ARK/.ARC files.  The  .LBR/.ARK/.ARC  extensions are
    not required.



    MISCELLANEOUS:

          KMD F                              Shows available upload space

    Use  this  command  to  see how much <F>ree upload space is available,
    prior  to  starting the transfer.   If the Sysop is  short  on  upload
    space,  leave a note about the file you have so room can be made.


                  = = = = = = = = = = = = = = = = = = = = =


    I  hope  this  guide  will help you to enjoy  the  exciting  world  of
    telecommunications!
