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

Text File | 1993-12-31 | 160.1 KB | 3,463 lines

1-Oct-87 18:42:53-EDT,1987;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 1 Oct 87 18:42-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 1 Oct 87 16:49:05 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 1 Oct 87 16:48:54 EDT
Received: from WILLET.SCRC.Symbolics.COM by YUKON.SCRC.Symbolics.COM via CHAOS with CHAOS-MAIL id 270025; Thu 1-Oct-87 16:16:00 EDT
Date: Thu, 1 Oct 87 16:15 EDT
From: Henry Minsky <[e-mail]>
Subject: Permitted data transmission rates on amateur radio
To: [e-mail], [e-mail]
Message-Id: <[e-mail]>


I just got a copy of the FCC REGULATIONS, PART 80 TO END. I thought
people would like to know the regs on data transmission rates in the
amateur bands:

Section 97.69  Digital communications

97.69(a)
...
(1) The sending speed shall not exceed the following:
(i) 300 baud on frequencies below 28 MHz;
(ii) 1200 baud on frequencies betwwen 28 and 50 MHz;
(iii) 19.6 kilobaud on frequencies between 50 and 220 MHz;
(iv) 56 kilobaud on frequencies above 220 MHz;

Also, note the following bandwidth limitations:

97.69(c)
(2) The bandwidth of an emission from a station using such digital codes
shall not exceed the following (where for this purpose the bandwidth is
defined as the width of the frequency band, outside of which the mean
power of any emission is attenuated by at least 26 decibels below the
mean power of the total emission; a 3 kHz sampling bandwidth being used
by the FCC in making this determination):

(i) 20 kHz on frequencies between 50 and 220 Mhz;
(ii) 100 Khz on frequencies between 220 and 902 MHz;
(iii) On frequencies above 902 MHz and bandwidth may be used provided
that the emission is in accordance with 97.63(b) and 97.73(c)

So, 19.6 Kilobaud is allowed on 2 meters, provided you can fit it into
20kHz!

Henry, N1EZP


 3-Oct-87 13:01:27-EDT,3538;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Oct 87 13:01-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:29:28 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:29:03 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA14962; Sat, 3 Oct 87 08:35:15 PDT
Return-Path: <bellcore!faline![e-mail]>
Message-Id: <[e-mail]>
Date: 3 Oct 87 05:52:03 GMT
From: bellcore!faline![e-mail] (Phil R. Karn)
To: [e-mail]
Subject: Re: Permitted data transmission rates on amateur radio
Summary: It's bandwidth OR signaling speed, not both
References: <[e-mail]>

I disagree with the view that 97.69 simultaneously limits you in both
bandwidth AND signaling speed.  Read paragraph (c) carefully. It begins with

    IN ADDITION to the above provisions, the use of ANY digital code is
    permitted on amateur frequencies above 50 Mhz...subject to the
    following requirements...[followed by the bandwidth restrictions]
    [emphasis mine]

You can therefore operate your digital station under EITHER the provisions
of paragraphs (a) and (b) OR paragraph (c); your choice. Paragraphs (a) and
(b) together say that you can run ASCII, AMTOR or Baudot anywhere FSK is
legal (including HF), subject to certain signaling rate limits.  OR, if
you're on 6m or higher and are communicating only within US territory, you
can instead choose to operate under paragraph (c): any digital code you
want, limited only by BANDWIDTH instead of signaling rate. Under either
provision you have to stay out of the CW-only bands and avoid encryption.

That the FCC meant an either-or interpretation should be obvious when you
consider that the paragraph (a) limit on signaling speed is only 56 kilobaud
above 220 Mhz, while under paragraph (c) there is no limit at all on
bandwidth above 902 Mhz.  Why would the Commission allow unlimited bandwidth
above 902 Mhz, more than the 100 Khz limit between 220 and 902 Mhz, if they
didn't intend to allow us to run our modems any faster above 902 Mhz than
below?

It is therefore perfectly legal to run 64 kbaud or more on 220, provided you
can do it in 100 Khz of bandwidth and you aren't having an international
QSO.

The use of baud instead of bits/sec in (a)(1) was intentional. The idea was
that the Commission should not discourage the use of bandwidth-efficient
modulation schemes that encode several bits/sec per baud.  In other words,
under paragraphs (a) and (b) you can run "ASCII" (whatever that is) at 64
kbps on 2 meters across the border to Canada if you can encode 4 or more
bits/symbol, thus keeping the signaling rate below 19600 baud.  (Note that
since you're not running under paragraph (c), you are NOT required to
squeeze the RF signal into 20 Khz -- though people would probably get rather
mad at you if you didn't).

[Of course, a much better way to link into Canada would be to
terminate the radio link 10 feet south of the border, run an optical
line-of-sight laser link across into Canada, and then put the signal back
onto an RF system operating under the Canadian digital rules. The US
portion could then operate at megabit rates under paragraph (c). :-)]

Clearly, section 97.69 is not well organized or concisely written; it
does, however, allow us an enormous amount of freedom to do what we want, so
nobody has yet complained.

Phil


 3-Oct-87 13:06:00-EDT,1433;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Oct 87 13:06-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:37:31 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:36:22 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA15051; Sat, 3 Oct 87 08:42:04 PDT
Return-Path: <bellcore!faline![e-mail]>
Message-Id: <[e-mail]>
Date: 2 Oct 87 08:13:04 GMT
From: bellcore!faline![e-mail] (Phil R. Karn)
To: [e-mail]
Subject: PACSAT funded!

Posted: Wed  Sep 30, 1987   9:31 PM GMT              Msg: IGIH-3165-6131
From:   VITA
To:     amsat
CC:     msweeting, hprice, vrip, ljohnson, jking, tclark, rdaniels
Subj:   DOE grants $350K to VITA for PACSAT!

The U.S. Department of Energy has made an award of $350,000
to VITA (Volunteers in Technical Assistance) for the purpose
of establishing an "international information exchange system
using a low earth orbiting satellite" (PACSAT).

The Margaret W. and Herbert Hoover, Jr. Foundation (Pasadena,
California) has also announced a challenge grant of $175,000
to VITA for the PACSAT project.

More details will be available at the 1st Annual USU Conference
on Small Satellites (Logan, Utah) October 7-9.

Gary Garriott
Manager - Information Technology
VITA


 3-Oct-87 15:05:25-EDT,1927;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Oct 87 15:05-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:34:16 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 11:34:03 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA14996; Sat, 3 Oct 87 08:40:34 PDT
Return-Path: <gatech!udel!princeton!idacrd![e-mail]>
Message-Id: <[e-mail]>
Date: 1 Oct 87 17:35:47 GMT
From: gatech!udel!princeton!idacrd![e-mail] (Bob McGwier)
To: [e-mail]
Subject: Re: AX.25 Level 3 specs wanted
References: <[e-mail]>

in article <[e-mail]>, [e-mail] (Markus Mueller) says:
> References:
>
> I just bought a used TNC that supports AX.25 Level 2 in version 2.0. However
> I have seen various references to level 3 (networking layer) software for
> TNC's that does true packet forwarding with an immediate acknowledge of
> packet reception beetween digipeaters. This allows you to send packets over
> as many digipeatres as you wish to with equal performance (it simply gets
> slower); however you have no direct indication of whether and when your
> packets have reached the destination.

Markus:

What you are seeing advertised over here are those units which have the
"KISS TNC" modules in them.  KISS stands for Keep It Simple Stupid.  It
has NO user tnc style interface and is strictly for translating
synchronous HDLC frames into asynchronous slip (serial line interface
protocol) frames for shipment to the HOST computer.  The protocol suite
this was originally developed for is TCP/IP/UDP (the ARPA protocol
suite) in the package by KA9Q.  He has the entire AX25/IP/TCP suite
running (very efficiently) in the IBM/PC and clones and is being ported
to other machines rapidly.

Bob



 3-Oct-87 16:12:15-EDT,1866;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Oct 87 16:12-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 15:02:41 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 15:01:31 EDT
Date:     Sat, 3 Oct 87 15:07:28 EDT
From: Brint Cooper <[e-mail]>
To: Henry Minsky <[e-mail]>,
    "Phil R. Karn" <bellcore!faline![e-mail]>
Cc: [e-mail], [e-mail]
Subject:  Re: Permitted data transmission rates on amateur radio
Message-Id:  <[e-mail]>


Henry Minsky writes:

> (1) The sending speed shall not exceed the following:
> (i) 300 baud on frequencies below 28 MHz;
> (ii) 1200 baud on frequencies betwwen 28 and 50 MHz;
> (iii) 19.6 kilobaud on frequencies between 50 and 220 MHz;
> (iv) 56 kilobaud on frequencies above 220 MHz;
>
Phil Karn responds:

> The use of baud instead of bits/sec in (a)(1) was intentional. The idea was
> that the Commission should not discourage the use of bandwidth-efficient
> modulation schemes that encode several bits/sec per baud.
>

    I wonder if this "idea" is recorded in Part 97 somewhere.  It
seems more than coincidental that the "baud rates" selected seem to
conicide exacely with commonly used data rates expressed in "bits per
second."  So, 1200 bits/second is implemented as 600 baud with 2 bits
per signalling element or 300 baud with 4 bits per symbol.  Phil's
interpretation would lead one to believe that 224,000 bit/second is
permitted above 220 MHz (56 kilobaud x 4 bits per symbol).

    My guess is that Section 97.69 is just plain wrong in this
regard.  It wouldn't be uncommon; writers and journalists who know
better continue to make the same error.

_Brint
 3-Oct-87 18:37:46-EDT,1866;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 3 Oct 87 18:37-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 15:02:41 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 3 Oct 87 15:01:31 EDT
Date:     Sat, 3 Oct 87 15:07:28 EDT
From: Brint Cooper <[e-mail]>
To: Henry Minsky <[e-mail]>,
    "Phil R. Karn" <bellcore!faline![e-mail]>
Cc: [e-mail], [e-mail]
Subject:  Re: Permitted data transmission rates on amateur radio
Message-Id:  <[e-mail]>


Henry Minsky writes:

> (1) The sending speed shall not exceed the following:
> (i) 300 baud on frequencies below 28 MHz;
> (ii) 1200 baud on frequencies betwwen 28 and 50 MHz;
> (iii) 19.6 kilobaud on frequencies between 50 and 220 MHz;
> (iv) 56 kilobaud on frequencies above 220 MHz;
>
Phil Karn responds:

> The use of baud instead of bits/sec in (a)(1) was intentional. The idea was
> that the Commission should not discourage the use of bandwidth-efficient
> modulation schemes that encode several bits/sec per baud.
>

    I wonder if this "idea" is recorded in Part 97 somewhere.  It
seems more than coincidental that the "baud rates" selected seem to
conicide exacely with commonly used data rates expressed in "bits per
second."  So, 1200 bits/second is implemented as 600 baud with 2 bits
per signalling element or 300 baud with 4 bits per symbol.  Phil's
interpretation would lead one to believe that 224,000 bit/second is
permitted above 220 MHz (56 kilobaud x 4 bits per symbol).

    My guess is that Section 97.69 is just plain wrong in this
regard.  It wouldn't be uncommon; writers and journalists who know
better continue to make the same error.

_Brint
 4-Oct-87 14:58:37-EDT,1640;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 4 Oct 87 14:58-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 4 Oct 87 13:32:14 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 4 Oct 87 13:32:02 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA12623; Sun, 4 Oct 87 10:40:10 PDT
Return-Path: <rutgers!sunybcs![e-mail]>
Message-Id: <[e-mail]>
Date: 4 Oct 87 15:47:04 GMT
From: rutgers!sunybcs![e-mail] (Devon E Bowen)
To: [e-mail]
Subject: Packet w/out TNC on a 64


I've heard rumors of a software package written in Europe for the C64 that
takes the place of the TNC during packet radio communications. From what I
hear, it's in the public domain and serves as the modem and terminal for
packet. All that's needed is an interface that costs about $18 in parts.
Does anyone know anything about this? Has anyone successfully done this?
I'll have access to the software and docs (in the near future), but I'd like
to have someone on the net that I could ask questions to if I run into any
problems. Any help or information is appreciated. Maybe I can afford packet
after all!!

                   Devon Bowen (KA2NRC)
                   University of Buffalo

*********************************************************
uucp:      ..!{ames,boulder,decvax,rutgers}!sunybcs!bowen
Internet:  [e-mail]
BITNET:    [e-mail]
*********************************************************


 4-Oct-87 15:36:43-EDT,1640;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 4 Oct 87 15:36-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 4 Oct 87 13:32:14 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 4 Oct 87 13:32:02 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA12623; Sun, 4 Oct 87 10:40:10 PDT
Return-Path: <rutgers!sunybcs![e-mail]>
Message-Id: <[e-mail]>
Date: 4 Oct 87 15:47:04 GMT
From: rutgers!sunybcs![e-mail] (Devon E Bowen)
To: [e-mail]
Subject: Packet w/out TNC on a 64


I've heard rumors of a software package written in Europe for the C64 that
takes the place of the TNC during packet radio communications. From what I
hear, it's in the public domain and serves as the modem and terminal for
packet. All that's needed is an interface that costs about $18 in parts.
Does anyone know anything about this? Has anyone successfully done this?
I'll have access to the software and docs (in the near future), but I'd like
to have someone on the net that I could ask questions to if I run into any
problems. Any help or information is appreciated. Maybe I can afford packet
after all!!

                   Devon Bowen (KA2NRC)
                   University of Buffalo

*********************************************************
uucp:      ..!{ames,boulder,decvax,rutgers}!sunybcs!bowen
Internet:  [e-mail]
BITNET:    [e-mail]
*********************************************************


 6-Oct-87 11:19:00-EDT,3525;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 6 Oct 87 11:18-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 6 Oct 87 09:54:27 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 6 Oct 87 09:53:57 EDT
Received: from computer-lab.cambridge.ac.uk by NSS.Cs.Ucl.AC.UK
       via Janet with NIFTP  id aa06692; 6 Oct 87 14:48 BST
Received: from cl.cam.ac.uk by Jenny.CL.Cam.AC.UK
       with SMTP with TCP/IP over Ethernet  id a015776; 6 Oct 87 14:42 BST
Date:     6 Oct 87 14:41:40 +0100 (Tuesday)
To: [e-mail]
From: Peter Robinson <[e-mail]>
Subject: Re: Packet w/out TNC on a 64
Message-Id: <[e-mail]>

I wonder if I could shed some light on Devon Bowen's enquiry about a
TNC-free system for packet radio?  Back in 1983 Alan Jones (G8WJL) and I
developed a packet radio system for the BBC computer (a moderately popular
home computer in the UK, made by Acorn in Cambridge).  This worked by
linking the cassette port of the computer directly to the
microphone/earphone socket of a transceiver, with the cassette motor
control operating the PTT.  The interface between the computer and the
radio was just a passive piece of wire.

The BBC computer records on cassette using a standard 6850 Asynchronous
Communications Interface Adapter to make up 8-bit bytes with parity which
are then modulated as 1200/2400 Hz tones using a separate semi-custom modem
chip.  As far as a packet radio program is concerned, bytes of data can be
written to the ACIA to cause tones to be emitted and when a suitable noise
is heard, bytes can be read.  We constructed a home-brewed datagram
protocol on top of this, programming entirely in Basic (Honestly!  Imagine
the contortions of handling the multi-tasking required...).  Anyway it all
worked, supporting several simultaneous channels with proper
acknowledgements, retransmissions after a timeout and all that good stuff.
There is a full description in the RSGB's Radio Communication of March 1985
if you are really interested.

Of course there are any number of criticisms that could be levelled against
the system:  we were lucky to get away as easily as we did with using
harmonically related tones;  the base bandwidth is only 300 bits/s (the
program did not go fast enough for 1200...) and that reduces to about 100
bits/s end to end after protocol overheads;  the protocol layers are not
apparent so there is essentially only one application available which chats
to other stations and it would be hard to relay packets;  and many more.
However it was cheap and it provided a reasonable introduction to the ideas
of packet radio - a sort of QRP approach.

In its heyday there were probably 1000 stations running the system (it is a
bit hard to count, because we encouraged free distributin of the program),
but interest has now moved into AX.25 (which, of course, is completely
incompatible with this system).  However, to answer the original question,
Mike Valentine (G4ANP) did manage to transfer the program to the Commodore
64, 128 and VIC computers, although a small external modem is required
because the Commodore machines do not have the built-in modem of the BBC
machines.  You could contact him for details, but the system will be of
little value in the current world of AX.25.

73, Peter Robinson (G3MRX).
 7-Oct-87 17:35:31-EDT,8641;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 7 Oct 87 17:35-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 14:22:09 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 14:12:38 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA18988; Wed, 7 Oct 87 11:15:15 PDT
Return-Path: <somewhere![e-mail]>
Message-Id: <[e-mail]>
Date: 6 Oct 87 18:48:58 GMT
From: [e-mail] (Paul A. Flaherty)
To: [e-mail]
Subject: AMNET Progress Paper
Reply-To: [e-mail] (Paul A. Flaherty)


        AMNET: An Amateur Packet Switched Network
            Paul Flaherty, N9FZX
            Project OSCAR


Abstract:
    The AMNET, a public service packet switched network, is detailed.  The
