World of Ham Radio 1994 January/AMSOFT_1994.iso/packet/docs/pd198703.doc

Text File | 1993-12-31 | 37.9 KB | 890 lines

5-Mar-87 15:26:47-EST,1581;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 5 Mar 87 15:26-EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA04644; Thu, 5 Mar 87 13:23:49 EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA04637; Thu, 5 Mar 87 13:23:36 EST
Received: from unido.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA22059; Thu, 5 Mar 87 13:21:56 EST
Message-Id: <[e-mail]>
Received: by unido.uucp with uucp;
      Thu, 5 Mar 87 18:12:32 +0100
To: [e-mail]
Date: Thu, 5 Mar 87 18:06:57 MET
From: "Rupert Mohr" <unido!rmi![e-mail]>
Subject: mailing list
Reply-To: "Rupert Mohr" <rmi![e-mail]>
Organization: RMI Nachrichtentechnik GmbH, Software Laboratories
Work-Phone: [phone]
Direct-Mail: Datex-P: (262) 45 2410 90528 CUD: ZCZC to: ZENTRALE
Telex: [phone] rmi              Teletex: 2627-241 4024=rmi
Installation: PCS Cadmus 9230
X-Mailer: ELM [version 1.2a]

Hello,

   I tried to get rec.ham.packet here in Germany via uucp for
quite a while now. Also it is announced, it does not get spooled
by seismo. Therefore please let me ask you to place me on this
mailing list(for redistribution to the community here).

73,
   Rupert (DL3NO)

*****************************************************************
* addresses:  uucp   [e-mail]       GeoNet rmi:rmi-aachen *
*             bix    rmiaachen            Btx    024121144-0001 *
*             cis    72446,415            Ham:   DL3NO/DK0AF    *
*****************************************************************


13-Mar-87 17:02:30-EST,2650;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Mar 87 17:02-EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA02366; Fri, 13 Mar 87 10:42:35 EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA02313; Fri, 13 Mar 87 10:37:46 EST
Message-Id: <[e-mail]>
Date: Fri, 13 Mar 87  9:58:40 EST
From: Bob Clements <[e-mail]>
Subject: Fred's slam at NET/ROM
To: [e-mail]
Cc: [e-mail]

Replying to:

>>    From: [e-mail] (Fred R. Goldstein dtn226-7388)
>>    Subject: OSI addressing instead of IP for packet nets
>>    Message-ID: <[e-mail]>
>>    Date: 13 Mar 87 03:16:21 GMT
>>    Sender: [e-mail]
>>
>>
>>            Having seen the "NET/ROM" announcement and all of the talk
>>    about TCP/IP, here are my comments on why neither is right, but
>>    a modified TCP/IP may be ideal.
>>
>>            I suppose that Software 2000 wants to be the next Monopolist.  I
>>    don't really hold much hope for them, but I'd sure like to do my best to
>>    stop them anyway!

Geez, Fred!  There was absolutely no call for the above nasty
attack.  It annoyed me so much I still haven't managed to read
the rest of your article.

"Software 2000" is really WA8DED, Ron Raikes, and one or two
other guys, who are trying to make the network work better.  Ron
is the guy who wrote the only WORKING code for the TNC-1, and who
freely donated it to the packet community.

They have taken the necessary time off from their paying jobs to
write NET/ROM, to make the network work better.  The network
really needed it, especially in high density areas like
California.  They intend to ask a very small price for the ROMs,
to recoup some of their lost income.

NET/ROM works well. According to W0RLI, it has more than doubled the
useful throughput on the North-South California digipeater chain.
Even Phil Karn, who was initially distressed to hear that it was
not implemented with an already-blessed protocol, has decided that
he can live with it, since it will pass IP frames for him.

I agree with Phil's concern, by the way.  But I'm sure glad to
see someone DOING something useful.  Have you got your AX25L2V2
code from TAPR yet?  Me neither.

I think your "Monopolist" comment deserves a retraction and
apology.  And if you really mean it that "I'd sure like to do my
best to stop them anyway!" I hope you mean to do it by providing
a better solution, not by slinging mud.

>>               fred k1io

Bob Clements, K1BC, [e-mail], K1BC @ K1BC, [e-mail]

