[net.micro] I thought this might possibly interest you, too.

CHARLIE@wpafb-info1.ARPA (09/07/84)



From:	MAILER         30-APR-1984 13:23  
To:	CHARLIE
Subj:	[Netmail From: cpmlist@Amsaa.ARPA] Re:  Request for addition to INFO-CPM mailing list

Return-Path: <cpmlist@Amsaa.ARPA>
Received: from AMSAA by WPAFB-INFO1.ARPA; 30 Apr 84 13:22:44 EST
Date:     Mon, 30 Apr 84 13:09:43 EDT
From:     Dave Towson (info-cpm) <cpmlist@Amsaa.ARPA>
To:       CHARLIE@wpafb-info1.arpa
Subject:  Re:  Request for addition to INFO-CPM mailing list

Welcome to INFO-CPM!  As you requested, you have been added to the distribution
list for this newsgroup.  Here is some information concerning the public-domain
software available via FTP from SIMTEL20.




                            THE SIMTEL20 ARCHIVES



OVERVIEW

     There is a collossal amount of free public domain CP/M software in
several archives on SIMTEL20, a PDP-20 running TOPS-20 at White Sands Missile
Range.  Files may be obtained using FTP (described in a following paragraph)
with user-name "anonymous".  For a password, use your host-name (or any string
of printing characters).  Throughout this message, FTP examples are given in a
GENERIC syntax.  You will have to consult either a local documentation file or
your friendly system wizard to learn the actual syntax used with your local
mainframe operating system.

     UNIX users can do "man ftp" for instructions.  ITS users can do 
":INFO FTP".  I will be happy to update this message to include pointers to
other sources of documentation if they are sent to INFO-CPM-REQUEST.

     To get directory listings, connect to SIMTEL20 via FTP and do this:

                get micro:<cpm>cpm.crclst 
                get micro:<cpmug>cpmug.crclst 
                get micro:<sigm>sigm.crclst 
		get micro:<unix>unix.crclst 
		get micro:<pc-blue>pc-blue.crclst 

The first will get you a directory of a cpm archive that was moved from MIT-MC.
This is the one to watch for the very latest CP/M offerings, as it is updated
frequently.  The second is the full catalog of the CP/M Users Group.  It (and
the third and fifth archives) will be updated as new disks are issued.  The 
third is the full catalog of the Special Interest Group for Microcomputers 
(SIG/M), a service of the Amateur Computer Group of New Jersey.  The fourth
contains UNIX-related software, not all of which is CP/M-specific.  That which
does apply specifically to CP/M is in the directory <UNIX.CPM>.  The CRCLST
file shows the contents of the full UNIX archive, which is growing rapidly.
The fifth archive contains software for the IBM-PC.

     There are many overlaps in the first three archives, but you will find the
latest versions in the <CPM> archive.  In general, the archived software is
very good, having been worked-over and refined by multiple users.  The comments
tend to be complete and imformative.



FILE TYPES

     Files in the <CPM> archive are stored in two formats, ASCII for DOC, HEX 
and ASM files, and ITS binary for COM and squeezed files.  Squeezed files have
been compressed using the programs available in directory <CPM.SQUSQ> to obtain
an approximate 35-percent size reduction.  These files can be identified by the
letter Q in the file-type field. For example, file MICRO:<CPM.MODEM903>DEFF.AQM
is a squeezed file.  It must be transferred as a binary file, and then un-
squeezed.  The unsqueezing can be done on the CP/M system using USQ-20.COM (or
whatever is the current version from directory <CPM.SQUSQ>), or there are
several host-based unsqueezers in the <CPM> archive (see for example, directory
<CPM.TOPS-20>).  File MICRO:<CPM>CPM.CRCLST shows the type of storage used for
each file in the <CPM> archive.

     ALL FILES in the <UNIX> archive are stored in ASCII.

     With the exception of the CATALOG FILES to be described later, ALL FILES
