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

Text File | 1993-12-31 | 272.5 KB | 6,038 lines

Fri,  2 Nov 90 04:30:08 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #184
To: packet-radio


Packet-Radio Digest         Fri,  2 Nov 90       Volume 90 : Issue 184

Today's Topics:
           KPC-2 to Regency HR-212 Diagram?
           TNC sources and non-return KISS

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 1 Nov 90 21:38:27 GMT
From: [e-mail]  (Peach)
Subject: KPC-2 to Regency HR-212 Diagram?
To: [e-mail]

I recently purchased a Regency HR-212 crystal transceiver.  This rig
did not come with a manual.  I want to use it as a dedicated packet
transceiver.

Is anyone out there using one of these?  If so I really need a copy
of the wiring diagram from the HR-212 mic connector to the KPC-2.
Any other hints on tuning this thing up for packet would be appreciated.

Please reply to the address below.  This is my wife's account.

Tnx & 73, Harold Peach, N4FLZ
Internet:  [e-mail]

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

Date: 1 Nov 90 17:39:06 GMT
From: wuarchive!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!levels![e-mail]
Subject: TNC sources and non-return KISS
To: [e-mail]

In article <[e-mail]>, [e-mail] writes:
>
>    Thanks to all those who have replied. We are aware of the KISS
> "param ax0 255" command, and this works fine on the version 1.1.7
> ROM which we have. The particular 1.1.6 version that we tried has
> a mailbox, which we figure could be handy (if we aren't running TCP/IP),
> but, as I said, the only way out of KISS as far as we can see is to
> disconnect the backup battery and power the TNC down. The normal
> code then executes on restart. I will disassemble the KISS code and
> compare it to the KISS sources I have, and see if I can get it to
> work that way.

> Thanks again,
> ....Ron

Hi Ron:

How does your ZMP relate to Packet Radio so far?  I recall something about
an overlay for this when going thru my ZMP docs. .  .

Ronn

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

End of Packet-Radio Digest
******************************
Date: Sat,  3 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #185
To: packet-radio


Packet-Radio Digest         Sat,  3 Nov 90       Volume 90 : Issue 185

Today's Topics:
              Pinging Phil Karn........
               TAPR TNC Sources

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 30 Oct 90 17:48:39 GMT
From: hpcc05!col![e-mail]  (Bdale Garbee)
Subject: Pinging Phil Karn........
To: [e-mail]

Try [e-mail], his Sun at home.

Bdale

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

Date: 30 Oct 90 17:48:08 GMT
From: hpcc05!col![e-mail]  (Bdale Garbee)
Subject: TAPR TNC Sources
To: [e-mail]

>Are the sources to the TAPR TNC code easily available?

No.

>And does anyone know how we can contact TAPR?

TAPR
PO Box 12925
Tucson, AZ  85732
[phone]

73 - Bdale, N3EUA, a TAPR Director

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

End of Packet-Radio Digest
******************************
Date: Mon,  5 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #186
To: packet-radio


Packet-Radio Digest         Mon,  5 Nov 90       Volume 90 : Issue 186

Today's Topics:
           TNC sources and non-return KISS

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 5 Nov 90 01:12:14 GMT
From: usc!samsung!munnari.oz.au!uniwa!vax7![e-mail]
Subject: TNC sources and non-return KISS
To: [e-mail]

> How does your ZMP relate to Packet Radio so far?  I recall something about
> an overlay for this when going thru my ZMP docs. .  .
>

   The current version of ZMP (1.6 I think -- it's been so long that I've
lost count) did YAPP transfers successfully for small files. The problem
began when the file was too big for the receive buffer: since there's
no hardware standardisation in CP/M, and I haven't implemented
CTS/RTS handshaking yet, there's no way to stop the TNC sending data.
I am thinking about a new ZMP version, so maybe that'll get done at the
same time.

....Ron

--
 Internet: [e-mail]
 ACSnet: [e-mail]
 Bitnet: [e-mail]
 UUCP  : uunet!munnari.oz!cc.curtin.edu.au!Murray_RJ

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

End of Packet-Radio Digest
******************************
Date: Tue,  6 Nov 90 04:30:06 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #187
To: packet-radio


Packet-Radio Digest         Tue,  6 Nov 90       Volume 90 : Issue 187

Today's Topics:
             56kbps modems - info please
                 G8BPQ PC/ROM
        MSYS and W0RLI tnx and help again !? (3 msgs)
              NNTP use in G1EMM
           TNC sources and non-return KISS

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 5 Nov 90 12:38:58 GMT
From: mcsun!ukc!acorn![e-mail]  (Adrian Godwin)
Subject: 56kbps modems - info please
To: [e-mail]

I have the CNC proceedings which describe the Heatherington (WA4DSY ??)
56kbps modem and am looking for more detailed constructional details.

Would somebody please point me to a source of circuits and / or PCBs ?

I've seen many references to these modems in postings from US packeteers -
is there anyone in the UK using them ? Or anything faster than 9600 bps ?
Or is there some legislation that stops us ?

Thanks,

-adrian (G7HWN)

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

Date: 5 Nov 90 21:45:22 GMT
From: att!cbnewsl!cbnewsk!cbnewsj![e-mail]  (The QRPer)
Subject: G8BPQ PC/ROM
To: [e-mail]

I was looking through the floppies that came with my DRSI board
the other day and noticed one marked PC/ROM by G8BPQ.  Is this
software supposed to give functionality equivalent to NET/ROM
or TheNet software?  If so, how does one set it up?  The
documentation isn't all that clear--or maybe I just don't
understand!

Thanks in advance.

73,
Bob K2PH

--
=========================================================================
Bob Schreibmaier K2PH  | UUCP: att!oblivion!k2ph or [e-mail]
AT&T Bell Laboratories | ARPA: [e-mail]
Lincroft, N.J. 07738   | ICBM: 40o21'N, 74o8'W

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

Date: 5 Nov 90 15:56:00 GMT
From: usc!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!levels![e-mail]
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

Thanks to all those who replied to my request for help on BBS software.
:-) I received volumes of very useful and informative comments and opinions!

We are currently evaluating MSYS V1.08, and it seems fine ! the only problems
we've had so far are small but annoying. Specifically

- When mail is received by MSYS via SMTP, the subject is the dest address
  ie in BM send mail to ALL@VK5NET, subject on MSYS becomes ALL@VK5NET.

- When you do that, and the distribution tables tell MSYS to send you back
  messages that are @VK5NET, you get it back again, etc etc etc etc ...

- How do I get bulletins addresses to ALL@VK5NET sent to my NOS node as
  VK5ZEU@VK5ZEU ?, ie can we spray the bulls out to all SMTP nodes addressed
  correctly ? or to a second address at that node eg BULL@VK5ZEU ?

- Does MSYS support SLIP ? a config file that was distributed with it suggests
  that it can, and defines a port as 'name slip link' but the only way we
  can even get it to look like its working to a NOS node is to setup the NOS
  for AX25 as the link type. So is it SLIP or just 'SerialAX25', it doesnt
  matter to us, but it doesnt say anything in the manual that we can find.

- Is telnet only for chat, can you connect to MSYS BBS using Telnet ?? we
  havent succeeded in doing it so far, again the manual isnt very specific...

- Is there any option for providing Xmodem download? Not that we will want
  this feature after there are more than 2 of us on IP, but as a kick start
  for people to get the code, it would be handy.

On these last 2 points, It seems strange that a BBS that is IP capable, would
have only AX25 BBS connections, surely where people are using IP, they have
their own freq allocation, and pure IP traffic would be preferrable to
having ax25 and IP mixed ??

** We would also like to evaluate W0RLI BBS, so if anyone has an FTP site
listed for it, I'd sure appreciate it if you could forward the sitename on !

+-Rob Mayfield-(VK5ZEU)----------------Australian Submarine Corporation------+
| Internet1 : [e-mail]     Internet2 : <problems with this one>  |
| Applelink : AUST0177                 AMPR      : VK5ZEU @ VK5WI.#SA.AUS.OC |
| AMPR-TCPIP: 44.136.171.1             VK5 AMPRIP: Address Coordinator       |
| Priv.Mail : Post Box 46, Henley Beach, South Australia, 5022               |
+--Views expressed in my correspondence are my own, unless otherwise stated--+

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

Date: 5 Nov 90 15:57:54 GMT
From: [e-mail]  (Brian Kantor)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

Yes, it's puzzling to me too that the MSYS bbs can't be accessed with
TELNET; it's a wierd shortcoming.

You'll note an interesting protocol violation when you disconnect from
the MSYS AX.25 port; you ALWAYS get a retry.  That's because the program
goes into disconnect mode BEFORE it acknowledges the packet containing
the disconnnect; you then time out and resend the packet and get a DM
back that actually disconnects you.  It's bizarre - it's apparently
taking a shortcut in the protocol state machine somehow.  Minor.

There are also some other wierdnesses - but nothing major.  I suspect
that if the author of MSYS were to distribute the source, he'd find a
LOT of people who'd make some really nifty additions to it, and fix the
bugs.  Dunno whether it's that he's hoping some day to make money off
it, or whether it's just the fatherhood thing.  It's a nice piece of
work.  There are several of them running in SoCal.

What I've been experimenting with lately is running G8BPQ on a PC to
provide the unwashed with a familiar interface, but having one selection
be "NOS", and allowing access to NOS running on the same host that way.
Thus unsophisticated users see something approximating a net/rom node
that they can use in a simple and straightforward manner, but the more
adventurous can connect to NOS and get to telnet, the mailbox, etc.
This is a nice way to do it because I can customize NOS any way I need
to, and I don't need a multitasker.  Furthermore, by making the NOS
console remotely accessable, I can start and stop NOS whenever I need to
without damaging the ability of the site to continue to forward net/rom
traffic - essential in virtual-circuit networks that can't route around
outages.
    - Brian

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

Date: 6 Nov 90 02:36:37 GMT
From: usenet.ins.cwru.edu!ncoast![e-mail]  (Brandon S. Allbery KB8JRR)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

As quoted from <[e-mail]> by [e-mail]:
+---------------
| We are currently evaluating MSYS V1.08, and it seems fine ! the only problems
| we've had so far are small but annoying. Specifically
+---------------

MSYS is currently at 1.09 and has at least one patch available over that.
(I'm quite certain of this; see my .sig for the reason.)

+---------------
| - Is telnet only for chat, can you connect to MSYS BBS using Telnet ?? we
|   havent succeeded in doing it so far, again the manual isnt very specific...
+---------------

Only for chat, I fear.  I'd like this to change as well.

+---------------
| - Is there any option for providing Xmodem download? Not that we will want
|   this feature after there are more than 2 of us on IP, but as a kick start
|   for people to get the code, it would be handy.
+---------------

I've been noodling this; the problem is that AX.25 TNCs can't deal with binary
data except in KISS mode --- in which case you probably might as well be
running NOS or MSYS anyway.  And even if you did, anyone monitoring the
frequency is going to have *weird* things happening to their display while
you're downloading a binary file.

The best way to deal with this is to allocate an AX.25 protocol value for
AX.25 binary file transfer, and arrange for TNCs to translate such packets to
and from some common protocol like x/y/zmodem or Kermit.  Or a simple KISS
mode program that emulates such a TNC.

+---------------
| On these last 2 points, It seems strange that a BBS that is IP capable, would
| have only AX25 BBS connections, surely where people are using IP, they have
| their own freq allocation, and pure IP traffic would be preferrable to
| having ax25 and IP mixed ??
+---------------

"Surely" not.  We run TCP/IP, NET/ROM, and straight AX.25 on the same
frequencies around here.  This probably had a big effect on how MSYS was
written.

(P.S.  Send me netmail and I'll see if I can get it to Mike.)

++Brandon
--
Me: Brandon S. Allbery                      VHF/UHF: KB8JRR on 220, 2m, 440
Internet: [e-mail]                Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR                      AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY

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

Date: Mon, 05 Nov 90 08:29:03 EST
From: Joseph Skoler <[e-mail]>
Subject: NNTP use in G1EMM
To: [e-mail]

Would some kind soul please explain how to use the NNTP function in
G1EMM.

I set it up using my own system as a host, as well as another's, but
both times ,after kicking NNTP, got the msg:
NNTP daemon entered, tagget = kc2yu
NNTP kc2yu:nntp Connect failed: Reset/Refused

What am I missing?

Thanks,
Joseph Skoler,  KC2YU
[e-mail]
[e-mail]
[e-mail]  [44.68.32.56]
[e-mail]

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

Date: 5 Nov 90 15:07:20 GMT
From: usc!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!levels![e-mail]
Subject: TNC sources and non-return KISS
To: [e-mail]

In article <[e-mail]>, [e-mail] writes:
>> How does your ZMP relate to Packet Radio so far?  I recall something about
>> an overlay for this when going thru my ZMP docs. .  .
>>
>
>    The current version of ZMP (1.6 I think -- it's been so long that I've
> lost count) did YAPP transfers successfully for small files. The problem
> began when the file was too big for the receive buffer: since there's
> no hardware standardisation in CP/M, and I haven't implemented
> CTS/RTS handshaking yet, there's no way to stop the TNC sending data.
> I am thinking about a new ZMP version, so maybe that'll get done at the
> same time.
>
> --

I only have seen a package of overlays for 1.6 locally.  CanI get the 1.6 ZMP
from Znode 62??  Or where can I get it if Lindsay doesn't have it?

Ronn  (Current 1.5 user)

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

End of Packet-Radio Digest
******************************
Date: Wed,  7 Nov 90 04:30:02 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #188
To: packet-radio


Packet-Radio Digest         Wed,  7 Nov 90       Volume 90 : Issue 188

Today's Topics:
                  DSY xtals?
        MSYS and W0RLI tnx and help again !? (2 msgs)
              NNTP use in G1EMM

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 7 Nov 90 04:34:49 GMT
From: uupsi!sunic!news.funet.fi!ousrvr!ousrvr![e-mail]  (Ari Husa OH8NUP)
Subject: DSY xtals?
To: [e-mail]

I've finally ordered the DSY 56 kbit modem - now it is just to wait..
and wait.. and wait (hopefully not for long).

To save time, I'd like to order the necessary frequency determining
crystals in advance. So, please, someone with the documentation handy,
e-mail me how to determine the frequency and type of the crystals.

If you know a reasonably-prized place to purchase them, it would be
appreciated as well.

Thanks,

    Luru
--
    ///
    o-o    Ham Radio Operators Do It In Higher Frequency
     o

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

Date: 7 Nov 90 00:18:43 GMT
From: usc!wuarchive!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!uniwa!vax7![e-mail]
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Brandon S. Allbery KB8JRR) writes:
> +---------------
> | - Is there any option for providing Xmodem download? Not that we will want
> |   this feature after there are more than 2 of us on IP, but as a kick start
> |   for people to get the code, it would be handy.
> +---------------
>
> I've been noodling this; the problem is that AX.25 TNCs can't deal with binary
> data except in KISS mode --- in which case you probably might as well be
> running NOS or MSYS anyway.  And even if you did, anyone monitoring the
> frequency is going to have *weird* things happening to their display while
> you're downloading a binary file.
>

   Perhaps I have it all wrong, but it seems to me that (unless you
convert the file to ASCII, in which case it takes twice as long to send),
ANY binary file transfer (YAPP, XMODEM, TCP/IP or whatever) is bound to
put *weird* things on the screen of anybody monitoring the frequency.

If they don't like it, they have several choices:
1. Turn their computer/terminal off and go and watch TV;
2. Only monitor packet types and not the contents as well (the MYOBB
   approach);
3. Put useful things like ESC and screen-clear sequences in the MFILT
   list.

....Ron

--
 Internet: [e-mail]                | "This brain is
 ACSnet: [e-mail]                      | intentionally
 Bitnet: [e-mail]    | left blank"
 UUCP  : uunet!munnari.oz!cc.curtin.edu.au!Murray_RJ |

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

Date: 7 Nov 90 03:54:49 GMT
From: netcom![e-mail]  (Morris Jones)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

[e-mail] (Brandon S. Allbery KB8JRR) writes:
> +---------------
> | - Is there any option for providing Xmodem download? Not that we will want
> |   this feature after there are more than 2 of us on IP, but as a kick start
> |   for people to get the code, it would be handy.
> +---------------

Brandon, Ed Greenberg and I swap files often by using UUENCODEd data.  It's
not a terribly inefficient technique if you make a ZIP of the files you want
to send, then uuencode it, then just dump and capture the data stream.  AX.25
is generally an adequate protocol for data protection, I wouldn't even be
too concerned about verifying the data.  However the ZIP file format also
has check codes to insure file integrity.

73, Mojo AA4KB
--
[e-mail]          Site Coordinating Instructor, San Jose South
Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
Campbell, CA              800-675-5559 ... 800-CC-RIDER

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

Date: 7 Nov 90 01:33:05 GMT
From: bionet!agate!shelby!msi.umn.edu!cs.umn.edu!uc!shamash![e-mail]  (Jeff Comstock)
Subject: NNTP use in G1EMM
To: [e-mail]

In article <[e-mail]> [e-mail] (Joseph Skoler) writes:
>Would some kind soul please explain how to use the NNTP function in
>G1EMM.
>
>I set it up using my own system as a host, as well as another's, but
>both times ,after kicking NNTP, got the msg:
>NNTP daemon entered, tagget = kc2yu
>NNTP kc2yu:nntp Connect failed: Reset/Refused
>
>What am I missing?

I would have to say that kc2yu is not running an nntp server.  The
standard G1EMM ( and KA9Q and PA0GRI as well ) do not contain
NNTP servers, only the NNTP client.  If you want to add an NNTP
server to nos, get pub/ka9q/incoming/nn901027.zip.  It was
developed using KA9Q NOS, so I would be glad to hear how it 'ports'
over to G1EMM.

Jeff - NR0D

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

Date: Tue, 6 Nov 90 23:08 GMT
From: "The Bandit, EI7DNB" <[e-mail]>
To: [e-mail]

Help!!

I was out in the CQ WW recently and we used K1EA. Because this was our
first time using a computer on site, we decided to use it off-line.
I must say the program is brillant, and I cant wait till the next contest
when we use it on line....

But we were running it on a PC with only 640K and once we broke the
5,000 QSO mark the thing ran out of memory.

So, I got a PC with 2 Meg's  of memory and  went to throw the rest of
the contacts in and when I loaded it up - I got a screen which
looked like : -


  0 ALL                   0   ________
  0 ALL                   0   ________

When I type in a call, the line flashs up as normal once I press the
return key, and goes back to the ALL thing again.

Now, the date for sending in the log is getting closer all the time and
a few members of the group are getting nervous, so :

- Is there something wrong with my PC??
- Is there a bug in the copy of the program I have,
- or, have I done something to upset the program (I did reinstall it from
      the original disk....)

I would be most grateful if someone could help or susgest something which
I could try and any comments could be helpful.

Thanks in advance,

John, EI7DNB

I would prefer e-mail but additions to the digest is fine.....

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

End of Packet-Radio Digest
******************************
Date: Thu,  8 Nov 90 04:30:07 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #189
To: packet-radio


Packet-Radio Digest         Thu,  8 Nov 90       Volume 90 : Issue 189

Today's Topics:
         MSYS and W0RLI tnx and help again !?
         PAC-COMM NB-9600 Modem Modification

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 8 Nov 90 04:38:26 GMT
From: ddi1!lrark![e-mail]  (Rick Mobley)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

 >
 >73, Mojo AA4KB
 >--
 >[e-mail]          Site Coordinating Instructor, San Jose South
 >Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
 >Campbell, CA              800-675-5559 ... 800-CC-RIDER

Could that be the same Mojo that once lived in Memphis? Send e-mail and bring
me up to date on whats happening. I get a chance to talk to LC W5TNT at times.


--
[e-mail]       *    bang path --> uunet!ddi1!lrark!rick    *
Ricky Mobley          *          LRTUG [phone]             *
1800 Sanford Dr. #4   *    GEnie Unix RT SysOp address LRARK      *
Little Rock, AR 72207 *     WB5FDP.AR.USA.NA wb5fdp.ampr.org      *

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

Date: 7 Nov 90 14:27:13 GMT
From: hpcc05!hpdmd48![e-mail]  (Steve King)
Subject: PAC-COMM NB-9600 Modem Modification
To: [e-mail]

Here is the modification I made to my PAC-COMM NB-9600 modem.  This mod
got rid of all the garbage calls in my mheard list both when using the
TNC in standard mode as well as while using net/nos software packages.
This modification makes sure that the modem will send all zeros to the
TNC until the modems PLL is locked on a signal.  This means that the
TNC will not be reading garbage comming in to the UART all the time.


I removed the socket for U11 (74HC14) and inserted the 74HC14 directly into
the PC board.  I then lifted all the pins of a 74HC00 except 7, 12 and 14.
These lifted pins were carefully bent so they were pointing straight out.
I cut back the bent pins so the 74HC00 can be piggybacked on the 74HC14.
Without removing the socket on  U11, I would not have ben able to slide
the modem and Tiny-2 back into the box (you may not have this problem).

I cut the trace from U11 pin 12 to U20 (74HC157) pin 13.  I soldered the
74HC00 on top of U11 (soldering pins 1, 12 and 14). I wired U10 pin
13 (LM339) to the 74HC00 pins 9 and 10.  I wired 74HC00 pin 8 to pin 13.
Pin 12 of U11 was connected to pin 12 of the 74HC00 when I piggybacked it.
I connected pin 11 of the 74HC00 to pin 1 and 2 of the 74HC00.  I connected
pin 3 of the 74HC00 to pin 13 of U20 (74HC157).  I think thats it.

Theory of operation:

The DCD signal comming from U10 (LM389) is low true so I invert it using
one of the nand gates (pins 8, 9 and 10).  This is used to qualify the
RXD signal from the 74HC14 (pin 12). Pin 11 of the 74HC00 is the RXD signal
(low true) qualified by the DCD signal which is LOCK DETECT.  One more
inversion of this signal (74HC00 pins 1, 2 and 3) and I have the qualified
RX DATA signal which is connected to U20 (74HC157) pin 13.

RX DATA is always zero until the PLL is locked to the data.  Then RX DATA
will be the true data comming from the unscrambler or zeros if we are not
locked.

Before making this change, my mheard was always full of random garbage.
After the change, my mheard is clean and my RXErrors is not increasing
at a rate of about 200 errors per minute.
PAC-COMM said that their firmware uses DCD to determine if the channel is
clear and not to determine if the data is valid.  This may not be true
for all versions of firmware available.

Anyway, there you have it.  Three gates later and I am much happier.
The 9600 baud modem seems to work very well.  I have not tested it under
any marginal situations.  The other station (who also has the mod) is
about 4 miles away and the signal seems too strong to determine how well
the modem works under weak signals.  From this distance I seldom see
a retry.

Steve King

Steve King   (KD7RO) [e-mail]
         Hewlett Packard
         Boise, Idaho

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

End of Packet-Radio Digest
******************************
Date: Fri,  9 Nov 90 04:30:10 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #190
To: packet-radio


Packet-Radio Digest         Fri,  9 Nov 90       Volume 90 : Issue 190

Today's Topics:
         MSYS and W0RLI tnx and help again !?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 8 Nov 90 04:38:48 GMT
From: hpl-opus!hpnmdla![e-mail]  (Alan Bloom)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

In rec.ham-radio.packet, [e-mail] writes:

...
>ANY binary file transfer (YAPP, XMODEM, TCP/IP or whatever) is bound to
>put *weird* things on the screen of anybody monitoring the frequency.

>If they don't like it, they have several choices:
>1. Turn their computer/terminal off and go and watch TV;
>2. Only monitor packet types and not the contents as well (the MYOBB
>   approach);
>3. Put useful things like ESC and screen-clear sequences in the MFILT
>   list.

My Kantronics TNC has a filter mode to delete all non-ASCII characters
when monitoring.  Don't TNC-2's have the same feature?

AL N1AL

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

End of Packet-Radio Digest
******************************
Date: Sat, 10 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #191
To: packet-radio


Packet-Radio Digest         Sat, 10 Nov 90       Volume 90 : Issue 191

Today's Topics:
           Questions, questions, questions
       Where is 70cm packet? Where is 2400baud packet?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 10 Nov 90 01:32:17 GMT
From: voder!pyramid!infmx![e-mail]  (Randall Rhea)
Subject: Questions, questions, questions
To: [e-mail]

In article <[e-mail]> [e-mail] (Jerome Kaidor) writes:
>In article <[e-mail]> [e-mail] (Jim Grubs) writes:
>>I wish to ask a fundamental question. Why are there so many questions on this
>>newsgroup (and the Fidonet HAM and PACKET echoes) on "How do I plug in the
>>power cord?" or "Why isn't the documentation more specific on whether the
>>machine screws tighten clockwise or counter clockwise?

I understand that an experienced ham would get tired of simple questions.
However, those of us who are new hams ask dumb questions without knowing
that they're dumb.  I hope that we don't discourage anyone from asking
questions on the net, for fear that someone will think it's "stupid."

... and I don't really buy the argument of "I learned about power supplies
when I stepped on a 600V one accidently. Ouch!"  We learn a lot from the
"school of hard knocks", but frankly, I would rather someone tell me
something on the net before I get electrocuted.




--

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Randall Rhea                                          Informix Software, Inc.
Senior Programmer/Analyst, MIS                    uunet!pyramid!infmx!randall

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

Date: 9 Nov 90 19:35:17 GMT
From: att!cbnewsc![e-mail]  (ted.g.kekatos)
Subject: Where is 70cm packet? Where is 2400baud packet?
To: [e-mail]

Fellow packeteers,

I have been hunting for 70cm packet in the Chicago area.
I have not heard any activity.

I have also been listening for 2400 baud activity on 2m and 70cm.

Does anyone have any info.





Ted G. Kekatos           Amateur Radio N9IXE
Packet: N9IXE @ WB9MJN.IL.USA.NA
INTERNET:  [e-mail]
UUCP: ..!att!ihlpl!tedk                       [phone]
AT&T Bell Laboratories, Indian Hill, IH-6T-206
2000 North Naperville Road.
Naperville, Illinois. 60566 USA

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

End of Packet-Radio Digest
******************************
Date: Tue, 13 Nov 90 04:30:10 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #192
To: packet-radio


Packet-Radio Digest         Tue, 13 Nov 90       Volume 90 : Issue 192

Today's Topics:
        MSYS and W0RLI tnx and help again !? (2 msgs)
        standard mark/space freqs, direct fsk
              Unix Ports of Net
             Which TNC? (4 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 12 Nov 90 15:29:48 GMT
From: sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!cci632![e-mail]  ( co-op)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

In rec.ham-radio.packet, [e-mail] writes:
>ANY binary file transfer (YAPP, XMODEM, TCP/IP or whatever) is bound to
>put *weird* things on the screen of anybody monitoring the frequency.

We encountered this here in Rochester, especially with people who
like to leave printers online monitoring 24 hrs/day.  One of us
had an IP address with a 12 in it (formfeed), I guess, and the guy
lost a whole box of paper in one night.

Isn't there also MNONAX25, which doesn't pass through anything with
other than a "no layer three" PID ?

I don't have a strong enough synonym for the word "idiot" to describe
the schmo's who told me to stop using tcp/ip because it screwed up
their screens.  Every once in a while I think that, if I were the IP
coordinator, most addresses would contain formfeeds, bells, and ANSI
escape sequences to make the whole screen go into flashing mode.  (Not
really, it's just an evil thought that's crossed my mind :-) ).

                        Chris

P.S. We just got PSI e-mail service -- anybody who reads this message,
please send a response to [e-mail]  I really want to know
from what parts of the network this address is useful.

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

Date: 13 Nov 90 03:36:20 GMT
From: envy![e-mail]  (Phil Karn)
Subject: MSYS and W0RLI tnx and help again !?
To: [e-mail]

In article <[e-mail]>, [e-mail] ( co-op) writes:
|> I don't have a strong enough synonym for the word "idiot" to describe
|> the schmo's who told me to stop using tcp/ip because it screwed up
|> their screens.

Amen!!

I once got into an on-the-air voice argument with somebody who felt
that way (the immediate context was either NET/ROM headers or binary
file transfers, not TCP/IP, but the idea was the same). I replied that
by the very same reasoning, a neighbor with RFI in his stereo could
ask him to stay off the air, even if the fault were to lie completely
with the stereo.

I explained that if several signals sharing the spectrum carry
"something" that distinguishes wanted information from unwanted
information and a receiver doesn't make use of it, then you can hardly
blame the transmitters for any problems that result. It doesn't matter
whether the "something" is a different frequency allocation or a
protocol ID, you can only fix the problem at the receiver!

He got *very* upset and refused to accept the analogy, mainly because
I think he knew that it was a very good one. But I never heard any more
complaints from him.

Phil

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

Date: 12 Nov 90 22:07:40 GMT
From: convex!texsun![e-mail]  (Monty Wilson)
Subject: standard mark/space freqs, direct fsk
To: [e-mail]

I am building a packet radio transceiver for the 10m band and I would
like to hear from anyone who has tried to use direct FSK rather than
audio tones into an LSB transmitter for this purpose.  I understand
that on HF packet the shift is 200 Hz rather than 170 Hz, but can
anyone tell me what the two tones are (in Hz off the carrier)?  I am
currently checking to see whether my friend's TNC (It's an MFJ 1270B,
similar to the 1274 but without tuning LEDs) has direct FSK output.
If it does, or if an easily accessible internal signal can be tapped,
I would like to use it to directly swing a transmit oscillator in my
transceiver, since it doesn't do sideband.  Thanks,
..........Monty WB5NVM.

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

Date: 12 Nov 90 09:34:02 GMT
From: van-bc!ubc-cs!nebulus!nebulus.ampr.org![e-mail]  (Dennis S. Breckenridge)
Subject: Unix Ports of Net
To: [e-mail]

I am looking for any hams that have worked on the UNIX port of
the KA9Q net program. I have most of it working, but I am stumped
with the telunix (telnet) problem I have. I am running a real old
version of NET and I would like to know where the latest and greatest
fixes live. I have heavily modified bm and xobbs to run clean on
an AT&T SVr3.2 machine.
73's

--
-----------------------------------------------------------------------------
      Dennis S. Breckenridge VE7TCP [44.135.160.59]  dennis@nebulus
           EMACS: Twelve Megabytes And Constantly Swapping!
-----------------------------------------------------------------------------

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

Date: 12 Nov 90 15:30:01 GMT
From: world!ksr![e-mail]  (Tom Varga)
Subject: Which TNC?
To: [e-mail]

Hi all,

    I've recently gotten very interested in getting involved with
packet. I've read the ARRL book on packet so at least I'm familiar
with the terminology.

    My basic question is which TNC should I consider buying?  I
have a macintosh SE/30 and also a Toshiba laptop and probably would
like to use both of these.  I also have an IC-24AT and am wondering if
I might be able to use this to at least start out with.

    Although it seems that 1200 baud is what is mostly available,
I can't imagine such a sloooow rate and would probably go out of my
mind.  (I'm spoiled since I have a workstation on my dest at work :)
Anyway, I don't mind starting out at 1200 baud but would like to have
an easy path to 2400 and preferably 9600 baud.  Is there such a beast
available?

    Finally, if I'm interested in TCP/IP and require KISS mode,
are'nt most TNC's overkill since it seems like KISS is almost a
straight connection to the modem.

    Which brings up the final question.  With today's PC's getting
quite powerful, it would make more sense put all 'firmware' into
software on the PC and drive the modem directly.  Certainly my SE/30
is fast enough to do even 9600 baud.  Does this exist or am I just
dreaming?

Thanks in advance,
Tom
--
================================================================================
= Tom Varga N2UA/1        617-895-9415        [e-mail]        uunet!ksr!tom =
=   There's never time to do it right, but there's always time to do it over.  =
================================================================================

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

Date: 12 Nov 90 22:11:21 GMT
From: usc!cs.utexas.edu!oakhill!dover!nddsun1![e-mail]  (Mark Monninger)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Tom Varga) writes:
>
>       ...  stuff deleted ...
>
>       Which brings up the final question.  With today's PC's getting
>quite powerful, it would make more sense put all 'firmware' into
>software on the PC and drive the modem directly.  Certainly my SE/30
>is fast enough to do even 9600 baud.  Does this exist or am I just
>dreaming?
>
>        ...  more stuff deleted ...

