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

Text File | 1993-12-31 | 112.8 KB | 2,661 lines

1-Aug-89 15:16:39-MDT,12603;000000000000
Return-Path: <[e-mail]>
Date: Tue,  1 Aug 89 15:00:36 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #183
To: [e-mail]

PACKET-RADIO Digest         Tue,  1 Aug 89       Volume 89 : Issue 183

Today's Topics:
         High speed packet questions (2 msgs)
              Need info on packet radio
             RFI from EGA display
            rs232 control for ICOM radios
           TX Holdup?  G8BPQ, RLI 10.10, MFJ-1270B
            wanted: kiss ONLY tnc
               Wanted ka9q Unix packet
----------------------------------------------------------------------

Date: 28 Jul 89 14:23:58 GMT
From: dscatl!kd4nc![e-mail]  (Gary Coffman)
Subject: High speed packet questions

In article <[e-mail]> [e-mail] (Ari Husa OH8NUP) writes:
>
>We are planning to put up a 56 kbps TCP/IP packet radio network. Now
>we have now pretty much come to the point where we must make the
>decision of ordering (and building) all the necessary equipment.
>
>Which is the best interface for IBM PC-compatible machines?  Should we
>use the Pac-Comm PC-100 (is it supported by KA9Q NET software yet?),
>or something else? Opinions, please!
>
>Thank You in advance, 73
>
>        Luru

Here in Atlanta we are still using a chopped up TNC2 on all our backbone
links. We are experimenting with several plugin cards, but are sticking
with the proven TNCs until we are sure we have something better working.

My opinion is that we really need some intelligence on any plugin we
wind up using. The need to off load the main cpu is very real when your
switch is attempting to service multiple high speed links. With the TNC
hanging on the modem, most any computer that can run KA9Q will be able
to use 56k. I am eagerly awaiting Mike's totally awesome board. It sounds
like it will be a very good solution for the PC world.

The DRSI card seems adequate if you only need to drive one 56k, but if
you need to switch multiple links, it will probably prove unfit for
the job.
73 Gary KE4ZV

------------------------------

Date: 31 Jul 89 17:12:30 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: High speed packet questions

>Which is the best interface for IBM PC-compatible machines?  Should we
>use the Pac-Comm PC-100 (is it supported by KA9Q NET software yet?),
>or something else? Opinions, please!

The driver for the PC-100 has not, to my knowledge, ever been completed or
tested.  For 56kb operation, KA9Q has written a high-speed driver for the DRSI
PCPA card, that works fairly well.

>As far as I recall, Mike Chepponis (K3MC) is working on a better
>interface. I wonder when that would become available?  And when would
>the software support it?

This fall sometime.  Negotiations are reportedly underway for commercial
production of the card.  I am not free to provide any further details.  The
PCPA card is a reasonable, if slow, alternative for the next 4-6 months.

>Another point of interest would be the possibility to link the system
>to other computers than IBM PC-line. Is it possible at all, apart from
>the old, painfully slow TNC's?

All you need is 56kb HDLC, with the ability to have the interface clocked by
the modems, assuming you plan to use the WA4DSY units.  The Macintosh does not
bring out all the lines needed, but solutions are being investigated.  For
other machines, you'll need to provide or locate an HDLC interface, write a
driver, or just use a TNC that's been modified.

73 - Bdale, N3EUA

------------------------------

Date: 1 Aug 89 17:50:29 GMT
From: usna![e-mail]  (Tim G. Smith )
Subject: Need info on packet radio

Hi- I was hoping that some one could provide me with some beginner
info on packet radio.

I know a little bit about packet radio and think I might be interested
in getting involved with it but need some more info. I really do not
know very much about amateur radio so responses should explain things
in a manner that a neophyte can understand. I do have plenty of
experience with tcp/ip and local/wide area networks so you don't have
to go too far in depth about tcp/ip although I am at a loss to know
how packet radio handles routing (does anyone run gated over packet
radio? Is there an official "core" to the packet net?).

Sorry if all of this has been asked before. Feel free to answer here
or send email- whichever you feel is more appropriate.

I would like info about the following:

1) What sort of license is required? I have heard someone mention that
the FCC is considering eliminating the Morse Code requirement for a
license- is this true? What would I need to do to get a license?

2) What sort of data speeds are possible? I was under the impression
that 300/1200 bps was the max speed but I have heard folks mention
56kb speeds.

3) What is the range of a typical transmitter? I am thinking of
linking two sites with packet radio instead of slip or some other
PTP over telephone.

4) How extensive is the packet bacbone? Would I be able to send
data across Maryland? The east coast? Coast to coast?

5) What sort of equipment do I need. I could use a description of all
the hardware from the serial port of my machine to the destination
computer's serial port.

thanks all,
    Tim Smith       (formerly of the US Naval Academy)
US mail:US Army, BRL                            E-mail:
    SLCBR-SE                                internet:[e-mail]
    Aberdeen Proving Grounds, MD 21005-5066 uucp    :...!uunet!brl!tsmith
MaBell :[phone] (or 6808)
Autovon: 298-6678


------------------------------

Date: 31 Jul 89 00:21:01 GMT
From: swlabs![e-mail]  (Jack Bonn)
Subject: RFI from EGA display

I have been encountering RFI while checking out some HF packet.

I just found where my RFI problem is.  The cable going to the Enhanced
Color Display (IBM's EGA monitor) is very noisy.  I notice that it is
the old type; it doesn't have an RFI trap on the video cable near the
display adaptor.  I really don't want to scrap the display and buy a new
one.

Does anyone know what is in those RFI traps?  Are they just wrapping
the wires around ferrite beads?  Or are they putting all the wires around
a toroid?  Are the RFI traps for displays available separately?  What
other things (bypass caps, etc) would be worth trying?

By the way, 10 meters has been booming in from South America.  Check
out 28,100.8 kHz.
--
Jack Bonn, KA1SMW, <> Software Labs, Ltd, Box 451, Easton CT  06612
uunet!swlabs!jack (UUCP)        [e-mail] (INTERNET)

------------------------------

Date: 31 Jul 89 15:11:38 GMT
From: bbn.com![e-mail]  (Martin Grossman)
Subject: rs232 control for ICOM radios

After reading article in August '89 "73 Amateur Radio" page 34
"Control Your Rig from a PC" my brother KA1PPG (without usenet access)
asked if its do-able on his rigs.  I've read both manuals on his
ICOM IC-740 and IC-251.  It seams not possible on the 740 since the
only leads that are come close are:

pin #           Description

11      Input for TRANSVERTER control.  When 8 Volts DC applied, the
    set can operate with a transverter.

12      Output reference voltage for band switching
13**    Output for external band switching

It seams do-able on his 251 because it has the following connections
on the ACC connector:

pin #           Description

16      Control signal (DBC) input terminal for external control
17      NC
18      NC
19      Control signal (DV) output terminal for external control
20      Control signal (RT) input terminal for external control
21      Data signal (DB1) input/output terminal for external control
22      Data signal (DB2) input/output terminal for external control
23      Data signal (DB4) input/output terminal for external control
24      Data signal (DB8) input/output terminal for external control


Now the article mentions that some radios have an input and output
that are 5V rs232 signals but neither of these do.

So can someone explain (or point me in the right direction) how to use
pins 16-24.

PS I can easily make my brother a board like mine that uses an 8255 PPI
   chip for digital control, if thats whats needed.

------------------------------

Date: Sun, 30 Jul 89 14:57 CDT
From: <[e-mail]> (Steve Hicks, 845-8964/764-7924)
Subject: TX Holdup?  G8BPQ, RLI 10.10, MFJ-1270B

Howdy....

I am having difficulty running the G8BPQ software under RLI 10.10.  If I turn
on MTX I can see transmitted packets going to my MFJ1270B 1.6.1, but the TNC
will hold the packets for up to 5 seconds before transmitting them.  The TNC
is, of course, running in KISS mode.  So if a user tries to connect to the BBS
or NODE, he may send five connects which will be followed by five responses
from the computer, but the TNC ends up holding them and transmitting them all
at once some time later.   I suspect a problem in the TNC software like a
poor choice of PERSIST or SLOTTIME, but I have no control over those
parameters from G8BPQ.  The software runs better on my KPC-2 (I am assuming
the default for these parameters are better suited to my particular
application)

What I'm looking for is something like:  Information that a new version of
    G8BPQ is out that sets these software parameters from the computer for me
    (I am running 3.20); some kind of quick fix C/BASIC program or something
    I can compile and run in my startup that will pre-load the values for
    me; some insight which demonstrates my misunderstanding of the problem
    and a new way of correcting it.  If needed I can enclose a copy of
    my current parameters in G8BPQ, but I feel that the problem has been
    traced to the TNC, rendering these parameter values irrelevant.

73/Stephen Hicks

        Packet:   SYSOP @ W5AC / WD5EMG @ 77840
INTERnet/SESQUInet:   S1H1420.TAMSIGMA.TAMU.EDU (128.194.1.1)
        BITnet:   S1H1420@TAMSIGMA
        THEnet:   SUMMA::S1H1420
      MCI Mail:   SHICKS
           CSI:   73747,676

------------------------------

Date: 31 Jul 89 17:08:13 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: wanted: kiss ONLY tnc

Any TNC-2 clone (MFJ 1270B, Paccomm tiny and micropower, etc...) can be fitted
with a KISS-Only ROM using the bits included in TNC_TNC2.ARC of the KA9Q
distribution.  This is the way I run my station.

There are similar bits for TNC-1 clones, and the VADCG/ASHBY boards.

Bdale, N3EUA

------------------------------

Date: 31 Jul 89 17:13:49 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: Wanted ka9q Unix packet

>I think what I am looking for Is KA9Q's package, but I am unable to download
>it from anywhere due to the fact that I can only use KERMIT.

Maybe this will help:

+------------------------------------------------------------------------------+
    HOW TO ACCESS THE WB3FFV AMATEUR RADIO TELEPHONE BBS !!!


 I have placed a BBS system on-line that is mainly oriented towards the
Amateur Community (but there is other stuff on-line). As of now I have not
attempted to promote this system any place except in the amateur channels
(PACKET, USENET, & word of mouth), and will continue under this policy, as
I hope to keep it oriented toward amateur radio. The various software for
UP/DOWNload is available via telephone dialup and Packet TCP/IP, and through
user support I hope to keep the latest and greatest ham software on-line.
Below is the information that is needed in order to access the BBS via
Telephone -or- TCP/IP, please pass it around to as many ham's as possible.

 System Name: WB3FFV
 Login: bbs
 Number: (301)-335-0858 -- 1200 & 2400 (Non-MNP)
 Number: (301)-335-1955 -- 2400 (MNP), 9600 & 19200 (PEP)
 Data Settings: 8 Bits, NO Parity, 1 Stop Bit
 Times: 24hrs/365days  (except for routine maintenance)
 Software: XBBS  (UNIX/Xenix Multiuser BBS)
 IP Address: 44.60.0.1 {wb3ffv.ampr.org}  [for FTP access on 145.550 mhz ONLY]
 Misc. Info: Machine is an 80386 computer running UNIX V.3 and features 300+
         meg of on-line storage. Most transfer protocols are available!!




73 - Bdale, N3EUA

------------------------------

End of PACKET-RADIO Digest V89 Issue #183
*****************************************
 4-Aug-89 10:16:05-MDT,10589;000000000000
Return-Path: <[e-mail]>
Date: Fri,  4 Aug 89 10:00:17 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #184
To: [e-mail]

PACKET-RADIO Digest         Fri,  4 Aug 89       Volume 89 : Issue 184

Today's Topics:
          Need info on packet radio (2 msgs)
             RFI from EGA display
           TX Holdup?  G8BPQ, RLI 10.10, MFJ-1270B
           Wanted ka9q Unix packet (2 msgs)
----------------------------------------------------------------------

Date: 4 Aug 89 10:31:38 GMT
From: cdp![e-mail]
Subject: Need info on packet radio

>   Hi- I was hoping that some one could provide me with some beginner
>   info on packet radio.
>
>   I know a little bit about packet radio and think I might be interested
>   ...
>   1) What sort of license is required? I have heard someone mention that
>   ...
>   2) What sort of data speeds are possible? I was under the impression
>   ...
>   3) What is the range of a typical transmitter? I am thinking of
>   ...
>   4) How extensive is the packet bacbone? Would I be able to send
>   ...
>   5) What sort of equipment do I need. I could use a description of all
>   ...
>
>   thanks all,
>       Tim Smith       (formerly of the US Naval Academy)
>   US mail:US Army, BRL                                E-mail:
>       SLCBR-SE                                internet:[e-mail]
>       Aberdeen Proving Grounds, MD 21005-5066 uucp    :...!uunet!brl!tsmith
>   MaBell :[phone] (or 6808)
>   Autovon: 298-6678


 I would love to receive this information also.  This is not the first
 time someone has made pretty much the same request.  Will one of you
 knowledgeable and articulate packet radio folks please write up a
 summary of these seemingly elementary but elusive facts?  It would be
 greatly appreciated.

 thanks,
 jim

 Jim Wampler
 ...uunet!pyramid!cdp!jim
 ...hplabs!cdp!jim
 [e-mail]