network utilizes a one megahertz wide linear transponder aboard the AMSTAR
Phase IV satellite, as well as several terrestrial gateway stations.  It
provides functionality similar to the ARPANET(1) in facilitating long distance
network traffic, using the DDN standard Internet Protocol (IP), and
Transmission Control Protocol (TCP).  The network fulfills the goals of the
Digital Community Access System (DCAS) in providing a number of standard
functions, including mail transfer (SMTP), bulletin transfer (NNTP), remote
file transfer (FTP), and remote login (TELNET) capabilities.

1. Motivation

    The motivation for a public service community access system can be
found in several papers proposing experiments with the AMSAT Phase III
satellites.  These early gateway experiments demonstrated both the feasibility
and desirability of long distance satellite links for voice repeaters.

    With the advent of the AMSAT Phase IV project, several proposals for
a simple, easy to access service were motivated by the following:

    1) To create a reliable long distance emergency communications system
        that was both easy to use, and inexpensive.

    2) To involve more amateurs in Amateur Space Program.

    3) To experiment with new and different concepts for network planning,
        management, and use.

    The voice Community Access System (vCAS) is currently being developed
by Jim Eagleson, WB6JNN, of Project Oscar.  The current design multiplexes
(using FDM) several voice channels onto a wideband linear transponder.
The voice channels use a modulation technique known as Amplitude Companded
SideBand, or ACSB, which provides FM quality voice in a fraction of the
bandwidth.

    Use of the vCAS system involves setting up a connection between a
memeber repeater and a regional gateway, then between two gateways, and
finally to the destination repeater.  In practice, this would require the
entry of a security access code, and then a three digit destination code.
One destination code (999) is reserved for a special "CQ" function, which
connects the user with a randomly chosen repeater.

    The signalling scheme for vCAS has yet to be well defined.  However,
the current proposal calls for an architecture similar to the AT&T
Co - Channel Interoffice Signalling (CCIS) system, with all trunk connection
functions performed out of the voice channel.

2. Digital CAS

    The Digital Community Access System (dCAS) has been motivated by
similar warrents.  In particular, the overwhelming growth of interest in
Packet Radio over the last few years indicates the popularity of digital
communications in the Amateur Community.  Also, there is a need for a
companion service to vCAS, to implement intergateway signalling.

    One of the first dCAS proposals came from the author (3).  It
involved the time division of a 128 kbps data stream, which was managed
by the satellite itself.  Channel allocation was obtained by requesting a
slot from the satellite on a separate multiaccess channel.

    This scheme had several downfalls, including:

    1)It required the development of a relatively high speed modem,
        which would be expensive.

    2)It required the use of a highly stable time base.

    3)Stations who were too remote from the terrestrial gateways could
        not use the system.

    4)It lacked the desired capacity.

    5)It used circuit switching, which is relatively ineffient when
        compared to packet switching.


    The current dCAS design is much simpler, more accessible, and less
expensive than the first.  It involves the use of a frequency division
multiplex scheme similar to the vCAS system, but using much wider (20 KHz)
channels.  Each trunk uses a four - ary QPSK scheme, and digital coding to
provide an end user data rate of 9600 bps, and requiring a 12 db signal to
noise (S/N) ration (3db margin) for a 1x10EXP(-6) bit error rate (BER).
Using this scheme, about fifty trunks can be provided in the transponder
space available.  The trunks would then be allocated between the terrestrial
gateways, using empirical data to predict relative traffic levels.

    This design is in essence a low speed copy of the architecture of the
ARPANET.  Because of the similarity, all of the research on increasing the
capacity of the ARPANET will be applicable to the AMNET; thus dCAS can build
on nearly twenty years of experience and exhaustive research.  In addition,
operation of the AMNET could provide valuable insight into future options for
the ARPANET.

    This architecture requires the use of the DDN standard protocol suite,
including TCP/IP and several other sevice protocols.  The use of TCP/IP does
mandate a certain level of sophistication, both on the part of the end user
and his equipment.  However, any network of this magnitude should require a
minimum level of hardware commensurate to its capabilities.  In particular,
many hobbyist computers lack the capability to deal with higher data rates
and multiprogramming capability.  A network designed for such computers would
be far less efficient, and would lack the desired capabilities.  Indeed, a
similar comparison would be the now famous battle between AM and SSB on the
HF bands during the infant years of Amateur Radio.

    For users who are not within distance of a gateway station, remote
access would be provided by allocating a few of the trunks as "open ended".
A remote user would access the network by choosing an unused, open trunk,
and then communicating with one of the gateways via the satellite transponder.

3. User Services

    The services provided by dCAS closely follow the services provided
by the DDN.  In particular:

    1) Electronic Mail.  The ability to send a message to a particular
        person has proven to enormously popular in the Amateur Packet
        Radio community.  This capability is provided by the Simple
        Message Transfer Protocol, or SMTP.

    2) Electronic News.  Another popular feature of the current packet
        radio setup is the passing of bulletins, articles, and
        for - sale messages. The Network News Transfer Protocol,
        NNTP, provides this service.

    3) File Transfer.  The ability to transfer software and data files
        is an important one, especially in a hobbyist community.
        FTP, the File Transfer Protocol, gives the user the ability
        to upload and download files from any machine in the network.

    4) Remote Login.  Another important service is to allow other people
        in the network to access a computing resource.  In particular,
        persons or groups who own timesharing systems, and are willing
        to allow public access to them, can present their systems for
        public use via the network.  TELNET, a protocol designed for
        use between a diversity of terminal and computing devices,
        provides this capability.


    Several other DDN protocols exist, providing secondary services,
public information, and other functions which may find use in the AMNET.


4. Summary

    The current implementation of dCAS, also known as the AMNET, will
provide a high level of functionality to users throughout the footprint
coverage of the AMSTAR Phase IV satellite.  The network builds upon the
experience of DARPA's DDN (also known as the ARPANET), and uses inexpensive
components to acheive high reliability at low cost.  It allows remote access
by stations far removed from metropolitan areas.  And, it will allow many
popular features of the current terrestrial packet radio network to be
extended nationwide.
--
-=Paul Flaherty, N9FZX           |Engineer(n) --
Computer Systems Lab -- Stanford |              A machine for converting beer
ARPA: [e-mail]  |              into blueprints.
UUCP: shasta!n9fzx!paulf@umunhum |


 7-Oct-87 17:41:49-EDT,8641;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 7 Oct 87 17:41-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 14:22:09 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 14:12:38 EDT
Received: by june.cs.washington.edu (5.52.1/6.6)
    id AA18988; Wed, 7 Oct 87 11:15:15 PDT
Return-Path: <somewhere![e-mail]>
Message-Id: <[e-mail]>
Date: 6 Oct 87 18:48:58 GMT
From: [e-mail] (Paul A. Flaherty)
To: [e-mail]
Subject: AMNET Progress Paper
Reply-To: [e-mail] (Paul A. Flaherty)


        AMNET: An Amateur Packet Switched Network
            Paul Flaherty, N9FZX
            Project OSCAR


Abstract:
    The AMNET, a public service packet switched network, is detailed.  The
network utilizes a one megahertz wide linear transponder aboard the AMSTAR
Phase IV satellite, as well as several terrestrial gateway stations.  It
provides functionality similar to the ARPANET(1) in facilitating long distance
network traffic, using the DDN standard Internet Protocol (IP), and
Transmission Control Protocol (TCP).  The network fulfills the goals of the
Digital Community Access System (DCAS) in providing a number of standard
functions, including mail transfer (SMTP), bulletin transfer (NNTP), remote
file transfer (FTP), and remote login (TELNET) capabilities.

1. Motivation

    The motivation for a public service community access system can be
found in several papers proposing experiments with the AMSAT Phase III
satellites.  These early gateway experiments demonstrated both the feasibility
and desirability of long distance satellite links for voice repeaters.

    With the advent of the AMSAT Phase IV project, several proposals for
a simple, easy to access service were motivated by the following:

    1) To create a reliable long distance emergency communications system
        that was both easy to use, and inexpensive.

    2) To involve more amateurs in Amateur Space Program.

    3) To experiment with new and different concepts for network planning,
        management, and use.

    The voice Community Access System (vCAS) is currently being developed
by Jim Eagleson, WB6JNN, of Project Oscar.  The current design multiplexes
(using FDM) several voice channels onto a wideband linear transponder.
The voice channels use a modulation technique known as Amplitude Companded
SideBand, or ACSB, which provides FM quality voice in a fraction of the
bandwidth.

    Use of the vCAS system involves setting up a connection between a
memeber repeater and a regional gateway, then between two gateways, and
finally to the destination repeater.  In practice, this would require the
entry of a security access code, and then a three digit destination code.
One destination code (999) is reserved for a special "CQ" function, which
connects the user with a randomly chosen repeater.

    The signalling scheme for vCAS has yet to be well defined.  However,
the current proposal calls for an architecture similar to the AT&T
Co - Channel Interoffice Signalling (CCIS) system, with all trunk connection
functions performed out of the voice channel.

2. Digital CAS

    The Digital Community Access System (dCAS) has been motivated by
similar warrents.  In particular, the overwhelming growth of interest in
Packet Radio over the last few years indicates the popularity of digital
communications in the Amateur Community.  Also, there is a need for a
companion service to vCAS, to implement intergateway signalling.

    One of the first dCAS proposals came from the author (3).  It
involved the time division of a 128 kbps data stream, which was managed
by the satellite itself.  Channel allocation was obtained by requesting a
slot from the satellite on a separate multiaccess channel.

    This scheme had several downfalls, including:

    1)It required the development of a relatively high speed modem,
        which would be expensive.

    2)It required the use of a highly stable time base.

    3)Stations who were too remote from the terrestrial gateways could
        not use the system.

    4)It lacked the desired capacity.

    5)It used circuit switching, which is relatively ineffient when
        compared to packet switching.


    The current dCAS design is much simpler, more accessible, and less
expensive than the first.  It involves the use of a frequency division
multiplex scheme similar to the vCAS system, but using much wider (20 KHz)
channels.  Each trunk uses a four - ary QPSK scheme, and digital coding to
provide an end user data rate of 9600 bps, and requiring a 12 db signal to
noise (S/N) ration (3db margin) for a 1x10EXP(-6) bit error rate (BER).
Using this scheme, about fifty trunks can be provided in the transponder
space available.  The trunks would then be allocated between the terrestrial
gateways, using empirical data to predict relative traffic levels.

    This design is in essence a low speed copy of the architecture of the
ARPANET.  Because of the similarity, all of the research on increasing the
capacity of the ARPANET will be applicable to the AMNET; thus dCAS can build
on nearly twenty years of experience and exhaustive research.  In addition,
operation of the AMNET could provide valuable insight into future options for
the ARPANET.

    This architecture requires the use of the DDN standard protocol suite,
including TCP/IP and several other sevice protocols.  The use of TCP/IP does
mandate a certain level of sophistication, both on the part of the end user
and his equipment.  However, any network of this magnitude should require a
minimum level of hardware commensurate to its capabilities.  In particular,
many hobbyist computers lack the capability to deal with higher data rates
and multiprogramming capability.  A network designed for such computers would
be far less efficient, and would lack the desired capabilities.  Indeed, a
similar comparison would be the now famous battle between AM and SSB on the
HF bands during the infant years of Amateur Radio.

    For users who are not within distance of a gateway station, remote
access would be provided by allocating a few of the trunks as "open ended".
A remote user would access the network by choosing an unused, open trunk,
and then communicating with one of the gateways via the satellite transponder.

3. User Services

    The services provided by dCAS closely follow the services provided
by the DDN.  In particular:

    1) Electronic Mail.  The ability to send a message to a particular
        person has proven to enormously popular in the Amateur Packet
        Radio community.  This capability is provided by the Simple
        Message Transfer Protocol, or SMTP.

    2) Electronic News.  Another popular feature of the current packet
        radio setup is the passing of bulletins, articles, and
        for - sale messages. The Network News Transfer Protocol,
        NNTP, provides this service.

    3) File Transfer.  The ability to transfer software and data files
        is an important one, especially in a hobbyist community.
        FTP, the File Transfer Protocol, gives the user the ability
        to upload and download files from any machine in the network.

    4) Remote Login.  Another important service is to allow other people
        in the network to access a computing resource.  In particular,
        persons or groups who own timesharing systems, and are willing
        to allow public access to them, can present their systems for
        public use via the network.  TELNET, a protocol designed for
        use between a diversity of terminal and computing devices,
        provides this capability.


    Several other DDN protocols exist, providing secondary services,
public information, and other functions which may find use in the AMNET.


4. Summary

    The current implementation of dCAS, also known as the AMNET, will
provide a high level of functionality to users throughout the footprint
coverage of the AMSTAR Phase IV satellite.  The network builds upon the
experience of DARPA's DDN (also known as the ARPANET), and uses inexpensive
components to acheive high reliability at low cost.  It allows remote access
by stations far removed from metropolitan areas.  And, it will allow many
popular features of the current terrestrial packet radio network to be
extended nationwide.
--
-=Paul Flaherty, N9FZX           |Engineer(n) --
Computer Systems Lab -- Stanford |              A machine for converting beer
ARPA: [e-mail]  |              into blueprints.
UUCP: shasta!n9fzx!paulf@umunhum |


 7-Oct-87 21:35:03-EDT,846;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 7 Oct 87 21:35-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 19:13:42 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 19:13:04 EDT
Date: Wed, 7 Oct 87 23:55:16 +0100
Posted-Date: Wed, 7 Oct 87 23:55:16 +0100
Received: by tor.nta.no (5.54/3.21)
    id AA22970; Wed, 7 Oct 87 23:55:16 +0100
From: Karl Georg Schjetne <[e-mail]>
To: <[e-mail]>
Message-Id: <550:[e-mail]>
Subject: PSR and PRM.

What happened to PSR and Packet Radio Magazine???????

As a member of TAPR I used to get PSR and later PRM.
The last edition I have recieved is vol.2, no.4, april 1987.

LA8GE, Karl Georg Schjetne.
 8-Oct-87 01:00:01-EDT,1398;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Oct 87 01:00-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 20:48:36 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 20:48:23 EDT