I've also wondered why this couldn't be done. Certainly a Mac or PC of the
AT class would be able to handle it. As I understand it, a TNC is just a
data packager that takes keyboard input, assembles it into AX.25 packets,
and sends it to a modem, and the opposite on the incoming (receives packets
from the modem, extracts the data and displays it). Can any of you packet
wizards enlighten us?

Any information on this would be greatly appreciated.

Thanks,

Mark    KG7JL

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

Date: 13 Nov 90 03:13:28 GMT
From: envy![e-mail]  (Phil Karn)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Tom Varga) writes:
|>      Finally, if I'm interested in TCP/IP and require KISS mode,
|> are'nt most TNC's overkill since it seems like KISS is almost a
|> straight connection to the modem.

Yes, they are. At the time we began our on-the-air experiments with
TCP/IP, we (K3MC, WB6RQN and I) devised the KISS TNC only because
we didn't all have HDLC interfaces directly on the computers we wanted
to use. Adapting existing TNCs to the job seemed like an expedient,
short-term solution.

We never expected it would become a de-facto standard. (Neither did
the Canadians expect in 1979 that the then-already-obsolete-and-surplus
Bell 202 modems they chose as a stopgap until better modems were ready
would become the standard for all of amateur packet radio...)

|>      Which brings up the final question.  With today's PC's getting
|> quite powerful, it would make more sense put all 'firmware' into
|> software on the PC and drive the modem directly.  Certainly my SE/30
|> is fast enough to do even 9600 baud.  Does this exist or am I just
|> dreaming?

It not only exists, but it is widely used. One company (DRSI) has a
product line based almost entirely on HDLC adaptor boards that plug
directly into PCs, making external TNCs (KISS or otherwise)
unnecessary. Similar boards are also available from several other
sources, including PACCOMM and HAPN. I travel with one installed in my
laptop. I just plug the laptop into my Icom HT, and I'm on the air.

You're quite right. The "TNC" was an appropriate idea about 10-15
years ago, when even the most computer-oriented ham had at most a
"dumb terminal", a 300 baud phone modem and perhaps a large S-100
system.  Nowadays, with something like half of the ham population
having more modern personal computers of some sort, the TNC concept is
an anachronism that should be done away with, along with 1200 baud
AFSK. But with an amateur population that still thinks of 1200 baud
packet as "fast" (perhaps it is, when compared to 60 WPM Baudot RTTY),
it's hard to make progress...

Phil

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

Date: 13 Nov 90 03:20:16 GMT
From: netcom![e-mail]  (Morris Jones)
Subject: Which TNC?
To: [e-mail]

[e-mail] writes:
>       I've recently gotten very interested in getting involved with
>packet.

Welcome!

>       My basic question is which TNC should I consider buying?  I
>have a macintosh SE/30 and also a Toshiba laptop and probably would
>like to use both of these.  I also have an IC-24AT and am wondering if
>I might be able to use this to at least start out with.

No problems for either.  All you need is a simple terminal program.

>       Although it seems that 1200 baud is what is mostly available,
>I can't imagine such a sloooow rate and would probably go out of my
>mind.  (I'm spoiled since I have a workstation on my dest at work :)
>Anyway, I don't mind starting out at 1200 baud but would like to have
>an easy path to 2400 and preferably 9600 baud.  Is there such a beast
>available?

It's not so awful at 1200.  I'm having a good time.  If you want to ragchew,
of course it makes no difference what baud rate you're using, as long as
it's faster than your typing.  :)

I have the understanding that 2400 is really a waste of time.  The modems
are using the same protocols as the telephone modems, and they're optimized
for telephone connections where the frequency control is a little better.
Or so I'm told.  But I don't know of much 2400 baud traffic here in San
Jose.

9600 on the other hand requires a much greater commitment and expense.  The
modulation technique in use currently involves frequency shifting a crystal,
and you can't use it with a synthesized rig.  Kantronics is selling a digital
radio specifically for this use.  It has two crystal channels, runs two
watts, and sells for about $200.  It's the DVR2-2.

Then you need a TNC that will support a 9600 baud modem, and I think that
means (at the moment) the Kantronics Data Engine.  They're a little pricey
for me.

>       Finally, if I'm interested in TCP/IP and require KISS mode,
>are'nt most TNC's overkill since it seems like KISS is almost a
>straight connection to the modem.

Well KISS isn't exactly a direct connection to the modem.  The TNC CPU is
still used to frame packets, check DCD, and a two-way data buffer.  The
only difference is the ROM, so the hardware isn't any cheaper.

>       Which brings up the final question.  With today's PC's getting
>quite powerful, it would make more sense put all 'firmware' into
>software on the PC and drive the modem directly.  Certainly my SE/30
>is fast enough to do even 9600 baud.  Does this exist or am I just
>dreaming?

Frankly it doesn't make sense at all.

Back in 1980, I converted my TRS-80 model 1 into a dedicated packet
terminal.  It drove a Western Digital SDLC packet controller chip, and I
adapted software written by the Vancouver Amateur Digital Communications
Group to run on the TRS-80's Z-80.  This is essentially what's going on
now with the TCP/IP software.

The problem is that you give up doing anything else with your computer.

Typically I use Procomm to speak to my TNC.  With Procomm I can run a split
screen CHAT mode, I can capture data to disk, I can read a string of
bulletins then scroll back and read them at leisure.  Other packet terminal
programs have been written to capture different data streams or connections
to different screens.  When you dedicate the computer to doing packet I/O,
you really give up all that flexibility.

Sure you can write those features into TCP/IP programs, but that means that
everyone has to do it *your* way.  Instead of picking between several
varieties of terminal programs, I only have the one available, unless I want
to hack on the NET code myself.  I can't add a widget to my computer that
does something interesting to this nice data pipe that I've attached.
There's nowhere to put it.

At my station I use the AEA PK-88.  In some ways I regret buying this unit,
because it won't support 9600 baud.  But in most ways I'm tickled pink with
it.  The software ROM is rock solid (a couple of known bugs are well
documented by other people).  It has a very good maildrop with reverse
forwarding to full-service BBSes available.  And I bought one off the shelf
for $120 at Quement Electronics.

And to me, best of all, I can shut off the computer, or use it to do other
things, and my TNC sits quietly under the radio sending my beacon, or
getting messages from friends.  This is the kind of multi-processing I
really appreciate.

Let us know ...

73, Mojo AA4KB

--
[e-mail]          Site Coordinating Instructor, San Jose South
Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
Campbell, CA              800-675-5559 ... 800-CC-RIDER
AA4KB @ N6LDL.#NOCAL.CA.USA.NA / aa4kb.ampr.org / netcom![e-mail]

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

Date: Mon, 12 Nov 90 13:59:34 EST
From: "Ken Wieringo [e-mail]" <[e-mail]>
To: [e-mail]

Help msg? I don't reconigise This address.army.mil for I-packrad???? Ken

[e-mail]>>ALSO .CC.VT.EDU >>AND IP 128.173.4.1
PHONES COMMERCIAL AND SCATS 703-857-7584>>FAX [phone]<<
SYSM AT UVA MERCURY U820 >>  IBMMAIL(USVPITMA) <<
2M PACKET AX.25 N4LYO @ N4MGQ.VA.24015.USA>>ARMY MARS AAT3PK/VA TEXN<<
ROANOKE VALLEY GRADUATE CENTER
POST MAIL: 117 W. CHURCH AVE.
ROANOKE, VA. 24011-1905

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

End of Packet-Radio Digest
******************************
Date: Wed, 14 Nov 90 04:30:06 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #193
To: packet-radio


Packet-Radio Digest         Wed, 14 Nov 90       Volume 90 : Issue 193

Today's Topics:
     Can Digicom be made to run on other Commodore machines ????
             Which TNC? (4 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 13 Nov 90 21:55:11 GMT
From: swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!comp.vuw.ac.nz!cc-server4.massey.ac.nz![e-mail]  (Giovanni Moretti)
Subject: Can Digicom be made to run on other Commodore machines ????
To: [e-mail]

Some friends of mine have sent me the following letter but
unfortunately as my hardware expertise is oriented towards 8051/6809
uP, I can't help them but you might ...

"...Digicom and its variations runs on a C64 (nearly 39k) and we would
like it to run on a Commodore Business Machines 4032 (40 column, 32K),
a 8032 (80 column, 32K), an 8096 (80 column, 96K) or a PET with 32K.

There are literally dozens of these machines about and they would be
ideal for Packet if Digicom can be made to run on them.  They all use
the 6502 CPU and comparable VIAs etc and run on a similar manner.

My information reveals that the different use of the Kernal entry
points is the major factor.  Also the limit of 32K of memory may be a
problem in the later versions of Digicom but may not be a problem in
earlier versions

73s Ian ZL1BKZ"

So how about it - seems like it would be possible (from one who avoids
C64s like the plague :-)

Seems a pity to waste all that hardware ...

Any help would be much appreciated.

Thanks
Giovanni ZL2BOI

--
------------------------------------------------------------------------------
Giovanni Moretti, Consultant       | [e-mail], Pkt-ZL2BOI@ZL2BFJ
Computer Centre,  Massey University| Ph 64 63 69099 x8398, FAX [phone]
Palmerston North, New Zealand      | QUITTERS NEVER WIN, WINNERS NEVER QUIT
------------------------------------------------------------------------------

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

Date: 13 Nov 90 15:48:31 GMT
From: crdgw1!trub![e-mail]  (Donald P Perley)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>[e-mail] writes:

>>      Which brings up the final question.  With today's PC's getting
>>quite powerful, it would make more sense put all 'firmware' into
>>software on the PC and drive the modem directly.  Certainly my SE/30
>>is fast enough to do even 9600 baud.  Does this exist or am I just
>>dreaming?
>
>Frankly it doesn't make sense at all.
>
>Back in 1980, I converted my TRS-80 model 1 into a dedicated packet
>terminal.  It drove a Western Digital SDLC packet controller chip, and I
>adapted software written by the Vancouver Amateur Digital Communications
>Group to run on the TRS-80's Z-80.  This is essentially what's going on
>now with the TCP/IP software.
>
>The problem is that you give up doing anything else with your computer.

Why?

>Typically I use Procomm to speak to my TNC.  With Procomm I can run a split
>screen CHAT mode, I can capture data to disk, I can read a string of
>bulletins then scroll back and read them at leisure.  Other packet terminal
>programs have been written to capture different data streams or connections
>to different screens.  When you dedicate the computer to doing packet I/O,
>you really give up all that flexibility.

But you don't have to dedicate the computer to it.  Just have a process
doing what the PAD part of the TNC does.  Give it a high enough priority
that it can't fall behind.  You should still have the majority of CPU
time available for the terminal program, and whatever else your computer
does in its spare time.

In 1980 your TRS-80's cpu wasn't any faster than the CPU in a TNC, and
you couldn't get a multitasking OS to let you separate the packet assembly
program from the terminal program.  A lot has changed in 10 years.

Having a standardized TNC does have advantages, like you never have to
worry about porting a new protocol to your platform, or losing the software
on your disk.

-don perley - ke2tp
--
[e-mail]

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

Date: 13 Nov 90 19:35:30 GMT
From: netcom![e-mail]  (Morris Jones)
Subject: Which TNC?
To: [e-mail]

[e-mail] (Donald P Perley) writes:
>[I wrote:]
>>The problem is that you give up doing anything else with your computer.
>
>Why?

When I'm running NET or NOS right now, I have _no_ features that I get with
my existing terminal emulator.  I can capture, but I don't have keyboard
macros, or scroll back, or script files, or chat mode, or ....

I've seen nothing here to suggest that this is going to change anytime in
the next couple of years.  NOS-in-a-box is what's being proposed, _not_
a computer-resident process running a packet controller chip.  In fact,
the sentiment I've been reading on tcp-group is urging Phil to avoid
re-writing Unix and build something for realistic small hobby PC clones.

>But you don't have to dedicate the computer to it.  Just have a process
>doing what the PAD part of the TNC does.  [...]

Pardon me?  My 286 doesn't do that.  1 Meg of memory is barely room to run
NOS.  I don't have $2500 to buy System V from Microport (that was the
"special offer" price in a flier I just received).  My 40 megs of disk
are full right now with DOS tools, and I have no where to put UNIX.  OS/2
isn't real on a 286, and Windows 3.0 might be a route to go, but it needs
lots more memory and disk before I can do it on my 286 realistically.

Seriously, what are you suggesting is the best route for a typical small
hobby computer owner?  My TNC cost me $120.  A computer suitable for
serious multi-processing will cost me $3,000.

Mojo AA4KB
--
[e-mail]          Site Coordinating Instructor, San Jose South
Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
Campbell, CA              800-675-5559 ... 800-CC-RIDER
AA4KB @ N6LDL.#NOCAL.CA.USA.NA / aa4kb.ampr.org / netcom![e-mail]

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

Date: 13 Nov 90 19:03:51 GMT
From: van-bc!mdivax1![e-mail]
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Tom Varga) writes:
>
>       ...  stuff deleted ...
>
>       Which brings up the final question.  With today's PC's getting
>quite powerful, it would make more sense put all 'firmware' into
>software on the PC and drive the modem directly.  Certainly my SE/30
>is fast enough to do even 9600 baud.  Does this exist or am I just
>dreaming?
>
There are a couple of reasons folks come up with not to do this. One
involves mailboxes on packet. To do this reasonably well, you need to leave
the system on. Do you want to leave your SE/30 on all the time? (at least
with MF it won't be dedicated to packet :-) ). It also means that, with a
PC, you need to devote your PC to packet only. It is aggravating to be
waiting for a message or connect and need to do work on the machine. Kind
of stops things (again, thanks MultiFinder).

Now, actually, I agree that this is a pretty food idea. In fact, a look at
how KA9Q's TCP/IP package is implimented shows an excellent way of doing it.
You still need some sort of a box to control the channel (the KISS TNC),
but the computer does the protocol and application support. AND, if you are
running a multiTasking system (like MultiFinder), you can do other things
at the same time.

Hmm. Not to start a "OS war", but it is not the power of the hardware that
determines what you can do on the machine, but the operating system. DOS
is pretty poor for doing multiple things at a time, while Mac and UNIX
are very effective at doing just that. This is the reason that many NET
users are now taking a good look at the plethora or "inexpensive" UNIX
ports that are around. It makes the NET package easier to impliment as well.

- Jack Brindle, WA4FIB/7.

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

Date: 13 Nov 90 17:19:55 GMT
From: infopiz!lupine!hansen![e-mail]  (Phil Graham)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Tom Varga) writes:

|>      My basic question is which TNC should I consider buying?  I
|> have a macintosh SE/30 and also a Toshiba laptop and probably would
|> like to use both of these.  I also have an IC-24AT and am wondering if
|> I might be able to use this to at least start out with.
With the hardware that you have (a computer and the IC-24AT it is no
problem to go up to 2400 baud with just simple cables, a TNC, and a
terminal emulator. If you want to get started the cheapest way purchase
a 1200 baud TNC (such as a MFJ 1270B) and plug this into one of you
computer serial ports, plug in the radio, run your software and off you go!

|>
|>      Although it seems that 1200 baud is what is mostly available,
|> I can't imagine such a sloooow rate and would probably go out of my
|> mind.  (I'm spoiled since I have a workstation on my dest at work :)
|> Anyway, I don't mind starting out at 1200 baud but would like to have
|> an easy path to 2400 and preferably 9600 baud.  Is there such a beast
|> available?
2400 Baud modems are available from a number of vendors. The only real
problem is that they are new and most people have not purchased the
upgrade for the old modems.  I will have one on Dec. 25th hee hee :-}.
A 2400 baud modem can still be plugged right into the radio with no
problems. I am sure that the computer will have no problems with this
(most computers can handle 9600 and some can handle 19200.

As for 9600 baud... Some kits are available now, but they are dedicated
units and most people who use these are using them with the satellites
(I think).

If you have big $$$ and can wait awhile longer then you can get one of
the new generation modems from AEA or LL Grace.  These modems are DSP
based machines that will run all modes (including 9600 baud packet).
The cost for these is around $700!

|>
|>      Finally, if I'm interested in TCP/IP and require KISS mode,
|> are'nt most TNC's overkill since it seems like KISS is almost a
|> straight connection to the modem.
As with everything nothing comes for free.  The modem companies want to
sell to the largest number of people possible, so they include software
for both types!

|>
|>      Which brings up the final question.  With today's PC's getting
|> quite powerful, it would make more sense put all 'firmware' into
|> software on the PC and drive the modem directly.  Certainly my SE/30
|> is fast enough to do even 9600 baud.  Does this exist or am I just
|> dreaming?
This has been done for the IBM/PC compatible.  From a company called
DRSI.  The cost of these products is not cheaper however than the
external modems.

As for using your using your SE/30... Don't count on it... Most hams own
IBM clone computers since they are alot cheaper than a Mac.   You can
use your SE/30, but you may find that the software is harder to find....

Good luck!

DE KJ6NN
Phil

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

End of Packet-Radio Digest
******************************
Date: Thu, 15 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #194
To: packet-radio


Packet-Radio Digest         Thu, 15 Nov 90       Volume 90 : Issue 194

Today's Topics:
        standard mark/space freqs, direct fsk
             Which TNC? (8 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 14 Nov 90 16:21:35 GMT
From: usc!wuarchive!zaphod.mps.ohio-state.edu!samsung!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: standard mark/space freqs, direct fsk
To: [e-mail]

In article <[e-mail]> [e-mail] (Monty Wilson) writes:
>I am building a packet radio transceiver for the 10m band and I would
>like to hear from anyone who has tried to use direct FSK rather than
>audio tones into an LSB transmitter for this purpose.  I understand
>that on HF packet the shift is 200 Hz rather than 170 Hz, but can
>anyone tell me what the two tones are (in Hz off the carrier)?  I am
>currently checking to see whether my friend's TNC (It's an MFJ 1270B,
>similar to the 1274 but without tuning LEDs) has direct FSK output.
>If it does, or if an easily accessible internal signal can be tapped,
>I would like to use it to directly swing a transmit oscillator in my
>transceiver, since it doesn't do sideband.  Thanks,
>..........Monty WB5NVM.

Direct FSK works fine for HF packet. Packet is HDLC and is only interested
in the transitions from one tone to the other so which tone is which is
not a problem. Three hundred baud packet unfortunately uses a 200hz shift
instead of the traditional RTTY shift of 170hz but this is a minor matter.
The only problem you face is the fact that you desire to use a tranceiver.
Making the transmit and received signals appear on a single channel can
be confusing. With AFSK and both stations using the same sideband, it's
easy since when you have the other station tuned in correctly, your
transmit signal will be correctly positioned. For direct FSK you must
offset the carrier frequency to either the mark or space frequency and
then shift it in the proper direction for each bit so that a station
copying your signal will be able to align his transmit signal to the
same frequencies. Standard practice is to shift the carrier 2110hz
below the nominal frequency on transmit and shift it an additional
200 hz to 2310hz below carrier frequency at the first bit transition.
Thus your signal will be shifting between 2110 and 2310 for each bit.
On ten meters there is the added complication that 1200 baud packet
is allowed. This is 1000hz shift between 1200hz below carrier and
2200hz below carrier. As a side note, the AFSK generator in TNCs is
phase coherent to avoid generating unnecessary mixing sideband products.
Your signal should be phase coherent too. Time your transitions so that
they switch at the zero crossing point of your RF waveforms and in the
same directional sense. That is to say if the RF waveform is decending
to zero before the transition, it should be continuing to decend after
the transition and vice versa. You may tap a TTL level signal for
transmitting at the input to the XR2206 function generator pin 9.

Gary KE4ZV

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

Date: 14 Nov 90 07:03:30 GMT
From: pasteur!agate!shelby!snorkelwacker.mit.edu!usc!ucselx!crash![e-mail]  (Skip Sanders)
Subject: Which TNC?
To: [e-mail]

As I recall from the texts on Packet I've read, the main reason for making
packet TNC's seperate hardware is that proper packet operations involve
what might be considered "doing many things at the same time"... packets are
monitored, assembled going the other way, and data sent to/from the terminal
all at the same time, and it's a LOT of work for a single CPU to keep up with.
The TNC has special-purpose chips that are designed to do all this stuff, and
your computer (if used) has time to handle files, etc along with the RS232
comms with the TNC without choking.  It CAN be, and IS being done in software
on the simple C64, with a simple modem to convert tones, but it's supposed
to be preferable to use a purpose-build packet chip for the work.

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

Date: 14 Nov 90 14:32:17 GMT
From: [e-mail]  (Brian Kantor)
Subject: Which TNC?
To: [e-mail]

Nearly every TNC on the market consists of an HDLC chip (the Z80-SIO
and Z-8530 SCC are the two most popular) and a small processor,
typically a Z-80.  There is NO custom packet hardware (other than the
modem itself) in there; the only digital chip that isn't found in the
typical home computer is the HDLC chip.

Any home computer could be equipped with an HDLC chip and do packet as
long as it's fast enough; at 1200 baud, I suspect even the Sinclair
ZX-81 pocket-rocket could have done AX.25, since it wasn't really very
much different from what's inside a TNC-2.  Remember that the Radio
Shack COCO and the TNC-1 were a lot more common than different.  A
Commodore-64 probably could do packet-on-a-card too, assuming a card
had been available.  But that's older technology.

Remember that the TNC was developed for a time when users had glass
ttys, not computers.  The initial concept was NOT primarily sharing of
networked computer resources, but rather human to human communication.
Only now are we getting away from kbd-to-kbd and kbd-to-bbs uses for
packet radio (although I think a lot of hams are really blind to the
other possibilities; many I talk to just can't conceive of anything
beyond "a better bbs").

With the ability of the PC to run loadable device drivers and TSRs,
it's simply a duplication of hardware to use an external device like a
TNC.  Thus if you have sufficient spare CPUage, it makes a lot of sense
to run the HDLC stuff on the PC bus directly, as that gives you the most
flexible configuration for experimenting, and the widest choice of
software.

At low speeds like 1200 bps (and probably up to a single port at 9600
bps), the typical PClone has plenty of snuff to handle packet radio
directly without a TNC.  With the DRSI PCPA and equivalent cards, the
hardware is available.

Indeed, if you're going to be doing the AX.25 (and other) protocol
stuff in the PC, you'll be running a KISS TNC in order to look at the
raw frames, and then the only thing the external TNC gives you is a bit
of buffering.

At higher speeds and multiple ports, you're probably running into the
stops of the PC; Phil reports that at 56kb the PC dies whilst a frame
is being received.  The answer here is not perfectly clear: you could
simply have a smarter HDLC card with a bunch of buffering (and perhaps
memory windows), or you can build a complete protocol engine on a card.

I'm inclined to let the main CPU do all protocols above HDLC, which
keeps the I/O cards simple and cheap, and lets me do special things,
like send 2048 and 8192 byte AX.25 frames on 56kbit or faster links.

The main packet switch that I'm building for our metropolitan lan is
pretty clearly going to be a bare-bones turbo AT with on-the-bus HDLC
cards (like the PCPA) and something custom-built that can talk HDLC at
56kb to the DSY modem without soaking the CPU.

I'd like to use something faster, like a SunSPARC, but I haven't got
the budget for it, nor are the I/O cards really available.  Right now
the PC/AT architecture, clumsy as it is, seems to be the best fit for
ham packet radio.

By the way, the Macintosh uses the 8530 chip and can do HDLC directly
out the serial port, except that Apple didn't run enough wires to the
connector so you can't get the needed signals (R/T clock, etc) very
easily.  Perhaps there's a card for the Mac-II that will revolutionize
packet.
        - Brian

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

Date: 14 Nov 90 16:37:05 GMT
From: agate!shelby!snorkelwacker.mit.edu!usc!samsung!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>
>I have the understanding that 2400 is really a waste of time.  The modems
>are using the same protocols as the telephone modems, and they're optimized
>for telephone connections where the frequency control is a little better.
>Or so I'm told.  But I don't know of much 2400 baud traffic here in San
>Jose.

There is some small advantage to 2400 baud but not nearly as much as you
would think. You get an average thruput multiplier of 1.25 or so due to
the fixed overhead (Txd, headers, etc) in the packet system. Real noticable
improvement requires 9600 baud.

>9600 on the other hand requires a much greater commitment and expense.  The
>modulation technique in use currently involves frequency shifting a crystal,
>and you can't use it with a synthesized rig.  Kantronics is selling a digital
>radio specifically for this use.  It has two crystal channels, runs two
>watts, and sells for about $200.  It's the DVR2-2.

Actually you can use the G3RUH modem with some synthesised radios, but you
must be willing to tinker with the PLL loop filter time constant.

>Then you need a TNC that will support a 9600 baud modem, and I think that
>means (at the moment) the Kantronics Data Engine.  They're a little pricey
>for me.

Actually any TNC2 compatible unit is capable of handling 9600 baud modems.
If it has a TAPR style modem disconnect header on it, it will work. The
main problem is finding someone else to talk to at this speed right now.
Many people still think it's expensive or difficult to use 9600 baud.
It's not very expensive (~$90) and not very difficult.

Gary KE4ZV

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

Date: 14 Nov 90 15:37:39 GMT
From: agate!shelby!snorkelwacker.mit.edu!usc!samsung!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Mark Monninger) writes:
>In article <[e-mail]> [e-mail] (Tom Varga) writes:
>>
>>       ...  stuff deleted ...
>>
>>      Which brings up the final question.  With today's PC's getting
>>quite powerful, it would make more sense put all 'firmware' into
>>software on the PC and drive the modem directly.  Certainly my SE/30
>>is fast enough to do even 9600 baud.  Does this exist or am I just
>>dreaming?
>>
>>        ...  more stuff deleted ...
>
>I've also wondered why this couldn't be done. Certainly a Mac or PC of the
>AT class would be able to handle it. As I understand it, a TNC is just a
>data packager that takes keyboard input, assembles it into AX.25 packets,
>and sends it to a modem, and the opposite on the incoming (receives packets
>from the modem, extracts the data and displays it). Can any of you packet
>wizards enlighten us?
>
>Any information on this would be greatly appreciated.

This can certainly be done, but some of us are moving in the opposite
direction by working with coprocessor boards to offload the details
of channel management from the main processor. This is becoming necessary
in packet switches with multiple high speed links. An example of what
you want is the DRSI board which is an 8530 and a single chip modem.
All of the software to do packet is run on the host processor. This
works fine for one or two low speed channels even though you are basically
turning a $3000 computer into a $130 TNC. Where this approach falls apart
is where you have more than two channels or you are using high speed
channels. The problem is that you have to process an interrupt for every
character of incoming data whether it is addressed to you or not. Even
garbage packets caused by collisions, weak signals, or channel noise
must be processed up to the point where the checksum fails. This creates
an intolerable amount of interrupts to the point where you begin to
lose characters due to overruns. By offloading channel management to
a coprocessor, your program only needs to receive one interrupt per
packet instead of one per character. And your program doesn't need to
deal with bad packets, channel noise, or packets not addressed to you.
Then your host processor is freed to run real applications.

Current TNCs are rather poor coprocessors because they must communicate with
the host by interrupt per character async lines. They do offload the tasks of
channel management and the discarding of bad packets and the discarding of
packets not addressed to your station however. Better solutions are possible
such as the Grace board or a few others still in progress. These coprocessors
are tightly coupled to the buss of the host and present a complete valid packet
addressed to your station with a single interrupt. Another approach
that has been discussed here is the idea of a traditional TNC with
a SCSI or ethernet interface to the host. This eliminates the interrupt
per character problem.

It depends on your expectations of what you want to do with packet
whether you choose to do all the dirty details in the computer or
offload them to a coprocessor. If you are content with keyboard chatting
on a single low speed channel then the software solution is for you.
If your station must act as a packet switch to several channels, or
you want to run complex server applications, then the coprocessor route
will serve you better.

Gary KE4ZV

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

Date: 14 Nov 90 15:51:07 GMT
From: envy![e-mail]  (Phil Karn)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Brian Kantor) writes:
|> Nearly every TNC on the market consists of an HDLC chip (the Z80-SIO
|> and Z-8530 SCC are the two most popular) and a small processor,
|> typically a Z-80.  There is NO custom packet hardware (other than the
|> modem itself) in there; the only digital chip that isn't found in the
|> typical home computer is the HDLC chip.

Quite true. This mirrors the "real" networking world, where those
"smart" outboard communication coprocessors that were supposed to
offload all that horribly complex protocol processing usually end up
running it more slowly than the host CPU. Even worse, the host CPU often
ends up spending more cycles talking to the communication coprocessor
than if it just did all the work itself. Besides poor architectural
design, another reason for this state of affairs is that the host
CPU industry, with many general purpose applications to give it large
economies of scale, has developed much faster than the communications
coprocessor market, which is still small and specialized.

|> At higher speeds and multiple ports, you're probably running into the
|> stops of the PC; Phil reports that at 56kb the PC dies whilst a frame
|> is being received.  The answer here is not perfectly clear: you could
|> simply have a smarter HDLC card with a bunch of buffering (and perhaps
|> memory windows), or you can build a complete protocol engine on a card.

This is because the presently-available HDLC cards don't support DMA
and have minimal internal buffering (the 8530 has only 3 bytes worth
on the receiver, and none on the transmitter, I believe).  With DMA
(or some other form of external buffering, such as FIFOs), even a slow
4.77 MHz XT has no problem at all dealing with 56kb data streams. Note
that this does NOT mean that you need external "smarts" - only a
sufficient amount of buffer memory so as to relieve the real-time
response requirements of the host CPU. Even small amounts of external
buffering can work wonders; consider the difference the NS16550A chip
(with its 16-byte FIFOs) makes when running NOS at high serial line speeds.

Phil

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

Date: 14 Nov 90 22:16:50 GMT
From: usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!trub![e-mail]  (Donald P Perley)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>[e-mail] (Donald P Perley) writes:
>>
>>>The problem is that you give up doing anything else with your computer.
>>
>>Why?
>
>>But you don't have to dedicate the computer to it.  Just have a process
>>doing what the PAD part of the TNC does.  [...]

>Pardon me?  My 286 doesn't do that.

Sorry.

>  1 Meg of memory is barely room to run
>NOS.  I don't have $2500 to buy System V from Microport (that was the
>"special offer" price in a flier I just received).  My 40 megs of disk
>are full right now with DOS tools, and I have no where to put UNIX.  OS/2
>isn't real on a 286, and Windows 3.0 might be a route to go, but it needs
>lots more memory and disk before I can do it on my 286 realistically.


>Seriously, what are you suggesting is the best route for a typical small
>hobby computer owner?  My TNC cost me $120.  A computer suitable for
>serious multi-processing will cost me $3,000.

A low end Amiga runs about $500 with multitasking.  You don't need
a 68030 workstation, you just need enough speed to keep up with what
the Z80 in the TNC would do, and enough left over to run your terminal
program.  The original poster has a mac se/30, which certainly ought
to be fast enough too. I think either of those has enough hardware
buffering that you don't have to interupt for every byte that comes in.

If you have the multitasking OS, I just don't see how taking out that
Z80 is going to chew up a huge amount of resources from the computer.
If you want to run 56kbaud, then you would certainly be justified in
offloading all that processing to an external TNC, but then a normal
TNC 2 wouldn't keep up either.

The TNC would be more convenient, since it is just plug'n'play, while
someone (maybe the user, augh!) would have to write the pad program
for the computer. Maybe you can't do it on a base level PC.. and buying
a TNC is going to be cheaper than upgrading.. but LOTS of people already
have capable computers.  If you feel crippled without multitasking, you're
right!