------------------------------

Date: 4 Aug 89 13:35:29 GMT
From: unccvax![e-mail]  (John Covington WN4BBJ)
Subject: Need info on packet radio

In article <241300001@cdp>, [e-mail] writes:
>
>
> >   Hi- I was hoping that some one could provide me with some beginner
> >   info on packet radio.
> >
> >   I know a little bit about packet radio and think I might be interested
> >   ...
> >   1) What sort of license is required? I have heard someone mention that
> >   ...
You need at least a Novice class Amateur Radio license to operate packet
on 222 MHz, at least a Technician class to operate on 144 MHz and a
General class license to operate packet on HF bands.
> >   2) What sort of data speeds are possible? I was under the impression
> >   ...
Most HF packet is at 300 baud, most 144 MHz packet is at 1200 baud but
many people are experimenting with speeds of 2400, 4800 and 9600 baud.
There is some 56KB stuff going on in the higher bands, but that is
usually done by clubs and packet groups, not individuals.

> >   3) What is the range of a typical transmitter? I am thinking of
> >   ...
On VHF you can go as far as 100 miles depending on your terrain.  HF is
limited only by propogation, and you can contact stations in countries
all over the world.
With packet, you can repeat through other stations (called digipeating)
and increase your range on VHF; a form of networking exists which can
allow you to make contact with people in other states.

> >   4) How extensive is the packet bacbone? Would I be able to send
> >   ...
This really depends on what part of the country you live in.  You can
send messages via bulletin boards to virtually the entire country, but
live QSOs have more limited range on VHF.
> >   5) What sort of equipment do I need. I could use a description of all
> >   ...
I will only give a brief description here.  You need a VHF or HF
transmitter, a terminal node controller and a terminal or computer (a
computer really works better since you can store messages for later
use).  If you want to put together a 144 MHz packet station you can
probably do it for less than $250 if you have a computer already.

------------------------------

Date: 4 Aug 89 07:36:22 GMT
From: jupiter![e-mail]  (Phil R. Karn)
Subject: RFI from EGA display

Several months ago I went on a concerted campaign to quiet the monitor
I use with my AT. This is a vanilla monochrome monitor, but I think the
techniques used have general applicability.

1. Find the power supply line between the main circuit board and the
video driver board at the base of the CRT. Replace it with shielded coax,
grounding the shields as appropriate, and bypass the supply line on the
driver board end.  I discovered that this wire was a significant radiator
of RF energy since the video driver board generates a pretty high level
signal.

2. Coat the inside of the cabinet with conductive paint. I used GC Nickel
Print; a single bottle was just enough. (Do this only if the cabinet is
nonconductive, naturally).

3. Sacrifice an old piece of RG-8 coax by removing the outer jacket with
a utility knife and slide out the inner conductor and dielectric.
Use the braid as an outer shield on the video drive cable from your
computer. Be sure to use conductive shells on the connector, and make
sure the braid makes good contact with the connector shell and with the
paint you applied to the inside of the cabinet.

I found these steps were successful in almost completely eliminating RFI
on the HF bands from my generic Taiwanese PC monitor.

Phil

------------------------------

Date: 1 Aug 89 13:52:27 GMT
From: mitel!sce!cognos!dgbt![e-mail]  (Barry Mclarnon )
Subject: TX Holdup?  G8BPQ, RLI 10.10, MFJ-1270B

From article <[e-mail]>, by [e-mail] (Steve Hicks, 845-8964/764-7924):
> Howdy....
>
> I am having difficulty running the G8BPQ software under RLI 10.10.  If I turn
> on MTX I can see transmitted packets going to my MFJ1270B 1.6.1, but the TNC
> will hold the packets for up to 5 seconds before transmitting them.  The TNC
> is, of course, running in KISS mode.  So if a user tries to connect to the BBS
> or NODE, he may send five connects which will be followed by five responses
> from the computer, but the TNC ends up holding them and transmitting them all
> at once some time later.   I suspect a problem in the TNC software like a
> poor choice of PERSIST or SLOTTIME, but I have no control over those
> parameters from G8BPQ.  The software runs better on my KPC-2 (I am assuming
> the default for these parameters are better suited to my particular
> application)
>
  [some text deleted]
>     and a new way of correcting it.  If needed I can enclose a copy of
>     my current parameters in G8BPQ, but I feel that the problem has been
>     traced to the TNC, rendering these parameter values irrelevant.

I think you may be mistaken about this - it sounds very much like this IS
a problem with parameter values.  When you see a monitored outgoing frame
on the screen, it is going to the "virtual" TNC (i.e., the G8BPQ code), not
to the actual TNC.  I'm also using G8BPQ 3.20 with KISS TNCs (and MBL 5.12)
and do not experience the problem you describe, so it is not an inherent
problem with that version.  I do hope that a version will be forthcoming
soon which will permit changing TXDELAY, PERSIST, and SLOTTIME in the KISS
driver.  The TXDELAY in particular is far too long for my application.

I suspect you have a problem with one of the parameters other than the 3
just mentioned.  Check your parameter list for your KISS port, paying
particular attention to the value of RESPTIME.  This should be the 9th
parameter in the list - if there is one missing before it, RESPTIME would
actually be set to the value intended for FRACK.  Since the latter is
nominally 5 seconds, this could explain your 5 second delay before keying
up.  Good luck!

By the way, if you have users who are actually sending 5 connect attempts
in 5 seconds, you'd better tell them to smarten up - *their* FRACK is way
too low!

>
> 73/Stephen Hicks
>

Barry VE3JF

--
Barry McLarnon    Communications Research Center    Ottawa, ON   Canada
UUCP: ...utzoo!bnr-vpa!bnr-rsc!dgbt!barry   INTERNET:  [e-mail]
Compu$erve: 71470,3651     Packet radio:  VE3JF @ VE3JF

------------------------------

Date: 2 Aug 89 03:08:35 GMT
From: n8emr![e-mail]  (Gary Sanders)
Subject: Wanted ka9q Unix packet

In article <[e-mail]> [e-mail] (Bdale Garbee) writes:
>>I think what I am looking for Is KA9Q's package, but I am unable to download
>>it from anywhere due to the fact that I can only use KERMIT.
>
>Maybe this will help:
>
>+------------------------------------------------------------------------------+
>        HOW TO ACCESS THE WB3FFV AMATEUR RADIO TELEPHONE BBS !!!
>

    YOu can also try my BBS.....  The latest and greatest ip code,
rli,mbl code.. lots of files...

    N8EMR's Ham BBS, 614-457-4227 (1200/2400/19.2 telebit,8N1)




--
Gary W. Sanders (gws@n8emr or ...!osu-cis!n8emr!gws), 72277,1325
N8EMR @ W8CQK (ip addr) 44.70.0.1 [Ohio AMPR address coordinator]
HAM/SWL/SCANNER BBS (1200/2400/PEP) 614-457-4227

------------------------------

Date: 3 Aug 89 03:55:45 GMT
From: texbell!ark!lrark![e-mail]  (Rick Mobley)
Subject: Wanted ka9q Unix packet

In article <[e-mail]>, [e-mail] (Bdale Garbee) writes:
> >I think what I am looking for Is KA9Q's package, but I am unable to download
> >it from anywhere due to the fact that I can only use KERMIT.
>
> Maybe this will help:
>
>  System Name: WB3FFV
>  Login: bbs
>  Number: (301)-335-0858 -- 1200 & 2400 (Non-MNP)
>  Number: (301)-335-1955 -- 2400 (MNP), 9600 & 19200 (PEP)

I have this package and have not been able to get it compiled under SCO Xenix
or IBM Xenix either. Has anyone been successful in getting it compiled using
the UNIX switches?

I am not sure I am reaching the NET. Can someone please reply so I know I'm
not just talking to my modem..

73 - Rick

--
Ricky L. Mobley, WB5FDP                                 CIS: 70505,1157
1800 Sanford Drive #4                                   PACKET: WB5FDP @ WD5B
Little Rock, AR 72207                                   XBBS: [phone]

------------------------------

End of PACKET-RADIO Digest V89 Issue #184
*****************************************
 4-Aug-89 15:05:21-MDT,16293;000000000000
Return-Path: <[e-mail]>
Date: Fri,  4 Aug 89 15:00:11 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #185
To: [e-mail]

PACKET-RADIO Digest         Fri,  4 Aug 89       Volume 89 : Issue 185

Today's Topics:
              Gateway 28-Jul-89
             High speed packet questions
----------------------------------------------------------------------

Date: 4 Aug 89 16:49:31 GMT
From: n8emr![e-mail]  (Gary Sanders)
Subject: Gateway 28-Jul-89

==============================================================
|               Relayed from packet radio via                |
| N8EMR's Ham BBS, 614-457-4227 (1200/2400/19.2 telebit,8N1) |
==============================================================

Gateway: The ARRL Packet Radio Newsletter

Stan Horzepa, WA1LOU, Editor

Volume 5, Number 22                                           July 28, 1989

          ARRL COMPUTER NETWORKING CONFERENCE COMING SOON

The 8th ARRL Computer Networking Conference will be held in Colorado
Springs, Colorado, at the Air Force Academy in the Fairchild Hall
conference area on Saturday, October 7.  This year's hosts are Tucson
Amateur Packet Radio (TAPR), Academy Amateur Radio Club, USAFA Cadet Radio
Club, Rocky Mountain Packet Radio Association (RMPRA) and the ARRL.  If you
plan on presenting a paper, please contact Lori Weinberg at ARRL
headquarters for an author's package.  Deadline for receipt of camera-ready
papers is August 28.

The Saturday session at the Academy will include prominent amateurs who are
doing packet-radio development work at the leading edge of technology.
They'll be speaking about the current efforts in the areas of packet-radio
satellites, networking (ROSE, TCP/IP, TexNet), the new version of AX.25,
digital signal processing, high speed packet radio, new packet-radio
hardware and software developments and many other fascinating development
efforts now in progress.

On Saturday evening (6:30-10:00 PM), there will be an opportunity to get
acquainted at a special (and informal) attitude adjustment session at the
conference hotel (the new Colorado Springs Marriott).  A full- size taco
buffet ($2 per pass through the buffet) and cash bar will be available.

There will boncurrent sessions at the conference hotel on Sunday.
The ARRL Digital Committee will be in open session and amateurs are welcome
to sit in.  At the same time, RMPRA will be hosting their annual Packetfest
in a separate meeting room.  The RMPRA Packetfest will feature many of the
prominent amateurs in attendance for the Networking Conference and Digital
Committee meeting.  The Sunday session will be of the tutorial/discussion/
question and answer type of presentation.

Conference headquarters will be the new Colorado Springs Marriott.
Reservations should be made by September 6.  When calling for reservations,
call the Marriott direct at 719-260-1800 (do not use the Marriott 800
number).  Be sure to identify yourself as a member of the "ARRL Networking
Conference."

Other nearby motels:

          Telephone

   Comfort Inn    719-598-6700
   Sheraton Inn   719-598-5770
   Drury Inn      719-598-2500

Colorado Springs Municipal Airport is approximately 10 miles from the
Marriott.  It is served by six national carriers with over 100 flights
daily from six major gateway cities: Chicago, St. Louis, Dalas/Ft.  Worth,
Phoenix, Salt Lake City and Denver.  Airport transportation to and from the
airport will be provided by the Marriott.  Arrival and departure times
should be coordinated with the hotel transportation staff.

For those arriving before 3 PM on Friday, October 6, a conducted tour of
the Air Force Academy has been planned.  The assembly point for this tour
will be announced in a later bulletin and will be posted at the hotel
registration desk.  Private transportation will be used.  If you need a
ride, letyour needs be known when sending in your registration fee.

Registration for the conference includes the conference, one copy of the
8th ARRL Computer Networking Conference proceedings, refreshments
throughout the day, lunch at the AFA Officers Club (transportation will be
provided) and use of the Marriott hospitality room.  There will be no
charge for the tour of the Air Force Academy.  Extra copies of the
conference proceedings will be available.

Upon receipt of your registration, you will be mailed a preprinted Marriott
reservation form and other matrials of interest.  Please indicate if you
would like to be included in the Air Force Academy tour.  For further
information send SASE with your name, call sign, address and telephone
number to:

     Andy Freeborn, N0CCZ
     522 Borrego Dr
     Colorado Springs, CO 80918
     Telephone [phone]