in the  <SIGM>, <CPMUG>  and  <PC-BLUE>  archives are stored in ITS binary,
a format  which had its origin  at MIT.   Each file  begins with  a  36-bit
identifier-word containing DSK8 in SIXBIT code.  This reads as 446353300000
in octal, and 933AD8000 in hexadecimal.  All data are stored as four 8-bit
bytes per 36-bit SIMTEL20 word, with the low-order four bits of each word
filled with zeros.  If such a file is interpreted as a contiguous string,
as will happen if a straight binary transfer is made to a 16 or 32-bit UNIX
machine, the four zero filler-bits per 36-bit group will cause rather bizarre
and frustrating results.  The methods for dealing with this situation, which
differ from machine to machine, are explained in a following paragraph.

     The ONLY files in the <SIGM>, <CPMUG> and <PC-BLUE> archives that are NOT
stored in ITS binary are the CATALOG files.  These files, which are stored in
ASCII, contain (in reverse numerical order) the -CATALOG.nnn files from all the
volumes of their respective archives.  To obtain these composite catalog
files, connect to SIMTEL20 via FTP and do this:

		get micro:<sigm>sigm.cat 
		get micro:<cpmug>cpmug.cat 
		get micro:<pc-blue>pc-blue.cat 

Remember, ALL are ASCII files.



FILE TRANSFER VIA FTP

     FTP stands for File Transfer Protocol, a formalized procedure for moving
files among machines on the Defense Data Network (DDN) and other networks that
connect with the DDN.  The protocol is implemented by a program called FTP.
The different mainframe operating systems implement FTP with variations in
command syntax.  Some systems have the remote-file-name precede the local-file-
name in the command.  Others reverse this order.  Some versions have the whole
command on a single input line, while others use multiple lines.  Read the
documentation for your local system, or consult a friendly system wizard
for the details of your local FTP command syntax.  FTP transfers from SIMTEL20
can be made with user-name "anonymous".  Use your host-name (or any string of
printing characters) for a password.

     Users of TOPS-10, TENEX, TOPS-20 or ITS systems can use "type image" or
"type paged" mode for ALL transfers.  UNIX users must use "type ascii" mode 
for ASCII files, and "type tenex" or "type L 8" mode for ITS binary files.
MULTICS users must use "type ascii" mode for ASCII files, and "type image"
mode for ITS binary.

     Once an ITS binary file has been transferred to your mainframe, additional
processing is needed to make it into a standard CP/M file.  This processing is
done automatically by the programs used on TOPS-20 and ITS machines for
downloading to a micro, so those users need not be concerned with this.  UNIX
users have only to remove the first four bytes of each file.  These four bytes 
are a special "ITS header", and are not really a part of the file.  They can
be removed using the UNIX utility "dd", or they can be removed using the
program ITSCVT, available as an ASCII-transferable .HEX file in directory
MICRO:<CPM.HEX>.

     Post-processing of files on MULTICS machines can be done using a modified
version of the system copy utility.  At present, transfer of this program is
a delicate matter because of the need to preserve the vendor's proprietary
rights.  If you need this utility, send a message to INFO-CPM-REQUEST, and
I'll put you in touch with the person who has the program.

     Anyone who can obtain an exact contiguous copy of an ITS binary file 
(probably using "type image" mode), and then download it to a CP/M machine
without losing any bits, can post-process the file into standard format using a 
CP/M program available from INFO-CPM-REQUEST.  If there is enough interest in 
this program, it can be added to the <CPM> archive.  If it necessary for you to
take this route, study the description of ITS binary format given in the 
section on FILE TYPES, so that you will know what to expect.  This method 
worked satisfactorily with transfers to our 16 and 32-bit UNIX machines before
we learned to use "type tenex" mode.



MAINFRAME PROGRAMS FOR TRANSFERRING FILES BETWEEN MAINFRAMES AND MICROS