-don perley - ke2tp

--
[e-mail]

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

Date: 14 Nov 90 18:25:17 GMT
From: sbi!zeus!newt![e-mail]  (Jean-Louis Ecochard)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>>But you don't have to dedicate the computer to it.  Just have a process
>>doing what the PAD part of the TNC does.  [...]
>
>Pardon me?  My 286 doesn't do that.  1 Meg of memory is barely room to run
>NOS.  I don't have $2500 to buy System V from Microport (that was the
>"special offer" price in a flier I just received).  My 40 megs of disk
>are full right now with DOS tools, and I have no where to put UNIX.  OS/2
>isn't real on a 286, and Windows 3.0 might be a route to go, but it needs
>lots more memory and disk before I can do it on my 286 realistically.
>

I suggest you investigate into other alternatives for your multitasking
needs like, from the most to the least expensive:

Desqview: a DOS multitasking utility lighter than MS windows
with virtual memory and a nice prioritizing of tasks based on
communication needs.

Double Dos: Allows you to run 2 concurrent DOS sessions.

Minix: an almost public domain ((c) Mc Graw Hill) version of Unix
that comes with source code for ~$100. Of course you would have
to port your application to it (it comes with a C compiler) but
it seems that you were considering Unix anyway and minix works
like Unix System 7.

>Seriously, what are you suggesting is the best route for a typical small
>hobby computer owner?  My TNC cost me $120.  A computer suitable for
>serious multi-processing will cost me $3,000.
>
I picked up a 68010 based, 4Mb RAM, graphics, 20Mb hard disk,
old Unix system for $900 at a hardware surplus sale. Since,
it has worked OK for my purpose. Of course, I had no support
or upgrades but then I have never needed it. It is now sitting
on a shelf doing nothing because I have no use for it anymore (got
better) I think you can do better than $3000 even if you want to stay
with PC compatible hardware. Check around at the computer fairs,
and ask the help of a friend that knows computer hardware so you don't
get ripped off. I have also seen some businesses giving hardware away
like UNIX PCs (68010/2Mb/40Mb HD).

>Mojo AA4KB

Good luck.
--
Jean-Louis Ecochard                 O
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~./_\.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 (__Y__)                 uunet!sbi!chi!jl

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

Date: 15 Nov 90 00:31:05 GMT
From: [e-mail]  (Mike Chepponis)
Subject: Which TNC?
To: [e-mail]

question "Which TNC".

I only want to mention that folks shouldn't be surprised when support for
the 56K WA4DSY modems becomes  part of the Mac NET distribution (s/w by WA8DZP).
There are indeed enough signals on the Macs to do DSY modems, IF we do the
modems in half-duplex mode.  Full duplex will require using signals from both
ports, or building simple ADB device to allow the Carrier Detect signal to get
into the Mac.

-Mike K3MC

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

End of Packet-Radio Digest
******************************
Date: Fri, 16 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #195
To: packet-radio


Packet-Radio Digest         Fri, 16 Nov 90       Volume 90 : Issue 195

Today's Topics:
               8mm. camcorders
              More TNC questions
             No code license & CW Bashing
             Packet-Radio Digest V90 #194
           Packet balloon in Champaign IL? (2 msgs)
             Which TNC? (7 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 15 Nov 90 15:30:38 GMT
From: att!news.cs.indiana.edu!news.nd.edu!cartan!ndmath!nstar!w8grt![e-mail]  (Jim Grubs)
Subject: 8mm. camcorders
To: [e-mail]

 > From: [e-mail] (Gary Coffman)
 > Date: 14 Nov 90 16:55:40 GMT
 > Organization: Gannett Technologies Group
 > Message-ID: <[e-mail]>
 > Newsgroups: rec.radio.shortwave,rec.ham-radio.swap,rec.ham-radio.packet,
 > rec.ham-radio
 >
 > A comment by someone who uses cameras professionally. In broadcast news
 > gathering, we find that the home cameras are too small and light to be
 > used properly.

Hmm, that's a point I hadn't considered. But when you're stalking a toddler,
it's rather like combat photography. The amazing thing is you get it done at
all. [:-)

--
Jim Grubs - via FidoNet node 1:234/1
UUCP: ...!ncar!asuvax!stjhmc!w8grt!jim.grubs
INTERNET: [e-mail]

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

Date: 15 Nov 90 20:13:14 GMT
From: usc!wuarchive!cs.utexas.edu!oakhill!dover!nddsun1![e-mail]  (Mark Monninger)
Subject: More TNC questions
To: [e-mail]

I really apprceiate the responses I received from various people regarding
using a PC as a TNC. However, I am still a bit confused about it. Let me
ask my (hopefully not too dumb) question point-blank:

I would like to get into packet radio. Nothing fancy, just 1200 bps on
2M, at least for now. Do I need a TNC, or is there some software, hopefully
public domain, that will allow me to use my IBM PC without an outboard
TNC and without buying any additional cards, etc.? I realize I'll need at
least a modem. I want to be able to plug the serial port of the PC into
the modem, plug the modem into my 2M radio, fire up the software, and be
on the air. I gather from the responses I received before that it is
possible, at least in theory, but can anyone point me to some real
software to do this? I have access to anonymous ftp over internet and
so can acquire it if it's there.

Any info will be appreciated.

Mark    KG7JL

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

Date: 15 Nov 90 15:27:19 GMT
From: att!news.cs.indiana.edu!news.nd.edu!cartan!ndmath!nstar!w8grt![e-mail]  (Jim Grubs)
Subject: No code license & CW Bashing
To: [e-mail]

 > From: [e-mail] (Gary Coffman)
 > Date: 14 Nov 90 16:44:56 GMT
 > Organization: Gannett Technologies Group
 > Message-ID: <[e-mail]>
 > Newsgroups: rec.radio.shortwave,rec.ham-radio.swap,rec.ham-radio.packet,
 > rec.ham-radio
 >
 > In article <[e-mail]> [e-mail] (Jim Grubs)
 > writes:
 > >
 > >Also, I would reduce maximum power to 200 watts for everyone. There's no
 > >earthly need for more than that and hasn't been since hams quit operating
 > on
 > >600 or 700 meters with rotary spark gap transmitters.
 >
 > Don't forget the moonbouncers, they still need the power for that path
 > unless
 > they use truely monsterous antenna arrays and/or lots of DSP. And when
 > they
 > have the monster arrays and lots of DSP the truly wacko will want to try
 > Mars bounce. :-)

Well, make that 200 watts for HF and non-moonbounce. But if you're going to
make an exception for EME, why stop at ONE KW? Why not 20? One wonders what
ingenious work with antennas, DSP, etc., would have been tried and perfected if
the KW was not available. Mars? Hmmm, lessee what's the pathloss for that...

--
Jim Grubs - via FidoNet node 1:234/1
UUCP: ...!ncar!asuvax!stjhmc!w8grt!jim.grubs
INTERNET: [e-mail]

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

Date: Thu, 15 Nov 90 14:48:30 GMT
From: "Pete Lucas, NCS-TLC, Holbrook House, Swindon" <[e-mail]>
Subject: Packet-Radio Digest V90 #194
To: [e-mail]

SUBJECT: Packet-Radio Digest V90 #194

Subject: Which TNC?

The world seems to be going through cycles on this one.. First home-computers
had separate disks, cassettes, CPUs, video modulators, power-units, modems
etc; then the 'system box' came along (IBM-PC style with everything in the
one case) but then that was outgrown.....
I use a DRSI card in an old original 4.77MHZ PC (twin floppies......!) and
IMHO its biggest advantages are aesthetic; i.e. no extra box, power supply,
connecting cables etc.    When the packet station has 24-hour-a-day
visibility (next to the TV!) a minimal-cables solution helps domestic harmony;
internal dialup modems help here too...
Now as to the processing power, something like the DRSI card is rather
lacking.... the 8530 is not the World's best HDLC-generator, and theres
no buffering to speak of on the DRSI board, so you get a LOT of interrupts;
this can cause problems. Faster hardware will evolve; and with the current
low price of second-user IBM-PCs etc, why not have a dedicated box?
IMHO multi-tasking on the majority of small industry-standard computers
stinks.

  Pete Lucas  G6WBJ   [e-mail] [e-mail]  0793-411613

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

Date: 15 Nov 90 17:59:18 GMT
From: usc!wuarchive!cec2![e-mail]  (Mike Bray)
Subject: Packet balloon in Champaign IL?
To: [e-mail]

Does anyone have information on a balloon launch December 1
in Champaign Illinois?

Mike Bray  [e-mail]

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

Date: 16 Nov 90 05:00:42 GMT
From: swrinde!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: Packet balloon in Champaign IL?
To: [e-mail]

[e-mail] (Mike Bray) writes:

>Does anyone have information on a balloon launch December 1
>in Champaign Illinois?

What I know so far is that it will be a CW beacon on 10m.
I've been asked to do some photography for it.
--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 15 Nov 90 15:38:38 GMT
From: rochester!rit!cci632![e-mail]  ( co-op)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Gary Coffman) writes:
>You get an average thruput multiplier of 1.25 or so due to
>the fixed overhead (Txd, headers, etc) in the packet system. Real noticable
>improvement requires 9600 baud.

Agreed - we've played with this out here.  I think that the "default" TX
delay in a new tnc is still around 300 milliseconds, isn't it?  If, at
1200 baud, you're dealing with a short packet length (say, less than 50
bytes, including headers) of less than 400 milliseconds, then more than 40%
of the transmit time is "dead carrier".  Solid state TR circuits and
quick-locking modern receivers just don't need that.

Maybe we can ask the TNC manufacturers to make less obnoxious and less
aggressive level 2 controllers -- chances are, the end user won't play
with these stats.

Chris/WZ2B

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

Date: 15 Nov 90 17:24:04 GMT
From: uupsi!uhasun![e-mail]  (Jon Bloom)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Phil Karn) writes:
> In article <[e-mail]>, [e-mail] (Brian Kantor) writes:
> |> At higher speeds and multiple ports, you're probably running into the
> |> stops of the PC; Phil reports that at 56kb the PC dies whilst a frame
> |> is being received.  The answer here is not perfectly clear: you could

> This is because the presently-available HDLC cards don't support DMA
> and have minimal internal buffering (the 8530 has only 3 bytes worth
> on the receiver, and none on the transmitter, I believe).  With DMA
> (or some other form of external buffering, such as FIFOs), even a slow
> 4.77 MHz XT has no problem at all dealing with 56kb data streams. Note

The proof of which is that 4.77 MHz XT's have no difficulty handling the
10 Mbit/s data stream of Ethernet because the controller card uses either
DMA or an on-board buffer.  With such techniques, 56 kbit/s is trivial.
(This is not to say that a 4.77 MHz XT can handle a *continuous* 10-Mbit/s
data stream, of course, but it can receive packets at 10 Mbit/s from the
Ethernet.  I'm not sure a 4.77 MHz XT could even handle continuous
56 kbit/s data.)

--
Jon Bloom, KE3Z                              | American Radio Relay League
Internet: [e-mail]         |
Snail:    225 Main St., Newington, CT 06111  | "I have no opinions."

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

Date: 15 Nov 90 20:48:35 GMT
From: netcom![e-mail]  (Morris Jones)
Subject: Which TNC?
To: [e-mail]

Well I don't understand.

I have a 12 MHz 286, and a PK-88 TNC.  I also have NET and a version of NOS
and an internet number.

With this arrangement I can use Procomm or a variety of packet-oriented
terminals to do AX.25 things.  Or I can use NET and do some TCP/IP things.

I've seen you all arguing for doing the packet processing on the main CPU.
The only example I have for doing this is NET and NOS, and it's *not fun*!

There is nothing else I can do with my computer when I'm running NOS.  I
can't trace other packet activity on the frequency to another window.  I
can't scroll back to read a message from a BBS.  I can't emulate a terminal
and do any terminal-specific graphics.  TELNET to another station is all
but useless -- with any traffic the backoff timer eventually reaches the
point where I sit twiddling my thumbs forever.  There's not enough memory
to run an editor or even Bdale's Mailer.  The mailer is as ugly as any
UNIX mailer I've ever seen.  I can't run any applications that "work with"
NOS and use it as a data pipe.  And I can't even "CQ".

All I can do is FTP, and SMTP mail.  What's more, if I don't leave my
computer on running NET or NOS at all times, there is hardly any chance
that I will ever receive any mail.  Oh yes, I forgot, I can "finger".  Joy.

TCP/IP is not fun.  Tying up my computer to support it is not fun.  Using
up a computer might be justified for a computer that was dedicated to being
a network node or a BBS or something, but it's not a way to be a leaf node
on a packet network.

How is my computer going to receive mail while I'm playing Windows
Solitaire?  My TNC does that for me just fine!

After using TCP/IP for a while, I realized that there just wasn't anything
to *do* with it and I've all but given up.  At least with the Net/Rom
network I can CQ!  With my TNC away on the serial line, I can try dozens
of different terminal applications that use the data pipe available.  It's
possible I could even run a couple of Microsoft Flight Simulators and let
them talk to each other.  Could I do that with my computer providing the
AX.25 protocol?  (I won't even ask for TCP/IP.)

You mention loadable device drivers.  That'd be nice.  I haven't seen any.
Maybe I'm missing something.

I'd like to write a CHAT cluster host to run on my PC.  That would
certainly tie up the PC, but it'd be a noble usage.  (Wouldn't it be nicer
to put it on a ROM in the TNC?  Cheap!)  Maybe this is something that would
help make using TCP/IP more fun, and I should build it using the TCP/IP
tools.  But it's not very tempting when I can offload a lot of packet
processing to the TNC.

I'm still going to miss doing other things with my PC.  <sigh>

Mojo
--
[e-mail]          Site Coordinating Instructor, San Jose South
Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
Campbell, CA              800-675-5559 ... 800-CC-RIDER
AA4KB @ N6LDL.#NOCAL.CA.USA.NA / aa4kb.ampr.org / netcom![e-mail]

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

Date: 15 Nov 90 22:20:18 GMT
From: [e-mail]  (Patty Winter)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>I have a 12 MHz 286, and a PK-88 TNC.  I also have NET and a version of NOS
>and an internet number.
>
>With this arrangement I can use Procomm or a variety of packet-oriented
>terminals to do AX.25 things.  Or I can use NET and do some TCP/IP things.

Idle curiosity: how come you don't use NET for AX.25 things? Perhaps
Procomm has some specific features you prefer? I just keep getting this
feeling that people don't realize you can do AX.25 and NET/ROM with
Phil's software.

>There is nothing else I can do with my computer when I'm running NOS.

I don't suppose you'd care to buy a Macintosh? :-)  Other than that,
can't you run DesqView or DoubleDOS or whatever those things are called?
Or do they require more memory than your system has?


Patty

--------------------------My opinions. All mine.----------------------
--
*****************************************************************************
Patty Winter N6BIS                        INTERNET: [e-mail]
AMPR.ORG: [44.4.0.44]                     UUCP: {decwrl,nsc,sun}!apple!winter
*****************************************************************************

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

Date: 16 Nov 90 00:50:12 GMT
From: netcom![e-mail]  (Morris Jones)
Subject: Which TNC?
To: [e-mail]

[e-mail] (Patty Winter) writes:
>Idle curiosity: how come you don't use NET for AX.25 things? Perhaps
>Procomm has some specific features you prefer? I just keep getting this
>feeling that people don't realize you can do AX.25 and NET/ROM with
>Phil's software.

Yes.  Procomm has scroll-back, which lets me read a collection of BBS
mail, then look back through it at will.  NET doesn't do this.  I'm well
aware of NET's AX.25 capabilities.  Other packet terminal programs have
capabilities to conduct multiple conversations on different "screens", while
monitoring other traffic on the frequency on yet another screen.  NET
and NOS don't do this either.  Procomm also has a "chat" mode which will
let me type a buffer ahead, then dump it when it's my turn.  But that's
not the real issue.

As long as NET is dominating my computer, there is no opportunity to write
"applications" like this that will take advantage of the communications
capabilities.  If TCP/IP were being taken care of by a small device
driver, I could write my own front end.  Something called FTP maybe.
I dunno.  The communication tool is not supposed to be the application
itself.

If you could get at TCP/IP the way you can get at the TNC, there would
be a cornucopia of people writing "applications" to use the pipe.  Like
there are with people writing "host mode" terminal programs for packet.

Is this something you can do with Mac NET that I can't do?  Maybe you're
right in that case.  Could you write a game?  A conversation cluster?
A mailbox?  A BBS?  Can you do it with a development system (software)
that costs $100?  (That was what Borland offered Turbo C++ to me in a
mailing a few months ago.  I probably should have bought.)

>                                                    Other than that,
>can't you run DesqView or DoubleDOS or whatever those things are called?
>Or do they require more memory than your system has?

Not only more memory, but more money.  The TNC is $120 solution to take
care of that task.  Cheaper than any of the other hardware or software
solutions.  It's something real to consider, and something that the TCP/IP
group doesn't really seem to care about.  (cost)  It sits quietly under
the 2m radio and gets mail for me.  I can go play solitaire on my
computer in the meantime.  Or my wife can do some Harvard Graphics while
I plug the TNC into a VT-100 that I have lying around.

>Patty

73,
Mojo AA4KB
--
[e-mail]          Site Coordinating Instructor, San Jose South
Morris "Mojo" Jones       Skilled Motorcycling And Rider Training (S.M.A.R.T.)
Campbell, CA              800-675-5559 ... 800-CC-RIDER
AA4KB @ N6LDL.#NOCAL.CA.USA.NA / aa4kb.ampr.org / netcom![e-mail]

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

Date: 16 Nov 90 04:40:02 GMT
From: [e-mail]  (Patty Winter)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Morris Jones) writes:
>
>Yes.  Procomm has scroll-back, which lets me read a collection of BBS
>mail, then look back through it at will.  NET doesn't do this.

Of course, it does let you record the messages into a file. I don't
find this a problem because I just move over to the text editor I
keep open and read them. You're right though about not being able to
reread the messages right on the NET screen.

>aware of NET's AX.25 capabilities.  Other packet terminal programs have
>capabilities to conduct multiple conversations on different "screens", while
>monitoring other traffic on the frequency on yet another screen.  NET
>and NOS don't do this either.

It isn't true to say that "NET" doesn't do this; the Macintosh version
most certainly does. It has separate windows for tracing, logging, console
(command), and each session. Maybe Amiga and UNIX users can report on their
versions; I don't know about them.

>  Could you write a game?

I don't know what it would take to do this in NET, but some folks in
this area came up with a nice packet-radio chess program that takes
advantage of the Macintosh's graphics to display the moves of realistic-
looking pieces on a chessboard background. So it's definitely feasible
on packet.


Patty

--
*****************************************************************************
Patty Winter N6BIS                        INTERNET: [e-mail]
AMPR.ORG: [44.4.0.44]                     UUCP: {decwrl,nsc,sun}!apple!winter
*****************************************************************************

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

Date: 16 Nov 90 09:09:13 GMT
From: envy![e-mail]  (Phil Karn)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Morris Jones) writes:
|> As long as NET is dominating my computer, there is no opportunity to write
|> "applications" like this that will take advantage of the communications
|> capabilities.  If TCP/IP were being taken care of by a small device
|> driver, I could write my own front end.  Something called FTP maybe.
|> I dunno.  The communication tool is not supposed to be the application
|> itself.

NOS's design is heavily influenced by the need to run under MS-DOS.
Unfortunately, MS-DOS is not a multitasking operating system, so NOS
contains its own internal multitasker so it can run multiple
(internal) applications in parallel above the network protocol stack.
If TCP/IP were moved off to an external device, freeing MS-DOS to run
your application, then your application would almost certainly be
limited to one user at a time. Unless, of course, you reinvented
something like NOS's multitasker and built it into your application.

I consider single-user servers to be *most* uninteresting.

In fact, I considered the ability to handle multiple simultaneous
users (who may be doing widely different things) to be so important
that I started this whole project in the first place. If I had been
satisfied with single-user servers, then I would have stuck with the
MIT PC/IP package (which already existed in 1985 when I started my
code).

|> If you could get at TCP/IP the way you can get at the TNC, there would
|> be a cornucopia of people writing "applications" to use the pipe.  Like
|> there are with people writing "host mode" terminal programs for packet.

There already are. Since I make full source code available, many
people have taken the opportunity to contribute applications and
enhancements of their own. At the moment, SM0RGV is enhancing his BBS
code like there's no tomorrow, Bill Simpson of MSU is doing very nice
things for the domain resolver code, G1EMM is adding all sorts of
miscellaneous features, K1IO and others are working on link-state
(SPF) routing, Katie Stevens of UC Davis has contributed a PPP
(point-to-point protocol) and TCP/IP header compression module, and
I'm working like mad trying to keep track of what everybody else is
doing so I can merge their efforts into a common system.

You too can write an application for NOS if you like; I've tried very
hard to make that as easy as possible, given the admittedly crippling
constraints of MS-DOS.  All you need is the code and a Turbo C
compiler. You can get the code from thumper.bellcore.com by anonymous
FTP (/pub/ka9q/nos/src*.zip) and Turbo C you can get from Borland for
a hundred bucks or less.

|> It's something real to consider, and something that the TCP/IP
|> group doesn't really seem to care about.  (cost)

You just pushed my hot button. If I didn't care about cost, I wouldn't
have spent almost all of my spare time (and then some) of the last
five years of my life writing NET/NOS and making it work on the
cheapest hardware platform (the IBM PC) that was usable despite its
utterly brain-damaged architecture -- just so I could give it all away
for free to the amateur radio community.  After all, there are already
many commercial TCP/IP implementations that work well.  All it takes
is money.  Source licenses to FTP Software's package cost something
like $50,000 *each*.

Nah, we don't care about cost.

Phil

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

End of Packet-Radio Digest
******************************
Date: Sat, 17 Nov 90 04:30:07 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #196
To: packet-radio


Packet-Radio Digest         Sat, 17 Nov 90       Volume 90 : Issue 196

Today's Topics:
                  AX.25 LAN
    Information required to get FT726R 9600Baud capable ?
                Minix
                  PSK modems
             Which TNC? (10 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 16 Nov 90 20:33:06 GMT
From: sbi!zeus!newt![e-mail]  (Jean-Louis Ecochard)
Subject: AX.25 LAN
To: [e-mail]

I recently got a brochure on Local Area Wireless Network
They use wide spectrum RF in the 902-928Mhz band with
20 milliwatts power using broad spectrum and AX.25.
It has a 500 ft range and does not require FCC licensing.
They got FCC approval on 7-7-89 for up to 1W and they hold a
patent on the LAWN ;-)

What is interesting to note is that they use a Z80 processor
on their network interface and that their TSR program occupies
only 40K under MS-DOS. Another point of interest is that it connects
to the serial port of the system. This allows it to drive modems
and printers.
Cost of the (1lb) unit is $289

I am not involved in packet (just in data packets using computers)
and have nothing to do with the vendor of this equipment
but I thought the information might be of some interest to the
members of this group.

For more information, the company is OCI at [phone]
and their techs are in Princeton (Sheryl Clark [phone]).

--
Jean-Louis Ecochard                 O
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~./_\.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 (__Y__)                 uunet!sbi!chi!jl

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

Date: 17 Nov 90 11:45:18 GMT
From: uhccux!munnari.oz.au!sirius.ucs.adelaide.edu.au!levels![e-mail]
Subject: Information required to get FT726R 9600Baud capable ?
To: [e-mail]

<< Posted for and on behalf of VK5ZSV>>

  Hi there, has anybody got information on how to modify an FT-726R to be
able to use it on 9600 baud.

  I am mainly interested in a way, to directly FM modulate this device,
bypassing the inbuilt audio section.   I intend to use the G3RUH modem with
the FT-726, I believe that '3RUH modem has been developed using this
Transceiver, so there must be some information about somewhere.

No worries about the RX part, I can get to the Discriminator easy enough,
I'm not up to scratch on solid state FM modulation though.

My main worry is, I cannot afford to ruin this tranceiver, not able to
replace it.

If anybody has got information on this, please let me know, I sure would
appreciate it.

Please mail replies to [e-mail]
               VK5ZSV@VK5WI.#SA.AUS.OC on packet radio.

73's VK5ZSV.

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

Date: 16 Nov 90 19:17:38 GMT
From: cunixf.cc.columbia.edu!cunixd.cc.columbia.edu![e-mail]  (Meir I Green)
Subject: Minix
To: [e-mail]

How can I get a copy of Minix?
 * * * * * * *  ======================= Meir Green                           |
* * * * * * * * ======================= [e-mail]           |
 * * * * * * *  ======================= N2JPG                                |

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

Date: 16 Nov 90 14:50:32 GMT
From: swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!wam![e-mail]  (Howard I. Tucker)
Subject: PSK modems
To: [e-mail]

Hey there!

With all the hub-bub about the store and foward pacsats being activated
I am real anxious to get on them.

I know pac-com has a built psk tnc,  How is it and what is the cost?, what is
thier address?

TAPR also has a kit psk modem,  How is it and what is the cost?.  I have
a TAPR TNC-2, It works but it creates a whole lot of RFI (Especially when
I try to run it with an HT)

Does anyone have any experience with either modem?


73 de KA1SUR
[e-mail]
301/864/1980


Quote for Pres. Bush, "Make Love, Not War!" ....Bart Simpson says "War is Bad!"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

Date: 15 Nov 90 19:50:31 GMT
From: uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Donald P Perley) writes:
>In article <[e-mail]> [e-mail] (Morris Jones) writes:
>>[e-mail] (Donald P Perley) writes:
>>>
>>>>The problem is that you give up doing anything else with your computer.
>>>
>>>Why?
>>
>>>But you don't have to dedicate the computer to it.  Just have a process
>>>doing what the PAD part of the TNC does.  [...]
>
>>Pardon me?  My 286 doesn't do that.
>
>Sorry.
>
>>  1 Meg of memory is barely room to run
>>NOS.  I don't have $2500 to buy System V from Microport (that was the
>>"special offer" price in a flier I just received).  My 40 megs of disk
>>are full right now with DOS tools, and I have no where to put UNIX.  OS/2
>>isn't real on a 286, and Windows 3.0 might be a route to go, but it needs
>>lots more memory and disk before I can do it on my 286 realistically.
>
>
>>Seriously, what are you suggesting is the best route for a typical small
>>hobby computer owner?  My TNC cost me $120.  A computer suitable for
>>serious multi-processing will cost me $3,000.
>
>A low end Amiga runs about $500 with multitasking.  You don't need
>a 68030 workstation, you just need enough speed to keep up with what
>the Z80 in the TNC would do, and enough left over to run your terminal
>program.  The original poster has a mac se/30, which certainly ought

Sure, single port and a terminal program is no problem even on a Xerox
820 or a C64. If that's all you want, a glass tty simulator on a slow
channel, then go for it. But the computer will still be tied up doing
channel access and character at a time processing. Not a lot of multi-
tasking power will be leftover. Certainly very little will be left to
do other time critical processing.

>to be fast enough too. I think either of those has enough hardware
>buffering that you don't have to interupt for every byte that comes in.

Unfortunately they don't. The SIO is double buffered as is the 8530 so
at best you need one interrupt per 2 characters at the start and once
the buffer pipeline is full, you have to pull them out as fast as they
come in or you have an overrun condition. This is no problem for a single
channel even at higher baud rates. Where the system falls down is with
multiple channels or when the processor has other time critical tasks
to perform such as managing the display or disk.

>If you have the multitasking OS, I just don't see how taking out that
>Z80 is going to chew up a huge amount of resources from the computer.

On a 33Mhz 386 running Interactive Unix, serial baudrates in excess of
9600 baud fail. Adding a 16550 with it's 16 byte fifo extends that to
just 19.2kb. If you have more than 8 processes going at once, almost
guaranteed with Unix, each process will have less compute power
available to it than a 4 Mhz Z80. And a 4 Mhz Z80 can't handle a single
56kb channel, though a 6 Mhz Z80 can. The problem is servicing time
critical data streams. Unix is not a realtime OS and is easily overwhelmed
by multiple fast external data streams that it can't flow control.

>If you want to run 56kbaud, then you would certainly be justified in
>offloading all that processing to an external TNC, but then a normal
>TNC 2 wouldn't keep up either.

Well a TNC2 can keep up with 56k if you soup it up with 6 Mhz parts
and use a special version of KISS that is optimized to the channel.
The Z80's forte is interrupt servicing. But KISS processing is not
enough offloading to solve the problem. You gain nearly 32k of buffering
in the TNC and you offload channel access control but the host still has to
deal with character at a time serial IO to get the packet inside where it
can be validated or discarded. On a busy switched trunk, you can still have
a buffer overflow.

The better solution is a smartcard in the host that can validate the packet
and issue a single interrupt to signal the host that a valid packet addressed
to the host is available. Then the host can easily handle multiple channels
and do the routing or applications processing required.

To give a real world example, one of our switches on an AT clone can deal
with four 1200 baud channels. But add a fifth channel and characters are
lost. With a 56kb channel, buffered by a special Kiss TNC and using a
16550 on a 19.2kb serial link to the PC, characters are lost if more than
one of the 1200 baud channels are active at the same time. The normal
packet retry mechanisms make it work, but the efficiency is very low.

I firmly believe that multitasking is not the correct answer for packet
switches or application servers. Instead, coprocessing is the best way
to go. The Grace card is already on the market and other, cheaper, cards
soon will be available.

None of my comments should be construed to mean that, for single users
with light demands, simpler, less hardware intensive means aren't suitable.
They are. However, the way packet is evolving, it makes sense to look at
the requirements for more serious uses of packet channels than keyboard
chatting.

Gary KE4ZV

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

Date: 16 Nov 90 13:06:25 GMT
From: elroy.jpl.nasa.gov!usc!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!platypus![e-mail]  (Bill Gunshannon)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Jon Bloom) writes:
>
> The proof of which is that 4.77 MHz XT's have no difficulty handling the
> 10 Mbit/s data stream of Ethernet because the controller card uses either
> DMA or an on-board buffer.

Actually, it can handle bursts at 10 Mbit, but to be realistic, the limit
is really the buss speed of the PC.  As long as the real thruput doesn't
reach that limit, things will be fine.  I doubt seriously that any PC even
one of IBM's whiz-bang PS2's could handle the data spit out by an SGI box!

>                              With such techniques, 56 kbit/s is trivial.
> (This is not to say that a 4.77 MHz XT can handle a *continuous* 10-Mbit/s
> data stream, of course, but it can receive packets at 10 Mbit/s from the
> Ethernet.  I'm not sure a 4.77 MHz XT could even handle continuous
> 56 kbit/s data.)

I feel fairly certain that 56Kbit could be handled by most PC's as long as
that was their primary task.  But not until we get the next generation of
interface cards.  The cards we are trying to use now were all really designed
for much slower serial links.


--

     Bill Gunshannon          |        If this statement wasn't here,
     [e-mail]   |  This space would be left intentionally blank

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

Date: Fri, 16 Nov 90 11:39:50 -0500
From: [e-mail] (Charlie Ross, Jr.)
Subject: Which TNC?
To: "[e-mail]"@gte.com, "[e-mail]"@gte.com

Mojo,