Received: from ROOK.SCRC.Symbolics.COM by VALLECITO.SCRC.Symbolics.COM via CHAOS with CHAOS-MAIL id 166598; Wed 7-Oct-87 20:31:03 EDT
Date: Wed, 7 Oct 87 20:30 EDT
From: Henry Minsky <[e-mail]>
Subject: AMNET Progress Paper
To: [e-mail], [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <[e-mail]>


I am an amateur radio operator who is interested in packet radio
networks. I have not heard of the AMNET before. I have been
participating in the TCP/IP activity that is going on using the KA9Q
package.

It wasn't clear from your progress paper what state the project was in.
Has the satellite been launched? Are actual groundstation servers
running?

I would be interested in helping if possible, if I could get some more
complete information on the program!

I cc'd this to the packet-radio mailing list because I got the
impression that some others were also unaware of this project.

Thanks,
    Henry Minsky, N1EZP
    Amateur IP address: [44.56.0.13]


 8-Oct-87 01:28:51-EDT,1398;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Oct 87 01:28-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 20:48:36 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 7 Oct 87 20:48:23 EDT
Received: from ROOK.SCRC.Symbolics.COM by VALLECITO.SCRC.Symbolics.COM via CHAOS with CHAOS-MAIL id 166598; Wed 7-Oct-87 20:31:03 EDT
Date: Wed, 7 Oct 87 20:30 EDT
From: Henry Minsky <[e-mail]>
Subject: AMNET Progress Paper
To: [e-mail], [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <[e-mail]>


I am an amateur radio operator who is interested in packet radio
networks. I have not heard of the AMNET before. I have been
participating in the TCP/IP activity that is going on using the KA9Q
package.

It wasn't clear from your progress paper what state the project was in.
Has the satellite been launched? Are actual groundstation servers
running?

I would be interested in helping if possible, if I could get some more
complete information on the program!

I cc'd this to the packet-radio mailing list because I got the
impression that some others were also unaware of this project.

Thanks,
    Henry Minsky, N1EZP
    Amateur IP address: [44.56.0.13]


 8-Oct-87 06:21:56-EDT,1304;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Oct 87 06:21-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 05:04:54 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 05:04:33 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA28139; Thu, 8 Oct 87 02:07:41 PDT
Message-Id: <[e-mail]>
Received: from TSO by DESY IBM-3084Q BB with NEWLIB-Clist AMAIL
Date:      8 OCT 87  09:47:02 MEZ
Ut-Date:  871008.084702 UT
From: [e-mail]
To: [e-mail]
Subject:  Re: Packet w/out TNC on a 64

Hello!
Yes, there is a program here in DL called DIGICOM>64 which does full
AX.25L2 Version 1 and 2. It's really like a TNC build into a 64.
Command structure is like the TAPR TNC's with the usual differences...
It only uses an external modem with 2206/2211 or 7910 or TCM3105 or
whatever you like. Sorry I can't read C64 disks otherwise I would
send a hex-dump of the program. I will look for the address of course.
It's sort of public domain here. I wonder why it hasn't spread into
thew new world by now.
    Karl-Heinz,     DK8HI,     F33PAP @ DHHDESY3.BITNET

.. unusual disclaimer...

 8-Oct-87 06:36:47-EDT,1304;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Oct 87 06:36-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 05:04:54 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 05:04:33 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA28139; Thu, 8 Oct 87 02:07:41 PDT
Message-Id: <[e-mail]>
Received: from TSO by DESY IBM-3084Q BB with NEWLIB-Clist AMAIL
Date:      8 OCT 87  09:47:02 MEZ
Ut-Date:  871008.084702 UT
From: [e-mail]
To: [e-mail]
Subject:  Re: Packet w/out TNC on a 64

Hello!
Yes, there is a program here in DL called DIGICOM>64 which does full
AX.25L2 Version 1 and 2. It's really like a TNC build into a 64.
Command structure is like the TAPR TNC's with the usual differences...
It only uses an external modem with 2206/2211 or 7910 or TCM3105 or
whatever you like. Sorry I can't read C64 disks otherwise I would
send a hex-dump of the program. I will look for the address of course.
It's sort of public domain here. I wonder why it hasn't spread into
thew new world by now.
    Karl-Heinz,     DK8HI,     F33PAP @ DHHDESY3.BITNET

.. unusual disclaimer...

 8-Oct-87 19:57:06-EDT,1285;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 8 Oct 87 19:57-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 13:02:31 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 8 Oct 87 11:32:46 EDT
Message-Id: <[e-mail]>
Received: from (MAILER)MITVMA.BITNET by MITVMA.MIT.EDU on 10/08/87 at
  11:36:46 EDT
Received: from UWALOCKE.BITNET (BRUCE) by MITVMA.MIT.EDU (Mailer X1.25)
  with
 BSMTP id 7491; Thu, 08 Oct 87 11:36:42 EDT
Date:      Thu,  8-OCT-1987 08:34:44.24 PDT
From: <[e-mail]> (BRUCE EDWARDS)
Subject:   Re:PSR and PRM
To: <[e-mail]>

      I got an issue of PSR about a week and a half ago.  On the last
page of the issue they explain why PRM isn't being sent out anymore and
the delay in getting PSR going again.  I don't have the issue here at work
so I hesitate to mention any more.  I assume most people in the group
who are members of TAPR have already received the issue, but I can mention
more if you want (after checking the article again.)

BITNET -- BRUCE%UWALOCKE
ARPA   -- [e-mail]
      (or [e-mail]@WISCVM.WISC.EDU till DEC 1)
 9-Oct-87 01:45:38-EDT,2351;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 01:45-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:34:18 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:34:07 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA16658; Thu, 8 Oct 87 21:34:33 PDT
Return-Path: <pyramid!prls!philabs!trotter![e-mail]>
Message-Id: <[e-mail]>
Date: 7 Oct 87 12:14:17 GMT
From: pyramid!prls!philabs!trotter![e-mail] (Bill Gunshannon)
To: [e-mail]
Subject: Re: Morse requirement
References: <[e-mail]>

In article <[e-mail]>, [e-mail] (Marc de Groot) writes:
>
> I believe it is illegal to transmit using digital modes on CB, and my
> previous remark should not be construed as a recommendation to break the law,
> but I'm surprised that it has not been done on a large scale already.

I have heard reports that it is being done in various parts of the country but
although I have listened here with my trusty R-390 I have not heard anything.
And as far as legality goes, I wouldn't worry about it as under the current
administration of the Citizens Band legal operation is immposible.

You ask what do I base this statement on, it's really quite simple.

When the FCC stopped issueing licenses for CB it did not cancel the applicable
set of regulations therefore you are still required to identify using your FCC
assigned callsign but you don't have one cause they don't assign them.
If they don't care about that rule, and based on what I hear they also don't
care about profanity, and of course there is still the power limits(heard a
guy tuning his linear last nite) I hardly think they will care if you started
running packet on channel 39.

But then I could be wrong. (and I'm sure someone will tell me if I am :-)

#include <standard.disclaimer>

bill gunshannon


UUCP: {philabs}\                        US SNAIL: Martin Marietta Data Systems
      {phri   } >!trotter.usma.edu!bill           USMA, Bldg 600, Room 26
      {sunybcs}/                                  West Point, NY  10996
RADIO:         KB3YV                    PHONE: WORK    [phone]
AX.25:         KB3YV @ K3RLI            PHONE: HOME    [phone]


 9-Oct-87 03:35:58-EDT,2909;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 03:35-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:37:34 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:37:16 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA16695; Thu, 8 Oct 87 21:37:38 PDT
Return-Path: <rutgers!princeton!idacrd![e-mail]>
Message-Id: <[e-mail]>
Date: 8 Oct 87 17:13:37 GMT
From: rutgers!princeton!idacrd![e-mail] (Bob McGwier)
To: [e-mail]
Subject: Re: AMNET Progress Paper
References: <[e-mail]>

in article <[e-mail]>, [e-mail] (Henry Minsky) says:
>
>
> I am an amateur radio operator who is interested in packet radio
> networks. I have not heard of the AMNET before. I have been
> participating in the TCP/IP activity that is going on using the KA9Q
> package.
>
> It wasn't clear from your progress paper what state the project was in.
> Has the satellite been launched? Are actual groundstation servers
> running?
>
> Thanks,
>       Henry Minsky, N1EZP
>       Amateur IP address: [44.56.0.13]

Hot Dog Paul is a hard working fellow!  AMNET as far as the satellite is
concerned is a longer term project than might be implied by his paper.
We are getting ready for a board (bored ?) of directors meeting in
November of AMSAT-NA (North America) where we will decide on the funding
of further Phase IV work.  It is my feeling that this project will go
forward.  There are a number of funding sources that HAVE APPROACHED US
and any one of them could fund the construction of the satellite system
which will cost $2000000.  We are clearly the worlds leading experts on
small satellite systems and our expertise (read that Jan King W3GEY
and Karl Meinzer DJ4ZC) are in demand.  The Phase IV project as it is
now embodied plans on a 1991-92 launch.  The 56 Kb modems are real right
now.  Phil and I are a long way towards finishing the four we have.
I think Phil is 7 trimmer capacitors from done.  The modems were
designed by WA4DSY, Dale Heatherington, technical father of the Hayes
Modems.  They are RF modems and expect 29 MHZ IF.  This makes them easy
to use and move by adding transverters.  Paul is working on the
Community Access System project with his other Project Oscar/ AMSAT
cohorts (I think that is still headed up by Jim Eagleson).  We have made
rapid progress it "bit stuffing" thanks to Phil and we are attacking
Level 1 (radios) and level 0 (humans :-) ) as the primary remaining
hurdle to a REAL AMNET.

Paul I didn't see that paper on the AMSAT schedule.  PLEASE send it to
Larry Koziel even if you can't attend the meeting in Detroit and one of
us wll read it and get it into the proceedings.

Bob N4HY


 9-Oct-87 03:41:02-EDT,1027;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 03:41-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:32:35 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 00:32:25 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA16635; Thu, 8 Oct 87 21:32:50 PDT
From: sun!leftlane![e-mail]
Return-Path: <sun!leftlane![e-mail]>
Message-Id: <[e-mail]>
Date: 8 Oct 87 18:50:48 GMT
To: [e-mail]
Subject: Packet on 10 mtrs -- in the Bay Area -- Does it exist?
Keywords: 10 packet ba pk-232

Does anyone run 10 mtr packet (300 or 1200 baud) in the Bay Area?  I haven't
heard a thing?  Say about 28.140.00 @ 1200 baud.  The band has been very quiet
(dead) here, but maybe useful for higher speed local traffic.

Is 40 mtrs the only active area?

AMTOR or RTTY would be fun too.  Any takers?

Mark
KB8DCX


 9-Oct-87 10:37:26-EDT,1151;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 10:37-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 09:21:27 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 09:21:16 EDT
Received: from WPI.BITNET by WISCVM.WISC.EDU ; Fri, 09 Oct 87 08:20:55 CDT
From: [e-mail]
Received: by wpi (4.12/4.7)
    id AA29090; Fri, 9 Oct 87 09:18:35 edt
Date: Fri, 9 Oct 87 09:18:35 edt
Message-Id: <8710091318.AA29090@wpi>
To: [e-mail]
Subject: Packet freqs

Regarding the recent inquiry about 10M and other packet activity.
I haven't heard anything on 15 or 10 meters but the following
are packet freqs with activity:
     80M around 3609Khz
     40M 7093 and 7096 Khz
     20M 14.101 .103 .105 .107 .109 .111 (all quite active although
                     the higher freqs 07, 09 are
                     predominately BBS traffic)
Hope the info helps.  73 de
Bill AA2S    Bitnet  wrm@wpi
         Arpanet [e-mail]
 9-Oct-87 15:52:40-EDT,1282;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 15:52-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 13:30:00 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 13:29:11 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA06950; Fri, 9 Oct 87 10:28:34 PDT
Message-Id: <[e-mail]>
Date:      8 OCT 87  09:47:02 MEZ
From: [e-mail]
To: [e-mail]
Subject:  Re: Packet w/out TNC on a 64

Hello!
Yes, there is a program here in DL called DIGICOM>64 which does full
AX.25L2 Version 1 and 2. It's really like a TNC build into a 64.
Command structure is like the TAPR TNC's with the usual differences...
It only uses an external modem with 2206/2211 or 7910 or TCM3105 or
whatever you like. Sorry I can't read C64 disks otherwise I would
send a hex-dump of the program. I will look for the address of course.
It's sort of public domain here. I wonder why it hasn't spread into
thew new world by now.
    Karl-Heinz,     DK8HI,     F33PAP @ DHHDESY3.BITNET

.. unusual disclaimer...
This is the third time I send this, wonder why it didn't go before...

 9-Oct-87 17:21:51-EDT,1995;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 17:21-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 15:04:55 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 15:04:40 EDT
Received: from ROOK.SCRC.Symbolics.COM by VALLECITO.SCRC.Symbolics.COM via CHAOS with CHAOS-MAIL id 167176; Fri 9-Oct-87 15:05:20 EDT
Date: Fri, 9 Oct 87 15:05 EDT
From: Henry Minsky <[e-mail]>
Subject: Re: Morse requirement
To: [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <[e-mail]>

    Message-Id: <[e-mail]>
    Date: 7 Oct 87 12:14:17 GMT
    From: pyramid!prls!philabs!trotter![e-mail] (Bill Gunshannon)
    To: [e-mail]
    Subject: Re: Morse requirement
    References: <[e-mail]>

    In article <[e-mail]>, [e-mail] (Marc de Groot) writes:
    >
    > I believe it is illegal to transmit using digital modes on CB, and my
    > previous remark should not be construed as a recommendation to break the law,
    > but I'm surprised that it has not been done on a large scale already.

    I have heard reports that it is being done in various parts of the country but
    although I have listened here with my trusty R-390 I have not heard anything.
    And as far as legality goes, I wouldn't worry about it as under the current
    administration of the Citizens Band legal operation is immposible.
    ...
    ...


I keep seeing ads and articles in the Ham magazines which refer to novices
being able to now do 'digital' modes on 28 Mhz, with the novice
enhancement privileges.

That's not true is it? The way I read the regulations is that only CW
and SSB are allowed with novice/technician on 28 Mhz. Or am I just a
little confused?

Henry, N1EZP


 9-Oct-87 22:18:45-EDT,6151;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 9 Oct 87 22:18-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 20:40:27 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 9 Oct 87 20:39:42 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA18257; Fri, 9 Oct 87 17:39:08 PDT
Message-Id: <[e-mail]>
Return-Path: [e-mail]
Received: by DTUZDV1 (Mailer X1.23) id 0369; Fri, 09 Oct 87 22:02:48 CET
Date:         Fri, 9 Oct 87 22:00 CET
From: Ralf D Kloth <[e-mail]>
Subject:      Internet Addresses
To: Packet-Rdo <[e-mail]>


Following is a list of the Internet addresses of German TCP/IP-
users on packet radio ( ... mostly using the KA9Q package ...).
If there should be similar lists in other countries, please let
me know and post them, either to this list or to my address.

73, Ralf

Ralf D. Kloth (DL4TA)
Weinbergweg 17, D-7400 Tuebingen, B.R.Deutschland
Electronic Mail (EARN/BITNET): [e-mail]
Packet-Radio: QSO path ...!db0da!db0id!dl4ta
           (or ...!db0da!db0id!df0ut-7!df0ut-2!dl4ta)
Packet-Radio AMPR-Internet: 044.130.048.001


German AMPRNET Amateur Packet Radio TCP/IP Internet Addesses
-----------------------------------------------------------------------

44.130.xxx.xxx - F.R. Germany
-----------------------------
44.130.000.xxx * Hamburg area SubNet
44.130.000.001    DL2VO (Gateway) Gunter Hille, 2000 Hamburg 20
44.130.000.002    DL2VO-1       Gunter Hille, 2000 Hamburg 20
44.130.000.003    DK5XA         Hartmut Krueger, 2000 Hamburg 60
44.130.000.004    DB2HK         Klaus Kleemann
44.130.000.005    DL5HAI        Juergen Drews, 2000 Hamburg
44.130.000.006    DL3HCM        Marita Semmelhack, 2000 Hamburg 65
44.130.000.007    DF7HI         Thomas Illies, 2000 Hamburg 65
44.130.000.008    DK8HI         Karl-Heinz Pape, 2000 Schenefeld
44.130.000.009    DB0DJ.test    Digipeater/Node, 2000 Hamburg
44.130.000.010    DB0HB.test    PBBS, 2000 Hamburg 65
44.130.000.011    DB8HN         Heinz Schultz, 2000 Hamburg 20

44.130.020.xxx * Aachen-Dueren area
44.130.020.001    DG2KK         Walter Doerr, 5160 Dueren
44.130.020.012    DK0AF         AMDAT e.V., 5100 Aachen (SUN-Gateway)
44.130.020.013    DK0AF         AMDAT e.V., 5100 Aachen
44.130.020.014    DK0AF         AMDAT e.V., 5100 Aachen
44.130.020.015    DK0AF         AMDAT e.V., 5100 Aachen
44.130.020.016    DL3NO         Rupert Mohr, 5100 Aachen

44.130.021.xxx * Euskirchen area ...
44.130.021.001    DL4KW         Rolf Willerscheid, 5350 Euskirchen
44.130.021.002    DG4KS-1       Andreas Kempf, 5350 Euskirchen
44.130.021.003    DD0KX         Wolfgang Schmitz, 5350 Euskirchen
44.130.021.004    DC8TS         Reinhard Schulze, 5350 Euskirchen
44.130.021.005    DL4KW-1       Rolf Willerscheid

44.130.024.xxx * Rhein-Main SubNet
44.130.024.001    DF7FE         Peter Ott, 6239 Eppstein
44.130.024.002    DG4KS         Andreas Kempf, 6501 Dexheim
44.130.024.003    DC6VQ         Gerhard Sexauer, 6239 Niederjosbach
44.130.024.004    DG3FBL        Jochen Sonnabend, 6082 Moerfelden
44.130.024.005    DK1YZ         Fred Boersch, 6239 Kriftel
44.130.024.006    DJ9KM         Klaus Metternich, 6238 Diedenbergen
44.130.024.007    DK1VJ         Bernd Breuer, 6234 Okriftel
44.130.024.008    DB3PA         Bernd Schneider, 6230 Zeilsheim
44.130.024.009    DG1FO         Claus Hobeck, 6232 Neuenhain
44.130.024.010    DC0NE         Karl Doerrer, 6239 Vockenhausen
44.130.024.011    DB7ZD         Dieter Hummel, 6230 Sindlingen
44.130.024.012    DL4FAA        Gerd Bader, 6230 Zeilsheim

44.130.025.xxx * Frankfurt SubNet
44.130.025.001    DJ3FC         Walter Michel, 6000 Frankfurt Nordwest
44.130.025.002    DD9ZY         Peter Michel, 6000 Frankfurt Nordwest
44.130.025.003    DH1FAB        Klaus-Dieter Friedrich, 6000 Frankfurt NW
44.130.025.004    DL8LE         Juergen Sturhahn, 6374 Steinbach/TS
44.130.025.005    DB5ZF         Oliver Teske, 6000 Frankfurt Berkesheim

44.130.029.xxx * Karlsruhe area (formerly 44.193.000.xxx)
44.130.029.002    DG9BAD        Thomas Waehner, 7500 Karlsruhe 21
44.130.029.016    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.017    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.018    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.019    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.020    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.021    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.022    DL5UY         Reinhard Meyer, 7515 Linkenheim 1
44.130.029.023    DL5UY         Reinhard Meyer, 7515 Linkenheim 1

44.130.048.xxx * Stuttgart/Tuebingen SubNet
44.130.048.001    DL4TA         Ralf D. Kloth, 7400 Tuebingen
44.130.048.002    DJ7KA         Hans Ulrich Wandel, 7400 Tuebingen
44.130.048.003    DK5SG         Dieter Deyke, 7034 Gaertringen
44.130.048.004    DF1TL         Klaus Dittrich, 7050 Waiblingen
44.130.048.005    DK3SI         Harald Tietze, 7016 Gerlingen
44.130.048.006    DL5TT         Josef Thalheimer, 7000 Stuttgart
44.130.048.007    DK1RI         Guenter Klomann, 7000 Stuttgart
44.130.048.008    DB2ST         Jupp Vermeulen, 7134 Knittlingen
44.130.048.009    DL5UE         Jan Schiefer, 7000 Stuttgart
44.130.048.010    DB0ID (Digi)  Stuttgart Net-Ctl (DK9SJ), 7000 Stuttgart
44.130.048.011    DJ3EG         Henning Gamlich, 7000 Stuttgart
44.130.048.012    DK0HU         Club Stn Hewlett-Packard, 7030 Boeblingen

44.193.000.xxx * Karlsruhe Subnet    ... partly moved to 44.130.29.xxx
44.193.000.001    DB1UY         Reinhard Bruckner, 7500 Karlsruhe 41
44.193.000.003    DG1GAL        Marius Krumm, 7556 Oetigheim

44.194.000.xxx * Villingen-Schwenningen area ...
44.194.000.001    DG3SAJ        Hans J. Goetz, 7734 Brigachtal

-----------------------------------------------------------------------
<EOF>
Acknowledge-To: Ralf D Kloth <ZRKL001@DTUZDV1>
10-Oct-87 16:43:25-EDT,1645;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Oct 87 16:43-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 10 Oct 87 15:20:22 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 10 Oct 87 15:19:59 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA04937; Sat, 10 Oct 87 12:19:23 PDT
Message-Id: <[e-mail]>
Return-Path: [e-mail]
Received: by DTUZDV1 (Mailer X1.23) id 1139; Sat, 10 Oct 87 19:19:15 CET
Date:         Sat, 10 Oct 87 19:02 CET
From: Bernhard Dolderer <[e-mail]>
Subject:      Re: Packet w/out TNC on a 64
To: <[e-mail]>

The program DIGICOM>64, which emulates a TNC on a C64 home computer and
allows usage of disk and printer, was written by Stefan Eckart DL2MDL
and Florian Radlherr DL8MBT. Only a simple modem (without HDLC controller)
is required in addition to the C64, so many OM's in West-Germany got
started in packet using this program.
In 1986, the program was distributed by  Gorch Pollow, DF3MH
                     D-8201 Au bei Bad Aibling
The cost of disk and shipping was DM 20.- (about $ 11), the program
itself is public domain, written by hams for hams, copying and further
distribution free of charge are encouraged, commercial usage is prohibited.
There is even a version for the C16, but the screen goes dark when traffic
is on the air.....(perhaps some computers are too small).

73    Bernhard Dolderer  DL4SBW     ([e-mail])
10-Oct-87 19:03:14-EDT,1645;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 10 Oct 87 19:03-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 10 Oct 87 15:20:22 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 10 Oct 87 15:19:59 EDT
Received: by jade.berkeley.edu (5.54 (CFC 4.23)/1.16.17)
    id AA04937; Sat, 10 Oct 87 12:19:23 PDT
Message-Id: <[e-mail]>
Return-Path: [e-mail]
Received: by DTUZDV1 (Mailer X1.23) id 1139; Sat, 10 Oct 87 19:19:15 CET
Date:         Sat, 10 Oct 87 19:02 CET
From: Bernhard Dolderer <[e-mail]>
Subject:      Re: Packet w/out TNC on a 64
To: <[e-mail]>

The program DIGICOM>64, which emulates a TNC on a C64 home computer and
allows usage of disk and printer, was written by Stefan Eckart DL2MDL
and Florian Radlherr DL8MBT. Only a simple modem (without HDLC controller)
is required in addition to the C64, so many OM's in West-Germany got
started in packet using this program.
In 1986, the program was distributed by  Gorch Pollow, DF3MH
                     D-8201 Au bei Bad Aibling
The cost of disk and shipping was DM 20.- (about $ 11), the program
itself is public domain, written by hams for hams, copying and further
distribution free of charge are encouraged, commercial usage is prohibited.
There is even a version for the C16, but the screen goes dark when traffic
is on the air.....(perhaps some computers are too small).

73    Bernhard Dolderer  DL4SBW     ([e-mail])
12-Oct-87 19:49:58-EDT,1548;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 12 Oct 87 19:49-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:05:05 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:04:52 EDT
Message-Id: <[e-mail]>
Received: from (MAILER)MITVMA.BITNET by MITVMA.MIT.EDU on 10/12/87 at
  18:05:02 EDT
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
Received: from OPMVAX.KPO.FI (SYSTEM@FINFUN) by MITVMA.MIT.EDU (Mailer
  X1.25)
 with BSMTP id 8293; Mon, 12 Oct 87 18:04:59 EDT
Date: Tue, 13 Oct 87 00:00 O
From: PMDF Mail Server  <[e-mail]>
Subject: Undeliverable mail
To: [e-mail]

Your message could not be delivered to:

    JJANTTI

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows:

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Fri, 9 Oct 87 22:15 O
Received: From FINHUTC(MAILER) by FINFUN with RSCS id 5889 for JJANTTI@FINFUN;
 Fri,  9 Oct 87 22:15 O
Received: by FINHUTC (Mailer X1.25) id 5881; Fri, 09 Oct 87 22:13:14 EET
Date: 8 OCT 87  09:47:02 MEZ
From: [e-mail]
Subject: Re: Packet w/out TNC on a 64
Sender: Packet-radio list <[e-mail]>
To: JARI J{NTTI <[e-mail]>
Reply-to: [e-mail]

12-Oct-87 21:20:22-EDT,1606;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 12 Oct 87 21:20-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:05:34 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:05:08 EDT
Message-Id: <[e-mail]>
Received: from (MAILER)MITVMA.BITNET by MITVMA.MIT.EDU on 10/12/87 at
  18:05:17 EDT
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
Received: from OPMVAX.KPO.FI (SYSTEM@FINFUN) by MITVMA.MIT.EDU (Mailer
  X1.25)
 with BSMTP id 8295; Mon, 12 Oct 87 18:05:01 EDT
Date: Tue, 13 Oct 87 00:00 O
From: PMDF Mail Server  <[e-mail]>
Subject: Undeliverable mail
To: [e-mail]

Your message could not be delivered to:

    JJANTTI

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows:

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Fri, 9 Oct 87 23:41 O
Received: From FINHUTC(MAILER) by FINFUN with RSCS id 6508 for JJANTTI@FINFUN;
 Fri,  9 Oct 87 23:41 O
Received: by FINHUTC (Mailer X1.25) id 6505; Fri, 09 Oct 87 23:39:26 EET
Date: Fri, 9 Oct 87 15:05 EDT
From: Henry Minsky <[e-mail]>
Subject: Re: Morse requirement
Sender: Packet-radio list <[e-mail]>
To: JARI J{NTTI <[e-mail]>
Reply-to: [e-mail]
In-Reply-To:  <[e-mail]>
13-Oct-87 00:06:47-EDT,1460;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 13 Oct 87 00:06-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:41:57 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Mon, 12 Oct 87 18:41:29 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA01444; Mon, 12 Oct 87 15:42:07 PDT
From: sun!imagen!atari!portal!cup.portal.com![e-mail]
Return-Path: <sun!imagen!atari!portal!cup.portal.com![e-mail]>
Message-Id: <[e-mail]>
Date: 11 Oct 87 15:08:05 GMT
To: [e-mail]
Subject: TAPR's Packet Status Register
Xportal-User-Id: 1.1001.1860

I am the new editor of Packet Status Register, the quarterly publication
of Tucson Amateur Packet Radio (TAPR).  Due to the recent demise of Packet
Radio Magazine, the TAPR Board of Directors has decided to begin publishing
PSR again.  Our first issue was mailed to TAPR members about two weeks ago.
The October issue is now in final editing and will be mailed by the end
of October to all current TAPR members.

If you have any material which would be appropriate for publication in PSR,
please send it to me at the address shown on the header of this message.

If you'd be interested in subscribing to PSR, TAPR's dues are $15/year.
TAPR's address is:

Tucson Amateur Packet Radio
PO Box 22888
Tucson, AZ 85734


14-Oct-87 20:48:29-EDT,1946;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 14 Oct 87 20:48-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 14 Oct 87 17:35:54 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 14 Oct 87 17:35:28 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA21683; Wed, 14 Oct 87 14:36:12 PDT
Return-Path: <uunet!mcvax!cernvax![e-mail]>
Message-Id: <[e-mail]>
Date: 13 Oct 87 19:30:29 GMT
From: uunet!mcvax!cernvax![e-mail] (frode)
To: [e-mail]
Subject: IARU Stand at TELECOM 87
Keywords: TELECOM 87, AMSAT news, DX news

            IARU Stand at TELECOM 87.
            **************************

The radio amateurs will be represented at  TELECOM 87 the worlds
largest telecomunication exhibition which is going to take place
in Geneva, Switzerland from the 20th to 27th October.

The objective of the IARU stand is to explain amateur radio to the
visitors of TELECOM.  This is no easy task as the visitors will be a
varied lot, ranging from WARC delegates, telecommunication professionals
and governmental officials to the general public.  But we hope to
achieve our task using a selection of exhibits and information displays
showing the latest in amateur radio technologies and activities.

But to succeed in giving the visitors and fellow hams the latest
information about amateur radio we will need YOUR help.  Please let
us have access to the latest news bulletins, DX news, propagation
forcasts, AMSAT news and what have you.

You can send your contributions via the net or by email.

              Many thanks
                 and
              best 73 de


   Frode Weierud, LA2RL, HB9CHL
   CARC - CERN Amateur Radio Club
   CERN - European Organization for Nuclear Research
   CH-1211 Geneva 23, Switzerland.

   BITNET address : [e-mail]


15-Oct-87 14:24:10-EDT,834;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 15 Oct 87 14:24-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 11:48:38 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 11:47:41 EDT
Message-Id: <[e-mail]>
Date: 15 Oct 1987 11:46:07 EDT
From: [e-mail]
Subject: Removal from Distribution
To: [e-mail]
Cc: [e-mail], [e-mail]



Gentleman,

Please remove me immediately from the packet radio (amateur) distribution.
Your discussions are becoming too voluminous for me to follow.

I will attempt to set up another mail directory for myself for
the amateur discussions, since I am still very interested and involved.

Paul Sass
-------
15-Oct-87 18:04:34-EDT,834;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 15 Oct 87 18:04-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 11:48:38 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 11:47:41 EDT
Message-Id: <[e-mail]>
Date: 15 Oct 1987 11:46:07 EDT
From: [e-mail]
Subject: Removal from Distribution
To: [e-mail]
Cc: [e-mail], [e-mail]



Gentleman,

Please remove me immediately from the packet radio (amateur) distribution.
Your discussions are becoming too voluminous for me to follow.

I will attempt to set up another mail directory for myself for
the amateur discussions, since I am still very interested and involved.

Paul Sass
-------
15-Oct-87 20:22:11-EDT,1532;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 15 Oct 87 20:22-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 16:53:14 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 16:52:54 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA11470; Thu, 15 Oct 87 13:53:22 PDT
Return-Path: <rutgers!unirot![e-mail]>
Message-Id: <[e-mail]>
Date: 13 Oct 87 11:16:38 GMT
From: rutgers!unirot![e-mail] (Steve Miller)
To: [e-mail]
Subject: I need help with my KAM.

I just bought a Kantronics KAM, and am having a problem.  While it
works pretty well with my Argonaut, it (the KAM) puts out alot of
RF that completely desenses by Yaesu FT23R (2m ht).  It's a bit odd,
because, while the signal strength meter on the ht goes full scale,
the squelch does not break.  Opening the squelch manually will allow
one to hear a strong hum, easily correlated with distance from the
KAM.  I made up long (50') wire to carry the ear and mike lines away
>from the KAM, but the RF comes down the ear line!  The folks at
Kantronics tell me that they use a Kenwood ht right on the bench with
a model 100 (which I am also using) and the KAM, with no trouble.

Does anyone else have my setup?  I need help!!!
--
    -Steve Miller WA4LDA            ihnp4!rutgers!unirot!srm

"The Fantasy Factory" is a trademark of Image Space, a New Jersey corporation.


15-Oct-87 22:27:58-EDT,2824;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 15 Oct 87 22:27-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 17:51:57 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 15 Oct 87 17:50:34 EDT
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA27794; Thu, 15 Oct 87 17:50:50 EDT
Received: by ACHILLES (5.45/4.7) id AA22811; Thu, 15 Oct 87 17:48:54 EDT
Received: from ROOK.SCRC.Symbolics.COM by VALLECITO.SCRC.Symbolics.COM via CHAOS with CHAOS-MAIL id 168550; Thu 15-Oct-87 17:48:57 EDT
Date: Thu, 15 Oct 87 17:48 EDT
From: Henry Minsky <[e-mail]>
Subject: I need help with my KAM.
To: [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <[e-mail]>

    Date: 13 Oct 87 11:16:38 GMT
    From: rutgers!unirot![e-mail] (Steve Miller)
    To: [e-mail]
    Subject: I need help with my KAM.

    I just bought a Kantronics KAM, and am having a problem.  While it
    works pretty well with my Argonaut, it (the KAM) puts out alot of
    RF that completely desenses by Yaesu FT23R (2m ht).  It's a bit odd,
    because, while the signal strength meter on the ht goes full scale,
    the squelch does not break.  Opening the squelch manually will allow
    one to hear a strong hum, easily correlated with distance from the
    KAM.  I made up long (50') wire to carry the ear and mike lines away
    >from the KAM, but the RF comes down the ear line!  The folks at
    Kantronics tell me that they use a Kenwood ht right on the bench with
    a model 100 (which I am also using) and the KAM, with no trouble.

    Does anyone else have my setup?  I need help!!!
    --
        -Steve Miller WA4LDA                ihnp4!rutgers!unirot!srm

I have operated with the setup you describe; a KAM and a FT23 ht.

I have never noticed any rf interference from the KAM to the ht. I did
notice alot of rf interference when I tried to connect the KAM to a
Kenwood 2mtr mobile xcvr on my bench. But this was when I had alligator
clips hanging off of the mic connector. When I made up a shielded
(Belden) cable to go from the KAM to the Kenwood, most of the
interference stopped.

Try making sure that the cable is as well shielded as possible, like use
cable with metal foil shield, and make sure the metal connector bodies
are grounded to something.

By the way, I was having terrible luck in making the NET tcp/ip package
work with my ft23r, until I found that you have to set the kiss
parameters txdelay to about 30 (300ms?), and the txtail to at least 10
or 20. Apparently, the transmitter was chopping off the tail of each
packet it transmitted.

Henry Minsky, N1EZP

16-Oct-87 03:47:43-EDT,1471;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 16 Oct 87 03:47-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 16 Oct 87 02:53:17 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 16 Oct 87 02:53:00 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA03061; Thu, 15 Oct 87 23:53:30 PDT
Return-Path: <ihnp4!homxb!hotps!ka2qhd![e-mail]>
Message-Id: <[e-mail]>
Date: 15 Oct 87 18:16:26 GMT
From: ihnp4!homxb!hotps!ka2qhd![e-mail] (Thomas A. Moulton)
To: [e-mail]
Subject: Re: Packet freqs
Summary: 10M activity
References: <[e-mail]>

Let's not forget the 10 Meter activity, 28.102 Mhz

Notice it is in the Novice band (!) and altho nobody is doing it
you can run 1200 Baud! (from the east coast openings to the central states
are very common, that could help the congestion on 20M...)
[That is if the 20M ops would relaize there are other bands besides 20M]

I have also seen [in the past] activity on 30M abt 10.147Mhz

Remember 30M is a TOTALLY DIGITAL BAND, WHY HAVEN'T we Jumped on it with
both feet?????

--
Life is too short to be mad about things.
Thomas A. Moulton, W2VY          Packet: w2vy@kd6th  Voice: 145.190 (r)
(201) 779-W2VY                   uucp: ...!ihnp4!hotps!ka2qhd!w2vy
FAX: [phone]              [phone] x3226 (w)


17-Oct-87 21:36:07-EDT,3102;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Oct 87 21:36-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 17 Oct 87 20:29:58 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 17 Oct 87 20:28:21 EDT
Date: Sat, 17 Oct 1987  18:25 MDT
Message-Id: <[e-mail]>
Sender: [e-mail]
From: Keith Petersen <[e-mail]>
To: [e-mail], [e-mail]
Cc: [e-mail], [e-mail]
Subject: KA9Q Internet TCP/IP for MSDOS files available from SIMTEL20

Now available via standard anonymous FTP from SIMTEL20...

Filename                Type     Bytes   CRC

Directory PD:<MSDOS.KA9Q-TCPIP>
ARCFILES.DIR            ASCII    14494  36FCH <--listing of all ARC dirs
NET_BM.ARC              BINARY   23563  0FD9H
NET_DES.ARC             BINARY   18954  2373H
NET_DOC.ARC             BINARY  106817  3824H
NET_EXE.ARC             BINARY   90321  BA0DH
NET_READ.ME             ASCII     1844  62EBH
NET_SRC.ARC             BINARY  208746  D2DBH
TNC_ASH.ARC             BINARY   57272  72ADH
TNC_LDR.ARC             BINARY   15810  695BH
TNC_TNC1.ARC            BINARY   33640  588FH
TNC_TNC2.ARC            BINARY   49768  84D2H

All ARCs here are SEA-compatible.  Here is the NET_READ.ME file:

Welcome to the KA9Q Internet Package!

*** WARNING:  The 870829.0 release was cobbled together during the paper
*** presentations at the 6th ARRL Digital Conference in Redondo Beach, CA.
*** It therefore has not been tested nearly as well as the previous release,
*** 870526.0... therefore, don't throw away your old disks until you've run
*** this long enough to be happy with it!  Problem reports always welcome.

The .ARC files that make up the distribution are compressed archives that
were created with the ARC program produced by System Enhancement Associates.

The distribution is structured based on the directory structure used to
create the software:

NET_BM.ARC      .\BM    - sources to Bdale's Mailer, and Gerard's Gateway
NET_DES.ARC     .\DES   - an implementation of DES (Data Encryption Standard)
              for possible use in validating logins, etc.
NET_DOC.ARC     .\DOC   - all of the doc files
NET_EXE.ARC     .\EXE   - executable programs and config files
NET_SRC.ARC     .\SRC   - sources to NET.EXE

TNC_ASH.ARC     .\TNC\ASH       - KISS for the VADCG and ASHBY boards
TNC_LDR.ARC     .\TNC\LDR       - N4HY's KISS downloader in Turbo Pascal
TNC_TNC1.ARC    .\TNC\TNC1      - KISS for the TAPR TNC-1 and clones
TNC_TNC2.ARC    .\TNC\TNC2      - KISS for the TAPR TNC-2 and clones


Whatever you do, *PLEASE* don't unpack all of the .ARC files in one directory,
as there are duplicate names all over the place... Makefiles, README files,
etc.

After unpacking, look for a README file in each archive.  Read this first,
before you do *anything* else.  Some are just informative, some are very
important.

Finally, we're constantly striving to improve this software, and the
distribution as a whole.  Comments may be forwarded to Bdale Garbee, N3EUA.
Several of the Doc files include info on how to reach me...

Above all, HAVE FUN!

73 - Bdale, N3EUA
17-Oct-87 21:43:30-EDT,1349;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 17 Oct 87 21:43-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 17 Oct 87 20:36:42 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 17 Oct 87 20:36:20 EDT
Resent-Message-Id: <[e-mail]>
Date: Saturday, 17 October 1987  14:38-MDT
Message-Id: <[e-mail]>
Sender: [e-mail] (Clarence Wilkerson)
From: [e-mail] (Clarence Wilkerson)
To: [e-mail]
Cc: [e-mail]
Resent-From: [e-mail]
Resent-To: [e-mail]
Resent-Date: Sat 17 Oct 1987 18:30-MDT

Although I have mostly pc's, at work I have SUNS and VAXES, while in
my basement here are two H89's and a MOSTEK STD bus system.

I've been playing with the KA9Q internet (packet radio) between my
pc's at home. There is source in Aztec C, but it's mentioned that the
stuff has been compiled for the Xerox 820, a z80 8 bit machine.  I
have different serial chips, but I wonder if an executable version for
z80's, with patch lists for different serial chips is out somewhere.

Clarence Wilkerson ( also at [e-mail])
716-244-1802 (Friday-Mon) 607-255-7241 ( Tue-Thurs )
18-Oct-87 12:53:31-EDT,1374;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 18 Oct 87 12:53-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 18 Oct 87 11:43:12 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 18 Oct 87 11:43:01 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA13127; Sun, 18 Oct 87 08:43:40 PDT
From: rutgers!iuvax!wa8ejh![e-mail]
Return-Path: <rutgers!iuvax!wa8ejh![e-mail]>
Message-Id: <[e-mail]>
Date: 18 Oct 87 04:20:15 GMT
To: [e-mail]
Subject: COSI alpha/beta status?
Keywords: COSI NET/ROM

What is the current status of the COSI project? We here in the Henderson
Kentucky/Evansville Indiana area are on a boundary line between NET/ROM
and the Pac-comm COSI systems (NET/ROM north, COSI south).

We are patiently waiting for some release of the revised COSI before
committing to either system.

If we could be added to the test system (either at alpha or beta level)
we could check it out for the creators, and make our determination
quickly. Considerable pressure is being applied to go NET/ROM now, but
if a testing site, we could hold them off long enough to make a firm
decision based on production models.
Replies are best sent to:

Ray Browning,
KJ4HP @ N4Xi


18-Oct-87 12:54:05-EDT,1469;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 18 Oct 87 12:54-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 18 Oct 87 11:45:19 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 18 Oct 87 11:45:09 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17791; Sun, 18 Oct 87 08:45:52 PDT
Return-Path: <bellcore!faline![e-mail]>
Message-Id: <[e-mail]>
Date: 18 Oct 87 06:58:11 GMT
From: bellcore!faline![e-mail] (Phil R. Karn)
To: [e-mail]
Subject: Re: KA9Q Internet TCP/IP for MSDOS files available from SIMTEL20
References: <[e-mail]>

I'm finishing up a major revision of the package, so an update will
be out soon.  Here are the highlights:

1. Full-blown AX.25 support. You can use net.exe to emulate an ordinary
AX.25 TNC and dumb terminal (so you can go slumming around your
local PBBS while you're waiting for an FTP to complete!)  You can
also use AX.25 to carry IP datagrams so you get link level fragmentation
and acknowledgements on a hop-by-hop basis.

2. Greatly improved portability.  A lot of pointer alignment problems
have been eliminated.

3. Session recording and uploading. You can record interactive sessions
in files, and upload files as though they were typed on the
keyboard.  This is mainly useful with the AX25TNC mode.

Phil


20-Oct-87 13:56:56-EDT,2031;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 20 Oct 87 13:56-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:34:19 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:34:08 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA03964; Tue, 20 Oct 87 08:34:43 PDT
Return-Path: <uunet!nuchat!splut![e-mail]>
Message-Id: <[e-mail]>
Date: 18 Oct 87 21:20:22 GMT
From: uunet!nuchat!splut![e-mail] (Jay Maynard)
To: [e-mail]
Subject: KA9Q's TCP/IP under Unix?...and other stuff
Keywords: addresses, porting, and TNC/1s

Several more-or-less unrelated questions/comments:

1) Is there a version of the KA9Q TCP/IP protocol suite set up to run under
Microport System V/AT? Am I likely to reinvent lots of wheels trying to port
it myself? I'd eventually like to set up this system as a packet/USEnet
gateway (Yes, I'm aware of the legal issues...netnews is a longer-term
consideration than mail.), but I'll need to get it running under Unix first.

2) Who's the person that coordinates the assignments of IP address blocks?
Our local organization (Houston Area Packet Radio Society) has gotten
general consensus agreement in Texas to serve as the address coordinator,
but messages left on Bdale Garbee's BBS have so far gone unanswered. Bdale,
you listening? Are you the right person?

3) (sitting here staring at a ROM) The current releases of KA9Q's package
contain ROMable KISS code for the TNC1. I haven't tried it yet (due mainly
to temporary lack of a DOS machine), but it's supposed to work fairly well.

--
Jay Maynard, K5ZC (@WB5BBW)...>splut!< | uucp: uunet!nuchat!splut!jay
Never ascribe to malice that which can |  or: academ!uhnix1!--^
adequately be explained by stupidity.  | GEnie: JAYMAYNARD   CI$: 71036,1603
The opinions herein are shared by neither of my cats, much less anyone else.


20-Oct-87 14:14:18-EDT,6963;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 20 Oct 87 14:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:44:19 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:43:41 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA04148; Tue, 20 Oct 87 08:44:25 PDT
Return-Path: <ihnp4!alberta!ncc![e-mail]>
Message-Id: <[e-mail]>
Date: 19 Oct 87 23:17:10 GMT
From: ihnp4!alberta!ncc![e-mail] (Lyndon Nerenberg)
To: [e-mail]
Subject: Packet map for Alberta
Keywords: incomplete

Larry asked me to post this. Please send additions to hime at the address
indicated, or to alberta!calgary!ve6boa!larry.
-----
Hi:
    Here is a packet network map, please spread it around as far as
    you can, so I can make it more accurate.

Thanks,
Larry

============================================================================
= DATE OF LAST REVISON: OCTOBER 17, 1987             -=< ALBERTA MAP >=-   =
============================================================================
            ** Larry Gadallah        **
            ** 1602 3524 31 St NW    **
            ** Calgary, Alta T2L 2A5 **
            ** 403-289-0129          **
=========================================================================
     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     +                                                            +
     +                                                            +
     +                                                            +
     +                                                            +
     +                                                            +
    +                                                              +
    +                                                              +
    +                                                              +
    +                                                              +
    +                                                              +
   +                                                                +
   +                                                                +
   +                                                                +
   +                                                                +
   +                  VE6BOK@--[EDM]-@VE6MC                          +
  +                   [SPL]  \      \                                +
  +                           ------@VE6MIQ [MIQ]                    +
  +                                                                  +
  +                                                                  +
   +                            [RDR]                                 +
  +                                                                   +
   ++                                                                 +
     +                              @VE6RCB [CBN]                     +
       +                           /                                   +
    + +                       /                                    +
       +                     @VE6RYC [CAL]                         +
      +                      |\                                    +
        +                    | \                                   +
         +       [CLR] VE6ROT@  \                                 +
           +                     \                                +
           +                      ---@VE6TWO [VUL]                +
        + +                                                   +
           +                                                  +
            +                                                +
              +                                              +
               +                                             +
               +                                             +
            +                                            +
              +                                          +
               +++++++++++++++++++++++++++++++++++++++++++
  =========================================================================
  EDM-Edmonton SPL-Stony Plain MIQ-Miquelon Lake RDR-Red Deer
  CBN-Carbon   CAL-Calgary     VUL-Vulcan        CLR-Clairesholm
  =========================================================================
               --> Digipeaters in Alberta <--
  =========================================================================
  CALLSIGN   SYSOP        LOCATION              TYPE
  -------------------------------------------------------------------
  VE6RYC     VE6CID       North Calgary         AX.25 lvl 2
  VE6MC      NARC?        East Edmonton         NetROM(?)/AX.25
  VE6BOK     VE6BOK       Stony Plain           AX.25 lvl 2
  VE6RCB     VE6CID       Carbon                AX.25 lvl 2
  VE6MIQ     ?            Miquelon Lake         AX.25 lvl 2
  VE6TWO     VE6ANI       Vulcan                AX.25 lvl 2(?)
  VE6ROT     VE6LZ        Clairesholm           AX.25 lvl 2

             Digi Connections
  -------------------------------------------------------------------
  DIGI                    CAN CONNECT TO:
  -------------------------------------------------------------------
  VE6RYC   -------------> VE6RCB/VE6ROT/VE6TWO
  VE6MIQ   -------------> VE6MC/VE6BOK
  VE6RCB   -------------> VE6RYC
  VE6ROT   -------------> VE6RYC/VE6TWO
  VE6TWO   -------------> VE6ROT/VE6RYC
  VE6BOK   -------------> VE6MIQ/VE6MC
  VE6MC    -------------> VE6BOK
  ============================================================================
           --> Known Packet Stations in Alberta <--

  legend <*> digipeater available 24h
     <w> W0RLI/WA7MBL pbbs
     <h> HF W0RLI/WA7MBL gateway
     <t> TCP/IP node/switch
     <n> NetROM node
  ============================================================================
  (Calgary)
   VE6LZ Cal    VE6LH Claude    VE6CID Doug     VE6AEZ<t> Ron   VE6JX Ian
   VE6NI Earl   VE6BOA<t> Larry VE6KC Larry     VE6ABV Martin   VE6ZP John
   VE6RYC<*>    CARA<w>         VE6AEZ-1<h>     VE6ANI Walter   VE6COT Pete
   VE6CIZ Gene  VE6VA George    VE6AW Paul      VE6CMY Ron      VE6AFO Ken
  (Edmonton)
   VE6BKT Keith VE6OG Les       VE6MC<*n>       VE6BSF Brian    VE6BLC Bob
   VE6AXL Ernie VE6BJP Jim      VE6CX George
  (Ft. Saskatchewan)
   VE6BEZ Terry
  (Lethbridge)
  (Red Deer)
   VE6BPR Al    VE6BDH Blair
  (Sherwood Park)
   VE6BDG Brian VE6GS Alex
  (St. Albert)
   VE6BMQ Geza
  (Stony Plain)
  VE6BOK<*> Ed

  Please notify Larry, VE6BOA@CARA of any errors or omissions, Thank you.
             ----  END OF ALBERTA MAP -1087 ----


20-Oct-87 15:01:01-EDT,2498;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 20 Oct 87 15:00-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 12:32:46 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 12:32:29 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA05907; Tue, 20 Oct 87 09:33:07 PDT
Return-Path: <cadre!pitt!winfree![e-mail]>
Message-Id: <[e-mail]>
Date: 19 Oct 87 19:30:58 GMT
From: cadre!pitt!winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: Re: TAPR TNC1
References: <289@usl>

In article <289@usl> [e-mail] (Stephen J. Mahler) writes:
>I am looking for some new firmware to get my trust old TAPR TNC1
>geared up for TCP/IP.

Sources and Intel and Motorola hex files are in the standard KA9Q TCP/IP
software release.  If you can FTP from Internet sites, look on the machine
louie.udel.edu, for the file pub/ka9q/tnc_tnc1.arc...

If you can't get to it there, try my BBS at 303/495-2061 (new number!), and
look for the file TNC_TNC1.ARC in the TCP files area.

>    ->  TAPR Software and KISS Bootstrap Loader

    Noone has done this other than by using a 27128 with the two pieces
    in the two halves, and a toggle switch to select one or the other...
    as far as I know.

>    ->  WA8DED Software and KISS Bootstrap Loader

    Don't bother.  The KISS implementation for the TNC1 is very solid
    right now.

>    ->  ( TAPR or WA8DED ) and KISS Software

    Lyle at TAPR was talking about doing this at one point.  You might
    try sending a note to Lyle c/o the TAPR post office box and ask
    if it ever got done?

>An address to mail to get a PROM or a file to blow my own PROMS
>would be great.

If none of the above suggestions work, send me some email and we'll go from
there...

>tnxs & 73     ....    Steve  KF5VH   ([e-mail])

Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa}!winfree!bdale
arpa: [e-mail]
fido: sysop of 128/19 303/495-2061      packet: n3eua @ k0hoa, Colorado Springs


--
Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa,vixie}!winfree!bdale
arpa: [e-mail]
fido: sysop of 128/19 303/495-2061      packet: n3eua @ k0hoa, Colorado Springs


20-Oct-87 15:14:20-EDT,6963;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 20 Oct 87 15:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:44:19 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 11:43:41 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA04148; Tue, 20 Oct 87 08:44:25 PDT
Return-Path: <ihnp4!alberta!ncc![e-mail]>
Message-Id: <[e-mail]>
Date: 19 Oct 87 23:17:10 GMT
From: ihnp4!alberta!ncc![e-mail] (Lyndon Nerenberg)
To: [e-mail]
Subject: Packet map for Alberta
Keywords: incomplete

Larry asked me to post this. Please send additions to hime at the address
indicated, or to alberta!calgary!ve6boa!larry.
-----
Hi:
    Here is a packet network map, please spread it around as far as
    you can, so I can make it more accurate.

Thanks,
Larry

============================================================================
= DATE OF LAST REVISON: OCTOBER 17, 1987             -=< ALBERTA MAP >=-   =
============================================================================
            ** Larry Gadallah        **
            ** 1602 3524 31 St NW    **
            ** Calgary, Alta T2L 2A5 **
            ** 403-289-0129          **
=========================================================================
     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     +                                                            +
     +                                                            +
     +                                                            +
     +                                                            +
     +                                                            +
    +                                                              +
    +                                                              +
    +                                                              +
    +                                                              +
    +                                                              +
   +                                                                +
   +                                                                +
   +                                                                +
   +                                                                +
   +                  VE6BOK@--[EDM]-@VE6MC                          +
  +                   [SPL]  \      \                                +
  +                           ------@VE6MIQ [MIQ]                    +
  +                                                                  +
  +                                                                  +
   +                            [RDR]                                 +
  +                                                                   +
   ++                                                                 +
     +                              @VE6RCB [CBN]                     +
       +                           /                                   +
    + +                       /                                    +
       +                     @VE6RYC [CAL]                         +
      +                      |\                                    +
        +                    | \                                   +
         +       [CLR] VE6ROT@  \                                 +
           +                     \                                +
           +                      ---@VE6TWO [VUL]                +
        + +                                                   +
           +                                                  +
            +                                                +
              +                                              +
               +                                             +
               +                                             +
            +                                            +
              +                                          +
               +++++++++++++++++++++++++++++++++++++++++++
  =========================================================================
  EDM-Edmonton SPL-Stony Plain MIQ-Miquelon Lake RDR-Red Deer
  CBN-Carbon   CAL-Calgary     VUL-Vulcan        CLR-Clairesholm
  =========================================================================
               --> Digipeaters in Alberta <--
  =========================================================================
  CALLSIGN   SYSOP        LOCATION              TYPE
  -------------------------------------------------------------------
  VE6RYC     VE6CID       North Calgary         AX.25 lvl 2
  VE6MC      NARC?        East Edmonton         NetROM(?)/AX.25
  VE6BOK     VE6BOK       Stony Plain           AX.25 lvl 2
  VE6RCB     VE6CID       Carbon                AX.25 lvl 2
  VE6MIQ     ?            Miquelon Lake         AX.25 lvl 2
  VE6TWO     VE6ANI       Vulcan                AX.25 lvl 2(?)
  VE6ROT     VE6LZ        Clairesholm           AX.25 lvl 2

             Digi Connections
  -------------------------------------------------------------------
  DIGI                    CAN CONNECT TO:
  -------------------------------------------------------------------
  VE6RYC   -------------> VE6RCB/VE6ROT/VE6TWO
  VE6MIQ   -------------> VE6MC/VE6BOK
  VE6RCB   -------------> VE6RYC
  VE6ROT   -------------> VE6RYC/VE6TWO
  VE6TWO   -------------> VE6ROT/VE6RYC
  VE6BOK   -------------> VE6MIQ/VE6MC
  VE6MC    -------------> VE6BOK
  ============================================================================
           --> Known Packet Stations in Alberta <--

  legend <*> digipeater available 24h
     <w> W0RLI/WA7MBL pbbs
     <h> HF W0RLI/WA7MBL gateway
     <t> TCP/IP node/switch
     <n> NetROM node
  ============================================================================
  (Calgary)
   VE6LZ Cal    VE6LH Claude    VE6CID Doug     VE6AEZ<t> Ron   VE6JX Ian
   VE6NI Earl   VE6BOA<t> Larry VE6KC Larry     VE6ABV Martin   VE6ZP John
   VE6RYC<*>    CARA<w>         VE6AEZ-1<h>     VE6ANI Walter   VE6COT Pete
   VE6CIZ Gene  VE6VA George    VE6AW Paul      VE6CMY Ron      VE6AFO Ken
  (Edmonton)
   VE6BKT Keith VE6OG Les       VE6MC<*n>       VE6BSF Brian    VE6BLC Bob
   VE6AXL Ernie VE6BJP Jim      VE6CX George
  (Ft. Saskatchewan)
   VE6BEZ Terry
  (Lethbridge)
  (Red Deer)
   VE6BPR Al    VE6BDH Blair
  (Sherwood Park)
   VE6BDG Brian VE6GS Alex
  (St. Albert)
   VE6BMQ Geza
  (Stony Plain)
  VE6BOK<*> Ed

  Please notify Larry, VE6BOA@CARA of any errors or omissions, Thank you.
             ----  END OF ALBERTA MAP -1087 ----


20-Oct-87 15:14:54-EDT,2498;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 20 Oct 87 15:14-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 12:32:46 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 20 Oct 87 12:32:29 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA05907; Tue, 20 Oct 87 09:33:07 PDT
Return-Path: <cadre!pitt!winfree![e-mail]>
Message-Id: <[e-mail]>
Date: 19 Oct 87 19:30:58 GMT
From: cadre!pitt!winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: Re: TAPR TNC1
References: <289@usl>

In article <289@usl> [e-mail] (Stephen J. Mahler) writes:
>I am looking for some new firmware to get my trust old TAPR TNC1
>geared up for TCP/IP.

Sources and Intel and Motorola hex files are in the standard KA9Q TCP/IP
software release.  If you can FTP from Internet sites, look on the machine
louie.udel.edu, for the file pub/ka9q/tnc_tnc1.arc...

If you can't get to it there, try my BBS at 303/495-2061 (new number!), and
look for the file TNC_TNC1.ARC in the TCP files area.

>    ->  TAPR Software and KISS Bootstrap Loader

    Noone has done this other than by using a 27128 with the two pieces
    in the two halves, and a toggle switch to select one or the other...
    as far as I know.

>    ->  WA8DED Software and KISS Bootstrap Loader

    Don't bother.  The KISS implementation for the TNC1 is very solid
    right now.

>    ->  ( TAPR or WA8DED ) and KISS Software

    Lyle at TAPR was talking about doing this at one point.  You might
    try sending a note to Lyle c/o the TAPR post office box and ask
    if it ever got done?

>An address to mail to get a PROM or a file to blow my own PROMS
>would be great.

If none of the above suggestions work, send me some email and we'll go from
there...

>tnxs & 73     ....    Steve  KF5VH   ([e-mail])

Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa}!winfree!bdale
arpa: [e-mail]
fido: sysop of 128/19 303/495-2061      packet: n3eua @ k0hoa, Colorado Springs


--
Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa,vixie}!winfree!bdale
arpa: [e-mail]
fido: sysop of 128/19 303/495-2061      packet: n3eua @ k0hoa, Colorado Springs


22-Oct-87 14:25:08-EDT,1505;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Oct 87 14:25-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 22 Oct 87 10:24:07 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 22 Oct 87 10:23:50 EDT
Message-Id: <[e-mail]>
Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Thu, 22 Oct 87 10:26:11 EST
Received: from MAINE.BITNET by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id
 7162; Thu, 22 Oct 87 10:26:08 EST
Received: by MAINE (Mailer X1.24) id 9784; Thu, 22 Oct 87 10:21:39 EDT
Subject: Just getting started
To: Packet Radio <[e-mail]>
From: Robert L. Metcalf <[e-mail]>
Date:    Thu, 22 Oct 1987 10:12 EDT

Hi all!

   I have been in ham radio for less than a year, so I don't know too much
about packet.  Is there enough activity on the HF bands to make a TNC worth
its cost?  Are any DX stations using packet?  Would a Baudot 'modem' be a more
useful device to have?

            TNX es 73,
                  Rob

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Robert L. Metcalf - KA1QKH                      ! /   /   /!  +--+ ! / !  !
  Bitnet: RLM@Maine                               !<   /__   !  !  ! !<  !--!
  ARPA:   [e-mail]      !  /     _!_ +-- !  !  !
  Snail Mail: 369 Main Street; Orono, ME 04473
22-Oct-87 14:56:40-EDT,1505;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 22 Oct 87 14:56-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 22 Oct 87 10:24:07 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 22 Oct 87 10:23:50 EDT
Message-Id: <[e-mail]>
Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Thu, 22 Oct 87 10:26:11 EST
Received: from MAINE.BITNET by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id
 7162; Thu, 22 Oct 87 10:26:08 EST
Received: by MAINE (Mailer X1.24) id 9784; Thu, 22 Oct 87 10:21:39 EDT
Subject: Just getting started
To: Packet Radio <[e-mail]>
From: Robert L. Metcalf <[e-mail]>
Date:    Thu, 22 Oct 1987 10:12 EDT

Hi all!

   I have been in ham radio for less than a year, so I don't know too much
about packet.  Is there enough activity on the HF bands to make a TNC worth
its cost?  Are any DX stations using packet?  Would a Baudot 'modem' be a more
useful device to have?

            TNX es 73,
                  Rob

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Robert L. Metcalf - KA1QKH                      ! /   /   /!  +--+ ! / !  !
  Bitnet: RLM@Maine                               !<   /__   !  !  ! !<  !--!
  ARPA:   [e-mail]      !  /     _!_ +-- !  !  !
  Snail Mail: 369 Main Street; Orono, ME 04473
24-Oct-87 15:56:23-EDT,1462;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Oct 87 15:56-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:47:40 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:47:29 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17760; Sat, 24 Oct 87 10:48:17 PDT
Return-Path: <ames!lll-tis!lll-lcc!well![e-mail]>
Message-Id: <[e-mail]>
Date: 24 Oct 87 06:29:04 GMT
From: ames!lll-tis!lll-lcc!well![e-mail] (Glenn S. Tenney)
To: [e-mail]
Subject: PBBSes and TCP/IP
Summary: info wanted

I've been trying packet (2M) since I got my ticket (2.5 mths) and am
very disappointed both with the speed and even more so with the PBBSes
out there.  I know I've used some PBBSes running W0RLI software and a
couple that seemed different.  I've finally gotten Phil's TCP/IP code
and hope to get it up whenever I find the time (RSN).

Now the questions:
1. W0RLI software *sucks* compared to FIDO/OPUS.  Is there any
   decent PBBS software out there?  Where?
2. Is there any existing software to run with the TCP/IP code
   that would let people use it as a BBS (ie. conferencing)?
   Ideally, any readnews software (I mean, netnews is better than
   W0RLI by a looong shot!)?

Were these stupid questions or what?
tnx
Glenn Tenney
AA6ER


24-Oct-87 17:06:37-EDT,2880;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Oct 87 17:06-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:45:59 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:45:39 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17727; Sat, 24 Oct 87 10:46:23 PDT
Return-Path: <cadre!pitt!winfree![e-mail]>
Message-Id: <[e-mail]>
Date: 23 Oct 87 15:06:28 GMT
From: cadre!pitt!winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: Re: KA9Q's TCP/IP under Unix?...and other stuff
References: <[e-mail]>

In article <[e-mail]> [e-mail] (Jay Maynard) writes:
>1) Is there a version of the KA9Q TCP/IP protocol suite set up to run under
>Microport System V/AT? Am I likely to reinvent lots of wheels trying to port
>it myself? I'd eventually like to set up this system as a packet/USEnet
>gateway (Yes, I'm aware of the legal issues...netnews is a longer-term
>consideration than mail.), but I'll need to get it running under Unix first.