Or you may contact Lori Weinberg, ARRL, telephone [phone],
FAX [phone]



                ROSE GROWS

Version 060289 of the ROSE X.25 Packet Switch release of 2 June 1989 is now
on the following systems: PacComm BBS at 813-874-3078 (file area #1), K4NGC
BBS at 703-680-5970 (file area #17).  This version fixes the LOADER (it
would lose memory space if you disconnected while uploading an application)
and adds a file operation to CONFIGUR.EXE.

               Network Status Report

The following report was filed by Bob Nelson, KB1BD, concerning the status
of ROSE in the New York-New Jersey Metropolitan Area.

Many of us have spent a considerable number of hours working on the network
this spring, fixing bugs, improving RF paths, etc.  We are now adding
additional paths to the network for your packet-radio pleasure.

I know some of you have had a bit of bad luck trying out some of this new
equipment.  Like all beta tests, there are quirks, however, after watching
the code for the last three weeks, it appears that the bugs that were
nipping at our heels all spring have met their fate... that was brought to
them by the exterminator Tom Moulton, W2VY.  The code in all modes appears
to be very stable, therefore, I ask you to try what you have so far and,
hopefully, find some enjoyment in its use.

From the KA2VLP-3 switch, that most of you use to connect to this station,
the following direct PBBS paths from the ROSE network are available. The
connect commands needed to use these PBBSs follow.  Please use the ROSE
path to minimize retries on the channel.

     C KB1BD-4 V KA2VLP-3,609426
     C KD6TH-4 V KA2VLP-3,201744 or
     C KD6TH-4 V KA2VLP-3,212456
     C WB2GTX-4 V KA2VLP-3,201744
     C WA2VXT-4 V KA2VLP-3,609426

If you are using a TNC that uses the old TNC 1 firmware, substitute the
second number in the all number fields with either an "o" or an "i"
depending on whether it is a 0 or 1, for example:

     C KD6TH-4 V KA2VLP-3,2o1744 or
     C KD6TH-4 V KA2VLP-3,2i2456

There are other ports ed by these PBBSs for mail-forwarding which have
been trunked, for the most part, off of the user channels.  This trunking
is occurring via ROSE switches on UHF.

User access ports to the ROSE network are now available at the following
sites:

  Call Sign   Address    Frequency    Location

  N2DSY-3     201744     145.07 MHz   Little Falls, NJ
* N2ELC-3     201663     145.09 MHz   Lake Hopatcong, NJ
  KA2VLP-3    609426     145.07 MHz   Hightstown, NJ
  N2EVW-7     609530     221.01 MHz   Trenton, NJ
  KD6TH-6     212456     145.07 MHz   New York City, NY
* N2EVW-8     609883     221.11 MHz   Trenton, NJ
  WA3YRI-3    609261     145.07 MHz   Mt Holly, NJ

* Under construction at time of this writing; may not yet be available for
use.

KD6TH-3 on 221.11 MHz in New York City will be converting from its standard
digipeater configuration to a ROSE switch very shortly .

If you would like to contact someone who has access to any of these
switches, invoke the following:

     C W2XXX-Y V N2VVV-T,609426

where W2XXX-Y is your call sign and SSID and N2VVV-T is the switch call
sign and SSID that the other person can access.

Access to NET/ROM is also available.  We are currently accessing it on
221.01 MHz and the channel is very crowded.  Access to other frequencies is
currently in the works, but until they are available, I offer the following
suggestions.

To access the NET/ROM network, use the following connect sequence:

     C WB2DRD-3 V KA2VLP-3,609530

The ROSE network will then set up a connection tothat station.  Remember,
although it says you are "connected" when using ROSE, you are only
connected to the virtual circuit, which may actually be in the process of
completing a connection.

After you make your connection and you know which node you wish to connect,
enter the following:

     C W3IWI-11

where W3IWI-11 is the target node.

If you are not sure which node to connect to, type:

     NODES

To check if you are connected to a NET/ROM node, type:

     INFO

If you have made your connection to WB2DRD-3 and type INFO, but do not get
a response back in 30 or 40 seconds, disconnect and try later because the
220-MHz channel is probably too busy.  If you do get a response back, feel
free to connect to any of the stations that are accessible from the
network.

To improve things, we will be expanding the ROSE network north and south.
A Manhattan switch was added recently and a link to northwestern New Jersey
should be up soon.  We hope to have a site in southern New Jersey in the
near future.

If you have friends that can access any of the netwrks outside of New
Jersey, who wish to contact you here on 145.07 MHz, have them try and
connect to the WB2DRD-3 NET/ROM node.  If they can, then they should be
able to connect to you here on 145.07 MHz.  After they make a connection to
WB2DRD-3, they must type:

     C W2XXX-Y v N2EVW-7,609426

where W2XXX-Y is your call sign and SSID, N2EVW-7 is the ROSE switch that
is on 221.01 MHz and 609426 is the ROSE address for the KA2VLP-3 ROSE
switch (access of any ROSE switch on the network and the use of the address
609426 results in a connect attempt here on 145.07 MHz via the KA2VLP
switch).  Remember, the TNC 1 problem mentioned earlier.

from Andy Funk, KB7UV


      BOSTON COMPUTER SOCIETY FORMS HAM RADIO SPECIAL INTEREST GROUP

The Boston Computer Society (BSC), the world's largest association of
personal computer users, recently announced the establishment of an Amateur
Radio Special Interest Group.  The BCS Member Services Committee voted to
establish the new ham radio group to tap the synergy existing between
personal computing and Amateur Radio.

"The formation of this special interest group will bridge two distinct, but
complimentary fields of interest," said Barry Porter, KB1PA, director of
the Amateur Radio Special Interest Group.  "It exposes personal computer
users to ham radio, while allowing Amateur Radio operators to take
advantage of the wealth of resources made available by the BCS, such as an
abundance of technically competent members, an enthusiastic volunteer-based
organization and extensive membership benefits."

Porter explained that applications for computers in ham radio include
digital radio communication, network management, earth-based and satellite
station control, video/FAX signal processing and a number of
special-purpose applications, such as propagation prediction, satellite
tracking, record-keeping and telemetry.

The Special Interest Group was formed by a core group of BCS members after
more than a year of planning and organization.  Monthly meetings and a
group newsletter cover such topics as packet radio, shortwave listening,
amateur satellites and reception of high resolution weather satellite
images.

The group's plans include several technology-related projects, both
hardware- and software-based.  In addition, an amateur Novice license class
will be offered in the fall.

The Boston Computer Society is the world's largest personal computer user
group with more than 31,000 members from every state and 57 countries
worldwide.  It is a nonprofit organization dedicated to educating people
about the uses of personal computers.  Founded in 1977, the BCS has its
headquarters in Boston.

To join BCS and te Amateur Radio Special Interest Group, send an SASE to:

     Amateur Radio Special Interest Group
     The Boston Computer Society
     One Center Plaza
     Boston, MA 02108

For further information, call Barry Porter, KB1PA, at 617-341-2639 or
617-769-6000 extension 174, or Tom Walsh, KT1W, at 617-466-2392.

        LOCAL PACKETEERS NEEDED TO HELP DISTRIBUTE BBS DATA

Howard Sargent, SYSOP of the SEL (Space Environment Laboratory) landline
BS, is looking for assistance from local radio amateurs to help get
bulletin-board information onto packet-radio nets.  (The SEL BBS provides
extensive propagation reports.  See "NOAA's Space Environment Laboratory
Public Computer Bulletin Board Service" in August QST.) Volunteers are
needed to regularly download files from the SEL mainframe computer and
assist in setting up methods to make the data available to as many amateurs
as possible.

If you'd like to help and you live in the Denver area (where it's a local
call to the 497 exchange in Boulder), give Howrd a call at 497-3697 to
discuss possibilities or write to him at:

     Space Environment Services Center
     NOAA/ERL R/E/SE2
     325 Broadway
     Boulder, CO 80303.

by Dave Rosenthal, N6TST from QST

GATEWAY CONTRIBUTIONS

Submissions for publication in Gateway are welcome.  You may submit
material via the U.S. mail to:

     Gateway
     Stan Horzepa, WA1LOU
     75 Kreger Drive
     Wolcott, CT 06716-2702

or electronically, via CompuServe to user ID 70645,247.  Via telphone,
your editor can be reached on evenings and weekends at 203- 879-1348 and he
can switch a modem on line to receive text at 300, 1200 or 2400 bit/s.
(Personal messages may be sent to your Gateway editor via packet radio to:
WA1LOU @ W1AW.)

The deadline for each issue of Gateway is the Saturday preceding the issue
date (which is typically a Friday).


REPRODUCTION OF GATEWAY MATERIAL

Material may be excerpted from Gateway without prior permission, provided
that the original contributor is credited and Gateway is identified as the
source.

--
Gary W. Sanders (gws@n8emr or ...!osu-cis!n8emr!gws), 72277,1325
N8EMR @ W8CQK (ip addr) 44.70.0.1 [Ohio AMPR address coordinator]
HAM/SWL/SCANNER BBS (1200/2400/PEP) 614-457-4227

------------------------------

Date: 4 Aug 89 01:02:10 GMT
From: att!mcdchg!ddsw1!indep1![e-mail]  (Peter Franks)
Subject: High speed packet questions

In article <[e-mail]> [e-mail] (Bdale Garbee) writes:
>>Which is the best interface for IBM PC-compatible machines?  Should we
>>use the Pac-Comm PC-100 (is it supported by KA9Q NET software yet?),
>>or something else? Opinions, please!
>
>The driver for the PC-100 has not, to my knowledge, ever been completed or
>tested.  For 56kb operation, KA9Q has written a high-speed driver for the DRSI
>PCPA card, that works fairly well.

I've read bits and pieces here and there about DRSI's stuff, but never anything
definitive.

Will the DRSI card described above, using the software described above, operate
under Xenix 2.2.3 (286)?  Where can I get literature, etc.?

I'm thinking of getting back into packet, probably using TCP/IP.  Is this the
way to go?  Opinions, please (hopefully from someone who is DOING it).

Thanks & 73

--
+------------------------------------------------------------------------------+
|  Peter Franks  |          [e-mail]  OR  [e-mail]          |
|      NI9D      |                     Use whichever one works                 |
+------------------------------------------------------------------------------+

------------------------------

End of PACKET-RADIO Digest V89 Issue #185
*****************************************
 9-Aug-89 15:28:58-MDT,7409;000000000000
Return-Path: <[e-mail]>
Date: Wed,  9 Aug 89 15:00:35 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #186
To: [e-mail]

PACKET-RADIO Digest         Wed,  9 Aug 89       Volume 89 : Issue 186

Today's Topics:
               FT727 on Packet
          Need info on packet radio (2 msgs)
              Packet radio mailing list
            rs232 control for ICOM radios
            TAPR Office Closed Temporarily
----------------------------------------------------------------------

Date: 9 Aug 89 17:45:00 GMT
From: apollo![e-mail]  (Carl Heinzl)
Subject: FT727 on Packet

First,  I appreciate the mail (and the call from Rick N7LDI) on how
to get the FT727 to work on packet with the MFJ 1278.  I first attempted
the easiest method available (with the parts I happened to have
available).  That was to take the mike line through the capacitor, tie
it to the ptt line, through a resistor to gnd.  While I was able to
key the transmitter I couldn't get any reply.  After varying the
capaciator and resistor all over the place with no results, I went with the
suggestion from Bob Merritt N7JKV and used a small audio
isolation transformer with a 10k pot (if anyone need a copy of the
schematic just let me know) and I was up and running in no time flat.

Now, to the meat of my project.  I'm off working on a multi connect
bulletin board system that will eventually allow both ax.25 AND tcp/ip
connection.  The AX.25 is working, but many features still need to
be added before I begin alpha/beta testing and then finally release
to the world.  I assume that the W0RLI BBS is pretty much the standard
system in place today (correct me if I'm wrong).
If anyone has any features that they like about BBS's
or ones that they WOULD like to see in future BBS's I have an open
ear.

-Carl-

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Carl G. Heinzl         Internet: [e-mail]
 Apollo Computer, Inc.  UUCP:     {mit-eddie,yale,uw-beaver}!apollo!heinzl_c
 Chelmsford, MA 01824   Phone:    [phone] x6701

--

------------------------------

Date: 7 Aug 89 19:09:24 GMT
From: swlabs![e-mail]  (Jack Bonn)
Subject: Need info on packet radio

In article <[e-mail]> [e-mail] (John Covington WN4BBJ) writes:
>
> You need at least a Novice class Amateur Radio license to operate packet
> on 222 MHz, at least a Technician class to operate on 144 MHz and a
> General class license to operate packet on HF bands.

Is this true?  "What's Going on in the New Novice Bands" (QST, May
1987) seems to contradict this.  In the section covering 28.1 to 28.5
MHz, it indicates that Novices have "new F1B (frequency shift keying, or
FSK) privileges from 28.1 to 28.3 kHz (sic); these privileges allow you
to use packet radio, AMTOR, and Baudot and ASCII RTTY."

Did anything later rescind this?

-Jack
--
Jack Bonn, KA1SMW, <> Software Labs, Ltd, Box 451, Easton CT  06612
uunet!swlabs!jack (UUCP)        [e-mail] (INTERNET)

------------------------------

Date: 8 Aug 89 17:18:38 GMT
From: unccvax![e-mail]  (John Covington WN4BBJ)
Subject: Need info on packet radio

In article <[e-mail]>, [e-mail] (Jack Bonn) writes:
> In article <[e-mail]> [e-mail] (John Covington WN4BBJ) writes:
> >
> > You need at least a Novice class Amateur Radio license to operate packet
> > on 222 MHz, at least a Technician class to operate on 144 MHz and a
> > General class license to operate packet on HF bands.
>
> Is this true?  "What's Going on in the New Novice Bands" (QST, May
> 1987) seems to contradict this.  In the section covering 28.1 to 28.5
> MHz, it indicates that Novices have "new F1B (frequency shift keying, or
> FSK) privileges from 28.1 to 28.3 kHz (sic); these privileges allow you
> to use packet radio, AMTOR, and Baudot and ASCII RTTY."
>
> Did anything later rescind this?