Most of your posting has already been addressed by others.  (Let me suggest
that you pay particular attention to Phil Karn's comments.)  Three specifics,
though, deserve additional treatment:

<<I've seen you all arguing for doing the packet processing on the main CPU.
The only example I have for doing this is NET and NOS, and it's *not fun*!>>

While you're entitled to your opinion, so am I:  I find straight-AX.25 packet
intolerably boring.  On TCP/IP, I have a *blast*.   Waiting for a crowded AX.25
channel as a message slowly appears in bursts on a terminal emulator screen is
a waste of my time. So is waiting 10, 20, 30 minutes for NET/ROM to establish a
link to a node I could almost *drive* to more quickly.  Naw, I'd rather
interact with a local computer at my own pace (fast) and let the system do
the dirty work while I go off and do something else.

<<What's more, if I don't leave my computer on running NET or NOS at all times,
there is hardly any chance that I will ever receive any mail.>>

Not true.  Leave it on overnight.  And while you're at work.  That's more
than enough.  I'm one of the more-active Eastern Mass stations and I'm only
up 40-60% of the time.  I use a Mac, so multitasking is easier for me,
but I frequently shut down NET to give the full CPU to some other application.
No big deal!

However, you won't receive any mail unless people want to send it to you.
You must send it to receive it, so to speak.

<<After using TCP/IP for a while, I realized that there just wasn't anything
to *do* with it and I've all but given up.>>

This comment has been heard before, and there's some validity to it.
Here in New England, we just published the first installment of a listing of
the things people can *do* on our network... the various kinds of servers,
gateways, etc. that are on the air.  You're right, unless there are
*applications* to be used, people get bored unless they're into it for the
simple challenge of getting the system to work.  But in all fairness, this
is not an area where you can expect the networking software gurus to provide
everything.  This is an area for local organizing, writing articles for
newsletters, elmering, cheerleading, and plain-and-simple application
programming to interface to the standard comm package.

There are already some interesting things available to "hang off" a packet IP
network... quick sample of some of the New England amprnet services:  W0RLI
gateway, Internet gateway, callsign server, conference bridge (="crowd" node),
mailbox systems, local news in FINGER form, and of course lots of file servers.
At least two people I know about are in some stage of making tcp-to-dialup-bbs
gateways.

Can more be added?  Absolutely!  As people get interested and
excited enough to do the work.  But I don't expect Phil, Dewayne, Bdale, Kelvin,
et al to do that work for us.  I'm just grateful for all they've done
so far!

TCP/IP boring?  No way.  I'll pick a "real" network anyday.  I don't enjoy
beating my head against a wall (or watching my TNC implement a protocol that
effectively does the same thing).

--Charlie
[e-mail]
[e-mail]
NC1N @ WA1PHY.MA

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

Date: 16 Nov 90 15:11:06 GMT
From: dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!njin!uupsi!cci632![e-mail]  ( co-op)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Patty Winter) writes:
>Idle curiosity: how come you don't use NET for AX.25 things?

Well, some people have complained that the trace function of NOS produces
too much text, making it impossible to casually monitor packets and
maintain a conversation at the same time.

(I've modified that part of the code slightly, but it's still not where
I want it to be -- in its own session)

Chris/WZ2B

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

Date: 16 Nov 90 15:11:59 GMT
From: dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!njin!uupsi!uhasun![e-mail]  (Jon Bloom)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] (Phil Karn) writes:
> In article <[e-mail]>, [e-mail] (Morris Jones) writes:
>
> |> It's something real to consider, and something that the TCP/IP
> |> group doesn't really seem to care about.  (cost)
>
> You just pushed my hot button. If I didn't care about cost, I wouldn't
> have spent almost all of my spare time (and then some) of the last
> five years of my life writing NET/NOS and making it work on the
> cheapest hardware platform (the IBM PC) that was usable despite its
> utterly brain-damaged architecture -- just so I could give it all away
> for free to the amateur radio community.  After all, there are already
> many commercial TCP/IP implementations that work well.  All it takes
> is money.  Source licenses to FTP Software's package cost something
> like $50,000 *each*.
>
> Nah, we don't care about cost.

The problem here--and it's by no means limited to this exchange of
messages--is that you two are talking about two different costs in
comparison to the cost of running a NET/NOS station.  Mojo is talking
about using NET as a functional equivalent of a TNC, while Phil is
talking about using it to construct a network.  Since a TNC costs $130
and a network costs thousands of dollars, you come to radically
different conclusions!

If what you want is to talk to your local AX.25 BBS so you can
receive messages, the TNC is the better solution: it's optimized
for that application and cheaper.  If what you want to do is help
construct a network that will support numerous applications for use
by multiple users, go with NOS/NET.  It's optimized for that use and
runs on the cheapest feasible hardware platforms.

--
Jon Bloom, KE3Z                              | American Radio Relay League
Internet: [e-mail]         |
Snail:    225 Main St., Newington, CT 06111  | "I have no opinions."

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

Date: 16 Nov 90 20:20:25 GMT
From: [e-mail]  (Patty Winter)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> [e-mail] (Christopher E. Piggott, WZ2B) writes:
>In article <[e-mail]> [e-mail] (Patty Winter) writes:
>>Idle curiosity: how come you don't use NET for AX.25 things?
>
>Well, some people have complained that the trace function of NOS produces
>too much text, making it impossible to casually monitor packets and
>maintain a conversation at the same time.


Yes, that drove me up the wall at first, too! Until Dewayne modified
the Macintosh code to put trace into its own window

That doesn't only happen with AX.25, though. Not sure why you mentioned
it in conjunction with that. The same problem occurs (in unmodified versions)
when you're running a TCP session and want to monitor the frequency.


Patty
--
*****************************************************************************
Patty Winter N6BIS                        INTERNET: [e-mail]
AMPR.ORG: [44.4.0.44]                     UUCP: {decwrl,nsc,sun}!apple!winter
*****************************************************************************

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

Date: 16 Nov 90 22:26:39 GMT
From: mintaka!think.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: Which TNC?
To: [e-mail]

[e-mail] (Bill Gunshannon) writes:

>I feel fairly certain that 56Kbit could be handled by most PC's as long as
>that was their primary task.  But not until we get the next generation of
>interface cards.  The cards we are trying to use now were all really designed
>for much slower serial links.

You really need a level of buffering, or at least DMA, to the extent that
as many packets that would arrive before the processor has to acknowledge
them to get more, should be fully bufferable before the CPU even has to be
interrupted.
--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 16 Nov 90 21:54:42 GMT
From: pasteur!dog.ee.lbl.gov!hellgate.utah.edu!cs.utexas.edu!helios![e-mail]  (Bill Hobson)
Subject: Which TNC?
To: [e-mail]

I wish I could get more people in my local area (central Texas)
interested in using NOS - it's a heck of a package and beats the heck
out of BBS reading and "talking" to other users through the keyboard!
If anyone has ideas on how to stimulate interest let me know.  Also, in
reply to those who want to use their PC for other things while NOS is
operating, how about Windows 3.0?  NOS works fine in background while I
fool around with other things.  I ran it on my 386SX with 2MB with no
problem, now with 4BM, it's even better!

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

Date: 17 Nov 90 01:32:26 GMT
From: envy![e-mail]  (Phil Karn)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>, [e-mail] ( co-op) writes:
|> Well, some people have complained that the trace function of NOS produces
|> too much text, making it impossible to casually monitor packets and
|> maintain a conversation at the same time.

Well, I put in the trace function originally so I could find protocol
implementation bugs. I still use it primarily for that purpose.

On any "real" network (like an Ethernet, or even a 56k channel) the
trace data goes by so fast you can't read it in real time no matter
how you present it to the user. It also slows things down considerably
(the CPU time spent scrolling the screen in a trace GREATLY exceeds
the time spent executing the protocol code.)  Indeed, if I'm trying to
troubleshoot a problem I'll usually direct tracing to a file (often on
RAMdisk) and then pore back over it at my leisure with a text editor.

But I suppose SOME peoples' networks are so sluggish that you actually
could follow everything that's happening AND carry on a conversation
if the trace output were only in a separate window. I guess I ought to
do something to keep these people happy. :-)

Phil

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

Date: 17 Nov 90 02:07:25 GMT
From: envy![e-mail]  (Phil Karn)
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]>,
[e-mail] (Phil Howard KA9WGN) writes:
|> You really need a level of buffering, or at least DMA, to the extent
that
|> as many packets that would arrive before the processor has to
acknowledge
|> them to get more, should be fully bufferable before the CPU even has
to be
|> interrupted.

Absolutely. The fact that the host CPU can't keep up with a particular
data rate while using a simple unbuffered interface board doesn't mean
that you have to have a full-blown outboard coprocessor.

In any network operating system there is always a conflict between
efficiency (i.e., maximizing average throughput) and limiting
interrupt response time (e.g., so that incoming data is not lost).

All you need to solve the conflict is simple, dumb hardware FIFO
buffering - enough of it that the host CPU doesn't have to quickly drop
whatever it's doing and race to "answer the doorbell" everytime a new
character arrives lest the character vanish before the CPU gets there.

With sufficient buffering, the CPU can take its time to finish cleanly
whatever it was doing when an interrupt arrives. It can also minimize
the number of "trips to the door" by gathering up data in bigger
batches on each trip. This frees cycles that can be better spent on
other things, like routing packets, running user applications, etc.

In NOS, I've tried to optimize throughput; this is one reason I chose
a "non preempting" task scheduler. That is, a task keeps the machine
until it explicitly gives it up by waiting for an event. Yes,
interrupt handlers do run asynchronously. But the only function of an
interrupt handler in NOS (beyond unblocking a task waiting for an
event, of course) is to "buy time" by buffering data until a regular
task can process or produce it.

In effect, I simulate dumb hardware FIFO buffering in the interrupt
handlers, and all actual processing of the data is deferred to the
regular tasks. But the cost of executing even these minimal interrupt
handlers for every character received is just too great when operating
at high speeds. For this there's really no alternative but to get some
hardware buffering, either in the form of FIFOs (e.g., NS16550A) or
DMA (e.g., the Ottawa 8530 board).

I cannot overemphasize the fact that the CPU cost of processing even
relatively "complex" protocol headers like those of AX.25 or TCP/IP
pales into utter insignificance beside the cost of merely receiving or
sending data on an interrupt-per-character basis.

Phil

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

End of Packet-Radio Digest
******************************
Date: Sun, 18 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #197
To: packet-radio


Packet-Radio Digest         Sun, 18 Nov 90       Volume 90 : Issue 197

Today's Topics:
                  BBS setup

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 17 Nov 90 13:30:50 GMT
From: eru!hagbard!sunic!news.funet.fi!ousrvr!ousrvr![e-mail]  (Ari Husa OH8NUP)
Subject: BBS setup
To: [e-mail]

This must have popped up somewhere.. but can anyone give a quick
overview of the NOS bbs setup - directories, files and their formats?

I suppose this is not (yet) in any of the NOS docs?

    Luru



--
    ///
    o-o    Ham Radio Operators Do It In Higher Frequency
     o

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

End of Packet-Radio Digest
******************************
Date: Tue, 20 Nov 90 04:30:10 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #198
To: packet-radio


Packet-Radio Digest         Tue, 20 Nov 90       Volume 90 : Issue 198

Today's Topics:
             Help needed with Heath H-89
             Local packet newsletter info
               Need Help with Xerox 820
       QRM problem to 14100kHz beacons from packet ops

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 19 Nov 90 21:54:08 GMT
From: rayssd![e-mail]  (John A. King)
Subject: Help needed with Heath H-89
To: [e-mail]

    *** WANTED ***
    A friend of mine with no net access
needs some help getting a Heath H-89
on Packet.
    His system is 64K RAM, with 5-1/4
soft-sectored floppies. He says the computer
works fine, but he has no software and
no computer knowlege. I'm trying to Elmer
him along, and would appreciate any help
with software for the H-89.
    Please respond via E-mail or packet:
     [e-mail] (Gary)
        or
     [e-mail] (Me)

  Thanks in advance.
--

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

Date: 18 Nov 90 05:20:41 GMT
From: usc!zaphod.mps.ohio-state.edu!caen!umich!sharkey!bnlux0!bnlls1.nsls.bnl.gov![e-mail]  (Bob Foxworth)
Subject: Local packet newsletter info
To: [e-mail]

[begin forwarded message]
Date: Sat, 17 Nov 90 12:35:37 EST
Message-Id: <[e-mail]>
From: [e-mail] (George Church)
To: nli91@kc2ky
Subject:
Status: R

>From [e-mail] Sat Nov 17 00:12:37 1990
Message-Id: <[e-mail]>


    *** POLI News ***
     ** 16 September 1990 **
      * NetNooze03 *

     PLEASE DISTRUBUTE FREELY!

Welcome to NetNooze, POLI's electronic newsletter. This
update is published as often as possible for the
benefit of Packeteers of Long Island members and all packeteers
within the POLI domain. Your comments and news tidbits are
welcome, so please jot them down and send them along.

*** POLI Meetings ***

     As reported in NetNooze01, Packeteers Of Long Island's
executive board has the Fall series of tutorials underway. The
calendar of meetings will carry the club through the remainder of
this year and on into 1991! Watch for packet club meeting
bulletins for dates and times.

Nominations for POLI officers at the November meeting resulted in
the following uncontested slate: Harry, WB2IBO for President;
John, KA2YMR, for VP; Jean, WA2BGE, for Secretary, and Frank,
KA2WJP for Treasurer. Elections are slated for the December
meeting.

Write-in nominations are also being taken. Watch for e-mail
announcements. By the way, all POLI members owe a hearty round of
applause to outgoing Treasurer Mario, WF2T, not only for superb
handling of the books, but for also getting the IRS and the State
of NY off POLI's back!

Oh yes, get ready for POLI's upcoming Holiday party!


*** WB2DVK Report ***

     Ron, WB2DVK, sends along the following material for NetNooze
readers. His initial comments relate to those of us building the
TCP/IP computer-to-computer communications net. His second
article describes some DSP developments:

    UNIX And Ham Radio--WB2SJZ has been experimenting with an
ATT 6300 unix-based computer, using an enhanced version of the
W2XO software that adapts UNIX for amateur use. The computer, on
line in the 144.91 subnet, has unique features embedded in the
code. For example, the software permits the sysop to provide
additional "sockets" which are accessible by initiating an ax25
connection to WB2SJZ-8 (this may later be augmented to accept
telnet connections).

    Gary Sanders N8EMR runs a landline bbs (614-895-2552, 2400-N-
8-1) that is a source of packet programs, including the UNIX
files that George is using, as well as NET and NOS files for IBM,
Mac and Amiga.

    There are enhancements in the works; watch for update
messages as things progress in the UNIX arena. The UNIX
environment may be the next wave of tcp/ip development beyond NET
and NOS, according to KA9Q and others. One reason for that is the
availability of economical UNIX computers on the new and used
market. -- WB2DVK.

Here are Ron's notes on DSP:

    DSP on the horizon - Digital Signal Processing modems are
here! The first of the wave of DSP modems designed for the
amateur radio market are being shipped from LL Grace. Based on
the V40 microcomputer, the modem is capable of operating in AFSK,
FSK, PSK modes to accommodate all of the present terrestrial and
satellite digital modulation and demodulation schemes. The DSP
modems handle present and future operating parameters using
software modem files that are uploaded to the modem's RAM so that
EPROM updates become a thing of the past.

    At $600, these units are meant for applications that warrant
the wide versatility that DSP modems offer. The technology isn't
new, it just hasn't been fully utilized in the amateur radio
market. Most of the telephone modems in use are DSP modems, using
the various DSP chips offered by Texas Instrument, Motorola,
AT&T, NEC and others. -- WB2DVK.


*** News Directly From WB2SJZ ***

George, WB2SJZ, sends along the following observations:

     I have been experimenting with a modified version of net I
recently received from N8EMR - Gary Sanders. It runs on a UNIX
PC-7300 and allows use of external sockets.  This version also
allows new mailbox commands to be created and mapped to external
sockets.

     I have defined several external sockets on my system by
writing some short shell scripts (batch files). Nothing
elaborate. They are no more than several lines long, but it shows
the kinds of things that can be done very easily with external
sockets. I have also created matching mailbox commands.

     Anyone interested in having a look can connect to my mailbox
wb2sjz-8. Once connected hit return then type 'h' for help.
Follow the help menu from there. For now please do not do a
telnet to the sockets listed.

...ENJOY & 73, George......

PS nli59 subnet s/b able to connect via n1dl-10 (mulport is on).
-- WB2SJZ.


*** Reader Feedback ***

NetNooze received this nice comment from TCP/IP developer John,
N2HLE in Coram:

 "NetNooze, eh? That was a good editorial. I enjoyed reading it."

Many thanks for the e-mail John!


*** Wormhole Developments ***

     Frank, WA2NDV, continues to work on the "wormhole" to Europe
as reported in NetNooze02. Working around callsign regulatory
roadblocks, flow control problems under KISS, and the limitations
of PRMBS software, Frank is making progress.

     POLI has funded a multi-band antenna for the New York City
site at NBC's Rockefeller Plaza, and Harry, WB2IBO owns most of
the remaining gear. Frank anticipates the wormhole project may
take quite a few months to actualize, largely due to legal
problems in the U.K. The hardware and software configuration is
rather complex as well.


*** WA2WAI TCP/IP Repeater Gets Workout ***

     The 448.775 MHz full duplex TCP/IP packet repeater,
WA2WAI/PR, is really getting a good workout these days, thanks to
Stan's untiring efforts to get the equipment working in an
optimal manner. Stan has been roaming the countryside with a
borrowed IFR signal analyzer, tuning transmitters in the TCP/IP
net as well as the repeater itself.

     The repeater is providing collision-free links between
WA2WAI and KC2KY's switch. This results in marked improvements in
throughput over the collision prone N1DL-10 POLI switch operating
at the Pinelawn site. N1DL-10, although multi-ported, still
suffers from the bane of packet radio--hidden transmitters.

     I have been having close to "realtime" keyboard QSOs with
WA1EQU in the Boston area, thanks to WA2WAI/PR.


*** KA9Q TCP/IP Gets More Powerful ***

     The advent of Phil Karn's New Operating System, aka NOS,
spells P-O-W-E-R in the TCP/IP computer-to-computer Amateur
network. Although still under development (and thus not bug
free), NOS includes the capability of running POP, RSPF, and RIP.
The latter automatically sets up routing for IP packets, much
like NetRom does in the AX.25 virtual circuit world. RSPF, the
Route Shortest Path First algorithm, works similarly. These
protocols promise freedom from the chore of maintaining intricate
and lengthy routing tables in a world where callsigns change,
computers come and go, and paths degrade or get better.

     Good news for the "I-can't-leave-my-computer-on-24-hours"
crowd is POP, the Post Office Protocol. N2PL and others have used
POP successfully in the NLI TCP/IP network to automatically
retrieve their mail carried by the TCP/IP network to their local
IP mail server.

     When they start up their TCP/IP computers and come on the
air, POP polls their nearest IP server station and their mail
automatically arrives at their own personal computer. Naturally,
the TCP/IP computers that are left on the air continuously still
switch IP frames, engage in full-tilt file transfer, and handle
remote processes like FCC database servers, "chat" servers, ,etc.


*** Ap-Link RTTY Connection ***

     Jules, W2JGR, reports he's been receiving the world-wide
distribution of the VK RTTY DX Report via Ap-Link, the 20 meter
AMTOR-to-packet system. Long Island packeteers receiving this
informative series of bulletins have Jules to thank!

*** 9600 Baud Plans ***

     A successful high speed link has been tested over a 9.5 mile
path between Mike, KA2FIR, and Alex, AI2Q on 145.59. Mike used a
G3RUH board and a Kantronics DVR2-2 radio. Alex used a G3RUH
board and a Maxon CP-1015 HT. The present LAN PLAN calls for all
operation at 9600 baud with WA2WAI as the gateway computer to the
WA2WAI/PR repeater. All 9600 baud LAN operations on 145.59 will
use TCP/IP, just as they do now. Other stations using 1200 baud
are expected to QSY to 448.775 MHz.

*** That's it for this issue. No more room! :-) Send e-mail
items for inclusion to AI2Q @ AI2Q or to IP address 44.68.24.8.
Very 73 for now! -- AI2Q, NetNooze ed.

[end forwarded message. Alex, ai2q, is in Freeport, L.I. New York]
[Neither my organization BNL nor its contractors have any responsibility
for this message.]
73, k2euh

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

Date: 19 Nov 90 21:50:31 GMT
From: rayssd![e-mail]  (John A. King)
Subject: Need Help with Xerox 820
To: [e-mail]

        *** WANTED ***
    I have taken a technological step backwards
and have acquired a Xerox 820-II with 8-inch
SS/DD floppies for use with my packet station.
    I would like to set up a personal mailbox,
possibly with forwarding capability. I don't
need a full blown BBS; we have quite enough of
them on the air here.
    Can anyone help me out with software? My