Yes.  Support for NET as a process under sysV will be included in the next
release.  The guy who's done the work has it up and running merrily at his
QTH.

>2) Who's the person that coordinates the assignments of IP address blocks?
>Our local organization (Houston Area Packet Radio Society) has gotten
>general consensus agreement in Texas to serve as the address coordinator,
>but messages left on Bdale Garbee's BBS have so far gone unanswered. Bdale,
>you listening? Are you the right person?

Yes, I'm here!  UUCP/Arpa mail always gets answered faster than BBS messages,
particularly when the BBS is having a rough time eating hard disks...  The
new number for the BBS at the new house, by the way, is 303/495-2061.

You need to contact Wally Linstruth.  WA6JPR.  [e-mail], or
...sdcsvax!net1!wally.  I have an address around here somewhere, it will be
included in the release notes for the next release, due real soon now.

>3) (sitting here staring at a ROM) The current releases of KA9Q's package
>contain ROMable KISS code for the TNC1. I haven't tried it yet (due mainly
>to temporary lack of a DOS machine), but it's supposed to work fairly well.

Yes, the TNC1 works great under KISS.  Thanks to Marc Kaufman (WB6ECE?) who
did the first port, and Gerard vander Grinten PA0GRI who made the latest set
of mods/fixes.  I run it here at the house, and we use it as a switch in
Colorado Springs.
--
Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa}!winfree!bdale
arpa: [e-mail]               packet: n3eua @ k0hoa, Colorado Springs
fido: sysop of 128/19 at 303/495-2061, 2400/1200/300 baud, 24hrs/day


