L From:	HENRY::IN%"RCONN%SIMTEL20.ARPA%relay.cs.net@rca.com"  6-SEP-1986 20:47, To:	EVERHART%ARISIA%rca.com@CSNET-RELAY.ARPA, Subj:	Welcome to the Ada Software Repository  =            WELCOME TO THE ADA SOFTWARE REPOSITORY ON SIMTEL20   F         You are now on the ADA-SW mailing list, through which users of> the Ada Software Repository (ASR) communicate with each other.  F         This  is  your  Welcome  to the Ada Software Repository, and aF copy of this message is kept  in  PD:<ADA.GENERAL>WELCOME.DOC  if  youF want  to  see  it  again  or  copy  it  for  other uses.  Feel free toF distribute this message and any other files in  PD:<ADA.GENERAL>  thatF you  wish  to take.  You may publish these files (in PD:<ADA.GENERAL>)F in  any  newsletter  or  commercial  publication  you  desire  without restriction.  2         This message contains the following files:   	  FILE					CONTENTS   4 PD:<ADA.GENERAL>ADAREPOS.DOC		Overview of RepositoryB PD:<ADA.GENERAL>AAREAD.ME		Pointers to Answers to Common Questions5 PD:<ADA.GENERAL>OPERATE.DOC  		Statement of Operation 7 PD:<ADA.GENERAL>FTP.DOC			How to Use FTP and Other Info 8 PD:<ADA.GENERAL>MLIST.DOC		About the ADA-SW Mailing List: PD:<ADA.GENERAL>FINDME.DOC              How to Find Things7 PD:<ADA.GENERAL>DIRLIST.DOC		Summary of ADA Directories = PD:<ADA.GENERAL>TAPEDIST.DOC		Acquiring Magtape of Repository 7 PD:<ADA.GENERAL>UUCPBIT.DOC		For non-DDN-resident users 5 PD:<ADA.GENERAL>NEWSLTR.DOC		About the ASR Newsletter 5 PD:<ADA.GENERAL>INDEX.DOC		About the ASR Master Index    	   F         This  Repository  has  been  set  up  for  YOU, and I heartilyF encourage your interaction, comments, questions, and support.  If  youF like  it,  use it, and find it to be of value, it has succeeded in itsF purpose.  If there is something about it that you don't like, use  theF ADA-SW  mailing  list  to  let all the users know or send a message toF ADA-SW-REQUEST@SIMTEL20 if you want to address the maintainer  of  the repository directly.  ;         Welcome to the Ada Software Repository on SIMTEL20!    	  				Richard Conn     ----> ADAREPOS.DOC <----  =                 The Ada Software Repository (ASR) on SIMTEL20   F         A   repository  of  Ada  programs,  software  components,  andF educational  material  has  been  established  on  the  SIMTEL20  hostF computer  on  the  Defense  Data  Network.   This  repository has beenF accessible to any host computer on  the  network  since  November  26, 1984.   F         This repository provides a free source for  Ada  programs  andF information.   By  employing the File Transfer Protocol (FTP) program,F users of DDN hosts are able to scan the directories of the  repositoryF and  transfer  files  to  their hosts.  If the files are Ada programs,F they may then compile these programs and  use  them  as  they  desire.F Modifying  these  programs  may  be  within their rights, and they mayF freely distribute these programs within and without the  DoD  as  theyF desire,  subject  to  the  restrictions  specified  for  each piece of software in its prologue.   F         The   Ada   Software   Repository   is  divided  into  severalF subdirectories.  These directories are organized by topic,  and  theirF names  and  a brief overview of their topics are contained in the file  DIRLIST.DOC in PD:<ADA.GENERAL>.  F         The  Ada  Software  Repository  on  SIMTEL20  serves two basicF roles:  to promote the exchange and use (reusability) of Ada  programsF and   tools  (including  components)  and  to  promote  Ada  educationF (especially by providing  several  working  examples  of  programs  in, source form for people to study and modify).  F         All members of the Ada  community  are  encouraged  to  freelyF extract  information  and programs from the repository as well as makeF contributions to it.  The only restrictions which apply to the  accessF and  use  of  this  software  are  presented  in the "Distribution andF Copyright" section of the  prologue  associated  with  each  piece  of	 software.      ----> AAREAD.ME <----      	 6 COMMONLY ASKED QUESTIONS AND WHERE TO FIND THE ANSWERS- SUBJECT:  ADA SOFTWARE REPOSITORY ON SIMTEL20    	 F         The  following  is  a collection of questions and the names ofF files which contain complete or partial answers  to  these  questions.F Unless    otherwise    noted,    these    files   are   contained   in PD:<ADA.GENERAL>.    	  QUESTION						FILES   D  1. What is the Ada Repository on SIMTEL20?		ADAREPOS.DOC, AAREAD.ME 							WELCOME.PRO  >  2. How do I Access the Ada Repository?			FTP.DOC, UUCPBIT.DOC 							TAPEDIST.DOC   J  3. How do I Find Out What is in the Ada Repository?	FINDME.DOC, MLIST.DOC 							DIRLIST.DOC, NEWSLTR.DOC  							INDEX.DOC  3  4. How do I Submit Software and other Items to the 2      Ada Repository?  How do I Modify and ResubmitM      Software that is already in the Ada Repository?	SUBMIT.DOC, CHECKOUT.DOC   2  5. How do I Contact the Repository Maintainer and/      other Users of the Repository?			MLIST.DOC   +  6. How do I get Started with Using the Ada +      Repository?					WELCOME.DOC, MLIST.DOC  							INDEX.DOC  /  7. How do I Contact the Authors of Software in 4      the Ada Repository?				PROLOGUE.DOC, SUBMIT.DOC   	      ----> OPERATE.DOC <----   @                 Statement of Operation - Ada Software Repository  F         The  Ada  Software  Repository  on  SIMTEL20 and the tape copyF service are unfunded activities and have been so  since  Richard  ConnF proposed  the  idea to Frank Wancho in November, 1984.  The disk driveF on which the repository is sharing space  with  other  collections  isF funded  by  the  Logistics  System  Support  Activity  (LSSA), an ArmyF Materiel Command (AMC, formerly DARCOM) activity.  LSSA  provided  theF funds  for the disk drive to support the UNIX/C collection for the AMCF community, which, because of the availability  via  ANONYMOUS  FTP  onF DDN,  is  available  to  the  entire  DDN community.  The Ada SoftwareF Repository resides on SIMTEL20  because  there  happens  to  be  space available on that disk drive.   F         SIMTEL20  is  owned  and  operated  by  the  Computer  SystemsF Directorate  at  White  Sands Missile Range in New Mexico, which is anF Installation/Field Operating  Activity  (I/FOA)  under  the  Test  andF Evaluation  Command  (TECOM)  at  Aberdeen Proving Ground in Maryland.F TECOM is, in turn, a major subordinate command under AMC.   AMC  is  a/ major command under the Department of the Army.   F         Richard Conn is the maintainer/operator of  the  Ada  SoftwareF Repository  and  also  maintains  the  ADA-SW electronic mailing list.F Frank Wancho is the sponsor of the Ada Software  Repository  and  runsF the  tape  distribution  service.   Both  Richard  and Frank work on a voluntary, unfunded basis.  F         The  Ada  Software  Repository  is not associated with the AdaF Joint Program Office.  All software, documentation, and other items ofD information in the Ada Software Repository are in the public domain.     ----> FTP.DOC <----     1                             THE SIMTEL20 ARCHIVES        SIGNIFICANT CHANGES   F      New MSDOS  archive  added:   SIMTEL20  now  has  a  new  archive,F PD:<MSDOS>.   This  archive,  like  the PD:<PC-BLUE> archive, containsF software for the MSDOS and PCDOS operating systems.   But  unlike  PC-F BLUE,  this archive is locally managed, and will be updated more oftenF (the PC-BLUE archive is updated only when new disks are issued by  theF PC-BLUE  Users  Group).   For  a  list  of  files,  get  a copy of the' directory file, PD:<MSDOS>MSDOS.CRCLST.   F      Newsgroup   correspondence   archive   files   moved:   NewsgroupF correspondence   archives   have    been    moved    from    directoryF PS:<MAIL.ARCHIVES>  to individual directories having names of the formF PS:<ARCHIVES.KEYWORD>, where "KEYWORD" has been chosen to indicate theF associated   newsgroup.    See   the   section   entitled   "NEWSGROUP0 CORRESPONDENCE ARCHIVES" for additional details.  F      Public  domain  archive  files  moved:   A  new large disk deviceF called PD:  has been installed  to  house  the  entire  public  domainF software   collection.   All  files  are  now  accessible  using  file specifications of the form:   4                         PD:<directory_name>file_name   Example:  5                         PD:<CPM.STARTER-KIT>LU310.COM   F      New logical names:  Files  in  the  <CPM>  archive  can  also  beF specified  with a new shortened notation using a logical name for eachF directory.  Thus, the file in the above example can also be  specified as:   -                         STARTER-KIT:LU310.COM   F         Note that the part of the directory name following the dot hasF been used as the logical name (followed by a  colon).   But  remember,F this new form of file specification applies only to the <CPM> archive.F To avoid confusion, all examples in the text to follow  will  use  the@ PD:  specification, as this form works with ALL of the archives.  F      Getting  started:   The   above   example   provides   a   sneakyF introduction  to  yet another new feature that should greatly ease theF "bootstrap  phase"  for  new  archive  users.   Now  in   one   place,F PD:<CPM.STARTER-KIT>, you will find all of the basic essentials neededF to begin using the archives.  These programs  provide  the  means  forF transferring,  unsqueezing  and  de-librarying archive files, and moreF will be said about them later in  this  document.   Special  kudos  to? archive maintainer Keith Petersen for this worthwhile addition.   F      Finally, a reminder:   For  quite  some  time  now,  "ITS  binaryF format"  has not been used for storage of binary files in the SIMTEL20F archives.  If you are a new user of the archives and  you  don't  knowF what ITS binary format is, don't worry about it; it no longer matters.F But apparently, some "veteran archive users" are still unaware of  theF change.  Therefore, please note that stripping the first four bytes ofF binary files, once necessary for removal of the special "ITS  header",F is  no  longer required.  Indeed, if you do this now, YOU WILL DESTROY
 THE FILES.       OVERVIEW  F      There is a collossal amount of free public  domain  software  forF the  CP/M,  PCDOS/MSDOS  and  UNIX  operating systems, and for the DoDF standard  programming  language,   Ada,   in   several   archives   onF SIMTEL20.ARPA,  a DECsystem-20 running the TOPS-20 operating system atF White Sands Missile Range.  Archives  of  correspondence  for  several3 newsgroups, including INFO-CPM, are also available.   F      You can obtain these  files  using  the  InterNet  file  transferF protocol,  FTP  (described  in  a following paragraph), with user-nameF "anonymous".  For a login password, use your host-name  or  any  otherF string  of printing characters.  Throughout this message, FTP examplesF are given in a GENERIC syntax.  You will have to consult either  localF documentation  or  your  friendly  system  wizard  to learn the actualF syntax used with your local mainframe operating system.  For the  sakeF of  brevity,  the  domain  suffix ".ARPA" will be dropped from further* references to SIMTEL20 in this discussion.  F      To  obtain directory listings, connect to SIMTEL20 via FTP and do this:    	 '                 get pd:<cpm>cpm.crclst  +                 get pd:<cpmug>cpmug.crclst  )                 get pd:<sigm>sigm.crclst  ! 		get pd:<pc-blue>pc-blue.crclst   		get pd:<msdos>msdos.crclst 		get pd:<unix>unix.crclst   		get pd:<ada>ada.crclst 	   F         The <CPM> archive is the one to watch for the very latest CP/MF offerings, as it is updated frequently.  The <CPMUG>, <SIGM> and  <PC-F BLUE>  archives  contain software distributed by the CP/M Users Group,F the SIG/M Users Group and the PC-Blue Users Group respectively.   ThisF software  is  available on diskettes from the associated users groups,F and the archives are updated as new volumes are issued.  The <PC-BLUE>F archive  contains  software for the IBM-PC and similar machines.  SomeF runs under CP/M, and some under PCDOS/MSDOS.  The <MSDOS> archive alsoF contains  software for the MSDOS and PCDOS operating systems; but thisF archive is locally managed, and therefore is updated  more  frequentlyF than  the <PC-BLUE> archive.  The <UNIX> archive contains a variety ofF UNIX tools.  Those  which  apply  specifically  to  CP/M  are  in  theF directory   <UNIX.CPM>.    The   <ADA>  archive  is  growing  rapidly.F Information about this archive is in directory  PD:<ADA.GENERAL>.   InF general,  the  archived software is very good, having been worked-overF and refined by many users.  The documentation and comments tend to  beF complete  and  informative.   Files  in  all  of these archives can be< obtained using the FTP procedures described in this message.  F      But  please note that due to the large number of files available,F the archive maintainers cannot possibly attempt to validate the properF operation  of  the  various programs.  When a program bug is reported,F immediate action is taken to either correct the error  or  remove  theF offending  program  from  the  archives.  Still, users must understandF that  all  archive  programs  are  offered  AS  IS,  and  the  archiveF maintainers  specifically disclaim any liability should these programsF malfunction or cause damage, incidental or  otherwise.   When  testingF ANY  new  software,  be certain that all information stored on disk isF backed-up before you start, so that  you  can  recover  if  files  areF damaged or erased.  This is particularly true if you have a hard disk,< in which case malfunctions can be spectacularly disasterous.      
 FILE TYPES  F      Files are stored in two formats:  Text files such as  those  withF names  that  end  with  DOC,  HEX, INF and ASM are sometimes stored asF ASCII files, but usually these files are  stored  in  binary  squeezedF form.   Binary  storage  is also used for executable (COM) and libraryF files.  Squeezed and library files are described  below.   All  binaryF data are stored as four 8-bit bytes per 36-bit SIMTEL20 word, with theF low-order four bits of each word filled with zeros.  If such a file isF interpreted  as  a  contiguous  string,  as  will happen if a straightF binary transfer is made to a 16 or 32-bit UNIX machine, the four  zeroF filler-bits per 36-bit group will cause rather bizarre and frustratingF results.  The methods for dealing with this  situation,  which  differ@ from machine to machine, are explained in a following paragraph.  F      Squeezed files have been compressed using programs  available  inF directory   <CPM.SQUSQ>  to  obtain  an  approximate  35-percent  sizeF reduction.  These files can be identified  by  the  letter  Q  in  theF extension  field.  For example, the file PD:<CPM.ASMUTL>RMACPAT.AQM isF a squeezed file.  It must be transferred as a binary  file,  and  thenF unsqueezed.   The  unsqueezing can be done on a CP/M system using USQ-F xx.COM (where "xx" is the current version) from directory <CPM.SQUSQ>,F or  there  are  several host-based unsqueezers in the <CPM> and <UNIX>E archives (see for example, directories <CPM.TOPS-20> and <UNIX.CPM>).   F      CP/M  library  files  (those  with  names  ending in LBR) combineF several regular CP/M files into a single BINARY file which contains anF internal  directory  of its contents.  They are created using the CP/MF library utility LUxxx.COM (where "xxx" is the current version) or someF other compatible utility.  The complete packages for LUxxx and a newerF compatible program called NULUxx (where "xx" is the  version)  can  beF found  in  directory  PD:<CPM.CPMLIB>.   C-language  source code for aF compatible UNIX utility called LAR (library archiver) is in  directory PD:<UNIX.CPM>.  F      Although the type of storage  used  for  a  particular  file  canF usually  be  inferred from the file-name, this is not always true.  ItF is a good idea to check the appropriate "crclst" file to ascertain theF storage  format  used  for  each  file  of interest.  Now, and for theF foreseeable future, storage formats for files in the  <SIGM>,  <CPMUG>F and  <PC-BLUE>  archives  can  be  determined  from  their "generationF numbers", as shown by the FTP directory command.  For example, the FTP command:  '                 dir pd:<pc-blue.vol001>c   will yield results of the form:m   	t 		-CATALOG.001.2 		ABSTRACT.001.2
 		BW.ASM.2
 		BW.BAS.1
 		BW.EXE.1
 		COLOR.ASM.2E
 		COLOR.BAS.1 
 		COLOR.EXE.1t 		...and so on 	i  F         All files with names ending  in  ".1"  are  stored  in  binaryF format, and those with names ending in ".2" are stored in ASCII.  ThisF relationship will continue to apply for files in the  <SIGM>,  <CPMUG>, and <PC-BLUE> archives until further notice.  A      WARNING:  Because the public  domain  archives  on  SIMTEL20 A                consume  a  huge  amount  of  disk-space,  storage A                capacity  will  be  conserved  by   the   greatesttA                practical  use  of  libraries  and squeezed files,.A                both of which are stored in binary format.  If you	A                cannot  properly  transfer  binary  files, you areyA                going to be VERY FRUSTRATED!  If  you  need  help,sA                please   contact  your  local  system  wizard  andEA                provide him/her  with  a  copy  of  this  message.SA                Having  done that, if you are still unable to make A                things work correctly, send a message to INFO-CPM-oA                REQUEST  at AMSAA.ARPA and I will try to help you. 8                Please provide the following information:   	nB 	1. Machine and operating system  (e.g., VAX-11/780, 4.2 BSD UNIX)/ 	2. Network software in use  (e.g., 3-Com UNET)eC 	3. Complete list of available FTP commands  (e.g., GET, PUT, etc.)n 	   F      Important  files  in  the  <CPMUG> and <PC-BLUE> archives are theF CATALOG files.  These files, which are stored in ASCII, contain the "-F CATALOG.nnn"  files from all the volumes of their respective archives.F To obtain these composite catalog files, connect to SIMTEL20  via  FTP and do this:   	E 		get pd:<cpmug>cpmug.cat $ 		get pd:<pc-blue.vol000>pcblue.cat  	y  F         A similar file exists for the <SIGM> archive, but it is storedF in  squeezed  form.   This  file, when unsqueezed, yields SIG.CAT (the4 catalog).  It can be obtained using the FTP command:  +                 get pd:<sigm.vol000>sig.cqta  7         (NOTE:  That's "L-and-three-zeros" in "vol000")a       FILE TRANSFER VIA FTPo  F      FTP stands for File Transfer Protocol, a formalized procedure forF moving  files  among  machines  on  the Defense Data Network (DDN) andF other networks that connect with the DDN.  The protocol is implementedF by  a  program  often  called  FTP.  The different mainframe operatingF systems implement FTP with variations in command syntax.  Some systemsF have the remote-file-name precede the local- file-name in the command.F Others reverse this order.  Some versions have the whole command on  aF single  input  line,  while  others  use  multiple  lines.   Read  theF documentation for your local system,  or  consult  a  friendly  system8 wizard for the details of your local FTP command syntax.  F      UNIX  users  can  do  something  like  "man  ftp"   for   on-lineF instructions.  However, not all UNIX FTP programs are called "ftp", soF you may have to snoop around in the system directories or ask a systemF wizard  for the correct local name to use with the "man" command.  ITSF users can do ":INFO FTP", and "HELP FTP" works  on  TOPS-20  and  someF other  operating systems.  I will be happy to update this message withF pointers to other sources of on-line documentation if they are sent to INFO-CPM-REQUEST@AMSAA.ARPA.  F      FTP  transfers  from  SIMTEL20  can  be   made   with   user-nameF "anonymous".   Use  your  host-name  or  any  other string of printingF characters for a password.  For anonymous  logins,  SIMTEL20  supportsF the FTP "change working directory" command.  (Your local syntax may beF something like CD, or CWD.)  Ignore the message that  prompts  you  toF enter  a  password.   This  command  allows  you  to specify a defaultF SIMTEL20 directory to be used for all  file  retrievals,  and  therebyF relieves you from having to repeatedly type "pd:<whatever>" as part of< each filename.  For example, you can do something like this:   	i 		cd pd:<cpm.goodstuff>u 		get filename-1 		get filename-2 		...and so on 	o  F instead of using the longer filename forms shown in previous examples.  F      Users of TOPS-10, TENEX, TOPS-20 or ITS systems can  use  "image"F or  "paged"  mode for ALL transfers.  UNIX users must use "ascii" modeF for ASCII files, and "tenex" or "type L  8"  mode  for  binary  files.F MULTICS  users  can use "ascii" mode for ASCII files, but binary filesF require special treatment that is  best  described  by  the  following> example provided by Paul Schauble <Schauble@mit-multics.arpa>:   	d     !ftp simtel20 M      220 SIMTEL20.ARPA FTP Server Process 5Z(14)-7 at Mon 10-Sep-84 00:27-MDTe         user_ftp:  !login anonymous8      331 ANONYMOUS user ok, send real ident as password.      Password:  !guest  D      user_ftp:  !quote "type l 8" <--(NOTE: That's lowercase "L" 8.)      200 Type L bytesize 8 ok.  9      user_ftp:  !get micro:<cpm.zcpr3>alias.hlp alias.hlpI:      150 Retrieve of MICRO:<CPM.ZCPR3>ALIAS.HLP.1 started.      226 Transfer completed.'      Total elapsed time:  35.7 seconds. <      4348 bytes transferred in 18.5 seconds (1850 bits/sec).        user_ftp:  !quitt(      221 QUIT command received. Goodbye. 	o  F         Lines beginning with "!"  are typed by the terminal user.  TheF received  files  are  stored  on MULTICS with one 8-bit byte per 9-bitF word, and  can  be  trans-  ferred  to  a  microcomputer  with  Kermit% (described in a following paragraph).u  F      All aspects of the  FTP  process  for  UNIX  machines  have  beenF automated  to  a  high degree by a program in directory PD:<UNIX.CPM>.F With this program, a simple command like "mb modm700.com" can  connectF to  SIMTEL20 and transfer the binary file "modm700.com" from directoryF PD:<CPM.MODEM7> to a local file also named "modm700.com", all with  noF user  intervention.   Batch command files containing multiple lines ofF the form in the above example can be run in no-hangup background  modeF to  transfer whole directories without the user even remaining logged-F in  on  his  local  system.   For  more  information,  get  the   file PD:<UNIX.CPM>AUTOFTP.DOC.       8 PROGRAMS FOR FILE TRANSFER BETWEEN MAINFRAMES AND MICROS  ( Christensen Protocol Mainframe Programs:  F      For  a  micro  to  reliably  exchange  files  with  a  mainframe,F cooperating  file transfer programs with automatic error detection andF retransmission of faulty blocks must be  running  on  both  computers.F One  such  family  of programs uses a popular protocol created by WardF Christensen and enhanced by others.  Directory PD:<UNIX.CPM>  containsF two  programs,  UC  and  the  older  UMODEM (both written in C), whichF implement  this   protocol   on   UNIX   machines.    See   the   file? PD:<UNIX>UNIX.CRCLST for a list of other useful UNIX utilities.u  F      On ITS machines, file transfer using the Christensen protocol canF be  done  using  MMODEM  (type  :MMODEM  for instructions), or LMODEM.F Documentation for LMODEM is in file .INFO.;LMODEM HELP.  Other  useful ITS utilities include:   	U: 	TYPE8  - types an ASCII file stored in ITS binary format.C 	TYPESQ - types an ITS binary format "squeezed" file (see the firstg& 	         paragraph under FILE TYPES).; 	USQ    - creates an unsqueezed version of a squeezed file. D 	HEXIFY - creates an Intel hex format file from an ITS binary format 	         COM file.e4 	COMIFY - creates a COM file from an Intel hex file.F 	CRC    - computes the Cyclic Redundancy Check value for a file, usingC 	         the same algorithm that is used by the CP/M program CRCK.o 	d  F         Brief instructions for any of these  utilities  except  LMODEM> can be obtained by typing ":utility_name" (for example, :CRC).  F      The ITS utilities listed above are also available  for  use  withF TOPS-20,  but  since ITS binary format is no longer being used for theF SIMTEL20 archives, these utilities have been converted  to  work  withF TOPS-20  binary  formats.   A  collection  of  TOPS-20  utilities  forF transferring  and  manipulating  files  can  be  found  in   directoryF PD:<CPM.TOPS-20>.   See  PD:<CPM>CPM.CRCLST  for  a  list of available	 programs.D  F      File  transfer  and  conversion  utilities  for  use with VAX/VMSF machines are contained in directory PD:<CPM.VAXVMS>.   See  CPM.CRCLST for details.    , Christensen Protocol Microcomputer Programs:  F      An  excellent  program  for transferring files between micros, orF between micros and mainframes is called MODM7xx,  where  the  "xx"  isF replaced  with  two  digits  to give the current version number.  ThisF program, often referred to as  MODEM7  (the  name  of  its  easier  toF pronounce ancestor), uses the popular Christensen protocol to transferF files with automatic error detection and retransmission  of  erroneous blocks.i  F      To get started with MODM7xx, you should first FTP and examine theF "DOC"    and    "MSG"    files    from   the   binary   library   fileF PD:<CPM.MODEM7>MODM7xx.LBR.  The "DOC" and "MSG"  files  are  actuallyF stored  in  the  library in squeezed form, so you will have to perform three steps to get them:  (         1.  FTP the binary library file.  B         2.  Extract the elements  having  filename  extensions  ofB             "DQC"  and "MQG".  If you have no facilities for doingB             this on your mainframe host (see the earlier  commentsB             on  mainframe-based  library utilities), then you willB             have to transfer the library to  a  microcomputer  andB             extract   the   necessary  elements  there.   If  thisB             requirement seems to put you in a "Catch-22" situationB             because  you  have  no  facilities  for  mainfrome-to-B             microcomputer transfers, there is a way out; read  the5             "Getting Started" section which follows|.e  B         3.  Use an "unsqueezer" (described above) to  convert  theB             "DQC"  and "MQG" files extracted from the library intoB             "DOC" and "MSG" files.  As in the case of the  libraryB             extractions,  unsqueezing  can  be  done  on  either aB             mainfrome host or a microcomputer, depending  on  your             circumstances.  F         Together, these files will tell you just about all there is toF know  about  getting MODM7xx to run on your machine.  Take the time toF read them; they're quite informative.  You will also get some  helpfulF insights  from  reading  some  of  the overlay files.  These overlays,F described in file PD:<CPM.MODEM7> M7OVL-yy.LST, are used to  customizeF MODM7xx  for  particular  machines without having to edit and assembleF the huge MODM7xx source file.  Complete  instructions  for  performingF this  procedure  are contained in each overlay file.  The letters "yy"F in the above filename should be replaced with two  digits  giving  the5 current version number as determined from CPM.CRCLST.   F      And then, there is MEX.  MEX stands for "modem executive", and itF is  just  what  the  name  implies, a communications and file-transferF program with a built-in mini operating system that  runs  under  CP/M.F This  program  can  do  file transfers using either the Christensen orF Compuserve protocol, and it  has  an  enormous  potential  for  highlyF automated  operations  because it can read and execute command-scriptsF pre-stored in disk files.  These scripts can include sending  commandsF to  a  remote  computer,  as  if  they had been sent manually from theF microcomputer in terminal-mode.  Users of this relatively new  programF are  still exploring its possibilities.  For more information, look inF CPM.CRCLST under the heading "PD:<CPM.MEX>", and then get the  variousF files  that  have "DQC" and "IQF" in their names.  These DOCumentationF and INFormation files are stored in squeezed form (note the "Q" in theF filename  extensions),  so  you will have to unsqueeze them.  OverlaysF for MODM7xx will also work with MEX, but they will not provide all  of the extended MEX features.     Kermit:l  F      Another  excellent  program  for  transferring  files  is  calledF KERMIT.  This program has the advantage  of  being  available  for  anF impressively  large  number  of  mainframes  and  micros.   It is, for@ example, available for the IBM-PC, and it DOES NOT require CP/M.  F      To  get started with KERMIT, connect to CU20B.ARPA using FTP, and do this:  "                 get ker:aaaread.me  F Note that this file is NOT on SIMTEL20, and the  name  is  subject  toF change.  If you cannot find a file with this name, snoop around in theF first half- dozen or so files in the alphabetical  listing  obtainableC using the FTP DIRectory command.  You should find something useful.a  E      Questions can be addressed to INFO-KERMIT-REQUEST at CU20B.ARPA.p     Getting Started:  F      In order to get MODM7xx, MEX or KERMIT running on your micro, youF must  first  transfer the necessary files from mainframe to micro.  IfF you already have a  receive-to-disk  communications  program  of  someF sort,  you can use it to move the needed files.  In the long-run it isF essential to be able to transfer 8-bit binary files, but initially  itF is  not absolutely necessary.  Some of the files are quite large.  ForF example, MODM7xx.COM is over 18K bytes, and the HEX  file  (which  youF will  need  if  you  can't  transfer 8-bit files) is over 45K.  MovingF large files to your micro without using an  error  detecting  protocolF can  result  in  frustrating  errors,  but it can be done by receivingF multiple copies and using manual or  machine-assisted  comparisons  toF locate  and  repair bad parts of the code.  However, there IS a better way.  F      Directory  PD:<CPM.STARTER-KIT>  contains a short starter-programF called PIPMODEM.ASM that can be FTPed to your mainframe, printed,  andF then  entered into your microcomputer by hand and assembled.  This canF then be used to down- load either MBOOT3.ASM or BMODEM.BAS  (dependingF on  whether  you prefer assembly language or BASIC), both of which canF receive files using the error detecting  Christensen  protocol.   OnceF you  have  this  capability,  you  can download the full-function fileF transfer program of your choice.  To examine this option,  connect  to SIMTEL20 via FTP and do this:a   	 ' 		get pd:<cpm.starter-kit>pipmodem.asm a' 		get pd:<cpm.starter-kit>pipmodem.doc  % 		get pd:<cpm.starter-kit>mboot3.asm d$ 		get pd:<cpm.starter-kit>bmodem.bas$ 		get pd:<cpm.starter-kit>bmodem.doc 	i        F         All are ASCII files.  Read PIPMODEM.DOC first,  then  look  atF MBOOT3.ASM  and  BMODEM.DOC.  PIPMODEM.DOC explains the situation veryF nicely.  Questions concerning these programs should be sent  to  INFO-) CPM@AMSAA.ARPA (NOT to INFO-CPM-REQUEST).i      ! NEWSGROUP CORRESPONDENCE ARCHIVES-  F      Copies  of  correspondence  for  several  newsgroups  are kept onF SIMTEL20 in directories with names of the form  PS:<ARCHIVES.KEYWORD>,F where  "KEYWORD" has been chosen to indicate the associated newsgroup.@ At present, the following correspondence archives are available:   	e( 		   newsgroup		   mail archive filename+ 		---------------		   ---------------------e" 		ADA-SW			   PS:<ARCHIVES.ADA-SW>+ 		AMETHYST-USERS		   PS:<ARCHIVES.AMETHYST>O  		INFO-68K		   PS:<ARCHIVES.68K>$ 		INFO-APPLE		   PS:<ARCHIVES.APPLE>  		INFO-CPM		   PS:<ARCHIVES.CPM>$ 		INFO-FORTH		   PS:<ARCHIVES.FORTH>" 		INFO-HAMS		   PS:<ARCHIVES.HAMS>$ 		INFO-MICRO		   PS:<ARCHIVES.MICRO>& 		INFO-MODEM7		   PS:<ARCHIVES.MODEM7>( 		INFO-MODEMXX		   PS:<ARCHIVES.MODEMXX>* 		INFO-MODULA-2		   PS:<ARCHIVES.MODULA-2>- 		NORTHSTAR-USERS		   PS:<ARCHIVES.NORTHSTAR>e& 		INFO-PASCAL		   PS:<ARCHIVES.PASCAL>$ 		UNIX-SW			   PS:<ARCHIVES.UNIX-SW>* 		INFO-XENIX310		   PS:<ARCHIVES.XENIX310> 	h  F         Descriptions of these and other newsgroups can be obtained viaF FTP  with  anonymous  login  (as  for  SIMTEL20)  from   the   NetworkF Information   Center's   host   SRI-NIC.ARPA.    Ask   for   the  fileF PS:<NETINFO>INTEREST-GROUPS.TXT (an ASCII  file).   And  please  note, this is NOT on SIMTEL20.  F      File names for SIMTEL20 newsgroup  correspondence  archives  haveF two  forms.  For example, PS:<ARCHIVES.CPM>CPM.ARCHIV.ymmdd is a groupF of files containing INFO-CPM correspondence going back several  years.F The  characters  "ymmdd"  in the file names are actually digits givingF the year, month and day of the last message in each  particular  file.F Current  correspondence  is  kept  in  the  file PS:<ARCHIVES.CPM>CPM-F ARCHIV.TXT, which is constantly changing.  Although INFO-CPM has  beenF used  as an example here, the same naming scheme is used for the otherF newsgroup files as well.  For a  complete  list  of  available  files,( connect to SIMTEL20 via FTP and do this:  !                 dir ps:<archives>   - You will receive a list of names of the form:   #                 KEYWORD.DIRECTORY.nf  F where  "n"  is  one or more digits.  For example, the INFO-CPM listingF currently appears as "CPM.DIRECTORY.1" To then get a list of files  in a particular archive, do this:  )                 dir ps:<archives.keyword>c  F where  "keyword"  (for  example,  "cpm")  is chosen from the precedingF list, and the word "directory" and the number "n" are  not  used.   At0 present, all of these files are stored in ASCII.      ' ADDITIONS, IMPROVEMENTS AND CORRECTIONS   F      Suggestions  for  additions, improvements and corrections to thisF message  are  always  welcome.   Please   send   them   to   INFO-CPM- REQUEST@AMSAA.ARPA.8  F      Contributions of public domain software are  actively  solicited.F If  you  have  something  that  seems appropriate for inclusion in theF <CPM>  archive,  please  contact  Keith   Petersen   <W8SDZ@SIMTEL20>.F Likewise,  contact  Richard Conn <ADA-SW-REQUEST@SIMTEL20> if you wishF to contribute to the <ADA> archive, and Sue  Tabron  <TABRON@SIMTEL20>- if you have something for the <UNIX> archive.t          Happy computing!o     	    					Dave Towson  					INFO-CPM-REQUEST@AMSAA.ARPA     ----> MLIST.DOC <----   F         An electronic mailing list exists for those who are interestedF in  accessing  and  contributing  software  to  the  Ada Repository onF SIMTEL20.  To subscribe to this  mailing  list,  send  a  request  via electronic mail to:a 	  		ADA-SW-REQUEST@SIMTEL20n 	hF         After you have been logged into the repository's mailing list,F you  will  receive  a  welcome  message  which  provides  introductory, information on how to access the repository.  F         The  mailing  list  serves  two  purposes:   to  help exchangeF information between  the  repository  users  and  to  mail  repositoryF submissions  to  the  maintainer  of  the  Ada Software Repository for inclusion in the archives.  F         PS:<ARCHIVES.ADA-SW>ADA-SW-ARCHIV.TXT   contains   all  recentF messages passed over the ADA-SW mailing list.  New users on  the  listF are  invited  to  get  a copy of this file and scan it for background;F older users may use it for reference.   In  either  case,  a  WARNING:F this is a BIG file!  PS:<ARCHIVES.ADA-SW>ADA-SW.ARCHIVE.ymmdd contains older messages by year/month.o  F         A  hardcopy newsletter and other hardcopy documentation on theF Ada Software Repository are published by Echelon, Inc.  and  available5 for reasonable charges.  Contact Echelon for details:e 	a 		Echelon, Inc.  		885 North San Antonio Road 		Los Altos, CA  94022 		415/948-3820 	t                       Richard Conn     ----> FINDME.DOC <----  4 HOW TO FIND THINGS IN THE ADA REPOSITORY ON SIMTEL20  F         The  contents  of the Ada Repository are organized in a numberF of different ways to make finding software  and  documentation  easierF for  the  user  of  the  repository.   The  following  summarizes  the information sources.     WELCOME MESSAGEu  F         The Welcome Message is a rather large text file which is  sentF to  all  new  subscribers to the ADA-SW electronic mailing list.  ThisF message contains a large amount of introductory material  on  the  AdaF Software  Repository,  the  operation  and  use  of  the  Ada SoftwareF Repository, and the Defense Data  Network.   The  Welcome  Message  is& stored in PD:<ADA.GENERAL>WELCOME.DOC.     SIMPLE DIRECTORY DISPLAYSi  F         FTP  can  provide  most  users with a directory display of allF files in any of the archives in the Ada Repository.  See the following files for more information:O   	, 		PD:<ADA.GENERAL>ADAREPOS.DOC) 			-- general info on repository contents  		PD:<ADA.GENERAL>AAREAD.MEs 			-- archive structures 		PD:<ADA.GENERAL>FTP.DOC + 			-- introduction to FTP and file transfere 		PD:<ADA.GENERAL>UUCP-BIT.DOC# 			-- accessing via UUCP and BITNETp 	a     ONLINE DOCUMENTATION SYSTEMb  F         The directory PD:<ADA.ONLINE-DOC> contains the source code (inF Ada), instructions, and data base for the online documentation system.F You  can  copy  all of these files over to your host computer, compileF the programs, and then run them to query the data  base,  which  givesF you  data  on  each directory in the repository.  This data includes aF brief description of the directory, a listing  of  its  contents  withF file  sizes, and descriptions of each program and piece of software inF the directory.  The data base may be copied from SIMTEL20 from time to1 time as more software is added to the repository.n     NEWSLETTERSe  F         Newsletters  are published monthly and placed in the directoryF PD:<ADA.NEWS>.  They are also available in hardcopy form for a nominalF annual subscription fee.  See the file PD:<ADA.GENERAL>NEWSLTR.DOC for details.     MASTER INDEX  F         A Master Index of all software  and  information  in  the  AdaF Software  Repository  is  published  by  Echelon, Inc.  This 300+ pageF loose-leaf book is updated periodically as the repository grows.   See/ the file PD:<ADA.GENERAL>INDEX.DOC for details.g     PROLOGUE FILES  F         Each piece of software has an associated PROLOGUE file of typeF PRO (eg, SAFEIO.PRO) which contains the Ada Repostory standard header.? See the file PD:<ADA.GENERAL>PROLOGUE.DOC for more information.o     GENERALo  F         The  files  in PD:<ADA.GENERAL> contain information on what isF in the Ada Repository, how to access and use the Ada  Repository,  and) other items of interest to the community.l       ----> DIRLIST.DOC <----i  F         The following presents a summary of the directories in the Ada Repository on SIMTEL20.E      Ada   PD:<ADA>  F         This  is  the  top-level  directory.    The   names   of   theF subdirectories  (*.DIRECTORY)  can  be  seen here.  The listing of allF files in all subdirectories (ADA.CRCLST) is also stored  here.   Also,F the  file  FILEUSE.DOC,  which  contains a listing of all files in theF repository, ordered by frequency of  use  (popularity),  is  contained here.o      Ada-SQL   PD:<ADA.ADA-SQL>  F         This   subdirectory   contains   files   associated  with  theF development of a standard Ada DBMS interface (Ada/SQL)  based  on  theF dpANS  Data  Base  Language  SQL.   It is anticipated that SQL will beF adopted as the Air Force standard Relational data base query language.   .  O  AI(   PD:<ADA.AI>f  F         This  subdirectory contains programs relating to the fields ofF artificial intelligence, such as expert systems, pattern  recognition, and heuristic analysis.      .a	  ANSI-LRM    PD:<ADA.ANSI-LRM>S  F         This subdirectory contains a machine-readable copy of the ANSIF Version of the Ada Language Reference Manual (LRM).   The  files  wereF obtained   from   the  directory  <ADA-LSN>  on  ECLB,  and  the  fileF FTPFILES.SUB shows the FTP process used to copy the files over and the renaming that was done.t  F         Chapters 1-14 and Appendices A-F are  included  as  CHAPxx.DOCF (like,  CHAP01.DOC  or  CHAPA.DOC).   Error files are also included asF CHAPxx.ERR.    The   Foreword    (FOREWORD.DOC,    ERR),    PostscriptF (POSTSCRPT.DOC,  ERR),  and  Table of Contents (TOC.DOC) are included. INDEX.DOC contains the index.      .e  Benchmarks2   PD:<ADA.BENCHMARKS>r  F         This subdirectory contains various  Ada  compiler  benchmarks.F An  attempt  has been made to see that entries in this subdirectory doF not  duplicate  entries  in  the  <BENCHMARK>   directory   on   ECLB.F Benchmarks submitted in conjunction with the NOSC tools are located in( the Ada Repository BENCHMARKS directory.     .D  CAIS   F         This  directory  contains  software associated with the Common APSE Interface Set (CAIS).  ,         The CAIS is defined in MIL-STD-CAIS.   .     CAIS_Toolsr   PD:<ADA.CAIS-TOOLS>o  F         This subdirectory contains tools which are compatable with andF modified or implemented  to  run  under  the  CAIS  presented  in  theF directory   PD:<ADA.CAIS>.    These   tools   have  been  modified  or@ implemented by Mitre Corporation and internally funded by Mitre.   .  r  Compilation_Order   PD:<ADA.COMPILATION-ORDER>  F         This subdirectory  contains  software  which  deals  with  theF analysis of groups of Ada programs to determine the proper compilationF order.  Other  information  pertaining  to  the  interrelationship  of6 software segments of a system may be obtained as well.     .R  Componentsa   PD:<ADA.COMPONENTS>c  F          This  is  the  components subdirectory.  Software components,F including general-purpose  procedures,  packages,  and  generics,  areF stored  here.  Examples are:  math packages, TERMCAP routines, generic2 linked list packages, and dynamic string packages.     .f  Cross_Reference   PD:<ADA.CROSS-REFERENCE>  F         This  subdirectory  contains  tools  which   generate   cross-" reference listing of Ada programs.     .t  Data Base Managementt  
 PD:<ADA.DBMS>e  F         This directory contains Ada software components  and  programs3 directly related to Data Base Management functions.h   .  t  DDN   PD:<ADA.DDN>  F         This subdirectory contains tools and components related to theF Defense Data Network, its  file  transfer,  mail,  and  communicationsF facilities.   Implementations  of  the TCP/IP communications protocol,C the FTP file transfer tool, and the SMTP mail handler are included.a     .o
  Debuggers   PD:<ADA.DEBUGGER>D  : 	This subdirectory contains Ada source-level debuggers.  A Symbolic Debugger is included.   .e  Editors   PD:<ADA.EDITORS>  F         This directory contains the source code and  documentation  on! some text editors written in Ada.h     .e
  Education   PD:<ADA.EDUCATION>  F         This   is   the   education  subdirectory.   Sample  programs,2 tutorials, and online courseware are located here.     .o  External_Toolsl   PD:<ADA.EXTERNAL-TOOLS>s  F         This subdirectory contains several miscellaneous  tools  whichF are  helpful  in  developing  Ada  code  but are not written in Ada orF pertain to  specific  environments.   For  example,  an  Ada  language= development interface for the EMACS editor can be found here.e     .n  Forms_Generator   PD:<ADA.FORMGEN>  F         This  subdirectory  contains tools for the generation of formsF for use by Ada programs.  The forms generator will display and  acceptF input  into  a  form  (in  a  screen-oriented  fashion via the virtualF terminal) in such a way that this mechanism is transparent to the  AdaF program  using  it.  Instead, the program simply reads fields from the form via procedure interfaces.     .e  General   PD:<ADA.GENERAL>  F         This  is  the  General   Information   subdirectory.    Notes,< comments, usage information, and other data are stored here.     .r  Graphical_Kernel_System   PD:<ADA.GKS>  F         This   subdirectory   contains   routines  associated  with  a Graphical Kernel System.     .   Management_ToolsU   PD:<ADA.MANAGEMENT-TOOLS>p  F         This subdirectory contains tools for use in  managing  an  AdaF software development project.  Status tracking and Manpower estimation tools are included.v     . 
  Math_Librarye  
 PD:<ADA.MATH>D  F         This subdirectory contains packages  of  math  routines.   AllF routines are written in Ada.  Routines for trig functions, exponentialF functions, matrix  manipulation,  bit  manipulation,  and  others  are contained here.x     .M  Menuu  
 PD:<ADA.MENU>l  F         This  subdirectory contains software used in the generation ofF menus.  Applications programs may use these menu generators as  front- ends.s     .   Message_Handlingm   PD:<ADA.MESSAGE-HANDLING>i  F         This  subdirectory  contains tools for use in message handling  facilities and message transfer.     .c  Metrics   PD:<ADA.METRICS>  F         This subdirectory  contains  tools  used  to  perform  metricsF analysis  of  Ada  software.   Tools  for  path  analysis, performance1 analysis, and other metrics reports are included.i     .f  Miscellaneous_Tools   PD:<ADA.TOOLS>  F         This is the  miscellaneous  tools  subdirectory.   Sources  toF various  tools  which  do  not  fit  into  the categories of the other subdirectories are placed here.t     .   Newsletters  
 PD:<ADA.NEWS>   = 	This subdirectory contains the Ada Software Repository (ASR)hD Newsletters.  They are numbered sequentially, starting at 001.  File names are ASRnnn.DOC.a   .   Online_Documentationt   PD:<ADA.ONLINE-DOC>v  F         This  directory  contains  supporting  files  for  the  online+ documentation system of the Ada Repository.      .  u  Pager   PD:<ADA.PAGER>  F         This subdirectory contains tools which create and  manipulatedF paged  files.  All SRC files are paged files, which are files composed5 of several smaller files separated by a special flag.      .   PDL   PD:<ADA.PDL>  F         This  subdirectory  contains  software  associated  with   AdaF Program  Design  Languages  and  tools  to  support  the  Ada  programF designer.  Such tools include tools for data  dictionary  manipulationF and design analysis.  There may be some overlap between this directoryF and software which may fall into the PDL category  that  is  scattered among the other subdirectories.e   .  y	  Pointersm   PD:<ADA.POINTERS>e  F         This is  the  pointers  subdirectory.   Information  on  otherF sources  of  software and information (such as the USC-ECLB resources)F is presented here.  This data  pertains  to  both  on-  and  off-  net
 resources.     .   Pretty_Printers   PD:<ADA.PRETTY-PRINTERS>  F         This  subdirectory  contains  pretty  printers  for Ada sourceF programs.  The pretty printers reformat the  Ada  source  programs  inF order  to  outline  the  structure  of  the programs and provide other& useful information for the programmer.     .<  Program_Stubber   PD:<ADA.STUBBER>  F         This  subdirectory  contains  Ada  program body stubber tools.F They analyze the definition of an Ada  software  design  and  generateB software bodies as stubs to be filled in later during development.     .r  Simulation    PD:<ADA.SIMULATION>@  > 	This subdirectory contains programs and tools associated with4 performing simulations, such as queuing simulations.   .e  Spelling_Checkers   PD:<ADA.SPELLER>  F         This subdirectory contains spelling checkers written  in  Ada.$ Dictionaries are also included here.     .e  Starter_Kit   PD:<ADA.STARTER-KIT>  F         This subdirectory contains tools which are useful in accessingF the software in the repository.  It includes the PAGER tool, which  is4 used to assemble and disassembled SRC (paged) files.     .M  Style_Checkers6   PD:<ADA.STYLE>  F         This  subdirectory  contains  Ada  style checking tools.  TheyF analyze  Ada  source  code  and  report  on  various  aspects  of  theF programming  style,  such  as  consistent  indentation and use of long variable names.N     .M  Virtual_Terminal.   PD:<ADA.VIRTERM>  F         This  subdirectory  contains  tools  for  a  virtual  terminalF package,  which performs screen-oriented functions by reading terminalF characteristics from a UNIX-like TERMCAP data base.   The  applicationF program  can call routines in these packages and not be concerned with% the type of terminal being addressed.)     .   WIS_ADA_Tools   PD:<ADA.WIS-ADA-TOOLS>  F         This directory contains information about the  software  toolsF submitted  by  the Naval Oceans Systems Center (NOSC).  An abstract of the tools is included.  ? 	These tools were paid for by WIS (WWMCCS Information Systems).a     .S     ----> TAPEDIST.DOC <----  3 Subject:  Ada Software Repository available on tapec  F         Tape copies of the files in PD:<ADA*> may  be  made  on  9TRK,F 1600  BPI  tapes  in TOPS-20 DUMPER, TOPS-10 INTERCHANGE, and Unix TarF formats.  Send a tape, a stamped, self-addressed mailing label, and  aF short,  informal  cover  letter  stating that you would like a copy ofF this collection and specifying the format.  Personnel at  White  SandsF will  make  the  tape  at  their  convenience and mail it back to you.$ There is no charge for this service.  F         Please  use  the  following  address to send your tape.  WhiteF Sands cannot accept cash, checks, money  orders  or  purchase  orders.) Send sufficient return postage in stamps.  	i 		Commanderp 		USA White Sands Missile Rangel) 		STEWS-IM-CM-S (Bldg. 362, Frank Wancho)a2 		White Sands Missile Range, New Mexico 88002-5072 	 F         DDN  electronic  mail  address  is  WANCHO@SIMTEL20.   Frank's! telephone number is 505/678-6257.e     ----> UUCPBIT.DOC <----i  F         "How  can  a  user  of  a USENET host access the public domainF microcomputer software collection on the  DDN/MILNET  host  SIMTEL20?"F is  being  asked with increasing frequency as that software collectionF continues to grow.  Unfortunately, direct access is  not  possible  asF there  is  no UUCP gateway for file transfer between SIMTEL20 (running= TOPS-20) and a USENET host (as there is for electronic mail).m  F         DDN,  formerly  known as ARPANET, is the Defense Data Network.F DDN, along with Arpanet, SATNET, SRINET, etc.  are all  members  of  aA TCP/IP protocol-based, multiple gateway network called InterNet.)e  F         USENET has been built on adjacent hosts  voluntarily  agreeingF to store- and-forward relatively short messages across the USENET overF dialup lines at 300 or 1200 bps.  In the past, helpful InterNet  usersF would  fetch  the  file(s)  requested  and  then  e-mail  them  to theF requestor.  However, it has been pointed out that large file transfersF disrupt   the  service,  delay  the  shorter  messages,  and  generateF unacceptably large phone bills, all of which add up  to  threaten  theF tenuous  connections that some USENET hosts can barely afford to have.F Therefore, we have been asked to encourage InterNet users not to  pass archive programs this way.  F         Now for the  good  news.   Some  InterNet  users,  if  sent  aF suitable  disk,  will download files and return mail the floppy to theF requestor.  To find a friendly InterNet user, send a message to  INFO-F CPM  at  DDN  host  AMSAA.ARPA via net.micro.cpm identifying your diskF format and your request.  Usually, someone will respond  and  come  toF your  aid.   If not, don't be bashful, wait a week and try again.  ButF please remember, any such arrangements are strictly  between  you  andF your  respondent.   This  is  not, repeat NOT, a service of either the InterNet or INFO-CPM.l  F         If  the  above  arrangement  is inconvenient, or doesn't work,: here are several other sources for public domain software.    F ----------------------------------------------------------------------  F         Information (and prices) are subject to change without notice.$ A volume is usually one floppy disk.   1.  Echelon, Inc.   F         The  Ada  Software Repository newsletters and Master Index are/ available from Echelon, Inc., for nominal fees:e 	  		Echelon, Inc.i 		885 N. San Antonio Roadb 		Los Altos, CA  94022 		415/948-3820 	a=         Echelon also supports the Z System (ZCPR3 and ZRDOS).t     2.  CP/M User's Groupa  .         The CP/MUG volumes are available from:   	    CP/M User's Group    1651 3rd Avenue    New York, NY 10028 	     1 3.  Special Interest Group/Microcomputers (SIG/M)c  -         The SIG/M volumes are distributed by:o   	f   SIG/Mt,   Amateur Computer Group of New Jersey, Inc.   Box 97   Iselin, NJ 08830 	     " 4.  New York Amateur Computer Club  C         PC-BLUE software volumes for the IBM-PC are available from:E   	>   S-100, CP/M User Group$   The New York Amateur Computer Club   P.O.  Box 106u   Church Street Stationp   New York, NY  10008y 	      5.  PicoNet CP/M Users Group  F         PicoNet,  CP/MUG,  and  SIG/M  software  volumes are available from:    	C	   PicoNete   P.O. Box 391566o   Mountain View, CA 94039E 	>     6.  Other sources:  F         Compuserve Information Service is  another  source  of  publicF domain software.  There are a number of special interest groups (SIGs)F devoted to specific hardware as well as CP-MIG, the generic CP/M  SIG,F a   repository   for  a  large  quantity  of  public  domain  softwareF downloadable by the  Compuserve  file  transer  protocol  (ChristensenF protocol  is  expected  by late summer, 1984).  There is no charge forF access to CP-MIG other than the  standard  CIS  connect  charges,  andF Compuserve can be accessed through their own communications network or through Tymnet.   F         Many  Remote  CP/M  (RCPM)  systems  around the country, whereD software is available for downloading for the price of a phone call.    F         I  would  like  to thank Dave Towson, Frank Wancho and CharlieF Strom for all their assistance in putting  this  blurb  together.   IfF anybody  out  in InterNet Land has any questions or comments about the0 above blurb, feel free to contact any one of us. 	.  ! Jeff Edelheit (edelheit at mitre)R< Revised 7/14/86 by Richard Conn (ADA-SW-REQUEST at SIMTEL20)   	l --> NEWSLTR.DOC <--r 	iF         The  Ada  Software  Repository  (ASR)  newsletter is publishedF monthly by Echelon, Inc.  Users of the ASR may freely transfer  copiesF of  the  newsletter from PD:<ADA.NEWS> via FTP (the newsletters are inF the files matching ASR*.DOC).  A hardcopy mailing of the newsletter isF also  available  by contacting Echelon (for current prices and placing orders): 	e 		Echelon, Inc.P 		885 N. San Antonio Road  		Los Altos, CA  94022 		415/948-3820 	      --> INDEX.DOC <--A  F         The Master Index of the Ada Software  Repository  (ASR)  is  aF loose-leaf book which contains details on the software and informationF in the ASR.  Each item  of  software  is  described  by  an  abstract,F information   on   the   host  compiler/operating  system  and  targetF environment, and a listing of all associated files and their locationsF in  the ASR.  Each item of information is described by an abstract and" a listing of all associated files.  F         The  Master Index breaks down the ASR into the following major0 categories, each presented as separate chapters: 	n) 		o ASR-Specific Information and Programsu 		o Artificial Intelligencen 		o Benchmarks 		o Communications  		o Reusable Software Components 		o Data Base Management 		o Documentationt 		o Graphics 		o Project Management" 		o Ada Software Development Tools 		o Other Toolss 		o the WIS Ada Tool Set 	iF         Selected items of information from the ASR are included in theF Master Index.  These items include the Welcome Message, which gives anF extensive  introduction  to the Ada Software Repository (its operationF and use) and the Defense Data Network (with emphasis on the use of FTP1 to transfer files from the archives on SIMTEL20).S  F         Appendices include (1) a Snapshot of the ASR  (ADA.SNP)  whichF names  each  directory  of  the  ASR  and  gives the total size of itsF contents in terms of bytes and lines of code, (2)  a  listing  of  allF files  in  each  directory  of  the  ASR  with file sizes and CRC dataF (ADA.CRCLST), and (3) a listing of all files in each directory of  the= ASR with file sizes, line counts, and PAGER hashes (ADA.RPT).)  F         The Master Index includes a complete table of contents,  whichF is  helpful  in  quickly  locating  specific items of interest, and anF extensive index.  The first publication of the Master  Index  exceeded 300 pages in size.  F         As the ASR grows, updates to the Master Index will be  issued.F The loose-leaf format of the Master Index was selected to facilite theF update process and to permit the users to assemble  the  Master  Index= and the ASR Newsletters conveniently in loose-leaf notebooks.t  F         The Master Index is available only through Echelon, Inc.   TheF ASR  Newsletters  may  be  obtained  from  the  ASR  in  the directoryF PD:<ADA.NEWS> or by hardcopy subscription through  Echelon,  Inc.   To= contact Echelon (for current pricing information and orders):o 	  		Echelon, Inc.i 		885 N. San Antonio Roadh 		Los Altos, CA  94022 		415/948-3820 	m ------- 