TNC is a TAPR TNC-2 (original ROMs) and the
Xerox is running (don't snicker) CP/M.
    Thank you in advance,
             John King,
       [e-mail]
---

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

Date: 18 Nov 90 05:05:15 GMT
From: csus.edu!wuarchive!zaphod.mps.ohio-state.edu!caen!umich!sharkey!bnlux0!bnlls1.nsls.bnl.gov![e-mail]  (Bob Foxworth)
Subject: QRM problem to 14100kHz beacons from packet ops
To: [e-mail]

[begin forwarded message. I agree with Norm's remarks -k2euh]

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

Date: (null)
From: [e-mail]
To: ALL@NLI

I sincerely hope that the internationally-recognized propagation beacons
have all been withdrawn from their traditional place on 14100.00 kHz.  I
hope so, because it appears that any beacon trying to "do its thing" on
that channel will be absolutely inundated by the horrendous packet
racket currently taking place on or within a few cycles of that
supposedly protected channel.

You don't have to be an expert to understand this problem.  Propagation
beacons operating with low powers down to a few watts simply cannot
survive amidst this monstrous gang of packet bandits that infests the
14100.00 kHz region.

Is it possible that these packet freaks simply do not KNOW about the
beacons?  Is it possible that they cannot pick a channel at least one
kilohertz AWAY from the 14100.00 kHz spot?  Is it possible that they
don't understand how to read and interpret their radio's tuning display?

It's easy to hear and see who is operating on or near the beacon
channel.  Just set your packet TNC to whatever it needs to copy 300 BPS
packets on HF.  Next, set your radio to "CW", then "LSB", then "USB",
then "FSK".  Now rock your tuning dial a wee bit -- one hundred cycles
will do -- and watch the collection of eggheads, turkeys and idiots
running BBSs, mailboxes and KA Nodes and the like!  And I'll wager - no,
I'll guarantee it! -- a number of these American packet systems run
unattended, an obvious violation of Part 97.

[end forwarded message]
[my organization BNL or its contractors have no opinion or responsibility
for anything here. Especially here...]
73 k2euh

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

End of Packet-Radio Digest
******************************
Date: Wed, 21 Nov 90 04:30:08 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #199
To: packet-radio


Packet-Radio Digest         Wed, 21 Nov 90       Volume 90 : Issue 199

Today's Topics:
                  Hi

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Tue, 20 Nov 90 09:31 PST
From: [e-mail]
Subject: Hi
To: [e-mail]

I would like to subscribe to your list.
Can you send me startup instructions?

thanks,

frappe

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

End of Packet-Radio Digest
******************************
Date: Fri, 23 Nov 90 04:30:10 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #200
To: packet-radio


Packet-Radio Digest         Fri, 23 Nov 90       Volume 90 : Issue 200

Today's Topics:
            FT-470/TNC connection
            HF Packet with TS830S (2 msgs)
        ka9q (nos) compiled under microsoft c
          KAM  <---> MBL 512 problem, HELP NEEDED !
                Minix
 To heck with TNC's, they are just a bottleneck (was: Re: Which TNC?)
                  Which TNC?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 20 Nov 90 21:53:33 GMT
From: ogicse!intelhf!donk![e-mail]  (jerry)
Subject: FT-470/TNC connection
To: [e-mail]

While waiting for my license to appear in the USnail, I thought I'd
put the wiring together for my HK-232 and FT-470.

When I bought the Yaesu, the salesman also sold me a sub-minature
stereo plug for the PTT/AUDIO jack. I assumed that PTT and AUDIO
were two seperate lines and was prepared to wire it as such.

Now after reading about 3 different articles on wiring hand-helds,
they all seem to indicate that PTT/AUDIO are on the tip.

Anyone want to give me some first-hand information? I really don't
want to re-wire or possibly damage either the TNC or the Yaesu.

Thanks in advance.

***************************************************************************
* Intel may own me body and soul, but these opinions are MINE. So there.  *
*-------------------------------------------------------------------------*
* [e-mail]         You can find me either here or        *
* [e-mail]         here                                  *
*-------------------------------------------------------------------------*
* "We have ways to make you scream."                                      *
* -- Intel advertisement, in the June 1989 Doctor Dobbs Journal           *
***************************************************************************

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

Date: 22 Nov 90 03:19:14 GMT
From: van-bc!ve7apu![e-mail]  (Bob Smits - VE7EMD)
Subject: HF Packet with TS830S
To: [e-mail]

Distributionworld : na
Organization: VADCG, Richmond, B.C.
Keywords:HF Packet,TS830S

In article <[e-mail]> jkaidor@ (Jerome Kaidor) writes:
>
>    Hi!   I'd like to tap into the net.wisdom here.  I just acquired a
>TNC, and I'd like to run HF packet with my venerable TS830.  But I now
>see that the optimum bandwidth is something like 500Hz.  Now, the
>TS830 has only one SSB position, with a 2.4 kHz filter. I _do_ have
>500Hz CW filters in both IFs ( 16 poles of 500Hz! ), but they are
>selectable only in the "CW Narrow" position.  Does anyone know of a
>modification to get the narrow filters in SSB mode on these radios?
>Alternately, I suppose I could run true FSK, with a capacitor
>diode-switched at some strategic spot.  This would be relatively
>straightforward to do in the CW mode. Of course, then I would have to
>do some kind of modification to the TNC ( MFJ1278 ) to get the digital
>data out for the FSK....  Has anybody out there already invented this
>wheel?  Hopefully, I'll find out that the filter is chosen with a dc
>level....
>
I used to run HF RTTY and HF packet with my Kenwood TS-820S which has
a similar filter arrangement. Don't confuse the HF packet shift (200 Hz)
with the HF packet bandwidth. You will have a hard time copying HF sigs
through a 500 Hz filter. HF RTTY, with its much slower baud rate and only
170 Hz shift will worOK as long asF shift straddles the centre of
of the signal.

I rewired the digital hold switch (a really useless switch) tturn on
the CW narrow filter instea

Your TS-830 would probably work much better for HF packet by installing
the "narrow SSB" filter, which the book says has a 60 db bandwidth of
900 Hz. If you're determined to try, however, the TS-830 uses mode switch
S18-5 to switch a positive DC voltage to either the SSB position or one
of four CW positions - CW1,CW2,CW3 and CW4. A diode matrix controls
which pairs of filters in the IF are gated on.

In SSB mode, the standard 2.7 Khz SSB filters in the 8.83 Mhz IF and the
455 Khz IF are turned on. Ditto for CW1.

An "on" signal at CW2 will turn on the optional 500 Hz wide 8.83 Mhz IF
filter and the 2.7 Khz wide 455 Khz IF filter.

An "on" signal at CW3 will turn on the 2.7 Khz wide 8.83 Mhz IF filter
and the optional 250 Hz wide 455 Khz IF filter.

An "on" signal at CW4 will turn on the 500 Hz wide 8.83 Mhz IF filter
and the 250 Hz wide 455 Khz IF filter.

The signal voltage going to S18-5 's wiper is labelled RLR and comes from
the AF board. Don't forget to disconnect the SSB line when one of the CW
positions is enabled.

Hope this helps.

73, Bob, VE7EMD

.

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

Date: 20 Nov 90 23:39:01 GMT
From: bionet!synoptics!@apple.com  (Jerome Kaidor)
Subject: HF Packet with TS830S
To: [e-mail]

Followup-To:
Distribution: world
Organization: SynOptics Communications Inc. Santa Clara, Ca.
Disclaimer: Sender is *solely* responsible for the contents of message
Keywords:

    Hi!   I'd like to tap into the net.wisdom here.  I just acquired a
TNC, and I'd like to run HF packet with my venerable TS830.  But I now
see that the optimum bandwidth is something like 500Hz.  Now, the
TS830 has only one SSB position, with a 2.4 kHz filter. I _do_ have
500Hz CW filters in both IFs ( 16 poles of 500Hz! ), but they are
selectable only in the "CW Narrow" position.  Does anyone know of a
modification to get the narrow filters in SSB mode on these radios?
Alternately, I suppose I could run true FSK, with a capacitor
diode-switched at some strategic spot.  This would be relatively
straightforward to do in the CW mode. Of course, then I would have to
do some kind of modification to the TNC ( MFJ1278 ) to get the digital
data out for the FSK....  Has anybody out there already invented this
wheel?  Hopefully, I'll find out that the filter is chosen with a dc
level....

    - Jerry Kaidor,  KF6VB

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

Date: 20 Nov 90 22:03:49 GMT
From: van-bc!ubc-cs!alberta!mts.ucs.UAlberta.CA!ualtavm![e-mail]  (Geoffrey Holan)
Subject: ka9q (nos) compiled under microsoft c
To: [e-mail]

under Microsoft C. Also is there a version that
has snmp built into it?     Thanks in advance.

        [e-mail]

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

Date: 20 Nov 90 20:41:09 GMT
From: rochester!kodak!uupsi!sunic!news.funet.fi!ousrvr!ousrvr![e-mail]  (Marko Wirtanen)
Subject: KAM  <---> MBL 512 problem, HELP NEEDED !
To: [e-mail]

Our club station has bought a KAM tnc which do not operate properely with
MBL box software. We had a TAPR-clone before, and it operated well.
Now with KAM it goes to a permanent loop, when a station is connected
to the MBL. MBL watches a DCD pin and when it goes up, MBL sends a CTRL-C
to switch tnc to command mode. Then MBL sens C to have information who
has connected. TAPR clone answers Link state is connected to ...
and KAM answers  A/V Link state is connected to ...  and this A/V
may be the reason.
Is it possible to mask out this A/V, or is it possible tu use KAM with
MBL at all ??????

Please send me information about this problem.

--


 ------------------------------------------------------------------------
    Marko Wirtanen                     E-mail: [e-mail]
 Rakentajantie 5C 406                  Phone: [phone]
    SF-90570 Oulu                      Ham Radio Call: OH8WM / OH3MMW
      FINLAND

      "Once you are in communications, you will never be out of it"
 ------------------------------------------------------------------------

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

Date: 19 Nov 90 12:05:11 GMT
From: cti1![e-mail]  (Mark Pledger)
Subject: Minix
To: [e-mail]

[e-mail] (Meir I Green) writes:

>How can I get a copy of Minix?
> * * * * * * *  ======================= Meir Green                           |
>* * * * * * * * ======================= [e-mail]           |
> * * * * * * *  ======================= N2JPG                                |

How about buying it.  You have to purchase it from Prentice-Hall it will cost
you about $150.00!


--
Sincerely,


Mark Pledger

--------------------------------------------------------------------------
CTI                              |              [phone] [voice]
2121 Crystal Drive               |              [phone] [fax]
Suite 103                        |
Arlington, DC  22202             |              [e-mail]
--------------------------------------------------------------------------

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

Date: 20 Nov 90 19:03:51 GMT
From: van-bc!ubc-cs!alberta!atha!aupair.cs.athabascau.ca![e-mail]  (Ross Alexander)
Subject: To heck with TNC's, they are just a bottleneck (was: Re: Which TNC?)
To: [e-mail]

[e-mail] (Phil Karn) writes:
>In article <[e-mail]>, [e-mail] (Brian Kantor) writes:
>|> is being received.  The answer here is not perfectly clear: you could
>|> simply have a smarter HDLC card with a bunch of buffering (and perhaps
>|> memory windows), or you can build a complete protocol engine on a card.
>This is because the presently-available HDLC cards don't support DMA
>and have minimal internal buffering (the 8530 has only 3 bytes worth
>on the receiver, and none on the transmitter, I believe).  With DMA
>(or some other form of external buffering, such as FIFOs), even a slow
>4.77 MHz XT has no problem at all dealing with 56kb data streams. Note

This may be relevant to the discussion; pardon me if it has been
posted here previously, but this is I think the solution to the
problem at hand (I myself am strongly in the "we don't need no
steeking TNCs or coprocessors" camp, BTW; give me one big fast CPU
with fast task switch and I'm quite happy, I feel the same way about
soi-disant "intelligent" disk controllers too :-):

     Return-Path: <alberta!dgbt.doc.ca![e-mail]>
     Date: Mon, 15 Oct 90 14:18:24 EDT
     From: [e-mail] (Barry McLarnon DGBT/DIP)
     Subject: Re:  PI board info request

     The Packet Working Group of the Ottawa Amateur Radio Club, Inc.
     is pleased to announce the PI (Packet Interface) card.

     The PI card is a cost-effective PC-compatible synchronous
     interface card for high-speed packet radio.  Designed for
     operation at speeds up to 57600 bits per second, this card
     offers the packet radio experimenter high performance at a
     reasonable cost.

     The PI card offers the following features:

       o Dual channel operation: 1 high-speed DMA, 1 low-speed
     non-DMA
       o Driver software for KA9Q NOS included
       o Compatible with PC,PC/XT, and PC/AT type systems
       o Low-speed port configurable for either RS-232 or TTL
     levels
       o Small size (5.25" length)

     The PI card has been extensively tested with the WA4DSY 56kb/s
     modem and KA9Q NOS, on various XT- and AT-class systems.  With
     suitable choice of parameters, FTP throughputs of as high as
     5600 bytes/s on half-duplex RF links have been attained.

     The PI card is available only fully assembled and tested,
     for US$120, or CDN$140.

     The package includes KA9Q NOS configured for the PI card, and
     installation documentation with schematics.  Software updates
     will be available via FTP from several INTERNET sites.  Updates
     on floppy will be available for $5, for postage and handling.

     Support will be available via USENET, the Internet, Compuserve,
     and the PBBS system.

     ________________________________________________________________

     Send this order form to:
      Ottawa Amateur Radio Club, Inc.
      P.O. Box 8873
      Ottawa, ON
      K1G 3J2
      CANADA
      Attn: Packet Working Group
     ________________________________________________________________

     Name:   ________________________________________
     Address: __________________________________ Prov./State: __________
     Zip/Code: ____________________ Country: __________
     Telephone: ______________________________
     E-mail address(es): ______________________________
     Quantity required: ____________________  x US$120/CDN$140
     Total amount enclosed: ____________________

     Please make cheque or money-order payable to
      "Ottawa Amateur Radio Club".
     Please allow four to six weeks for delivery.
--
--
Ross Alexander    [e-mail]    [phone]    ve6pdq

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

Date: 20 Nov 90 22:12:17 GMT
From: rochester!kodak!uupsi!cci632![e-mail]  (Just another hired gun (n2hkd))
Subject: Which TNC?
To: [e-mail]

In article <[e-mail]> mdivax1!bb12c!jackb (Jack Brindle) writes:
>In article <[e-mail]> [e-mail] (Tom Varga) writes:
>>
>>       ...  stuff deleted ...
>>
>>
>There are a couple of reasons folks come up with not to do this. One
>involves mailboxes on packet. To do this reasonably well, you need to leave
>the system on. Do you want to leave your SE/30 on all the time? (at least
>with MF it won't be dedicated to packet :-) ). It also means that, with a
>PC, you need to devote your PC to packet only. It is aggravating to be
>waiting for a message or connect and need to do work on the machine. Kind
>of stops things (again, thanks MultiFinder).
Now hear's a neat thought about that thread.

Why does mail have to be done that way? Why not use a 'hub' or 'gateway'
style system running POP (post office protocol). If the local mys machine
could handle POP then the BBS in your area would have your mail. When
you come home for dinner, run ka9q, have dinner, read yuour mail.
Doing this would allow you to use your (enter favorite computer type
here) for this purpose only when you need it. Also set up a
public area for sharing files between users. Let the first user
put it on the file server, send mail, second user retrieves it,
second user deletes it, and second user emails first user of success.

Funny thing is that this is done regularly here between the remote
(dial in appletalk/TCPIP slip) users and our service bereau.

Just a thought about systems and solutions vs. the solo game.

Side note: maybe this would work really well if the local users
of the local BBS would form a maintence club for donations to
keep the BBS upgraded and up to capacity so that the SYSOP doesn't
go broke.  (remeber a lot of small donations can go a long way
when compared to the individual efforts).
>
>- Jack Brindle, WA4FIB/7.

--

email:   [e-mail] or cb@cci632  or !rochester!kodak!n2hkd!curtis
Curtis Braun, N2HKD, Computronics, PO Box 1002 Fairport NY, 14450

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

End of Packet-Radio Digest
******************************
Date: Sat, 24 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #201
To: packet-radio


Packet-Radio Digest         Sat, 24 Nov 90       Volume 90 : Issue 201

Today's Topics:
             information sources?
           internet-packet radio mail How to do it?
                Minix (2 msgs)
                 Packet Radio
 To heck with TNC's, they are just a bottleneck (was: Re: Which TNC?)
                  Which TNC?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 22 Nov 90 01:12:35 GMT
From: sco![e-mail]  (John DuBois)
Subject: information sources?
To: [e-mail]

<obligatory statement about how i'm sure this
question has been asked a zillion times before>

     Are there any good books or other sources of information on packet radio?
The tcp/ip stuff discussed here sounds particularly interesting; I have a
XENIX box that would love to be involved :-)  Anyone know if there's packet
traffic in the Monterey Bay area?
     Regarding serial io overhead...  I have an old (well, 3 years old) smart
multiport board.  It has an 8088 onboard for smarts, and 128k of dual-port
memory for a buffer and communication with the host cpu.  Since it's dual-
ported, io is as fast as memory access.  It can be set during initialization
to only interrupt when a certain amount of data has accumulated, etc.  This
is pretty old stuff, and cheap nowadays.  It seems to me that this sort of
hardware + a modem will always be cheaper than a dedicated TNC that includes
onboard cpu and (preferably memory-mapped) buffer, since there is a *much*
larger market for it... yes, the protocol will then have to be handled by
the host, but I think even my lowly SX would be able to handle it with plenty
of CPU time to spare for the other things it's used for, esp. with the nice
buffers.  It can't be much worse than SLIP.

    John DuBois
    [e-mail]

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

Date: 21 Nov 90 09:37:07 GMT
From: eru!hagbard!sunic!mcsun!unido!ira.uka.de!fauern!lan![e-mail]  (Oliver Breidenbach)
Subject: internet-packet radio mail How to do it?
To: [e-mail]

Hi there,
I'm a kind of new in this business. So I'm not quite sure if anything I write
is understandable. But I'll try my best.
I currently, as I understand it I'm working on a net called internet. As I
know, there are several gateways to other nets. So I think there may be a
gateway to packet radio as well. The idea is to send e-mail to some friend
of mine, who doe's packet radio.
Can anyone tell me, how that will work?
Thanks in advance,

Oliver 'Broke' Breidenbach

understandab

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

Date: 23 Nov 90 20:33:17 GMT
From: swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!economics.adelaide.edu.au![e-mail]
Subject: Minix
To: [e-mail]

You can download MINIX from quite a few anonymous ftp sites on the net.
(In source and executable form)

                -David.

[e-mail]
OR [e-mail]           Adelaide University, South Australia.

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

Date: 23 Nov 90 23:18:49 GMT
From: uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ub![e-mail]  (Devon E Bowen)
Subject: Minix
To: [e-mail]

In article <[e-mail]>, [e-mail] writes:
> You can download MINIX from quite a few anonymous ftp sites on the net.
> (In source and executable form)

I hope not. Prentice-Hall holds the copyrights and sells it for about $150.
What goes around on the net are upgrade patches and programs for minix that
others write and decided to put in the public domain. They assumes you have
already purchased a copy from PH, though.

For more info on minix, I'd recommend comp.os.minix.

Devon

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

Date: 22 Nov 90 03:24:30 GMT
From: usc!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!utorvm!ryerson![e-mail]  (Roger Smith)
Subject: Packet Radio
To: [e-mail]

Greetings,
Could some one point me in the right direction as to the ideal transceiver
for high speed (well 9600 baud) packet operations, what of the direct
connect digital radios that were once touted on this net.
  Is there such a thing as the ideal transceiver for packet operations?
Roger Smith

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

Date: 23 Nov 90 07:13:22 GMT
From: lib![e-mail]  (Jay Maynard)
Subject: To heck with TNC's, they are just a bottleneck (was: Re: Which TNC?)
To: [e-mail]

In article <[e-mail]> [e-mail] (Ross Alexander) writes:
>This may be relevant to the discussion; pardon me if it has been
>posted here previously, but this is I think the solution to the
>problem at hand (I myself am strongly in the "we don't need no
>steeking TNCs or coprocessors" camp, BTW; give me one big fast CPU
>with fast task switch and I'm quite happy, I feel the same way about
>soi-disant "intelligent" disk controllers too :-):

That's great, but what if the computer you already have is working its
status bits off just doing the real work that earns its keep? It looks like
moving from a 10 MHz 286 to a 10 MHz 68010 is going to get me a machine
that, while it may be more reliable, is _slower_ (the best case Dhrystone
comparison shows the 68010 to only be 64% the speed of the 286). That means
the Unix box will have even less time to stuff packets and still do other
useful work.

I plan to address the problem with a PC with an Ottawa card - but that goes
from a $125 TNC to a $600 TNC - hardly an improvement.

--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
[e-mail]  | adequately be explained by stupidity.
     "With design like this, who needs bugs?" - Boyd Roberts

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

Date: 16 Nov 90 05:50:18 GMT
From: n3dmc![e-mail]  (John Limpert)
Subject: Which TNC?
To: [e-mail]

[e-mail] (Jon Bloom) writes:
>I'm not sure a 4.77 MHz XT could even handle continuous
>56 kbit/s data.

I've processed data at a continuous rate of 500 kbps on an original
IBM PC (4.77 MHz 8088).  The system was receiving 4800 bit packets
on a synchronous line.  The interface hardware used DMA, just one
interrupt per 4800 bit packet.  The bandwidth of the PC's I/O bus
was the limiting factor.

--
John A. Limpert         The strongest reason for the people to retain the right
[e-mail]   to keep and bear arms is, as a last resort, to protect
uunet!n3dmc!johnl       themselves against tyranny in government.  T. Jefferson.

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

End of Packet-Radio Digest
******************************
Date: Sun, 25 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #202
To: packet-radio


Packet-Radio Digest         Sun, 25 Nov 90       Volume 90 : Issue 202

Today's Topics:
           FTP site for KA9Q NOSNET wanted.
               TCP/IP via NET/ROM nodes

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 22 Nov 90 15:22:19 GMT
From: mvb.saic.com!ncr-sd!ncrlnk!ncrstp!npdiss1![e-mail]
Subject: FTP site for KA9Q NOSNET wanted.
To: [e-mail]

Does anyone know of an anonymous FTP site for aquiring
Phil Karn's TCP/IP NOSNET software?  Also, if anyone knows who
the IP coordinator for the Minneapolis area is I'd appreciate that
info.


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

Date: 24 Nov 90 14:40:38 GMT
From: att!cbnewsj![e-mail]  (thomas.kenny)
Subject: TCP/IP via NET/ROM nodes
To: [e-mail]

I'm trying to get net running at my station at home and this is
my first experience in setting up a host. I am not able to reach
any IP switches due to lower power and such at this time. Until
I get more power out and a beam antenna I'd like to reach an IP
switch via NET/ROM nodes which I am able to reach. I believe this
can be done but have not found the right commands yet. I'm assuming
it's some sort of special route command... Please send me email
if you think you can help me out. Thanks and 73 DE KB2GLO, Tom.

--
Tom Kenny, KB2GLO
uucp:   att!lzatt!tek          internet: [e-mail]
packet: [e-mail]  ampr: [e-mail] [44.64.0.10]

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

Date: (null)
From: (null)
--
Chuck Rissmeyer  - [e-mail]
KE0VG            - KE0VG @ WB0GDB.mn.usa.na.earth
MENSA            - Minnesota (1129142)

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

End of Packet-Radio Digest
******************************
Date: Mon, 26 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #203
To: packet-radio


Packet-Radio Digest         Mon, 26 Nov 90       Volume 90 : Issue 203

Today's Topics:
      AMIGA: where to find KA9Q files for anonymous FTP
       ARC: where to find KA9Q files for anonymous FTP
      ATARI: where to find KA9Q files for anonymous FTP
       MAC: where to find KA9Q files for anonymous FTP
      MSDOS: where to find KA9Q files for anonymous FTP
       TAR: where to find KA9Q files for anonymous FTP
       ZIP: where to find KA9Q files for anonymous FTP
       ZOO: where to find KA9Q files for anonymous FTP

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 26 Nov 90 00:16:14 GMT
From: usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: AMIGA: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files which matched "amiga" anywhere in their path name:

brolga.cc.uq.oz.au:   116727 Mar  8  1988 pub/ka9q/amiga_binaries.uu
brolga.cc.uq.oz.au:   163453 Feb 18  1988 pub/ka9q/net_amiga.uu
freebie.engin.umich.edu:   887197 Oct 12 18:28 pub/Amiga/ka9q_slfp.tar.Z
louie.udel.edu:   116727 Dec 22  1989 pub/ka9q/amiga_binaries.uu*
louie.udel.edu:   163453 Dec 22  1989 pub/ka9q/net_amiga.uu
sunic.sunet.se:   512188 Jan 28  1990 .sics.se/archive/packet/ka9q/nos/amiganos.zoo
terminator.cc.umich.edu:   887197 Oct 12 18:20 pub/amiga/ka9q_slfp.tar.Z
thumper.bellcore.com:   203787 Nov 12 11:03 pub/ka9q/amiga/AmigaKIT19.lzh
thumper.bellcore.com:   215584 Oct 29 12:50 pub/ka9q/amiga/AmigaNOS17
thumper.bellcore.com:   326119 Oct 29 12:51 pub/ka9q/amiga/AmigaNOS17.lzh
thumper.bellcore.com:   339156 Nov 12 11:04 pub/ka9q/amiga/AmigaNOS19.lzh
thumper.bellcore.com:     9704 Oct 23 15:37 pub/ka9q/amiga/amiganos.ls
thumper.bellcore.com:     1315 Oct 23 15:39 pub/ka9q/amiga/amiganos.nos-startup
thumper.bellcore.com:     8272 Oct 23 15:38 pub/ka9q/amiga/amiganos.nos0214.txt
thumper.bellcore.com:   203718 Nov 13 11:37 pub/ka9q/incoming/AmigaKIT19.lzh
thumper.bellcore.com:   200704 Nov 13 11:38 pub/ka9q/incoming/AmigaNOS19.lzh

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:22:36 GMT
From: usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: ARC: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files that matched ".arc" in their pathnames:

aggie.ucdavis.edu:   128366 Apr  5  1990 dist/ucdmail/ka9q/netpop2.arc
aggie.ucdavis.edu:    51513 Apr  5  1990 dist/ucdmail/ka9q/pop2src.arc
aggie.ucdavis.edu:   457082 Apr  5  1990 dist/ucdmail/ka9q/src.arc
apple.com:    85066 May 14  1989 pub/ArchiveVol1/tcpip/ka9q/drivers.arc
apple.com:   100352 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/msysd102.arc
apple.com:   239616 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/msysp102.arc
apple.com:   171989 May 14  1989 pub/ArchiveVol1/tcpip/ka9q/net_pc.arc
apple.com:   511664 May 14  1989 pub/ArchiveVol1/tcpip/ka9q/net_src.arc
apple.com:    57076 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/tnc_ash.arc
apple.com:    15790 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/tnc_ldr.arc
apple.com:    52127 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/tnc_tnc1.arc
apple.com:    49542 Apr  9  1989 pub/ArchiveVol1/tcpip/ka9q/tnc_tnc2.arc
apple.com:   148547 May 14  1989 pub/ArchiveVol1/tcpip/ka9q/userman.arc
apple.com:    51076 May 14  1989 pub/ArchiveVol1/tcpip/ka9q/xobbs.arc
brazos.rice.edu:     7413 Jan 12  1988 pub/KA9Q/nelson.ARC
brazos.rice.edu:   108322 Jan  5  1988 pub/KA9Q/net_amig.ARC
brazos.rice.edu:    19127 Jan 12  1988 pub/KA9Q/net_bm.ARC
brazos.rice.edu:    26249 Jan 12  1988 pub/KA9Q/net_des.ARC
brazos.rice.edu:   143157 Jan 12  1988 pub/KA9Q/net_doc.ARC
brazos.rice.edu:   116992 Jan  5  1988 pub/KA9Q/net_mac.ARC
brazos.rice.edu:   126524 Jan 12  1988 pub/KA9Q/net_pc.ARC
brazos.rice.edu:   302422 Jan 12  1988 pub/KA9Q/net_src.ARC
brazos.rice.edu:    47379 Jan  5  1988 pub/KA9Q/pxx107.ARC
brazos.rice.edu:    57076 Jan 12  1988 pub/KA9Q/tnc_ash.ARC
brazos.rice.edu:    15790 Jan 12  1988 pub/KA9Q/tnc_ldr.ARC
brazos.rice.edu:    52127 Jan 12  1988 pub/KA9Q/tnc_tnc1.ARC
brazos.rice.edu:    49542 Jan 12  1988 pub/KA9Q/tnc_tnc2.ARC
brolga.cc.uq.oz.au:    48964 Mar 31  1988 pub/ka9q/am.arc
brolga.cc.uq.oz.au:    31080 Feb 18  1988 pub/ka9q/bdalebits.arc
brolga.cc.uq.oz.au:   171235 Aug 18  1988 pub/ka9q/finger.arc
brolga.cc.uq.oz.au:    13667 Dec 15  1987 pub/ka9q/intrlv.arc
brolga.cc.uq.oz.au:   108322 Dec 30  1987 pub/ka9q/net_amig.arc
brolga.cc.uq.oz.au:    70775 Apr 23  1988 pub/ka9q/net_bm.arc
brolga.cc.uq.oz.au:    26249 Dec 30  1987 pub/ka9q/net_des.arc
brolga.cc.uq.oz.au:   143194 Jan 20  1988 pub/ka9q/net_doc.arc
brolga.cc.uq.oz.au:   115955 May 18  1988 pub/ka9q/net_ew.arc
brolga.cc.uq.oz.au:   142297 Jul 21  1988 pub/ka9q/net_pc.arc
brolga.cc.uq.oz.au:   318378 Jul 21  1988 pub/ka9q/net_src.arc
brolga.cc.uq.oz.au:   343796 Jun 27  1988 pub/ka9q/net_srcT.arc
brolga.cc.uq.oz.au:    56320 Feb 13  1988 pub/ka9q/netam_src.arc
brolga.cc.uq.oz.au:    19816 Apr 27  1988 pub/ka9q/nrbdale.arc
brolga.cc.uq.oz.au:   151494 Aug 23  1988 pub/ka9q/nrnet.arc
brolga.cc.uq.oz.au:    18143 Feb 18  1988 pub/ka9q/phil.arc
brolga.cc.uq.oz.au:    37094 Apr  6  1988 pub/ka9q/pxx111.arc
brolga.cc.uq.oz.au:     9220 Dec 15  1987 pub/ka9q/ramdisk.arc
brolga.cc.uq.oz.au:    40448 May 19  1988 pub/ka9q/server16.arc
brolga.cc.uq.oz.au:    57076 Dec 30  1987 pub/ka9q/tnc_ash.arc
brolga.cc.uq.oz.au:    15790 Dec 30  1987 pub/ka9q/tnc_ldr.arc
brolga.cc.uq.oz.au:    52127 Dec 30  1987 pub/ka9q/tnc_tnc1.arc
brolga.cc.uq.oz.au:    49542 Dec 30  1987 pub/ka9q/tnc_tnc2.arc
citi.umich.edu:   604050 May 24 14:34 deborah/ka9q.arc*
ditmela.cng.dit.csiro.au:    39420 Sep 12 04:57 pub/ka9q/bm_src.arc
ditmela.cng.dit.csiro.au:    44821 Sep 12 04:52 pub/ka9q/nos-man.arc
ditmela.cng.dit.csiro.au:   127698 Sep 12 04:53 pub/ka9q/nos-net.arc
jyu.fi:   147238 Mar  8  1989 pub/atari/ka9q_doc.arc*
jyu.fi:   246814 Mar  8  1989 pub/atari/ka9q_src.arc*
jyu.fi:   152731 Mar  8  1989 pub/atari/ka9q_st.arc*
ftp.uu.net:    76005 Jun 29  1988 networking/ka9q/88-121.arc
ftp.uu.net:   348989 Jul 26  1988 networking/ka9q/alpha.arc
ftp.uu.net:   372916 Mar 26  1989 networking/ka9q/aztecnos.arc
ftp.uu.net:    39420 May 10  1989 networking/ka9q/bm_src.arc
ftp.uu.net:    72015 Nov 22  1988 networking/ka9q/bmdist.arc
ftp.uu.net:    38547 Jul  8 14:24 networking/ka9q/bmexe.arc
ftp.uu.net:    40121 Jul  8 14:24 networking/ka9q/bmsrc.arc
ftp.uu.net:    52479 Jul  6 00:17 networking/ka9q/crh_n.arc
ftp.uu.net:   288270 Aug 29 01:08 networking/ka9q/drivers.arc
ftp.uu.net:   646442 Aug 29 01:08 networking/ka9q/driverss.arc
ftp.uu.net:   100466 Aug 10  1989 networking/ka9q/msys105d.arc
ftp.uu.net:   239551 Aug 10  1989 networking/ka9q/msys105p.arc
ftp.uu.net:        0 Aug 25 02:50 networking/ka9q/net.arc
ftp.uu.net:    42505 Jun  9  1988 networking/ka9q/net_bm.arc
ftp.uu.net:    29050 Dec  5  1988 networking/ka9q/net_des.arc
ftp.uu.net:   150013 Jun  9  1988 networking/ka9q/net_doc.arc
ftp.uu.net:   241511 May 16  1989 networking/ka9q/net_hp.arc
ftp.uu.net:   171989 May 10  1989 networking/ka9q/net_pc.arc
ftp.uu.net:   511664 May 10  1989 networking/ka9q/net_src.arc
ftp.uu.net:   124213 May 16  1989 networking/ka9q/net_st.arc
ftp.uu.net:   386542 Jun 21  1989 networking/ka9q/osrc.arc
ftp.uu.net:    68922 Jun 29  1988 networking/ka9q/part97.arc
ftp.uu.net:    41621 Jan 30  1989 networking/ka9q/pk232.arc
ftp.uu.net:    37094 Apr 14  1988 networking/ka9q/pxx111.arc
ftp.uu.net:   442322 Aug 31  1989 networking/ka9q/src.arc
ftp.uu.net:   443190 Sep  7  1989 networking/ka9q/src890906.arc
ftp.uu.net:    53998 May 14  1989 networking/ka9q/tnc_ash.arc
ftp.uu.net:    15790 Jan  6  1988 networking/ka9q/tnc_ldr.arc
ftp.uu.net:    34710 May 14  1989 networking/ka9q/tnc_tnc1.arc
ftp.uu.net:    49664 May 14  1989 networking/ka9q/tnc_tnc2.arc
ftp.uu.net:   148547 May 10  1989 networking/ka9q/userman.arc
ftp.uu.net:    51047 May 14  1989 networking/ka9q/xobbs.arc
gatekeeper.dec.com:    76005 Apr  7  1989 pub/net/ka9q/88-121.arc
gatekeeper.dec.com:   348989 Apr  7  1989 pub/net/ka9q/alpha.arc
gatekeeper.dec.com:   372916 Apr  7  1989 pub/net/ka9q/aztecnos.arc
gatekeeper.dec.com:    72015 Apr  7  1989 pub/net/ka9q/bmdist.arc
gatekeeper.dec.com:     2587 Aug 29 13:42 pub/net/ka9q/clarkson/buf160.arc
gatekeeper.dec.com:    37666 Aug 29 13:44 pub/net/ka9q/clarkson/diffs.arc
gatekeeper.dec.com:   288270 Aug 29 13:47 pub/net/ka9q/clarkson/drivers.arc
gatekeeper.dec.com:   646442 Aug 29 13:53 pub/net/ka9q/clarkson/driverss.arc
gatekeeper.dec.com:    21504 Aug 29 13:56 pub/net/ka9q/clarkson/execom14.arc
gatekeeper.dec.com:    36063 Aug 29 13:58 pub/net/ka9q/clarkson/patch.arc
gatekeeper.dec.com:   279402 Aug 29 14:00 pub/net/ka9q/clarkson/pcip_sos.arc
gatekeeper.dec.com:   579277 Aug 29 14:06 pub/net/ka9q/clarkson/pcippkt.arc
gatekeeper.dec.com:    85066 Aug 29 14:07 pub/net/ka9q/clarkson/pktd2.arc
gatekeeper.dec.com:   110153 Aug 29 14:07 pub/net/ka9q/clarkson/pktd2_0.arc
gatekeeper.dec.com:    92299 Aug 29 14:08 pub/net/ka9q/clarkson/pktd3.arc
gatekeeper.dec.com:   153142 Aug 29 14:09 pub/net/ka9q/clarkson/pktd3_0.arc
gatekeeper.dec.com:    95232 Aug 29 14:09 pub/net/ka9q/clarkson/pktd4_0.arc
gatekeeper.dec.com:    85066 Apr  7  1989 pub/net/ka9q/drivers.arc
gatekeeper.dec.com:    42505 Apr  7  1989 pub/net/ka9q/net_bm.arc
gatekeeper.dec.com:    29050 Apr  7  1989 pub/net/ka9q/net_des.arc
gatekeeper.dec.com:   150013 Apr  7  1989 pub/net/ka9q/net_doc.arc
gatekeeper.dec.com:   142297 Apr  7  1989 pub/net/ka9q/net_pc.arc
gatekeeper.dec.com:   318378 Apr  7  1989 pub/net/ka9q/net_src.arc
gatekeeper.dec.com:    68922 Apr  7  1989 pub/net/ka9q/part97.arc
gatekeeper.dec.com:    41621 Apr  7  1989 pub/net/ka9q/pk232.arc
gatekeeper.dec.com:    37094 Apr  7  1989 pub/net/ka9q/pxx111.arc
gatekeeper.dec.com:   379427 Apr  7  1989 pub/net/ka9q/src.arc
gatekeeper.dec.com:    57076 Apr  7  1989 pub/net/ka9q/tnc_ash.arc
gatekeeper.dec.com:    15790 Apr  7  1989 pub/net/ka9q/tnc_ldr.arc
gatekeeper.dec.com:    52127 Apr  7  1989 pub/net/ka9q/tnc_tnc1.arc
gatekeeper.dec.com:    49542 Apr  7  1989 pub/net/ka9q/tnc_tnc2.arc
giza.cis.ohio-state.edu:    39420 Sep 10  1989 pub/ibm-pc/ka9q/bm_src.arc
giza.cis.ohio-state.edu:   153142 Sep 10  1989 pub/ibm-pc/ka9q/drivers.arc
giza.cis.ohio-state.edu:    72015 Sep 10  1989 pub/ibm-pc/ka9q/obmdist.arc
giza.cis.ohio-state.edu:   150013 Sep 10  1989 pub/ibm-pc/ka9q/onet_doc.arc
giza.cis.ohio-state.edu:   386542 Sep 10  1989 pub/ibm-pc/ka9q/osrc.arc
giza.cis.ohio-state.edu:   444177 Sep 10  1989 pub/ibm-pc/ka9q/src.arc
giza.cis.ohio-state.edu:   148547 Sep 10  1989 pub/ibm-pc/ka9q/userman.arc
grivel.une.oz.au:    72015 May 31 07:23 pub/ka9q/bmdist.arc
grivel.une.oz.au:   288270 Aug 29 09:49 pub/ka9q/drivers7.arc
hp4nl.nluug.nl:    76005 May 29  1989 pub/network/ka9q/88-121.arc
hp4nl.nluug.nl:   348989 May 29  1989 pub/network/ka9q/alpha.arc
hp4nl.nluug.nl:   372916 May 29  1989 pub/network/ka9q/aztecnos.arc
hp4nl.nluug.nl:    39420 May 29  1989 pub/network/ka9q/bm_src.arc
hp4nl.nluug.nl:    72015 May 29  1989 pub/network/ka9q/bmdist.arc
hp4nl.nluug.nl:    85066 May 29  1989 pub/network/ka9q/drivers.arc
hp4nl.nluug.nl:    26880 Jan 29  1990 pub/network/ka9q/g1emmdif.arc
hp4nl.nluug.nl:   193024 Jan 29  1990 pub/network/ka9q/g1emmexe.arc
hp4nl.nluug.nl:   518656 Jan 29  1990 pub/network/ka9q/g1emmsrc.arc
hp4nl.nluug.nl:   100352 May 29  1989 pub/network/ka9q/msysd102.arc
hp4nl.nluug.nl:   100313 May 29  1989 pub/network/ka9q/msysd103.arc
hp4nl.nluug.nl:   239616 May 29  1989 pub/network/ka9q/msysp102.arc
hp4nl.nluug.nl:   244796 May 29  1989 pub/network/ka9q/msysp103.arc
hp4nl.nluug.nl:    42505 May 29  1989 pub/network/ka9q/net_bm.arc
hp4nl.nluug.nl:    29050 May 29  1989 pub/network/ka9q/net_des.arc
hp4nl.nluug.nl:   150013 May 29  1989 pub/network/ka9q/net_doc.arc
hp4nl.nluug.nl:   241511 May 29  1989 pub/network/ka9q/net_hp.arc
hp4nl.nluug.nl:   171989 May 29  1989 pub/network/ka9q/net_pc.arc
hp4nl.nluug.nl:   511664 May 29  1989 pub/network/ka9q/net_src.arc
hp4nl.nluug.nl:   124213 May 29  1989 pub/network/ka9q/net_st.arc
hp4nl.nluug.nl:   144723 Jan 29  1990 pub/network/ka9q/nos_0125.arc
hp4nl.nluug.nl:    68922 May 29  1989 pub/network/ka9q/part97.arc
hp4nl.nluug.nl:    41621 May 29  1989 pub/network/ka9q/pk232.arc
hp4nl.nluug.nl:    37094 May 29  1989 pub/network/ka9q/pxx111.arc
hp4nl.nluug.nl:   519974 Jan 29  1990 pub/network/ka9q/src.arc
hp4nl.nluug.nl:    53998 May 29  1989 pub/network/ka9q/tnc_ash.arc
hp4nl.nluug.nl:    15790 May 29  1989 pub/network/ka9q/tnc_ldr.arc
hp4nl.nluug.nl:    34710 May 29  1989 pub/network/ka9q/tnc_tnc1.arc
hp4nl.nluug.nl:    49664 May 29  1989 pub/network/ka9q/tnc_tnc2.arc
hp4nl.nluug.nl:   148547 May 29  1989 pub/network/ka9q/userman.arc
hp4nl.nluug.nl:    51047 May 29  1989 pub/network/ka9q/xobbs.arc
imag.imag.fr:    60522 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/Ajouts_TRW/drivers.arc
imag.imag.fr:   171235 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/finger.arc
imag.imag.fr:     7385 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/nelson.arc
imag.imag.fr:    37772 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_bm.arc
imag.imag.fr:    26249 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_des.arc
imag.imag.fr:   143194 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_doc.arc
imag.imag.fr:   115955 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_ew.arc
imag.imag.fr:   142297 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_pc.arc
imag.imag.fr:   318378 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_src.arc
imag.imag.fr:   343796 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_srcT.arc
imag.imag.fr:    56320 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/netam_src.arc
imag.imag.fr:   168586 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/nrnet_new.arc
imag.imag.fr:    46952 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/pxx107.arc
imag.imag.fr:    40448 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/server16.arc
imag.imag.fr:    57076 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/tnc_ash.arc
imag.imag.fr:    15790 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/tnc_ldr.arc
imag.imag.fr:    52127 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/tnc_tnc1.arc
imag.imag.fr:    49542 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/tnc_tnc2.arc
isy.liu.se:      837 Nov 26  1989 ka9q/X-axsock.arc
isy.liu.se:     1577 Nov 26  1989 ka9q/X-bm_src.arc
isy.liu.se:     2095 Nov 26  1989 ka9q/X-net_des.arc
isy.liu.se:      689 Nov 26  1989 ka9q/X-net_pc.arc
isy.liu.se:     8607 Nov 26  1989 ka9q/X-net_src1.arc
isy.liu.se:     4537 Nov 26  1989 ka9q/X-net_src2.arc
isy.liu.se:    11197 Nov 26  1989 ka9q/X-src.arc
isy.liu.se:      319 Nov 26  1989 ka9q/X-userman.arc
isy.liu.se:     2391 Nov 26  1989 ka9q/X-xobbs.arc
isy.liu.se:    42629 Nov  7  1989 ka9q/axsock.arc
isy.liu.se:    38642 Nov  7  1989 ka9q/bm_src.arc
isy.liu.se:    29050 Nov  7  1989 ka9q/net_des.arc
isy.liu.se:   173957 Nov  7  1989 ka9q/net_pc.arc
isy.liu.se:   342460 Nov  7  1989 ka9q/net_src1.arc
isy.liu.se:   162518 Nov  7  1989 ka9q/net_src2.arc
isy.liu.se:   383479 Nov  7  1989 ka9q/src.arc
isy.liu.se:    49542 Nov  7  1989 ka9q/tnc_tnc2.arc
isy.liu.se:   129108 Nov  7  1989 ka9q/userman.arc
isy.liu.se:    52905 Nov  7  1989 ka9q/xobbs.arc
kolvi.hut.fi:    48648 Mar 18  1990 tcpip/ka9q/allfiles.arc
kolvi.hut.fi:    11999 Jun 14 20:38 tcpip/ka9q/atari/atari.arc
kolvi.hut.fi:    39420 May  9  1989 tcpip/ka9q/bm_src.arc
kolvi.hut.fi:    85066 May  4  1989 tcpip/ka9q/drivers.arc
kolvi.hut.fi:    29050 May  4  1989 tcpip/ka9q/net_des.arc
kolvi.hut.fi:   241511 May 20  1989 tcpip/ka9q/net_hp.arc
kolvi.hut.fi:   171989 May  9  1989 tcpip/ka9q/net_pc.arc
kolvi.hut.fi:   511664 May  9  1989 tcpip/ka9q/net_src.arc
kolvi.hut.fi:   124213 May 20  1989 tcpip/ka9q/net_st.arc
kolvi.hut.fi:    11745 Apr 24  1990 tcpip/ka9q/netracer.arc
kolvi.hut.fi:   578806 Jul 11 21:03 tcpip/ka9q/nos/src.arc
kolvi.hut.fi:    37094 Apr 19  1989 tcpip/ka9q/pxx111.arc
kolvi.hut.fi:    42496 Apr 19  1989 tcpip/ka9q/server18.arc
kolvi.hut.fi:    57076 Apr 19  1989 tcpip/ka9q/tnc_ash.arc
kolvi.hut.fi:    15790 Apr 19  1989 tcpip/ka9q/tnc_ldr.arc
kolvi.hut.fi:    52127 Apr 19  1989 tcpip/ka9q/tnc_tnc1.arc
kolvi.hut.fi:    49542 May  4  1989 tcpip/ka9q/tnc_tnc2.arc
kolvi.hut.fi:   148547 May  9  1989 tcpip/ka9q/userman.arc
kolvi.hut.fi:   201635 May 27 09:39 tcpip/ka9q/view.arc
kolvi.hut.fi:    51076 May  9  1989 tcpip/ka9q/xobbs.arc
louie.udel.edu:    48964 Dec 22  1989 pub/ka9q/am.arc
louie.udel.edu:    31080 Dec 22  1989 pub/ka9q/bdalebits.arc
louie.udel.edu:   152825 Dec 22  1989 pub/ka9q/drivers.arc
louie.udel.edu:   171235 Dec 22  1989 pub/ka9q/finger.arc
louie.udel.edu:    13667 Dec 22  1989 pub/ka9q/intrlv.arc
louie.udel.edu:   108322 Dec 22  1989 pub/ka9q/net_amig.arc
louie.udel.edu:    70775 Dec 22  1989 pub/ka9q/net_bm.arc
louie.udel.edu:    26249 Dec 22  1989 pub/ka9q/net_des.arc
louie.udel.edu:   143194 Dec 22  1989 pub/ka9q/net_doc.arc
louie.udel.edu:   115955 Dec 22  1989 pub/ka9q/net_ew.arc
louie.udel.edu:   142297 Dec 22  1989 pub/ka9q/net_pc.arc
louie.udel.edu:   318378 Dec 22  1989 pub/ka9q/net_src.arc*
louie.udel.edu:   343796 Dec 22  1989 pub/ka9q/net_srcT.arc
louie.udel.edu:    56320 Dec 22  1989 pub/ka9q/netam_src.arc
louie.udel.edu:    19816 Dec 22  1989 pub/ka9q/nrbdale.arc
louie.udel.edu:   521671 Dec 22  1989 pub/ka9q/nrnet.arc
louie.udel.edu:    18143 Dec 22  1989 pub/ka9q/phil.arc
louie.udel.edu:    37094 Dec 22  1989 pub/ka9q/pxx111.arc
louie.udel.edu:     9220 Dec 22  1989 pub/ka9q/ramdisk.arc
louie.udel.edu:    40448 Dec 22  1989 pub/ka9q/server16.arc
louie.udel.edu:    57076 Dec 22  1989 pub/ka9q/tnc_ash.arc
louie.udel.edu:    15790 Dec 22  1989 pub/ka9q/tnc_ldr.arc
louie.udel.edu:    52127 Dec 22  1989 pub/ka9q/tnc_tnc1.arc
louie.udel.edu:    49542 Dec 22  1989 pub/ka9q/tnc_tnc2.arc
mcsun.eu.net:    76005 May 29  1989 network/ka9q/88-121.arc
mcsun.eu.net:   348989 May 29  1989 network/ka9q/alpha.arc
mcsun.eu.net:   372916 May 29  1989 network/ka9q/aztecnos.arc
mcsun.eu.net:    39420 May 29  1989 network/ka9q/bm_src.arc
mcsun.eu.net:    72015 May 29  1989 network/ka9q/bmdist.arc
mcsun.eu.net:    85066 May 29  1989 network/ka9q/drivers.arc
mcsun.eu.net:    26880 Jan 29  1990 network/ka9q/g1emmdif.arc
mcsun.eu.net:   193024 Jan 29  1990 network/ka9q/g1emmexe.arc
mcsun.eu.net:   518656 Jan 29  1990 network/ka9q/g1emmsrc.arc
mcsun.eu.net:   100352 May 29  1989 network/ka9q/msysd102.arc
mcsun.eu.net:   100313 May 29  1989 network/ka9q/msysd103.arc
mcsun.eu.net:   239616 May 29  1989 network/ka9q/msysp102.arc
mcsun.eu.net:   244796 May 29  1989 network/ka9q/msysp103.arc
mcsun.eu.net:    42505 May 29  1989 network/ka9q/net_bm.arc
mcsun.eu.net:    29050 May 29  1989 network/ka9q/net_des.arc
mcsun.eu.net:   150013 May 29  1989 network/ka9q/net_doc.arc
mcsun.eu.net:   241511 May 29  1989 network/ka9q/net_hp.arc
mcsun.eu.net:   171989 May 29  1989 network/ka9q/net_pc.arc
mcsun.eu.net:   511664 May 29  1989 network/ka9q/net_src.arc
mcsun.eu.net:   124213 May 29  1989 network/ka9q/net_st.arc
mcsun.eu.net:   144723 Jan 29  1990 network/ka9q/nos_0125.arc
mcsun.eu.net:    68922 May 29  1989 network/ka9q/part97.arc
mcsun.eu.net:    41621 May 29  1989 network/ka9q/pk232.arc
mcsun.eu.net:    37094 May 29  1989 network/ka9q/pxx111.arc
mcsun.eu.net:   519974 Jan 29  1990 network/ka9q/src.arc
mcsun.eu.net:    53998 May 29  1989 network/ka9q/tnc_ash.arc
mcsun.eu.net:    15790 May 29  1989 network/ka9q/tnc_ldr.arc
mcsun.eu.net:    34710 May 29  1989 network/ka9q/tnc_tnc1.arc
mcsun.eu.net:    49664 May 29  1989 network/ka9q/tnc_tnc2.arc
mcsun.eu.net:   148547 May 29  1989 network/ka9q/userman.arc
mcsun.eu.net:    51047 May 29  1989 network/ka9q/xobbs.arc
orion.oac.uci.edu:   171989 Aug  8  1989 ntslib/ibm-pc/ka9q/arcfiles/net_pc.arc
pacific.mps.ohio-state.edu:    96811 Feb  6  1990 msdos/ka9q/nethopexe.arc
pacific.mps.ohio-state.edu:    40184 Feb  6  1990 msdos/ka9q/nethopsrc.arc
pacific.mps.ohio-state.edu:   145554 Feb 18  1990 msdos/ka9q/nos_0214.arc
pacific.mps.ohio-state.edu:   152328 Feb  6  1990 msdos/ka9q/ppp/netppp.arc
pacific.mps.ohio-state.edu:   100115 Feb  6  1990 msdos/ka9q/ppp/pppsrc.arc
pacific.mps.ohio-state.edu:   519761 Feb  6  1990 msdos/ka9q/ppp/src.arc
pacific.mps.ohio-state.edu:   576492 Jun 16 17:52 msdos/ka9q/src.arc
plains.nodak.edu:   147238 Jun 20 00:18 pub/atari/other.bins/ka9q/ka9q_doc.arc
plains.nodak.edu:   246814 Jun 20 00:22 pub/atari/other.bins/ka9q/ka9q_src.arc
plains.nodak.edu:   152731 Jun 20 00:26 pub/atari/other.bins/ka9q/ka9q_st.arc
plains.nodak.edu:    68816 Jun 20 00:27 pub/atari/other.bins/ka9q/ka9qst.arc
radio.astro.utoronto.ca:   509075 Jan  9  1990 msdos/ka9q.900105.src.arc
radio.astro.utoronto.ca:   153142 Jan 29 18:08 msdos/ka9q.drivers.arc
rusmv1.rus.uni-stuttgart.de:     2587 Jan 16  1990 soft/pc/pc-public/misc/ka9q-tcpip/buf160.arc
rusmv1.rus.uni-stuttgart.de:   123008 Feb 12  1990 soft/pc/pc-public/misc/ka9q-tcpip/drivers.arc
rusmv1.rus.uni-stuttgart.de:   304101 Jan 16  1990 soft/pc/pc-public/misc/ka9q-tcpip/driverss.arc
rusmv1.rus.uni-stuttgart.de:   509075 Jan 16  1990 soft/pc/pc-public/misc/ka9q-tcpip/net.arc
rusmv1.rus.uni-stuttgart.de:   212480 Feb 12  1990 soft/pc/pc-public/misc/ka9q-tcpip/nrnet.arc
rusmv1.rus.uni-stuttgart.de:    37120 Feb 12  1990 soft/pc/pc-public/misc/ka9q-tcpip/pxx111.arc
rusmv1.rus.uni-stuttgart.de:    49664 Feb 12  1990 soft/pc/pc-public/misc/ka9q-tcpip/tnc_tnc2.arc
sics.se:    39420 May  9  1989 archive/packet/ka9q/bm_src.arc
sics.se:   288270 Sep  3 10:09 archive/packet/ka9q/drivers.arc
sics.se:   156157 Dec 21  1988 archive/packet/ka9q/net33_st.arc
sics.se:    29050 May  1  1989 archive/packet/ka9q/net_des.arc
sics.se:   171989 May  9  1989 archive/packet/ka9q/net_pc.arc
sics.se:   511664 May  9  1989 archive/packet/ka9q/net_src.arc
sics.se:    36992 Nov 11  1989 archive/packet/ka9q/nos/domain.arc
sics.se:    25634 Sep 27 21:01 archive/packet/ka9q/nos/forth.arc
sics.se:    38087 Oct 28 14:27 archive/packet/ka9q/nos/lzw.arc
sics.se:    63853 Nov  2 22:40 archive/packet/ka9q/nos/mailbox.arc
sics.se:    20575 May  1  1990 archive/packet/ka9q/nos/nntp.arc
sics.se:    24539 Oct 15 11:16 archive/packet/ka9q/nos/rarp.arc
sics.se:    68259 Nov  4 09:09 archive/packet/ka9q/nos/rspf.arc
sics.se:   112835 Jan 28  1990 archive/packet/ka9q/nos/view.arc
sics.se:    49542 May  1  1989 archive/packet/ka9q/tnc_tnc2.arc
sics.se:   148547 May  9  1989 archive/packet/ka9q/userman.arc
sics.se:    51076 May  9  1989 archive/packet/ka9q/xobbs.arc
sirius.ucs.adelaide.edu.au:     2587 Dec 16  1989 pub/ka9q/buf160.arc
sirius.ucs.adelaide.edu.au:    37666 Apr 20  1990 pub/ka9q/diffs.arc
sirius.ucs.adelaide.edu.au:   209601 Apr 20  1990 pub/ka9q/drivers.arc
sirius.ucs.adelaide.edu.au:   475539 Apr 20  1990 pub/ka9q/driverss.arc
sirius.ucs.adelaide.edu.au:    21504 Apr 20  1990 pub/ka9q/execom14.arc
sirius.ucs.adelaide.edu.au:    36063 Apr 20  1990 pub/ka9q/patch.arc
sirius.ucs.adelaide.edu.au:   565837 Apr 20  1990 pub/ka9q/src900331.arc
sirius.ucs.adelaide.edu.au:   485153 Dec 16  1989 pub/ka9q/tns.arc
sirius.ucs.adelaide.edu.au:     8251 Apr 20  1990 pub/ka9q/tools.arc
sun.soe.clarkson.edu:    78291 Nov  2 09:44 pub/ka9q/3c523x.arc
sun.soe.clarkson.edu:     2587 Sep 19  1989 pub/ka9q/buf160.arc
sun.soe.clarkson.edu:    37666 Dec 22  1989 pub/ka9q/diffs.arc
sun.soe.clarkson.edu:   288270 Aug 29 01:08 pub/ka9q/drivers.arc
sun.soe.clarkson.edu:   646442 Aug 29 01:09 pub/ka9q/driverss.arc
sun.soe.clarkson.edu:    21504 Feb 12  1990 pub/ka9q/execom14.arc
sun.soe.clarkson.edu:    36063 Dec 22  1989 pub/ka9q/patch.arc
sun.soe.clarkson.edu:   279402 May 31 12:18 pub/ka9q/pcip_sos.arc
sun.soe.clarkson.edu:   579277 Apr 21  1990 pub/ka9q/pcippkt.arc
sun.soe.clarkson.edu:    85066 Jun 29 13:17 pub/ka9q/pktd2.arc
sun.soe.clarkson.edu:   110153 Jun 29 13:17 pub/ka9q/pktd2_0.arc
sun.soe.clarkson.edu:    92299 Jun 29 13:17 pub/ka9q/pktd3.arc
sun.soe.clarkson.edu:   153142 Jun 29 13:17 pub/ka9q/pktd3_0.arc
sun.soe.clarkson.edu:   209872 Jun 29 13:17 pub/ka9q/pktd4_0.arc
sun.soe.clarkson.edu:   102142 Jun 29 13:17 pub/ka9q/pktd5_0.arc
sun.soe.clarkson.edu:   304101 Jun 29 13:17 pub/ka9q/pktd5_0s.arc
sun.soe.clarkson.edu:   209601 Jun 29 13:17 pub/ka9q/pktd6_0.arc
sun.soe.clarkson.edu:   475539 Jun 29 13:17 pub/ka9q/pktd6_0s.arc
sun.soe.clarkson.edu:   288270 Aug 29 01:08 pub/ka9q/pktd7_0.arc
sun.soe.clarkson.edu:   646442 Aug 29 01:09 pub/ka9q/pktd7_0s.arc
sun.soe.clarkson.edu:    70021 Jun 25 13:27 pub/ka9q/printnet.arc
sunic.sunet.se:    39420 May  9  1989 .sics.se/archive/packet/ka9q/bm_src.arc
sunic.sunet.se:   288270 Sep  3 08:09 .sics.se/archive/packet/ka9q/drivers.arc
sunic.sunet.se:   156157 Dec 21  1988 .sics.se/archive/packet/ka9q/net33_st.arc
sunic.sunet.se:    29050 May  1  1989 .sics.se/archive/packet/ka9q/net_des.arc
sunic.sunet.se:   171989 May  9  1989 .sics.se/archive/packet/ka9q/net_pc.arc
sunic.sunet.se:   511664 May  9  1989 .sics.se/archive/packet/ka9q/net_src.arc
sunic.sunet.se:    36992 Nov 11  1989 .sics.se/archive/packet/ka9q/nos/domain.arc
sunic.sunet.se:    23264 Aug 24 20:58 .sics.se/archive/packet/ka9q/nos/forth.arc
sunic.sunet.se:    20575 May  1 20:29 .sics.se/archive/packet/ka9q/nos/nntp.arc
sunic.sunet.se:    47015 Aug 18 17:26 .sics.se/archive/packet/ka9q/nos/rspf.arc
sunic.sunet.se:   594963 Apr 13 18:58 .sics.se/archive/packet/ka9q/nos/src.arc
sunic.sunet.se:   112835 Jan 28  1990 .sics.se/archive/packet/ka9q/nos/view.arc
sunic.sunet.se:    49542 May  1  1989 .sics.se/archive/packet/ka9q/tnc_tnc2.arc
sunic.sunet.se:   148547 May  9  1989 .sics.se/archive/packet/ka9q/userman.arc
sunic.sunet.se:    51076 May  9  1989 .sics.se/archive/packet/ka9q/xobbs.arc
surya.waterloo.edu:    38547 Aug  8 05:56 networking/ka9q/bm/bmexe.arc
surya.waterloo.edu:    40121 Aug  8 05:57 networking/ka9q/bm/bmsrc.arc
surya.waterloo.edu:    52479 Aug  8 05:55 networking/ka9q/nansi/crh_n.arc
terminator.cc.umich.edu:   147238 Apr 12  1989 atari/telecomm/ka9q_doc.arc
terminator.cc.umich.edu:   246814 Apr 12  1989 atari/telecomm/ka9q_src.arc
terminator.cc.umich.edu:   152731 Apr 12  1989 atari/telecomm/ka9q_st.arc
terminator.cc.umich.edu:    68816 Apr 12  1989 atari/telecomm/ka9qst.arc
terminator.cc.umich.edu:   209601 Jun 28 03:39 msdos/communications/ka9q/drivers.arc*
terminator.cc.umich.edu:   475539 Jun 28 03:39 msdos/communications/ka9q/driverss.arc*
terminator.cc.umich.edu:   271683 Jun 28 03:39 msdos/communications/ka9q/net.arc*
terminator.cc.umich.edu:   449408 Jun 28 03:39 msdos/communications/ka9q/netsrc88.arc*
thumper.bellcore.com:    38547 Jul  8 14:24 pub/ka9q/bm/bmexe.arc
thumper.bellcore.com:    40121 Jul  8 14:20 pub/ka9q/bm/bmsrc.arc
thumper.bellcore.com:    52479 Jul  6 00:17 pub/ka9q/nansi/crh_n.arc
thumper.bellcore.com:    55121 Nov  1 01:47 pub/ka9q/nansi/nan24hyc.arc
ucdavis.ucdavis.edu:   176570 Aug 13 08:24 dist/ucdmail/ka9q/netpop2.arc
ucdavis.ucdavis.edu:    51513 Apr  5  1990 dist/ucdmail/ka9q/pop2src.arc
ucdavis.ucdavis.edu:   457082 Apr  5  1990 dist/ucdmail/ka9q/src.arc
unido.informatik.uni-dortmund.de:   136192 Jul  5 12:59 other/ka9q/flash/src.arc
unido.informatik.uni-dortmund.de:    74752 Sep  9  1988 pub/comp/msdos/ka9q/drivers.arc
unido.informatik.uni-dortmund.de:    31360 Jun 23  1988 pub/comp/msdos/ka9q/finger.arc
unido.informatik.uni-dortmund.de:    21263 Jul 22  1988 pub/comp/msdos/ka9q/ka9q-epr.arc
unido.informatik.uni-dortmund.de:    33664 Jun 23  1988 pub/comp/msdos/ka9q/kit.arc
unido.informatik.uni-dortmund.de:     7413 Jun 22  1988 pub/comp/msdos/ka9q/nelson.arc
unido.informatik.uni-dortmund.de:    54598 Jun 22  1988 pub/comp/msdos/ka9q/net_amig.arcab.Z
unido.informatik.uni-dortmund.de:    43264 Jul 27  1988 pub/comp/msdos/ka9q/net_bm.arc
unido.informatik.uni-dortmund.de:    26249 Jun 22  1988 pub/comp/msdos/ka9q/net_des.arc
unido.informatik.uni-dortmund.de:   143157 Jun 22  1988 pub/comp/msdos/ka9q/net_doc.arc
unido.informatik.uni-dortmund.de:   116992 Jun 22  1988 pub/comp/msdos/ka9q/net_mac.arc
unido.informatik.uni-dortmund.de:   144384 Jul 27  1988 pub/comp/msdos/ka9q/net_pc.arc
unido.informatik.uni-dortmund.de:   315648 Jun 28  1988 pub/comp/msdos/ka9q/net_src.arc
unido.informatik.uni-dortmund.de:   124213 May 18 17:07 pub/comp/msdos/ka9q/net_st.arc
unido.informatik.uni-dortmund.de:   374272 Jan 20  1989 pub/comp/msdos/ka9q/nos.arc
unido.informatik.uni-dortmund.de:   177024 Jun 28  1988 pub/comp/msdos/ka9q/nrnet.arc
unido.informatik.uni-dortmund.de:    47379 Jun 22  1988 pub/comp/msdos/ka9q/pxx107.arc
unido.informatik.uni-dortmund.de:    40448 Sep  1  1988 pub/comp/msdos/ka9q/server16.arc
unido.informatik.uni-dortmund.de:   574436 May 18 16:57 pub/comp/msdos/ka9q/src.arc
unido.informatik.uni-dortmund.de:    57076 Jun 22  1988 pub/comp/msdos/ka9q/tnc_ash.arc
unido.informatik.uni-dortmund.de:    15790 Jun 22  1988 pub/comp/msdos/ka9q/tnc_ldr.arc
unido.informatik.uni-dortmund.de:    52127 Jun 22  1988 pub/comp/msdos/ka9q/tnc_tnc1.arc
unido.informatik.uni-dortmund.de:    49542 Jun 22  1988 pub/comp/msdos/ka9q/tnc_tnc2.arc
unido.informatik.uni-dortmund.de:   148547 May 18 16:46 pub/comp/msdos/ka9q/userman.arc
uunet.uu.net:    76005 Jun 29  1988 networking/ka9q/88-121.arc
uunet.uu.net:   348989 Jul 26  1988 networking/ka9q/alpha.arc
uunet.uu.net:   372916 Mar 26  1989 networking/ka9q/aztecnos.arc
uunet.uu.net:    39420 May 10  1989 networking/ka9q/bm_src.arc
uunet.uu.net:    72015 Nov 22  1988 networking/ka9q/bmdist.arc
uunet.uu.net:    38547 Jul  8 14:24 networking/ka9q/bmexe.arc
uunet.uu.net:    40121 Jul  8 14:24 networking/ka9q/bmsrc.arc
uunet.uu.net:    52479 Jul  6 00:17 networking/ka9q/crh_n.arc
uunet.uu.net:   288270 Aug 29 01:08 networking/ka9q/drivers.arc
uunet.uu.net:   646442 Aug 29 01:08 networking/ka9q/driverss.arc
uunet.uu.net:   100466 Aug 10  1989 networking/ka9q/msys105d.arc
uunet.uu.net:   239551 Aug 10  1989 networking/ka9q/msys105p.arc
uunet.uu.net:        0 Aug 25 02:50 networking/ka9q/net.arc
uunet.uu.net:    42505 Jun  9  1988 networking/ka9q/net_bm.arc
uunet.uu.net:    29050 Dec  5  1988 networking/ka9q/net_des.arc
uunet.uu.net:   150013 Jun  9  1988 networking/ka9q/net_doc.arc
uunet.uu.net:   241511 May 16  1989 networking/ka9q/net_hp.arc
uunet.uu.net:   171989 May 10  1989 networking/ka9q/net_pc.arc
uunet.uu.net:   511664 May 10  1989 networking/ka9q/net_src.arc
uunet.uu.net:   124213 May 16  1989 networking/ka9q/net_st.arc
uunet.uu.net:   386542 Jun 21  1989 networking/ka9q/osrc.arc
uunet.uu.net:    68922 Jun 29  1988 networking/ka9q/part97.arc
uunet.uu.net:    41621 Jan 30  1989 networking/ka9q/pk232.arc
uunet.uu.net:    37094 Apr 14  1988 networking/ka9q/pxx111.arc
uunet.uu.net:   442322 Aug 31  1989 networking/ka9q/src.arc
uunet.uu.net:   443190 Sep  7  1989 networking/ka9q/src890906.arc
uunet.uu.net:    53998 May 14  1989 networking/ka9q/tnc_ash.arc
uunet.uu.net:    15790 Jan  6  1988 networking/ka9q/tnc_ldr.arc
uunet.uu.net:    34710 May 14  1989 networking/ka9q/tnc_tnc1.arc
uunet.uu.net:    49664 May 14  1989 networking/ka9q/tnc_tnc2.arc
uunet.uu.net:   148547 May 10  1989 networking/ka9q/userman.arc
uunet.uu.net:    51047 May 14  1989 networking/ka9q/xobbs.arc
vax.cs.pitt.edu:   150013 Jan  9  1990 pub/ka9q/net_doc.arc
vax.cs.pitt.edu:   171989 Jun 30  1989 pub/ka9q/net_pc.arc
vax.cs.pitt.edu:    39937 Feb 17  1990 pub/ka9q/scc.arc
vax.cs.pitt.edu:   148547 Jan 23  1990 pub/ka9q/userman.arc
wuarchive.wustl.edu:    39420 May 10  1989 mirrors/misc/ka9q-tcpip/bm_src.arc
wuarchive.wustl.edu:   646442 Aug 30 19:00 mirrors/misc/ka9q-tcpip/driverss.arc
wuarchive.wustl.edu:    21535 Aug  2  1988 mirrors/misc/ka9q-tcpip/eprint.arc
wuarchive.wustl.edu:    33565 Feb 15  1988 mirrors/misc/ka9q-tcpip/kit.arc
wuarchive.wustl.edu:   232860 Oct 31 18:00 mirrors/misc/ka9q-tcpip/net-1029.arc
wuarchive.wustl.edu:   108322 Mar 21  1988 mirrors/misc/ka9q-tcpip/net_amig.arc
wuarchive.wustl.edu:    43208 Jun 17  1988 mirrors/misc/ka9q-tcpip/net_bm.arc
wuarchive.wustl.edu:   240480 May 15  1989 mirrors/misc/ka9q-tcpip/net_hp.arc
wuarchive.wustl.edu:   171989 May 10  1989 mirrors/misc/ka9q-tcpip/net_pc.arc
wuarchive.wustl.edu:   511664 May 10  1989 mirrors/misc/ka9q-tcpip/net_src.arc
wuarchive.wustl.edu:   124213 May 15  1989 mirrors/misc/ka9q-tcpip/net_st.arc
wuarchive.wustl.edu:    47524 Aug 26 19:00 mirrors/misc/ka9q-tcpip/nos-man.arc
wuarchive.wustl.edu:   128952 Aug 28 19:00 mirrors/misc/ka9q-tcpip/nos-net.arc
wuarchive.wustl.edu:    37094 Apr 30  1988 mirrors/misc/ka9q-tcpip/pxx111.arc
wuarchive.wustl.edu:    40448 Aug  4  1988 mirrors/misc/ka9q-tcpip/server16.arc
wuarchive.wustl.edu:    57076 Jan  1  1988 mirrors/misc/ka9q-tcpip/tnc_ash.arc
wuarchive.wustl.edu:    15790 Jan  1  1988 mirrors/misc/ka9q-tcpip/tnc_ldr.arc
wuarchive.wustl.edu:    34710 May 15  1989 mirrors/misc/ka9q-tcpip/tnc_tnc1.arc
wuarchive.wustl.edu:    49542 Jan  1  1988 mirrors/misc/ka9q-tcpip/tnc_tnc2.arc
wuarchive.wustl.edu:   148547 May 10  1989 mirrors/misc/ka9q-tcpip/userman.arc
wuarchive.wustl.edu:   320333 Oct 29 18:00 mirrors/misc/ka9q-tcpip/view1029.arc
wuarchive.wustl.edu:    51076 May 10  1989 mirrors/misc/ka9q-tcpip/xobbs.arc
xlnvax.excelan.com:    76005 Aug 23  1989 pub/networking/ka9q/88-121.arc
xlnvax.excelan.com:   348989 Aug 23  1989 pub/networking/ka9q/alpha.arc
xlnvax.excelan.com:   153142 Aug 23  1989 pub/networking/ka9q/drivers.arc
xlnvax.excelan.com:   241511 Aug 23  1989 pub/networking/ka9q/net_hp.arc
xlnvax.excelan.com:   386542 Aug 23  1989 pub/networking/ka9q/osrc.arc

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:17:38 GMT
From: usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: ATARI: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files which matched "atari" in their path names:

jyu.fi:   147238 Mar  8  1989 pub/atari/ka9q_doc.arc*
jyu.fi:   246814 Mar  8  1989 pub/atari/ka9q_src.arc*
jyu.fi:   152731 Mar  8  1989 pub/atari/ka9q_st.arc*
kolvi.hut.fi:      354 Jun 14 20:38 tcpip/ka9q/atari/README
kolvi.hut.fi:    11999 Jun 14 20:38 tcpip/ka9q/atari/atari.arc
kolvi.hut.fi:   740266 Jun 15 21:12 tcpip/ka9q/atari/atari.zoo
plains.nodak.edu:   125599 Aug  6 16:31 pub/atari/other.bins/ka9q/ka9q.pr.Z
plains.nodak.edu:   147238 Jun 20 00:18 pub/atari/other.bins/ka9q/ka9q_doc.arc
plains.nodak.edu:   246814 Jun 20 00:22 pub/atari/other.bins/ka9q/ka9q_src.arc
plains.nodak.edu:   152731 Jun 20 00:26 pub/atari/other.bins/ka9q/ka9q_st.arc
plains.nodak.edu:    68816 Jun 20 00:27 pub/atari/other.bins/ka9q/ka9qst.arc
plains.nodak.edu:     9781 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/ARP.C
plains.nodak.edu:     2894 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ARP.H
plains.nodak.edu:     4040 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ARPCMD.C
plains.nodak.edu:      752 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ARPDUMP.C
plains.nodak.edu:     2441 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AUDIT.C
plains.nodak.edu:     8988 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AX25.C
plains.nodak.edu:     1792 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AX25.H
plains.nodak.edu:    12052 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AX25CMD.C
plains.nodak.edu:     6132 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AX25DUMP.C
plains.nodak.edu:    13003 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/AX25SUBR.C
plains.nodak.edu:     2767 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/AX25USER.C
plains.nodak.edu:     6959 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AXMBX.C
plains.nodak.edu:      634 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/AXMBX.H
plains.nodak.edu:     2932 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/CMDPARSE.C
plains.nodak.edu:      401 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/CMDPARSE.H
plains.nodak.edu:      942 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/CONFIG.H
plains.nodak.edu:    14033 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/DIRUTIL.C
plains.nodak.edu:     3493 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/FILES.C
plains.nodak.edu:     3135 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/FTP.C
plains.nodak.edu:     1396 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/FTP.H
plains.nodak.edu:    14302 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/FTPCLI.C
plains.nodak.edu:    16571 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/FTPSERV.C
plains.nodak.edu:     2178 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/GLOBAL.H
plains.nodak.edu:     4778 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ICMP.C
plains.nodak.edu:     2030 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ICMP.H
plains.nodak.edu:     4810 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ICMPCMD.C
plains.nodak.edu:     1492 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ICMPDUMP.C
plains.nodak.edu:      671 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/ICMPMSG.C
plains.nodak.edu:     1325 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/IFACE.C
plains.nodak.edu:     1248 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/IFACE.H
plains.nodak.edu:     1251 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/INTERNET.H
plains.nodak.edu:    10118 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/IP.C
plains.nodak.edu:     3339 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/IP.H
plains.nodak.edu:     4887 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/IPCMD.C
plains.nodak.edu:     1606 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/IPDUMP.C
plains.nodak.edu:    14703 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/IPROUTE.C
plains.nodak.edu:     1311 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/KISS.C
plains.nodak.edu:       44 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/KISS.H
plains.nodak.edu:    11107 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/LAPB.C
plains.nodak.edu:     2653 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/LAPB.H
plains.nodak.edu:     2031 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/LAPBTIME.C
plains.nodak.edu:      716 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/LCSUM.C
plains.nodak.edu:    19514 Dec  2  1988 pub/atari/other.bins/ka9q/tmp/MAIN.C
plains.nodak.edu:     5295 Dec  2  1988 pub/atari/other.bins/ka9q/tmp/MAKEFILE
plains.nodak.edu:     7486 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/MBUF.C
plains.nodak.edu:      590 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/MBUF.H
plains.nodak.edu:      666 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/MISC.C
plains.nodak.edu:     5202 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/NETROM.H
plains.nodak.edu:     2704 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NETUSER.C
plains.nodak.edu:     1092 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NETUSER.H
plains.nodak.edu:    21828 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NR3.C
plains.nodak.edu:    12792 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NRCMD.C
plains.nodak.edu:     6112 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NRS.C
plains.nodak.edu:     1299 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/NRS.H
plains.nodak.edu:     2929 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/PATHNAME.C
plains.nodak.edu:      443 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/PING.H
plains.nodak.edu:      157 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/REMOTE.H
plains.nodak.edu:     7323 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/SESSION.C
plains.nodak.edu:      844 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/SESSION.H
plains.nodak.edu:    12295 Dec  2  1988 pub/atari/other.bins/ka9q/tmp/SLFP.C
plains.nodak.edu:     1803 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/SLFP.H
plains.nodak.edu:    10270 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/SLIP.C
plains.nodak.edu:      976 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/SLIP.H
plains.nodak.edu:     3601 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/SMISC.C
plains.nodak.edu:     2246 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/SMTP.H
plains.nodak.edu:    16522 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/SMTPCLI.C
plains.nodak.edu:    12769 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/SMTPSERV.C
plains.nodak.edu:    17892 Dec  2  1988 pub/atari/other.bins/ka9q/tmp/ST.C
plains.nodak.edu:     1001 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/ST.H
plains.nodak.edu:     5318 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCP.H
plains.nodak.edu:     6135 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCPCMD.C
plains.nodak.edu:     1283 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCPDUMP.C
plains.nodak.edu:    20896 Oct 22 08:53 pub/atari/other.bins/ka9q/tmp/TCPIN.C
plains.nodak.edu:     5143 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCPOUT.C
plains.nodak.edu:     6412 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCPSUBR.C
plains.nodak.edu:     1343 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TCPTIMER.C
plains.nodak.edu:     6793 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/TCPUSER.C
plains.nodak.edu:     9082 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TELNET.C
plains.nodak.edu:     1039 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TELNET.H
plains.nodak.edu:     1763 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TIMER.C
plains.nodak.edu:     1162 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TIMER.H
plains.nodak.edu:     2600 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/TNSERV.C
plains.nodak.edu:     4314 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/TRACE.C
plains.nodak.edu:      393 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/TRACE.H
plains.nodak.edu:     2102 Nov 30  1988 pub/atari/other.bins/ka9q/tmp/TTYDRIV.C
plains.nodak.edu:     7681 Nov 29  1988 pub/atari/other.bins/ka9q/tmp/UDP.C
plains.nodak.edu:     1227 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/UDP.H
plains.nodak.edu:      920 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/UDPCMD.C
plains.nodak.edu:      788 Jul 28  1988 pub/atari/other.bins/ka9q/tmp/UDPDUMP.C
plains.nodak.edu:      477 Dec  2  1988 pub/atari/other.bins/ka9q/tmp/VERSION.C
terminator.cc.umich.edu:   147238 Apr 12  1989 atari/telecomm/ka9q_doc.arc
terminator.cc.umich.edu:   246814 Apr 12  1989 atari/telecomm/ka9q_src.arc
terminator.cc.umich.edu:   152731 Apr 12  1989 atari/telecomm/ka9q_st.arc
terminator.cc.umich.edu:    68816 Apr 12  1989 atari/telecomm/ka9qst.arc

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:19:05 GMT
From: news.cs.indiana.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: MAC: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files which matched "mac" in their pathnames:

bellcore.com:       36 Jul 19 19:42 pub/ka9q/.emacs_406
brazos.rice.edu:   116992 Jan  5  1988 pub/KA9Q/net_mac.ARC
brolga.cc.uq.oz.au:   223461 Feb 28  1988 pub/ka9q/net_mac.hqx
flash.bellcore.com:       36 Jul 19 19:42 pub/ka9q/.emacs_406
ftp.uu.net:    64896 May  4  1989 networking/ka9q/MacBM.hqx
ftp.uu.net:   139520 May  4  1989 networking/ka9q/MacBMsrc.hqx
ftp.uu.net:   220288 May  4  1989 networking/ka9q/MacNet.hqx
ftp.uu.net:    58087 Jul 30 00:57 networking/ka9q/kiss.mac
funet.fi:    46976 Nov 12  1989 networking/mac/ka9q/BM-Mac.SIT
funet.fi:   159232 Nov 12  1989 networking/mac/ka9q/NET-Mac.SIT
grivel.une.oz.au:    81536 Aug 20 04:27 pub/ka9q/BM-Mac2.sit.hqx
grivel.une.oz.au:   249856 Aug 20 04:33 pub/ka9q/Net-Mac2.sit.hqx
grivel.une.oz.au:    64896 Aug  8 01:46 pub/ka9q/macbm.hqx
grivel.une.oz.au:   220288 Aug  8 01:46 pub/ka9q/macnet.hqx
kth.se:   746624 May 10  1989 macintosh/info-mac/KA9Q/MNetsrc.hqx
kth.se:    64896 May 10  1989 macintosh/info-mac/KA9Q/MacBM.hqx
kth.se:   139520 May 10  1989 macintosh/info-mac/KA9Q/MacBMsrc.hqx
kth.se:   220288 May 10  1989 macintosh/info-mac/KA9Q/MacNet.hqx
kth.se:      193 May 10  1989 macintosh/info-mac/KA9Q/README
hp4nl.nluug.nl:    64896 May 29  1989 pub/network/ka9q/MacBM.hqx
hp4nl.nluug.nl:   139520 May 29  1989 pub/network/ka9q/MacBMsrc.hqx
hp4nl.nluug.nl:   220288 May 29  1989 pub/network/ka9q/MacNet.hqx
imag.imag.fr:   182861 Mar 15  1990 archive/tcp-ip/ip-sur-pc/ka9q/net_mac.hqx.Z
kolvi.hut.fi:   746624 Jan 28  1990 tcpip/ka9q/mac/MNetsrc.hqx
kolvi.hut.fi:    64896 Jan 28  1990 tcpip/ka9q/mac/MacBM.hqx
kolvi.hut.fi:   139520 Jan 28  1990 tcpip/ka9q/mac/MacBMsrc.hqx
kolvi.hut.fi:   220288 Jan 28  1990 tcpip/ka9q/mac/MacNet.hqx
kolvi.hut.fi:     2467 May 24  1989 tcpip/ka9q/mac/how-to.mac
louie.udel.edu:   223461 Dec 22  1989 pub/ka9q/net_mac.hqx
mcsun.eu.net:    64896 May 29  1989 network/ka9q/MacBM.hqx
mcsun.eu.net:   139520 May 29  1989 network/ka9q/MacBMsrc.hqx
mcsun.eu.net:   220288 May 29  1989 network/ka9q/MacNet.hqx
sics.se:   159232 Jan 28  1990 archive/packet/ka9q/macnet.sit
sunic.sunet.se:   159232 Jan 28  1990 .sics.se/archive/packet/ka9q/macnet.sit
thumper.bellcore.com:    58087 Jul 30 00:57 pub/ka9q/kiss/kiss.mac
thumper.bellcore.com:    25814 Sep 27 06:54 pub/ka9q/kiss/kissV.4.mac.Z
unido.informatik.uni-dortmund.de:       83 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/lmacros.h.Z
unido.informatik.uni-dortmund.de:   116992 Jun 22  1988 pub/comp/msdos/ka9q/net_mac.arc
utsun.s.u-tokyo.ac.jp:    67079 Jul 16 15:21 Mac/KA9Q/bm_mac2.hqx.part1
utsun.s.u-tokyo.ac.jp:    13983 Jul 16 15:21 Mac/KA9Q/bm_mac2.hqx.part2
utsun.s.u-tokyo.ac.jp:    67100 Jul 16 15:24 Mac/KA9Q/bmsrc.hqx.part1
utsun.s.u-tokyo.ac.jp:    42989 Jul 16 15:25 Mac/KA9Q/bmsrc.hqx.part2
utsun.s.u-tokyo.ac.jp:    67739 Jul 16 15:20 Mac/KA9Q/net_mac2.hqx.part1
utsun.s.u-tokyo.ac.jp:    66902 Jul 16 15:20 Mac/KA9Q/net_mac2.hqx.part2
utsun.s.u-tokyo.ac.jp:    66902 Jul 16 15:21 Mac/KA9Q/net_mac2.hqx.part3
utsun.s.u-tokyo.ac.jp:    45228 Jul 16 15:21 Mac/KA9Q/net_mac2.hqx.part4
utsun.s.u-tokyo.ac.jp:    67325 Jul 16 15:22 Mac/KA9Q/netsrc.hqx.part01
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:22 Mac/KA9Q/netsrc.hqx.part02
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:23 Mac/KA9Q/netsrc.hqx.part03
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:23 Mac/KA9Q/netsrc.hqx.part04
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:23 Mac/KA9Q/netsrc.hqx.part05
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:23 Mac/KA9Q/netsrc.hqx.part06
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:24 Mac/KA9Q/netsrc.hqx.part07
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:24 Mac/KA9Q/netsrc.hqx.part08
utsun.s.u-tokyo.ac.jp:    66916 Jul 16 15:24 Mac/KA9Q/netsrc.hqx.part09
utsun.s.u-tokyo.ac.jp:     1531 Jul 16 15:24 Mac/KA9Q/netsrc.hqx.part10
uunet.uu.net:    64896 May  4  1989 networking/ka9q/MacBM.hqx
uunet.uu.net:   139520 May  4  1989 networking/ka9q/MacBMsrc.hqx
uunet.uu.net:   220288 May  4  1989 networking/ka9q/MacNet.hqx
uunet.uu.net:    58087 Jul 30 00:57 networking/ka9q/kiss.mac
wuarchive.wustl.edu:    81536 Jul  1 19:00 mirrors/misc/ka9q-tcpip/bm-mac2-sit.hqx
wuarchive.wustl.edu:   112384 Jul  1 19:00 mirrors/misc/ka9q-tcpip/bm-mac2-src-sit.hqx
wuarchive.wustl.edu:   249856 Jul  1 19:00 mirrors/misc/ka9q-tcpip/net-mac2-sit.hqx
wuarchive.wustl.edu:   618880 Jul  1 19:00 mirrors/misc/ka9q-tcpip/net-mac2-src-sit.hqx
xlnvax.excelan.com:    64896 Aug 23  1989 pub/networking/ka9q/MacBM.hqx
xlnvax.excelan.com:   139520 Aug 23  1989 pub/networking/ka9q/MacBMsrc.hqx
xlnvax.excelan.com:   220288 Aug 23  1989 pub/networking/ka9q/MacNet.hqx

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:20:43 GMT
From: news.cs.indiana.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: MSDOS: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files which matched "msdos" in their pathnames:
(no files matched "ms-dos")

aqua.whoi.edu:       19 Apr  4  1989 pub/ka9q@ -> /sources/msdos/ka9q
pacific.mps.ohio-state.edu:   280892 Jun 16 17:52 msdos/ka9q/net.exe
pacific.mps.ohio-state.edu:    96811 Feb  6  1990 msdos/ka9q/nethopexe.arc
pacific.mps.ohio-state.edu:    40184 Feb  6  1990 msdos/ka9q/nethopsrc.arc
pacific.mps.ohio-state.edu:   145554 Feb 18  1990 msdos/ka9q/nos_0214.arc
pacific.mps.ohio-state.edu:   152328 Feb  6  1990 msdos/ka9q/ppp/netppp.arc
pacific.mps.ohio-state.edu:   100115 Feb  6  1990 msdos/ka9q/ppp/pppsrc.arc
pacific.mps.ohio-state.edu:   519761 Feb  6  1990 msdos/ka9q/ppp/src.arc
pacific.mps.ohio-state.edu:   576492 Jun 16 17:52 msdos/ka9q/src.arc
radio.astro.utoronto.ca:   509075 Jan  9  1990 msdos/ka9q.900105.src.arc
radio.astro.utoronto.ca:   153142 Jan 29 18:08 msdos/ka9q.drivers.arc
rusmv1.rus.uni-stuttgart.de:      256 Feb 12  1990 soft/pc/pc-public/msdos/ka9q-tcpip/aaaread.me
terminator.cc.umich.edu:   209601 Jun 28 03:39 msdos/communications/ka9q/drivers.arc*
terminator.cc.umich.edu:   475539 Jun 28 03:39 msdos/communications/ka9q/driverss.arc*
terminator.cc.umich.edu:   193200 Aug  6 23:51 msdos/communications/ka9q/ka9q.zip*
terminator.cc.umich.edu:   271683 Jun 28 03:39 msdos/communications/ka9q/net.arc*
terminator.cc.umich.edu:   449408 Jun 28 03:39 msdos/communications/ka9q/netsrc88.arc*
unido.informatik.uni-dortmund.de:    36603 Dec 28  1987 pub/comp/msdos/ka9q/TUTORIAL.DOC.Z
unido.informatik.uni-dortmund.de:    83775 Dec 28  1987 pub/comp/msdos/ka9q/USERMAN.DOC.Z
unido.informatik.uni-dortmund.de:    74752 Sep  9  1988 pub/comp/msdos/ka9q/drivers.arc
unido.informatik.uni-dortmund.de:    31360 Jun 23  1988 pub/comp/msdos/ka9q/finger.arc
unido.informatik.uni-dortmund.de:    21263 Jul 22  1988 pub/comp/msdos/ka9q/ka9q-epr.arc
unido.informatik.uni-dortmund.de:    33664 Jun 23  1988 pub/comp/msdos/ka9q/kit.arc
unido.informatik.uni-dortmund.de:      993 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/README.Z
unido.informatik.uni-dortmund.de:    20821 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/diffs.Z
unido.informatik.uni-dortmund.de:      320 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/ka9q.lnk.Z
unido.informatik.uni-dortmund.de:       83 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/lmacros.h.Z
unido.informatik.uni-dortmund.de:     1080 Dec  8  1988 pub/comp/msdos/ka9q/msft-c/msft-c.head.Z
unido.informatik.uni-dortmund.de:     4702 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/rsh.c.Z
unido.informatik.uni-dortmund.de:      240 Jun 25  1988 pub/comp/msdos/ka9q/msft-c/rsh.h.Z
unido.informatik.uni-dortmund.de:     7413 Jun 22  1988 pub/comp/msdos/ka9q/nelson.arc
unido.informatik.uni-dortmund.de:    54598 Jun 22  1988 pub/comp/msdos/ka9q/net_amig.arcab.Z
unido.informatik.uni-dortmund.de:    27096 Feb  2  1988 pub/comp/msdos/ka9q/net_amig.xbtoa
unido.informatik.uni-dortmund.de:    43264 Jul 27  1988 pub/comp/msdos/ka9q/net_bm.arc
unido.informatik.uni-dortmund.de:    26249 Jun 22  1988 pub/comp/msdos/ka9q/net_des.arc
unido.informatik.uni-dortmund.de:   143157 Jun 22  1988 pub/comp/msdos/ka9q/net_doc.arc
unido.informatik.uni-dortmund.de:   116992 Jun 22  1988 pub/comp/msdos/ka9q/net_mac.arc
unido.informatik.uni-dortmund.de:   144384 Jul 27  1988 pub/comp/msdos/ka9q/net_pc.arc
unido.informatik.uni-dortmund.de:   315648 Jun 28  1988 pub/comp/msdos/ka9q/net_src.arc
unido.informatik.uni-dortmund.de:   124213 May 18 17:07 pub/comp/msdos/ka9q/net_st.arc
unido.informatik.uni-dortmund.de:   374272 Jan 20  1989 pub/comp/msdos/ka9q/nos.arc
unido.informatik.uni-dortmund.de:   177024 Jun 28  1988 pub/comp/msdos/ka9q/nrnet.arc
unido.informatik.uni-dortmund.de:    47379 Jun 22  1988 pub/comp/msdos/ka9q/pxx107.arc
unido.informatik.uni-dortmund.de:    40448 Sep  1  1988 pub/comp/msdos/ka9q/server16.arc
unido.informatik.uni-dortmund.de:   574436 May 18 16:57 pub/comp/msdos/ka9q/src.arc
unido.informatik.uni-dortmund.de:    57076 Jun 22  1988 pub/comp/msdos/ka9q/tnc_ash.arc
unido.informatik.uni-dortmund.de:    15790 Jun 22  1988 pub/comp/msdos/ka9q/tnc_ldr.arc
unido.informatik.uni-dortmund.de:    52127 Jun 22  1988 pub/comp/msdos/ka9q/tnc_tnc1.arc
unido.informatik.uni-dortmund.de:    49542 Jun 22  1988 pub/comp/msdos/ka9q/tnc_tnc2.arc
unido.informatik.uni-dortmund.de:   148547 May 18 16:46 pub/comp/msdos/ka9q/userman.arc
unido.informatik.uni-dortmund.de:    31383 May 18 16:46 pub/comp/msdos/ka9q/userref.nr.Z
wuarchive.wustl.edu:      433 Oct 28 18:00 mirrors/msdos/ka9q-tcpip/00-index.txt
wuarchive.wustl.edu:      137 Apr  2  1989 mirrors/msdos/ka9q-tcpip/aaaread.me

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:24:02 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: TAR: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files that matched ".tar" in their pathnames:

bu-it.bu.edu:  1110032 Jun 11  1988 src/NETIMPL/ka9q.tar.Z
bu.edu:  1110032 Jun 11  1988 src/NETIMPL/ka9q.tar.Z
col.hp.com:   491913 Sep 28 18:39 packet/nos/ka9q/src.tar.Z
freebie.engin.umich.edu:   887197 Oct 12 18:28 pub/Amiga/ka9q_slfp.tar.Z
ftp.uu.net:   105431 Jul 31 19:11 networking/ka9q/server.tar.Z
ftp.uu.net:   485117 Aug 22 00:09 networking/ka9q/src.tar.Z
ftp.uu.net:   439811 Sep 22 18:19 networking/ka9q.slip.tar.Z
gatekeeper.dec.com:    71499 Aug 29 13:43 pub/net/ka9q/clarkson/compat.tar.Z
hp4nl.nluug.nl:    56135 Apr 19  1990 pub/network/ka9q/pktd.tar.Z
isy.liu.se:    51200 Nov  7  1989 ka9q/nosunix.tar
mcsun.eu.net:    56135 Apr 19  1990 network/ka9q/pktd.tar.Z
munnari.oz.au:    94985 Jun  1 15:10 pub/net/secure-ka9q.tar.Z
sics.se:    32733 Aug 19 22:50 archive/packet/ka9q/nos/lwpnos.tar.Z
sics.se:   249849 May  4  1990 archive/packet/ka9q/nos/netnix.tar.Z
sics.se:   475715 Oct 17 10:31 archive/packet/ka9q/nos/nosunix-all.tar.Z
sics.se:    44895 Oct  9 09:47 archive/packet/ka9q/nos/nosunix.tar.Z
sics.se:   491913 Oct  2 13:14 archive/packet/ka9q/nos/src.tar.Z
sics.se:    92160 Oct 19  1989 archive/packet/ka9q/nos/streams.tar
sics.se:    32784 Apr 11  1990 archive/packet/ka9q/nos/tundrvr.tar.Z
sirius.ucs.adelaide.edu.au:    55080 Apr 20  1990 pub/ka9q/compat.kit.tar.Z
sirius.ucs.adelaide.edu.au:    26463 Dec 16  1989 pub/ka9q/pcnfs.tar.Z
sirius.ucs.adelaide.edu.au:    56135 Apr 20  1990 pub/ka9q/pktd.tar.Z
sun.soe.clarkson.edu:    71499 Jul  8 17:39 pub/ka9q/compat.tar.Z
sunic.sunet.se:    32733 Aug 19 20:50 .sics.se/archive/packet/ka9q/nos/lwpnos.tar.Z
sunic.sunet.se:   249849 May  4 21:36 .sics.se/archive/packet/ka9q/nos/netnix.tar.Z
sunic.sunet.se:    45013 Aug 19 20:52 .sics.se/archive/packet/ka9q/nos/nosunix.tar.Z
sunic.sunet.se:    92160 Oct 19  1989 .sics.se/archive/packet/ka9q/nos/streams.tar
sunic.sunet.se:    32784 Apr 11 21:14 .sics.se/archive/packet/ka9q/nos/tundrvr.tar.Z
surya.waterloo.edu:   486895 Aug  8 05:51 networking/ka9q/nos/src.tar.Z
terminator.cc.umich.edu:   887197 Oct 12 18:20 pub/amiga/ka9q_slfp.tar.Z
terminator.cc.umich.edu:   887197 Oct 12 18:19 pub/ka9q.tar.Z
thumper.bellcore.com:   105431 Jul 31 19:09 pub/ka9q/g0bsx/server.tar.Z
thumper.bellcore.com:    81920 Sep 24 19:09 pub/ka9q/incoming/wa2zzx.tar
thumper.bellcore.com:   491913 Aug 28 20:09 pub/ka9q/nos/src.tar.Z
thumper.bellcore.com:   142179 Nov  7 21:42 pub/ka9q/util/unzip.tar.Z
unido.informatik.uni-dortmund.de:   249849 Jul  5 12:59 other/ka9q/flash/netnix.tar.Z
unido.informatik.uni-dortmund.de:    44681 Jul  5 12:59 other/ka9q/flash/nosunix.tar.Z
unido.informatik.uni-dortmund.de:    92160 Jul  5 12:59 other/ka9q/flash/streams.tar
unido.informatik.uni-dortmund.de:    32784 Jul  5 12:59 other/ka9q/flash/tundrvr.tar.Z
unido.informatik.uni-dortmund.de:    44921 Aug 23  1989 other/ka9q/ka9q.smtp.tar.Z
unido.informatik.uni-dortmund.de:   349131 Aug 23  1989 other/ka9q/ka9q.tar.Z
uniwa.uwa.oz.au:    94985 Oct 19 14:54 pub/pc/ka9q/net.tar.Z
uunet.uu.net:   105431 Jul 31 19:11 networking/ka9q/server.tar.Z
uunet.uu.net:   485117 Aug 22 00:09 networking/ka9q/src.tar.Z
uunet.uu.net:   439811 Sep 22 18:19 networking/ka9q.slip.tar.Z
vax.cs.pitt.edu:   242411 Jul 19  1989 pub/ka9q/nos-unix.tar.Z
vega.hut.fi:    26463 Sep  9  1989 pub/pc/comutil/ka9q/pcnfs_packet_driver_interface.tar.Z

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:25:19 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: ZIP: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files that matched ".zip" in their pathnames:

col.hp.com:   431468 Sep 28 18:41 packet/nos/ka9q/src.zip
col.hp.com:   490310 Oct 30 17:56 packet/nos/ka9q/src1029.zip
ditmela.cng.dit.csiro.au:    30898 Sep 12 04:57 pub/ka9q/bmexe332.zip
ditmela.cng.dit.csiro.au:   431487 Sep 12 04:56 pub/ka9q/nos-src.zip
ece.orst.edu:   159775 Sep 12 20:13 pub/ka9q/wg7jexe.zip
ece.orst.edu:   484873 Sep 12 20:13 pub/ka9q/wg7jsrc.zip
emunix.emich.edu:   193200 Aug  8 22:35 tmp/ka9q.zip
ftp.uu.net:    37729 Aug 21 15:30 networking/ka9q/modem.zip
ftp.uu.net:   180552 Jul 23 11:57 networking/ka9q/nose0716.zip
ftp.uu.net:    31201 May  8  1990 networking/ka9q/nosman.zip
ftp.uu.net:   469506 Jul 23 11:57 networking/ka9q/noss0716.zip
ftp.uu.net:   431505 Aug 25 02:50 networking/ka9q/src.zip
gatekeeper.dec.com:    56408 Aug 29 13:43 pub/net/ka9q/clarkson/compat.zip
gatekeeper.dec.com:   378426 Aug 29 13:56 pub/net/ka9q/clarkson/drvrss6a.zip
grivel.une.oz.au:   587381 Nov  3 03:12 pub/ka9q/emm102911.zip
grivel.une.oz.au:   490310 Oct 30 10:22 pub/ka9q/src1029.zip
hp4nl.nluug.nl:   139737 Jan 29  1990 pub/network/ka9q/nos_0125.zip
iraun1.ira.uka.de:    95105 Feb  2  1990 pub/ibm-pc/Ka9q/bm.zip
iraun1.ira.uka.de:   488850 Feb  2  1990 pub/ibm-pc/Ka9q/ka9q.zip
kolvi.hut.fi:    29618 Feb 24  1990 tcpip/ka9q/fixm108.zip
kolvi.hut.fi:   452032 Jun 14 00:21 tcpip/ka9q/nos/g1emm61210.zip
kolvi.hut.fi:   452796 Jul  6 10:21 tcpip/ka9q/nos/g1emm62211.zip
kolvi.hut.fi:   454164 Jul 11 21:20 tcpip/ka9q/nos/g1emm71010.zip
kolvi.hut.fi:   431468 Sep  5 11:40 tcpip/ka9q/nos/src.zip
kolvi.hut.fi:   490310 Nov  3 12:04 tcpip/ka9q/nos/src1029.zip
mcsun.eu.net:   139737 Jan 29  1990 network/ka9q/nos_0125.zip
miki.cs.titech.ac.jp:   490540 Jan 30  1990 pub/ka9q/nos0117.zip
miki.cs.titech.ac.jp:   258434 Jan 30  1990 pub/ka9q/terakoya.zip
miki.cs.titech.ac.jp:   156344 Jan 30  1990 pub/ka9q/uupc.zip
samba.acs.unc.edu:   488850 Jan 22  1990 pub/novell_gate/ka9q.zip
shamash.cdc.com:    51401 Oct 27 10:50 pub/ka9q/nn901027.zip
sics.se:    13113 Dec  1  1989 archive/packet/ka9q/fixmail.zip
slopoke.mlb.semi.harris.com:    95105 Feb  1  1990 pub/pc/ka9q/bm.zip
slopoke.mlb.semi.harris.com:   488850 Oct 24 22:31 pub/pc/ka9q/ka9-src.zip
sun.soe.clarkson.edu:    56408 Jul 11 11:21 pub/ka9q/compat.zip
sun.soe.clarkson.edu:   378426 Jun 22 10:22 pub/ka9q/drvrss6a.zip
sunic.sunet.se:    13113 Dec  1  1989 .sics.se/archive/packet/ka9q/fixmail.zip
terminator.cc.umich.edu:   193200 Aug  6 23:51 msdos/communications/ka9q/ka9q.zip*
thumper.bellcore.com:    42578 Nov 12 18:05 pub/ka9q/dsp/modem.zip
thumper.bellcore.com:   587473 Nov  5 18:26 pub/ka9q/g1emm/emm02912.zip
thumper.bellcore.com:   454816 Jul 20 00:43 pub/ka9q/g1emm/emm71410.zip
thumper.bellcore.com:   455728 Aug 14 16:09 pub/ka9q/g1emm/emm81010.zip
thumper.bellcore.com:   474839 Sep 13 16:03 pub/ka9q/g1emm/emm82812.zip
thumper.bellcore.com:   515082 Sep 28 16:21 pub/ka9q/g1emm/emm82814.zip
thumper.bellcore.com:   517969 Oct  5 16:31 pub/ka9q/g1emm/emm82816.zip
thumper.bellcore.com:   518101 Oct  9 09:34 pub/ka9q/g1emm/emm82817.zip
thumper.bellcore.com:   527938 Oct 29 19:06 pub/ka9q/g1emm/emm82823.zip
thumper.bellcore.com:   372146 Nov 12 16:49 pub/ka9q/g1emm/g1emmkit.zip
thumper.bellcore.com:   598253 Nov  9 16:09 pub/ka9q/g1emm/kh110810.zip
thumper.bellcore.com:   599919 Nov 12 14:04 pub/ka9q/g1emm/kh110812.zip
thumper.bellcore.com:   375259 Nov 15 18:33 pub/ka9q/incoming/g1emmkit.zip
thumper.bellcore.com:   584127 Nov 15 14:34 pub/ka9q/incoming/kh111410.zip
thumper.bellcore.com:    51401 Oct 28 01:53 pub/ka9q/incoming/nn901027.zip
thumper.bellcore.com:    40323 Nov 15 15:52 pub/ka9q/incoming/tcppt1.zip
thumper.bellcore.com:    28166 Nov 16 20:42 pub/ka9q/incoming/was1114a.zip
thumper.bellcore.com:     6231 Nov  6 18:32 pub/ka9q/nos/asmobj.zip
thumper.bellcore.com:   431468 Aug 28 19:56 pub/ka9q/nos/src.zip
thumper.bellcore.com:   490310 Oct 29 17:19 pub/ka9q/nos/src1029.zip
thumper.bellcore.com:   494069 Nov  6 08:14 pub/ka9q/nos/src1105.zip
thumper.bellcore.com:   506305 Nov  7 20:48 pub/ka9q/nos/src1107.zip
thumper.bellcore.com:   506399 Nov  8 22:58 pub/ka9q/nos/src1108.zip
thumper.bellcore.com:   527789 Nov 12 19:20 pub/ka9q/nos/src1112.zip
thumper.bellcore.com:   527798 Nov 14 23:21 pub/ka9q/nos/src1114.zip
thumper.bellcore.com:   180552 Jul 23 11:57 pub/ka9q/pa0gri/nose0716.zip
thumper.bellcore.com:   182123 Aug 22 10:33 pub/ka9q/pa0gri/nose0819.zip
thumper.bellcore.com:   196500 Sep 20 15:52 pub/ka9q/pa0gri/nose0828.zip
thumper.bellcore.com:   469506 Jul 23 11:56 pub/ka9q/pa0gri/noss0716.zip
thumper.bellcore.com:   541395 Aug 22 10:34 pub/ka9q/pa0gri/noss0819.zip
thumper.bellcore.com:   568913 Sep 20 15:54 pub/ka9q/pa0gri/noss0828.zip
thumper.bellcore.com:    35944 Aug 24 22:10 pub/ka9q/util/lzexeeng.zip
thumper.bellcore.com:    20352 Aug  9 13:56 pub/ka9q/util/tar.zip
thumper.bellcore.com:    21471 Aug  9 18:13 pub/ka9q/util/vi.zip
uunet.uu.net:    37729 Aug 21 15:30 networking/ka9q/modem.zip
uunet.uu.net:   180552 Jul 23 11:57 networking/ka9q/nose0716.zip
uunet.uu.net:    31201 May  8  1990 networking/ka9q/nosman.zip
uunet.uu.net:   469506 Jul 23 11:57 networking/ka9q/noss0716.zip
uunet.uu.net:   431505 Aug 25 02:50 networking/ka9q/src.zip
uxc.cso.uiuc.edu:   488850 Jan 24  1990 mail/novell-gw/ka9q.zip
wuarchive.wustl.edu:    30898 Jul 22 19:00 mirrors/misc/ka9q-tcpip/bmexe332.zip
wuarchive.wustl.edu:   360960 Apr 16  1990 mirrors/misc/ka9q-tcpip/driverss.zip
wuarchive.wustl.edu:    19916 Jul 22 19:00 mirrors/misc/ka9q-tcpip/nntp4nos.zip
wuarchive.wustl.edu:   193200 Aug 13 19:00 mirrors/misc/ka9q-tcpip/nos-slfp.zip
wuarchive.wustl.edu:   431468 Aug 28 19:00 mirrors/misc/ka9q-tcpip/nos-src.zip
wuarchive.wustl.edu:   490310 Oct 29 18:00 mirrors/misc/ka9q-tcpip/src-1029.zip

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

Date: 26 Nov 90 00:26:25 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu![e-mail]  (Phil Howard KA9WGN)
Subject: ZOO: where to find KA9Q files for anonymous FTP
To: [e-mail]

These are files that matched ".zoo" in their pathnames:

kolvi.hut.fi:   740266 Jun 15 21:12 tcpip/ka9q/atari/atari.zoo
sunic.sunet.se:   512188 Jan 28  1990 .sics.se/archive/packet/ka9q/nos/amiganos.zoo

--

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<[e-mail]> | no matter what the particular issue is all about.

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

End of Packet-Radio Digest
******************************
Date: Tue, 27 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #204
To: packet-radio


Packet-Radio Digest         Tue, 27 Nov 90       Volume 90 : Issue 204

Today's Topics:
           beams, was Re: TCP/IP via NET/ROM nodes
   Could someone please summarize, or suggest lit. ref's? (2 msgs)
               Help NOS Params (2 msgs)
              Packet with TS830S
              satelite ftp site.
                 TNC220 EPROM

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 26 Nov 90 15:23:18 GMT
From: cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!crdgw1![e-mail]  (Donald P Perley)
Subject: beams, was Re: TCP/IP via NET/ROM nodes
To: [e-mail]

In article <[e-mail]>, kb2glo@cbnewsj (thomas.kenny) writes:
> Until
>I get more power out and a beam antenna I'd like to reach an IP
>switch via NET/ROM nodes which I am able to reach.

Apologies if this was a flamefest put to bed before I started reading the
group...

What is the bottom line vis a vis packet etiquette of using a beam antenna
for packet?

Pro:

Your signal is stronger.. maybe you can avoid using a digipeater or
netnodes.

Con:

You won't hear a lot of signals that are off your beam, so you will
double with other stations more often than with an omni antenna.

Other considerations?

-don perley - [e-mail] (packet)

[e-mail]

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

Date: 26 Nov 90 13:11:55 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!caen!uflorida![e-mail]  (Brian Bartholomew)
Subject: Could someone please summarize, or suggest lit. ref's?
To: [e-mail]

O.K.  I've read the FAQ posting.  I've read all the messages in the
group.  I've looked for other groups that might better apply.  And I
still don't know anything.  Would one of you kind people out there
take the time to summarize for me the choices I have in fast packet
radio?

I am a long-time UNIX user who is about to be financially in a
position to purchase my own workstation for home use.  Unfortunatly, I
have become addicted to good net.access, so now I am looking for ways
to connect the home machine to the work network.  SLIP or PPP come to
mind as software adaptations suitable for running over a modem, but
2400 baud just doesn't cut it.

Ultimatly I am looking for a single workstation's share of an
ethernet, i.e. about 1 Mbits/second, but I realize the notion of
shoving this through a voice line is hopeless.  I saw a posting
earlier mentioning a modem that is perhaps more reasonable, at
5Kbits/second.  If this modem could be used on a plain Bell line, and
it didn't cost many thousands of dollars for a pair, I would be
overjoyed.

In general, I am taking the long view of all this.  I will be wanting
conectivity from now onwards.  ISDN isn't going to get to my doorstep
for at least another 10 years.  If these sorts of modems need the
sorts of bandwidth I think they do, radio in some form is the only
reasonable solution.  I have a reasonable hardware background, and
would be willing to get whatever liscenses it would take to run this
sort of setup.  Getting a ham liscense might even be the key to
picking up what remaining electrical engineering I am interested in
learning.

Please note that I explicitly not interested in: re-inventing
multitasking, virtual memory, a TCP/IP protocol stack, TCP/IP clients,
net access for the budgetarily challenged, or anything else having to
do with underpowered, OS-crippled MS-DOS machines.  On the other hand,
I am perfectly willing to share what I learn and build with the net
and anyone else who is interested.


--
"Any sufficiently advanced technology is indistinguishable from a rigged demo."
-------------------------------------------------------------------------------
Brian Bartholomew       UUCP:       ...gatech!uflorida!mathlab.math.ufl.edu!bb
University of Florida   Internet:   [e-mail]

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

Date: 26 Nov 90 18:43:14 GMT
From: prism!mailer.cc.fsu.edu!sun13![e-mail]  (John Murray)
Subject: Could someone please summarize, or suggest lit. ref's?
To: [e-mail]

In article <[e-mail]> [e-mail] (Brian Bartholomew) writes:
>
>I am a long-time UNIX user who is about to be financially in a
>position to purchase my own workstation for home use.
[...]
>2400 baud just doesn't cut it.
[...]
>earlier mentioning a modem that is perhaps more reasonable, at
>5Kbits/second.  If this modem could be used on a plain Bell line, and
>it didn't cost many thousands of dollars for a pair, I would be
>overjoyed.

A Telebit Trailblazer can run 9600 baud over Ma Bell's lines. Of course,
you need another Trailblazer on the other end, but don't you have the
same problem with packet?

The advantage of using common-carrier Ma Bell is that you don't have to
worry about being held responsible for putting alt.sex.pictures out over
the air! :-) :-)

>Brian Bartholomew      UUCP:       ...gatech!uflorida!mathlab.math.ufl.edu!bb

--
Disclaimer: Any opinions above (or below) have nothing to do with reality.
John R. Murray              |"Death needs time for what it kills to grow in for
[e-mail]   | Apuk's sweet sake, you stupid vulgar greedy ugly
Supercomputer Research Inst.| American Death Sucker.." - William S. Burroughs

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

Date: 21 Nov 90 08:11:56 GMT
From: usenet.ins.cwru.edu!ncoast!n8hsp![e-mail]  (Terry Bell)
Subject: Help NOS Params
To: [e-mail]

Can someone define the following params for me and also what are you
setting them up at?
ax max (?)
ax pthresh (?)         (please define)
ne acktime (?)
ne choketime (?)
ne derate (?)          (please define)
ne promiscuous (?)     (please define)
smtp batch (?)         (please define)
Has anyone been able to get the "nntp" client to work with a DOS UUCP
program? I am reviewing the DOS UUCP "Waffle" program but I understand
the "nntp" server is not complete yet. I have two DOS machines here and
would like the NOS machine to access and retrieve the rec.ham-radio.packet
newsgroup off the UUCP machine and put it in the NOS "areas" notefile.
Thanks, Terry
N8HSP @WA8BXN.OH !usenet.ins.cwru.edu!ncoast!n8hsp!tbell

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

Date: 27 Nov 90 03:13:45 GMT
From: [e-mail]  (Brian Kantor)
Subject: Help NOS Params
To: [e-mail]

In article <[e-mail]> [e-mail] (Terry Bell) writes:

1. Your return address is invalid.  Don't use ampr.org addresses on the
internet nor on Usenet unless you've set up an MX forwarder to pass the
mail back to you.  You haven't.

>Can someone define the following params for me and also what are you
>setting them up at?

NOS now comes with a pretty decent document that explains most of these,
and there is also a sample autoexec.net file to set them to typical
values.  You should be able to get both from whereever you got the NOS
code from.
        - Brian

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

Date: 26 Nov 90 23:05:36 GMT
From: usc!wuarchive!uwm.edu!bionet!synoptics!@ucsd.edu  (Jerome Kaidor)
Subject: Packet with TS830S
To: [e-mail]

Followup-To:
Distribution: world
Organization: SynOptics Communications Inc. Santa Clara, Ca.
Disclaimer: Sender is *solely* responsible for the contents of message
Keywords:

   I'd like to thank the net for the informative responses I've gotten
about my TS830.  As you recall, I wanted to use the narrow filters in
SSB mode.  Well, this weekend, I got out my schematics.  I found out
that the filters were indeed switched with diodes, and it turned out
to be a fairly straightforward task to break the line from the mode
switch to the SSB filter diodes.  It turned out that the digital hold
switch is a DPDT unit, even though it is only used as an SPST.  So I
disconnected the digital hold wires and taped them off, and converted
the switch to select the 500 HZ filter in SSB mode.  If anybody's
interested, I will email the gory details...

    I found the 500Hz filter very usable for narrow-shift packet. The
MFJ1278 has a tuning indicator that shows whether the signal is ON
frequency or OFF, to an accuracy of about 10 Hz.  So I set that 500Hz
filter right on by tuning to a frequency with no signals, and
centering the filter noise with the tuning indicator and the IF shift.
  Of course on a rig without a tuning indicator, this would be pretty
hard....

        - Jerry Kaidor, KF6VB

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

Date: 27 Nov 90 06:04:32 GMT
From: unmvax!ariel.unm.edu!nmsu!opus![e-mail]  (smouldering dog)
Subject: satelite ftp site.
To: [e-mail]

I apologize that this is probably not the interest group to ask this
but...does anyone know where I could get weather satelite pictures
via ftp?  I am also interested in decoding satelite data and porting
to my amiga...has anyone done this?
        thanx,
        owen white.
--

-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-
         safe is to sex as fish is to bicycle
-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-=-*-=-

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

Date: Mon, 26 Nov 90  22:20:43 EET
From: [e-mail]
Subject: TNC220 EPROM
To: [e-mail]

Does anyone have any new EPROM for the TNC220
which has KISS and or MAILBOX .
I have V 1.1.5 and WA8DED EPROM .
Maybe the WA8DED eprom have KISS but it does not work properly.
Can any one helpme.
I make a few mods to the VHF MODEM and its mush more better now.
Any TNC220 user can send me mail for the above.
TNX George SV1BDS Athens
[e-mail]

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

End of Packet-Radio Digest
******************************
Date: Wed, 28 Nov 90 04:30:03 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #205
To: packet-radio


Packet-Radio Digest         Wed, 28 Nov 90       Volume 90 : Issue 205

Today's Topics:
          1200 baud AFSK (VHF) packet on 10 meters?
           beams, was Re: TCP/IP via NET/ROM nodes
    Could someone please summarize, or suggest lit. ref's?
                   Request

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 27 Nov 90 17:56:27 GMT
From: att!cbnewsj![e-mail]  (thomas.kenny)
Subject: 1200 baud AFSK (VHF) packet on 10 meters?
To: [e-mail]

I remember a thread a while back on this subject but I don't remember
the final concenus of the airchair layers :-) In other words here we
go again....