24-Oct-87 17:45:38-EDT,1837;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Oct 87 17:45-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:50:25 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:50:14 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17792; Sat, 24 Oct 87 10:51:03 PDT
Return-Path: <hao!boulder!sunybcs![e-mail]>
Message-Id: <[e-mail]>
Date: 24 Oct 87 13:42:35 GMT
From: hao!boulder!sunybcs![e-mail] (Devon E Bowen)
To: [e-mail]
Subject: packet networking

Here I go again tapping USENET with more questions about packet...

This one is more related to school, though. I'm taking a class in Local
Area Networks and we have to do some kind of research paper before the
end of the semester. I was hoping to do something on packet radio. This
would allow me to study packet in more detail and get my school work
done at the same time.

I don't really know what area I'd like to focus on, so I'm looking for
references for any facet of packet radio that can be remotely tied to
networking. Something on the protocals, history (ALOHA net - I believe),
or current plans or implementations. This is a graduate level class, so
I'm looking for the nitty-gritty technical details. Does anyone have any
such references that I might consult? Thanks in advance...


                   Devon Bowen (KA2NRC)
                   University of Buffalo

*********************************************************
uucp:      ..!{ames,boulder,decvax,rutgers}!sunybcs!bowen
Internet:  [e-mail]
BITNET:    [e-mail]
*********************************************************