16-Mar-87 01:15:02-EST,5556;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 16 Mar 87 01:14-EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA28039; Sun, 15 Mar 87 21:54:15 EST
Received: by EDDIE.MIT.EDU (5.31/4.7) id AA27908; Sun, 15 Mar 87 21:49:37 EST
Date: Sun, 15 Mar 1987  19:46 MST
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail]
Subject: KA9Q TCP/IP files now available from SIMTEL20

Today I called Bdale Garbee's BBS and downloaded the latest KA9Q
TCP/IP and related files for MS/PCDOS.  They are now available on
SIMTEL20 as:

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
870227.ANN                      ASCII    24576  F9AAH
AUTHENT.TXT                     ASCII    14336  2F23H
BOTHTNC2.ARC                    BINARY    7168  66FCH
IPADDR.TXT                      ASCII    14336  20DEH
KA9Q_BIN.ARC                    BINARY   58880  EFC1H
KA9Q_BM.ARC                     BINARY    4224  2268H
KA9Q_DOC.ARC                    BINARY   40576  82DBH
KA9Q_EXE.ARC                    BINARY   95232  EA3BH
KA9Q_SRC.ARC                    BINARY  173056  CA5BH
KA9Q_TNC.ARC                    BINARY   94208  3492H

Here is a copy of Bdale's descriptions of these and other related
files available from his BBS.

 The files in this area represent the latest version of the full ARPA Internet
 IP/TCP protocol suite as written by KA9Q, with help from N3EUA and others.
 The purpose of this code is to allow use of the Internet protocols
 on Amateur packet radio.

 Note that all of the software in this distribution is protected under the
 copyright laws of the United States.  The sources are released by the
 authors for non-commercial duplication than use, but all rights are
 retained.

 All code compiled and tested under Aztec C 3.40a on an IBM PC "clone"

               Latest Revision: 870227

 *
 * This first archive is everything you need to run the package
 *

KA9Q_EXE.ARC   94981 02-27-87  Binary Distribution:  docs, configs, programs

 *
 * The next archive is the entire sourcecode distribution.  It contains
 * everything that is in KA9Q_EXE.ARC, as well as sources and some
 * additional documents.
 *

KA9Q_ALL.ARC  373172 02-27-87  Full Source Distribution

 *
 * and the next batch of archives are the pieces that are in the full
 * source distribution, for those who would rather download in smaller
 * pieces for whatever reason...
 *

KA9Q_BIN.ARC   58760 02-27-87  the EXE directory, binary and config files
KA9Q_BM.ARC     4125 01-02-80  the BM directory, Bdale's Mailer
KA9Q_DOC.ARC   40498 02-09-87  the DOC directory, documentation
KA9Q_SRC.ARC  172845 02-27-87  the SRC directory, sources to NET.EXE
KA9Q_TNC.ARC   94079 02-27-87  the TNC directory, KISS for the TNC2

 *
 * A special overlay for the TAPR TNC-2 EPROM that allows you to run both
 * TCP/IP and normal AX.25 packet operations from the same TNC and ROM.
 * Versions 1.1.2, 1.1.3, and 1.1.4 of the TAPR ROM are supported.  These
 * files are now included in the full and TNC archives as well...
 *

BOTHTNC2.ARC    6373 01-02-80  Intel HEX downloader overlay for TNC-2 EPROM

 *
 * Documents from the DOD ARPA publications list.  Some are specifications of
 * various protocols, some are documentation about networking experiments
 * performed, etc.  If you need a particular RFC that isn't here, leave a note
 * for the sysop, N3EUA... I have all of them on another system here...
 *

RFCINDEX.ARC   38783 08-21-86  Index to all available RFC's as of 860818