Christensen Protocol:

     For a micro to reliably exchange files with a mainframe, cooperating
file transfer programs with automatic error detection and retransmission 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 MICRO:<UNIX.CPM> contains two programs, UC and the older UMODEM
(both written in C), which implement this protocol on UNIX machines.  See the
file MICRO:<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 in file .INFO.;LMODEM HELP. Other useful ITS utilities include TYPE8,
which types an ASCII file stored in ITS binary format; TYPESQ, which types an
ITS binary format "squeezed" file (see the first paragraph under FILE TYPES);
USQ, which creates an unsqueezed version of a squeezed file; HEXIFY, which
creates an Intel hex format file from an ITS binary format COM file; COMIFY
which creates a COM file from an Intel hex file; and CRC, which computes the
Cyclic Redundancy Check value for a file, using the same algorithm that is used
by the CP/M program CRCK.  Brief instructions for any of these utilities except
LMODEM can be obtained by typing ":utility_name" (for example, :CRC).

     TOPS-20 utilities for transferring and manipulating files can be found in
directory MICRO:<CPM.TOPS-20>.  See MICRO:<CPM>CPM.CRCLST for a list of
available programs.

     File transfer and conversion utilities for use with VAX/VMS machines are
contained in directory MICRO:<CPM.VAXVMS>.  See MICRO:<CPM>CPM.CRCLST for
details.


Kermit:

     Another excellent program for transferring files is called KERMIT.  This
program has the advantage of being available for an impressively large number
of mainframes and micros.  It is, for example, available for the IBM-PC, and
DOES NOT require CP/M.

     To get started with KERMIT, connect to Columbia-20 using FTP, and do this:

		get ps:<kermit>00readme.txt 
		dir ps:<kermit> 

Note two things:  The machine name is "columbia-dash-twenty", and the filename
begins with "zero-zero".

     After reading 00README.TXT, look at your directory listing and see what's
currently available (it may have changed since the last edit of 00README.TXT).
Questions can be addressed to INFO-KERMIT-REQUEST @ COLUMBIA-20.



MICROCOMPUTER PROGRAMS FOR TRANSFERRING FILES BETWEEN MAINFRAMES AND MICROS

Christensen Protocol:

     An excellent program for transferring files between micros, or between
micros and mainframes is called MDM7xx, 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 MDM7xx, you should first FTP and examine three files
from the directory MICRO:<CPM.MODEM7>.  After connecting to SIMTEL20, do this:

		get micro:<cpm.modem7>(see below) 
		get micro:<cpm.modem7>mdm7xx.doc 
		get micro:<cpm.modem7>mdm7xx.msg 

All are ASCII files.  Together, they will tell you just about all there is to
know about getting the program to run on your machine.  Take the time to read
these files; they're quite informative. You will also get some helpful insights
from reading some of the overlay files.  These overlays, described in file
MICRO:<CPM.MODEM7>(see below), are used to customize MDM7xx for particular
machines without having to edit and assemble the huge MDM7xx source file. 
Complete instructions for performing this procedure are contained in each 
overlay file.  The above use of "see below" refers to a file with the
characters "OVL" in its name.  This message will be updated when the name of
that file becomes stable (at this moment, there are two).


Kermit:

     As stated in an earlier paragraph, KERMIT is also an excellent program for
transferring files between computers.  It, too, does automatic error detection 
and retransmission, and it works between mainframe and micro, between micros,
and between mainframes.  See the earlier paragraph for details.


Getting Started:

     In order to get MDM7xx or KERMIT running on your 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.  It is VERY CONVENIENT to be able to transfer 8-bit binary