24-Oct-87 17:54:29-EDT,2880;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Oct 87 17:54-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:45:59 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:45:39 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17727; Sat, 24 Oct 87 10:46:23 PDT
Return-Path: <cadre!pitt!winfree![e-mail]>
Message-Id: <[e-mail]>
Date: 23 Oct 87 15:06:28 GMT
From: cadre!pitt!winfree![e-mail] (Bdale Garbee)
To: [e-mail]
Subject: Re: KA9Q's TCP/IP under Unix?...and other stuff
References: <[e-mail]>

In article <[e-mail]> [e-mail] (Jay Maynard) writes:
>1) Is there a version of the KA9Q TCP/IP protocol suite set up to run under
>Microport System V/AT? Am I likely to reinvent lots of wheels trying to port
>it myself? I'd eventually like to set up this system as a packet/USEnet
>gateway (Yes, I'm aware of the legal issues...netnews is a longer-term
>consideration than mail.), but I'll need to get it running under Unix first.

Yes.  Support for NET as a process under sysV will be included in the next
release.  The guy who's done the work has it up and running merrily at his
QTH.

>2) Who's the person that coordinates the assignments of IP address blocks?
>Our local organization (Houston Area Packet Radio Society) has gotten
>general consensus agreement in Texas to serve as the address coordinator,
>but messages left on Bdale Garbee's BBS have so far gone unanswered. Bdale,
>you listening? Are you the right person?

Yes, I'm here!  UUCP/Arpa mail always gets answered faster than BBS messages,
particularly when the BBS is having a rough time eating hard disks...  The
new number for the BBS at the new house, by the way, is 303/495-2061.

You need to contact Wally Linstruth.  WA6JPR.  [e-mail], or
...sdcsvax!net1!wally.  I have an address around here somewhere, it will be
included in the release notes for the next release, due real soon now.

>3) (sitting here staring at a ROM) The current releases of KA9Q's package
>contain ROMable KISS code for the TNC1. I haven't tried it yet (due mainly
>to temporary lack of a DOS machine), but it's supposed to work fairly well.

Yes, the TNC1 works great under KISS.  Thanks to Marc Kaufman (WB6ECE?) who
did the first port, and Gerard vander Grinten PA0GRI who made the latest set
of mods/fixes.  I run it here at the house, and we use it as a switch in
Colorado Springs.
--
Bdale Garbee, N3EUA                     phone: [phone] h, 303/590-2868 w
uucp: {bellcore,crash,hp-lsd,ncc,pitt,usafa}!winfree!bdale
arpa: [e-mail]               packet: n3eua @ k0hoa, Colorado Springs
fido: sysop of 128/19 at 303/495-2061, 2400/1200/300 baud, 24hrs/day


24-Oct-87 20:26:05-EDT,1837;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 24 Oct 87 20:26-EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:50:25 EDT
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 24 Oct 87 13:50:14 EDT
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17792; Sat, 24 Oct 87 10:51:03 PDT
Return-Path: <hao!boulder!sunybcs![e-mail]>
Message-Id: <[e-mail]>
Date: 24 Oct 87 13:42:35 GMT
From: hao!boulder!sunybcs![e-mail] (Devon E Bowen)
To: [e-mail]
Subject: packet networking

Here I go again tapping USENET with more questions about packet...

This one is more related to school, though. I'm taking a class in Local
Area Networks and we have to do some kind of research paper before the
end of the semester. I was hoping to do something on packet radio. This
would allow me to study packet in more detail and get my school work
done at the same time.

I don't really know what area I'd like to focus on, so I'm looking for
references for any facet of packet radio that can be remotely tied to
networking. Something on the protocals, history (ALOHA net - I believe),
or current plans or implementations. This is a graduate level class, so
I'm looking for the nitty-gritty technical details. Does anyone have any
such references that I might consult? Thanks in advance...


                   Devon Bowen (KA2NRC)
                   University of Buffalo

*********************************************************
uucp:      ..!{ames,boulder,decvax,rutgers}!sunybcs!bowen
Internet:  [e-mail]
BITNET:    [e-mail]
*********************************************************


25-Oct-87 15:44:51-EST,6892;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 25 Oct 87 15:44-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 25 Oct 87 14:05:43 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 25 Oct 87 14:04:41 EST
Resent-Message-Id: <[e-mail]>
Date: Sunday, 25 October 1987  11:58-MST
Message-Id: <[e-mail]>
Sender: Keith Petersen <[e-mail]>
From: Keith Petersen <[e-mail]>
To: [e-mail]
Subject:   NCSA Telnet version 2.0 for IBMPC available from SIMTEL20
Resent-From: [e-mail]
Resent-To: [e-mail]
Resent-Date: Sun 25 Oct 1987 12:04-MST

Now available from SIMTEL20...

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.TELNET>
PCTEL20.ARC.1                   BINARY  216064  25BEH

The announcement from NCSA follows.  Please note the Macintosh version
is *not* available from SIMTEL20, only the IBMPC version.

--Keith Petersen

--forwarded message--
From: [e-mail] (Tim K telnet use)
Newsgroups: comp.protocols.tcp-ip
Subject: NCSA Telnet version 2.0 available
Date: 5 Oct 87 20:55:31 GMT

New software for free . . .