RFC791.ARC     36668 08-20-86  Internet Protocol (IP)
RFC792.ARC     10084 08-20-86  Internet Control Message Protocol (ICMP)
RFC793.ARC     70201 08-21-86  Transmission Control Protocol (TCP)
RFC821.ARC     43696 08-21-86  Simple Mail Transfer Protocol (SMTP)
RFC822.ARC     47769 08-21-86  Standard Format of ARPA-Internet Text Messages
RFC826.ARC     10257 12-15-86  Address Resolution Protocol (ARP)
RFC829.ARC      5605 12-31-86  Packet Satellite Technology Reference Sources
RFC854.ARC     17140 12-31-86  TELNET Protocol Specification
RFC862.ARC       722 12-31-86  Echo Protocol
RFC863.ARC       720 12-31-86  Discard Protocol
RFC959.ARC     59605 12-31-86  File Transfer Protocol (FTP)
RFC963.ARC     19634 12-31-86  Some Problems with the Spec. of the IP Protocol
RFC964.ARC      8799 12-31-86  Some Problems with the Spec. of the TCP Protocol
RFC968.ARC      1416 12-31-86  Twas the Night Before Startup (Xmas Humor)
RFC970.ARC     10926 12-31-86  On Packet Switches with Infinite Storage
RFC974.ARC      8703 12-31-86  Mail Routing and the Domain System
RFC977.ARC     26079 12-31-86  Network News Transfer Protocol (NNTP)
RFC981.ARC     25034 12-31-86  An Experimental Multiple-Path Routing Algorithm
RFC986.ARC      4678 12-31-86  Use of IP addresses in ISO Connectionless
RFC987.ARC     50014 12-31-86  Mapping between X.400 and RFC822 Mail
RFC988.ARC     18492 12-31-86  Host Extensions for IP Multicasting
RFC990.ARC     76849 12-31-86  Assigned Numbers (protocol port numbers)
RFC991.ARC     23817 12-31-86  Official Arpa Internet Protocols

 *
 * Other papers and documents
 *

IPADDR.TXT     13406 11-13-86  Paper by Wally WA6JPR on ip address assignment.
AUTHENT.TXT    13741 12-15-86  Paper by Phil KA9Q on authentification with IP

 *
 * Revision information
 *

870227.ANN     23967 02-27-87  What changed from 870216.0 to 870227.0

------------------------
73,
--Keith Petersen
Arpa: [e-mail]
Uucp: {bellcore,decwrl,harvard,lll-crg,ucbvax,uw-beaver}!simtel20.arpa!w8sdz
GEnie Mail: W8SDZ
21-Mar-87 14:23:03-EST,3183;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 21 Mar 87 14:23-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 21 Mar 87 13:10:18 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 21 Mar 87 13:09:56 EST
Date: Sat, 21 Mar 1987  11:07 MST
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail]
Subject: W0RLI C MailBox V 2.4 now available from SIMTEL20

The latest version of the W0RLI packet radio mailbox program for
MS/PCDOS now now available from SIMTEL20.  Internet readers may use
FTP with the standard ANONYMOUS username and password GUEST to get
these files.  Others may use our archive server to get the files via
netmail.

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
MB24.ARC.1                      BINARY  106310  54F6H
MB24READ.ME.1                   ASCII     1869  4DEBH
MBSRC24.ARC.1                   BINARY   74507  27D2H
IO24.ARC.1                      BINARY    7766  3221H
IOSRC24.ARC.1                   BINARY   50235  0663H

Here's Hank's readme file which explains what's new.

--------

       The W0RLI / VE3GYQ C BBS

  Release notes for C BBS Version 2.4 - 3/10/87

  *** YES ! ALL your messages and bug reports DO get here.
  If I answered more than just a few, I could write no code.
  (Todays harvest is 7 printed pages + 1 hour land line time).
  Without the reports debugging is near impossible.

  Please please include DOS version, DoubleDOS or DESQView version,
  device driver used. Many problems only show under specific versions.

  Version 2.3 had no new features, just bug fixes.
  Thank you all for the testing. The next release or two
  (until perhaps the end of March) will continue to be bug fix releases.

  *** Note: Check that any sub-directory you use in config.mb exists,
  the existance of any directory / device paths is NOT checked.

  There is work in progress on Macintosh (wa6bcw), ATARI (kb6irs).
  I would appreciate hearing of any working porting to other systems.

  To extract the REAL files from the archives:

  ARC E MB24      (The MailBox stuff)
  ARC E MBSRC24   (The MailBox source code)
  ARC E IO24      (The serial port device drivers)
  ARC E IOSRC24   (The serial driver source code)

  MBMODE can be used to set the port parameters, in the same
  manner that MODE would be. MBMODE supports COM1 thru COM7.

  The code has been run on:

    Several flavors of IBM and compatibles.
    Leading Edge "M".
    Victor VI, Victor V286 clone.
    Zenith Z-100 (port not yet finished).
    Xerox 820 (Not too useful).
    Victor 9000 (ah6cl, n6iya).
    OS-9 (Contact DH1IAZ for details).

  The code runs under DoubleDOS or DESQView.

  Please read the first few pages of NOTES.MB before you attempt to run
  the program, and read it in detail for information on setting up
  route tables, etc.

  There WILL be sysops documentation sometime "soon".


  ... Hank