I have a Tiny 2 TNC that I use on 2 meters. I'm curious as to if I can
use it on 10 meters. I have an old rule book but I'm sure it's still
accurate on this matter. It seems you can transmit 1200 baud data on
the 10 meter band. The only other restriction is that the mark and space
audio frequencies differ by 1000 Hz or less. Can somebody tell me if
the modems used in the VHF TNCs fit into this category.

If it is legal I'm aware of the hassles I'll have turning on SSB but
willing to live with it to just try it out. I might even try it out
on 10 FM up above 29 Mhz of course...

Any information would be appreciated. Thanks and 73 DE KB2GLO, Tom.

--
Tom Kenny, KB2GLO
uucp:   att!lzatt!tek          internet: [e-mail]
packet: [e-mail]  ampr: [e-mail] [44.64.0.10]

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

Date: 27 Nov 90 19:19:36 GMT
From: usc!sdd.hp.com!wuarchive!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: beams, was Re: TCP/IP via NET/ROM nodes
To: [e-mail]

In article <[e-mail]> perley@galaxy (Donald P Perley) writes:
>
>What is the bottom line vis a vis packet etiquette of using a beam antenna
>for packet?
>
>Pro:
>
>Your signal is stronger.. maybe you can avoid using a digipeater or
>netnodes.
>
>Con:
>
>You won't hear a lot of signals that are off your beam, so you will
>double with other stations more often than with an omni antenna.
>
>Other considerations?