The National Center for Supercomputing Applications has good news and
more good news for Macintosh and PC TCP/IP users.

    New version 2.0 of NCSA Telnet for the PC
    New version 2.0 of NCSA Telnet for the Macintosh
    New hardware support in testing
    Mailing list for telnet related questions/bugs ([e-mail])
    User/Developer forum at TCP/IP conference in December
    SOURCE CODE coming soon!

On November 1, NCSA will release full source code to version 2.1 of
NCSA Telnet for the PC and Macintosh.  Anyone may use, modify and
redistribute this code subject to the licensing (not-for-profit)
statement included with the source.  We will redistribute contributed
source code on an ongoing basis.

Version 2.0 of NCSA Telnet is available now -- availability
information is appended to this note.  We have many new features,
including Tektronix 4014 emulation.  Previous bug on PCs and XTs is
gone.  The pre-printed manual has been completely re-written and is
worth the $20.

We are sponsoring a mailing list for people interested in keeping up
with the NCSA Telnet distribution and the various groups taking part
in future development.  The address is [e-mail].  Send a
message to [e-mail] to get on the list.

For the PC, we have a driver for the MICOM NI5210 (not the NI5010)
board, which has a list price of $395.00 and a driver for the
Ungermann-Bass (IBM) NIC Ethernet board.  These drivers won't be
included until version 2.1 but may be available upon request.

For the Macintosh, we are testing a version which uses Apple's new
EtherTalk driver directly.  This is not in version 2.0, but will be
in 2.1.

There will be a meeting at Advanced Computing Environment's TCP/IP
conference in December.  I will discuss user problems and the status
of various development projects.  This will be a good time to ask
technical questions.

Thanks for your interest, some details follow the signature,

Tim Krauskopf
National Center for Supercomputing Applications (NCSA)
University of Illinois

[e-mail]            (ARPA)
[e-mail]  (alternate)
14013@ncsavmsa                (BITNET)

--------------------------------------------------------------------
Fact Sheet
----------

National Center for Supercomputing Applications presents:

NCSA Telnet for the PC, version 2.0
NCSA Telnet for the Macintosh, version 2.0

These programs are copyrighted, but distributed in binary form with
no license fee.  Source code will be available on November 1.

Features included in version 2.0 of NCSA Telnet:
-----------------------------------------------
DARPA standard telnet
Built-in standard FTP server for file transfer
VT102 emulation in multiple, simultaneous sessions
Class A,B and C addressing with standard subnetting
Tektronix 4014 graphics emulation
Scrollback for each session
Each session in a different window (Macintosh)
Supports Croft gateway - KIP (Macintosh)
Capture text to a file (PC)
Full color support (PC)

How to obtain:
-------------
1) From a friend

The disk, documentation and files may be copied freely and distributed in
binary form, unmodified, with copyright notices intact.  This distribution
is free and no copies may be sold for profit.

2) Anonymous FTP from   uxc.cso.uiuc.edu   in the NCSA subdirectory.

The PC version is a tar file which contain binary files.  There is also a
compressed tar file with the same contents.  After the files are extracted
from the tar file, some binary transfer (e.g. kermit, NCSA Telnet) should
be used to download the files to the PC.  The documentation is in line
printer format.

The Macintosh version is in the NCSA/Mac subdirectory and consists of
several files encoded with BinHex 4.0 and/or Pack-It.  You may want to
consult the READ.ME file to determine which files to download.  Download
them with a binary transfer method (kermit, NCSA Telnet) and use BinHex
4.0 and/or Pack-It to extract the files.  The documentation is in
Microsoft Word 3.0 format.

3) Diskette

On-disk copies, with a printed manual are available for $20 each, which
covers materials, handling and postage.  Orders can only be accepted if
accompanied by a check made out to the University of Illinois.  Send to:

NCSA Telnet orders (specify PC or Macintosh version)
152 Computing Applications Building
605 E. Springfield Ave.
Champaign, IL 61820

Hardware required:
-----------------
PC: IBM PC,XT, AT or compatible. 3COM 3C501 Etherlink board.
    IBM RT PC Baseband adapter support soon.
    Ungermann-Bass NIC board support soon.
    MICOM NI5210 Ethernet board support soon.

Mac: Macintosh 512K, Plus, SE or Macintosh II.
    Kinetics, Inc. FastPath, EtherSC or Etherport SE.
    Kinetics gateway software or Stanford KIP (Croft) gateway software.
    Support soon for Apple EtherTalk board and software for the
    Macintosh II.

The best source of information about Kinetics is directly from the company.
Kinetics Inc.                     FastPath approx. $2500
Suite 110                         EtherSC approx. $1250
2500 Camino Diablo                EtherPort SE approx. $800
Walnut Creek, CA  94596
[phone]

Mailing List:
------------
Mail to [e-mail] to be added to the list of recipients.
To post messages to the list, mail to [e-mail].
If your mailer cannot resolve ncsa.uiuc.edu, route mail through
uxc.cso.uiuc.edu, also known as uiucuxc.arpa.

Other questions:
---------------
mail to [e-mail] (alternate: [e-mail])
25-Oct-87 18:02:59-EST,6892;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 25 Oct 87 18:02-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 25 Oct 87 14:05:43 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sun, 25 Oct 87 14:04:41 EST
Resent-Message-Id: <[e-mail]>
Date: Sunday, 25 October 1987  11:58-MST
Message-Id: <[e-mail]>
Sender: Keith Petersen <[e-mail]>
From: Keith Petersen <[e-mail]>
To: [e-mail]
Subject:   NCSA Telnet version 2.0 for IBMPC available from SIMTEL20
Resent-From: [e-mail]
Resent-To: [e-mail]
Resent-Date: Sun 25 Oct 1987 12:04-MST

Now available from SIMTEL20...

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.TELNET>
PCTEL20.ARC.1                   BINARY  216064  25BEH

The announcement from NCSA follows.  Please note the Macintosh version
is *not* available from SIMTEL20, only the IBMPC version.

--Keith Petersen

--forwarded message--
From: [e-mail] (Tim K telnet use)
Newsgroups: comp.protocols.tcp-ip
Subject: NCSA Telnet version 2.0 available
Date: 5 Oct 87 20:55:31 GMT

New software for free . . .

The National Center for Supercomputing Applications has good news and
more good news for Macintosh and PC TCP/IP users.

    New version 2.0 of NCSA Telnet for the PC
    New version 2.0 of NCSA Telnet for the Macintosh
    New hardware support in testing
    Mailing list for telnet related questions/bugs ([e-mail])
    User/Developer forum at TCP/IP conference in December
    SOURCE CODE coming soon!

On November 1, NCSA will release full source code to version 2.1 of
NCSA Telnet for the PC and Macintosh.  Anyone may use, modify and
redistribute this code subject to the licensing (not-for-profit)
statement included with the source.  We will redistribute contributed
source code on an ongoing basis.

Version 2.0 of NCSA Telnet is available now -- availability
information is appended to this note.  We have many new features,
including Tektronix 4014 emulation.  Previous bug on PCs and XTs is
gone.  The pre-printed manual has been completely re-written and is
worth the $20.

We are sponsoring a mailing list for people interested in keeping up
with the NCSA Telnet distribution and the various groups taking part
in future development.  The address is [e-mail].  Send a
message to [e-mail] to get on the list.

For the PC, we have a driver for the MICOM NI5210 (not the NI5010)
board, which has a list price of $395.00 and a driver for the
Ungermann-Bass (IBM) NIC Ethernet board.  These drivers won't be
included until version 2.1 but may be available upon request.

For the Macintosh, we are testing a version which uses Apple's new
EtherTalk driver directly.  This is not in version 2.0, but will be
in 2.1.

There will be a meeting at Advanced Computing Environment's TCP/IP
conference in December.  I will discuss user problems and the status
of various development projects.  This will be a good time to ask
technical questions.

Thanks for your interest, some details follow the signature,

Tim Krauskopf
National Center for Supercomputing Applications (NCSA)
University of Illinois

[e-mail]            (ARPA)
[e-mail]  (alternate)
14013@ncsavmsa                (BITNET)

--------------------------------------------------------------------
Fact Sheet
----------

National Center for Supercomputing Applications presents:

NCSA Telnet for the PC, version 2.0
NCSA Telnet for the Macintosh, version 2.0

These programs are copyrighted, but distributed in binary form with
no license fee.  Source code will be available on November 1.

Features included in version 2.0 of NCSA Telnet:
-----------------------------------------------
DARPA standard telnet
Built-in standard FTP server for file transfer
VT102 emulation in multiple, simultaneous sessions
Class A,B and C addressing with standard subnetting
Tektronix 4014 graphics emulation
Scrollback for each session
Each session in a different window (Macintosh)
Supports Croft gateway - KIP (Macintosh)
Capture text to a file (PC)
Full color support (PC)

How to obtain:
-------------
1) From a friend

The disk, documentation and files may be copied freely and distributed in
binary form, unmodified, with copyright notices intact.  This distribution
is free and no copies may be sold for profit.

2) Anonymous FTP from   uxc.cso.uiuc.edu   in the NCSA subdirectory.

The PC version is a tar file which contain binary files.  There is also a
compressed tar file with the same contents.  After the files are extracted
from the tar file, some binary transfer (e.g. kermit, NCSA Telnet) should
be used to download the files to the PC.  The documentation is in line
printer format.

The Macintosh version is in the NCSA/Mac subdirectory and consists of
several files encoded with BinHex 4.0 and/or Pack-It.  You may want to
consult the READ.ME file to determine which files to download.  Download
them with a binary transfer method (kermit, NCSA Telnet) and use BinHex
4.0 and/or Pack-It to extract the files.  The documentation is in
Microsoft Word 3.0 format.

3) Diskette

On-disk copies, with a printed manual are available for $20 each, which
covers materials, handling and postage.  Orders can only be accepted if
accompanied by a check made out to the University of Illinois.  Send to:

NCSA Telnet orders (specify PC or Macintosh version)
152 Computing Applications Building
605 E. Springfield Ave.
Champaign, IL 61820

Hardware required:
-----------------
PC: IBM PC,XT, AT or compatible. 3COM 3C501 Etherlink board.
    IBM RT PC Baseband adapter support soon.
    Ungermann-Bass NIC board support soon.
    MICOM NI5210 Ethernet board support soon.

Mac: Macintosh 512K, Plus, SE or Macintosh II.
    Kinetics, Inc. FastPath, EtherSC or Etherport SE.
    Kinetics gateway software or Stanford KIP (Croft) gateway software.
    Support soon for Apple EtherTalk board and software for the
    Macintosh II.

The best source of information about Kinetics is directly from the company.
Kinetics Inc.                     FastPath approx. $2500
Suite 110                         EtherSC approx. $1250
2500 Camino Diablo                EtherPort SE approx. $800
Walnut Creek, CA  94596
[phone]

Mailing List:
------------
Mail to [e-mail] to be added to the list of recipients.
To post messages to the list, mail to [e-mail].
If your mailer cannot resolve ncsa.uiuc.edu, route mail through
uxc.cso.uiuc.edu, also known as uiucuxc.arpa.

Other questions:
---------------
mail to [e-mail] (alternate: [e-mail])
27-Oct-87 03:05:54-EST,4797;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 03:05-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 00:55:01 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 00:54:28 EST
Resent-Message-Id: <[e-mail]>
Date: Monday, 26 October 1987  12:02-MST
Message-Id: <[e-mail]>
Sender: [e-mail] (Robert B. Hoffman)
From: [e-mail] (Robert B. Hoffman)
To: [e-mail]
Subject:   W0RLI PBBS version 4.0 available from SIMTEL20
Resent-From: [e-mail]
Resent-To: [e-mail]
Resent-Date: Mon 26 Oct 1987 22:53-MST

The latest W0RLI/VE3GYQ C PBBS, version 4.0, is now available
for anonymous FTP from host SIMTEL20.

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
IO40.ARC                        BINARY   10752  3905H
IOSRC40.ARC                     BINARY   41984  AAC9H
MB40READ.ME                     ASCII     3496  4CA9H
RUN40.ARC                       BINARY  120320  D4F8H
SRC40.ARC                       BINARY   90624  C256H

These files replace the earlier io32.arc, iosrc32.arc, run32.arc, and
src32.arc.  The file MBBIOS.ARC has not been updated and is still
available...

Filename                        Type     Bytes   CRC

Directory PD:<MSDOS.PACKET>
MBBIOS.ARC                      BINARY   32256  E594H

    ---Bob/N3CVL

[This is the file README from RUN40.ARC]

     The W0RLI / VE3GYQ C BBS

Release notes for C BBS Version 4.0 - 10/1/87

See the file CHANGES.MB for details on new features included
and bugs fixed in this release.

               *** Warning ***

If you are now running a version prior to 4.0 you must convert
your existing message and user files to version 4 format.

First, backup all files in the directory used by the MailBox.
In case something goes wrong, you will be able to restore
everything to where it was without loss of messages.

The conversion from earlier versions to version 4 is done by MBCONV.
Set the default directory to the directory containing the
MAIL.DAT and USER.DAT files. Then run MBCONV.

If you are running a version prior to 3.0 you must first make
certain that the message text has been moved to individual files.
Do this by executing the GF command.

             *** Note ***

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

         *** Getting started ***

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".
WB2MNF is working on it, some documentation has been prepared
by VE4AFO and N0AN, KB6IRS has volunteered time for editing.

If you would like to help prepare either the sysops documentation,
or the user documentation, please let me (or WB2MNF) know - we can
use all the help we can get. I don't write good English ... so
I'm not much help ...

... Hank

[This is an excerpt from the CHANGES.MB file from RUN40.ARC]

    Changes from V3.5 to V4.0    Starting 9/19/87

Fixed bug: download to a tnc did not return to terminal mode properly.
Removed 256 character limit on greeting message.
Added message state "H" (held), hold list, LH command.
Much better handling of disconnect of "unhappy" tnc (from ve3gyq).
Various bugs that showed up in 3.5 are fixed.
Yet another change to DD timeslice handling.
Message and User files version 8

    Changes from V3.4 to V3.5    Starting 9/7/87

Sent to VE3GYQ 9/18/87
Added new message state O for "old".
Param in config.mb, how many days old is "old".
Messages check for "old" once per day.
KO will kill all "old".
LO will list all "old".

Allow "/EX" to be used as end of file or message.
Added reverse forwarding a la wa7mbl.
Added RH (Read with Headers). Removed display of headers in normal read.
Improved the DoubleDOS "free time" switching.
When forwarding, sometimes data was sent to tnc when it was in cmd: mode.
Message to WP now generated only once per day.

    Changes from V3.3 to V3.4    Starting 8/17/87

PRTLOG reports time spent forwarding.
New log items for start and end of forwarding.
Initialization now disconnects any connected tnc.
Corrected bug in GM/GU when .BAK on different drive than .DAT
Added @ BBS translation list to config.mb per k0kby.
Ignore *** DISCON if port idle. Cured wrong "port in use" error.

    Changes from V3.2 to V3.3    Starting 6/19/87

Do not show "cc:" if all have been forwarded.
Fixed forward to "*" so that owners msgs stay put.
Cured "console times out after terminal mode."
Added "@FILE" indirection to fwd.mb.
Abort forward with control-F. Zaps the connect as soon as possible.

27-Oct-87 16:52:03-EST,1207;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 16:52-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 13:25:14 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 13:25:03 EST
Message-Id: <[e-mail]>
Received: from relay2.cs.net by RELAY.CS.NET id ad01190; 27 Oct 87 12:57 EST
Received: from bgsu.edu by RELAY.CS.NET id bg14025; 27 Oct 87 12:48 EST
Received: by andy.bgsu.edu (5.51/3.1)
        id AA28243 ; Mon, 26 Oct 87 13:22:17 EST
Date: Mon, 26 Oct 87 13:22:17 EST
From: Louis Graue <[e-mail]>
To: [e-mail]
Subject: Re:  Just getting started
Cc: [e-mail], [e-mail],
    [e-mail]
Mmdf-Warning:  Parse error in original version of preceding line at RELAY.CS.NET

Yes lots of activity on HF and plenty of DX stations on the 20 meter band
at between 14100 and 14110.  Some DX stations have automated stations on
packet so that you can connect and get reply even if nobody is home.
You find them by watching for their beacons.

27-Oct-87 18:47:17-EST,1207;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 18:47-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 13:25:14 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 13:25:03 EST
Message-Id: <[e-mail]>
Received: from relay2.cs.net by RELAY.CS.NET id ad01190; 27 Oct 87 12:57 EST
Received: from bgsu.edu by RELAY.CS.NET id bg14025; 27 Oct 87 12:48 EST
Received: by andy.bgsu.edu (5.51/3.1)
        id AA28243 ; Mon, 26 Oct 87 13:22:17 EST
Date: Mon, 26 Oct 87 13:22:17 EST
From: Louis Graue <[e-mail]>
To: [e-mail]
Subject: Re:  Just getting started
Cc: [e-mail], [e-mail],
    [e-mail]
Mmdf-Warning:  Parse error in original version of preceding line at RELAY.CS.NET

Yes lots of activity on HF and plenty of DX stations on the 20 meter band
at between 14100 and 14110.  Some DX stations have automated stations on
packet so that you can connect and get reply even if nobody is home.
You find them by watching for their beacons.