Hmm, you may be right about 10 meters (I thought it was voice and cw
only but I guess I was wrong).  However, you need a General class
license to operate packet on any HF  band besides 10 meters.

Thanks for the correction.
73 de John WN4BBJ

John Covington WN4BBJ        E-mail: [e-mail]
P.O. Box 217122              MCI Mail: JCOVINGTON 342-6957
Charlotte, NC 28221-7122     Packet Radio: WN4BBJ @ KK4L
[phone]               "Give it back, Eric, it's not yours" (the ICOM)

------------------------------

Date: Mon Aug 07 08:06:34 1989
From: microsoft![e-mail]
Subject: Packet radio mailing list

Please subscribe me to the Packet Radio Mailing List.
Thanks Nate Dixon


------------------------------

Date: 3 Aug 89 23:33:20 GMT
From: cs.utexas.edu!sun-barr!newstop!east!tjp![e-mail]  (John Painter - Sun BOS Hardware)
Subject: rs232 control for ICOM radios

In article <[e-mail]> [e-mail] (Martin Grossman) writes:
>
>pin #          Description
>
>16     Control signal (DBC) input terminal for external control
>17     NC
>18     NC
>19     Control signal (DV) output terminal for external control
>20     Control signal (RT) input terminal for external control
>21     Data signal (DB1) input/output terminal for external control
>22     Data signal (DB2) input/output terminal for external control
>23     Data signal (DB4) input/output terminal for external control
>24     Data signal (DB8) input/output terminal for external control
>
>
>Now the article mentions that some radios have an input and output
>that are 5V rs232 signals but neither of these do.
>
ICOM makes a board to covert from parrallel to serial for the older
ICOM equipment.  Try AES or HRO (I can't remember the part number off
the top of my head)  I believe it is about $25.00 at discount.

/Tjp
-disclaimer:> I am not a HAM soo... what do I know.  (sorry, bad taste
form code/code-free discussions)

useless blank lines follow to satisfy silly mailer requirement 'n' now


------------------------------

Date: 6 Aug 89 05:08:26 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: TAPR Office Closed Temporarily

From Compuserve, HAMNET section 9:

#: 104571 S9/Packet Radio
    02-Aug-89  19:56:51
Sb: TAPR office is back
Fm: ANDY FREEBORN  N0CCZ 73177,1317
To: All

After a short period of down time at the TAPR office due to the early arrival
of a baby girl to Cris, our office manager, we're now back in business as
usual.

Heather, N7DZU, is answering the remoted phone calls and handling all of the
office duties. The new supply of DCD mod kits have arrived and back orders are
being filled as rapidly as possible.

Office hours continue to be from 1000 to 1500 Aizona time (which is the same as
PDT) Tuesday through Friday. A recorder will be placed on line to take urgent
messages during other hours.  We're playing catch-up as quickly as we can for
all unfilled requests.

We appreciate your patience and understanding.

Andy  N0CCZ

------------------------------

End of PACKET-RADIO Digest V89 Issue #186
*****************************************
10-Aug-89 01:04:45-MDT,17625;000000000000
Return-Path: <[e-mail]>
Date: Thu, 10 Aug 89 01:00:22 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #187
To: [e-mail]

PACKET-RADIO Digest         Thu, 10 Aug 89       Volume 89 : Issue 187

Today's Topics:
              Gateway 14-Jul-89
----------------------------------------------------------------------

Date: 9 Aug 89 19:32:03 GMT
From: n8emr![e-mail]  (Gary Sanders)
Subject: Gateway 14-Jul-89

==============================================================
|               Relayed from packet radio via                |
| N8EMR's Ham BBS, 614-457-4227 (1200/2400/19.2 telebit,8N1) |
==============================================================

Gateway: The ARRL Packet Radio Newsletter              July 14, 1989

Volume 5, Number 21                                      Part 1 of 4

Stan Horzepa, WA1LOU, Editor

      WASHINGTON FREQUENCY COORDINATOR ENDS PACKET RADIO COORDINATION

