Date   : Fri, 20 May 1988 11:53:00 MDT
From   : Keith Petersen <W8SDZ@SIMTEL20.ARPA>
Subject: z80 assemblers

Have you tried the archive server?  Before you flame me please be
fully informed.  Comp.Os.Cpm is a newsgroup for messages, not
binaries.  If you insist on posting binaries I will have no choice but
to ask that the gateway between Usenet and Arpanet be SHUT OFF.

[Note: In the following discussion, if you are not on BITNET
substitute the address LISTSERV@CICGE.RPI.EDU for the address shown.]

            Help information for the PDGET command
*****************************************************************

     Selected portions of the SIMTEL20 public domain software archives
are available via a file server at RPICICGE.BITNET.  At present the
collections include the following directories:

     PD1:<CPM.*>     -- The Info-CPM archive (CP/M machines)
     PD1:<SIGM.*>    -- The SIG/M User Group archive (CP/M machines)
     PD1:<MISC.*>    -- The Miscellaneous archives
     PD1:<MSDOS.*>   -- The IBM-PC/MSDOS archives
     PD1:<PC-BLUE.*> -- The PC-Blue User Group archive (MSDOS machines)
Planned:
     PD1:<CPMUG.*>   -- The CP/M User Group archive.

Any of the files in these collections are available from the file
server LISTSERV@RPICICGE.BITNET.  The server responds to two commands.
/PDDIR requests a directory listing of files available in an archive,
and /PDGET requests a file from an archive.  The file server accepts
commands in both interactive messages or RFC822-style mail.  (On
VM and MVS Bitnet hosts, TELL LISTSERV AT RPICICGE... can be used to
send an interactive message.  Other Bitnet systems may have similar
facilities.  People on non-Bitnet systems must use the mail interface,
and must insure that the From: header represents a valid return path.)

****Note:  The server actually responds to many, many other commands,
           but none of them have anything to do with the archives.

The two commands have the following form:

      /PDGET  <format>  simtel.filename  < ( encoding >
      /PDDIR  simtel.pattern

The <...> mark things that are optional.

* "simtel.filename" specifies the name of a file to be delivered to the
    user.  Names are usually of the form "PD1:<dir.subdir>name.type"

* "simtel.pattern" specifies a search pattern used in generating a
    directory listing.  The form of the pattern is like the filename
    mentioned above, but asterisks (*) may be used freely in the
    subdir, name, and type parts as wild cards (but not in the dir field.)

* "format" specifies the method of transmission to be used:

    NETDATA  -- suitable for transfer to Bitnet hosts that can accept
                files in IBM Netdata format.
    PUNCH    -- suitable for transfer to Bitnet hosts that can accept
                files but cannot decode the Netdata format.  Files
                are sent as 80-byte card-images.
    MAIL     -- suitable for transfer to hosts that can accept only
                mail or are accessible to Bitnet only through gateways.
                Large files sent via mail are split into several
                smaller files that the recipient must reassemble.
    If the format is omitted, NETDATA is assumed for Bitnet hosts
    and MAIL for all others.

* "encoding" specifies any special encoding of the file data:

    ASIS     -- suitable for hosts that can receive binary data.  The
                file is sent exactly as it is stored on RPICICGE:
                CP/M sector images, binary mostly.  ASIS may be used
                only with format NETDATA.
    UUENCODE -- suitable for hosts that cannot receive binary data.
                The file is sent uuencoded.
    TRANSLATE -- suitable for any host, but only when the file actually
                represents readable text.  The file is translated into
                character data format.
    If the encoding is omitted, files are sent ASIS if the transmission
    format is NETDATA, and UUENCODEd otherwise.

/PDDIR Examples:
===============
(1)  The user is looking for the ARC programs.
            /PDDIR  PD1:<MSDOS.*>ARC*.*

(2)  The user wants a listing of the full MSDOS collection.
            /PDDIR  PD1:<MSDOS>

/PDGET Examples:
===============
In each of the following examples the user wants the -FILES.DOC file to
examine on his host and the PKX35A35.EXE file to download to his micro,
both from the MSDOS collection.  Note that none of the examples have a
closing parenthesis!

(1)  The user is on an IBM host directly connected to Bitnet:
           /PDGET  NETDATA  PD1:<MSDOS.STARTER>-FILES.DOC  (TRANSLATE
           /PDGET  NETDATA  PD1:<MSDOS.ARC-LBR>PKX35A35.EXE

(2)  The user is on a non-IBM host directly connected to Bitnet and can
     receive Netdata files:
           /PDGET  NETDATA  PD1:<MSDOS.STARTER>-FILES.DOC  (TRANSLATE
           /PDGET  NETDATA  PD1:<MSDOS.ARC-LBR>PKX35A35.EXE  (UUE

(3)  The user is on a non-IBM host directly connected to Bitnet and can
     receive punch files:
           /PDGET  PUNCH  PD1:<MSDOS.STARTER>-FILES.DOC  (TRANSLATE
           /PDGET  PUNCH  PD1:<MSDOS.ARC-LBR>PKX35A35.EXE  (UUE

(4)  The user is on some host somewhere:
           /PDGET  MAIL  PD1:<MSDOS.STARTER>-FILES.DOC  (TRANSLATE
           /PDGET  MAIL  PD1:<MSDOS.ARC-LBR>PKX35A35.EXE  (UUE

--Keith Petersen
Maintainer of the CP/M and MSDOS archives at SIMTEL20.ARPA


End of INFO-CPM Digest
******************************