Narrowly beamed signals (902 Mhz and above) allow space diversity frequency
reuse and are highly recomended. At 2 meters the necessary beamwidths
require moonbounce grade antennas and a low power cellular type approach
is better for channel reuse. Still, if you are forced to use a digipeater
or node, you double the time your signal and the repeated copy of your
signal occupies the channel and a high site digi can hear stations that
can't hear you. They might attempt to transmit to the digi while you are.
This creates a hidden terminal problem that can rapidly bog down a channel.
So, even at two meters, direct connections are beneficial IF there is no
high site digi on the channel. It's best for point to point work to move
off the channels that have high site digis or nodes.

Gary KE4ZV

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

Date: 27 Nov 90 19:07:34 GMT
From: snorkelwacker.mit.edu!usc!wuarchive!emory!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: Could someone please summarize, or suggest lit. ref's?
To: [e-mail]

In article <[e-mail]> [e-mail] (Brian Bartholomew) writes:
>
>
>O.K.  I've read the FAQ posting.  I've read all the messages in the
>group.  I've looked for other groups that might better apply.  And I
>still don't know anything.  Would one of you kind people out there
>take the time to summarize for me the choices I have in fast packet
>radio?
>
>I am a long-time UNIX user who is about to be financially in a
>position to purchase my own workstation for home use.  Unfortunatly, I
>have become addicted to good net.access, so now I am looking for ways
>to connect the home machine to the work network.  SLIP or PPP come to
>mind as software adaptations suitable for running over a modem, but
>2400 baud just doesn't cut it.
>
>Ultimatly I am looking for a single workstation's share of an
>ethernet, i.e. about 1 Mbits/second, but I realize the notion of
>shoving this through a voice line is hopeless.  I saw a posting
>earlier mentioning a modem that is perhaps more reasonable, at
>5Kbits/second.  If this modem could be used on a plain Bell line, and
>it didn't cost many thousands of dollars for a pair, I would be
>overjoyed.