The Western Washington Amateur Relay Association (WWARA), the frequency
coordinator for Western Washington, has terminated frequency coordination
of packet-radio operations.  At its April meeting, the membership of WWARA
voted unanimously to approve a proposal that ends its packet-radio
frequency coordination function (see "No Packet-Radio Coordination
Proposed" i Gateway, Volume 5, Number 11).  WWARA will retain the power to
coordinate frequencies of packet-radio operations that wish to use a
standard voice repeater frequency pair.  After the proposal was accepted,
WWARA terminated all of its previous packet- radio frequency coordinations
and sent certified letters to the affected parties notifying them of the
termination.

The WWARA membership also unanimously voted to recognize the Northwest
Amateur Packet Radio Association (NAPRA) as the frequency coordinator of
those paet-radio operations that are no longer under WWARA's
jurisdiction.

from The Coordinator (WWARA's newsletter)

        BROADCAST PROTOCOL PROPOSED FOR SATELLITES

Harold Price, NK6K, and Jeff Ward, G0/K8KA, have presented revision 4 of a
proposal for a protocol to be used by the UoSAT-D Packet Communications
Experiment and by the AMSAT-NA MicroSats.  This protocol is meant to
facilitate the transmission of data to large numbers of ground users and
would supplement the standard AX.25 connected mode.

The designof the protocol is not yet final, nor is its particular
implementation on the satellites.  Allowing time for comments, a final
version should be available in late July.

Comments on this proposal are welcome and encouraged.  Address comments to
HPRICE or UOSAT via Telemail, 71635,1174 via CompuServe, NK6K @ WB6YMH or
G0K8KA @ GB2UP via packet radio.

[The proposal is available for downloading from Data Library 9 (DL9) on
CompuServe's HamNet.]

             AMSAT SPACE SYMPOSIUM RESCHEDULED

A conflit between the scheduled dates of the MicroSat/UoSAT launch and the
AMSAT-NA Space Symposium have motivated AMSAT-NA officials to reschedule
the Symposium to the weekend of November 3-5 (the MicroSat/UoSAT launch is
now scheduled for November 10 and the Symposium had been originally
scheduled for November 10-12).  Since many key personnel for the satellite
program will be delivering papers at the Symposium, it was felt that it
would be impossible for them to be in two places at once.  Therefore, to
avoid ts conflict, the Symposium was rescheduled to one week earlier.

Everything else remains the same.  The location of the Symposium is Des
Moines, with registration on Friday, seminars on Saturday, the Annual
AMSAT-NA Banquet on Saturday evening and the Board of Directors meeting on
Sunday.  With the launch of the MicroSats and UoSATs D and E, there will be
many papers devoted to various aspects of these new satellites.  For more
information, contact AMSAT-NA at 301-589-6062 or Ralph Wallio, W0RPK, at
515-961-6406.

Gateway: The ARRL Packet Radio Newsletter              July 14, 1989

Volume 5, Number 21                                      Part 2 of 4

THE W0RLI INTERVIEW

Hank Oredson, W0RLI, is the author of the world-renowned W0RLI Mailbox
software.  In 1984, Hank wrote his mailbox software for the Xerox 820
computer, however, the limitations of that computer caused Hank to
switch to the IBM PC (and its clones) where it now resides in PBBSs
throughout the packet-radio world.  Herb Sallis, WB1DSW, and other
members of the New England Packet Radio Association (NEPRA) spent an
afternoon discussing the state of the packet-radio art with Hnk while
he was visiting Massachusetts.  The following interview was written by
Herb and published in NEPRA's newsletter, NEPRA PacketEar.

By the way, Hank recently released Version 10.08 of his mailbox
software and it is available from the usual sources.

Q: How are things going on your side of the country in terms of the network
   your folks are putting together?

W0RLI:  Not too well in my area actually.  Northern California LAN
   frequencies are out of control.  We have some real problems in terms of
   overall network speed versus the number of packet users on the air at
   any given time.  Many of the network enhancements we looked forward to
   from NET/ROM haven't come into being with hidden transmitters and faulty
   radios among the top problems.

Q: Is anyone doing anything about the situation?

W0RLI:  I suppose just as in any network, we have some political hurdles
   to deal with.  Mountaintops, while not scarce, are difficult to acquire
   because of the tremendous number of other services (ham and non-am) in
   use.  Like many other networks, we have the "doers" and "users." The
   doers are so few in number that they can't get enough done fast enough,
   while the users do most of the complaining.

   There are moves afoot to experiment with the new 9600-baud modems
   available from England.  Some radios and modem kits are being prepared
   for testing, but right now I'm not exactly sure where all that is.
   Getting the network to move faster has to be an absolute priority.

Q: Describe briefly the size of the network at this time.

W0RLI:  In my small area, there are 24 active NET/ROM nodes and
   approximately six active full-time mailbox systems.  I have a hard time
   keeping track of the numbers out there beyond the valley I live in, but
   it seems as though we're sprouting new systems each day.

Hank quickly looked at a New England backbone map and commented:  A lot has
changed since I left.  This looks impressive!  Does it work?  I would say
that New England and the East Coast have a good looking network... much
better than ours given the current state of affairs.

Q: How many of your mailbox systems are in operation today?

W0RLI:  Worldwide?  About 2000.  That's a seat-of-the-pants guess.  By the
   way, you can expect to see the first Russian mailbox systems appearing
   on the air within the next few weeks.

Q: Glastnost.

W0RLI:  Indeed!  I know there are over 350 mailboxes running now in Japan,
   too.

Q: That's a sizeable number.  Are the Japanese netoorks different?  Are
   they better, worse, the same?

W0RLI:  Far superior I feel that the Japanese are doing their network the
   right way and the effort they have put into organization, control and
   implementation is paying off handsomely.

Q: Please tell us their secrets!!

W0RLI:  First, they have assigned a Network Administrator for each of their
   sectors. He/she is given almost total reign in terms of setting up
   things like individual station parameters, NET/ROM and digipeater
   parameters, mailbox behaviors, frequency allotments, etc.  If someone
   doesn't play by the rules, that station is excluded from accessing
   mailboxes and is generally considered persona non grata until he/she
   changes his/her thinking.

   Also, they have wisely allocated large chunks of frequency spectrum for
   packet use.  They have carved out many channels on 2 meters with
   standard spacing.  Further, they have allotted 200 channels in the 440
   to 450-MHz range.  Each block of 100 channels is spaced at least 100 kHz
   apart giving them the ultimate in flexibility later when faster speeds
   become widely available.  The

   Japanese really know how to organize.  They multi-channel everything.
   They are also aggressively moving into the 1296-MHz range so that sites
   are available and in use for later upgrading.

Q: How do you come to know so much about Japan?

W0RLI:  In February 1988, they had a giant organizing effort, a major
   conference, and I was invited to attend, all expenses paid.  I
   gratefully attended and have kept abreast of affairs over there through

Gateway: The ARRL Packet Radio Newsletter              July 14, 1989

Volume 5, Number 21                                      Part 3 of 4

             THE W0RLI INTERVIEW  (Continued)

Q: Very interesting.  Speaking of "mailboxes," we've all seen the arrival
   of AA4RE's Multi-Connect BBS software recently.  What can you tell us
   about it?

W0RLI:  First off, I'm really not involved in that project as heavily as
   some people think.  I do have a business to run and other things I like
   to do.  From what I see, it looks and feels like a W0RLI system except
   that AA4RE uses the multi-connect capability of the newer TNCs.

   From my perspective, we already have networks jammed with retries and
   crashes brought on by the nature of the AX.25 protocol.  I don't think
   most people realize that, although their TNCs are set to 1200 baud on
   the RF port, the more stations you add to a channel, the worse things
   become in terms of congestion, and, as a result, your throughput rate is
   roughly divided by the number of stations that can be heard.  Thus, 1200
   baud is more like 50 baud on a busy channel crammed with retries and
  failures.  Multi-connects from a BBS standpoint adds to the futility.
   The full weight of the system's multiple attempts to resend the same
   packets over and over as the approaching acknowledgements fail to
   satisfy the sending TNC, bring further doom upon a channel.  This is why
   I, for one, have stayed away from doing anything of this sort.  At 1200
   baud, it will bring most networks to their knees!

   By the way, I'm glad to hear you use the word "mailbox" instead of BBS.
   I have clled my program a mailbox from the very beginning.

Q: What will the next version of the mailbox look like?

W0RLI:  I don't have any firm plans in mind.  It does exactly what I think
   needs to be done at this time.  On the other hand, I would say that my
   new task would be to incorporate some specific kinds of "server"
   functions to do specific tasks related to specific needs.  And, of
   course, there are always those nifty little suggestions that come from
   just about everywhere, not to mention "bug" fixes.

Q: Speaking of new features, the round-table function came out in Version
   9.01, but was not documented and caused some problems.  What was the
   force behind it?

W0RLI:  You know I listen to folks when they ask for things and I try to
   give due consideration where I feel it's necessary.  The request for a
   round-table function came from an ARES group that pleaded desperately
   for a way to conduct a net-type operation.  So, I stuck it in and they
   usd it once, maybe twice and went back to sending mail back and forth.
   I guess it wasn't as useful as they first thought!  I may take it out if
   there's no need for it.  My philosophy is that I consider memory to be
   at a premium, so I try to keep my code as tight, compact and short as
   possible.

   Incidentally, let me comment on the lack of documentation.  I can't do
   both.

   The mailbox now supports passwords for remote SYSOPs.  I did this at the
   request of some European mailbox operators who were bein plagued by
   "packet terrorists" bent on destroying their network.  I know this
   feature is one that I'll probably keep.

Q: I quite agree.  The code is so rich at this point that I frankly don't
   see how one single person could keep the documentation whole.  Now,
   where do you see the future of packet radio going?  Is TCP/IP going to
   take over?

W0RLI:  The first question is an interesting one, one which I get asked all
   the time.  My answer is that I'm not certain.  We have lots of good
   aplications out there now just beginning to come to the fore.  We need
   to move the network faster.  We need some satellite links between major
   areas of the country and around the globe, more than what is available
   now.  We need to educate users and SYSOPs alike.  Twenty minutes ago, we
   looked at NM1D's DOSGate, a real slick tool that can be used for a
   variety of purposes.  That's available now and I hope to see more of
   them spring up.

   I also get many questions about TCP/IP nd what it's future is.  My
   opinion is that it's nice, but it doesn't do anything more than the
   current systems can do.  I know it is getting more play in this area
   now.  I'm all for new things.

Q: It's been great seeing you again and getting your insights.  All of us
   want to thank you for your tireless efforts in providing such a fine
   system.

W0RLI:  Thanks.  I'll be back some day soon, I trust, and be able to make a
   NEPRA meeting!

Q: We all hope you'll be back soon. 73.

(For more information abouNEPRA, write to PO Box 208, East Kingston, NH
03827 or attend one of their monthly meetings on the second Thursday of
each month, 7:30 PM at the Honeywell plant cafeteria in Billerica, MA.)


Gateway: The ARRL Packet Radio Newsletter              July 14, 1989

Volume 5, Number 21                                      Part 4 of 4

                 LAN-LINK

LAN-LINK is a packet-radio and AMTOR terminal program that runs on IBM PCs
or clones and provides a window into the Local Area Network (LAN) for the
AEA PK-232s, Kantronics KAMs, TNC 1s and TNC 2s.  It uses menus and
function keys to allow the user to communicate, rather than play with TNC
parameters which he doesn't understand.  Some of its features follow.

o Recognizes your call sign in a PBBS mail beacon, then automatically
  connects and downloads your messages.

o Automatically requests bulletins from the PBBS on subjects that interest
  you.

o Provides a conference mode for multiconnect situations.

o Provides split-screen operation for incoming and outgoing text, as well
  as for terminal status information.

o Alerts you when a predetermined call sign shows up in a packet header on
  frequency.

o Automatically captures to disk a recording of all connections.  Indicates
  number of packet radio connections.

o Provdes "smart" packet mode printer control that turns off upon
  disconnection.

o Indicates that a specified station has connected while you were away.

o Automatically sets NET/ROM and KA-Node paths from its call/path file.

o Stores and forwards LAN messages.

o Automatically connects and downloads messages from other LAN-LINK
  stations.

o Determines paths to DX stations.

o Provides AMTOR/packet-radio MSO and Selective Automatic Answering Machine
  function that displays a message queue.

o Automatically configures TNC for HF and VHF packet-radiooperation.

o Calls CQ repetitively and alerts you when a reply is received.

o Provides RTTY SELCAL mode.

o Supports RTTY Navy MARS File Transfer Protocols (PK-232 only).

o Contest mode sends standard message and automatically increments QSO
  count.

o Provides single keystroke set-up to receive UoSAT-OSCAR 9 and Phase III
  RTTY telemetry (PK-232 only).

LAN-LINK is distributed as shareware, ie, the user can try the program and,
if he wishes to keep it, he registers his copy by sending $35 to its
author.  Registration entitles the owner to upgrades and full support.
Users of earlier versions of LAN-LINK and of PK3223COM Version 1.48 may
upgrade by sending the author a blank, formatted diskette and SASE.

LAN-LINK is written, maintained and upgraded by Joe Kasser, G3ZCZ, POB
3419, Silver Spring, MD 20901, telephone [phone].

from Joe Kasser, G3ZCZ

               GATEWAY CONTRIBUTIONS

Submissions for publication in Gateway are welcome.  You may submit
material via the US mail to:

    Gateway
    Stan Horzepa, WA1LOU
    75 Kreger Drive
    Wolcott, CT 06716-2702

or electronically, via CompuServe to user ID 70645,247.  Via telephone,
your editor can be reached on evenings and weekends at 203-879-1348 and he
can switch a modem on line to receive text at 300, 1200 or 2400 bit/s.
(Personal messages may be sent to your Gateway editor via packet radio to:
WA1LOU @ W1AW.)

The deadline for each issue of Gateway is the Saturday preceding the issue
date (which is typically a Friday).

            REPRODUCTION OF GATEWAY MATERIAL

Material may be excerpted from Gateway without prior permission, provided
that the original contributor is credited and Gateway is identified as the
source.

------------------------------

End of PACKET-RADIO Digest V89 Issue #187
*****************************************
14-Aug-89 11:47:42-MDT,4945;000000000000
Mail-From: KPETERSEN created at 14-Aug-89 11:37:56
Return-Path: <[e-mail]>
Date: Mon, 14 Aug 89 11:37:54 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #188
To: [e-mail]

PACKET-RADIO Digest         Mon, 14 Aug 89       Volume 89 : Issue 188

Today's Topics:
               GETTING STARTED?
               HDLC driver for KA9Q sfw
              Need info on packet radio
          PCroute 2.0 ($800 IP router) now available
----------------------------------------------------------------------

Date: 10 Aug 89 20:19:20 GMT
From: tahoe!wheeler![e-mail]  (Mike Whitbeck)
Subject: GETTING STARTED?

I am interested in packet radio as a hobby and have a few
questions:

What do I need in the way of hardware and software (especially
at the radio end- I have a desktop 68000).? Is a modem used in
packet radio?

What kind of license(s) is required?
What are the licensing requirements?
What magazines regularly cover packet-radio?
How do I find out what (if any) other operators might be active
    in my area (i.e. within range)?

Thanks in advance!

------------------------------

Date: 12 Aug 89 00:22:56 GMT
From: lll-crg.llnl.gov![e-mail]  (Edjik)
Subject: HDLC driver for KA9Q sfw

Hi, Im in the process of debugging an HDLC driver for the KA9Q sfw
package.  Does anyone know of any other HDLC driver avalable for this
software?  I am using the MITEL ISDN card plugged into a IBM AT.  If
anyone knows of anyone else using this board with the ka9q sfw, plz
let me know so i can talk to someone about a few strangenesses ive
encountered.  Thanks.

--Edjik

------------------------------

Date: 9 Aug 89 16:53:11 GMT
From: att!tsdiag!ka2qhd![e-mail]  (Thomas A Moulton RATS Clifton NJ)
Subject: Need info on packet radio

Jack, nothing has changed since then, FSK modes are still OK
--
Life is too short to be mad about things.
Thomas A. Moulton, W2VY          Packet: w2vy@kd6th  Voice: 145.190 (r)
[phone]                   uucp: rutgers!petsd!tsdiag!ka2qhd!w2vy

------------------------------

Date: Fri, 11 Aug 1989  22:09 MDT
From: Keith Petersen <[e-mail]>
Subject: PCroute 2.0 ($800 IP router) now available

This file is now available from SIMTEL20 as pd1:<msdos.network>PCROUT20.ARC.

--Keith

[--forwarded message (somewhat edited for brevity)--]
From: [e-mail]  (Vance Morrison )
Organization: Northwestern Univ. Evanston, Il.
Subject: PCroute 2.0 ($800 IP router) now available
To: [e-mail]

Well, at long last, PCroute2.0 is available.  Version 2.0 is a big
step forward for PCroute.  In particular SLIP support has now been
added.  For those unfamiliar with PCroute here is a short description.

Vance

----------------------------------------------------------------


        PCROUTE - an IP routing program from the IBM PC
                 Vance Morrison
            [e-mail]

    Traditionally IP routers have been fairly high performance,
expensive machines.  Typically they run about $5000-$10,000 a unit.
Until now a IP router for under $5000 was just about impossible
to get.  Recent developments in PC hardware, however, has made
it possible to convert a PC to an IP router for a TOTAL of $800
a unit.  This price is less that the cost of many ethernet boards
and thus it now makes sense to always use dedicated router to
perform IP gatewaying functions.

---------------------------------------------------------------------
What is PCroute?

    PCroute is software written for an PC/XT (or AT) or clone that will
allow it to act as a IP router.   At present the following interfaces
are supported.

    Ethernet - (WD8003E card) (recommeded no more than 4 interfaces)
    Starlan  - (WD8003S card) (up to 6 interfaces)
    Localtalk - (Apple localtalk card for the PC) (1 interface max)
    SLIP      - (COM1..COM4)  (2 interfaces max)

   One of the most common configuration for the router is as an
ethernet-ethernet router, but this is not the only configuration possible.
The software supports up to 6 interfaces of varying types, so many
many configurations are possible.  Exact details on what is possible
is explained in the installation/compilation manual

   In addition to the XT, the only other hardware needed are the
networking cards, which at present run about $225 a piece (for ethernet).
Since you can buy an XT (10Mhz, without an monitor) for $350, the total
cost for the hardware is $800

--end forwarded message--

------------------------------

End of PACKET-RADIO Digest V89 Issue #188
*****************************************
17-Aug-89 10:33:04-MDT,10790;000000000000
Return-Path: <[e-mail]>
Date: Thu, 17 Aug 89 10:00:18 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #189
To: [e-mail]

PACKET-RADIO Digest         Thu, 17 Aug 89       Volume 89 : Issue 189

Today's Topics:
                2m-220 gateway
              GETTING STARTED? (2 msgs)
              Interfacing to FT-208R HT?
            Model 43 Teletype Help
----------------------------------------------------------------------

Date: 17 Aug 1989 06:34-CDT
From: "410 BMW/SCX--KI Sawyer AFB MI" <[e-mail]>
Subject: 2m-220 gateway

Can someone please tell me simply what is required for a cross-band
gateway without twenty miles of dissertation on NET, NETROM, etc?

All I want is the simplest/cheapest/easiest way to get some of our
local novices, now on 220, to the two-meter system.  Do I need two
TNCs? If so, how do I hook them together?  Is there one unit that will
do?  Anyone have personal experience in doing this?


Again, no long stuff on TCP/IP, NET, etc, just simple.  We have lots
of new novices, some who have run right out and bought shiny new 220
rigs, only to have almost no one to talk to.  If I can get a gateway of
some type so they can access the BBSs, etc on two-meters packet, we may
be able to keep them in the hobby.

Please E-mail, as I don't always get to read the newsgroup.

Thanks and 73,

Michael

*******************************************************************************
Michael Barnes                       *   The nice thing about policies
InterNet: [e-mail]    *   and standards, is that there
HamNet: WA7SKG                       *   are so many to choose from.
BellNet: 906-346-2578                *   If you don't find any you
DS Net: 472-2578                     *   like, simply wait for next
Snail Net: 2001CS/XP                 *   years models!
       K.I. SAWYER AFB, MI       *
             49843-6346      *
*******************************************************************************
DISCLAIMER: The ideas, comments, remarks, replies, insinuations,
innuendos, flatuations, and any other conceivable or inconceivable
outputs presented here, real, imagined, or implied, simply do not
exist.  The names are real, the stories have been changed due to
simple boredom.
*******************************************************************************



------------------------------

Date: 14 Aug 89 22:31:39 GMT
From: elbereth.rutgers.edu!hardees.rutgers.edu![e-mail]  (Ron Natalie)
Subject: GETTING STARTED?

> What do I need in the way of hardware and software (especially
> at the radio end- I have a desktop 68000).? Is a modem used in
> packet radio?

The most common basic technology for packet radio is a device called
a TNC.  The most common of which is a design known as the TAPR TNC 2.
This will run you somewhere around $100-$200 dollars depending on the
bells and whistles you get with it.  This device is a combination
modem and protocol engine for packet radio.  It looks like a 1200
baud modem (plug the radio into one side, plug a RS-232 cable from
a terminal into the other).  The thing is intelligent so you can
just plug a terminal into it and go, or you can get sophisticated
and do nifty things with personal computers.  The radio and antenna
will cost you somewhere between $100-400 dollars depending on how
classy you want to get and whether you buy new or used.

> What kind of license(s) is required?

An amateur radio license is required.  There are five classes.
Even the lowest license class (Novice) will allow you to do
packet, but the Technician license class is probably the most
common as it allows you to use radios on all the allocated VHF/UHF
frequencies.

> What are the licensing requirements?

To get an amateur radio license you need to pass two tests.
One is a Morse code test where you demonstrate the ability to
receive morse code at a given speed that varies for license
class.  The Novice and Technician classes both require 5 Words
per Minute.  There is talk of a no code version of license amounting
pretty much to what the technician license is now, but that is
probably still off in the future.

The other test is a multiple choice test on radio theory and
the essential regulations pertaining to amateur radio.  It's
30 questions for the Novice and another 25 for the Technician.
I've given about a dozen novice tests and I have never seen
anyone fail it yet.

> What magazines regularly cover packet-radio?

There are three major amateur radio magazines:  QST, 73, and CQ.
They all cover packet radio to some extent.   QST is the official
rag of the American Radio Relay League, the major national amateur
radio association.  They also publish a packet radio newsletter called
"Gateway" which you can also find in electronic form on many BBS systems.
73 is published by Wayne Green (they guy who brought us Kilobaud many
years ago).  It usually has a more technical bend to it, but you also
have to contend with Wayne's frequently corrosive commentary.  CQ is
another long time journal that deals mostly with the traditional contesting
and DX hunting amateur radio activities, but does have a packet column.

In addition, there are books available.  "Tune in the World with Ham
Radio" is a general introduction to amateur radio and provides all
the information you need to get your Novice license.  It also can be
ordered with cassette tapes for learning Morse code.  It comes from
the ARRL.  There are other various ARRL publications on packet including
are more detailed book (something like Get ***Connected with Packet)
as well as the packet radio protocol specification and procedings from
the packet radio conferences held.

> How do I find out what (if any) other operators might be active
>       in my area (i.e. within range)?

If you mean before you get on the air, you might try looking for
a local club.  The ARRL can tell you if there are any affiliated
clubs in your area.  Also, another group called NARA, has a nation
wide directory of helpful hams that have volunteered to have their
name listed as contact points.  If you tell me where you are, I
can look that up.

If you mean, within range on the air, the answer is really
complex.  In addition to people you live near that you can
talk to directly, there is an extensive network system in
many areas that allows you to talk to people many states
away.  In addition, HF packet allows you to talk directly
to stations around the world. If you'd like to check on
how active your area is, and have a scanner, set it to 145.01
and see if you hear sounds like whales mating.  Those are the
packet radio modem burts.  145.01 is the main "hang out"
frequency.  You could even buy a TNC and hook it up to the
scanner and eavesdrop (it's legal) on these while you are
working on getting your license.  You only need the license
to transmit.

-Ron

------------------------------

Date: 15 Aug 89 19:22:42 GMT
From: gem.mps.ohio-state.edu!ginosko!aplcen!jhunix![e-mail]  (Thomas G Edwards)
Subject: GETTING STARTED?

I just got my TNC to work properly with my HT last night, and suprisingly
was able to find a NET/ROM and digipeat to a local PBBS.  Now I have more
questions:

1)  I think I understand the NODES commands of NET/ROM, but what do the other
    commands (besides CONNECT) mean?

2)  Does anyone use Kantronics KANODES on the East Coast?
3)   How does TCP/IP fit into the picture?

I realize that local packet maps may help, but even though I have a general
idea of how some of the higher-level networking systems work, I don't
know how to use them.  Furthermore,
4)  Where on the internet/packet/Baltimore can I find packet software
    for the Commodore Amiga?