files, although in most cases it is not absolutely necessary.  Some of the 
files are quite large.  For example, MDM7xx.COM is over 18K bytes, and the HEX
file (which you will need if you can't transfer 8-bit files) is over 52K.  
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 MICRO:<CPM.MODEM> contains a file that can be FTPed to your
mainframe, printed, and then entered into your micro by hand and assembled. 
It is quite short.  To examine this option, connect to SIMTEL20 via FTP and
do this:

		get micro:<cpm.modem>pipmodem.asm 
		get micro:<cpm.modem>pipmodem.doc 
		get micro:<cpm.modem>mboot3.asm 

All are ASCII files.  Read PIPMODEM.DOC first, then look at MBOOT3.ASM.
PIPMODEM.DOC explains the situation very nicely.  Questions concerning these 
programs should be sent to INFO-CPM @ AMSAA.



ADDITIONS, IMPROVEMENTS AND CORRECTIONS

     Suggestions for additions, improvements and corrections to this message
are always welcome.  Please send them to INFO-CPM-REQUEST.  Additional
information concerning FTP is, however, beyond the scope of this message.  If
you need help with FTP, please read the documentation for your local system,
or see your friendly system wizard.

     Contributions of public domain software are actively solicited.  If you
have something that seems appropriate for inclusion in the <CPM> archive, 
please contact Keith Petersen <W8SDZ@SIMTEL20>.  Likewise, contributions to the
<UNIX> archive can be addressed to Richard Conn <RCONN@SIMTEL20>.

     Happy hacking!



					Dave Towson
					INFO-CPM-REQUEST @ AMSAA





P.S.  Please note the following changes:



Received: From brl-vgr.arpa.ARPA by AMSAA via smtp;  28 Apr 84 22:54 EST
Received: from simtel20.arpa by BRL-VGR.ARPA id a010988; 28 Apr 84 22:55 EST
Date: 28 Apr 1984  20:54 MST (Sat)
Message-ID: <WANCHO.12011218699.BABYL@SIMTEL20>
From: "Frank J. Wancho" <WANCHO@simtel20.ARPA>
To:   INFO-CPM@BRL-VGR.ARPA
Cc:   INFO-MICRO@BRL-VGR.ARPA
Subject: Space crunch and tar tapes

The current collections of public domain files are bursting the seams
of the RP06 that's holding them.  Here are the current disk usage
stats taken Friday afternoon:

MICRO:<CPM.*>		14,818 disk pages
MICRO:<CPMUG.*>		 7,692			15.4 MBytes
MICRO:<SIGM.*>		20,192			40.4
MICRO:<PC-BLUE.*>	 3,260			 6.5
			------			----
Total:			46,019 disk pages	62.3 MBytes

A TOPS-20 disk page is 512 36-bit words, and the above figures include
the values for the superior directories in each case.

On top of that, it also looks like I'll be getting new SIG/M releases
monthly (five more volumes just showed up).  So, to relieve the
potential trauma of lack of elbow room on MICRO:, I have prevailed
upon Gail Zacharias to apply her file type determining algorithms used
in DE-LBR to build another program.  This program analyses each file
and converts only those files which it determines are truly ASCII text
files, but stored in ITS-Binary format, into ASCII text files.  I'll
be running her program on the files in the above directories, except
MICRO:<CPM.*> over the next few days.

This, of course, means that my oft-repeated statement that ALL the
files in those directories are stored in ITS-Binary format will no
longer be true.  To avoid confusion, Gail's program happens to write
out the next generation, which will be .2 in most cases.  This means
that your clue for FTP is that if the filename shows up as file.typ.1,
it is ITS-Binary, and if it shows up as file.typ.2, it is ASCII.  You
will also have an updated .CRCLST to reference, which shows the
storage method for each file.

Simply because ASCII text files are stored five characters per word,
instead of four bytes per word in ITS Binary format, I expect to
recover a considerable amount of file space by using this utility.
However, the catch is, other than looking for the .2 generation
number, that most of the CRC values published with each volume and
elsewhere will no longer match the files stored in ASCII format.

Don't expect the conversions to happen all at once.  Just be forwarned
that things are changing if you see something strange.

Finally, a note for those of you on Unix machines, especially those
not connected to DDN (and thus do not have FTP access to SIMTEL20).  I
have received an updated version of the TOPS-20 tar program which can
now write binary as well as ASCII files to tar tapes.  After I finish
the conversions, I'll see if I can find time to experiment with the
program to see how many tapes will be needed to store all these files.
What I expect we can do is make a set of tapes available to a
volunteer beta site to see if they can be read.  If so, then start
them out to a distribution path to interested sites who are willing to
provide the disk space to keep them online, or to make copies for
further distribution.  Just bear in mind that these files are as-is.

--Frank


Received: From simtel20.arpa.ARPA by AMSAA via smtp;  29 Apr 84 19:58 EDT
Date: 29 Apr 1984  18:00 MDT (Sun)
Message-ID: <WANCHO.12011438247.BABYL@SIMTEL20>
From: "Frank J. Wancho" <WANCHO@SIMTEL20>
To:   GZ@MC
cc:   WANCHO@SIMTEL20, W8SDZ@SIMTEL20, towson@AMSAA
Subject: Results of ASCIFY use

Gail,

I just finished processing all of our what used to be ITS-Binary-only
directories, and the overall space-savings was 3,708 pages, and NOT
the some 15,000 I expected.  Still, it did recover *some* space --
3,708 pages is not a light-weight figure.  Turned out to be about 12%.

Only problem with ASCIFY I encountered in the batch job was that I had
neglected to remove the empty directories from being processed.
ASCIFY aborted the batch job when it found the first such directory.
No big deal -- it worked fine.  Used /DWIM for everything.

There are still some files with names implying that they are ASCII,
but were left alone by ASCIFY.  As best as I can figure, they are
files created by W*.  I will leave them alone.  I believe the .2
generation number is a good-enough clue, and besides, if someone took
the trouble to use W* to create the file, I'm sure there was a reason.
I think I've fooled with Mother Nature long enough for one day...

Again, thanks for yet another handy utility!

--Frank


Received: From brl.arpa.ARPA by AMSAA via smtp;  30 Apr 84 1:13 EDT
Received: From simtel20.arpa.ARPA by BRL-AOS via smtp;  30 Apr 84 1:13 EDT
Date: 29 Apr 1984  23:11 MDT (Sun)
Message-ID: <WANCHO.12011494826.BABYL@SIMTEL20>
From: "Frank J. Wancho" <WANCHO@Simtel20.ARPA>
To:   INFO-CPM@Brl-Aos.ARPA
Cc:   INFO-MICRO@Brl-Aos.ARPA
Subject: Collection Conversions Complete

The conversions of MICRO:<PC-BLUE.*>, MICRO:<CPMUG.*>, and
MICRO:<SIGM.*> are now complete.  Files with a generation number of .2
are ASCII files, while those with .1 remain ITS-Binary files.

Some files with apparent ASCII filetype names, such as, .BAS, .ASM,
.DOC, and others, were not converted because a high-bit was detected or
there were more than 40% control characters before the first ^Z (the
CP/M EOF for ASCII files).  The most likely reason is that such files
were created or edited using WordStar in Document mode.  There will be
no further conversions attempted on such files.

Each of the above directories now contains an up-to-date .CRCLST file
which indicates which files are "COM" (ITS-Binary) and which are ASCII
files.

For those interested in such things, the total disk space recovered
was 3,708 pages or about 12%.  Not quite as much as I had hoped, but
every page counts.

--Frank



From:	MAILER          3-MAY-1984 10:06  
To:	ELDER,CHARLIE
Subj:	[Netmail From: W8SDZ@Simtel20.ARPA] SIMTEL20 CP/M directory list update

Return-Path: <info-cpm-request@AMSAA.ARPA>
Received: from AMSAA by WPAFB-INFO1.ARPA;  3 May 84 10:05:54 EST
Received: From simtel20.arpa.ARPA by AMSAA via smtp;  3 May 84 9:24 EDT
Date: 3 May 1984  07:16 MDT (Thu)
Message-ID: <KPETERSEN.12012369530.BABYL@SIMTEL20>
Sender: KPETERSEN@Simtel20.ARPA
From: Keith Petersen <W8SDZ@Simtel20.ARPA>
To:   Info-Cpm@Amsaa.ARPA
Subject: SIMTEL20 CP/M directory list update

MICRO:<CPM>CPM.CRCLST on SIMTEL20 (the file listing all the filenames,
sizes and CRCs of the MICRO<CPM.xx> directories) has been updated as
of today.  If you cannot FTP it, and you are not already on the list
to receive it via netmail, send a note to W8SDZ@SIMTEL20 asking to be
added to the list.

--Keith


From:	MAILER          4-MAY-1984 14:29  
To:	ELDER,CHARLIE
Subj:	[Netmail From: wcwells%ucbopal.CC@Ucb-Vax.ARPA] Re: SIMTEL help (SIMTELP?..yuk)

Return-Path: <info-cpm-request@AMSAA.ARPA>
Received: from AMSAA by WPAFB-INFO1.ARPA;  4 May 84 14:29:25 EST
Received: From brl.arpa.ARPA by AMSAA via smtp;  4 May 84 13:11 EDT
Received: From ucb-vax.arpa.ARPA by BRL-AOS via smtp;  4 May 84 13:06 EDT
Received: from ucbjade.CC.Berkeley.ARPA (ucbjade.ARPA) by UCB-VAX.ARPA (4.24/4.27)
	id AA21936; Fri, 4 May 84 10:03:50 pdt
Received: from ucbopal.CC.Berkeley.ARPA by ucbjade.CC.Berkeley.ARPA
	(4.14.3/4.16) id AA25025; Fri, 4 May 84 10:04:02 pdt
Received: by ucbopal.CC.Berkeley.ARPA
	(4.14/4.16) id AA25762; Fri, 4 May 84 10:03:27 pdt
Date: Fri, 4 May 84 10:03:27 pdt
From: William C. Wells <wcwells%ucbopal.CC@Ucb-Vax.ARPA>
Message-Id: <8405041703.AA25762@ucbopal.CC.Berkeley.ARPA>
To: sdcsvax!bmcg!asgb!rob@Ucb-Vax.ARPA
Subject: Re: SIMTEL help (SIMTELP?..yuk)
Cc: info-cpm@Brl-Aos.ARPA

You must be on a host conected to one of the Internet networks (eg.
ARPANET, MILNET, etc.) to access files in the CPM program library on
the SIMTEL20 system. The CPM program library on SIMTEL20 is primarily
an organized version of the CP/M Users Group and SIG/M public software
volumes (with superceded versions of programs deleted).

The CP/M Users Group and SIG/M public domain volumes are available from
several offnet sources. One of the best offnet sources for CPM public
software is the PicoNet CP/M Users Group, P.O. Box 391566, Mountain
View, CA 94039.

Bill Wells
wcwells@Berkeley.ARPA
ucbvax!wcwells


From:	MAILER         21-MAY-1984 13:31  
To:	CHARLIE
Subj:	[Netmail From: cpmlist@Amsaa.ARPA] Re:  Removal from INFO-CPM mailing list

Return-Path: <cpmlist@Amsaa.ARPA>
Received: from AMSAA by WPAFB-INFO1.ARPA; 21 May 84 13:31:09 EST
Date:     Mon, 21 May 84 13:21:23 EDT
From:     Dave Towson (info-cpm) <cpmlist@Amsaa.ARPA>
To:       CHARLIE@wpafb-info1.arpa
Subject:  Re:  Removal from INFO-CPM mailing list

Charlie - per your request, you have been deleted from info-cpm distribution.



Dave Towson
info-cpm-request@amsaa


------