---------

--Keith Petersen
Arpa: [e-mail]
Uucp: {bellcore,decwrl,harvard,lll-crg,ucbvax,uw-beaver}!simtel20.arpa!w8sdz
GEnie Mail: W8SDZ
21-Mar-87 14:57:04-EST,3183;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 21 Mar 87 14:57-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 21 Mar 87 13:10:18 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sat, 21 Mar 87 13:09:56 EST
Date: Sat, 21 Mar 1987  11:07 MST
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail]
Subject: W0RLI C MailBox V 2.4 now available from SIMTEL20

The latest version of the W0RLI packet radio mailbox program for
MS/PCDOS now now available from SIMTEL20.  Internet readers may use
FTP with the standard ANONYMOUS username and password GUEST to get
these files.  Others may use our archive server to get the files via
netmail.

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
MB24.ARC.1                      BINARY  106310  54F6H
MB24READ.ME.1                   ASCII     1869  4DEBH
MBSRC24.ARC.1                   BINARY   74507  27D2H
IO24.ARC.1                      BINARY    7766  3221H
IOSRC24.ARC.1                   BINARY   50235  0663H

Here's Hank's readme file which explains what's new.

--------

       The W0RLI / VE3GYQ C BBS

  Release notes for C BBS Version 2.4 - 3/10/87

  *** YES ! ALL your messages and bug reports DO get here.
  If I answered more than just a few, I could write no code.
  (Todays harvest is 7 printed pages + 1 hour land line time).
  Without the reports debugging is near impossible.

  Please please include DOS version, DoubleDOS or DESQView version,
  device driver used. Many problems only show under specific versions.

  Version 2.3 had no new features, just bug fixes.
  Thank you all for the testing. The next release or two
  (until perhaps the end of March) will continue to be bug fix releases.

  *** Note: Check that any sub-directory you use in config.mb exists,
  the existance of any directory / device paths is NOT checked.

  There is work in progress on Macintosh (wa6bcw), ATARI (kb6irs).
  I would appreciate hearing of any working porting to other systems.

  To extract the REAL files from the archives:

  ARC E MB24      (The MailBox stuff)
  ARC E MBSRC24   (The MailBox source code)
  ARC E IO24      (The serial port device drivers)
  ARC E IOSRC24   (The serial driver source code)

  MBMODE can be used to set the port parameters, in the same
  manner that MODE would be. MBMODE supports COM1 thru COM7.

  The code has been run on:

    Several flavors of IBM and compatibles.
    Leading Edge "M".
    Victor VI, Victor V286 clone.
    Zenith Z-100 (port not yet finished).
    Xerox 820 (Not too useful).
    Victor 9000 (ah6cl, n6iya).
    OS-9 (Contact DH1IAZ for details).

  The code runs under DoubleDOS or DESQView.

  Please read the first few pages of NOTES.MB before you attempt to run
  the program, and read it in detail for information on setting up
  route tables, etc.

  There WILL be sysops documentation sometime "soon".


  ... Hank

---------

--Keith Petersen
Arpa: [e-mail]
Uucp: {bellcore,decwrl,harvard,lll-crg,ucbvax,uw-beaver}!simtel20.arpa!w8sdz
GEnie Mail: W8SDZ
22-Mar-87 10:18:46-EST,5828;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Mar 87 10:18-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 22 Mar 87 09:08:51 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 22 Mar 87 09:08:33 EST
Date: Sun, 22 Mar 1987  07:06 MST
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail], [e-mail]
Subject: SIMTEL20 file server
In-Reply-To: Msg of 22 Mar 87 13:49:31 N (Sun) from Anders Klemets <enea!kuling!klemets at seismo.CSS.GOV>