5)  How come HELP seems so little and far between on packet Nodes and PBBS's?
-Thomas Edwards
 N3HAU@N3ZH     (wow..I always wanted to sign like that!)
 [e-mail]

------------------------------

Date: 15 Aug 89 20:31:38 GMT
From: deimos.cis.ksu.edu!harris.cis.ksu.edu![e-mail]  (Myron A. Calhoun)
Subject: Interfacing to FT-208R HT?

Has anyone interfaced any of the common TNC's (preferably Kantronics)
to an FT-208R handi-talkie?  From examining the 208R schematic, it
looks simple, as the PTT input does NOT seem to interact with the mic
input.  But I thought I'd ask first!
--Myron, W0PBV.
--
Myron A. Calhoun, PhD EE, W0PBV, [phone] (work), 539-4448 (home).
INTERNET: [e-mail]
BITNET:   [e-mail]
UUCP:  ...{rutgers, texbell}!ksuvax1!harry!mac

------------------------------

Date: 17 Aug 1989 06:39-CDT
From: "410 BMW/SCX--KI Sawyer AFB MI" <[e-mail]>
Subject: Model 43 Teletype Help

I need any information I can get on Model 43 Teletype units.
I recently aquired several of these units that seem to work.
They have DB25 connectors on them for the I/O.  Are these RS-232
ports?  I have been told the output is standard ASCII.  My plan is to
use them as terminals on packet and with other modem type services.
I also understand there is a way to connect a video monitor to these.
Any data would be appreciated, including references to magazine articles.

Please E-mail as don't always get to read the newsgroups.

Thanks and 73,
Michael.

*******************************************************************************
Michael Barnes                       *   The nice thing about policies
InterNet: [e-mail]    *   and standards, is that there
HamNet: WA7SKG                       *   are so many to choose from.
BellNet: 906-346-2578                *   If you don't find any you
DS Net: 472-2578                     *   like, simply wait for next
Snail Net: 2001CS/XP                 *   years models!
       K.I. SAWYER AFB, MI       *
             49843-6346      *
*******************************************************************************
DISCLAIMER: The ideas, comments, remarks, replies, insinuations,
innuendos, flatuations, and any other conceivable or inconceivable
outputs presented here, real, imagined, or implied, simply do not
exist.  The names are real, the stories have been changed due to
simple boredom.
*******************************************************************************



------------------------------

End of PACKET-RADIO Digest V89 Issue #189
*****************************************
19-Aug-89 15:06:46-MDT,8512;000000000000
Return-Path: <[e-mail]>
Date: Sat, 19 Aug 89 15:00:54 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #190
To: [e-mail]

PACKET-RADIO Digest         Sat, 19 Aug 89       Volume 89 : Issue 190

Today's Topics:
                2m-220 gateway
              8th ARRL CNC Registration
              MFJ-1278 problem with RTTY
            Model 43 Teletype Help
               Wanted ka9q Unix packet
----------------------------------------------------------------------

Date: 18 Aug 89 23:45:37 GMT
From: wuarchive!texbell!uhnix1!sugar![e-mail]  (Jason Asbahr)
Subject: 2m-220 gateway

Has there been any discussion on a packet-Usenet gateway?  Or the use of
radio to connect 'nix sites?

      -Jason Asbahr, clattering away at sugar, Houston

------------------------------

Date: 17 Aug 89 15:05:46 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: 8th ARRL CNC Registration

Andy asked me to post this... **PLEASE** register if you're planning to be
here... it's important that we have some idea of how many folks are planning
to attend!

73 - Bdale, N3EUA


The 8th ARRL Computer Networking Conference (read PACKET RADIO) will be held
in Colorado Springs on the 7th and 8th of October 1989.

If you plan on presenting a paper, please contact Lori Weinberg at ARRL
headquarters for an authors's package. Deadline for receipt of camera-ready
papers is August 28.

On Saturday Oct. 7th the speakers will be presenting their papers describing
the latest in packet radio digital, RF, networking and satellite
developments. This session will be held in conference facilities at the Air
Force Academy. Hosts will be TAPR, AFA ARC, AFA Cadet ARC, RMPRA & ARRL.
On Saturday eve there will be an attitude adjustment hour at the Marriott.

On Sunday Oct. 8th the ARRL Digital Committee will meet in open session at
the new Colorado Springs Marriott.

Also on Sunday the Rocky Mountain Packet Radio Association will host their
annual Packetfest at the Marriott. This years Packetfest will feature
speakers in attendance for the conference. The RMPRA session will consist of
tutorial/discussion/Q&A presentations as well as demonstrations.

Conference headquarters (and hospitality room) will be at the Colorado
Springs Marriott. Special conference rates are: Single room, $45; extra
person in room, $13. Reservations must be made by September 6th. After this
date there is no assurance that space or the special rate will be available.
When calling for reservations, call the Marriott direct at [phone]
(do not use the Marriott 800 number). To get the special rate be sure to
identify yourself as a member of the "ARRL Networking Conference".

A conducted tour of the Air Force Academy is planned for those arriving
before 3PM on Friday, October 6th. Private transportation will be used so
please indicate your interest in this tour when sending in your registration.
There will be no charge for the tour.

Special activities for those ladies accompanying their ham spouses are being
arranged for Saturday. Drop a note to Karen Garbee, N1FED, 4390 Darr Circle,
Colorado Springs, CO, 80908 to get the details. Karen can also be reached at
[phone], Compuserve 76430,3323, or [e-mail].

Registration for the conference is $20.00. This fee includes the conference,
one bound copy of the 8th Networking Conference papers, refreshments through-
out the day of the conference, lunch at the AFA Officers Club (transportation
will be provided) and use  of the Marriott hospitality room. Extra copies of
the bound conference papers will be available for $12.00 each.

  IMPORTANT      ********       IMPORTANT      ********       IMPORTANT

In order that suitable arrangement are made to accomodate all in attendance
it is important that you register before October 2nd. Send your $20
registration fee (make checks payable to Andy Freeborn), along with your
name, call, address and telephone number to:

Andy Freeborn, N0CCZ, President TAPR
5222 Borrego Drive
Colorado Springs, CO  80918
Telephone: [phone]

------------------------------

Date: 18 Aug 89 17:05:01 GMT
From: cs.utexas.edu!swrinde!dpmizar!dptspd![e-mail]  (Lee Ziegenhals)
Subject: MFJ-1278 problem with RTTY

I bought a used MFJ-1278 a few months ago (I wanted a PK-232, but I couldn't
pass up the price for the 1278).  I noticed a problem with RTTY when I tried
to access one of the Air Force MARS computers.  The colon (":") was being
transmitted as an exclamation point ("!").

I called MFJ, and the fellow who took the call indicated that this was a
known problem, and that he would ship me a new EPROM that day.  That was
Monday, and the firmware arrived yesterday.  I was quite pleased with the
response time.

I am posting this to the net to let people know that this problem exists,
and that MFJ has a fix for the problem.  It seemed to occur both with the
old firmware *and* with the new 2.3 upgrade.  The interesting thing is that
the EPROM with the fix in it also had a 2.3 label on it, and signed on with
the same version number!  In other words, I don't know if there is any
way to tell if you have the fixed version or not, without actually testing.
Seems to me that there should have been some type of version or revision
number change, something like "2.3.1" or whatever.

If anyone else has been unable to access some of the RTTY BBSs that require
the colon character in the commands (such as the aforementioned AF MARS
computers), that is the problem.  Btw, you can test this out without going
on the air by setting FULLDUP ON, and installing JMP 7.  This provides a
loopback function, so you can see what you send being sent back to you.  Don't
forget to disconnect from your radio before you do this :-).

73/Lee, N5LYT

------------------------------

Date: 17 Aug 1989 06:39-CDT
From: "410 BMW/SCX--KI Sawyer AFB MI" <[e-mail]>
Subject: Model 43 Teletype Help

