jchvr@ihlpg.ATT.COM (Hartong) (06/24/87)
A while back I found out that there is a machine somewhere in this world
that is used as archive for lots of nice public domain software for ther
ibm-pc. All you need to do is direct email to it and you get the programs
of your choice. I would like to thank those that told me how access all
these goodies. Here is my info on this beaty (Keep up the good work!).
From uucp Thu Jun 18 13:28 MDT 1987
------------
To obtain up to five files in a single request message by netmail from
the public domain archives kept on SIMTEL20.ARPA, send a message to:
ARCHIVE-REQUEST@SIMTEL20.ARPA
or via uucp:
...!ucbvax!simtel20.arpa!archive-request
...!uw-beaver!simtel20.arpa!archive-request
...!decwrl!simtel20.arpa!archive-request
...!lll-lcc!simtel20.arpa!archive-request
...!ut-sally!simtel20.arpa!archive-request
...!harvard!simtel20.arpa!archive-request
HFVR: the path I used was: ihnp4!simtel20!archive-request, and it worked!!
[do NOT use host "seismo" - they are blocking messages from the server]
The message body must contain lines beginning with the keyword SEND,
one SEND line for each file requested. Case is not significant.
The general syntax of a SEND line is:
SEND format filename
In general, a filename consists of the following components:
device:<directory>file.type.generation
"device:" is usually PD:, and the combination of PD:<directory> is
expected unless an alias has been advertised of the form "alias:",
which takes the place of both device and directory fields. The
generation field should be left off in order to default to the highest
generation number so you can be sure of getting the latest version of
the file requested. "file.type" follows the usual filenaming
conventions.
In all formats listed below, if the file to be sent is larger than
55K, the file is sent in numbered parts. The parts must be
reassembled in order and edited to remove any headers, preface, and
trailers before the process can be reversed to reconstruct the
original file.
Allowable formats are:
SEND HELP
This file you are reading now.
SEND INFO
A detailed description of the SIMTEL20 Archives, which
includes this file, pointers to certain key files, and
descriptions of various file transfer programs and related
utilities.
SEND BOOTSTRAP
A brief quick reference listing of filenames of the key
utilities used to reconstruct files sent by the compression
and encoding techniques listed below.
SEND DIR filespec
This format returns a CRC list of the requested files, and is
the only format which allows wildcard filenames (but not
wildcard directory names). The list is sent as an ASCII text
file. The wildcard characters are "*" and "%". The asterisk
means any number of characters, while the percent sign means
exactly one character. Either or both may appear in any
combination in either or both the file or type fields, while
only the asterisk may appear in the generation field.
SEND RAW filename
If the file is ASCII, it is sent as-is, regardless of size.
This format is the least efficient over network and mail
gateway resources. Use this format only if you absolutely
must.
SEND DET filename
Same as RAW, except the file is detabified.
With the four formats listed below, if the file is ASCII and under 25k
characters, it is sent as-is, as if RAW format was requested. Binary
files are always processed according to the requested format.
However, a request for ARC or SQ processing of files with type ".ARC",
".LBR", or ".%Q%" is ignored and the original file is either uuencoded
or hexified (if possible), according to the requested format. If the
file was not sent RAW, a short preface is inserted at the front of the
message describing the process actually taken and a CRC entry
describing the original file.
SEND ARE filename or SEND filename
The original file is made into a uuencoded ARC file.
SEND ARH filename
The original file is made into a hexified ARC file if the ARC
file is under 64K bytes long. Otherwise, an apology is
returned instead of the requested file.
SEND SQE filename
The original file is made into a uuencoded SQueezed file.
SEND SQH filename
The original file is made into a hexified SQueezed file if the
Squeezed file is under 64K bytes long. Otherwise, an apology
is returned instead of the requested file.
To get started in finding your way around the SIMTEL20 archives, send
another request: SEND INFO
From uucp Thu Jun 18 13:28 MDT 1987
>From hao!csnet-relay!ARCHIVE-SERVER%simtel20.arpa%simtel20.arpa Thu Jun 18 06:25:08 1987 remote from ihnp4
Received: by ihnp4.ATT.COM id AA06797; 18 Jun 87 06:25:08 CDT (Thu)
Received: from hao-hw.UCAR.EDU (hao-hw.ARPA) by hao.UCAR.EDU (4.12/1.00.UUCP-MOD.8-11-85)
id AA12136; Thu, 18 Jun 87 02:35:16 mdt
Message-Id: <8706180831.AA04902@hao-hw.UCAR.EDU>
Received: by hao-hw.UCAR.EDU (4.13/1.00.UUCP-MOD.8-11-85)
id AA04902; Thu, 18 Jun 87 02:31:18 mdt
Received: from relay.cs.net by RELAY.CS.NET id ai14916; 16 Jun 87 3:33 EDT
Received: from simtel20.arpa by RELAY.CS.NET id aa11020; 16 Jun 87 3:34 EDT
Date: Tue, 16 Jun 87 00:41:21 MDT
From: ihnp4!simtel20.arpa!ARCHIVE-REQUEST
Sender: ihnp4!simtel20.arpa!ARCHIVE-SERVER
To: hvlpb!hvrietsc%ihnp4.UUX%ncar.csnet@csnet-relay
Subject: INFO (on the SIMTEL20 Archives)
Received: from CSNet-Relay by ncar; 18 Jun 87 2:16:29-MDT (Thu)
Status: RO
THE SIMTEL20 ARCHIVES
OVERVIEW
There is a collossal amount of free public domain software for the
CP/M, PCDOS/MSDOS and UNIX operating systems, and for the DoD standard
programming language, Ada, in several archives on SIMTEL20.ARPA, a
DECSYSTEM-20 running the TOPS-20 operating system at White Sands
Missile Range.
To obtain a directory listing of interest to you, send your request to
ARCHIVE-REQUEST@SIMTEL20 with up to five of the following commands
in the body of any one message:
SEND PD:<CPM>CPM.CRCLST
SEND PD:<CPMUG>CPMUG.CRCLST
SEND PD:<SIGM>SIGM.CRCLST
SEND PD:<PC-BLUE>PC-BLUE.CRCLST
SEND PD:<MSDOS>MSDOS.CRCLST
SEND PD:<UNIX>UNIX.CRCLST
SEND PD:<ADA>ADA.CRCLST
SEND PD:<MISC>MISC.CRCLST
The PD:<CPM> archive is the one to watch for the very latest CP/M
offerings, as it is updated frequently. The PD:<CPMUG>, PD:<SIGM> and
PD:<PC-BLUE> archives contain software distributed by the CP/M Users
Group, the SIG/M Users Group and the PC-Blue Users Group respectively.
This software is available on diskettes from the associated users
groups, and the archives are updated as new volumes are issued.
The PD:<PC-BLUE> archive contains software for the IBM-PC and similar
machines. Some runs under CP/M, and some under PCDOS/MSDOS. The
PD:<MSDOS> archive also contains software for the MSDOS and PCDOS
operating systems; but this archive is locally managed, and therefore
is updated more frequently than the PD:<PC-BLUE> archive.
The PD:<UNIX> archive contains a variety of UNIX tools. Those which
apply specifically to CP/M are in the directory PD:<UNIX.CPM>.
The PD:<ADA> archive is growing rapidly. Information about this
archive is in directory PD:<ADA.GENERAL>.
In general, the archived software is very good, having been
worked-over and refined by many users. The documentation and comments
tend to be complete and informative. Files in all of these archives
can be obtained using the ARCHIVE-REQUEST procedures described in this
message.
DISCLAIMER
Please note that due to the large number of files available, the
archive maintainers cannot possibly attempt to validate the proper
operation of the various programs. When a program bug is reported,
immediate action is taken to either correct the error or remove the
offending program from the archives. Still, users must understand
that all archive programs are offered AS-IS, and the archive
maintainers specifically disclaim any liability should these programs
malfunction or cause damage, incidental or otherwise. When testing
ANY new software, be certain that all information stored on disk is
backed-up before you start, so that you can recover if files are
damaged or erased. This is particularly true if you have a hard disk,
in which case malfunctions can be spectacularly disasterous.
HOW TO USE ARCHIVE-REQUEST
To obtain up to five files in a single request message by netmail from
the public domain archives kept on SIMTEL20.ARPA, send a message to:
ARCHIVE-REQUEST@SIMTEL20.ARPA
or via uucp:
...!ucbvax!simtel20.arpa!archive-request
...!uw-beaver!simtel20.arpa!archive-request
...!decwrl!simtel20.arpa!archive-request
...!lll-lcc!simtel20.arpa!archive-request
...!ut-sally!simtel20.arpa!archive-request
...!harvard!simtel20.arpa!archive-request
[do NOT use host "seismo" - they are blocking messages from the server]
The message body must contain lines beginning with the keyword SEND,
one SEND line for each file requested. Case is not significant.
The general syntax of a SEND line is:
SEND format filename
In general, a filename consists of the following components:
device:<directory>file.type.generation
"device:" is usually PD:, and the combination of PD:<directory> is
expected unless an alias has been advertised of the form "alias:",
which takes the place of both device and directory fields. The
generation field should be left off in order to default to the highest
generation number so you can be sure of getting the latest version of
the file requested. "file.type" follows the usual filenaming
conventions.
In all formats listed below, if the file to be sent is larger than
55K, the file is sent in numbered parts. The parts must be
reassembled in order and edited to remove any headers, preface, and
trailers before the process can be reversed to reconstruct the
original file.
Allowable formats are:
SEND HELP
This section you are reading now.
SEND INFO
This file you are reading now.
SEND BOOTSTRAP
A brief quick reference listing of filenames of the key
utilities used to reconstruct files sent by the compression
and encoding techniques listed below.
SEND DIR filespec
This format returns a CRC list of the requested files, and is
the only format which allows wildcard filenames (but not
wildcard directory names). The list is sent as an ASCII text
file. The wildcard characters are "*" and "%". The asterisk
means any number of characters, while the percent sign means
exactly one character. Either or both may appear in any
combination in either or both the file or type fields, while
only the asterisk may appear in the generation field.
SEND RAW filename
If the file is ASCII, it is sent as-is, regardless of size.
This format is the least efficient over network and mail
gateway resources. Use this format only if you absolutely
must.
SEND DET filename
Same as RAW, except the file is detabified.
With the four formats listed below, if the file is ASCII and under 25k
characters, it is sent as-is, as if RAW format was requested. Binary
files are always processed according to the requested format.
However, a request for ARC or SQ processing of files with type ".ARC",
".LBR", or ".%Q%" is ignored and the original file is either uuencoded
or hexified (if possible), according to the requested format. If the
file was not sent RAW, a short preface is inserted at the front of the
message describing the process actually taken and a CRC entry
describing the original file.
SEND ARE filename or SEND filename
The original file is made into a uuencoded ARC file.
SEND ARH filename
The original file is made into a hexified ARC file if the ARC
file is under 64K bytes long. Otherwise, an apology is
returned instead of the requested file.
SEND SQE filename
The original file is made into a uuencoded SQueezed file.
SEND SQH filename
The original file is made into a hexified SQueezed file if the
Squeezed file is under 64K bytes long. Otherwise, an apology
is returned instead of the requested file.
ARCHIVE-REQUEST is actually a batch job that reschedules itself for
one hour later after it has completed the current batch. This
frequency may be changed, depending on volume and system load.
FILE TYPES
Squeezed files have been compressed using programs available in
directory PD:<CPM.SQUSQ> to obtain an approximate 35-percent size
reduction. These files can be identified by the letter Q in the
extension field. For example, the file PD:<CPM.ASMUTL>RMACPAT.AQM is
a squeezed file. It must be transferred as a binary file, and then
unsqueezed. The unsqueezing can be done on a CP/M system using
USQ-xx.COM (where "xx" is the current version) from directory
PD:<CPM.SQUSQ>, or there are several host-based unsqueezers in the
PD:<CPM> and PD:<UNIX> archives (see for example, directories
PD:<MISC.TOPS-20> and PD:<UNIX.SQ-USQ>).
CP/M library files (those with names ending in LBR) combine several
regular CP/M files into a single BINARY file which contains an
internal directory of its contents. They are created using the CP/M
library utility LUxxx.COM (where "xxx" is the current version) or some
other compatible utility. The complete packages for LUxxx and a newer
compatible program called NULUxx (where "xx" is the version) can be
found in directory PD:<CPM.ARC-LBR>. C-language source code for a
compatible UNIX utility called LAR (library archiver) is in directory
PD:<UNIX.ARC-LBR>.
Important files in the PD:<CPMUG> and PD:<PC-BLUE> archives are the
CATALOG files. These files contain the "-CATALOG.nnn" files from all
the volumes of their respective archives. To obtain these composite
catalog files, send a message to ARCHIVE-REQUEST@SIMTEL20 with the
message body containing either or both of the following requests:
SEND PD:<CPMUG>CPMUG.CAT
SEND PD:<PC-BLUE.VOL000>PCBLUE.CAT
Similar files exist for the PD:<SIGM> archive, but they are stored in
squeezed form. Tell ARCHIVE-REQUEST to send the files with the
request:
SEND PD:<SIGM.VOL000>SIG0.CQT <--volumes 151-294
SEND PD:<SIGM.VOL000>SIG1.CQT <--volumes 1-150
PROGRAMS FOR TRANSFERRING FILES AMONG MAINFRAMES AND MICROS
Christensen Protocol Mainframe Programs:
For a micro to reliably exchange files with a mainframe, cooperating
file transfer programs with automatic error detection and retrans-
mission of faulty blocks must be running on both computers. One such
family of programs uses a popular protocol created by Ward Christensen
and enhanced by others. Directory PD:<UNIX.XMODEM> contains several
programs, XMODEM, RZ/SZ (ZMODEM), UC and the older UMODEM (all written
in C), which implement this protocol on UNIX machines. See the file
PD:<UNIX>UNIX.CRCLST for a list of other useful UNIX utilities.
On ITS machines, file transfer using the Christensen protocol can be
done using MMODEM (type :MMODEM for instructions), or LMODEM.
Documentation for LMODEM is on your host in file .INFO.;LMODEM HELP.
A collection of TOPS-20 utilities for transferring and manipulating
files can be found in directory PD:<MISC.TOPS-20>. See
PD:<MISC>MISC.CRCLST for a list of available programs.
File transfer and conversion utilities for use with VAX/VMS machines
are contained in directory PD:<MISC.VAXVMS>. See PD:<MISC>MISC.CRCLST
for details.
Christensen Protocol Microcomputer Programs:
An excellent program for transferring files between micros, or between
micros and mainframes is called MODM7xx, where the "xx" is replaced
with two digits to give the current version number. This program,
often referred to as MODEM7 (the name of its easier to pronounce
ancestor), uses the popular Christensen protocol to transfer files
with automatic error detection and retransmission of erroneous blocks.
To get started with MODM7xx, first get and examine the "DOC" and "MSG"
files from the binary library file PD:<CPM.MODEM7>MODM7xx.LBR. The
"DOC" and "MSG" files are actually stored in the library in squeezed
form, so you will have to perform three steps to get them:
1. Get the binary library file.
2. Extract the elements having filename extensions of "DQC" and
"MQG". If you have no facilities for doing this on your
mainframe host (see the earlier comments on mainframe-based
library utilities), then you will have to transfer the library to
a microcomputer and extract the necessary elements there. If
this requirement seems to put you in a "Catch-22" situation
because you have no facilities for mainfrome-to-microcomputer
transfers, there is a way out; read the "Getting Started" section
which follows.
3. Use an "unsqueezer" (described above) to convert the "DQC" and
"MQG" files extracted from the library into "DOC" and "MSG"
files. As in the case of the library extractions, unsqueezing can
be done on either a mainfrome host or a microcomputer, depending
on your circumstances.
Together, these files will tell you just about all there is to know
about getting MODM7xx to run on your machine. Take the time to read
them; they're quite informative. You will also get some helpful
insights from reading some of the overlay files. These overlays,
described in file PD:<CPM.MODEM7>M7OVL-yy.LST, are used to customize
MODM7xx for particular machines without having to edit and assemble
the huge MODM7xx source file. Complete instructions for performing
this procedure are contained in each overlay file. The letters "yy" in
the above filename should be replaced with two digits giving the
current version number as determined from CPM.CRCLST.
And then, there is MEX. MEX stands for "Modem EXecutive", and it is
just what the name implies, a communications and file-transfer program
with a built-in mini operating system that runs under CP/M. This
program can do file transfers using either the Christensen or
CompuServe protocol, and it has an enormous potential for highly
automated operations because it can read and execute command-scripts
pre-stored in disk files. These scripts can include sending commands
to a remote computer, as if they had been sent manually from the
microcomputer in terminal-mode. Users of this relatively new program
are still exploring its possibilities. For more information, look in
CPM.CRCLST under the heading "PD:<CPM.MEX>", and then get the various
files that have "DQC" and "IQF" in their names. These DOCumentation
and INFormation files are stored in squeezed form (note the "Q" in the
filename extensions), so you will have to unsqueeze them. Overlays
for MODM7xx will also work with MEX, but they will not provide all of
the extended MEX features.
Getting Started:
In order to get MODM7xx or MEX running on your CP/M micro, you must
first transfer the necessary files from mainframe to micro. If you
already have a receive-to-disk communications program of some sort,
you can use it to move the needed files. In the long-run it is
essential to be able to transfer 8-bit binary files, but initially it
is not absolutely necessary. Some of the files are quite large. For
example, MODM7xx.COM is over 18K bytes, and the HEX file (which you
will need if you can't transfer 8-bit files) is over 45K. Moving
large files to your micro without using an error detecting protocol
can result in frustrating errors, but it can be done by receiving
multiple copies and using manual or machine-assisted comparisons to
locate and repair bad parts of the code. However, there IS a better
way.
Directory PD:<CPM.STARTER-KIT> contains a short starter-program called
PIPMODEM.ASM which you can get to your mainframe, print it, and then
enter into your microcomputer by hand and assemble. This can then be
used to down-load either MBOOT3.ASM or BMODEM.BAS (depending on
whether you prefer assembly language or BASIC), both of which can
receive files using the error detecting Christensen protocol. Once
you have this capability, you can download the full-function file
transfer program of your choice. To examine this option, send the
following requests to ARCHIVE-REQUEST@SIMTEL20:
SEND RAW PD:<CPM.STARTER-KIT>PIPMODEM.ASM
SEND RAW PD:<CPM.STARTER-KIT>PIPMODEM.DOC
SEND RAW PD:<CPM.STARTER-KIT>MBOOT3.ASM
SEND RAW PD:<CPM.STARTER-KIT>BMODEM.BAS
SEND RAW PD:<CPM.STARTER-KIT>BMODEM.DOC
Read PIPMODEM.DOC first, then look at MBOOT3.ASM and BMODEM.DOC.
PIPMODEM.DOC explains the situation very nicely. Questions concerning
these programs should be sent to INFO-CPM@SIMTEL20.ARPA (NOT to
INFO-CPM-REQUEST).
CONTRIBUTING PUBLIC DOMAIN PROGRAMS
Contributions of public domain software are actively solicited. If
you have something that seems appropriate for inclusion in the
PD:<CPM>, PD:<MSDOS>, or PD:<MISC> archives, please contact Keith
Petersen <W8SDZ@SIMTEL20>. Likewise, contact Richard Conn
<ADA-SW-REQUEST@SIMTEL20> if you wish to contribute to the PD:<ADA>
archive, and Tom Harrison <UNIX-SW-REQUEST@SIMTEL20> if you have
something for the PD:<UNIX> archive.
Special thanks to Dave Towson <Info-Cpm-Request@AMSAA.ARPA> for
writing the original file from which this was extracted.
Happy computing!
Keith Petersen
W8SDZ@SIMTEL20.ARPA
--------
Greeting: H.F. van Rietschote