If you want to be able to do work related stuff as well as ham related
stuff, your best bet is a pair of 19.2kb Telebit Trailblazers over the twisted
pair at $900 each. Or a pair of generic 9.6kb V42bis modems at about $500 each.

Over radio, the 56kb modems output 29Mhz RF in a 70khz bandwidth. You
need a transverter to kick them up to a UHF frequency. The modem is
$225 and a suitable transverter is in the $160 to $320 range. If you want
more info on the Grapes 56k modems, contact KD4NC by email via the bang
path of gatech!kd4nc!dug and he will send you info and ordering instructions.

The next step down in radio modems is the 9600 baud G3RUH modem available as a
daughter board for the TNC2 from Paccom in Florida. Pricing of a system goes
like this: Modem $99, TNC2 $130, radio $449. Some serious shopping can get the
radio down in the $300 range. Some serious tinkering can convert a surplus
commercial band radio for about $100.

There is experimental work in progress on 1 Mbit links at around 1 Ghz and
10 Mbit links at 10 Ghz. When this becomes available it will be line of sight
type links with pricing in the $200 to $500 range (estimate).

So there are at least three ways to go in relatively high speed packet and
all are around $500 per station. Note that packet overhead will limit your
throughput to less than channel capacity in all cases. The 56kb link acts
much like a direct dialup 19.2kb session when telneting and the G3RUH acts
like a 2400 dialup line. For file transfers where long packets are the
rule, throughput approaches channel capacity.

If you want to do work related things over radio, you can get a commercial
license for a point to point link. 9600 baud is the best you will be able
to do on a commercial channel however. You could get an experimental license
to use the 56kb modems, but there is government paperwork involved. For
non-work related things, a ham radio license will let you play with any
speed you like as long as you stay in the band (upper UHF). Go for it.

Gary KE4ZV

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

Date: 27 Nov 90 17:22:00 EST
From: Michael (M.A.) Meystel <[e-mail]>
Subject: Request
To: <[e-mail]>

Not to be posted to the list:

To whom it may concern:

I have been subscribed to the packet-radio list for a long time now. For
some reason, I am missing digests 144-159, 161-189, and 191-199.

Were they mailed to me?

Perhaps I am subscribed as [e-mail] - my mail from there is
forwarded to me at [e-mail]

Thank you.

Mike

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

End of Packet-Radio Digest
******************************
Date: Thu, 29 Nov 90 04:30:05 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #206
To: packet-radio


Packet-Radio Digest         Thu, 29 Nov 90       Volume 90 : Issue 206

Today's Topics:
     Anybody using integrated microprocessor & serial I/O chips?
    Could someone please summarize, or suggest lit. ref's?
           Internet/Packet Radio gateway? (2 msgs)
           New England TCP sample newletter
             Question for usenet
             WA8NLC 3456 mHz transverter
          Windows 3.0 based packet radio programs ?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 28 Nov 90 15:34:38 GMT
From: bacchus.pa.dec.com!hollie.rdg.dec.com!ryn.esg.dec.com!muhthr.dec.com!bruthr.cdad.dec.com![e-mail]  (Andy Payne)
Subject: Anybody using integrated microprocessor & serial I/O chips?
To: [e-mail]

Has anyone done anything with the integrated microprocessor and serial I/O chips
(like the 68302:  68k core + ISDN style serial I/O, or the Z80181:  Z180 core + 1
SCC-style channel)?

These chips (especially the '302) look like a great way to build small, cheap,
low-power packet-radio gadgets.

--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI       Internet:    [e-mail]
                 UUCP:        ...decwrl!ad.enet!payne

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

Date: 28 Nov 90 22:01:29 GMT
From: att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!cci632![e-mail]  (Just another hired gun (n2hkd))
Subject: Could someone please summarize, or suggest lit. ref's?
To: [e-mail]

In article <[e-mail]> [e-mail] (John Murray) writes:
>In article <[e-mail]> [e-mail] (Brian Bartholomew) writes:
>A Telebit Trailblazer can run 9600 baud over Ma Bell's lines. Of course,
^^^^^ my t2500 runs at 19.2K, Zmodem transfer 1500cps+ (pc was slow)
This does not mean that it will be that fast for network SLIP applications.
You can expect 960 minus over head (lot's for appletalk) using V.32
modem. The reason for this is that Telebit PEP mode is half duplex
(on the phone side) and V.32 is full duplex. The turn around time
on PEP is about the same as V.32 through put.

Getting a deicated Bell set up for 56Kb via  lease line is another
way to go. Push them for ISDN and maybe they'll give you a cost
break. By the way ISDN has been Beta tested here. This area is well
on it's way to have ISDN  be something real within 1991.

Good Luck

--

email:   [e-mail] or cb@cci632  or !rochester!kodak!n2hkd!curtis
Curtis Braun, N2HKD, Computronics, PO Box 1002 Fairport NY, 14450

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

Date: Wed, 28 Nov 90 10:22:55 EST
From: [e-mail] (Sigurd P. Crossland - Contel WTP 2214N 703-818-4202)
Subject: Internet/Packet Radio gateway?
To: [e-mail]

What is the trick to getting E-Mail to a recipient on the ampr.org domain?  I
have been monitoring the Packet-Radio Digest for the past several months and
have yet to see any mention of any Internet gateway.  Recently the requirement
to reach a colleague (N6BFM) who has a login on W8ZF prompted the search for a
means to reach him via the Internet.

A nameserver query for the ampr.org domain returns both UCSD.EDU and
THUMPER.BELLCORE.COM and they have records for w8zf-pc.ampr.org, IP address
44.36.8.33.  Are w8zf and w8zf-pc one and the same and are they actually nodes
on the Internet which should be accessible using the TCP/IP suite?   Must one
take into consideration some longer propagation delays associated with radio
communications as opposed to conventional Internet links when using ping?  Are
the ampr.org sites listed only accessible by using SMTP, specifying a source
route, an E-Mail gateway, or some other technique?

My attempts to mail a message to [e-mail] have been bounced with
a "w8zf-pc.ampr.org: Network is unreachable" reply on differing occasions.  (I
had thought there might be some sort of window of availability associated with
the ampr.org domain.)

Any assistance in getting an E-Mail correspondence initiated with N6BFM will be
most appreciated as will any enlightenment that might be shared on the packet
radio network topology in general.  Thanks.  Take care.

- Sig

Sigurd P. Crossland                       Internet: [e-mail]
Contel Federal Systems                    Telephone: [phone]
15000 Conference Center Drive
Chantilly, VA  22021

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

Date: Wed, 28 Nov 90 08:21:57 -0800
From: brian (Brian Kantor)
Subject: Internet/Packet Radio gateway?
To: [e-mail]

There is no packet gateway between the AMPRNet (network 44) and the rest
of the internet.  AMPRNet is not a connected network.

There are a few mail forwarders for a few specific destinations, but
in general, there is currently no way to exchange mail with ampr.org
sites and the internet.

There is a problem in that some people have obtained ampr.org addresses
and then connected their systems using uucp or some other non-IP
protocol, are using the ampr.org hostname in their return addresses,
yet have not set up nor registered a forwarder with the internet.
Thus mail from them reaches the internet via uucp-to-internet gateways,
but there is no path back.

As domain administrator for AMPR.ORG, I am distressed by this turn of
events and try to enlighten people as to what they are doing wrong, but
it continues to occur.

Apologies for your difficulties.

    Brian Kantor
        [e-mail]  BRIAN@UCSD ucsd!brian

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

Date: 28 Nov 90 18:00:24 GMT
From: att!cbnewsj![e-mail]  (thomas.kenny)
Subject: New England TCP sample newletter
To: [e-mail]

Today I uploaded a sample newsletter of the New England TCPer to
thumper.bellcore.com. The newsletter is in post script format and
can be found under the name netcper.ps.Z. Enjoy and 73 DE KB2GLO, Tom.

--
Tom Kenny, KB2GLO
uucp:   att!lzatt!tek          internet: [e-mail]
packet: [e-mail]  ampr: [e-mail] [44.64.0.10]

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

Date: 15 Nov 90 08:55:16 GMT
From: usc!elroy.jpl.nasa.gov!grian!puffin!wd6ehr.ampr.org![e-mail]  (Mike Curtis [phone])
Subject: Question for usenet
To: [e-mail]

could someone please help me,im very confused,my new swr meter for
tuning my antenna,its from korea the meter not the antenna,the
directions are hard to understand and say that the reflected power
lower than the forward power reading,is this ok,this does not sound
right to me,doesnt it have to be higher because all the power is
going to the antenna,mike has showed me stuff from usenet and i think
you can help,you guys know a lot,he said its ok to write this,thank
you for helping,this is my first ham letter,im waiting for my technician
license to come in the mail,i wish it would hurry up,i like ham radio,
mike lets me use his radios,ive talked to ian in england and alan in
tahetie in the pacific ocean,please send answers to wd6ehr mike,he
said you know what this means and will send it there,mike will give
them to me.73s,david bright

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

Date: 28 Nov 90 19:04:54 GMT
From: [e-mail]  (Rick Spanbauer)
Subject: WA8NLC 3456 mHz transverter
To: [e-mail]

Has anyone investigated using the WA8NLC 3456 mhz transverter as the
RF deck for either the DSY modem (one would need to downconvert the
NLC 144 mHz IF -> 28 mHz) or the FSK section of the N6GN 10 ghz data modem?
The NLC transverter seems like a really nice choice for data, at least
for a microwave neophyte like myself, as it is apparently designed to
plug and chug, ie no tuneups, network analyzer aligned filters, etc.
Down East Microwave sells the kit for $195.

                    Rick Spanbauer, WB2CFV
                    State U of NY/Stony Brook

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

Date: Wed, 28 Nov 90 09:06:24 PST
From: [e-mail] (CAL-LAB (MS:JER2-85 TEL:7589))
Subject: Windows 3.0 based packet radio programs ?
To: "[e-mail]"@HERMES.intel.com

Are there programs available that utilize the graphics of Windows 3.0
in the Packet Radio world ? e.g. - KA9Q's net, NOS or just something fancier
than the built-in teminal program of Windows 3.0.
73,
Rich

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

End of Packet-Radio Digest
******************************
Date: Fri, 30 Nov 90 04:30:04 PST
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V90 #207
To: packet-radio


Packet-Radio Digest         Fri, 30 Nov 90       Volume 90 : Issue 207

Today's Topics:
           FTP site for KA9Q NOSNET wanted.
            Internet/Packet Radio gateway?
            Microprocessors w/ serial port
                   NET-ROM
                Slow Scan tv?
                TexNet
          Windows 3.0 based packet radio programs ?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 27 Nov 90 23:41:56 GMT
From: hpcc05!col![e-mail]  (Bdale Garbee)
Subject: FTP site for KA9Q NOSNET wanted.
To: [e-mail]

>Does anyone know of an anonymous FTP site for aquiring
>Phil Karn's TCP/IP NOSNET software?  Also, if anyone knows who
>the IP coordinator for the Minneapolis area is I'd appreciate that
>info.

Try thumper.bellcore.com, in the directory tree pub/ka9q.  Phil's bits are in
the nos subdirectory, the G1EMM variant is in it's own subdirectory, etc...

Bdale

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

Date: 29 Nov 90 19:19:29 GMT
From: csus.edu!wuarchive!emory!emcard!wa4mei!ke4zv![e-mail]  (Gary Coffman)
Subject: Internet/Packet Radio gateway?
To: [e-mail]

In article <[e-mail]> [e-mail] (Sigurd P. Crossland - Contel WTP 2214N 703-818-4202) writes:
>
>What is the trick to getting E-Mail to a recipient on the ampr.org domain?  I
>have been monitoring the Packet-Radio Digest for the past several months and
>have yet to see any mention of any Internet gateway.  Recently the requirement
>to reach a colleague (N6BFM) who has a login on W8ZF prompted the search for a
>means to reach him via the Internet.
>
>A nameserver query for the ampr.org domain returns both UCSD.EDU and
>THUMPER.BELLCORE.COM and they have records for w8zf-pc.ampr.org, IP address
>44.36.8.33.  Are w8zf and w8zf-pc one and the same and are they actually nodes
>on the Internet which should be accessible using the TCP/IP suite?   Must one
>take into consideration some longer propagation delays associated with radio
>communications as opposed to conventional Internet links when using ping?  Are
>the ampr.org sites listed only accessible by using SMTP, specifying a source
>route, an E-Mail gateway, or some other technique?
>
>My attempts to mail a message to [e-mail] have been bounced with
>a "w8zf-pc.ampr.org: Network is unreachable" reply on differing occasions.  (I
>had thought there might be some sort of window of availability associated with
>the ampr.org domain.)
>
>Any assistance in getting an E-Mail correspondence initiated with N6BFM will be
>most appreciated as will any enlightenment that might be shared on the packet
>radio network topology in general.  Thanks.  Take care.

As Brian Kantor will probably tell you, Network 44 is not connected to the
internet. In addition w8zf-pc.ampr.org is a defunct address for W8ZF. You
may be able to get uucp mail to W8ZF via the path ...gatech!kd4nc!w8zf since
Dean has a login on the system kd4nc.  There are several Unix systems run by
amateurs in the Atlanta area. Your friend N6BFM may be able to get a login on
one of them.

Gary KE4ZV

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

Date: Thu, 29 Nov 90 23:23 CST
From: [e-mail]
Subject: Microprocessors w/ serial port
To: [e-mail]

I have had considerable experience with Motrola's 68HC11. It is a
very capable chip. It comes in several configurations. It is
designed as a control processor. It has 2 serial ports, 4 A/D
converters, an extremely sophisticated timer and very low power.
It has up to 512 bytes of RAM and up to 2K of EEPROM on board.
It can run stand alone or it can easily access 64K of RAM.
Motorola has very good support for the 68HC11 including small C
compiler, a basic interpreter, an assembler of course, a real
time operating kernel (all Public Domain) and a bulletin board.
I understand they also have a good C compiler they sell for about
$100.00. The make an evaluation board that cost about $120.00
(half that if you are a student). All you need to run is a +/- 12
and 5 volt power supply (could steal it off your computer and
computer with a serial port and a terminal program. The board has
an onboard monitor called Buffalo that will upload, download
single step, assemble and do all the normal monitor things. Also
included are a good assembler, small C and some other stuff.

This board can be used to make real stuff. I have built several
projects including a self filling scale, and CW transmitter, and a
very sophisticated timer. We have also built up a board that only
uses five volts by using a MAX 232 chip for the rs232 Driver.

Also when you call Motorola you can get real people that know what
they are talking about and call back when they say they will.

I am very interested in doing a packet port to the 68HC11
preferably in C. I have a very good C development system at my
disposal and need to implement some type of computer to computer
radio link for a research project. So I might as well kill two
birds with one stone. If any one knows of a C implementation of
AX.25 (public domain preferable but other deals are possible) I
am sure interested!!!!

We also have developments systems for 68xxx and Intel 8051. IMHO
68HC11 is the far the better choice for the stuff I do, control
of agricultural machinery, buildings and food possessing equipment.


Gordon Couger N5QAQ/AA AGENGCC@OSUCC

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

Date: 29 Nov 90 19:33:02 GMT
From: mintaka!snorkelwacker.mit.edu!usc!oxy![e-mail]  (Bryan Douglas Reeves)
Subject: NET-ROM
To: [e-mail]

Can someone please summarize the theory of NET-ROM packewt fowarding and
networking?  I have been told it is he predominent form here in
California, and would like more information on using it.

73, Doug

------------------------------------------------------------------------
B. Douglas Reeves (N6XHW)       [e-mail]  (Internet, of course!)
147.705/445.450 in So Cal        1600 Campus Rd., La, Ca, 90041 (USnail)
"Cogito, ergo es."                Occidental College Computer Networking

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

Date: 29 Nov 90 01:59:00 GMT
From: sgi!cdp![e-mail]
Subject: Slow Scan tv?
To: [e-mail]

Hello, a bit of a long shot.. Does anyone know anything about slow
scan video (specifically those Japanese picture phones?).

Doug Dulmage

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

Date: 29 Nov 90 19:37:05 GMT
From: csus.edu!wuarchive!usc!gate.oxy.edu!oxy![e-mail]  (Bryan Douglas Reeves)
Subject: TexNet
To: [e-mail]

Does anyonw have a e-mail address for TexNet?  I need internet or bitnet,
not packet (unless there's a good gateway..).

73, Doug

------------------------------------------------------------------------
B. Douglas Reeves (N6XHW)       [e-mail]  (Internet, of course!)
147.705/445.450 in So Cal        1600 Campus Rd., La, Ca, 90041 (USnail)
"Cogito, ergo es."                Occidental College Computer Networking

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

Date: 29 Nov 90 14:54:30 GMT
From: [e-mail]  (Peter John Skelly)
Subject: Windows 3.0 based packet radio programs ?
To: [e-mail]

I'm concidering writing a packet program for windows.  Any suggestions would be
helpful.


Pete Skelly

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

End of Packet-Radio Digest
******************************