> Pardon my ignorance Keith, but what is the username of your fileserver
> for netmail? If I would like to fetch a file using netmail I should
> state the filname in the subject line, shouldn't I?  I guess you get a
> lot of letters asking for the same thing all the time, but I hope you
> don't mind helping me...

I don't mind at all.  The files are here for everyone to access.
Internet users should use FTP rather than netmail.  FTP transfers the
files much faster and avoids placing additional load on the mailer.

The subject line is ignored by the fileserver.

The fileserver cannot answer requests which use a path that includes
seismo.  The most successful route is ucbvax because they have an
excellent program that properly formats the "From:" line of messages
coming through the gateway.

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:

[e-mail]

or via uucp:
   ...!ucbvax!simtel20.arpa!archive-request
   ...!uw-beaver!simtel20.arpa!archive-request
   ...!decwrl!simtel20.arpa!archive-request
   ...!lll-crg!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 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.

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
a message to the server with the request: SEND INFO

--Keith Petersen
Arpa: [e-mail]
Uucp: {bellcore,decwrl,harvard,lll-crg,ucbvax,uw-beaver}!simtel20.arpa!w8sdz
GEnie Mail: W8SDZ
22-Mar-87 11:02:45-EST,5828;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Mar 87 11:02-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 22 Mar 87 09:08:51 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Sun, 22 Mar 87 09:08:33 EST
Date: Sun, 22 Mar 1987  07:06 MST
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail], [e-mail]
Subject: SIMTEL20 file server
In-Reply-To: Msg of 22 Mar 87 13:49:31 N (Sun) from Anders Klemets <enea!kuling!klemets at seismo.CSS.GOV>

> Pardon my ignorance Keith, but what is the username of your fileserver
> for netmail? If I would like to fetch a file using netmail I should
> state the filname in the subject line, shouldn't I?  I guess you get a
> lot of letters asking for the same thing all the time, but I hope you
> don't mind helping me...

I don't mind at all.  The files are here for everyone to access.
Internet users should use FTP rather than netmail.  FTP transfers the
files much faster and avoids placing additional load on the mailer.

The subject line is ignored by the fileserver.

The fileserver cannot answer requests which use a path that includes
seismo.  The most successful route is ucbvax because they have an
excellent program that properly formats the "From:" line of messages
coming through the gateway.

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:

[e-mail]

or via uucp:
   ...!ucbvax!simtel20.arpa!archive-request
   ...!uw-beaver!simtel20.arpa!archive-request
   ...!decwrl!simtel20.arpa!archive-request
   ...!lll-crg!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 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.

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
a message to the server with the request: SEND INFO

--Keith Petersen
Arpa: [e-mail]
Uucp: {bellcore,decwrl,harvard,lll-crg,ucbvax,uw-beaver}!simtel20.arpa!w8sdz
GEnie Mail: W8SDZ
24-Mar-87 01:26:40-EST,899;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Mar 87 01:26-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 24 Mar 87 00:12:55 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Tue, 24 Mar 87 00:03:35 EST
Received: by bass.nosc.mil (5.31/4.7)
    id AA11291; Mon, 23 Mar 87 21:02:32 PST
Received: by crash.CTS.COM (5.54/UUCP-Project/rel-1.0/09-14-86)
    id AA00841; Mon, 23 Mar 87 20:56:46 PST
Message-Id: <[e-mail]>
Date: Mon, 23 Mar 87 20:47:24 PST
From: [e-mail] (Mike Kao)
To: crash!packet-radio@[e-mail]
Subject: KNAC?

I'm not sure if this is the right place to post this, but:

Does anyone here know how to "boost" the range of an FM antenna? I'm trying to
receive KNAC 105.5 (LA station) from here in SD. Please leave me mail if you
know.
25-Mar-87 16:07:43-EST,944;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 25 Mar 87 16:07-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 25 Mar 87 02:17:53 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Wed, 25 Mar 87 02:15:06 EST
Message-Id: <[e-mail]>
Date: 25 Mar 87 01:58 EST
From: Crawford@DCA-EMS
Subject: hf on packet
To: [e-mail]