I need any information I can get on Model 43 Teletype units.
I recently aquired several of these units that seem to work.
They have DB25 connectors on them for the I/O.  Are these RS-232
ports?  I have been told the output is standard ASCII.  My plan is to
use them as terminals on packet and with other modem type services.
I also understand there is a way to connect a video monitor to these.
Any data would be appreciated, including references to magazine articles.

Please E-mail as don't always get to read the newsgroups.

Thanks and 73,
Michael.

*******************************************************************************
Michael Barnes                       *   The nice thing about policies
InterNet: [e-mail]    *   and standards, is that there
HamNet: WA7SKG                       *   are so many to choose from.
BellNet: 906-346-2578                *   If you don't find any you
DS Net: 472-2578                     *   like, simply wait for next
Snail Net: 2001CS/XP                 *   years models!
       K.I. SAWYER AFB, MI       *
             49843-6346      *
*******************************************************************************
DISCLAIMER: The ideas, comments, remarks, replies, insinuations,
innuendos, flatuations, and any other conceivable or inconceivable
outputs presented here, real, imagined, or implied, simply do not
exist.  The names are real, the stories have been changed due to
simple boredom.
*******************************************************************************



------------------------------

Date: 19 Aug 89 00:14:58 GMT
From: hpfcdc!hpldola!hp-lsd!col![e-mail]  (Bdale Garbee)
Subject: Wanted ka9q Unix packet

>I have this package and have not been able to get it compiled under SCO Xenix
>or IBM Xenix either. Has anyone been successful in getting it compiled using
>the UNIX switches?

I run 890421.1 all the time on my Unix box... what kinds of problems are you
having?

Bdale, N3EUA

------------------------------

End of PACKET-RADIO Digest V89 Issue #190
*****************************************
24-Aug-89 23:50:49-MDT,18319;000000000000
Mail-From: KPETERSEN created at 24-Aug-89 23:17:05
Return-Path: <[e-mail]>
Date: Thu, 24 Aug 89 23:17:04 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #191
To: [e-mail]

PACKET-RADIO Digest         Thu, 24 Aug 89       Volume 89 : Issue 191

Today's Topics:
              Gateway 11-Aug-89
----------------------------------------------------------------------

Date: 22 Aug 89 23:53:10 GMT
From: n8emr![e-mail]  (Gary Sanders)
Subject: Gateway 11-Aug-89

==============================================================
|               Relayed from packet radio via                |
| N8EMR's Ham BBS, 614-457-4227 (1200/2400/19.2 telebit,8N1) |
==============================================================

Gateway: The ARRL Packet Radio Newsletter - Stan Horzepa, WA1LOU, Editor

         Volume 5, Number 23 - August 11, 1989 - P 1 of 4

       TEXAS SYSOP DISCUSSES NTS AT ARRL NATIONAL CONVENTION

At the ARRL National Convention in Dallas-Fort Worth, June 2-4, Texas SYSOP
David Cheek, WA5MWD, presented a 15-minute seminar on "Packet Mailboxes and
the NTS." A summary of the points he made in his presentation follow:

1. All NTS traffic must be properly formatted, according to ARRL guidelines

2. Traffic must be addressed properly (using "ST").

3. Keep the text length below 25 words.

4. PBBS operators must cultivate NTS/packet-radio liaison stations.
   These folks are critical to our success.  Formal packet-radio NTS
   net designation may be an answer in some areas.

5. ZIP-Code routing within most states can lead to "dead end" delivery.
   This needs more research by PBBS operators and NTS people, but it is not
   safe to assume that even though the message reaches the proper PBBS for
   its ZIP Code, that it is going to get delivered.  Along this line, we
   have considered taking NTS traffic as directly to NTS section phone and
   CW nets as possible, and not using packet radio for the "final 200
   miles" of delivery.  This is very local matter, and must be checked.
   What works in Texas may not work everywhere, and we are not sure what
   works in Texas yet.

by David Cheek, WA5MWD @ WA5MWD from Indiana Packet NTS Newsletter

         FERNALD DISASTER DRILL TESTS PACKET RADIO

On June 24, a tank car carrying white phosphorous tipped over next to the
Fernald Nuclear Feed Materials processing plant near Cincinnati.
Simultaneously, a leak of radon gas was detected from Waste Silo 23 at the
nuclear plant.

Far fetched?  Maybe, but a similar scenario was played out in a simulated
emergency test spearheaded by the Ohio Emergency Management Agency (what
we used to call Civil Defense) in cooperation with several local disaster
relief agencies including police, fire departments and the Red Cross.

Approximately 30 amateurs were involved including members of the Butler
County VHF Society, Hamilton County Amateur Radio Public Service Corps and
Queen City Emergency Net.  Most activity was on 2- meter voice circuits.
However, I had the privilege of operating packet radio during this disaster
drill.  W8VVL, the Queen City Emergency Net station, was activated in
downtown Cincinnati.  Vern Barhorst, WD4EEB, and I were dispatched to a
simulated shelter at Groesbeck United Methodist Church, approximately 10
miles from the simulated disaster, where evacuees were sent.

The bottom line...it worked.  The only real hold-up was typing the
information into the computers.  I erred and didn't check out my 2-meter
packet radio, so I was stuck on 221.11 MHz and had to use N8XX-3 to get
to WA8DFD's 220/145-MHz dual-port node.

There was other activity on 144.91 MHz, so John Dine, WA8DFD, and W8VVL,
moved to a private frequency.  Our combined typing ability was perhaps 100
bit/s and our information input from Red Cross was less than 10 bit/s, so
this could have been overkill, but it didn't hurt.

WD4EEB and I traded tasks of shadowing the Red Cross and typing into my
Hewlett Packard Portable-Plus.  Traffic came in bunches and it always
seemed that we had to fight the syndrome of engaging keyboard before
getting all essential data (usually the name and title of the addressee and
originator).  Printers at both ends and attention to details like formal
message form, complete address and signature, etc, really impressed the Red
Cross, observers from Ohio EMA, and the press.  We appeared to have our act
together and appeared to know what we were doing (you needn't be totally
candid with the served agencies).

A total of 20 messages were handled between the two stations during the
course of the 2-hour drill.  Most of the traffic was administrative with
approximately five disaster welfare inquiries.

It was over at approximately 11:30 AM, in plenty of time for us hams to go
out and finish setting up for Field Day...which is another story.

by Hank Greeb, N8XX


Gateway: The ARRL Packet Radio Newsletter - Stan Horzepa, WA1LOU, Editor

         Volume 5, Number 23 - August 11, 1989 - P 2 of 4

         DOSGATE: PACKET-RADIO WINDOW TO MS-DOS COMPUTERS

The DOSGATE project started about seven years ago.  I saw a need for users
to understand that packet radio has a greater purpose in life than simply
be a great big network of PBBSs.  Packet radio promised to bring computers
and radio together and most users tended to think "PBBS" when they thought
of packet radio.  I see packet radio evolving into something more and
DOSGATE as a ray of light creeping under the door that is waiting to be
opened!

If you are familiar with using an MS-DOS-based PC, then you are familiar
with the DOSGATE system, as DOSGATE is only a window between the amateur
packet-radio network and the MS-DOS machine.  The functions that may be
performed by a DOSGATE system are only limited by your imagination.

DOSGATE is an alternative to the traditional PBBS.  Where the typical PBBS
allows users to send/read/forward mail/messages/files to one another and
keeps us all in touch with the Amateur Radio world, DOSGATE is not limited
to these functions.  DOSGATE allows the packet- radio user to access a PC
and perform almost any task.  Just as if the user were sitting in front of
a PC in their home or shack, the user can be in complete control of the
computer and can decide which software application to use.  Any hardware
available to the DOSGATE system can be used by the remote network user.  It
does not take much imagination to understand the power available to the
packet-radio network with one of these machines.  Just think about the
applications that could be made available with a system that has a 32-bit,
25-MHz, 80386 CPU, an 80387 floating-point co-processor, 16 Mbytes of RAM
and 300 Mbytes of disk storage, not to mention optical disk drives!
Understand that this power is available to any user on the amateur
packet-radio network, including users who only have "simple" computers at
home, eg, C-64s or Model 100 laptops.  Even the remote user that does not
have a computer at all can make use of the complete DOSGATE system!

This means that the user connected to a DOSGATE system could do almost
anything that is conceivable with a computer!  One might choose to play a
game, calculate the position of the OSCAR satellites, access an on-line
call sign directory, develop and compile programs or send mail to another
user and DOSGATE could perform all the usual PBBS functions in addition to
providing advanced higher level functions.

What Is DOSGATE?

Technically, DOSGATE is a software device driver for the MS-DOS operating
system running on PC-compatible computers.  Simply, this means that DOSGATE
is a software product that runs in conjunction with MS-DOS and allows the
packet-radio world to interface to the PC via an EIA-232 serial port.
Basically, the computer "console" (the keyboard and CRT) is "paralleled"
with the EIA-232 serial port.  When a remote packet-radio user types
something into his TNC, the data is entered into the system as if the user
had been sitting in front of the DOSGATE computer and typed the data on the
local keyboard.  Similarly, as data is sent to the local screen on the
DOSGATE system, the same data is sent out the EIA-232 serial port to be
sent to the remote user via the packet-radio network.

Why does one need the DOSGATE driver to use the computer as a DOS gateway
via packet radio?

The DOSGATE driver is needed to resolve packet-radio interface problems.
All problems are not solved, however, and there are some limitations.

For instance, most packet-radio users have local echo of their keyboards so
they can see what they are typing without the usual packet-radio delays.
The first problem is that most DOS systems that are not designed to be used
remotely, also have local echo of the keyboard.  If one were to simply
interface the computer with a TNC, the results would be unsatisfactory in
that the user would see each character echoed twice, once immediately as
they typed the character and again as echoed from the remote computer, but
delayed by the turnaround delays of the packet-radio network.  DOSGATE
attempts to solve this problem by cancelling the echoing of characters to
the remote port.

Another problem solved by the DOSGATE driver is knowing when a user is
connected and making the identification of the user known to the system.
This allows the system to appear to be intelligent by knowing who the user
is without forcing the user to answer a "Please Login:" prompt.
Additionally, by knowing when a user enters or leaves the system, certain
housekeeping can be performed such as checking to see if the user has any
unread mail upon entering the system and preparing the system for the next
user when the current user leaves the system.


Gateway: The ARRL Packet Radio Newsletter - Stan Horzepa, WA1LOU, Editor

         Volume 5, Number 23 - August 11, 1989 - P 3 of 4

       DOSGATE: PACKET-RADIO WINDOW TO MS-DOS COMPUTERS (Continued)

Does this mean that DOSGATE allows a user to run every piece of software
ever written for a PC?

Unfortunately, no.  DOSGATE is a software solution that is tightly coupled
with the operating system.  Any programs that bypass the operating system
and use the system BIOS or directly access the hardware will not be
compatible with DOSGATE.  This software will still work correctly for a
local user, but the remote user will be unable to make use of it.  Because
of speed and other considerations, much of today's software directly
accesses the hardware and, as such, is not compatible with DOSGATE for a
remote user.

Also, any software that simply erases the screen or uses graphics, direct
cursor addressing, or ANSI escape sequences should be considered
non-DOSGATE compatible.  By the very nature of packet radio, we have many
different types of users on the network.  Some are using C-64s with only 40
columns on their screens, some have Model 100 laptops with a limited LCD
screens, others are using Macs or ATs.  This all boils down to one thing:
for programs to be useable by the wide range of systems that appear on the
packet-radio network, all software should use only the normal printable
ASCII character set.  This means no block graphic characters, no erasing of
screens, no direct cursor addressing, etc.  If you wanted to limit DOSGATE
activities to a small group of compatible computers, then you could remove
many of these restrictions.

What can one expect from the DOSGATE system?

There is no limit to the potential of the DOSGATE system, as DOSGATE allows
the packet-radio network user to control a computer that can be very
sophisticated or very simple depending on the system configuration.  The
hardware required can be as simple as a basic PC with one floppy disk drive
or a more exotic 33-MHz, 80386 machine with a 80387 math co-processor, 16
Mbytes of memory and 600 Mbytes of disk storage!  Almost any hardware that
can be connected to the computer could be controlled via software on the
DOSGATE system.

A local Amateur Radio club uses DOSGATE to provide several services to its
members.  For example, the club membership list is on line to allow one
member to get another member's address and telephone number.  The club
newsletter editor uses DOSGATE to gather news and to allow club members an
easy method for submitting articles for the newsletter.  When the
newsletter is complete, it is placed on the DOSGATE system so that anyone
could read it.  Various club committees use the DOSGATE simple mail system
to keep in touch with members of the committee and other club members.
DOSGATE allows each member to have access to the "club computer."

An example implementation:

The DOSGATE development system now on line in Derry, New Hampshire (145.070
as NM1D-2) consists of the following hardware: PC-XT with 640 kbyte of RAM,
10 Mbyte of hard disk storage, 8087 math co-processor, Kantronics TNC 2
compatible TNC, ICOM 2-meter 25-watt transceiver, 12- volt power supply for
the transceiver, and 2-meter omnidirectional antenna.

Here is a sample of the software that is currently available to users of
the packet-radio network:

AUTOEXAM - Allows a user to "take" an Amateur Radio exam from Novice to
Extra class.  Generates a different exam for each session.

SEESATS - Generates real-time output to show where various OSCAR satellites
are currently located.  Also useful in a prediction mode to allow one to
plan for future passes.

GCIRCLE - The user inputs his latitude and longitude and the program then
outputs a custom great circle bearing and distance chart for the DXCC
countries list.

DOSMAIL - A simple (not autoforwarding) mail system, similar to a typical
PBBS that uses the standard Read, List and Kill commands.

AUTOCALL - An on-line (electronic) call sign directory that allows you to
find other Amateur Radio operators.  Type AUTOLOG NM1D and you will be
given NM1D's name, address, license class and previous call sign, if any.

REPEATER - An on-line database of repeaters in the local area.  Simply type
REPEATER 146.85 to receive a list of repeaters on the area in 146.85 MHz or
type REPEATER BOSTON to receive a list of repeaters in Boston.

HELP - Type HELP to receive a list of some of the more popular commands or
type HELP MAIL to receive help on the mail utilities.

Games - Various text-based "adventure" style games that can be played in
real time.

by Rich Bono, NM1D from NEPRA PacketEar

Gateway: The ARRL Packet Radio Newsletter - Stan Horzepa, WA1LOU, Editor

         Volume 5, Number 23 - August 11, 1989 - P 4 of 4

               NOVICE NOTCH: TCP/IP

W2KB-2, in cooperation with the Public Service Electric and Gas Company
Employees Amateur Radio Club, WA2FHZ, is now operating as a TCP/IP switch
running the KA9Q software on a Zenith Z151 computer.  The W2KB-2 switch is
located in Newark, New Jersey, and has IP address [44.64.0.55].  Presently,
ports are operational on 144.910 MHz and 223.440 MHz.  The 223.440-MHz port
is available for Novice class licensees wishing to participate in the
growing TCP/IP network.  Direct coverage of the switch includes the
northeastern New Jersey and New York City areas.  Additional information is
available on the 145.430-MHz and 224.280-MHz voice repeaters or by
packet-radio mail to W2KB@KD6TH.

from Ken Brown, W2KB

(Gateway would like to continue publicizing Novice packet-radio activity,
so if you know of any, please let me know, too. - WA1LOU)

       1990 NETWORKING CONFERENCE TO GO NORTH OF THE BORDER

The 1990 Computer Networking Conference will be a joint CRRL/ARRL
effort and will be held in London, Ontario, on September 22, 1990.

            SOFTWARE UPGRADES AVAILABLE

Here is a list of recently released upgrades to packet-radio software:

   APLINK, Version 3.81 (W5SMM's AMTOR ARQ Mailbox-PBBS combo)

   TheNode/PcNode, Version 3.23 (hot networking software by G8BPQ)

   MSYS, Version 1.05 (WA8BXN's multiuser, multiport, multifunction PBBS)

   W0RLI Mailbox, Version 10.11 (the grandaddy of PBBSs)

             CHESS TOURNAMENT IN CHECK

Chris Rendenna, KB2BBW, administrator of a chess tournament that is being
played via packet radio, has announced that the tournament is closed to any
additional players (80 players are involved at this time) and that he will
be on vacation and off the air until September 7, so players should wait
until then before trying to contact him.


SORRY, WRONG NUMBER FOR LAN-LINK

The telephone number for Joe Kasser, G3ZCZ, published in Gateway, Volume 5,
Number 21, (see article titled "LAN-LINK") was in error.  The correct
number is 301-593-6136.

from Rob Roberts, K5XA

               GATEWAY CONTRIBUTIONS

Submissions for publication in Gateway are welcome.  You may submit
material via the US mail to:

    Gateway
    Stan Horzepa, WA1LOU
    75 Kreger Drive
    Wolcott, CT 06716-2702

or electronically, via CompuServe to user ID 70645,247.  Via telephone,
your editor can be reached on evenings and weekends at 203- 879-1348 and he
can switch a modem on line to receive text at 300, 1200 or 2400 bit/s.
(Personal messages may be sent to your Gateway editor via packet radio to:
WA1LOU @ W1AW.)

The deadline for each issue of Gateway is the Saturday preceding the issue
date (which is typically a Friday).

             REPRODUCTION OF GATEWAY MATERIAL

Material may be excerpted from Gateway without prior permission,
provided that the original contributor is credited and Gateway is
identified as the source.

--
Gary W. Sanders (gws@n8emr or ...!osu-cis!n8emr!gws), 72277,1325
N8EMR @ W8CQK (ip addr) 44.70.0.1 [Ohio AMPR address coordinator]
HAM/SWL/SCANNER BBS (1200/2400/PEP) 614-457-4227

------------------------------

End of PACKET-RADIO Digest V89 Issue #191
*****************************************
25-Aug-89 01:19:24-MDT,8718;000000000000
Return-Path: <[e-mail]>
Date: Fri, 25 Aug 89 01:00:31 MDT
From: [e-mail]
Reply-To: [e-mail]
Subject: PACKET-RADIO Digest V89 #192
To: [e-mail]

PACKET-RADIO Digest         Fri, 25 Aug 89       Volume 89 : Issue 192

Today's Topics:
                NET on a Mac?
         nos.exe file formats? nos erases domain.txt
             PACKET-modem from 6809-01 ?
          Packet gateway and uucp forwarding
            Unix/BBS/gateways/etc
               Wanted ka9q Unix packet
----------------------------------------------------------------------

Date: 22 Aug 89 13:52:00 GMT
From: silver![e-mail]
Subject: NET on a Mac?

I used to see items on the net about refinements to the KA9Q code
ported to the Macintosh.  I paid no attention to them.  Now I wish
I had ...

I downloaded the bits from louie.udel.edu ... are these the latest
and greatest?  If not, can someone point me there?  Thanks.

   -- Pat Barkey  WA8YVR

      [e-mail]

------------------------------

Date: 24 Aug 89 22:02:55 GMT
From: att!watmath!julian!uwovax![e-mail]  (Mark Bramwell 1-519-661-3714)
Subject: nos.exe file formats? nos erases domain.txt

I have the Aug 89 release of NOS and I have a few questions.

I have created \DOMAIN.TXT but nos always erases it when I exit the program.
Is nos suppose to create the file itself?  How do I enter ip addresses for
people that I already know if I don't use domain.txt.

Has ftpusers changed its format?

ve3pzr password \ 7      no longer works when I connect to myself.
I can login but get permission denied on every command.

Is there a manual that describes nos?  I have the older net.exe manual from
May 89.
--


..........................................................................
.  Mark Bramwell,    VE3PZR                                              .
.                                                                        .
.  The University of Western Ontario           Bitnet:  [e-mail]  .
.  School of Business Administration           Packet:  VE3PZR @ VE3GYQ  .
.  London, Ontario, N6A 3K7                    Phone:   (519)  661-3714  .
..........................................................................

------------------------------

Date: 23 Aug 89 16:53:12 GMT
From: mcsun!sunic!ericom!radar.ericsson.se!kiere![e-mail]
Subject: PACKET-modem from 6809-01 ?

Hallo everyone. I hav a single-card computer running without OS
It is built of a M-6809 CPU, SY-6522 paralell and timer, m-6850 serial
and a ROM-monitor that can recieve S1-records for loading programs.

I wonder if anyone has some sort of source-code ( for 6809,6801 or sim)
that makes this act like a packet-modem ( with AM7910 modem-chip )

Urban Holmdahl
SM0SXA

------------------------------

Date: 23 Aug 89 09:36:21 GMT
From: sun-barr!texsun!texbell!ark!lrark!argate![e-mail]  (Richard Duncan)
Subject: Packet gateway and uucp forwarding

I am using software that I wrote under Unix for my packet gateway.  It
is compatible with RLI/MBL forwarding protocol and allows most features
of those systems, but then a more extended user interface (database,
weather wire, etc.).

Three of us are using this software here in Little Rock:  KC5JH, WB5FDP
and myself.  We are forwarding mail not only by radio but also via uucp.
This can be either via uucp to ~uucppublic or by mail.  Messages are
imported and exported into the pbbs system.

The capability exist to use the mail feature (or even posted bulletins
for national distribution) of this network for message transfer.  A
recent past discussion concerning this concept was briefly brough up
about a month ago, but our usenet feed was not fully operational.

In our current system, a message is sent to the destination system's
uucppublic.  Those files are moved into a special directory for import
into the bbs. This function can be automatic or done manually for
control of the traffic coming in.  Mail going out is not monitored at
this time putting the responsiblity on the destination operator (unless
hte mail is deleted before being forwarded).  An acknowledgement message
is then returned to the originating system that it was received and
brought into the bbs.

Now the question.  Is the acknowledgement of the message required within
the BBS software, or depend on the uucp/mail system to inform us of a
problem with the delivery?  There are other questions, but this one is
in debate between us right now. I can see justification for both.

I am also interested in any other comments/questions about handling
this packet traffic this way which could allow me good communications
with other parts of the country when HF is not as dependable.

Anyone with thoughts or comments?
                                        Rich WD5B

:------------------------------------------------------------------:
: Richard Duncan  WD5B           Packet:  WD5B @ WD5B.AR.USA.NA    :
: Little Rock, AR                BBS:     501/568-6809 (2400/1200) :
: UUCP:    ...!texbell!ark!lrark!argate!richard                    :
:------------------------------------------------------------------:

------------------------------

Date: 24 Aug 89 04:19:21 GMT
From: pitt!w2xo![e-mail]  (Jim Durham)
Subject: Unix/BBS/gateways/etc

In response to several articles I have seen on this newsgroup...

1. Here in Pittsburgh, there are 3 of us running KA9Q under Unix SysV,
   so it *does* work just fine, as Bdale said.

2. It is interesting that, under Unix, I was able to write a multi-
connect, multi-freq RLI/MBL style bbs to interface with the KA9Q code.
The KA9Q code has "hooks" called "upcalls" that allow application
programs to use the AX25, net/rom and TCP/IP support of the KA9Q
software from applications such as my bbs. Running under Unix means
that I can have many bbs processes all running simultaneously, one of
which is the forwarder, so that many people can connect, even on the
same tnc/frequency simultaneously and mail forwarding can still go
on, even if *that* is on the same frequency.

3. Regarding the Usenet interface.. I have a primitive facility
to handle Usenet mail in the bbs. Basically, I have a usenet
distribution list that is looked at whenever new mail is received
on the bbs. If the addressee's call is found in the usenet list, the
message is handed to the Unix mailer and mailed to that guy's( or gal's)
usenet address. Incoming mail from usenet has still not been worked
out. I have considered something like "bbs@w2xo", which would put
all the packet-destined mail in /usr/mail/bbs. This could be scanned
by the bbs mail daemon. However, since the address is "bbs@w2xo", there
would have to be some way for the packet mail address to be derived.
Any ideas?

4. I have also implemented a simple "rn" facility, which gets a *lot*
of use. The bbs "talks" to the KA9Q code thru IPC message queues, so
all that is necessary here is to open a pipe to "fgrep" to return
the subject lines of the articles in the newsgroup and feed the output
of the pipe up the message queues to the KA9Q process. When a person
asks to read a newgroup article, you merely open a pipe to "cat"
the article back to the bbs and stuff it up the message queue to
the KA9Q code, where it is transmitted. Makes life simple.


So, this was all to promote KA9Q's net under Unix. It works very nicely,
and a lot more can be done that under MS-DOS.. :-).

-73
Jim, W2XO  (w2xo![e-mail])

------------------------------

Date: 21 Aug 89 02:20:26 GMT
From: brutus.cs.uiuc.edu!wuarchive!texbell!ark!lrark![e-mail]  (Rick Mobley)
Subject: Wanted ka9q Unix packet

In article <[e-mail]>, [e-mail] (Bdale Garbee) writes:
> >I have this package and have not been able to get it compiled under SCO Xenix
> I run 890421.1 all the time on my Unix box... what kinds of problems are you
> having?
> Bdale, N3EUA

Where could I get a copy of this? I haven't been able to get it running either.
I get a compile error (will write it down if that would help), and can't get
past that point.
--
Ricky L. Mobley, WB5FDP                                 CIS: 70505,1157
1800 Sanford Drive #4                                   PACKET: WB5FDP @ WD5B
Little Rock, AR 72207                                   XBBS: [phone]

------------------------------

End of PACKET-RADIO Digest V89 Issue #192
*****************************************