27-Oct-87 20:50:11-EST,2134;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 20:50-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 15:02:50 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 15:01:54 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA20970; Tue, 27 Oct 87 12:00:07 PST
Return-Path: <seismo!uunet!mcvax!enea!kuling![e-mail]>
Message-Id: <[e-mail]>
Date: 26 Oct 87 14:03:36 GMT
From: seismo!uunet!mcvax!enea!kuling![e-mail] (Anders Klemets)
To: [e-mail]
Subject: Information exchange (Was: Packet w/out TNC on a 64)
Keywords: Digicom, Gateway
References: <[e-mail]>

People over here have been using the DIGICOM>64 software during more than
one year now. I know of very few hams who are using a CBM-64 with an ordinary
hardware TNC. (Or at least very few who openly admit it.) The DIGICOM>64
software has more features than a TAPR TNC, for instance enhanced monitoring
functions and remote control of the computer and "TNC" from the radio.

QST had an article this spring about different TNC's and a couple of
software-TNC's. But I was rather surprised about that not a word was
mentioned about the West-German Digicom software. I suppose the author simply
didn't know about it.

More than a year ago somebody used to post some very informative Gateway
bulletins on the net. I, and I think many other non American hams
appreciated them a lot. I suspect that there must be other things going on
in the U.S. regarding packet than just TCP/IP, but we never hear about it
nowadays.
It would be great if somebody would care to start posting the Gateway
bulletin again. Maybe we could even keep you Americans informed if something
interesting is developed over here and we would all benefit from this
information exchange.

--
    Anders Klemets, Sikvagen 51, S-135 41 Tyreso, SWEDEN
    UUCP/ARPA:      [e-mail]
            [e-mail]
    Phone:          [phone]
    Packet:         SM0RGV @ SK0TM


27-Oct-87 21:38:51-EST,1415;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 21:38-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 14:58:11 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 14:57:46 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA20906; Tue, 27 Oct 87 11:58:44 PST
Return-Path: <ihnp4!homxb!homxc![e-mail]>
Message-Id: <[e-mail]>
Date: 26 Oct 87 21:35:30 GMT
From: ihnp4!homxb!homxc![e-mail] (J.NAGY)
To: [e-mail]
Subject: Software for PK-232

I know that a number of netnews readers are using the
PK-232 with various  computers and I wonder what kind
of software you are using. Two packages which appear
popular are:
    1) AEA's own PakRatt software.
    2) G3ZCZ pk232com package (available on CompuServe)

I'd like to hear from people who have used these packages.
What is unique about them that you particularly like?  Is
there some outstanding feature that you find particularly
useful, or that makes operating the digital modes particularly
convenient?  If there is some reader in the Central New Jersey
area who could demonstrate this (or some prefered) software
to me, I would be very grateful.

Thanks and 73,


Jonathan Nagy NK2D
{ihnp4|allegra|harvard}!homxc!jdn
[phone]


27-Oct-87 22:48:04-EST,1076;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 27 Oct 87 22:48-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 20:31:40 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Tue, 27 Oct 87 20:31:13 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA24318; Tue, 27 Oct 87 17:31:52 PST
Return-Path: <ihnp4!homxb!homxc![e-mail]>
Message-Id: <[e-mail]>
Date: 27 Oct 87 13:39:20 GMT
From: ihnp4!homxb!homxc![e-mail] (J.NAGY)
To: [e-mail]
Subject: TERMINAL SOFTWARE
Keywords: AMTOR/PACKET/RTTY/CW, Software, PRO-COM

I have heard of a program for IBM PC/compatibles called
PRO-COM. Has anyone had experience with this software?
I would like to obtain a copy of the operating manual,
and, if possible see a demo. Does anyone know if this
software is available from a PBBS system or Compuserve?

Thanks & 73,

NK2D

Jonathan Nagy
{ihnp4|allegra|harvard}!homxc!jdn
[phone]


28-Oct-87 22:59:29-EST,1861;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 28 Oct 87 22:59-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 28 Oct 87 18:49:06 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Wed, 28 Oct 87 18:48:18 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA03565; Wed, 28 Oct 87 15:17:48 PST
Return-Path: <linus!raybed2!cvbnet![e-mail]>
Message-Id: <[e-mail]>
Date: 27 Oct 87 14:43:51 GMT
From: linus!raybed2!cvbnet![e-mail] (Gary Delong)
To: [e-mail]
Subject: Re: PBBSes and TCP/IP
References: <[e-mail]>

In article <[e-mail]>, [e-mail] (Glenn S. Tenney) writes:
>
> Now the questions:
> 1. W0RLI software *sucks* compared to FIDO/OPUS.  Is there any
>    decent PBBS software out there?  Where?
> 2. Is there any existing software to run with the TCP/IP code
>    that would let people use it as a BBS (ie. conferencing)?
>    Ideally, any readnews software (I mean, netnews is better than
>    W0RLI by a looong shot!)?
>
> Were these stupid questions or what?
> tnx
> Glenn Tenney
> AA6ER

No, Glenn, they aren't stupid questions, just phrased in such a way that anyone
who spent thousands of hours of his own time developing code that is given away
would have to be pissed.

I think you might have better luck it you approched it:

    I'd really like to get together with someone to work on a
    FIDO/OPUS approch to packet.

Remember, W0RLI is a person, not a product.

73s

--
   _____
  /  \    /   All spelling errors        |       Gary A. Delong, N1BIP
  |   \  /    intentional for testing    |       linus!raybed2!cvbnet!gdelong
  \____\/     rn spellcorrector v1.02A.  |       [phone] x5232


29-Oct-87 02:33:39-EST,1136;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 29 Oct 87 02:33-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 29 Oct 87 00:03:12 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Thu, 29 Oct 87 00:02:46 EST
Message-Id: <[e-mail]>
Received: from relay2.cs.net by RELAY.CS.NET id ae15453; 28 Oct 87 18:51 EST
Received: from pitt by RELAY.CS.NET id ae22816; 28 Oct 87 18:48 EST
Received: by pitt (5.51/4.7)
    id AA27310; Wed, 28 Oct 87 10:27:30 EST
From: Bob Hoffman <[e-mail]>
To: [e-mail]
Date: Wed, 28 Oct 87 10:27:26 EDT
Subject: Information exchange
X-Mailer: ELM [version 1.2a]

Anders Klemets writes:
> It would be great if somebody would care to start posting the Gateway
> bulletin again.

For quite some time, Gateway has not been available electronically.
This may have been due to staff changes at the ARRL.  Recently, I read
on CompuServe's HamNet that they will be posting them again soon.
If so, and if I get them, I will post them here.

    ---Bob.

30-Oct-87 21:18:53-EST,1711;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 30 Oct 87 21:18-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 18:09:42 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 18:09:28 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17928; Fri, 30 Oct 87 15:10:40 PST
Return-Path: <labrea!Lindy![e-mail]>
Message-Id: <[e-mail]>
Date: 30 Oct 87 16:39:07 GMT
From: labrea!Lindy![e-mail] (Andy Valencia)
To: [e-mail]
Subject: New packet BBS
Keywords: packet, BBS


    I have recently brought up a multi-user packet system running on
MINIX.  It's available in the San Francisco bay area via n6mpw-1.  It allows
an arbitrary number of people to be signed on concurrently, each talking
to his(her) own processes.  I currently have a mail system, a discussion system
(ala net news), on-line help, and an outbound call-maker.  In the next week
I plan to polish up the mail interface so that W0RLI-type mail can be
handled, and I am just about done with a client for the outbound-call facility
to allow mail to be forwarded out.  MINIX is actually a hideous platform
for this (lost interrupts, bugs, crashes), and I am seriously looking at
moving to SCO XENIX or Microport UNIX (Microport might be interested in donating
a copy to the cause, but we'll see....)  My plan is to hack this all into
a stable, supportable state, then release it to the public domain.

    So, if you have the time, give me a connect on 145.09!

                73's Andy Valencia WB6RRU

cmd:c wb6rru v n6mpw-1
    Do it now!


30-Oct-87 22:35:20-EST,2093;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 30 Oct 87 22:35-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 18:08:11 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 18:07:59 EST
Received: by june.cs.washington.edu (5.52.1/6.10)
    id AA17874; Fri, 30 Oct 87 15:09:04 PST
Return-Path: <rutgers!nysernic!itsgw!batcomputer![e-mail]>
Message-Id: <[e-mail]>
Date: 30 Oct 87 12:20:56 GMT
From: rutgers!nysernic!itsgw!batcomputer![e-mail] (Mitch Collinsworth)
To: [e-mail]
Subject: Re: Hurtin' TNC
Keywords: GLB TNC-2A, TNC2 clone, doesn't transmit
References: <[e-mail]>

Last nite I played around some more with the GLB after posting the
problem.  It had been several days since I'd last tried it, so I didn't
remember all the details perfectly.  Here's some more info.

The DCD LED is on ALL THE TIME.  I guess this would explain why it
refuses to transmit.  When I swap in the MFJ 1270B (using the same
transceiver and cables, different power supply) its DCD LED only lights
when it hears a packet.  When I take the receive audio connector out of
the receiver so I can listen to the receiver with the speaker, I find
that when the GLB is powered on, there is a "carrier" on the channel
(i.e. something is breaking the squelch).  When I turn the GLB off, it
goes away.  This happens even when the receive and transmit audio cables
are plugged into the MFJ (i.e. none in GLB).  It is obviously generating
some kind of noise that the receiver (IC2AT on external antenna) is
picking up.  Could this same noise be what is holding DCD down? up? whatever?
I tried setting FULLDUP ON and interestingly, it still wouldn't transmit.
Does this mean DCD is not what is keeping it from transmitting?
Yesterday someone suggested checking the XMITOK parameter.  It is ON,
so that's not the problem.

-Mitch Collinsworth, K2VD
 [e-mail]


31-Oct-87 00:56:19-EST,4196;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 31 Oct 87 00:56-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 21:58:40 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Fri, 30 Oct 87 21:53:33 EST
Message-Id: <[e-mail]>
Received: from amc1 by AMC-HQ.ARPA id ac00168; 30 Oct 87 7:49 EST
Date:     Fri, 30 Oct 87 7:22:15 EST
From: "D. H. Bennett, AMCRM-FTM"  <[e-mail]>
To: [e-mail],
    [e-mail]
Subject:  FOR YOUR INFORMATION - BEWARE!!!!!!!!

The following messages were sent to me on packet radio and I think all
should read and beware!!!!!  If its true then I will no longer be placing
my USA-PKT files on CompuServe and I will cancel my account.
====================================================================
13 Sep 86  15:34:01
From: Eric Larson
To:   All
Subj: CI$
OK GUYS - FLAME ON!!
The following letter appeared on a Fido BBS I occasionally call:
  After only nine days of service to Macintosh, Amiga, and Atari
ST users, the MouseTrap BBS is officially shut down. Why???
  When the system first went into service, I left "ads" on just
about every BBS I could call, as well as on CompuServe and GEnie.
Apparently, Neil Shapiro (the coordinating sysop of the Mac user
group on CompuServe) called the system and noted that one of the
services offered by the board was downloads of Public Domain
software acquired from users,CompuServe and GEnie. As you and I
well know, this is common practice -I'd be willing to bet that
90% of all the software in BBS download sections and User Group
Public Domain Libraries is obtained from either CompuServe, the
Source or GEnie.
  On September 11, I received a registered letter in the mail
from the law firm of Bricker and Eckler, representing CompuServe.
The letter stated that by allowing my users to download Public
Domain software which I had acquired from CompuServe, I was
infringing on their copyright as well as violating the terms of
the customer agreement.  I was told that if I did not cease and
desist all activity immediately,I would be subject to further
legal action including possible civil remedies or criminal
penalties.
This got my attention!  I shut down my BBS, which I had spent a
great deal of time and money on preparing. I had planned on
running a BBS as a service for computer users, not as an exercise
in copyright law. What I am REALLY concerned about is this:what
implications does this have for other distributors of Public
domain software?  The "letter of the law" as stated by CompuServe
maintains that ANY REPRODUCTION OR PUBLISHING  of information
obtained through their service is illegal, EVEN IF THE FILES ARE
IN THE PUBLIC DOMAIN!  This implies that every time one of us
downloads a public domain program from CompuServe and gives a
copy of it to a friend, we are breaking the law.  This means
that every time a User Group librarian copies a program acquired
from CompuServe and gives it to a club member, he or she is
breaking the law. As noted, I have shut down my system.  I've
also cancelled my subscription to CompuServe so that they'll be
sure that I'm not "Stealing" Public Domain programs from them.
I would be more than happy to discuss thissituation with any
other Sysop or concerned user.
  Steve Sande - Former Sysop, The MouseTrap BBS.
I'd encourage people to reconsider use of Compuserve.
-FLAME OFF
--
 * Origin: Sit_UBU_Sit (U.S. Robotics) - Lombard, IL (115/500)
From: Brad Hicks
To:   Eric Larson
Subj: CompuSlime
Re:   CI$
They mean it, too.  I take it you DO know who owns CompuServe, don't you?
(For those of you who don't: does the name H&R Block ring a bell? Is there
anybody in the United States with MORE lawyers on retainer but not doing much
this time of year?)
......(edited)
You see, there is no such thing as "public domain"
on CIS, as your user agreement EXPLICITLY GIVES THEM OWNERSHIP of anything you
upload there, and holds you LIABLE if you upload something that they can't
own!





31-Oct-87 10:05:04-EST,4196;000000000000
Received: from EDDIE.MIT.EDU by DEEP-THOUGHT.MIT.EDU via Chaosnet; 31 Oct 87 10:05-EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 31 Oct 87 03:36:37 EST
Received: by EDDIE.MIT.EDU with sendmail-5.45/4.7 id <[e-mail]>; Sat, 31 Oct 87 03:33:56 EST
Message-Id: <[e-mail]>
Received: from amc1 by AMC-HQ.ARPA id ac00168; 30 Oct 87 7:49 EST
Date:     Fri, 30 Oct 87 7:22:15 EST
From: "D. H. Bennett, AMCRM-FTM"  <[e-mail]>
To: [e-mail],
    [e-mail]
Subject:  FOR YOUR INFORMATION - BEWARE!!!!!!!!

The following messages were sent to me on packet radio and I think all
should read and beware!!!!!  If its true then I will no longer be placing
my USA-PKT files on CompuServe and I will cancel my account.
====================================================================
13 Sep 86  15:34:01
From: Eric Larson
To:   All
Subj: CI$
OK GUYS - FLAME ON!!
The following letter appeared on a Fido BBS I occasionally call:
  After only nine days of service to Macintosh, Amiga, and Atari
ST users, the MouseTrap BBS is officially shut down. Why???
  When the system first went into service, I left "ads" on just
about every BBS I could call, as well as on CompuServe and GEnie.
Apparently, Neil Shapiro (the coordinating sysop of the Mac user
group on CompuServe) called the system and noted that one of the
services offered by the board was downloads of Public Domain
software acquired from users,CompuServe and GEnie. As you and I
well know, this is common practice -I'd be willing to bet that
90% of all the software in BBS download sections and User Group
Public Domain Libraries is obtained from either CompuServe, the
Source or GEnie.
  On September 11, I received a registered letter in the mail
from the law firm of Bricker and Eckler, representing CompuServe.
The letter stated that by allowing my users to download Public
Domain software which I had acquired from CompuServe, I was
infringing on their copyright as well as violating the terms of
the customer agreement.  I was told that if I did not cease and
desist all activity immediately,I would be subject to further
legal action including possible civil remedies or criminal
penalties.
This got my attention!  I shut down my BBS, which I had spent a
great deal of time and money on preparing. I had planned on
running a BBS as a service for computer users, not as an exercise
in copyright law. What I am REALLY concerned about is this:what
implications does this have for other distributors of Public
domain software?  The "letter of the law" as stated by CompuServe
maintains that ANY REPRODUCTION OR PUBLISHING  of information
obtained through their service is illegal, EVEN IF THE FILES ARE
IN THE PUBLIC DOMAIN!  This implies that every time one of us
downloads a public domain program from CompuServe and gives a
copy of it to a friend, we are breaking the law.  This means
that every time a User Group librarian copies a program acquired
from CompuServe and gives it to a club member, he or she is
breaking the law. As noted, I have shut down my system.  I've
also cancelled my subscription to CompuServe so that they'll be
sure that I'm not "Stealing" Public Domain programs from them.
I would be more than happy to discuss thissituation with any
other Sysop or concerned user.
  Steve Sande - Former Sysop, The MouseTrap BBS.
I'd encourage people to reconsider use of Compuserve.
-FLAME OFF
--
 * Origin: Sit_UBU_Sit (U.S. Robotics) - Lombard, IL (115/500)
From: Brad Hicks
To:   Eric Larson
Subj: CompuSlime
Re:   CI$
They mean it, too.  I take it you DO know who owns CompuServe, don't you?
(For those of you who don't: does the name H&R Block ring a bell? Is there
anybody in the United States with MORE lawyers on retainer but not doing much
this time of year?)
......(edited)
You see, there is no such thing as "public domain"
on CIS, as your user agreement EXPLICITLY GIVES THEM OWNERSHIP of anything you
upload there, and holds you LIABLE if you upload something that they can't
own!