is anyone out there using packet on hf with direct fsk keying?
any problems/successes with the 170 hz fsk keying shift
vs the standard 200 hz shift for packet?
i am tryin g to use an ic-751 with tnc-220 and direct fsk keying
with no success.  can receive sometimes, and something is going out,
but no connections.  i am ofsetting the xmit 100 hz since the
fsk generator in the 751 is 100 hz higher than the 2025 hz mark
freq of the tnc.
any suggestions?
jerry on8ua  k7upj

26-Mar-87 17:54:58-EST,1893;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 26 Mar 87 17:54-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 26 Mar 87 14:51:29 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 26 Mar 87 14:50:44 EST
Message-Id: <[e-mail]>
Received: by AMC-HQ via xmm1;  26 Mar 87 13:55 EST
Date:     26 Mar 87 7:42:32-EST (Thu)
From: [e-mail]
To: [e-mail],
    [e-mail]
Subject:  Request for Help

For some time I have been transmitting the USA-PKT.### file to all users
on the Info-Hams and Packet net. Last week I obtained an account with
CompuServe and will be uploading the same file there also. The reason
why I am letting you know is that I was hoping some of you out there
will let the Amateur Community know that the USA-PKT.### file will be
available starting this week-end on the CompuServe HamNet.  I need the
help of all to keep this list up to date. Currently this file is
available to all of the following, and contains over 1000 digipeater and
pbbs call signs in the United States.

       AMRAD Fido BBS - 703-734-1387
       ARPANET        - HamNet
       ARPANET        - PacketNet

This listing is of use to all PBBS System Operators.  It can be used
to create or update their forwarding files. It also provides a list
of PBBS that the Packet User can use to address mail to a friend in
an area where he/she doesnt know what PBBS's are available.

So do me a favor and pass on the list to all your friends. Also if
you have a LandLine BBS in the area that the hams use, please add it
to their download area.

Thank you for your time,

Don Bennett (K4NGC)
 Home 703-670-4773
 Work 703-274-9355
 AMRAD BBS 703-734-1387
 (dbennett@amc-hq)
26-Mar-87 23:49:52-EST,1560;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 26 Mar 87 23:49-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 26 Mar 87 21:36:04 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Thu, 26 Mar 87 21:35:44 EST
Message-Id: <[e-mail]>
Received: from ALASKA.BITNET by wiscvm.wisc.edu on 03/26/87 at 20:12:50 CST
Date:     Thu, 26 Mar 87 17:13 AST
From: <[e-mail]>
Subject:  CP/M ASM sources
To: [e-mail]
X-Original-To:  [e-mail], FXDDR

I dug an old generic CP/M box out of the closet...64K, two 5.25" drives,
basic CP/M utilities.  Since the market for used CP/M boxes is non-existant,
particularly for no-name boxes, I got to thinking about putting it to
work, so...
Does anybody know of a packet BBS written in your garden-variety 8080 ASM
that I might get a copy of?  Doesn't have to do much...a read-only board
would be fine.  I've seen a lot written about the Xerox 820 (never seen
one though)...maybe something written for it would serve.
We'd really have an impressive packet network if everyone dug out the
old 8-bit computers and put them to work as nodes.  All we need is
networking software that will fit in 48K or so.  Oh well, maybe in a
few more years when everybody dumps the PCs we can get a bunch of those
cheap and put them to work with TCP/IP.

Don Rice
University of Alaska, Fairbanks   BITNET%"FXDDR@ALASKA"
CIS 72337,3417  //  KL7JIQ
27-Mar-87 16:53:49-EST,2596;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Mar 87 16:53-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 27 Mar 87 14:26:47 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Fri, 27 Mar 87 14:26:20 EST
Message-Id: <[e-mail]>
Received: from ECNCDC(MISS014) by MITVMA (Mailer X1.23) id 4470;
      Fri, 27 Mar 87 14:17:00 EST
Date:     Fri 27 Mar 1987 12:26 CST
From: Thomas Churchill <[e-mail]>
Subject:  _Gateway_
To: <[e-mail]>

Does anyone out there in net.land know where I could obtain back issues
of the ARRL publication _Gateway_ ?  Prefereably in an electronic form
over the net.

