ftp.barnyard.co.uk/2015.02.ftp.barnyard.co.uk.tar/ftp.barnyard.co.uk/cpm/walnut-creek-CDROM/CPM/NUBYE/NUKMD111.ARK/NUKMD.HLP

Text File | 1987-02-02 | 12KB | 241 lines

                    NUKMD
                   (a User's guide)
                      by
                  Tom Brady
                 Decibel PBBS
                [phone]


       NUKMD is currently one of the most popular RCP/M (Remote CP/M) file
    transfer  utilities  which    you  are  likely to  run  across  in  your
    electronic    travels.  While similar in general operation to the   XMDM
    [sic] utility (generally  known  by the user as XMODEM) still used    by
    many   RCP/M's,  NUKMD  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.

    NUKMD  is  a direct offshoot of the XMDM series,  but with the  useful
    addition  of  the MS-DOS derived 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  NUKMD  and  then just tell your program (i.e.   IMP for
    CP/M  users  --  PROCOMM,    Pro-YAM  or other  MS-DOS   programs which
    support  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   NUKMD  during    the
    transfer  --  a   nifty feature  even  if only  transferring  a single
    file.   The same   thing works for uploads (from you to the RCP/M)    as
    well  -- tell  NUKMD  to start  up    batch receive (i.e.    "KMD  R"  -
    no     filename  specified),     then tell your program what file(s)   you
    wish  to send batch mode.

       NUKMD 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,  NUKMD  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 NUKMD, 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 is a menu of command examples displayed to you  when
    NUKMD  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 (from this system to you)

    NUKMD S   EXAMPLE.LBR               Normal file download
    NUKMD S   B1:EXAMPLE.DQC               From a named drive/user area
    NUKMD SP  YOURFILE.EXT               Download from private area
    NUKMD SB  EXAMPLE.*                1k batch mode
    NUKMD SB  EX*.* B1:NUBYE*.* D1:NUK*.*      1k multiple file batch request
    NUKMD SK  EXAMPLE.LBR               Force 1k Ymodem protocol
    NUKMD SX  EXAMPLE.LBR               Force Xmodem protocol
  * NUKMD SS  EXAMPLE.DQC               Special download

    Note:  When requesting a batch transfer,  wild cards may be used.  You
    may  also  specify multiple files  on similar  d/u areas as  the  last
    download example shows.   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  --  keep in mind, however, being
    granted "unlimited" time does not mean you can "rape" the system...

       The  "SP" command informs NUKMD 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 NUKMD fails to find the file  specified,    it
    aborts with a message telling you no file exists with that name.

       The  "SS"  command informs NUKMD to allow "special"  downloading of
    files  from a normally accessible drive/user area,    although that user
    may  be restricted from downloading.   This is handy if you operate  a
    semi-restricted system,  allowing users into your file areas,  but not
    allowing general downloads until they have been verified.    With  this
    command  option  (when set at assembly time)  all new users could  get
    current BBS lists,    system DIRectories, etc from a public area -- they
    would not be able to download from *any* other drive/user area.

       NUKMD  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   (from you to this system)

    NUKMD R   EXAMPLE.OBJ               Normal file upload
    NUKMD RC  EXAMPLE.LBR               Force checksum
    NUKMD RP  EXAMPLE.AQM               Private upload
    NUKMD RPC EXAMPLE.AQM               Private upload (force checksum)
    NUKMD R                       1k Ymodem batch upload
    NUKMD RP                       ...to private area
    NUKMD RM  MESSAGE.FIL               See note below
  * NUKMD RW  EXAMPLE.TXT               Restricted upload command

    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 (or  files)  you
    wish  to  upload  to the Sysop's private area -- when no  filename    is
    specified,     NUKMD     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.

  *   The  "RW"  command is available to users who have "special"  access
    privileges    and  not  the general public.    NUKMD will  not  allow    an
    unauthorized user access to this command.

       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, NUKMD will erase it in most cases.

       When   you  have finished uploading your file(s)  to  the   system,
    NUKMD will    then  ask  you    to assign a category to  it  -- categories
    vary according  to each Sysop.    Next you are 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...


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


    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  (special function)

    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/NUKMD  combination,  or MBYE/XMDM 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,  NUKMD will not allow you  to  use  this
    command.

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


    This section displays examples for downloading individual file members
    from    .LBR/.ARK/.ARC file collections.   .ARK files are of the  same
    structure  as  .ARC  files    --  only 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.


    NUKMD L  NUKMD110 NUKMD.HQS          {.LBR file}
    NUKMD LX NUKMD110 NUKMD.HQS          Force Xmodem protocol

    NUKMD A  NUKMD110 NUKMD.HIS          {.ARK/.ARC file}
    NUKMD AK NUKMD110 NUKMD.HIS          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.


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


    General Features/Comments:

     1)  NUKMD provides full support for both Ymodem and Xmodem
        protocols.
     2)  NUKMD supports any communication package which offers
        the user Xmodem or Ymodem transfer protocols, both
        CP/M and MS-DOS -- commercial and public domain.
     3)  NUKMD uses automatic protocol detection and will
        determine which mode to use for a transfer:
          Xmodem 128-byte packets (CRC or checksum)
          Ymodem 1k-byte packets  (CRC only)
     4)  NUKMD supports those terminal programs which offer the
        user Ymodem batch transfer capability.    These include
        (but aren't limited to) IMP, Yam, ProYam and PROCOMM.
     5)  Individual file members may be extracted from .ARK (CP/M) and
        .ARC (MS-DOS) file collections via the "A" download option
        and from .LBR (both CP/M and MS-DOS) files via the "L"
        option.


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


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