In addition, I am currently writing a Packet-based Bulliten board system
to support an indefinate number of users from 1 TNC using 1 rs-232 port.
Has anyone else tried this?  I already have the main substance of the
board coded, and am now writing notefiler drivers, a database program,
and a number of other utilitys.  I expect the line count of the code to
exceed 3000 lines, quite possibly becoming even larger once more programs
become implemented on line.  (Nothing like the old days, where 4K was a
big deal, huh?).  I am writing this for a Macintosh+ w/1  Meg ram, for
anyone interested.  What I would like is:  Any information on other PBBS
who have tried similar experiments.  How does the responce time for each
packet relate to the number of users on the board?  -Has- anyone tried
this, and do they have statistics for a multi-port, multi-tnc PBBS -vs-
the responce time for a single-port, single-tnc, multi-user board?  It
would seem that the advantages of doing it this way would be so much
greater, that nobody would use the multi-port method.  (Responce time
should be improved somewhat just by eliminating collisions between
packets between the adjacent TNC's)  In addition, it's considerably less
expensive.  (Just as cheap as a single user station, since there is no
additional hardware).  The obvious drawback is the increased complexity
of the software but then, as they say in the computer feild "Don't sweat
it, it's just ones and zeros"  I'd be very interested as to what has been
done along these lines.
Thanks in advance for any help/information-

   ____  ____           -- Thomas Churchill
  /__   /      /  /    Educational Computing Network @ WIU/Illinois
 /     /      /  /     BITNET:   MISS014@ECNCDC
/___  /____  /  /      INTERNET: [e-mail]
30-Mar-87 05:28:29-EST,1314;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 30 Mar 87 05:28-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 30 Mar 87 04:34:18 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 30 Mar 87 04:34:08 EST
Received: from unido.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
    id AA05425; Mon, 30 Mar 87 04:33:21 EST
Message-Id: <[e-mail]>
Received: by unido.uucp with uucp;
      Mon, 30 Mar 87 11:26:10 +0100
To: [e-mail]
Date: Mon, 30 Mar 87 11:23:40 MET
From: "RMI Nachrichtentechnik GmbH" <unido!rmi![e-mail]>
Subject: w0rlo c mailbox
Cc: [e-mail] (RDKlothDL4TA)
Organization: RMI Nachrichtentechnik GmbH, Software Laboratories
Work-Phone: [phone]
Direct-Mail: Datex-P: (262) 45 2410 90832 CUD: ZCZC to: ZENTRALE
Telex: (041) 172414024 BOX              Teletex: 2627-241 4024=BOX
Installation: PCS Cadmus 9230
X-Mailer: ELM [version 1.2a]

#: 54652 S9/Packet Radio
    29-Mar-87  13:43:49
Sb: #54637-w0rli pbbs
Fm: David Toth VE3GYQ 72255,152

gave me the msg, that a new version of the w0rli pbbs
will be released this week.

Any comment on how getting software via the uucp
archive server ?

Rupert , dl3no

30-Mar-87 11:58:39-EST,1117;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 30 Mar 87 11:58-EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 30 Mar 87 10:29:53 EST
Received: by EDDIE.MIT.EDU with sendmail-5.31/4.7 id <[e-mail]>; Mon, 30 Mar 87 10:29:36 EST
Received: from truchas.lanl.gov.ARPA by LANL.ARPA (1.2/5.17)
    id AA18068; Mon, 30 Mar 87 08:28:22 mst
Received: by truchas.lanl.gov.ARPA (3.2/5.17)
    id AA02250; Mon, 30 Mar 87 08:27:12 MST
Date: Mon, 30 Mar 87 08:27:12 MST
From: [e-mail] (Dave Wade)
Message-Id: <[e-mail]>
To: [e-mail], [e-mail]
Subject: Re:  _Gateway_
Cc: [e-mail]

I would be interested in a copy of anything you come up with, if you don't
mind.  I have a Mac+ also, and have been trying to get software for Packet.
I haven't seen anything that I recognized as a viable packet station yet,
perhaps you have experimented with something that works?  I'd sure like to
know about it if you have something which works.  Thanks
Dave Wade